433-340 Software Engineering Project

This subject is available only to Software Engineering students, for whom it is mandatory.

433-252 Software Engineering Principles and Tools, 433-253 Algorithms and Data Structures and 433-254 Software Design.

433-341 Software Engineering Process and Practice.

The objectives of this subject are for students to experience team-oriented software engineering; to appreciate the importance of planning and managing the software process; to be involved in requirements elicitation and the subsequent phases of software development including documentation, requirements analysis, specification, design, implementation and testing; and to be familiar with some of the problems that can arise during execution of the software development process. Students will work on a substantial practical team project drawn from areas such as system software, applications software, graphics or networks. They will be involved in all phases of the project, including requirements analysis, functional specification, system design, implementation, documentation and testing. Lectures will cover applied software engineering issues in areas such as configuration management, release engineering, technical reviews, and software testing.

• ability to communicate effectively, not only with engineers but also with the community at large

• ability to undertake problem identification, formulation and solution

• ability to utilise a systems approach to design and operational performance

• ability to function effectively as an individual and in multi-disciplinary and multi-cultural teams, with the capacity to be a leader or manager as well as an effective team member

• understanding of the social, cultural, global and environmental responsibilities of the professional engineer, and the need for sustainable development

• international awareness and openness to the world, based on understanding and appreciation of social and cultural diversity and respect for individual human rights and dignity

Software processes developed by the team for their specific project as evidenced by project management documents, a software requirements specification, design specification, and test plan of approximately 200 pages in total (70%); and a release component consisting of a working system, user documentation and installation (30%). Students are expected to spend 12 hours per week on the project. To pass the subject students must obtain at least 50% overall, 35/70 for their process component, and 15/30 for their release component.