Music GaraGe

Thursday, September 3, 2009
UML state and sequence diagram


UML State Diagram





UML Sequence Diagram
posted by musicgarage @ 9:04 AM   0 comments

Wednesday, August 12, 2009
UML Activity Diagram
posted by musicgarage @ 8:06 AM   0 comments

Monday, August 3, 2009
Entity Relationship Diagram (ERD)

posted by musicgarage @ 10:14 AM   1 comments

Level 1(Data Flow Diagram)
posted by musicgarage @ 10:13 AM   0 comments

Level 0 (Data Flow Diagram)
posted by musicgarage @ 9:27 AM   0 comments

Monday, July 20, 2009
UML design


As required for this week's assignment, we as a group have come up with UML to show about how our website is suppouse to be and how does the user, administrator and programmer interacts with it.

posted by musicgarage @ 9:19 AM   0 comments

Monday, July 13, 2009
Software Life Cycle
Rapid Application Development (RAD)


Entering week 4, our group decide to upload our software life cycle so that the others might get a clearer picture about our task and the way were going to develop our software. To do so we as a group gathered at one of our group mates home over the weekend to decide and design our software life cycle.

After discussing, we have decided that the best approach towards our software design was to implement the usage of the Rapid Application Development (RAD), which was a “High-speed” version of waterfall model (short cycles). The reason why we decided that this approach was the best was mainly related to our work structure which consists of separate teams doing separate tasks over a short period of time. By implementing the Rapid Application Development (RAD), our work structure becomes easier and organized.

Since our team is separated into a designing, research and programming team, the Rapid Application Development (RAD) allows us to complete the functions, then
integrated as a whole in order to come up with our final product, which is an online shopping website. The other reason was that this design requires high commitment from each member, which is clearly visible through each members effort through the weeks and also that this website design is not high technically risky, which again is another point why we choose this design.

In the case of comparing to other design, we feel that the waterfall model does not suit us since delay usually incur when a earlier process is not completed. The increment model on the other hand focuses on delivery of operational product with each increment and evaluation in every increment. The prototype model also implements constant evaluation and alot of compromising which is rejected by our group of professionals. Finally the spiral model is also rejected since our team's performance cannot be determined during the entire structure.

In conclusion, the Rapid Application Development (RAD) is the best suited approach for our team since it blends into our project perfectly after comparing with the other modules.
posted by musicgarage @ 1:53 AM   0 comments

© 2006 Music GaraGe | Blogger Templates by Gecko & Fly.
No part of the content or the blog may be reproduced without permission.
Learn how to Make Money Online at GeckoandFly
First Aid and Health Information at Medical Health

 
 

Web This Blog
About Me


Name: musicgarage
Home:
About Me:
See my complete profile

Previous Post
Archives
Links
Affiliates

make money online blogger templates