Tuesday, September 1, 2009

Updated Grantt Chart 2/9/2009

0 comments

Because some time schedule changes for this assignment..so we make some changes to our grantt chart..

 

Please click here and download it...

 

Prepared by Yeoh Tze Wei (Team Leader)

Posted By Goh Seng Yiung (Documentation Manager)

Wednesday, August 12, 2009

UML Diagram

0 comments

UML Sequence Diagram For Track Order

TOS1

UML State Diagram For Track Order

TOS

 

UML Sequence Diagram For Search Order

SOS1

UML State Diagram For Search Order

SOS

 

 

Prepared By Yeoh Tze Wei (Team Leader),Soh Wee Long(Programming Leader 1)

Revised By Bryan Chia Wen-Jun (Programming Leader 2)

Posted By Phang Xiao Shen(Design Manager)

Mindmap Lecture 7

0 comments

Mindmap Chap7

 

 

Prepared By Yeoh Tze Wei (Team Leader)

Posted By Goh Seng Yiung (Documentation Manager)

Activity Diagram Updated Correct Version

0 comments

Updated 2/9/2009

Correction of our previous diagram as follows :

AD

 

Prepared By Bryan Chia Wen-Jun(Programming Leader 2)

Posted By Yeoh Tze Wei (Team Leader)

Thursday, July 30, 2009

Revise Version Data Flow Diagram(DFD)

0 comments

Updated 2/9/2009

Data Flow Diagram Level 0

DFD0

Data Flow Diagram Level 1

DFD1

 

Note : To be a seller first must register as a customer then only send an email to the admin to request to be seller. From there, after get the positive notification from admin then your status will be direct change to seller then seller will share the same access right as admin to website.

 

Prepared By Yeoh Tze Wei (Team Leader),Soh Wee Long(Programming Leader 1)

Revised By Bryan Chia Wen-Jun (Programming Leader 2)

Posted By Phang Xiao Shen(Design Manager)

Entity Relationship Diagram(ERD)

3 comments

Updated 2/9/2009

The purpose of draw this diagram to show the relationship among the objects and personal attributes that belong to them.

Diagram 1

ERD1

Description

1)Seller/Administrator is provided with a control panel page at the eEasy Online Shopping Store with series of functions.

2)The Control Panel contains edit file functions and website application functions.(Assumption : In order to have Edit File & Website Application functions, we must have a control panel first.[Mandatory]There may be a situation in which the functions is not necessary to implement.[Optional])

Diagram 2

ERD2

1)Customer can places many order(one to one relationship) as they wish when in eEasy Online Shopping Store and viceversa.(Assumption:In order to have a list of order,we  must have at least one customer.[Mandatory]There may be situation in which placement order action is not necessary from the customer.[Optional])

2)Order can contains many order items details in the list and viceversa is part of the order.(Assumption:In order to have a order items details, we  must have at least one order taken from the customer.[Mandatory]There may be situation in which order items details is not necessary direct from the order list.[Optional])

3)Visitors can view many categories as they wish in eEasy Online Shopping Store.(many to many relationship)

4)Each category will contains many product.(one to many relationship)

5)The product will have the order items details.

 

 

Prepared By Yeoh Tze Wei(Team Leader)

Checked By Soh Wee Long(Programming Leader 2)

Documentation By Goh Seng Yiung(Documentation Manager)

Posted By Phang Xiao Shen(Design Manager)

Activity Diagram Wrong Version

1 comments

Please Ignore It..Thanks

The purpose of draw this diagram to show the workflows of stepwise activities and actions, with support for choice, iteration and concurrency for our eEasy Online Shopping Store.

AD

 For Clear Version, Please Click Download Here.

Basically, we will flow this diagram to help in designing our eEasy Online Shopping Website in order to meet our desired requirement.

 

 

Prepared By Bryan Chia Wen-Jun(Programming Leader 2)

Idea By Yeoh Tze Wei(Team Leader)

Checked By Soh Wee Long(Programming Leader 2)

Documentation By Goh Seng Yiung(Documentation Manager)

Posted By Phang Xiao Shen(Design Manager)

Saturday, July 18, 2009

Data Flow Diagram Level 0 & 1

0 comments

Updated Version at above..Ignore this one..Thanks

The purpose we prepare this is to provide a graphical information of the flow of data through eEasy Online Shopping Store Website System.

Level 0 - Description

At first, the Web Administrator will monitor the website activities and take care management of the website. Meanwhile, the user can assess the website for buying, selling or to get product information.

DFD0

 Level 1 – Description

DFD1

The Web Administrator will monitor the website’s activities and the management of the website. The web administrator will have the full access into the website. Once the user add item to sell list in website, administrator will receive the items details to take into consideration. Only after administrator approve, the item will only be allowed to go into sell list of the eEasy Online Shopping Store Website. So, our website is act as a medium between the seller and customer(buyer). Beside that, our website will serve to provide the details of all product listed there, if a user intend to buy, he/she has to contact the seller and make payment through the website

Meanwhile, the user can access the website for buying, selling or to get product information. As only a registered user can buy or sell items in eEasy Online Shopping Online Store Website, he/she must agree to the terms and conditions of the system. Once register, he/she will receive a verification mail to his/her email, which have a link to our website. By clicking on the link then will direct verify the user’s registration and then he/she will become a official member in eEasy Online Shopping Store.

A seller can advertise the item he/she willing to sell with the personal detail. If the item advertise is not approve by administer, he will receive a message from administer regarding it. The user still can review the detail about the item he/she willing to sell which is still wait for administrator consideration.

To the user who wants to buy an item, he/she can access to contact detail of the seller. He/she can contact the seller regarding the item.

 

 

Prepared By Yeoh Tze Wei (Team Leader),Soh Wee Long(Programming Leader 1)

Checked By Bryan Chia Wen-Jun (Programming Leader 2)

Posted By Phang Xiao Shen(Design Manager)

Week 5 Work Progress Upload UML Diagram

0 comments

UML Use Case Diagram

Our purpose create use case diagram is to present a graphical overview of the functionality provided by our eEasy Shopping Store Website Application System.

UseCaseDiagramForeEasyShoppingStoreApplication

Figure Above Show Use Case Diagram For eEasy Shopping Store Application

Use Case Diagram Description

For Website Users (Seller, Customer, Vistors) Accessible

Use case title : Register Personal Information

Input : Full Name, Gender, Date of Birth, Address, Contact Information

Output : Store Full name, Gender, Date of birth, Contact Information

Description : Sent a verification email to the seller email address.

Users required to register before using the system. This system is to storing the information into the database so that the users can access and retrieve data from the system. From that, the system by verifying the email address the users key into it.

For Users and Web Administrator Accessible

Use case title : Sign in/Check in

Input : Username(email address) and User Password

For admin : Admin username and password

Output : Login as user either seller or customers(buyer) or administrator

Use case title : Sign out/Check out

Input : A click button on log out icon

Output : Users had been log out from the system message box prompt out

For Seller and Customer(buyer) Accessible

Use case title : Select product categories

Input : User selected product categories

Output : Information of that product categories that users had selected for it (price, quantity available and etc)

For Seller Accessible

Use case title : Review product details

Input : Review on selected product items for update details such as items picture,price and available quantity in order to make some changes to the advertisement product items on the website

Output : Display the new updated information on the product that had been reviewed by the seller

Use case title : Sell Product

Input : Add the product that wish to sell into the list at the website

Output : The sell list will display the new updated sell product items list

For Customer(Buyer) Users Accessible

Use case title : Search/Check product information

Input : Select or key in the product that wish to find or check its information

Output : Display out the product seller name, contact number, price, quantity available and etc. Beside that, customer or buyer also can view the term & conditions, payment and shipping method and procedure information at there

Description: The buyer can contact the seller through messaging the seller regarding the availability of the item, and the seller reply the availability item.

Use case title : Purchase product

Input : Select the what product wish to purchase and also the quantity and payment method

Output : Confirmation message will display at the final process in the shopping cart steps

For Administrator Accessible

Use case title : Manage website users application

Input : Selected the web application or activity that used by users to be approve or reject it

Output : Selected web application or activity will be process based on the command choosen by the administrator

Use case title : Monitor webpage activities

Input : Monitor webpage activities

Output : Generate report of overall activities of all users in the website

Use case title : Manage website users membership appliaction status

Input : Review the membership appliaction status either approve or reject it

Output : Display total number registered members or rejected members

 

Prepared By Yeoh Tze Wei (Team Leader),Soh Wee Long(Programming Leader 1)

Checked By Bryan Chia Wen-Jun (Programming Leader 2)

Posted By Goh Seng Yiung(Documentation Manager)

Saturday, July 11, 2009

Software Life Cycle Model

0 comments

Software Life Cycle Model Diagram

Details :

The software lifecycle chosen for our team to carry out the project is a combination of the Rapid Application Development (RAD) and waterfall model. With the combination model we used, we can develop our project faster and systematic.

As each of our programming leader and other group member has a computer and complete pre-existing components condition, we have divide ourselves into two teams with each programming leader lead a group. The separate teams will complete the functions by part, and then integrated them as a whole system. The functions of the website can be easily link together so there should not much problems for the integration part. Since the requirements are clearly well-understood, RAD model can help to come out with a fully functional shopping application in a short time.

In addition, with the combination of the waterfall model, we can improve our planning and management stage. Moreover the online shopping applications are well-defined and repeated projects since there are a lot of online shopping website such as e-bay exists in the internet world. In the waterfall model, the activities ‘flow’ from one phase to another in a systematic and sequential form. After the system testing, if there are corrections, it will return to a previous phase and ‘flow’ from there again. The systematic project monitoring and control can make our software development more effective and efficiency.

 

Prepared By Soh Wee Long (Programming Leader 1)

Checked By Yeoh Tze Wei (Team Leader)

Posted By Phang Xiao Shen (Design Manager)

Friday, July 10, 2009

Week 4 Work Progress Updated 2/9/2009

2 comments

Activity On Diagram Revise Version

Please click here to download (updated 2/9/2008)

Grantt Chart Previous Version

Please click here for download

 

Prepared By

Yeoh Tze Wei (Team Leader),

Soh Wee Long (Programming Leader 1),

Bryan Chia Wen Jun (Programming Leader 2)

 

Posted By Goh Seng Yiung (Documentation Manager)

Friday, July 3, 2009

Project Management-Grantt Chart

0 comments

 

Tasks Start Date Duration (days) End Date
Proposal and preparation 06/18/2009 10 6/28/2009
Project planning, design and estimation 06/29/2009 20 7/19/2009
Web development 06/22/2009 83 9/13/2009
Testing, debugging and wrap up 08/24/2009 20 9/13/2009
Documentation 08/31/2009 13 9/13/2009
Presentation 09/14/2009 4 9/18/2009

Grantt Chart

Prepared By Soh Wee Long (Programming Leader 1)

Checked By Yeoh Tze Wei (Team Leader)

Posted By Goh Seng Yiung (Documentation Leader)

Activity On Arrow Diagram(AOA)

1 comments

Activity Precedence Table

Activity

Immediate Predecessor

Duration(weeks)

A

2

B

3

C

A,B

11

D

C

3

E

D

2

F

E

1

AOA new

Key Details :

A = Proposal and preparation

B = Project planning, design and estimation

C = Web development

D = Testing, Debugging and wrap up project

E = Project Documentation

F = Presentation

 

Prepared By Yeoh Tze Wei (Team Leader)

Checked By Goh Seng Yiung (Documentation Manager)

Posted By Phang Xiao Shen (Design Manager)

Sunday, June 28, 2009

Gantt Chart of the project

1 comments

Phase 1 : Proposal and preparation week

Phase 2 : Planning, requirement and design

Phase 3 : Development

Phase 4 : Testing and Debugging

Phase 5 : Documentation

Phase 6 : Group Presentation

GranttChart

Prepared by Team Leader Yeoh Tze Wei

Posted by Documentation Manager Goh Seng Yiung

Saturday, June 27, 2009

Meeting Minutes 1

0 comments

First Meeting Minutes

Date: 26-6-2009 (Friday)
Time: 7pm-8.30pm
Venue: Library Foyer
Attendance: all team members

Agenda Meeting

1) Update each person tasks in our team up to this point

2) Discuss and planning for project milestones from week 3 onward

3) Discuss and sharing idea about coding,testing and debugging for our online shopping webpage

4) Discuss the requirement to prepare the design diagram for project development

Prepared By Goh Seng Yiung (Documentation Manager)

Checked By Yeoh Tze Wei (Team Manager)

Thursday, June 25, 2009

Website Store Drop Down Structure

0 comments

Updated 2/9/2009

DropPic

Prepared by:
Soh Wee Long - Programming Leader 1
Bryan Chia Wen-Jun - Programming Leader 2

Page Progression Diagram Draft Sketch

0 comments

 

Prepared by:
Soh Wee Long - Programming Leader 1
Bryan Chia Wen-Jun - Programming Leader 2

Tuesday, June 23, 2009

Project Procedures

0 comments

Project Workflow Diagram:

Before our team can deploy out a usable, attractive and user friendly online shopping webpage and then we will follow several steps as provided in below :

Analysis – define what is the project scope, objective and what the problems may arise during the development of our project such as programming language for our webpage, resources and etc. All this we will look into it in very details.

Design – Creation our prototype model before deployment into a workable online shopping webpage. By this ways, it is a good move to enhance our group member relationships through communication by giving each person of our group members to raise their feedback or idea at every stage of design stage of this project.

Development – Analysis on the final workable model of our project before provide our customer a fully utilize and workable solution.

Testing – Lastly we will provide final checking on our project such as testing and debugging the coding for our project and also come out the documentation as a guidelines to our customer

 Please click here to download

Brief Introduction Website :
We will design the whole our online shopping website to be user-friendly and easily navigable, never making the customer feel confused or unsure as to what he should be his next step. Beside that, we will make our online shopping website acts as a salesperson at the counter that guides our customer right up to the checkout counter and payment gateway.


Main features :
The interface will be very simple and very obvious to our customer as they entering our site by displaying our products on the first page itself. They should never have any doubts whether they have come to the wrong place and leave our site immediately. Instead, they should be made to feel that they are entering a right website that looks like it would provide what they are searching for.
 
Benefits of eEasy Shopping Store Website
  1. Bargaining power of consumers. They enjoy a wider choice
  2. Supplier power. It is more difficult for consumers to manage a non-digital channel.
  3. Threat of new entrants. Online means it is easier to introduce new services with lower over-heads
  4. Rivalry among competitors. It is easier to introduce products and services to different markets

 

Prepared by:
Yeoh Tze Wei -Team Leader
Goh Seng Yiung - Document Manager

eEasy Shopping Online Store

1 comments

Project Objectives :

To be able to construct a workable design and development of an innovative online shopping web application such as provide e-transaction and etc.


Project Scope :

Coordination of web development tasks at weekly basis by all our group member to ensure that the project will have certain quality standard and procedures.
 
Our website theme will mostly will look alike or ideal to www.luvclothez.com.
 
Luvclothes


Project Outcomes :

We should acquire project management skills during this entire project such as communication skills, organizational skills, team building skills, leadership skills and technological skills.


Prepared by:
Yeoh Tze Wei -Team Leader
Goh Seng Yiung - Document Manager

Hot EZ shoppers!!

0 comments
Team Organization :


Shopping Prince

1. Yeoh Tze Wei
1061102959
twyeoh5079@yahoo.com

2. Goh Seng Yiung
1061105603
sengyiung@hotmail.com

3. Soh Wee Long
1061103166
justlo@hotmail.com

4. Bryan Chia Wen-Jun
1061103267
bryanchiawj@hotmail.com

Shopping Princess

1. Phang Xiao Shen
1061106880
shen_ph88@hotmail.com





 

web prepared by

Phang Xiao Shen
Design Manager

Contact

ezzshop2009@gmail.com

eEasy Shopping Store Copyright 2008 Shoppaholic Designed by Ipiet Templates Image by Tadpole's Notez Distributed by Blogger Blog Templates