PROPOSED SCHEDULE  FOR PROJECT DEVELOPMENT

Greetings! The proposed schedule is listed below:

The group will firstly meet up to get to know one another. Next, the group will assume the role of the Client and decide on a project for the developing group to work on. The preliminary requirements for such a system will also be decided. Furthermore, the group, now assuming the role of the Developer, will be approached by another group to undertake a project. The group will discuss this new project if there is time.

WEEK 2: Detailed Discussion, Tools Familiarization and 1st Case Diagram Preparation

For this week, roles and responsibilities should be assigned to all members of the group. It is important that the group has to familiarize will the various software tools such as Rational Rose and ASP software. Moreover, secondary refinements of the system specifications should be done as well. Case diagram should be done and the website should be started as soon as possible as well.

WEEK 3: Setting up Website, 1st Refinement of Use Case Diagram and Setting up of Database Software

The group will decide whether to use the Object Oriented Approach or the Function Oriented Approach. Refinement of the preliminary case diagram is essential so as to give a full picture of the project. Potential List of the project will also determine the various classes and objects, hence it has to be done too. Writing of the database for the software will start with the use of ASP programming language. The new website should be up and running this week.

Week 4: Confirm/Reject list and Object/Class Diagram

Revision of potential list will be done this week and the confirm/rejection list based on the criteria of Needed remembrance, Needed services and Multiple attributes will be determined. Since object oriented analysis is decided, at least a preliminary object/class diagram must be drawn up. This would help to develop the software and the team will refine the object diagram in due time.

Week 5: Develop Software design

This week, the database should be largely developed. A final refined object Diagram will be done. This will ensure consistency among the team as we go about our software design.

Week 6 and 7: Implementation and Testing I

In these 2 weeks, the database will be actively refined and troubleshoot to meet the Client's requirements. Testing will be done to ensure that the system works under the stated requirements. Use of either static and dynamic testing will suffice.

Week 8 and 9: Testing II and System Integration

In these 2 weeks, white box testing techniques comprising basis path testing, graph matrices and loop testing will be performed on the system. Black box testing comprising quivalence partitioning, boundary value analysis, logic based testing and data validation testing will also be performed. Incremental integration will be performed on unit tested objects in the specified general-specialization or whole-part structure. The system integration should be done according to the refined object diagram and refined structure charts.