CC2007 - Software Engineering 1 (2017/18)
| Module specification | Module approved to run in 2017/18, but may be subject to modification | ||||||||||||
| Module title | Software Engineering 1 | ||||||||||||
| Module level | Intermediate (05) | ||||||||||||
| Credit rating for module | 15 | ||||||||||||
| School | School of Computing and Digital Media | ||||||||||||
| Assessment components |
|
||||||||||||
| Running in 2017/18(Please note that module timeslots are subject to change) | No instances running in the year |
Module summary
This module develops knowledge and skills for producing quality software components and
introduces principles of software project management.
Prior learning requirements
Introduction to Programming (CC1006N or CC1F06N)
Module aims
The aims of this module are to provide sound knowledge and skills for producing quality software components and to apply such knowledge and skills by designing and developing realistic software applications. It also provides students with the opportunity to understand the activities and procedures involved in software project management.
Syllabus
1. Software life cycle models: waterfall, prototyping, incremental.
2. Requirements analysis: techniques and tools.
3. Design: techniques and tools.
4. Validation and verification: techniques and tools.
5. Project Management: project planning and scheduling techniques, basic cost estimation techniques, staff management.
Learning and teaching
A combination of formal lectures and tutorials will be used. Students will be given ample opportunity to promote their own learning on a one-to-one or group basis. Case studies will be used to apply the relevant skills and technical contents to the curriculum of the unit. Group work is promoted for a short period during lecture sessions and seminar sessions.
Lectures and tutorials are 4 hours per week, and unsupervised learning 2 hours per week.
Learning outcomes
On successful completion of this module students must:
1. demonstrate an understanding of the basic concepts and stages involved in the software
development process [A2];
2. identify and document the needs of users [A1];
3. design a suitable conceptual/programming model for a software application [A3];
4. demonstrate an understanding of various software verification and validation techniques and
use some of these techniques in practice [A2];
5. demonstrate an understanding of software project management and related activities
[A2,A3].
Assessment strategy
There will be a two-hour examination worth 50% of the total marks at the end of the semester. There will be one piece of course work worth 50%. Students will be asked to work as a group to develop a solution for a given scenario.
This module is pass on aggregate.
Bibliography
1. Software Engineering– A Practitioner’s Approach by Roger S Pressman, McGraw-Hill.
Fifth Edition (2001), 0-07-709411-5
2. Software Engineering by Ian Sommerville, Addison-Wesley (2001), 0201-39815 X