00155002_AungZayYa_Project_Final

MCC

1

Mobile Sale System

Aung Zay Ya (00155002)

MCC Yangon Campus

2

Abstract

My name is AungZayYa and I am a Level 5 Diploma in computing student at MCC Training Institute. As level 5

students, individual projects which involve creating a web-based systems are required to do. For the project, the title

is Online Smart Mobile Selling System. A website will be implemented to provide online mobile sell to customers.

The current system is a paper-based system and customers are required to come to the shop to buy item. At

the shop, they have to fill in information forms about personal details and delivery details. Staffs will check over the

information and respond to customer with collection date and other information. If the customers are pleased with

the time, confirmation and payment is made to the shop. All of above processes are taken manually.

The proposed system is a computerized system that allows customers to order services online. With an

automated system, only registered customers can log in to order services. After log in, customers can choose their

desired smart phone. Then, customer must have banking account because product cost cash the customer banking

account.

Therefore, the system will allow customers to get convenient services and staffs will be able to work more efficiently.

3

Table of ContentsAbstract...........................................................................................................................................................................2

Acknowledgement..........................................................................................................................................................5

Chapter 1 : Introduction..................................................................................................................................................6

The system to be developed.......................................................................................................................................6

Justification for the method or framework used.........................................................................................................7

The Solution That Emerged.........................................................................................................................................7

Aims and Objectives of the project.............................................................................................................................8

A short Overview of the remaining chapters...............................................................................................................8

Chapter 2: Analysis..........................................................................................................................................................9

2.1 introduction...........................................................................................................................................................9

2.2 Functional with MOSCOW prioritization and Non-Functional Requirements......................................................10

2.3 Complete Use Case Diagram...............................................................................................................................11

Over all Use Case Diagram.....................................................................................................................................11

Detail Use Case Diagrams......................................................................................................................................11

2.4 System Architecture............................................................................................................................................12

2.4.1 Interfaces with other system........................................................................................................................12

2.4.2 An Overview of the technical architectures..................................................................................................12

2.5 Initial Class Diagram............................................................................................................................................12

2.6 Conclusion...........................................................................................................................................................12

Chapter 3: Design..........................................................................................................................................................13

3.1 Introduction...................................................................................................................................................13

3.2 A detailed class diagram................................................................................................................................13

8.2 Sequence Diagram.........................................................................................................................................18

3.4 Input Form Design.........................................................................................................................................25

3.5 Report Form Design.......................................................................................................................................33

3.6 Conclusion.....................................................................................................................................................35

Chapter 4 – Implementation.........................................................................................................................................36

Introduction..............................................................................................................................................................36

Choice of Programming Language.............................................................................................................................36

System Cutover from Development Architecture to Implementation Architecture..................................................37

Data Migration from Development Architecture and Existing System to Implement...............................................37

Training Schedule......................................................................................................................................................38

Conclusion.................................................................................................................................................................38

4

Chapter 5 – Other Project Matters................................................................................................................................39

Introduction..............................................................................................................................................................39

Project Management.................................................................................................................................................39

Risk Management......................................................................................................................................................40

Configuration Management......................................................................................................................................42

Testing-Black Box Testing..........................................................................................................................................44

Unit Testing...........................................................................................................................................................44

Integration Testing................................................................................................................................................46

Chapter 6 – Conclusion.................................................................................................................................................49

Evaluation..................................................................................................................................................................49

References....................................................................................................................................................................50

Appendices....................................................................................................................................................................50

Requirements Catalogue...........................................................................................................................................50

Mobile Sale Registration........................................................................................................................................50

Use Case Descriptions...............................................................................................................................................51

Login Process Use Case Description......................................................................................................................51

Brand Registration Use Case Description..............................................................................................................52

Customer Registration Use Case Description........................................................................................................53

Customer Item Order Use Case Description..........................................................................................................54

Staff Report Use Case Description.........................................................................................................................55

Customer Item Search Use Case Description.........................................................................................................56

Staff Paid Use Case Description.............................................................................................................................57

Staff Product Registration Use Case Description...................................................................................................58

Staff Register Use Case Description.......................................................................................................................59

Detailed Class Definitions..........................................................................................................................................60

Test Scripts................................................................................................................................................................60

User Guide.................................................................................................................................................................60

System Code..............................................................................................................................................................60

5

Acknowledgement

I would like to express my special thanks of gratitude to my class tutor Daw Phyo Thwe Aye as well

as my lecturer U Moe Arkar Lwin who gave me the golden opportunity to do this assignment - Mobile Sale System,

which also helped me in doing a lot of Research and I came to know about so many new things I am really thankful to

them. Secondly, I would also like to thank my parents and friends who helped me a lot in finalizing this assignment

within the limited time frame.

6

Chapter 1 : Introduction

The system to be developed

The “Win Mobile World” mobile phone shop was opened in 2012 with a paper-based system. It is located in No(46,

48)A, Shan Kone Street, San Chaung Township, Yangon. There is no one branch.

With the paper based system, customers have to come to the shop to buy for product. Personal information

forms have to be filled by customers. Payment will be made after customer paid. As the shop became more famous,

a lot of new customers keep coming to buy for mobile. The staff can no longer take the amount of data they have to

deal with every day.

There are a lot of problems due to the expansion of the shop. Careless mistakes such as misspellings are

made more often by the staffs. Customers give wrong address and claim that they have not done it. Therefore, more

miscommunications occur between staffs and customers which put bad reputation on the shop. Items get lost due to

staff carelessness and customers’ mistakes. Paper can be damaged or lost easily and there may not be any more

copies of the data. Moreover, it takes more time for staffs to find data on the paper. Therefore, Customers start to

complain about their smart phone warranty.

In this report, the proposed system will be developed with helps of analyzing the business environments and

presenting the analysis with use case diagrams and class diagrams. The functional areas of the project will be

defined. The method or framework used to do the analysis. Other behavioral models will also help t implement the

technical flows of the functional scopes and implementation of the project will be discussed. Other project matters,

such as Project, Risk and Configuration management will be shown in the following chapters. Then the implemented

system will be tested using unit and integration testing techniques. Lastly, user’s manual guides will be created.

The new system needs to allow customers to order online without having to come to the shop personally. It

should store all customers’ information and let them log in to order a delivery service. New customers could register

to order. It needs to let customers keep track of their deliveries by looking at their orders statuses.

The proposed system should allow only the administrators to register new staff. It must only allow the

administrators to view reports of the system. Reports may show how the shop is doing during that particular period.

The administrators will also have their own accounts.

After the registration of staffs, they may be able to log in to the system and register new brand, product and

edit for paid customer for the system. They may also be able to delete existing information. They will be keep

customer buying item; therefore, other staffs and customers can know about their smart phone warranty.

7

Justification for the method or framework used

SSADM (Structured System Analysis and Design Methodology)

SSADM is a well-defined and structured methodology. It can also be used to produce accurate information

systems. Waterfall Method is used in SSADM and each step of the method needs to be complete before starting the

next step. All procedures in each step should be undertaken thoroughly because it may be impossible to return back

to the previous step. So, it usually takes longer to developers to finish a step because they will not be able to go back

to change the requirements. This methodology focuses more on the technical requirements of the system. SSADM

uses three techniques such as Logical Data Modeling, Data Flow Modeling and Entity/Event modeling to provide

different versions of the same system.

Justification for the method or framework

SSADM is very simple and easy to understand. Its components can be easily reused between systems. It is

more flexible, modifiable and easily maintainable. System can be developed faster with low on costs. In this project,

techniques of SSADM will be used such as use case diagrams, class diagrams and sequence diagrams.

The Solution That Emerged

To solve all above problems, web based system is used to provide better mobile sale services and order

taking processes. With the proposed system, customers can order for smart phone while they are at homes.

Customers will be asked to register and then they can log in and submit a delivery form to get a service. Payment will

be done banking account. The proposed system will provide conveniences to both customers and staffs. Firstly, staffs

will be able to find customers and their information quickly. They will be able to track the items. Therefore,

communication between staffs and customers will be improved.

Staff will also be able to register brand , product , and paid conveniently. Administrator will be able to

register staffs online, and will be able to view the reports of the system easily. Overall, deleting and processes will be

easier, without having to go through all required papers. Staff will be less stressful.

8

Aims and Objectives of the project

Aims

To open 24/7 hour mobile sale service and induce the staff count and decrease the mobile product show

space in shop and sell quickly.

Objectives

- To let customer register online without having to come to the shop.

- To pick various types of brand, products and services online

- To know today hot products.

- To see monthly new staff register.

- To see monthly top 10 products.

- To see monthly order amount.

- To see monthly new arrival product.

A short Overview of the remaining chapters

Chapter 2 report is about the system analysis. Chapter 2 report includes

functional and non-functional requirements of the system,

Use Case Diagram,

System Architecture and

Initial Class diagram.

Chapter 3 report is about the design of the system. Therefore it includes

a detailed class diagram,

sequence diagram,

input form design and

report form design.

Chapter 4 report is about the implementation of the system. Therefore, chapter 4 includes

choosing the programming language,

System implementation Architecture and

Data Migration Architecture to implementation and

training schedule.

Chapter 5 report is about the other project matters including

the project management,

9

risk management,

configuration management and

testing.

Chapter 6 report is about conclusion of the work that is done in developing this project.

The facts described above are the short overview of the remaining chapters.

Chapter 2: Analysis

2.1 introductionThis chapter includes

o Functional with MOSCOW prioritization and Non-Functional Requirements

o Complete Use Case Diagram

o System Architecture

o Initial Class Diagram and

10

o Conclusion.

2.2 Functional with MOSCOW prioritization and Non-Functional RequirementsMust Have Requirements-

1. Customer Registration

2. Customer Log In

3. Product Searching by Name

4. Product Detail View

5. Product Order

6. Brand Registration

7. Staff Registration

8. Staff Log In

9. Confirm Payment

10. Current Month New Customer Report

11. Current Month Top 10 Popular Item List

12. Current Month New Arrival Item List

13. Current Month Total Income

Should Have Requirements - none

Could Have Requirements - none

Would Have Requirements - none

11

2.3 Complete Use Case Diagram

Over all Use Case Diagram

Detail Use Case Diagrams

12

2.4 System Architecture

2.4.1 Interfaces with other systemMobile Sales & Services System is in no relation with the other system. It stands independently.

2.4.2 An Overview of the technical architecturesLanguage PHP

Tools Sublime Text 2.0

Platforms MS Window XP and above

Database MySQL client version: 5.1.41

Standard Web Browser Mozilla Firefox 26.0 and above and Chrome

2.5 Initial Class Diagram

2.6 ConclusionIn this chapter, I created the Use Case Diagrams, Initial Class Diagram and choose what development tools

and platforms will be used.

When creating the Use Case Diagram including considering of form design I met some difficulties. As the system is a little complex, Use Case Diagram have so many requirements. So, after business presentation, I have to modify the use cases again.

When choosing Web Browser, My Form Design does not work well in IE. Therefore I standardize the web browser to be Firefox or Chrome.

13

Chapter 3: Design

3.1 Introduction

This chapter will include detailed class diagram of the system which show the classes and their relationship within the system. Behavioral models will be also included to show the technical flow of the system. Later, input forms and output forms will be presented by referencing detail class diagrams and behavioral models.

-

3.2 A detailed class diagramDetails Customer & Staff Log In

4

14

Details Customer Registration

Details Item Order

5

15

Details Item Search

Details Paid

6

16

Details Staff Registration

Details Brand Registration

7

17

Details Product Registration

Details Item Report

8

18

8.2 Sequence Diagram

Customer Item Searching

Customer Log In

19

Customer Product Detail View

Customer Product Order

20

Customer Registration

Report Monthly New Arrival

21

Report Monthly Top 10 Popular

Report Monthly Total Order

22

Report New Customer

Staff Brand Registration

23

Staff Log In

Staff Paid

24

Staff product registration

Staff Registration

25

3.4 Input Form Design

User Index

User Search By Brand

26

User Search By Word

User Log In

27

User Sign Up

28

User Welcome Index

User Order

29

User Help

Admin Log In

30

Admin Signup

31

Admin Index

Admin Paid

32

Admin Brand Registration

Admin Product Registration

33

Admin Help

3.5 Report Form DesignAdmin Current Month New Customer Report

34

Admin Current Month Top 10 Popular Product

Admin Current Month New Arrival Product

35

Admin Current Total Order Amount

3.6 Conclusion

In this chapter, the web-based design of the system has been created and how each process will be achieved in what order is already assumed using sequence and robust diagrams. From this, technical coding of the processes can be written using PHP language.

36

Chapter 4 – Implementation

Introduction

In this chapter, a programming language will be chosen to write technical part of the system. This chapter

will explain about how system is implemented step by step, then how data are inserted or registered into the

implemented system and will explain in detail of how long it will take for staff to train to use the new web-based

system.

Choice of Programming Language

PHP

PHP (Hypertext Preprocessor) is an open source server side language that mostly used for developing web

applications and web services. It is a loosely typed language which does not need to define data types for variables.

PHP can be also used with MySQL, Oracle, MS SQL Server database software. Data in the database can be easily

manipulated by PHP.

Choose the language

PHP is very user friendly and it is easy to learn to use. It can be installed on various platforms such as Linux,

UNIX and Windows. It is available and free all the time. PHP can also be embedded into HTML to create dynamic

websites.

37

System Cutover from Development Architecture to Implementation Architecture

The final step of the system development is to migrate the development-testing-staging architecture to implementation-production environment. The main goals of migration are to achieve the system requirements and to complete the project within limited time and cost. To migrate systems, cutover strategies has to be used. Cutover to the new system have four basic strategies: Pilot, Immediate, Phased and Parallel Cutover.

Nevertheless, the technique of Parallel Cutover is used for Mobile Sale System. Win Mobile Sale and Services is currently running purchased process with the manual system, i.e. they are doing the purchase system with paper work. When computerised system is implemented with the test data, we have to deliver the firstly implement system to the organisation. Then all the transactions are designed and coded with real data from Win Mobile. When the system is completely developed, process of training users has to be carried out. The mangers and staffs are trained to carry out the required transactions. The customers from Win Mobile can view the website through the internet and make purchase. With the use of parallel cutover strategy, the new implemented system is run simultaneously with the old until the reliability and accuracy of the new system can be verified so that we can get very low risk and provides to reduce risk. When all the requirements are successfully met, the manual system is dropped and the new computerized is implemented. Therefore, new system can store more data and can explore both current data and previous old data at one place and cannot be easily destroyed by nature disasters.

Data Migration from Development Architecture and Existing System to Implement

The actual data are inserted into the system by using the form designs for the new system. The web-based

system is tested and ensured that there will be no errors before using it. Each record from manual paper is

transmitted to the database by entering data on each corresponding form design and data is validated first in order

to be inserted into the database. Staff will also be asked to register data during their training session to know how

the system works.

38

Training Schedule

Training level is divided into Admin or Staff.

Admin

Training Period Names of Processes to be trained

5 minutes Admin Logging in

5 minutes Updating Paid

5 minutes Brand Registration

15 minutes Staff Registration

20 minutes Product Registration

An hour Generating 4 report

Estimation of total period length = about 2 hours

ConclusionImplementation stage includes choice of language and data migration from development architecture. It is

okay for me to work out. There is no problem for me at this stage.

39

Chapter 5 – Other Project Matters

Introduction

This chapter will explain about other project matters such as project, risk, and configuration management.

Project management will show how long each process takes to implement the final system. In risk management, how

the system security is guaranteed will be explained. Configuration management will show what hardware and

software requirements are for the system. Then, testing of the system will be done using unit and integration testing

techniques.

Project Management

Gantt Charts

40

Risk Management

Risk can be reduced by some actions but they cannot be eliminated completely. So users should tolerate

risks but should minimize the impact of risks.

Computer based Threats

- Viruses, worms, Trojan horse

- Data Loss

- User Accounts hacking

- Database System being Hacked by intruders

- Software failure

- Hardware Failure

Non Computer based Threats

- Natural Disasters

- Intruders to organisations’ properties

- Back up Data Loss

Counter Measures41

To reduce the impact of data loss from viruses, software failure and hardware failure,

The organization should have licensed anti-virus programs installed on every computer within the

organization. The anti-virus should protect all type of viruses from internet, external drives, and

internal applications.

Every staff should have daily back up of their own data and the organization should also have daily

back-up of organization-wide data.

For security of user accounts and databases,

Password to log in the system is hashed; therefore, it is hard to intruders to know the password to

the system.

Staff and Administrator accounts are different depending on their position but they exist within the

same table. Therefore, it is hard for intruders to get the password of administrators.

Log in page is the same page for everyone; therefore, it would take a long time for intruders to hack

administrators’ passwords, since they will have to go through every data from both staff and

customer tables.

When data are passed in the program codes, they are filter using “htmlspecialchars ( )”, to avoid

SQL injections.

To reduce the impact of data loss from natural disasters, intruders and losing the back-up data,

Their back up data should be saved offsite.

Server room should be secured with a security and CCTV.

Entry to the organisation’s building must be highly secured using finger print scanning or ID card

verification systems.

Software Development Threats

- Miscommunication

- Inexperienced project team

- Inexperienced developers

- Business rules are not clearly defined

Counter Measures

The organization should make sure that developers or project team have previous

experience with this type of project.

Business needs should be clearly identified and developers should know them clearly and

questions can be asked by developers, if something is unclear.

Developers need to be in contact with the business on regular basic to verify some problems.

42

Configuration Management

Server Side Software Requirements

- Sublime Text Version 2.0

- MySQL (Version 5.6.12)

- Google Chrome Version 32 or above

- Internet Explorer Version 10 or above

- Firefox Mozilla Version 23 or above

- Wamp (Version 2.4)

Server Side Hardware Requirements

Hardware Minimum Requirement Maximum Requirements

Laptop or Desktop Windows 7 Windows 8

Processor Intel core i3 Intel core i5

Hard Disk Storage Space 300GB 450GB

Random Access Memory

(RAM)

3GB 7GB

Motherboard Main board Support

Screen Resolution 800x 600 1366 x 768

Graphic Card AGP 1GB AGP 2GB

Optical Drive CD-ROM Drive and DVD-ROM Driver

USB Drive 2.0 3.0

Keyboard Computer or Laptop keyboard types

Mouse Optical Mouse

Client Side Software Requirements

- Sublime Text Version 2.0

- MySQL (Version 5.6.12)

- Google ChromeVersion 32 or above

- Internet Explorer Version 10 or above

- Firefox Mozilla Version 23 or above

- Wamp (Version 2.4)

43

Client Side Hardware Requirements

Hardware Minimum Requirement Maximum Requirements

Processor Intel core i3 Intel core i5

Hard Disk Storage Space 300GB 450GB

Random Access Memory

(RAM)

2GB 3GB

Motherboard Main board Support

Screen Resolution 800x 600 1366 x 768

Graphic Card AGP 1GB AGP 2GB

Optical Drive CD-ROM Drive and DVD-ROM Driver

USB Drive 2.0 3.0

Keyboard Desktop computer or Laptop keyboard types

Mouse Optical Mouse

-

44

Testing-Black Box Testing

Unit Testing

Unit Test 1 Tests Class: Customer Designed By:Aung Zay Ya

Data Source: Customer Entry Objective: Test Basic Functionality Tester : Aung Zay Ya

Test Case Description TasksExpected

ResultActual Result

1.1 Test for Basic

Functionality

Entered customer details:

Customer Name :Kaung Khant

Email:[email protected]

Password:asdfjkl;

New customer

data is

inserted into

the database.

Figure 5.8

Figure 5.9

Figure 5.8

45

mailto:[email protected]

Figure 5.9

46

Integration Testing

Integration Test 1 Tests Classes: Customer and Staff Designed By:Aung Zay Ya

Data Source: Customer Entry Objective: Test Basic Functionality Tester : Aung Zay Ya

Test Case Description TasksExpected

ResultActual Result

1.1.1

1.1.2

Test for Basic

Functionality

Test for Basic

Functionality

Entered customer details:

Customer Name :Kaung Khant

Email:[email protected]

Password:asdfjkl;

Entered staff details:

Staff Name : Linn Ko

Email: [email protected]

Password:jkl;asdf

New customer

data is

inserted into

the database.

New staff

information is

added into the

database.

Figure 5.12

Figure 5.13

Figure 5.14

Figure 5.15

47

mailto:[email protected]

Figure 5.12

Figure 5.13

48

Figure 5.14

Figure 5.15

49

Chapter 6 – Conclusion

Evaluation

The new web-based system has eased the amount of work staffs have to do daily and the amounts of effort

customer have to give in order to purchase. The system also achieved the objectives of letting customer order for

services online by choosing desire brand types. Staffs are able to look for purchase details more easily and

administrators are able to generate their reports more quickly.

Some difficulties with this project are with the development architecture where clear decisions were made

in order to create this web based system. For example: drawing a use case diagram and deciding which actor would

be suitable to do which business processes. There were some problems with class diagram also because the

relationships between the classes and attributes were important in order to continue with this project. This project

has some problems with where to put the price for discount type.

If I could add or change the web-based system, I would add a Delivery Services so that customers don’t need

to come the shop. I would also like a system that directly choose the desire phone.

Overall, the project has achieved its aims and objectives but it could be improved in many other ways using

by adding delivery system. For now, the project will fulfill the needs of customers and it will reduce the amount of

paper work staffs have to do. It will increase productivity and improve performance of the service.

50

References

Beginning PHP and MySQL Form Novice to Professional Fourth Edition/ W. Jason Gilmore/ Copyright © 2010 by W. Jason Gilmore/ ISBN-13 (pbk): 978-1-4302-3114-1

Appendices

Requirements Catalogue

Brand Registration

Source: Brand Sign Off: Admin Requirement ID: 1

Functional Requirement: To Insert Brand Name

Non-Functional Requirement(s);

Description:

To Insert brand

information

Target Value:

Cannot duplicate brand

ID

Acceptable Rage:

-

Comment:

-

Product Registration

Source: Product Sign Off: Admin Requirement ID: 1

Functional Requirement: To Insert Product Information


Description:

To Insert product

information

Target Value:

Cannot duplicate

Product ID

Acceptable Rage:

-

Comment:

-

Staff Registration

Source: Staff Sign Off: Admin Requirement ID: 1

Functional Requirement: To Insert Staff Information


Description:

To Insert staff

information

Target Value:

Cannot duplicate staff

ID

Acceptable Rage:

-

Comment:

-

51

Staff Log In

Source: Staff Sign Off: Admin Requirement ID:

Functional Requirement: To Log In Staff


Description:

Staff Must be Register

Target Value:

-

Acceptable Rage:

-

Comment:

-

Customer Registration

Source: Customer Sign Off: Customer Requirement ID: 1

Functional Requirement: To Insert Customer information


Description:

To Customer information

Target Value:

To Insert customer

information

Acceptable Rage:

-

Comment:

-

Customer Product Searching

Source: Product Searching Sign Off: Customer Requirement ID:

Functional Requirement: To product searching


Description:

To Customer searching

the product

Target Value:

-

Acceptable Rage:

-

Comment:

-

Customer Product Detail View

Source: Product Detail View Sign Off: Customer Requirement ID:

Functional Requirement: To product detail view


Description:

To view customer

product detail view

Target Value:

-

Acceptable Rage:

-

Comment:

-

52

Customer Item Order

Source: Product Order Sign Off: Customer Requirement ID:

Functional Requirement: To order product


Description:

To Customer must be log

in

Target Value:

-

Acceptable Rage:

-

Comment:

-

Customer Log In

Source: Customer Sign Off: Admin Requirement ID:

Functional Requirement: To Customer Log In


Description:

Customer Must be

Register

Target Value:

-

Acceptable Rage:

-

Comment:

-

New Customer Report

Source: New Customer Report Sign Off: Admin Requirement ID: 1

Functional Requirement: To view new customer report


Description:

New Customer Report

Target Value:

-

Acceptable Rage:

-

Comment:

-

Current Month Top 10 Popular Item

Source: New Customer Report Sign Off: Admin Requirement ID: 1

Functional Requirement: To view Top 10 Popular Item report


Description:

To view Top 10 Popular

Item

Target Value:

-

Acceptable Rage:

-

Comment:

-

53

Current Month New Arrival Product List

Source: New Arrival Product Report Sign Off: Admin Requirement ID: 1

Functional Requirement: To view new arrival product


Description:

To view New Arrival

Product

Target Value:

-

Acceptable Rage:

-

Comment:

-

Current Month Total Income

Source: Current Month Total

Income

Sign Off: Admin Requirement ID: 1

Functional Requirement: To view current month total income


Description:

To view current month

total income

Target Value:

-

Acceptable Rage:

-

Comment:

-

54

Use Case Descriptions

Login Process Use Case Description

Use Case: Login

Actor : Staff, Customer

Precondition: The users need to register first

Flow of events

Home Page > Log In Button

Primary Scenario or Normal Condition

1. Staff or Customer entering login Page by clicking the log in Button at home page.

2. Staff or Customer enters username and password.

3. Staff or Customer click the log in Button.

4. System check for valid user.

5. If staff is valid, display the item entry page and use case end.

6. If customer is valid, display the search page and use case end.

Post Condition: Each users or staff get the access of using the system

Alternative paths

In step 3: if empty email and password, display error message.

In step 4: If invalid user, display error message.

Any step: Cancel button click go to home page.

55

Brand Registration Use Case DescriptionUse Case: Brand Registration

Actor : Staff

Precondition: The staff need to register first

Flow of events

Home Page > Entry > Brand


1. Staff entering Brand Page by clicking the Brand Button at staff home page.

2. Staff enter Brand Name.

3. Staff click the Add Button.

4. System check for valid brand.

Post Condition: If user is staff: The current page is brand page

Alternative paths

In step 3: if empty brand, display error message.

56

Customer Registration Use Case DescriptionUse Case: Customer Registration

Actor : Customer

Precondition:

Flow of events

Home Page > Log In > Sign Up


1. Customer enter Sign Up Page by clicking the Sign Up Button atCustomer Log In page.

2. Customer enter Name.

3. Customer enter Password.

4. Customer enter Email.

Post Condition: If user is Customer: The current page is User Welcome Page.

Alternative paths

In step 2: if empty Name, display error message.

In step 3: if empty Password, display error message.

In step 4: if empty Email, display error message.

57

Customer Item Order Use Case DescriptionUse Case: Customer Item Order

Actor : Customer

Precondition:

Flow of events

Welcome Page > Product Detail


1. Customer enter Prodcut Detail Page by clicking the product higlight text or image at welcome page.

2. Customer Click the order.

Post Condition: If user is Customer: The current page is Product Detail Page.

Alternative paths

In step 2: if cusomer has not already log in, display error message.

58

Staff Report Use Case DescriptionUse Case: Staff Report

Actor : Staff

Precondition: Staff must be log in

Flow of events

Welcome Page > Report


1. Customer enter Report Page by clicking the report dropdown menu at welcome page.

2. Customer Click the report.

Post Condition: If user is Staff: The current page is welcome Page.

Alternative paths

59

Customer Item Search Use Case DescriptionUse Case: Customer Item Search

Actor : Customer

Precondition:

Flow of events

Welcome Page > Search Page


1. Customer enter welcome page.

2. Customer type the text in "search" text box at the top andd then Click the search button.

Post Condition: If user is Customer: The current page is Search Page.

Alternative paths

60

Staff Paid Use Case DescriptionUse Case: Staff Paid

Actor : Staff


Flow of events

Welcome Page > Paid


1. Staff enter Paid Page by clicking the Paid at welcome page.

2. Customer Click the paid check box.

3. Customer Click add button.

Post Condition: If user is Staff: The current page is Paid Page.

Alternative paths

61

Staff Product Registration Use Case DescriptionUse Case: Staff Product Registration

Actor : Staff


Flow of events

Welcome Page > Product Register


1. Staff enter Product Page by clicking the Product at welcome page.

2. Staff choose brand.

3. Staff enter product name.

4. Staff enter description

5. Staff enter price.

Post Condition: If user is Staff: The current page is Product Page.

Alternative paths:

In step 2: if staff don't choose anyone, display error message.

In step 3: if empty product name, display error message.

In step 4: if empty description , display error message.

In step 5: if empty price , display error message.

62

Staff Register Use Case DescriptionUse Case: Staff Register

Actor : Staff

Precondition:

Flow of events

Log In > Sign Up


1. Staff enter Sign Up Page by clicking the Sign Up Button at Staff Log In page.

2. Staff enter Name.

3. Staff enter Password.

4. Staff enter Email.

Post Condition: If user is Staff: The current page is User Welcome Page.

Alternative paths:

In step 2: if empty Name, display error message.

In step 3: if empty Password, display error message.

In step 4: if empty Email, display error message.

63

Detailed Class Definitions

64

Test Scripts

Paid

65

Brand

66

Product

67

User Guide

Home Page Guide

You will be taken to Home Page after log in.

1. By Clicking “Help” button on every Page.

Figure 7.19

System Code

<?php

include("php/dbopen.php");

session_start();

$_SESSION['CustomerName'] = "Unknown";

$cookname = "login"; //$user_arr['Name']

$thetext = $cookname;

setcookie("texttokeep",$thetext,time() + 10000);

/*$_SESSION["favcolor"]

session_unset();*/

?>

68

<html lang="en">

<head>

<?php

include("php/headerimport.php")

?>

<title>Smart Mobile Myanmar Homepage</title>







</head>

<body>



<?php

if ($_COOKIE["texttokeep"] == 'login') {

include("php/indexmenu.php");

}else{

include("php/welcomemenu.php");

}

?>



<div class="container">

69

<div class="row">

<?php

include("php/list.php");

?>

<div class="col-md-9">

<div class="row carousel-holder">



<div class="row">

<?php

echo "<h1>***TODAYS HOT***</h1>";

//$sqlQue = "SELECT * FROM `product` WHERE 1";

$result = mysqli_query($con,"SELECT `PID`,`BrandName`,`ProductName`,`Price`,`ImageID` FROM `product` GROUP BY `BrandName` Order By `Price` Desc");

$myTable = "<table><tr>";

$c = 0;

while($row = mysqli_fetch_array($result))

{

$myTable .= "<td width='30%' align='center'><a href='product.php?id=". $row['PID'] ."'><img src=images/" . $row['ImageID'] ."></img><br>". $row['ProductName'] ."</a><span> (". $row['Price'] ."Kyats)<br><br></span></td>";

$c = $c + 1;

if($c==3){

$myTable .= "</tr><tr>";

}

}

$myTable .= "</tr></table>";

echo $myTable;

?>

</div>

</div>

71

</div>

</div>



<?php

include("php/footer.php");

?>

<script src="js/jquery-1.11.0.js"></script>

<script src="js/bootstrap.min.js"></script>

</body>

</html>

72

Date post:	13-Apr-2017
Category:	Documents
Upload:	aung-zay-ya
View:	28 times
Download:	0 times

00155002_AungZayYa_Project_Final

Documents