8/03/2009 07:25:00 PM

DFD- Data Flow Diagram-Level 0 & Level 1

Posted by In Tech Corp.


-by Rasool-

comments (2)
TOP

7/30/2009 10:00:00 PM

Entity Relationship Diagram (ERD)

Posted by In Tech Corp.


Entity Relationship Diagram above show available entities, attributes and relationships of our online shopping system. The database is the most important entity in the ERD diagram, it link all the relations between entities. It can be access and control by administrator. Other entities can log in and access some information from database only.

-by Wong Chii Lok and Ng Hin Mung-

comments (0)
TOP

7/20/2009 08:39:00 PM

Use Case Diagram (Week5)

Posted by In Tech Corp.


Here is the description for the Use Case Diagram:

Administrator

  • Can manage login-Can update new products from suppliers
  • Can manage users database include viewing user profile
  • Can view products-Make payments to deliverers and suppliers
  • Can view and reply feedbacks accordingly

Supplier
  • Introduce new products to administrator
  • View products of administrator
  • Receive payments from administrator after supplied productsBanker
  • Manage payments make by in between administrator, suppliers, users and deliverers

User
  • Can login own profile
  • Can view products-Have add to cart feature
  • Make payments to administrator
  • Can make return unexpected products to administrator through deliverer
  • Can view and give comments or feedbacks

Deliverer
  • Receive payments from administrator after success deliver products to users or vice versa
  • Deliver products to users or administrator

Not user
  • Can view products
  • Can view feedbacks and comments only

-by Mohammad Rasool Sarrafi Aghdam-

comments (0)
TOP

7/11/2009 02:01:00 AM

Lifecycle Model used in our Project

Posted by In Tech Corp.


Here is the lifecycle model diagram we use in this project. The main model is RAD
(Rapid Application Development) model sub with prototype and incremental model.

Our team has chosen Rapid Application Development (RAD) as main software life cycle for our project. The main reason we choose this model is because of it can reduce the complexity of the project effectively and even faster (short cycle) compare with other method. Rapid Application Development (RAD) can provide a fully functional system in a short period of time. This model helps a lot with dividing our team into several teams for particular task. Besides, it only requires human resource and commitment which are fulfill our team condition. Lastly it needs no high technical risk.

Rather than using Rapid Application Development model to be our main bone for whole project, prototype model is also applied as sub-model in this RAD. At first, client and us determine project objectives and draft requirements as beginning. Prototype then quickly being built and get evaluation from client so that client is always participate and make better requirements are visible.

We also adding incremental model to be our sub-software life cycle model. This model separate whole team into few teams to make our product gets ensured with quality and efficient. Product is being developed by follow all the stage in incremental procedure. It is more focus on delivery of the operational product with each increment. So that, our product can be evaluated and given feedback all the times before reach to the final deployment stage. It make easy to manage technical risk so that product is qualitatively developed.

-fairly done by all members of In-Tech.Corp-

comments (0)
TOP

7/08/2009 02:06:00 AM

AOA Diagram of the project

Posted by In Tech Corp.

AOA diagramActivity dependency table
-by Tan Kah Wah-

comments (2)
TOP

7/08/2009 01:45:00 AM

Team Member and Posting

Posted by In Tech Corp.

-by Ng Hin Mung-

comments (0)
TOP

7/06/2009 02:28:00 AM

Gantt Chart of the project

Posted by In Tech Corp.



Activities
A. Recruit group member - 1day
B. Set up a blog and update the blog weekly - 4days
C. Research on coding tools - 7days
D. Prepare a proposal - 7days
E. Design a project planning diagram and a Gantt Chart - 7days
F. Coding the application -14days
G. Sent the coding to lecturer to get feedback - 1day
H. Re-contracture the coding - 14days
I. Sent the coding again to get feedback from lecturer - 1day
J. Test and finalize on our developed application and document -7days
K. Write a final technical report to describe the features of software system -7days
L. Present our application to lecturer -7days
M. Submission of project final technical report -7days

-by Wong Chii Lok-

comments (2)
TOP

Subscribe to: Posts (Atom)