Im2042 - Is Modeling & Design

8/10/2019 Im2042 - Is Modeling & Design

1/52

1

ASSIGNMENT

IM 2042 INFORMATION SYSTEMMODELING & DESIGN

GROUP PORTFOLIO

IC NUMBER : 90041214-5139

MATRIC C. NUMBER : USE4-12/10-00106

LECTURER NAME : MR. MASHAL

& MR. MURUGANATHAN

DATE : 07/11/2012


2/52


3/52

3

INTRODUCTION

Online buying and selling allows customers to communicate with the organization

directly without cost of transportation and also reduce stress of the customers, by sitting relax in

their own house or office, transecting business online. According to (Oxford Advanced Learners

Dictionary), the meaning of Marketplace is an activity of competing other companies to buy and

sell goods and services etc .and the same (Oxford Advanced Learne rs Dictionary), define

online, as a connected to computer or internet.

In todays business world, the web is considered by many companies as the most

important channel for marketing. This has prompted these companies to start seeking to have an

online marketing system that can help them optimize websites so as to improve the experience of

the visitors and also increase conversions. These online marketing systems are meant to deliver

website analysis that will enable the better understanding of visitors behavior that will help to

make advancements and improvements that will culminate to more successful interactions with

the customers. In as much as the marketers are looking for iterative and responsive and analytics

solutions, most of the online marketing systems have some technical/user interaction difficulties

which includes difficulty to change, difficult to change analytic capability that are labor-

intensive that require marketers to know upfront what questions they want answered.

This brought about the need for Omar Ali to improve on is sells strategy been the most

famous trader in Malaysia. The system will not only increase its sales, but it will also increase

the customer network. A good look and consideration on the idea will be of great benefit to the

company if the company ventures into having an online marketplace. This paper explains further

on what the system will look like and the needed facilities.


4/52

4

PROBLEM STATEMENT

This market places system about to be created would help in buying and selling of products

conveniently by individuals in their respective regions. The following are the problems that weretaken into consideration that brought about the idea of the creation of this system:

Limited time of sales: this system would enlarge the time of sale, this system would be an

automated on line system thereby the buyers would not need to interact with any sales

personnel for purchase.

Slow trading: this system would help put slow trading out of order in the sense that when

an individual purchases a product he/she would provide an address for which the item or product would be delivered to.

Difficulties in finding exact product: this system would put difficulty in finding an exact

item out of place; the system would have an advanced search portal for the users to

search for exact products i.e. a shoe with an exact size and color.

High cost of running businesses: thus system would help the project sponsor cut down on

the work force running his organization whenever this system is implemented, this

system would automate at least 70% of the manual labor thereby reducing their

workforce which means a reduction in operation cost.


5/52

5

OBJECTIVES

On creating a marketing system the following questions what would be the benefits of creating

the system? and what must we provide to our customers? have been asked. These questionshave brought about a rise in the project objectives which are listed below:

This system would break the barriers of difference in time and location sales, due to the

fact that the system would be online therefore on accessing the system at any point in

time through the use of the internet, purchases can be made.

One of the major objectives of this system is eliminate processing errors; therefore the

processing and data arrangement and management would be carried out by the system

itself therefore reducing the possibilities of processing errors.

Another important of objective of the system would making it a very cheap means of

doing business therefore the delivery of a product in the same region would be made free

else outside the companies geographical region.


6/52

6

Project Sponsor Omar Ali

Business Need This project was initiated to connect buyers and sellers To carry out businesses without the barriers of time or distance

To increase the sales of our users. To eliminate processing errors. To help create a cheap means of doing business. To help create a fast and more convenient means of doing

business. To help with access to the world market.

BusinessRequirements

On using the online marketplace system there are three (3) main usersnamely; Registered users, Unregistered user and the Administrator, the

Administrator user has unlimited access to the system while an

registered user has some limitations and also the unregistered user the

following below are a few functions of the user of the online

marketing system can perform: -

The following are function that can be carried out by an Administrator The administrator can accept or reject any posted product of

item The administrator can delete a user The administrator can create another admin account

The following are function that can be carried out by a Registered user The registered users can login into the system.

The registered users can logout of the system. The registered users can purchase items. The registered users can upload items for sale. The registered users can add to cart. The registered users can perform advanced search function.


7/52


8/52

8

and it prevents users information from harm. Effectiveness: The system will be done in such a way that the

downtime will not be frequent and people will be able to

perform task at any time of the day. Privacy: The privacy in order not to allow corresponding

match from logs on the website. Reliability: This system shall be operational at all time all year

round. This will give the users opportunity to access the system

any given time. Backup: The system will be able to recover lost information

from back-up within an hour if any form of failure occurs.

Capacity: The system is capable of supporting multiple userssimultaneously without experiencing a downtime.

Operational: The website will be available all day round

Hardware, software and Network requirements are as follows: -

Computer system: the computer system must have access to

any internet service provider so as to access the system fromany given location.

Network requirements: the network requirements could be any

of the following WAN, LAN MAN because this system should

have the ability of access from any place in the world. Browsers such as IE5+, Mozilla Firefox, Google chrome, and

other browsers that support JavaScript and flash animations.


9/52

9

FEASIBLITY ANALYSIS

TECHNICAL FEASIBLITY

In order to properly carry out a technical feasibility there are some four (4) major questions that

need to be answered, the following below are the questions that must be answered in order to

carry out technical feasibility:

The familiarity with application used to design the system. Project size. Familiarity with the technology used to design the system. Compatibility with the current system.

The risk with the familiarity with application used to design the system is relatively low as a

result of the following reasons:

The system analyst and his team designing the system have signed a letter an agreement

that they are familiar with the application demanded by the project sponsor to be used to

design, in example are CSS (Cascading Style sheet), HTML (Hyper Text Markup

Language), PHP (Hypertext Preprocessor) and MYSQL.

The system risk with the project size is relatively low as a result of the following reasons:

The project team consists of 12 personnels due to the size of the project. The Project time frame and deadline set by the project sponsor Omar Ali is somewhat

flexible thereby reducing the risk, due to the fact that the system is large and would

require a lot of time to meet all of its requirements.

The system risk with the familiarity with the technology used to design the system is relatively

low as a result of the following reasons:


10/52

10

The users of the new marketplace system would be both computer literates and illiterates

or novices as the case maybe there by as a result of the tool tips which would be put in

place this would help the users understand the system effectively.

The system risk with the compatibility with the current system is very low as a result of the

following reasons:

The system in question which is marketplace system would be compatible such that the

current system would be designed to carry on from where the existing system has left off.

ECONOMIC FEASIBLITY

A cost benefit analysis estimate was performed you could see the spreadsheet below for details

conservative estimates for the cost benefit analysis for the online marketplace system. This

system would bring about a significant change and boost the sales of the company.

Intangible costs and benefits, improved customer satisfaction, increased sales estimates and

enhanced system (in example 24/7 sales and purchasing, regional trade made easy) were all

taken into consideration when drawing out the estimates you have below.

TABLE SHOWING THE BENEFITS OF CREATING THE SYSTEM


11/52

11

TABLE SHOWING THE DEVELOPMENT COSTS OF THE SYSTEM

TABLE SHOWING THE OPERATIONAL COST OF THE SYSTEM

Total costs [for first four (4) years]

Total Benefits Total Costs (Net Present Value (NPV))

$99,110.7 $92,400 = $6,710.7= NPV

Return on Investment (ROI) = Total benefits Total costs/total costs

= 2,250/69,700

= 0.03228120

Therefore ROI = 3.26% after 3 years.


12/52

12

The break-even point will be reached within 3 years.

ORGANISATIONAL FEASIBLITY

From the organization point of view this project has a moderately low risk; the project champion

Omar Ali has a strong interest in the project and therefore making it a top priority project.

The users of the system i.e. registered and unregistered users are expected to utterly be of

approval of the online marketplace system. Hence, it solves the problem of going to the actually

sales area to purchase the item but with the creation of this system our esteemed clients would be

able purchase directly from their homes and can have the items delivered to their location of

choice depending on the companies shipping policies, making purchases and sales easy for ourclients thereby making our system utterly important. To avoid a situation whereby the system

would not meet the required standard of the stakeholder i.e. the system users the project team

met with the stakeholders in form of a question and answer session to get down all the

requirements required by them i.e. stake holders.

The companys staff would be trained to operate the system and potentially to provide

customer care services to their esteemed clients. The company should consider hiring a consultant with experience in similar application

to assist with the project and also to assist with training of their personnels on how to use

the system.

SCHEDULE FEASIBILITY

Schedule feasibility involves questions such as how much time is available to build the newsystem, when it can be built.

The system development process is scheduled to take a period of two hundred and twenty-three

working days provided all resources needed are provided by the organization. Also, two weeks

will be required for testing in order to check for errors while the end users are making use of the

system. A total of three software developers, two designers and quality assurance personnel will


13/52

13

be working to bring the sales system into actualization. If the project is not delivered within the

specified time, we will bare twenty percent of the total cost of production.

TIME ESTIMATE FOR PROPOSED SYSTEM

Gantt chart

The main purpose and Gantt chart usage is to be damaged one numbers of large into a

sum smaller duties in one way very organized. In this system chart show period it will be taking

per task level would be finished.

No. Task Name Start Finish Duration

Oct 2012 Nov 2012

19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13

1 1d10/19/201210/19/2012Feasibility Study for Proposed System

2 1w10/26/201210/22/2012Study Requirements and Possible UML

3 2d10/30/201210/29/2012Identify Aim and Objectives

4 1d10/30/201210/30/2012Sketch GUI

5 3d11/2/201210/31/2012Methodology Study

6 2d11/6/201211/5/2012Produce System Proposal

7 1d11/7/201211/7/2012Design UML Diagrams

8 2d11/9/201211/8/2012Design Actual UML

9 1w11/16/201211/12/2012Implementing and Editing


14/52

14

ANALYSIS OF AS-IS-SYSTEM The present system is a manual system which has little or no security purchasing

information can be accessed by unapproved personnel. The system we are about to create would be a web based system the current web system

is a manual system, on using the requirement analysis techniques BPA (Business

process automation) we the design team would build the companys application using

the web extension HTTP (Hypertext Transfer Protocol) PHP (Hypertext Preprocessor)

and MYSQL.

In the current system only the registered users have access to use the system. On the current system the users cannot directly upload materials for sales without going

through the company.


15/52

15

USECASE DIAGRAM OF AS-IS-SYSTEM

View FAQEnquiry

View ProfileMake an offer

Post Product

View User Agreement

Purchase an item

Delete Post

Remove User

Add Staff

Search Items

Administrator

Sign In

Unregistered User

Sign out

Registered User

As-is-System


16/52

16

IMPROVEMENTS

In order to adequately collect the right functions for the system we analyzed a similar

system i.e. Alibaba.com and also Ebay.com to come out with proper functions for the system and

to understand and get the advantages their system provides in order to apply them in the to-be-system, observation and document analysis of other systems were also taking into consideration.

Applying business process improvement we as a team of analyst will analysis the present

system and also conduct interviews with selected tourists who have used the current system. We

will also conduct brief interviews with the manager of the tourism company in order to have a

better understanding of the system.

Following the joint application technique, our team of analysts will study other

organizations systems and also act as customers in order to know the weakness of the

organization and also study their business process. The interviews will enable us to identify

problem areas of the current system so that we recommend improvements using informal

benchmarking.

The system would become a web based application, i.e. users around the world be able to

access the system and purchase items of their choice. The system would be easy to use with the help of tool tip for each and every function

available on the system. The new system would improve the security of the system with the use of an enhanced

web extension known as HTTPS which is Hypertext Transfer Protocol over Secure

Socket Layer which can be used to secure the information the website into the database. To increase the patrons via the easy access by the use of web services, which was not

available in the previous system due to the fact that it was not a web based application.


17/52

17

PROPOSED TO BE SYSTEM

The system which we the design team proposed to implement due to the shortcomings of the

previous system has been analyzed using a vast number of requirement gathering techniquessuch as JAD session which would be carried out with the project sponsor Omar Ali and a system

analyst of the company, also informal benchmarking and activity elimination were also used to

enhance the systems functions, the following functions will be implemented search, sign in,

register, advanced search, bids/offers, watch list, sell an item, whats hot, sell for charity.

The system will partners with commercial enterprises who wish to advertise and want

visible link of their business in our system.

The following are some non-functional requirements that the system would provide for the users

of this system: - Security: Provision of strong firewall to prevent hackers from gaining access into the

system. Effectiveness: Downtime will be avoided to avoid error in transaction. Privacy: Users details will be protected and be given utmost protection.

Reliability: Users are sure of a system with 100% activeness. Performance: The system will be running on a dedicated server making it perform well

and faster. Operational: All functions will work constantly without problem.


18/52

18

USECASE DIAGRAM OF THE PROPOSED TO BE SYSTEM

View FAQEnquiry

View Profile

Edit Profile

Make an offer

Post Product

Add Cart About Us

View User Agreement

Purchase an item

View Products

Save Searches

Delete Post

Remove User

Reject Product

Accept Product

Add Staff

Search Items

Administrator

Sign In

Unregistered User

Make Registeration

Sign out

Registered User

Report an item

Proposed to be System


19/52

19

USECASE DESCRIPTION, SEQUENCE DIAGRAMS AND COLLABORATION

DIAGRAMS

Amalina Asma Bt. Azmi (U 1060788)

1.1 Use case name: Sign in

2.1 Brief Description: This use case would enable the registered user to Sign in into the system.

3.1 Precondition: The user must have an account i.e. the user must have registered beforehand.

4.1 Primary actor: Registered User and Administrator

5.1 Flow of events:5.1.1 Basic Flow:

This use case begins when the user click on the Sign in button on the main

page. The system would display a sign in page.

The user would key in his/her username and password.

The user would click on the sign in button [Alternative1: Cancel].

The system would verify the given information [Exceptional1: Invalid User

name], [Exceptional2: Invalid Password].

The system would display the home page.

5.2.1 Alternative flow Alternative1: cancel: Th e system shall send a message Cancelled on user demand.

5.3.1 Exceptional flow Exceptional 1: Invalid Email ID: when the User name is wrong, the system would

display a message for the user that the Invalid Email ID/ User name.

Exceptional 2: Invalid password: when the password is wrong, the system would displaya message for the user that the T he password entered is invalid.

6.1 Post condition: The user can login into the system.

7.1 Constraints:

The username given must be valid.

Registered User Sign in


20/52

20

The password given must be valid.

Sequence Diagram for Sign-in

Collaboration Diagram for Sign-in

: RegisteredUser : Re gisteredUser : Homepage: Home page : SigningForm: Si gningForm : SigninControl: Si gninControl : UserAccountTable: UserAccountTable

Click on sign in button

Display()

Key in (Usern ame,password)

Click on sign in button

Send information()

Verify Information

Retrive

Return

Display

E1: invalidUsername

E2: invalidpassword

: RegisteredUser

: HomePage

: SigninControl

: SigninForm

: UserAccountTable 1: Click on sign in button()

2: Display()

3: Key in Username and pass word()4: Click on sign in button()

5: Send i nformation()

6: Verify information

7: Retrive

8: Return

9: Display


21/52

21

1.1 Use case name: Make Registration Amalina Asma Bt. Azmi (U 1060788)

1.1 Brief Description : This use case would enable the unregistered user to register to become a

registered user of the system.

2.1 Precondition: The user must have an email address to register.

3.1 Primary actor: Unregistered User

4.1 Flow of events:

4.1.1 Basic Flow: This use case begins when t he user click on the Register hyperlink.

The system would display the registration form on the screen. The user would key in First name, last name, address[street number, city, postal

code, and country] telephone number, email address, retype email address,

create password, retype password, pick security question, answer and date of

birth, after which the user must key in the verification code.

The user would tick the I agree check box to agree to the terms and conditionsof the company.

The user would click on the Continue button[Alternative1: Cancel]

The system would verify the entered information [Exceptional 1: Invalid Email]

Exceptional 2: Invalid ID, Exceptional 3: Invalid Password].

The system would display a welcome message on the home page.

4.2.1 Alternative flow Alternative1: Cancel: Th e system shall send a message The registration cancelled on

user demand.

4.3.1 Exceptional flow Exceptional 1: Invalid Email ID: when the email id is not valid, the system would

display a message for the user that the Email ID is invalid.

Unregistered User Make registration


22/52

22

Exceptional 3: Invalid password: when the password is invalid, the system would

display a message for the user that the The password is invalid.

5.1 Post condition: The user will become a registered user.

6.1 Constraints:

The email address must be valid.

The password must be more than 8 characters uppercase and lowercase.

Sequence Diagram for Registration

Collaboration Diagram for Registration

: UnregisterUser : HomePage : RegistrationForm : RegistrationControl : UserAccountTable

Click on "Register" hyperlink()

Display()

key in First name, last name, stree t address, city . . . .

tick t he "I agree" check box ()

click on t he "continue" button()

A1: Cancel

Send information()Verify information()

E1:Email ID E2: invalidID

E3: invalidpassword

Save information()

Return

Display "Confirm registration from Email ID"

: RegistrationForm

: UnregisterUser : HomePage

: RegistrationControl

: UserAccountTable

1: Click on "Register" hyperlink()

2: Display()

3: key in First name, last name, street address, city . . . .4: tick the "I agree" check box ()5: click on the "continue" button()

6: S end information()

7: Verify information()8: Save information()

9: Return

10: Display "Confirm registration from Email ID"


23/52


24/52

24

Sequence Diagram for Edit profile

Collaboration Diagram for Edit Profile

: RegisteredUser: RegisteredUser : ProfilePage: Profi lePage : EditProfileForm: EditProfileForm : EditProfileControl: EditProfileControl : UserAccountTable: UserAccountTable

Click on "Edit profile" button

Display

Select the field to edit

Click on the "save" button

Send information

Verify information

Save i nformation

Return

Displ ay confirmation message

E1: Invali dcharacters

A1: Cancel

: RegisteredUser

: ProfilePage

: EditProfileForm

: EditProfileControl : UserAccountTable

1: Click on Edit profile button 2: Display

3: Edit the desired field()4: Click on the save button

5: Send information


7: Save information

8: Return

9: Edit Is Successful


25/52

25

Kuralovian S/O Ganesan (U1153153)

1.1 Use case name: Saved Searches

2.1 Brief Description: This use case will enable/allow registered users to save searches.

3.1 Precondition: The user must search for an item.

4.1 Primary actor: Registered user

5.1 Flow of events:

5.1.1 Basic Flow: This use case begins when the user clicks on save search hyperlink on searched

result page

The system would display the search detail boundary. The user would click on save button [A1: cancel]

The system would display confirmation me ssage on searched result page Y our

search has been saved

5.2.1 Alternative flow Alternative1: cancel: The system shall send a message Process was canceled on

user demand.

5.2.2 Exceptional flow Not available

6.1 Post condition: The user would be able to save searches made by him or her

7.1 Constraints: The user must have an account

Registered User Save searches


26/52

26

Sequence Diagram for Saved Searches

Collaboration Diagram for Saved Searches

: RegisteredUser: RegisteredUser : SearchedResultPage: SearchedRes ul tPa ge : SaveSearchForm: SaveSearchForm : SearchControl: SearchControl : SavedItems: SavedItems

Clicks on s ave searchhyperli nk

Display

Key in name of search and description

Click on save button

Send information

Verify information

Save information

Return

Displa y confirmation messa ge

A1: Cancel

E1: Invalidcharacters

: RegisteredUser : SearchedResultPage : SaveSearchControl

: SaveSearchTable : SearchDetail

1: clic ks on save search hyperlink

2: Display()

3: Save() 4: Send information()

5: Save()6: Return()

7: Display "Search saved" mess age()


27/52

27

1.1 Use case name: Make an offer ( Kuralovian S/O Ganesan - U1153153)

2.1 Brief Description: This use case is initiated by the customer especially buyers; this use case

would enable a registered user to make an offer on a product of his or her choice.

3.1 Precondition: The user would select an item.

4.1 Primary actor: Registered User

5.1 Flow of events:

5.1.1 Basic Flow: The user would select an item of choice.

The system would display the purchase item page. The user would click on the Make an offer button.

The system would display an offer form The user would enter the amount he/she want to offer for the item displayed

The user would click on submit button[Alternative1: Cancel]

The system would verify the amount given [E1: invalid amount].

The syst em would display a dialog box A re you sure you want to make an offerfor this item

The user would click on the submit button [Alternative2: Cancel].

The system would display a confirmation message an offer has been made.

5.2.1 Alternative flow Alternative 1: cancel: Th e system shall send a message The offer was canceled on user

demand. Alternative 2: cancel: Th e system shall send a message T he offer was canceled on user

demand.

5.3.1 Exceptional flow E1: invalid amount: when the amount is wrong, the system would display a

message Invalid amount.

6.1 Post condition: The user would make an offer on item.

Make an offer Registered User


28/52

28

7.1 Constraints: The amount must be above the lowest amount stipulated.

Sequence Diagram for Make an offer

Collaboration Diagram for Make an offer

: RegisteredUser: RegisteredUser : PurchaseItemPage: PurchaseItemPage : OfferForm: OfferForm : AddControl: AddControl : OfferTable: OfferTable

Clic k on the "make an offer" button

Display

Key in amount of choice

Click on "submit" button

Send information

Verify information

Display dial ogue box

Clic k on the"submit" button

Send information

Save information

Return

Display confirmation message

A1: Cancel

A2: Cancel

E1:Invalidamount

: OfferControl

: RegisteredUser : PurchaseItemPage

: OfferForm

: OfferTable

1: click on the "make an offer" button

2: Display

3: Key in amount of choice4: Click on Submit button

5: Send information


7: Display Dialog box

8: click on the submit button

9: send information

10: Save information

11: Return

12: Display confirmation message


29/52

29

1.1 Use case name: Post an advertisement (Kuralovian S/O Ganesan - U1153153)

2.1 Brief Description: This use case would enable a registered user to post an advertisement

(product).

3.1 Precondition: The user must be logged in as a registered user.

4.1 Primary actor: Registered user

5.1 Flow of events:

5.1.1 Basic Flow: The registered user would click on post an advertisement (product) on his home

page. The system would display the advertisement page.

The registered user would key in his/her advertisement of choice.

The registered user would click on the submit button [Alternative2: Cancel]. The system would send the information to the control

The system would verify the information keyed in [E1: invalid data] The system would save the information in the database

The system would display a confirmation message Your advertisement has been

posted .

5.2.1 Alternative flow Alternative 1: Cancel: The system shall send a message T he advertisement posting was

canceled on u ser demand.

5.3.1 Exceptional flow E1: Invalid data: when the data is wrong the system would display wrong

data.

6.1 Post condition: The registered user would post an advertisement.

7.1 Constraints: Advertisement can only be posted by the registered user.

Registered User PostAnAdvertisement


30/52

30

Sequence Diagram for post an advertisement

Collaboration Diagram for Post an advertisement

: Administrator : Administrator : HomePage: HomePa ge : AdvertisementPage: AdvertisementPa ge : AdvertisementControl: AdvertisementControl : AdvertisementTable: AdvertisementTable

1: Click on the Advertisement hyperlink

2: Display

A1:Cancel

E1: InvalidData

5: Send information


7: Save information

8: Return

9: Display confirmation message

3: Key-in the information

4: Click on Submit button

: Administrator

: HomePage

: AdvertisementPage

: AdvertisementTable : AdvertisementControl


1: Click on the Advertisement hyperlink

3: Key-in the information4: Click on Submit button

2: Display

5: Send information

7: Save information

8: Return

9: Display confir mation message


31/52


32/52


33/52


34/52

34

Sequence Diagram for Add to cart

Collaboration Diagram for Add to cart

: RegisteredUser

: RegisteredUser

: CurrentPage: CurrentPa ge : AddtoCartControl: AddtoCartControl

: ProductTable: ProductTable

1: Click Add to Cart link

2: Send Information

3: Verify Information

4: Send InformationE1: Pleaseselect...

5: Return

6: Display product details

7: Click Confirm

A1: Cancel 8: Send Information


10: Send Information

11: Return

12: Display number of product in "Add To Cart"

: Registered User : CurrentPage

: AddtoCartControl: ProductTable

1: Click Add to Cart link

2: Send Information

3: Verify I nformation

4: Send Information

5: Return

6: Display product details

7: Click Confirm

8: Send Information


10: Send Information

11: Return

12: Display number of product in "Add To Cart"


35/52


36/52

36

Sequence Diagram for Search Items

Collaboration Diagram for Search Items

: RegisteredUser

: Re gisteredUser

: HomePage: HomePa ge : SearchControntrol: SearchControntrol : ProductTable: ProductTable

1: Key-in first letter in search box

2: Send Info

3: Display list of products

4: Select Product and click "Search"

A1: Cancel5: Send Info

6: Verify availability

7: Send Info

8: Return

9: Display poduct details

E1: Productis ...

: Registered User : HomePage

: SearchControntrol : ProductTable

1: Key-in first letter in search box

2: Send Info

3: Display list of products

4: Select Product and click "Search"

5: Send Info

6: Verify availability

7: Send Info

8: Return

9: Display poduct details


37/52

37

Dinesh Kumar S/O Radakarisnen (U1060792)

1.1 Use case name: Add Staff

2.1 Brief Description: This use case would enable the Admin to add a staff if necessary.

3.1 Precondition: The user must be logged in as an Admin.

4.1 Primary actor: Admin

5.1 Flow of events:

5.1.1 Basic Flow: This use case begins when the admin click on the Add Staff on the main home

page. The system will be displayed of Add Staff form.

The admin are able to key in the information of new staff. The admin click on Add button. [A1: Cancel]

The system will verify the information. [E1: Invalid information.]

The system will pop up a message New Staff successfully added for 5 seconds onthe main homepage.

5.2.1 Alternative flow Alternative 1: Cancel: The admin will be able to cancel the add new user information

that have been entered as well as the system will be able to clear the form.

5.3.1 Exceptional flow E1: Invalid data: when the data is wrong the system would display wrong

data.

6.6 Post condition: The administrator must be approved the submitted registration to continue

add new staff. Means that the admin should receive the registration form and approved it to

have the new staff information to be key-in the system.

7.1 Constraints: This function only can be viewed by the admin.

Adminstrator AddStaff


38/52

38

Sequence Diagram of Add Staff

Collaboration Diagram for Add Staff

: Administrator : Administrator : AddstaffForm: A ddstaffForm : AddStaffControl: AddStaffControl: HomePage: HomePa ge : StaffTable: StaffTable

1: Click "Add Staff" link

2: Display

3: Key-in new st aff info

4: Click "Add" button

A1: Cancel 5: Send Info

6: Verify Info

E1: InvalidInfo

7: Send info and save

8: Return

9: Display message "New Staff successfully added"

: AddStaffControl

: HomePage

: StaffTable

: Administrator

: AddstaffForm

1: Click "Add Staff" link

2: Display

3: Key-in new st aff info

4: Click "Add" button

5: Send Info

6: Verify Info

7: Send info and save

8: Return

9: Display mess age "New Staff successfully added"


39/52


40/52

40

Sequence Diagram For Approve Product

Collaboration Diagram for Approve Products

: ProductTable: ProductTable: Administrator : Administrator : HomePage: HomePa ge : ApproveProductControl

: ApproveProductControl

: ApproveProductForm: ApproveProductForm

1: Click "Approve Product" link

2: Display

3: Check the info of the product

4: Click "Approve" button

A1: Cancel

5: Send info

6: Verify info

7: Send and save the product's details

8: Return

9: Dsplay "Product succes sfully added"

E1: InvalidInfo

: Administrator

: HomePage

: ApproveProductForm

: ApproveProductControl

: ProductTable

1: Click " Approve Product" link

2: Display

3: Check the info of the product4: Click "Approve" button

5: Send info

6: Verify info

7: Send and save the product's details

8: Return

9: Dsplay "Product succ essfully added"


41/52

41

1.1 Use case name: Remove User Dinesh Kumar S/O Radakarisnen (U1060792)

2.1 Brief Description: This use case is initiated by the Administrator; this use case would enable

an Administrator to remove user .

3.1 Precondition: The user must be logged in as an Administrator.

4.1 Primary actor: Administrator

5.1 Flow of events:

5.1.1 Basic Flow: The administrator would click on view user page(all user) The system would display the user page

The administrator would click select the user that he/she want to delete. The administrator would click on the Delete button.

The system would display a dialog box.

The Administrator would click on the OK button [Alternative1: Cancel].

The system would display a confirmation message User has been deleted.

5.2.1 Alternative flow Alternative1: cancel: Th e system shall send a message T he deletion was canceled on

Use r demand.

5.3.1 Exceptional flow

E1: Please Choose a user: This is very important, because admin must select a user to

do the removing process

6.1 Post condition: The Administrator would add new staff.

7.1 Constraints: Removing User can only be done by the Administrator.

Adminstrator RemoveUser


42/52

42

Sequence Diagram for Remove User

Collaboration Diagram for Remove User

: Administrator : Administrator : HomePage: HomePa ge : RemoveUserPage: RemoveUserPa ge : RemoveUserControl: RemoveUserControl : UserAccountTable: UserAccountTable

1: Click on "Remove User" link

2: Display

3: Select User to be removed

4: Click on "Delete"

A1: Cancel

5: Send info

6: Verify info

E1: Pleasechoos...

7: Delete User

8: Return

9: Display "User has been deleted" message

: Administrator

: HomePage

: RemoveUserPage

: RemoveUserControl

: UserAccountTable

1: Click o n "Remove User" link

2: Display

3: Select User to be removed4: Click on "Delete"

5: Send info

6: Verify info

7: Delete User

8: Return9: Display "User has been deleted" message


43/52

43

ACTIVITY DIAGRAMS

This diagram contains of four activity diagrams for the main important use case.

1. Add to cart ( Amalina Asma Bt. Azmi U1060788)

Login

SearchItems

View Items

Add to cart

Items added to cart successfully

Note: Unregisteredcustomer can onlypurchase not morethan 3 items.

Activity Cancelled

Adding to cart failed

Register

Guest exceeding 3 items

Items will be added to cart and customer will automatically advance to payment page

CancelItem unavailable

Add to cart

Invalid Login


44/52

44

Make Registration ( Dinesh Kumar S/O Radakarisnen U1060792)

Click register

fill detials

Click "Continue"button

Send link toEmail address

Display registerform

Verifyinformation

[invalid information]

Saveinformation

[valid info]

Save information i ndatabase

Display successfulmessage

SystemUser


45/52

45

Purchasing (Kuralovian S/O Ganesan U1153153)

Click onbuy button

Key indetails

Click on "purchase"button

Key in bankingdetails

Display successfulmessage

Display purchaseitem form

Banking detailsdialogue box

Save purchaseddetails

Send

Confirm bankingdetails

BankOnline Market place systemRegistered User


46/52

46

STATE CHART DIAGRAM (Freddy Aberd Nicholson USE4-05/09-00093)

displaysRegistration Form

Click on Registerhyperlinnk

Registration formmust be filled

Registration Form notfilled

Select user Agreement andPolicy on the Registration form

User Fill'sRegistration Form

Clicks onContinue Button

Retrieve and ConfirmInformation the Data Base

System must Add user tothe system Data Base

system confirms details inthe Data Base

Login Form mustbe filled

system displayLogin Form

CLick onLogin button

User will key inuser name andpassword

Show WelcomeMessage


47/52


48/52


49/52

49

MOST SUITABLE PROGRAMMING LANGUAGES USED FOR INTERFACE DESIGN

FOR THIS SYSTEM

The 3 most suitable programming languages that can be used for the interface design for this

system can be are listed below: -


50/52

50


51/52

51

COMPARISON BETWEEN THE DIFFRERENT PROGRAMMMING LANGUAGES

THAT CAN BE USED FOR INTERFACE DESIGN

As stated above in the explanations, advantages and disadvantages they are all unique in their

own different ways the table below further differentiates them in the unique form


52/52

REFERENCES

Documents

Im2042 - Is Modeling & Design