home > undergraduate > Software Engineering Design  > Software Engineering Design Homepage

Software Engineering Design (670.200) 6 points / Semester 2 Handbook Description The theory and practice of designing large software systems, with emphasis on the object-oriented design paradigm. Basic software process models; Requirements analysis; UML modelling; The design process; Design constraints; Software architecture; Design patterns; Configuration management; Software reuse; Verification and validation; Designing test cases; Software project documentation. Prerequisites: Software Engineering 104 or Java 124; Unit Aims The major aim of the unit is to teach techniques for the design, implementation and documentation of programs which are larger than encountered in earlier units. On successfully completing this unit students will, Be able to identify characteristics of software products and to contrast software with other engineered products; Use the object paradigm to analyse, design and test computer software; Be able to read and analyse requirements documents including UML models; Be able to 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 Coordinator/Lecturer A/Prof Mark Reynolds Room 1.16 mark@csse.uwa.edu.au Tutors Mark, Tim, Adam Web-based help facility www.cs.uwa.edu.au/cgi-bin/help200 Textbook Bernd Bruegge and Allen H Dutoit, Object-Oriented Software Engineering (2nd ed), Prentice Hall, 2004, ISBN 0-13-191179-1 Recommended Reading Ian Sommerville, Software engineering 7th Ed. Addison-Wesley International Computer Science Series, 2004 Roger S. Pressman, Software engineering : a practitioner's approach 5th ed., European adaptation. McGraw-Hill, 2000 See also the SED200 bibliography and UWA SE Resources Page links on the unit home page Contact Hours This unit consists of 26 hours of lectures and 12 hours of practical classes. Supervised practical classes, of 2 hours each, are held in weeks 3, 5, 7, 9, 11, 13 at times and locations to be advised (see sed200 timetable). Students are expected to undertake around 7 study hours per week of unsupervised learning (recommended reading and questions from the lectures, preparation and review of the practical classes and assignment work) to achieve satisfactory progress in this unit. Type Time Day Location Lecture 9-10 Tue Murdoch L.Th. Lecture 10-11 Fri Murdoch L.Th. Assessment Assessment is by two written assignments, a mid-semester test and a final 2 hour examination held in November. 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. Practical 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. Before undertaking this unit, students are encouraged to read Section 6.11 of the Guidelines for Academic Assessment. In particular, students will be required to demonstrate satisfactory progress in all practical components of assessment before being permitted to sit the final examination. Assessment % of final mark Assessment Due Dates Mid Semester Test 10% 10am Friday 3rd September (week 7) Assignment 1 (Design) 15% 12noon Wednesday 7th September (week 8) Assignment 2 (Verification) 15% 12noon Wednesday 20th October (week 12) Exam 2 hours 60% November Examinations Unsatisfactory Progress Any student who does not demonstrate satisfactory progress in this unit, as defined in the FECM Policy 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. 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 School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism. Faculty Scaling Final assessment is subject to the Faculty Scaling Policy.     home > undergraduate > Software Engineering Design  > Software Engineering Design Homepage    This information is correct as at 21-Jul-2004, but is subject to change from time to time. In particular, The University reserves the right to change the content and/or method of presentation and/or the method of assessment of any unit of study, to withdraw any unit of study or programme, and/or to vary arrangements for any programme. Copyright© 2004 School of Computer Science, & Software Engineering The University of Western Australia CRICOS Provider Code: 00126G Last updated: 21-Jul-2004