Module Provider: |
School of Systems Engineering |
Number of credits: |
20 [10 ECTS credits] |
Level: |
C (Certificate) |
Terms in which taught: |
Autumn, Spring and Summer |
Module Convenor: |
Dr
RJ
McCrindle |
Pre-requisites: |
|
Co-requisites: |
|
Modules excluded: |
|
Module version for: |
2007/8 |
Aims:
This module will provide an understanding of the concepts and practice of software engineering; supported by general problem solving, simple algorithms and mathematical formulation of a variety of common tasks. |
Assessable learning outcomes:
By the end of the module, it is expected that the student will be able to:
describe the System Life Cycle, software development phases and approaches and process models
differentiate between tactical and strategic approaches to problem solving and judge the appropriate level for specific tasks
construct algorithms in pseudo-code for simple problems such as travelling salesperson
translate certain types of English sentences into formal notation
write out truth tables and perform some simple formal proofs
carry out simple systems investigation, requirements analysis and specification
carry out data modelling
carry out architectural and detailed design
use the knowledge gained during analysis and design and apply to a variety of given scenarios
describe the essentials of project planning, configuration management, testing |
Additional outcomes:
The module also aims to encourage the development of the following skills:
working with others in a group project and understanding a team approach to projects
understanding of why planning is important in their own work
appreciating the need for back-ups |
Outline content:
Software Engineering; Problem Solving; pseudo-code and algorithms; the language and notation of Discrete Mathematics and its use in simple logic, basic reasoning and proofs |
Brief description of teaching
and learning methods:
Two 1-hour lectures each week and one 1-hour seminar/exercise class each week. The lectures will cover the theoretical aspects of the subject and the seminars will cover exercises and case studies on the practice. The seminars, which can be real or electronic, will also control the group project that will run throughout the year. Reports will be required at the end of the first and second terms and a group presentation will be given in the third term. |
Contact hours:
| |
Autumn |
Spring |
Summer |
| Lectures |
20 |
20 |
4 |
| Tutorials/seminars |
10 |
10 |
4 |
| Practicals |
|
|
|
| Other contact (eg study visits) |
|
|
|
| |
|
|
|
| Total hours |
30 |
30 |
8 |
| |
|
|
|
| Number of essays or assignments |
Weekly exercises |
Weekly exercises |
|
| Other (eg major seminar paper) |
1 |
1 |
1 |
|
Assessment:
Coursework
Coursework will be undertaken by small groups of students (4-6). Students will be required to keep individual log books.
Relative percentage of coursework: 45%
Examinations: One 2-hour written examination
Requirements for a pass
Students will be required to obtain a mark of 40% overall based on coursework and the examination.
Re-assessment
Students will be re-examined in September (examination only). |
staff
UoR Home