SCHEDULE UPDATE FOR PROJECT DEVELOPMENT

Greetings! In this page we present our software development schedule week by week.

WEEK 2(lab2): Detailed Discussion, Tools Familiarisation and 1st Case Diagram Preparation

The group gathered to appoint the various roles and assigned responsibilities. The lab session was used mainly to discuss the project in further detail, as well as to familiarize with the software such as the Rational Rose program. The website for the interface program is also prepared. The Prelimary use Case Diagram was prepared and uploaded to the website.

WEEK 3(lab3): Setting up Website, 1st Refinement of Use Case Diagram and Setting up of DataBase Software

This week, the Microhub website is up and running. Object Oriented Analysis Approach is used to model the project. The team analysts redefined the preliminary case diagram and identified the Potential List of the project, which has been uploaded into the website. Moreover, we've started on using ASP as the programming language for our database. Programmers are working on the algorithms as well. Priliminary Implementation diagrams have been modelled to assist in later modelling implementation.

Week 4(lab4): Confirm/Reject list and Object/Class Diagram

We have refined our potential list, and rejected those that failed to meet the criteria of Needed remembrance, Needed services and Multiple attributes. Moreover, we have included a preliminary object diagram. This would help us to develop our software and the team will continuously refine the diagram to suit it to the customer's needs. The first sequence diagram is also discussed and drawn.

Week 5(lab5):Revised Class Diagram and Construction of Database

This week the team has revised the preliminary class diagram. The team is delving into the database, creating two databases for the project. The first database(information database) will consist of the time between each MRT and Bus stops. The second database(administrative database) will be used to integrate the first database as well as to provide user interface with the customers. However, both databases are still in the construction phrase. Modular testing of classes will be done once they are ready.

Week 6 and 8 (lab6 and lab 7):Implementation and Testing I

 
In these two weeks, the team has created the adminstrative interface to create bus routes using ASP(admin service protocol) with visual C programming language. In order to do so, the team will first program the software, after which upload the software to a data server system that supports the software.

The information database is also created as well. Software coupling and testing is being carried out to ensure proper data flow between the two databases.

Futhermore, the team has created a small scale model of the map of a island, creating 3 bus routes and 1 MRT route to service the island. The bus stops and mrt stations have stored in the information database and together with the adminstrative database, the team will test out the software, it's robustness and determine the coupling level. Moreover, a collaboration diagram has been created as well, and will be further refined and expanded in detail.

Week 9 and 10(lab8 and lab9):Testing II and implementation

The team has refined our sequence diagram in detail, which will illustrate how the different functions relate to each other. Also we have further refined our collaboration diagram to demonstrate the full structure of our software. Testing has began as well. Our group has initiated static, unit level testing, integration lesting and black box testing, which intensively tests our software with many test cases so that our software will be able to meet the requirements specified by the clients.

Week 11(lab 10):Implementation and Integration

This week we continue our testing phrase with testing the software using white box testing. Final integration is completed, after which we test the entire system integration(integration test) for robustness and ensure that the system works under stress.