Unit outline for Software Engineering: Design (CITS2220).

6 points / Semester 1
Location: UWA (Crawley)

Handbook description

This unit covers basic software process models and process management including (1) requirements analysis—actors, scenarios and use cases; object identification from use cases; modelling courses of objects with UML class diagrams; modelling object interactions with UML sequence diagrams; modelling the behaviour of individual objects with UML statecharts; (2) software design—using formal rationale to document design decisions; advanced design constraints including reliability, availability, maintainability; (3) software architectures—monolithic, distributed, client/server, event driven; (4) object-oriented concepts and design patterns—observer; abstract factory, adapter; bridge and façade; and (5) testing software—standard test processes (unit tests, integration, system, performance, acceptance, installation); code inspections; equivalence class tests; path testing; conformance testing; and use case tests.

Prerequisites:

Unit aims

Students are able to use the object-oriented paradigm to analyse, design and test computer software; read and analyse requirements analysis documentation including UML models; read and develop system design documents; know several standard software architectures and design patterns; design and execute test cases using white and black box methods; become effective team members; undertake problem identification, formulation and solution; and apply knowledge of basic science and engineering skills.

Teaching staff

Unit Co-ordinator: Dr. Du Huynh

Textbook

Bernd Bruegge and Allen H. Dutoit. Object-Oriented Software Engineering, Prentice Hall, 2004, ISBN 0-13-191179-1.

Recommended texts

• Roger S. Pressman. Software engineering : a practitioner's approach, 5th ed., European adaptation. McGraw-Hill, 2000.
• Ian Sommerville. Software engineering, 6th ed., Addison-Wesley International computer science series, 2001.

Contact hours

38 (lectures: 26 hrs; practical classes: 12 hrs)

Assessment

This comprises two written assignments, a mid-semester test and a final examination. The written assignments develop in-depth technical competence in software engineering design, problem identification, formulation and solution and practical application of methods for designing and testing software. Practice classes support the assignments using group exercises to develop students' ability to communicate and function effectively in a team. The mid-semester test and examination focus on problem solving, the application of basic knowledge and in-depth technical competence in software engineering design. The expectation of lifelong learning is fostered by student-led solutions for software engineering problems and reflection on the quality of those solutions by self-assessment. Supplementary assessment is not available in this unit except in the case of a bachelor's pass degree student who has obtained a mark of 45 to 49 and is currently enrolled in this unit, and it is the only remaining unit that the student must pass in order to complete the course.

Unsatisfactory progress

Any student who does not demonstrate satisfactory progress in this unit, as defined in the Faculty's policies on assessment practices and procedures, may be refused admission to the final examinations. The final deadline for notification of unsatisfactory progress is the last day of Week 10.

Penalties

The School of Computer Science and Software Engineering has adopted a policy on minimum penalties for late items of assessment. This is the default policy of all units unless indicated otherwise, in writing, by the specific unit coordinator.

This policy shall apply to all items of continuous assessment, whether submitted either physically or electronically. Immediately after the submission deadline for an item of continuous assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF. The minimum mark possible for late submission is zero. The percentage is based on the item´s total contribution to the unit´s assessment. For example, a project contributing 40% to the unit´s assessment will incur a penalty of 8 marks for each day late until it is submitted or a mark of zero results.

A more detailed description is given in this School´s policy on late submission. The Faculty does have an appeals procedure, the details of which can found at the policy for appeals.

Special consideration

Applications for consideration, deferral of tests or exams or extensions of time for assignments on medical, personal or other grounds must be lodged with the faculty office no later than three working days after the due date for the assessment in question. This rule will apply to all students, except in exceptional circumstances.

Plagiarism

Plagiarism is broadly defined to be when any portion of the work presented for assessment, can be attributed to another party. The student making the submission should acknowledge what aspects of the presented work is not directly derived by them. For the purposes of plagiarism it is irrelevant that you have been given permission by someone to copy their work and present it as your own.

You are directed to the Faculty's policy on plagiarism.

Academic misconduct

The University of Western Australia strongly supports teaching and learning that promotes academic literacy and ethical scholarship for all students. As part of this commitment, UWA has recently developed new guidelines relating to Academic Misconduct (including plagiarism). It is also developing a range of resources for students and staff to further strengthen academic literacy and ethical scholarship at UWA. Further information is available on the Teaching and Learning website.

Academic Conduct Essentials (ACE)

All students who have not previously been enrolled at UWA are required to complete a short compulsory online module called Academic Conduct Essentials (ACE) within the first 10 weeks of semester. ACE introduces students to essential knowledge regarding ethical scholarship, helps prepare them for the expectations of their university career and informs them of correct academic conduct.

The unit can be accessed via WebCT. The final unit quiz must be completed with a mark of 80% or greater. Students may attempt the quiz as many times as they wish to gain the required pass mark. Completion of the unit will be recorded as an Ungraded Pass (UP) on students’ academic records. Non-completion (NC) within the required timeframe will also be documented on formal academic records.

Faculty Marks Adjustment Policy

Final assessment is subject to the Faculty's scaling policy.

Supplementary Examinations

Supplementary examinations will be awarded in accordance with the Faculty policy on supplementary assessment.

Student rights

Consult the University's Charter of Student Rights and Responsibilities.