home > undergraduate > Software Engineering 104  > Software Engineering 104 Homepage

Software Engineering 104 (670.104) 6 points / Semester 2 Handbook Description This unit introduces students to the foundations of software engineering by using the object-oriented design methodologies required for the generation and maintenance of reliable software. Students gain an understanding of engineering design practice as it applies to software production through exposure to the software lifecycle model. Concepts are developed and reinforced throughout the unit via case studies and practical exercises using a modern object-oriented programming language and software engineering tools. Unit Aims The major aim of the unit is to introduce students to the software engineering process. The generic learning outcomes are: technical competence in the basics of software engineering ability to undertake problem identification, formulation and solution ability to use a systems approach to design and test software ability to communicate effectively, not only with software engineers but also with stakeholders ability to function effectively as an individual and in a multi-disciplinary team expectation of the need to undertake lifelong learning, and the capacity to do so. Teaching Staff Coordinator/Lecturer Dr Du Huynh Email du@csse.uwa.edu.au Recommended Reading Y. Daniel Liang. Introduction to Java Progamming with SunONE Studio 4, Prentice-Hall, 2003. P. Stevens and R. Pooley. Using UML: Software Engineering with Objects and Components, Addison-Wesley, updated edition, 2000. James M. Slack. Programming and Problem Solving with Java, Brooks/Cole, 2000. Bruce Eckel. Thinking in Java Online or Prentice Hall. Ian Sommerville. Software Engineering Addison-Wesley, 6th edition, 2001. Contact Hours Students will be required to attend 29 hours of lectures, and a 3-hour laboratory session during weeks 3-12 (designed actually to take 2.5 hours). In addition there will be 8 voluntary revision lectures. To complete the work in this unit students are expected to work out of hours. As this is a 6 point unit, a total of 10-12 hours per week on average (including lectures, research, preparation and revision) would be usual. Assessment Each lab during weeks 3-9 will have about 5 exercises. These will be marked by the demonstrator during the laboratory for a total of 45 marks. This will be scaled to give a 15% overall mark towards the final mark for the unit. Students must complete the laboratory exercises for weeks 3-9 before week 10. Students must obtain a mark of at least 45% in the exam in order to pass the unit. A poor exam performance cannot normally be offset by high marks for the lab and project. Description When Weight Mid-semester test week 8 15% Lab component weeks 2-9 15% Project weeks 10-12 20% 2 hour exam November 50% 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 Projects MUST be handed in on the prescribed due date. The exact dates will be given to you on the day you receive the project specification. Projects will have deducted 10% from the final mark for each day late. All work submitted for assessment must be the individual student's own work or the work of an individual group for the project. See the Faculty policy on plagiarism 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.     home > undergraduate > Software Engineering 104  > Software Engineering 104 Homepage    This information is correct as at 08-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: 08-Jul-2004