1. Software Engineering, A Practitioner`s Approach, Pressman R. S., 5th European Ed., McGraw-Hill 2000.

1. Software Engineering, Somerville I., Addison Wesley,
2. Software Metrics, Fenton N. E. & Pfleeger S. L., 2nd Ed., International Thompson Computer Press.
3. TickIT Guide, British Standards Institute

1. Critical awareness of the practice in quality and process improvement, including the current ISO standards and SEI programmes (CMMI), and their impact on software engineering.
2. Critical awareness of the state of the art in project management, risk assessment models and management, of the software development process.
3. A critical appreciation of the duties and responsibilities of a professional Software Engineer.
4. A critical awareness of the role of experimentation and empirical assessment to underpin software engineering.

5. Determine appropriate criteria against which to select development strategies for specific circumstances.
6. Apply a selective approach to the choice and exploitation of appropriate software development tools and techniques in order to increase the productivity and quality of the software development process.

Students will review the development of legal responsibilities of the Software Engineer, and review examples of the application of professional standards, codes of conduct and legislation such as the Data Protection act.

Review of ISO standards and SEI CMMI/ CMM, TSP, PSP guidelines, as applied to software engineering and development, with examples/case studies of their impact.

Students will be introduced to generic concepts of risk, and review risk assessment models for system development (such as RISKIT and SEI Software Risk Management) and interdependent systems change (such as RAMESES) through case studies. Students will review the development of the field of project management through review of for productivity and quality, and for people, problem and process elements Software measurement - need to measure consistently, objectivity and subjectivity in measurement, prediction systems and direct and indirect measures with examples of recent, useful metrics - what they can do why they are valid. A review, through examples and case studies, of software measurement for project management, development processes, and product characteristic assessment and prediction.

Students will review the selection process and factors applied to; various development methods (data oriented, object oriented, XP and Formal) and development processes, software development tools and techniques in order to increase the productivity and quality of the software development process.

This module will be taught by lectures covering the key topics of the syllabus, directed reading, and tutorials (incorporating case study work). Assessment will be via a combination of Research Based Paper, and Examination.

Lectures: 25 hours
Tutorial: 25 hours
Directed Reading and Self-Study: 100 hours
Research: 50 hours

ASSESSMENT METHODS

1. One individual research-based assignment contributing 50% of the overall module mark and testing learning outcomes a,b, c and e.
2. One formal examination contributing 50% 0f the overall module mark and testing learning outcomesa,b c, d and f.