Project Guidelines The three primary criteria for a successful project are: satisfying the client's needs, usability

of the product, and maintainability over the life of the product. Deliverables 1. Baseline project plan (Feasibility study and plan) a. Due: 17th March, 2011 b. Weight age: 4% 2. Requirements specification (after requirements analysis) and design document (detailed design) a. Due: 28th March, 2011 b. Weight age : 6% 3. Implementation details (presentation of workable prototype and progress) a. Due:25th April, 2011 b. Weight age: 6% 4. Test plans and test results (unit testing, acceptance and integration test results) a. Due: 16th May, 2011 b. Weight age: 4% 5. Final delivery of product and report (project presentation, demo and documentation) a. Due: 6th June, 2011 b. Weight age: 5% on the final product and 5% on the presentation and the final report

The software development team must meet the expectations from their clients:

A careful study of the requirements. A design that meets those requirements. A tested and well documented system that performs as specified.

*Every software team meetings must be minuted by one of the team members and compiled for submission at the end of the semester.*

Baseline Project Plan

Write a short feasibility report that describes the project that you have selected. The exact form of the report is up to you, but it should be well written and suitable to present to an external client. The length is likely to be between five and ten pages. The report should include the following:

An overview of the project describing the scope of the project and the client/organization for which the work will be done. [2] A preliminary requirements analysis and your recommended solution to the problem [1] Software Process to be followed, e.g., modified waterfall model, iterative refinement, prototype, or a hybrid of any other, etc. [2] Outline plan, showing principal activities and project deliverables with a time line (Gantt chart) [2] Concise feasibility study of cost and time. [2] Communication plan both with the client and among your team members[1] Probable technical requirements (details can be given later) Team member roles and responsibilities

The proposal must be well written (this will count toward the final project grade), and must be clear enough so that your client will understand what the project entails.

Requirements Analysis and Design of the system

Requirements Specification: Description of the expected software features and constraints, and other
attributes. 1. Appropriateness of the data gathering techniques undertaken. 2. Clear description of functional requirements analysis using DFDs or Use cases 3. Clear description of data model using ERDs

Design: Description of how the software will meet the requirements.

1. Design overview 2. System architectural design 3. Detailed descriptions of components used 4. Basic user interface design with description of design elements used