12335 (v.4) Software Engineering 351
| Area: | Department of Computing |
| Credits: | 25.0 |
| Contact Hours: | 3.0 |
| Lecture: | 1 x 2 Hours Weekly |
| Practical: | 1 x 1 Hours Weekly |
| Prerequisite(s): | 8934 (v.7) Software Engineering 252 or any previous version
|
| Syllabus: | Quality, safety and reliability from the standpoint of ethics and professional responsibility. Evolving and assessing a mature Quality Management System (ISO 9000:2000, CMM, CMM-I). Processes for verification and validation of software-based systems. Processes for managing safety and reliability. Strategies for improving reliability using fault tolerance in software based systems. Software reuse and the impact on cost and quality. The use of Graphical Modelling Languages and Formal Specification Techniques (Z, DFD, UML) to overcome difficulties communicating synchronization and timing issues in real-time systems and facilitating formal reasoning. |
| |
| Unit Outcomes: | Upon successful completion of this unit, the student should be able to prepare Quality Management Documentation in ISO 9000:2000 format and understand how an organization prepares for and receives ISO 9000:2000 certification. Students will have learnt how an organization's quality maturity can be assessed using SEI CMM and CMM-I and will be able to use formalal specification techniques (Z, DFD and UML) for simple formal reasoning and communication of synchronization and timing issues. They will gain anunderstanding of the importance of developing a quality culture within an organization and the significance of planning, measurement, and analysis in managing quality and reliability and finally, they will be able to develop well-defined, repeatable, measurable, and auditable processes for managing the quality, safety and reliability of software-based systems. |
| Text and references listed above are for your information only and current as of September 30, 2003. Please check with the unit coordinator for up-to-date information. |
| Unit References: | Fishman, C., 1996, 'They write the right stuff' http:www.fastcompany.com/online/06/writestuff.html. NASA, 2002, 'ARC Quality Manual', NASA Ames Research Center, ISO 9000 Process Documents, http://www.isoeasy.org/iso_9000_process_docuents.htm. NASA, 1999,'Project Management for the Design, Development, and Maintenance of Software', NASA Ames Research Center, ISO 9000 Process Documents, http://www.isoeasy.org/iso_9000_process_documents.htm. Oberg, J., 1999, 'Why the mars probe went off course', IEEE Spectrum, December 1999, pages 34-39. Hall, A., 1990, 'Seven Myths of Formal Methods', IEEE Software, September, 1999, pp 11-19. Wing, J. M., 1990, 'A Specifier's Introduction to Formal Methods', IEEE Computer, September, 1999, pp 8-24. Nissanke, N., 1999, 'Formal Specification, Techniques and Applications', Springer, London. Delisle, N. and Garlan, D., 1990, 'A Formal Specification of an Oscilloscope', IEEE Software, September, pp 29-36. Ward, P.T. and Mellor, S.J., 1985, 'Structured development of Real-Time Systems', Vol. 1, Prentice Hall, New York. Douglass, B. P., 2000, 'Introduction to Real-Time Systems and Objects' in 'Real-Time UML: Developing Efficient Objects for Embedded Systems', 2nd Edition, pp 1-47, Addison-Wesley, Reading. |
| Unit Texts: | Sommerville, I., 2002, 'Software Engineering', Addison-Wesley, Harlow. |
| |
| Unit Assessment Breakdown: | Mid-semester test 20%. Assignment 20%. Final Examination 60%. |
| Year | Location | Period | Internal | Area External | Central External | | 2004 | Bentley Campus | Semester 1 | Y | | | |
Current as of: February 2, 2004
CRICOS provider code 00301J
