Anda di halaman 1dari 2

Term Project Overview 1.

Introduction Real-world software development is different from the experience gained in most class programming projects. Requirements are often unclear and complex. No one can accomplish a fairly complex project single-handedly. Systematic testing is vital. In the real world, one must work with the realization that the software produced will be used by, and maintained by, other people, hence usability and maintainability are important qualities. The purpose of the software Engineering term project is to help you get a feel for real-world software development. Students will work together in teams of 5-6 members. You should understand that the project will require a significant commitment of your time from the beginning of the semester to the end. 1.1 Overall Objectives Learn teamwork. o Task distribution, communication and coordination. o Learn to break down tasks and define responsibilities. o Learn to use supporting tools for team collaboration. Apply problem definition techniques. o Learn to elicit and specify requirements. o Learn to use object-oriented analysis techniques. Create solution systematically. o Learn to create design models. o Develop implementation that is consistent with design. Gain experience with validation techniques. o Learn to conduct formal reviews and inspections. o Learn to plan tests early in the process. 2. Project Proposals Each team must come up with their own proposal for a term project that is nontrivial, sizeable, and fills a realistic need. It must also be original work. The proposed project can be in any application domain (networking, games, security, bioinformatics, graphics, device controllers, software development tools, etc.), as long as you have an expert you can consult for domain specific issues. You will be taking this proposed project from problem definition to system test following basic software engineering processes. 3. Working Together 3.1 Grading Policy Each member of the team is expected to contribute equally to the project. Note that project grades will be given on an individual basis. If there is a clear discrepancy in individual contributions, individual project grades will be adjusted accordingly. 3.2 Team Roles While I do not require any particular team structure, each team must appoint a leader who will coordinate the distribution and assignment of work and serve as the point of contact. 3. Usability

As with real software products, it is expected that the software produced for this project will be easy to use for its intended users. 5. Project Artifacts To Be Submitted These are the artifacts that should be submitted. Requirements Requirements specification document 25% Design Design document 20% Implementation Source code 25% Verification & Validation Test plan Test scripts System test summaries 20% Management Project plan (Weekly logs) Post-mortem report 10%

Anda mungkin juga menyukai