home > undergraduate > Software Requirements and Project Management  > Software Requirements and Project Management Homepage

Software Requirements and Project Management (670.300) 6 points / Semester 1 Handbook Description The official Handbook entry Unit Aims This unit studies the characteristics of software systems: complexity and change; management of large software engineering projects: configuration management, team work and communication; Requirements engineering: elicitation, analysis, specification, documentation and evolution; Process management: planning, estimation, metrics and risk; Verification and validation of software: inspections, test case design and execution, reliability and defect metrics. On successfully completing this unit students will be able to, 1. distinguish software products from other engineered products; 2. select and apply requirements engineering techniques for the elicitation, analysis, specification, verification and evolution of software requirements; 3. select and apply project management techniques for process modelling, planning, estimation, process metrics and risk management; 4. perform software verification and validation using inspections, design and execution of system test cases, and use reliability and defect metrics; and 5. become effective team members, undertake problem identification, formulation and solution, and apply knowledge of basic science and engineering skills. Teaching Staff Unit Coordinator Dr Rachel Cardell-Oliver, Rm 1.20 rachel@csse.uwa.edu.au Consultation Times Thursday or Friday Unit Home Webpage www.undergraduate.cs.uwa.edu.au/units/670.300.html Unit Help Webpage http://www.csse.uwa.edu.au/run/helpse300 Unit Help Email helpse300@csse Textbook Bernd Bruegge and Allen H Dutoit, Object-Oriented Software Engineering: Using UML, Patterns and Java, 2nd edition, Prentice Hall, 2004, ISBN 0-13-047110-0 Students who already have a copy of the 2000 1st edition of this book (ISBN 0-13-489725-0) may use that. Recommended Reading Ian Sommerville, Software engineering 7th Ed. Addison-Wesley International Computer Science Series, 2004 (see also the 6th edition, 2001, UPSL 005.1 2001 SOF) Roger S. Pressman adapted by Daryl Ince, Software engineering : a practitioner's approach 5th ed., European adaptation. McGraw-Hill, 2000, UPSL 005.1 2000 SOF N.E. Fenton and S.L. Pfleeger, Software Metrics, 2nd ed. International Thompson Publishing, 1997, UPSL 005.14 1997 SOF Contact Hours This unit consists of 24 hours of lectures and 16 hours of practical classes. There are 8 practical classes to be held in weeks 2, 3, 6, 7, 8, 10, 11 and 12. It is expected that you will need to undertake additional study (recommended reading and questions from the lectures, preparation and review of the practical classes and assignment work) to achieve satisfactory progress in this unit. You should be spending 10 hours a week on this unit so an additional 6 hours per week is a reasonable estimate. Type Time Day Location Lecture 4-5 Thu Woolnough Lecture 12-1 Fri Austin Assessment Assessment is by a research essay (with two deliverables), a portfolio of practical work (deliverables in week 8 and week 12), a mid-semester test, and a final 2 hour examination held in June. The examination and mid-semester test assess students' understanding of the practice and theory of requirements engineering, project management and verification and validation for large software systems. The practical work portfolio assesses students' ability to apply team work and communication skills to problem solving in software requirements and project management. The research essay assesses students' ability to undertake problem identification, formulation and solution in software requirements and project management. Submissions for the essay and the practical portfolio must be handed in by 12 noon on the due dates (see below) to the Computer Science Office 1.31A. 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 Dates Essay Plan 3% 12 noon Wed Apr 6th (week 5) Mid-semester test 10% 12noon Fri 8 Apr (week 5) Final Essay 15% 12 noon Wed 11 May (week 10) Practical Portfolio 12% 12 noon Wed 1 June (week 13) Examination 60% 2hrs, June Examination Period 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 Requirements and Project Management  > Software Requirements and Project Management Homepage    This information is correct as at 01-Mar-2005, 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© 2005 School of Computer Science, & Software Engineering The University of Western Australia CRICOS Provider Code: 00126G Last updated: 01-Mar-2005