PROJECT OVERVIEW STATEMENT DEVELOPMENT OF A SOFTWARE Project Name: ENGINEERING LABORATORY OOMeter/I/05 Project Code: Problem/Opportunity The software

engineering program is in need of a laboratory for teaching software engineering courses. Goal The goal of this project is to set up a laboratory environment equipped all the software, hardware and procedures for using them to perform software engineering activities. Objectives The following tasks will be required to achieve the above goal: 1. Install a configuration management (CM) system such as CVS 2. Produce documentation for novices on how to effectively use the CM system 3. Install a UML modeling tool such as Borland Together ControlCenter or Rational Rose 4. Provide documentation for using it to perform specific processes and tasks such as design, requirements modeling, forward and reverse engineering, etc. 5. Provide easy-to-follow documentation(s) on at least one modeling methodology for engineering OO software, for instance eXtreme Programming (XP) 6. Set up testing frameworks such as JUnit and JMeter 7. Provide easy-to-follow documentation for using these testing frameworks 8. Provide forms for logging activities performed by students and other lab users in order to facilitate audits and review of activities 9. Equip instructors and lab assistants with the know-how for using these systems 10. Provide lab manuals for teaching lab components of major software engineering courses Success Criteria The success of the project hinges on the following: 1. Allocation of adequate budget for procuring software, hardware, and books 2. Provision of incentives to motivate team members 3. Adequate coordination and cooperation among team members 4. Some practical experience in engineering OO systems can also help Assumptions, Risks, Obstacles 1. It is assumed that team members would have a good mastery of basic OO concepts, and/or some field experience in using OO technologies such as UML, design patterns, frameworks, etc. 2. It is assumed that every piece of software, hardware, procedure documented would have been tried out hands-on, during the development of the relevant documentation or procedure manual. 3. It is assumed that team members will follow good documentation practices, to facilitate continuity of work Team Leader: Prepared By: Raimi A. Rufai Approved By: Team Members: Date: June 15, 2003 Date