软件工程评估和管理英文讲义CSEM01 handbook 2005 15.doc

School of Computing and TechnologyMODULE HANDBOOKCSEM01Software Engineering Evolution and ManagementTitle:Software Engineering Evolution and ManagementModule Code:CSEM01Module Leader:Name:Anne ComerRoom:DGIC 229Tel no:0191 515 3419Email address:ersunderland.ac.ukHANDBOOK CONTENTS:1.Introduction to the Module2.General Information3.Learning Outcomes4.Teaching, Learning and Assessment Approaches5.Planned Schedule6.Reading List1.Introduction to the ModuleCSEMO1 forms a 15- credit module with two distinct software engineering strands:-software evolution- software managementLecturing and tutorial sessions will provide somewhere in the region of forty hours lecturer and tutor contact time. It is expected that you will undertake a further one hundred and ten hours of study.1.1 Indicative ContentSoftware Engineering project evaluation and planning. Project monitoring. Project management: personal, team and project based. Software development approaches. Critical evaluation of development approaches and their advocates. Choosing a development methodology for a software engineering project. Impact of methodology on project plan. Management techniques appropriate to software engineering projects. Historical and contemporary software development approaches: competing software development/ evolution approaches. Personal performance. Evaluation of team performance within a software engineering project Appropriate development approach for a software engineering project with given constraints and domain.1.2 Module DescriptorThe module is summarised in the module descriptor which can be found through the school web site, starting at the following URL:http:/osiris.sunderland.ac.uk/programmers/modlevel.php?level=MFor more specific details, and for module and learning materials, please use the module home page, at the following URL:http:/www.cet.sunderland.ac.uk/cs0aco/csem01/csem01.htm 1.3 Necessary Previous KnowledgeA first degree in computing/software engineering or related subject will be advantageous when coming to this module.2.General Information2.1 Teaching Team MembersNameRoomTel:EmailMs. Anne Comer 229515 3419ersunderland.ac.ukProf. Helen Edwardshelen.edwardssunderland.ac.ukThe majority of lectures will be given by Anne Comer. Both Anne Comer and Prof. Edwards will be on-hand during the tutorials.2.2 Support ServicesThe Learning Resource Centre (LRC) for the St Peters campus is administered by Library Services and located in the Reg Vardy Centre. Please read the notices to be found there and in the library, regarding opening hours and other arrangements. All assignments must be handed in to the LRC by the prescribed dates and times.2.3Notice BoardsPlease regularly look at your Software Engineering programme notice board; from time to time it may be necessary to place important notices, requiring your attention, on these notice boards. Such notices will also be added to the module home page.2.4TimetableTeaching on the module consists of four hours timetabled per week for up to twelve weeks. The four hours shall be split between a lecture and tutorial.The lecture will be used to disseminate material as well as providing guidance for students as to appropriate methods of study for each topic week by week.The supervised tutorial will be used for discussing case studies. Tutorial work will often be undertaken with students working in collaborative groups.2.5Learning HoursThe module is worth 15 credits, which means that you are expected to spend about 150 hours of study on the topics covered in the module. These expected learning hours include time spent in lectures and tutorials, and the time you spend on assignments and individual study. They reflect the amount of effort you are likely to expend to ensure the best possible chance of passing the module.2.6AssessmentCoursework 100% based on one portfolio worth 60% and one critical review (including presentation) worth 40% together covering all learning outcomes.2.7Support MaterialsCopies of the lecture slides and other teaching materials will generally be available prior to the lectures and can be located on the home page for CSEM01. In certain circumstances some additional notes on topics covered may be made available. 3.Learning OutcomesLearning outcomes are defined in terms of knowledge and ability. That is, what you are expected to know at the end of the module, and what you are expected to be able to do by the end of the module. The learning outcomes for CSEM01 are stated as follows:Knowledge:1. Management techniques appropriate to software engineering projects.2. A range of historical and contemporary software development approaches.Abilities:3. Plan and control personal tasks within a software engineering project 4. Evaluate the team performance within a software engineering project 5. Work effectively within a software engineering project contributing to the delivery of a product.6. Contribute to the planning, scheduling, monitoring and control of a software engineering project.7. Critically evaluate competing software development/evolution approaches8.Choose an appropriate development approach for a software engineering project with given constraints and domain.4.Teaching and Learning ApproachesStudents will be required to adopt an experiential and reflective learning approach to the module. Through the tutorials, a project will be set that will require students to work in small teams to deliver the product. It is a requirement that students adopt project management processes to realise the objective and, at the micro-level, demonstrate personal project management. Typically such a project would require the students to define rigorous software engineering experiments (and their associated evaluation mechanisms) that could be used to measure the effectiveness of disparate software development/evolution approaches. The module delivery will be task-oriented. The students will be required to critique software engineering approaches: evaluating the strength of evidence supporting claims made by proponents of the approaches and reflecting these against their experiences in their project. The module will be supported by short lectures, task-setting and milestone sessions, group and individual work and directed reading.Lectures: 18 hoursTutorials: 24 hours (including milestone sessions and student presentations) Assignment:40 hoursSelf study:70 hoursAssessment method:Coursework 100% based on one portfolio worth 60% and one critical review (including presentation) worth 40% together covering all learning outcomes.5.Planned ScheduleTeaching will normally be against the topics, and in the sequence shown here, although this may vary from time to time.Week beginningContent21/02/05Module details, Housekeeping, Module web page, Staff, Assignments, Why this module? - its importance and context28/02/05Project Evaluation and Planning (evaluation, measurement and models, impact of method on plan)(Individual Assignment Issued. Due Wednesday 18th May 2005)07/03/05Project Management, CMMI, Quality Management(Group Assignment Issued. Due Wednesday 8th June 2005)14/03/05Maintenance and Configuration Management04/04/05Team Software Process11/04/05Personal Software Process18/04/05Legacy Systems25/04/04Software management - again02/05/04Empirical Assessment in Software Engineering 09/05/04Software Evolution as a process16/05/04Software Evolution as an artefact23/05/04Tidy up; post implemenatation reviews, software testing principles, software reviews.6.Reading List Basili, V, R and Briand, L.C. (Eds) Journal of Empirical Softwa