Deriving the sequence diagram
The software is simple flow chart diagram
This diagram serves to demonstrate our main concept how the system should work. Based on this and the analysis we have done, the sequence diagram was implemented.
Originally we had two sequence diagrams for the user (vehicle) and the administrator respectively as these two points are our main concern. However in the end we divided the diagrams further to each input either from the user or the administrator.
The diagrams put in perspective the collaboration between various classes in details according to sequence of the steps in a particular process. The diagrams are specific enough in terms of how the interaction is carried out by the message and the values returned.
From the sequence diagram, we devised the collaboration diagram where we put the interactions between the classes/objects in architectural view of the classes involved. This includes the syntax of the messages.
The final step was deriving the class diagram by putting together the various collaboration diagrams appropriately. In the end the class diagram was very specific since we know all the functions to be implemented, the architecture of the classes even the data that needs to be declared.
However, this process was done iteratively as we continuously found things to be improved or improvised in an effort to make the system as robust as possible. Since our project is quite complicated due to the client's requirements, the design process went slowly as there are quite a number of classes to be implemented.
Home | Project | Progress | Report | About Us
CopyRight @ 2003 FreshMaker Ltd. All rights reserved