Prototype E Commerce Website PDF

CT046-3-2 System Development Method
1.0 PROJECT PLANNING 2
2.0 SYSTEM ANALYSIS 11
2.1 REQUIREMENT ANALYSIS 11

2.2 REQUIREMENT SPECIFICATION 14
2.2.1 FUNCTIONAL REQUIREMENTS 14
2.2.2 NON-FUNCTIONAL REQUIREMENTS 17
3.0 INITIAL DESIGN 23
3.1 CONCEPTUAL DESIGN 23
3.1.1 USE CASE DESCRIPTIONS (AKASHDEEP SINGH TP034684) 24
3.1.2 USE CASE DESCRIPTIONS (CHAI JIA JIUN) 25
3.1.3 USE CASE DESCRIPTIONS (CHUAH SIEW YIING) 26
3.1.4 USE CASE DESCRIPTIONS (JASMINE TOH SHEAU-MINT) 27
3.2 OBJECT DIAGRAM 28
3.3 BEHAVIOUR DIAGRAM 29
3.3.1 BEHAVIOUR DIAGRAM (AKASHDEEP SINGH TP034684) 29
3.3.2 BEHAVIOUR DIAGRAM (CHAI JIA JIUN TP037875) 30
3.3.3 BEHAVIOUR DIAGRAM (CHUAH SIEW YIING) 31
3.3.4 BEHAVIOUR DIAGRAM (JASMINE TOH SHEAU-MINT TP034709) 32
4.0 PHYSICAL DESIGN 33
4.1 PROTOTYPE 33
5.1 CONSTRUCTION 42
5.2 TESTING 44
5.3 SYSTEM DEPLOYMENT 46
PART B - INDIVIDUAL COMPONENT (30%) 6.0 SELECTION OF METHODOLOGY 47
6.1 COMPARE AND CONTRAST (AKASHDEEP SINGH TP 034684) 47
6.2 COMPARE AND CONTRAST (CHAI JIA JIUN TP037875) 56
6.3 COMPARE AND CONTRAST (CHUAH SIEW YIING) 60
6.4 COMPARE AND CONTRAST (JASMINE TOH SHEAU-MINT) ERROR! BOOKMARK NOT DEFINED.
7.0 REFERENCES 68
1
PART A - GROUP COMPONENT (70%)
1.0 Project Planning
1.1 Introduction
MyCloths was established in the year of 2014. It is now known as a top leading
Malaysian retail clothing store, distributing a variety of Malaysian traditional cloths in the recent
years. It also has its own store in KLCC, in the capital city of Malaysia. Even knowing that they
are a top leading company, MyCloths continues to strive their best in a persistent and consistent
manner, such as providing good services to their customers that will deem to bring good
blessings towards the company’s reputation. Good services are such as attending company’s
phone calls, validating customer’s email purchases, delivery of customer’s goods to their
doorstep.
As the company grows in the view of the growing number of customers, MyCloths is
interested in having a better management of the orders, inventory and relationship between the
customers by establish an online store by October 2016. The vision of MyCloths is to be a
market leader in the use of technology to provide the best possible customer service with the
broadest range of Malaysian traditional cloths. Therefore, with the belief of web-based
management as a great platform to expand MyCloths business internationally and to drive the
sales and experience to a whole new level of growth. The efficiency would be done by just
clicking a button within the internet connection and the online store provides 24/7 services with
the updated information and it was available at any time.
2
1.2 Problem Statement and proposed solution
As the business grows, MyCloths would like to have a better management of their orders,
inventory and relationship with the customers. The current system used by MyCloths is offline
based system. There are many problem which are faced or will be faced if they do not upgrade to
an online system.
Problem Statement
● Management System
The Current way the business deals is offline where customer make purchases by only walk in
and by calling the shop. This way is not effective and also time consuming especially to handle
all customers at a time.
● Progress Tracking
The Shop currently deploys a conventional face-to-face / offline system. Every core
process such as payment, orders, progress tracking must be operated offline via face-to-face or
telecommunication. It is not convenient for customer to track their goods and also it is hard to
make sure all your customer know about your new product or promotion. [Orders inventory and
relationship with customer]
● Extra Cost
Staff would be required to work overtime to take care of shop’s busy processes
aforementioned. This would normally happens when it is at peak period, and when the company
starts operating business during public holidays. A lot of unnecessary overhead are needed in
order to keep this business in good condition. For example, staff will be required to be efficient
when handling customer’s orders or emails. As no one likes to wait, customers would be ensure
to be happy and would also be loyal to MyCloths company due to quick response of customer’s
requests.
3
● Data Storage
The paper based data storage is not only hard to handle but it is also not easy to make any
changes. Not only that, it will be hard to search because it takes time to find any information if
needed. Paper based also consumes a lot of space to be managed properly compare to online
system. On the other hand, all the information is not safe if any natural disaster occurs as there is
no backup available .
Proposed Solution
The solution our team has to this issue is a Online shopping system. An online shopping
system that permits a customer to submit online orders for item sand/or services from a store that
serves both walk-in customers and online customers. The online shopping system presents an
online display of an order cutoff time and an associated delivery window for items selected by
the customer. The customer can just sign up and then log in to start shopping as long they have
internet connection. All payment is made online where customer can be anywhere around the
globe to place an order.
4
1.3 Resource Planning and Scheduling
What are the ‘resources’ in a typical IT Project? Resource planning is important,

especially to estimate time and cost of the project. Done at early stage of planning, with clear
requirements. Involves activities: Define scope, Human Resource Planning, Resource Costing,
Resource scheduling and job delegation, Equipment planning, Resource RISK planning.
This section presents the resource planning and scheduling of MyCloths online store
system. We will strictly comply to our planned schedule until 9th September 2016. Our Work
Breakdown Structure (WBS) and Gantt chart are as displayed in Figure 1.1(a) and Figure 1.1(b)
respectively.
Figure 1.1(a) Work Breakdown Structure (WBS)
5
Figure 1.1(b) Gantt Chart
The life cycle and methodology approach that will be used to deliver this system is Waterfall. It
promotes quality control of process and product, and it is very rigid.
Figure 1.2 Waterfall Methodology
6
1.4 Requirement Gathering
Requirements gathering is an essential part of any project and project management.

Understanding fully what a project will deliver is critical to its success (Duncan, 2016).
Requirements definition report is correct, unambiguous, complete, consistent, verifiable,
modifiable, traceable, and ranked for importance. Requirements are best determined by systems
analysts and business people together. Techniques used are Interviews and Observation.
Interview
This team has agreed to use interview to collect t information on what MyCloths online
system would do. Interviews is where people having some private conversation when asking and
answering the questions. Interview can be consider as one of the best method for gathering the
information as we receive feedback on the question asked face to face immediately with more
explanation and it’s important for making the project, especially when the team want to design
and create the system for MyCloths.
There are few advantages of using interview as information gathering technique. First,
Better Observation of Behavior (Sincero, 2012). This is because we can actually see the outlook
and behavior of the respondents to the designed system based on the face reaction, body
movement and more. Next, tolerable Longer Interviews (Sincero, 2012). This means Open –
ended questions are more tolerated through the interviews as they will get a chance to explain
more about what they think about our new system compare writing it down.
Not just that, there are also some disadvantage in using interview which we realized
while carrying out the interview which is time consuming. This is because each interview can
take up to maximum 20 minutes depending on the type of respondent. Next is Cost, Cost is a
major disadvantage for face-to-face interviews. They require a staff of people to conduct the
interviews, which means there might be personnel costs. Personnel are the highest cost a
business can incur. It’s difficult to keep costs low when personnel are needed (Wyse, 2014).
7
The team decided to interview The Manager and other workers in MyCloths and also 5
loyal customer which have been shopping there. The total time taken for this interview is 3 days.
All the interview session happened at MyCloths and phone call. There were 5 open-ended
question asked where each question took up to 5 minutes minimum and 8 min maximum
depending on the respondent. The team did not wanted to waste a lot of time by asking many
complicated question, so all the question are straightforward. Below are the sample questions
asked :-
Sample question:
1) Do you agree with the system of MyCloths online Shop? Please state your reason.
2) How long is the duration to serve a customer once he or she walks in?
3) How long have you attempt to customers’ calls if they have any enquiries?
4) How do you keep all of the shop’s records?
5) Which area you would like to improve in the current system of MyCloths Shop? Please state
your reason.
6) What are basic functions you would like to perform on the online store of MyCloths Shop?
8
Observation
The type of research for this section is observational research. The definition of the word
observation is an act of recognizing and noting a fact or occurrence often involving measurement
with instruments (Merriam, 2016). Observation required whenever there insufficient knowledge
on a certain problem and at the same time to learn new information.
There are two types of observation, direct (observe how observee work by standing near
to them) and indirect (use remote video camera to observe). Direct observation is used as it is
comparatively cheaper and enables the system analyst can obtain reliable information directly
from users and ask them questions immediately during observation. However, people may
probably not perform as usual if they know they are being observed and they may be disturbed.
Benefits and Setbacks of Observation
Observation has various benefits as method for data collection. Observations can easily
be made as there are many examples in real life. This allows researchers to be able to find many
examples in real life situations so that the data collected can be accurate and reliable.
Observation does not require researchers on gathering respondents’ responses instead researchers
can just observe them which saves a lot of time. The problems are easily identifiable through
observation by making an in-depth analysis of the problem.
On the other hand, there are a number of setbacks regarding observational research. One
of the setbacks is that occurrence in the past cannot be observed and observations can only study
current situation which makes the observers having no other option but only to depend on the
documents available. Observation can be very time consuming as it may require the observer to
wait for a specific event to happen in order to study that particular event. Another setback of
observation is that the observer may have their own biases which may affect the result of the
observation.
9
Conduct of the investigation method
The first location that was chosen is the Buy Me. Buy Me uses almost the same system as
the store center we are researching about. The store specialize in selling traditional clothes. The
chosen store focuses on calling and walk-in customer. Target users being observed are manager,
clerk, walk-in customers and staff who serve walk-in customers and handles orders. The
observation is conducted on both weekdays when the staff are not too busy and willing to answer
questions and weekend when there are more customers so that the observer can know whether
the current system can operate fluently even when the workload increases. Besides, observer has
to find out whether customers satisfy with current system. The way the business is conducted is
similar to MyCloths where customer can call to purchase an item which is seen on a booklet or
they could just walk-in into the shop.
10
2.0 System Analysis
2.1 Requirement Analysis
Requirement analysis is important in compile, analyse and present data gathered from the
investigation activities. In order to understand why MyCloths online store is carried out and what
is the requirement need to be fulfilled. As the team member has conduct an interview and
observation on MyCloths online store and the local store, the following are the details that have
gathered from both analysis.
2.1.1 Interview
The requirement analysis of interviews will be conclude as by using the qualitative analysis as to
explores the nature of qualitative data of MyCloths store current systems. Qualitative analysis is
aiming to uncover or understand the big picture. (Libweb.surrey, 2012) All results may be carry
to answer the respective questions regarding the project. Based on the interview, the interviewer
response has been concluded to a results as the following statement.
1) Do you agree with the system of MyCloths online Shop? Please state your reason.
There are 81% of interviewers agree, 12% disagree and 7% are choosing nature.
2) How long is the duration to serve a customer once he or she walks in?
From the interview response, the data shows that the average time for a staff to serves a walk in
customers is between 10 minutes to 30 minutes.
3) How long have you attempt to customers’ calls if they have any enquiries?
70% of the staff choose to minimun of 5 to 10 minutes and 30% of the staff takes maximun 10 to
20 minutes per customer’s calls.
11
4) How do you keep all of the shop’s records?
The respondents are the local stores’ staff of MyCloths. The results of this questions is all of the
shops’ records are paper-based and they need to take note of customers’ orders by using
traditional method which is writing it into a notebook and refer back to the notebook page by
page when they have to tracking the order and get the quantity those information. It will be mess
up when the notebook get lost.
5) Which area you would like to improve in the current system of MyCloths Shop? Please
state your reason.
Most of the response from the customers which is 58% of the respondents is about to require
MyCloths Shop to improve the quality services as their customer services are not satisfy and the
productivity and efficiency work was weak. 24% of the responses are wish to get answers’ calls
by the staff as to getting more details on their order and the product information. 23% of the
customers have the same response which is wish to improve the order tracking of the product as
they can know when and what of the product is out of stock.
6) What are basic functions you would like to perform on the online store of MyCloths
Shop?
There are some basic functions that customers would like to get from MyCloths online store
which is to perform an online order, tracking the quantity of product, shipping card, compare
product and online payment. There are 27% of the customer would like to get the online order
functions, 11% of the customer are needs get the functions for tracking the quantity of product,
22% of customers would like to get a shipping card functions in the online store, 15% of the
customers want to compare product and 25% of the customers choose to get the online payment
functions. As a conclusion, the highest functions that has been choosing by the customers is
online order functions and the second is the online payment functions.
12
2.1.1 Obeservation
From observation and interview the developers found out that the current system is
operate with low efficiency, low throughput, slow response time, poor data management and data
inaccuracy. The users are wish to have functional system that can improved the performance of
current system. With similar system review developers are able to identify the suitable layout for
the new system followed by determining the coding method and database that will be
implemented into the new system. It also helps to determine the useful function for the new
system such as user friendly payment mechanism and feedback system. At last, the results are
presented under the forms of project requirements which classified the requirements into
functional requirements, non-functional requirements, business requirements, user requirements,
technical requirements, system requirements and so on.
13
2.2 Requirement Specification
2.2.1 Functional Requirements
This defines what this MyCloths Online System is suppose to do. The system is required to have
the following functional requirements:
Functional Requirements
1. Webpage Login
Member to login to MyCloths system. Supplier have function to login to Supplier system.
Store Manager have the function to login into Store Manager system. Staff have function to
login to Staff system.
2. Webpage Logout
Member to logout from supplier system.
3. View List of Inventories
Store Manager to view new entry of inventory from supplier and member’s order inventory.
4. Order List of Needed Product
Store Manager compiles a list of needed product and sends an order to the supplier.
5. View Pending Order List of Needed Product
Supplier View the order list of needed product sent by MyCloths Store Manager.
6. Verify Order List of Needed Product
Supplier verify the supplied cloths is sent to MyCloths warehouse.
7. Make Detailed List of Supplied Product
Store Manager receives details of new product, along with the number of product that have
arrived in the warehouse. Store Manager creates a list of supplied product for Staff to enter
into MyCloths database.
8. Manage Inventory of Product
Staff manages the inventory of the product. Staff has to ensure each product has its respective
product ID, product name, product category, image, description, quantity of product and unit
price. Staff can Add new product, Remove product or Update existing product into MyCloths
14
as according to store manager’s detailed list of supplied product and member’s order
inventory.
9. Update Website
Store clerk which is part of staff is responsible to update website.
10. Manage Member Delivery Order
Staff handles the date of shipment and update member delivery order information.
11. View Product
Customer could browse or navigate the website for product for free.
12. Search Product
Customer could search the desire product of their choice for free.
13. Register
Function to assist customer to create a new account to be a member of MyCloths.
14. View Account Information
Member could view their account information, view rewards, view purchase history,
15. View Rewards
Member to view available discounts or gifts.
16. Manage Purchased Review
Member could view, add, edit or delete their own review of the purchased product only.
17. Read Product Review
Only member have access to read other product reviews.
18. Read More Product Information
While viewing product, member have access to read more details of the cloths.
19. Add to Shopping Cart
While viewing product, member could add product in shopping cart if they wish to purchase.
20. View Shopping Cart
Member could view the summary of selection and the total cost to be paid.
21. Place Order
Member to place order if they want to buy.
22. Verify Shopping Cart
Member will be prompt a confirmation message before proceeding to verify payment.
15
23. Verify Payment
Member will verify their payment to complete the Place Order.
24. Issue Receipt
Member will be issued an option to save or print receipt once payment is made.
16
2.2.2 Non-Functional Requirements
This defines how this MyCloths online system is suppose to be.
Non-Functional Requirements
Look and Feel

Requirements
1. Appearance Requirements
The application of this system shall appear simple and
straightforward. Its appearance shall conform to the common
reading pattern, that is, from top to bottom, left to right.
2. Style Requirements
The application of this system shall have a basic and simple
Graphic user Interface(GUI).
Usability and
Humanity 1. Ease of Use Requirements
Requirements This system shall be easy for everyone to use. This system
shall help users to avoid making mistakes by prompting
confirm messages and so on.
2. Personalisation and Internationalisation Requirements
The application of this system shall allow user to retain to
user’s’ settings preferences. The website is only available in
english
3. Learning Requirements
This system shall be easy for everyone to learn. The staff can
assist the user with FAQ. Any future question user can send
email to MyCloths to be assisted by customer service.
4. Understandability and Politeness Requirements
This system shall use appropriate symbols and proper words
depending on the language that is understandable by
17
everyone. There will be no online advertisement on the
website.
5. Accessibility Requirements
This system shall be able to be used by partially sighted users.
Performance
Requirements 1. Speed and Latency Requirements
The response shall be fast enough to avoid interrupting the
user’s flow of thought. The response time to display a
particular product shall not be more than 10 seconds as our
server are based in Malaysia also depending on the internet
speed. The system shall update new information right after
the responsible staff updated the website.
2. Safety-critical Requirements
User are allow to zoom in or out to view a product better as
we don't want them to weaken their eye strength
3. Precision or Accuracy Requirements
All monetary amounts shall be accurate to two decimal
places. The accuracy of the calculation of payment shall be
very high.
4. Reliability and Availability Requirements
This system shall be available for use 24 hours per day, 365
days per year.
5. Robustness or Fault Tolerance Requirements
This system shall continue to operate on backup servers ann it
won't be disconnected from the main server. This system shall
operate on backup power generator so it does not disconnect
from the electricity source.
6. Capacity Requirements
This system shall cater for about 150 simultaneous users for
18
weekdays and about 300 simultaneous users for weekends for
every retail store.
7. Scalability and Extensibility Requirements
This system shall be capable of processing the expected
growth of 500 customers.. This system shall be able to
process 10 000 transactions per hour.
8. Longevity Requirements
This system shall be expected to operate within the maximum
maintenance budget for a minimum of ten years.
9. Installation Requirements
No installation is required for customers and members, as
long the customer has an internet connection and a browser to
surf into the website. For employee, the system shall be
installed in the retail store and specified environment.
Operational and
Environment 1. Expected Physical Environment
Requirements This system shall be used in a retail environment. The
physical environment is also expected to be air-conditioned
( to keep the server cool as it's running 24 hours) and
surrounded by various products with security door at the
entrance.
2. Release Requirements
Each release shall not cause previous features to fail. The
maintenance releases will be offered to the end users after
being approved from testing.
Maintainability and
Supports 1. Maintenance Requirements
Requirements A new retail store must be able to be added to the system in a
day. A management information system report shall be
19
available within one working week of the data when the
requirements are agreed upon.
2. Supportability Requirements
This system shall be supported by help centres that control
the end users S.B.S. account. s.
Security
Requirements 1. Access Requirements
. Only retailers shall be able to access the database of its own
stores. Only authorised personnel such as S.B.S. help centre
can access end users’ accounts other than the end users
themselves.
2. Integrity Requirements
This system shall be able to detect any hacking activities done
to the end users’ accounts and freeze the end users’ accounts.
3. Privacy Requirements
The mobile application of this system shall make its users
aware of its information practices before collecting data from
them. It shall also notify customers of changes to its
information policy. It shall protect private information in
accordance with the relevant privacy laws.
4. Audit Requirements
Every purchase made using this system shall be recorded to
the database along with the user name, location, time, items
and prices.
Cultural and Political

Requirements 1. Cultural Requirements
This system shall not be offensive to religious or ethnic
groups. This system is available in English as it's one of the
20
most known and understandable language
2. Political Requirements
This system shall be able to make all functionality available
to the CEO as the CEO is the Supersuper.
Compliance
Requirements 1. Legal Compliance Requirements
Personal information shall be implemented so as to comply
with the Personal Data Protection Act. This system shall be
able to comply with the tax laws.
2. Standard Compliance Requirements
Meets all the requirement which is set by MAC an
21
22
3.0 Initial Design
3.1 Conceptual Design
Figure 3.1 MyCloths Online System Use Case Diagram
23
3.1.1 Use Case Descriptions (Akashdeep Singh TP034684)
Use Case Register

Name
Actors Non Member
Precondition Non Member is not login but is in the system only able to view the
s website and product.
Basic Flow 1. Non Member input email address, password, and confirm
password,. After input, customer click “GO” button.
2. System validate input.
3. System returns message “Successfully register.”
4. System generate new member account into member database.
Alternative 1. System returns “Invalid mail” message when email input is

Flow invalid.
2. System returns “6 characters or longer” when password input is
too short.
3. System returns “Password does not match” when confirm
password input is not the same as password.
4. Exit.
Exit ● Submit button is clicked.

Condition ● Navigate to other buttons.
● Click return to previous page.
● Click exit button.
24
3.1.2 Use Case Descriptions (Chai Jia Jiun)
Use Case Order List of Needed Product

Name
Actors Member
Preconditions Member is login in the system
Basic Flow 1. Member is logged in into the system.

2. Homepage is displayed
3. Product description
4. Member add the product into cart
Alternative
Flow
Exit ● Navigate to other button.

Condition ● Click exit button.
25
3.1.3 Use Case Descriptions (Chuah Siew Yiing)
Use Case Verify Order List of Needed Product

Name
Actors Supplier
Preconditions Supplier is login and has clicked “SUP” button.
1. System retrieves Supplier’s button request.

Basic Flow 2. System sends Supplier to “View Pending Order List of Needed
Product”.
3. Supplier inputs product name, amount, order date, sent out date,
tracking code, price and click “Send Order” button.
4. System returns message “Order Sent.”
Alternative
Flow
● Navigate to other buttons

Exit Condition ● Click return to previous page
● Exit button is clicked
26
3.1.4 Use Case Descriptions (Jasmine Toh Sheau-mint)
Use Case Manage Member Delivery Order

Name
Actors Staff
Extends Update Website
Preconditions Staff is login in the system and selected “Manage Delivery Order”
Basic Flow 5. Staff is logged in into the system.

6. Staff Clicks on Delivery Button
7. Staff is directed to Tracking Page
8. Staff enter the track ID and Update the Status
9. Staff Click submit to update the status of delivery
Alternative
Flow
Post 1. Homepage is shown.

Condition 2. Manage Member Delivery Order is shown.
3. Member delivery order number, status and details will be shown.
Exit ● Return page button is clicked

Condition ● Navigate other button is clicked.
● System Logout button is clicked.
● Exit button is clicked.
27
3.2 Object Diagram
Figure 3.2.1 Class Diagram for MyCloths Online System
28
3.3 Behaviour Diagram
3.3.1 Behaviour Diagram (Akashdeep Singh TP034684)
Figure 3.3.1 Register State Behaviour Diagram
29
3.3.2 Behaviour Diagram (Chai Jia Jiun TP037875)
Figure 3.3.2 Add to Shopping Cart State Behaviour Diagram
30
3.3.3 Behaviour Diagram (Chuah Siew Yiing)
Figure 3.3.3 Verify Order List of Needed Product State Behaviour Diagram
31
3.3.4 Behaviour Diagram (Jasmine Toh Sheau-mint TP034709)
Figure 3.3.4 Manage Member Delivery Order State Behaviour Diagram
32
4.0 Physical Design
4.1 Prototype
In this assignment students were advised to create a prototype of MyCloths website.

This website prototype will include the essential functionality such as products review, add
products to shopping cart, purchase products so on. Picture below shows main page of the
website prototype.
Diagram 4.1.1 Homepage
Users are able to view all the products as listed by best seller or item on sales and prices
of the Traditional Clothes.
33
Diagram 4.1.2 Quick Review and Compare
Diagram 4.1.3 Product Details

As soon as user clicked on quick review as shown in diagram 4.1.2, it will show the
product info and user can add products to cart.
34
Diagram 4.1.4 Sign up for non-member

When user added product to cart, non-member will need to sign up and proceed to
shopping cart.
35
Diagram 4.1.5 View cart
Diagram 4.1.6 Shopping Cart
Once the member confirm to checkout, they can click on confirm and subtotal is shown.
36
Diagram 4.1.7 Checkout Page
After confirming order, members can make payment by filling in payment details.
Diagram 4.1.8 Receipt
After members paid successfully, they will receive their receipt online and they can
choose to print or save the receipt.
37
Diagram 4.1.9 Where to buy
It shows the location and map of Mycloths.
38
Diagram 4.1.10 FAQ
It provides member some frequently asked questions to solve their doubts.
Diagram 4.1.11 Contact
Members can drop by messages for inquiries.
39
Diagram 4.1.12 Update Account Information
Member can update their account by names, phone, address and password.
Diagram 4.1.13 Rewards

Member can claim their rewards from here. If there's coupon, user can apply the coupon
code to enjoy the rewards.
40
Diagram 4.1.14 Staff, Store Manager and Supplier
Staff, Supplier and Store manager need to enter a password to view their page, the
password is 12345.
41
5.0 Implementation and Deployment
5.1 Construction
System construction is the process of building the rest of the system through a
programming language. This is usually done after the design of the system is approved. Figure
below shows a list of software and tools that are being used in the process of system construction.
The project team had used several software/tools to develop online store for MyCloths Shop.
Wix.com is the main tool used in creating the prototype for Mycloths online store. It
provides variety of visually impressive layouts that designed for small businesses, restaurants,
online stores and artists such as musicians and photographers. They are optimized for mobile
devices and can be spiced up with one of the numerous apps available from the Wix App Market.
(Tool Tester, 2016). The purpose of using Wix.com is to help and guide us throughtout the
assignment for creating an exclusive and user-friendly website which featured with graphics,
menu and other functionality operatively.
Software/Tools Purpose
HTML HTML is used to create the whole website layout. HTML is

used because that a basic need for developing a website.
PHP PHP is used to connect the website with MySQL database.

To store data which include customers’ information and
tracking product.
CSS CSS is used to help beautify the website to make the website
looks more elegant and useable.
42
JavaScript JavaScript is used to make the website more interesting and

with the use of animations such as slide show.
Notepad ++ Notepad++ is a code editing software that is used to code

this website which include HTML, PHP, CSS, and
JavaScript for the website. Notepad++ is used as it is
free and simple to learn.
MySQL MySQL is a database software that is used to store

customers’ data as well as tracking data.
Photoshop Photoshop is a picture editing software that is used to make a

mock up design for the website. Also, for editing the
cloth image to make it much shaper and etc before
uploading
GitLab GitLab is a repository hosting site which allows developers

to upload their codes on the site. Each developer will
just have to push the code which is changed and other
user will just have to pull it. Multiple people can work
on a project to make work simpler and easier.
SourceTree SourceTree is a git client that allows developers to push their

codes to the particular place where the data is stored.
43
5.2 Testing
Software testing is a procedure of executing a software or application with the

expectation of finding the software bugs. It is a process of validating and verifying a software
program in order to meet the business and technical requirements. (Istqb, 2016) The type of
software testing this team would carry out for MyCloths is compatibility testing. The developer
must be sure that the system is executable and compatible with other application software and
operating systems. The three level of testing used would be Unit test, Integration test, and
System test. Integration test develop tests with minimal overlap that test an interesting path or
scenario through use case. System test is a test combinations of use cases instantiated under
different conditions such as hardware configurations, system loads, number of actors and
database size. Below are the different levels of testing suitable to be carried out on MyCloths
online website.
44
No. Test Case Test Type Test Steps Expected Actual Remarks
Result Result
1. Webpage Unit Test 1. Open User Shows error Correction

Login application. successfully message. made to
2. Click signed-in Email is code to
Login/Sign into the invalid and check ID
up. system. password validity.
3. Input “x” for Home Page length must
email and displayed. be between
“x” for 4 and 15.
password.
2. Add to Integration 1. User login as User able to - -

Shopping Test Member and add desired
Cart view product to
product. cart.
2. User click
“Add to
Cart”
3. Search Order System 1. User enter Result is Result takes Developer

Test “<” to search shown. forever to to take this
bar. load. problem
into
consideratio
n..
Table 5.2 Test plan
45
5.3 System Deployment
To determine the system deployment to use is depend on the scope and complexity of the
change associated with the new system and the organisation’s risk aversion. (Valacich, 2006)
The two type of system deployment this team has decided to use is direct changeover and phased
changeover.
Before the implementation stage of this system, the design stage will be practiced on a
few sheets of papers. After the group is able to be satisfied with the design, it will undergone a
direct changeover to Microsoft Visio. With this changeover, it will tremendously help this team
to save cost. However, it is a time-consuming process and it requires the whole system to finish
installation in order to see the benefits.
This team will contribute to the phased changeover of the system. Phased changeover is a
changing from the old information system to the new one incrementally, starting with one or a
few functional components and then gradually extending the installation to cover the whole
system. (Valacich, 2006) This team will assist the phased changeover of MyCloths online system
by using a substitution method. This is as a mean to improve the current system into a more
upgraded and more refactored system. The team will create another website as a backup design
system. While helping to enhance and beautify the system to be more user friendly, the system
will also be able to have more scalability, giving more capabilities with extended incrementation
such as adding a Wish list Cart. Additional features would be adding customised mini game for
customer to play in the homepage, adding songs, videos, customised mouse design in the system.
46
PART B - INDIVIDUAL COMPONENT (30%)
6.0 Selection of Methodology
6.1 Compare and Contrast (Akashdeep Singh TP 034684)
Among the 3 methodology which I have picked, Scrum, Extreme Programming (XP) and
Waterfall are suitable for developing MyCloths online store. I believe the most suitable to be
used for this project will be Extreme Programing (XP) below are the comparison why ;-
Scrum Extreme Waterfall

Programming
(XP)
Purpose Good for completing To deliver the To develop

complex and software which transaction- or
innovative project meets customers’ mainframe-based
(Scrum Alliance, needs on time system (CMS, 2005).
2016). (Kumar et al, 2015).
Stages/ Cycle The whole cycle Start with Planning Very systematic as it
begins with the stage and continue follows the flow of
creation of Product by repetition: stages and starts with
Backlog, followed by Designing, Coding, Requirements,
Sprint Planning, Testing and Design,
Sprint with iteration Listening.Teration Implementation,
of 2 to 4 weeks and is 1 to 2 weeks but Verification and ends
result in potential it ends with a with Maintenance.
shippable product functional product.
47
increment..
User Involvement User is highly User is highly User involvement is

involved in all the involved in all the low and restricted to
stages stages the defining of
requirements at the
planning stage. Does
not usually meet user
requirement most of
the time
Project Team Team with 3 to 9 Team ranges from 5 Team Usually

members. to 15 people. depends on project
but usually large
team as it's normally
a complex project,
Documentation Minimal Minimal Comprehensive and

completed
Time/ Cost Cost to develop the Cost to develop the Be managed as user
product are hard to be product are hard to is not much involved
estimated if be estimated if in every stage.
requirements keep requirements keep
changing (Harnek changing (Harnek
Singh, 2016). Singh, 2015).
Change Allowance Allow change Allow change No changes allowed
48
as this will cost more
Suitability · Suitable for Works Great for a Suitable for large,

fast-moving and project which costly and complex
cutting edge project changes the project.
requirements,
speedily frequently.
Drawback · Knowledgeable Knowledgeable and · Inflexible

and skilful team skilful team because going
members are needed members are backwards to
to make the project needed to make the previous stages and
successful project successful skipping of
unimportant steps are
·The success depends The success not encouraged as
on commitment of depends on this will increase
team members commitment of cost.
team members.
6.2 Extreme Programing (XP)

Among this 3 methodology which i have discussed, I believe Extreme Programing (XP) is best
methodology for MyCloths online store project. XP is way better for this project as it all about
speed and flexibility because as a retailer MYCloths definitely will not want to fall behind of
their competitors due to that fast and working product offered by XP is much suitable for this
project. Next, there are 3 to 9 people which works on a project depending on the deadline and XP
would be able to be released and fully functional by that time compared to Scrum. On the other
hand, User involvement during development of the project will ensure that the project is made
49
just the way which is desire by MyCloths unlike Waterfall where the user involvement is low.
Not just that, changes can be made to MyCloths after getting feedback from end user as it's an
ongoing process. Last, XP focus on delivering fully-tested, independent, valuable, small features
as said by agilistapm (2016)
50
6.1 Compare and Contrast (Chai Jia Jiun TP037875)
Elements SDLC Waterfall Scrum DSDM
Purpose ❖ Linear sequence ❖ A system that is ❖ To develop a

design and each self-reliant on system that
phase must be the team meets the
completed working business needs
before moving together in a on time and
to the next clear on budget.
phases ❖ To emphasize ❖ To address
❖ Used only when delivery of common
the valuable, problems
requirements independent, faced by
are very well small and fully projects such
known, clear tested features as late
and fixed. of the software. delivery, cost
overruns or
the final
deliverable
not being
completely fit
for purpose.
Model Structured Iterative incremental Iterative incremental

model model
Phases 1. Requirement 1. Initiate 1. Pre-project

analysis 2. Plan and phases
2. System Design Estimate 2. Feasibility
51
3. Implementation 3. Implement phases
4. System Testing 4. Review and 3. Foundation
5. System Retrospect phases
Deployment 5. Release 4. Exploration
6. System phases
Maintenance 5. Engineering
phases
6. Project life-
cycle phases
7. Post-project
phases
Time Long as the particular Short as the entire Short as it optimum

phase is required to be phase can be completed length is typically
completed in order to within 2-4 weeks between two and four
proceed to next phase. weeks
Cost Expensive if there are The cost is fixed during The software project
changes needed to be the process of is ensured to be
done which lead to developing software delivered on budget
redesign, project which means that the
reimplementation and cost is fixed as
retesting. MoSCow technique
and time boxing are
practised and
followed.
Risk of changes Changes for the scope Easily embrace changes Accommodate to
of the software project over following a plan. changes other than
can cause high level of following the plan
risk and uncertainty of blindly.
52
the software project.
User involvement Users are not allowed High level of user It concerns what users
to review and provide involvement is need the most.
feedback on a software compulsory. Therefore, it allows
product users to heavily
involved in the
development process
which causes high
level of user
involvement
Strength ❖ Simple to ❖ SCRUM teams ❖ covers the

implement can collaborate entire
❖ Stresses more efficiently lifecycle of a
meticulous and project and
record keeping communicate provides best
allows for the when the project practice
ability to is requiring guidance for
improve upon more attention on-time
the existing to certain sprints ❖ in-budget
program in the ❖ Easy Feedback delivery of
future. and Changes projects
❖ It has high ❖ The project ❖ with proven
visibility as the manager can scalability to
output is establish what address
generated after areas need fixed projects of all
each stage with less sizes and for
damage to other any business
areas due to the sector
frequency of the
53
feedback.
Drawbacks ❖ Real projects ❖ Slacking Team ❖ More user

rarely follow Members Cause involvement
the sequential Inefficiency. If can be danger
flow and one member of some time if
iterations in this the team the user is not
model are ❖ The high an appropriate
handled possibility level one
indirectly of creating ❖ restrictive and
❖ difficult to get intense project difficult to
customer cycle with tight work with
requirements deadlines and compared to
explicitly high level of other agile
❖ Each phase stress due to development
must be new software
completed requirements method
before moving and uncertainty
to the next ❖ Stress can build
phases, hard to up due to the
move back to frequency of
change on the deadlines
previous phase throughout a
❖ a small change SCRUM
in any previous managed
stage can cause project.
big problem for
subsequent
phases as all
phases are
54
dependent on
each-other.
55
6.2 Dynamic System Development Method (DSDM)
DSDM is stands for Dynamic System Development Method which is selected as the most
suitable methodology for developing MyCloths online store. The one of the reason to choose the
DSDM among the others system development methodologies such as SDLC waterfall and Scrum
due to they typically focus on development and delivery of product only (DSDM Consortium,
2015). DSDM involvement in an iterative development and incremental approach which
recognizes that projects are limited by time and resources, and plan accordingly to meet the
business needs and continuous user is responsive to changing requirements, in order to develop
a system that meets the business needs on time and on budget. (McKay, 2015) DSDM supports a
testing technique which is called acceptance test that can help MyCloths to verify the software
product has met the requirements specification where this technique is not supported by using
SDLC waterfall and SCRUM. (TutorialsPoint, 2016) Besides that, DSDM has been developed to
address common problems faced by projects such as late delivery, cost overruns or the final
deliverable not being completely fit for purpose.
There are eight principles of DSDM which consists of focus on the business need, deliver
on time, collaborate, never compromise quality, build incrementally from firm foundations,
develop iteratively, demonstrate control and communicate continuously and clearly. The main
criteria for acceptance of deliverable in DSDM is on delivering a system that addresses the
current business needs. It focuses on its efforts on critical functionality and the frequent delivery
of products. (Quotium, 2013) The product can be tested and reviewed where the test record and
review document can be taken into account at the next iteration or phase. It would be suitable for
MyCloths as it was a small business shop which DSDM has proved to be scalable and work
effectively in this kind of business.
56
The DSDM framework consists of three sequential phases which is pre-project, project
life cycle which contain 5 stages and post-project. The first stage of developing an online store
for MyCloths by using DSDM methodology is pre-project stage. The objectives of this stage is to
describe the business problem to be addressed and confirm the project is in line with business
strategy. As an example, MyCloths store to conducts various discussions which to identify the
current problem faced by MyCloths local store. They will have to determine a solution for the
problem and the development of an online store which named MyCloths.com.my is the solution
of MyCloths.
The next stage is the feasibility stage that takes place which the project team analyses the
project. It looks into the team available, the budget available the expected functionalities and the
possibility of building the functionalities in the resources available. (Quotium, 2013) The project
team determines the viability of MyCloths.com.my online store project bases on business and
technical perspective which to determining the availability of proejct team, resources which can
aid to build the functionalities of the project, the cost effectiveness and timeframes.
After the agreement of the feasibility assessment, foundations stage is the next after the
feasibility study. There are three essential perspectives of business, solution and management
must to be combined to provide a clear project. (ukessays, 2015) This stage guide the project
team to establish whether there is a feasible solution of MyCloths.com.my to the business
problem from Pre-Project, outline the possible approaches for delivery which including strategies
for sourcing the solution and project management, state the timescale and costs for the project
overall and more. Through this stage, the project team is able to gain deeper understanding on
details of online store project scope and how it will be carried out and so on.
57
Next is the exploration phase which is applicable when different teams are responsible
for creating early iterations of the solution and for engineering the finished system. (ukessays,
2015) This may be the case where the bulk of the development is outsourced or completed
offshore. The objectives of the exploration phase which to create a functional solution that meets
the needs of the business. This phase is to deploy the solution into the real environment and to
train the user like the staff of MyCloths store to understand all the functions of the
MyCloths.com.my
The last is the Post Project phase which used for assessing the deployed solution. The
project team estimates how good the expected business benefits of MyCloths Shop had met. The
project team access benefits for individual releases, the whole website developed which is
MyCloths.com.my or may completely omitted depends on the needs of MyCloths Shop.
58
6.1 Compare and Contrast (Chuah Siew Yiing)
The best development methodology depends on project characteristics. (Dennis, 2009)

The three IS development methodologies I feel suitable for this project are Spiral, Phased, and
Scrum. Below is a comparison summary table of my chosen methodologies:
IS Development Spiral RAD- Iterative Scrum

Methodologies
Purpose Focuses on early Parallel developed “Team-work” based

identification and components or methodology
reduction of project functions. They all
risks. will be assembled
together into a
working prototype.
Model Incremental Incremental Agile development
Phrases Planning, Risk Business modeling, Product backlog

Analysis, Data modeling, refinement, Sprint
Engineering, Process modeling, planning meeting,
Evaluation Application Daily standup
( Istqbexamcertificati generation, Testing meeting, Sprint
on, n.d) and turnover review meeting,
( Istqbexamcertificati Sprint retrospective
on, n.d) meeting (umsl,n.d)
Risk of Changes Low Moderate Low
59
Suitability Continuously Quick application Efficient schedule
reducing project risk development Improve productivity
level in teams
Usefulness for Excellent Good Excellent

unclear user
requirements
Usefulness for Good Good Poor

unfamiliar technology
Usefulness for Excellent Good Poor

complex systems
Usefulness for Good Good Good

reliable systems
Usefulness for short Good Excellent Excellent

time schedule
Usefulness for Poor Excellent Excellent

schedule visibility
6.2 Scrum
Scrum is an agile, iterative, incremental developing method.(Usmd. n.d) It relies on a

cross-functional team, consisting of product owner, team members, and scrum master. I have
chosen this because it dominates the other 2 methodologies in terms of a unclear user
requirementsand excellent in for short time schedule.
To support the statement, I will describe on how it will be developed in my new project.
A product owner, responsible in gathering information, begins with product backlog refinement.
Product owner will gather inputs to plan the project workflow. Secondly, product owner will
hold a sprint planning meeting with the team, picking the best to least priority stories from them.
60
Product owner will compile the stories to a sprint backlog and breakout the task to each team
members. A daily standup meeting will be held daily to check the team’s work progress, next
coming work plan and obstacles. The team will present their work during the sprint review
meeting. Product owner will access the team’s work through the sprint backlog and has a right to
reject uncompleted stories. Finally, the team and product owner will meet scrum master in the
sprint retrospective meeting to get scrum master’s feedbacks for the team and product owner’s
sprint to test how the project’s system implementation and deployment efficiencies.
I believe this methodology would give a hopeful direction to my new project because of
the benefit it provided. Its product is not based on unfinished work, but rather based on a
completed work. (Buttice, Matthew. 2015)
Figure 6.3.2 Scrum Methodology (Zailan. 2016)
61
6.4 Compare and Contrast (Jasmine Toh Sheau-mint)
Methodologies SDLC Waterfall DSDM RAD
Purpose To illustrate the To ensure the To make a high-

software feasibility and speed, qualified
development business sense system that uses
process by using of project the lowest cost.
linear sequential before it is
flow and make developed.
sure there is no To deliver clear
overlapping in the picture on all
process of aspects of the
developing software by
software. making heavy
use of
prototyping.
Model Structured Interactive incremental Unified Modeling
model Language (UML)
Phrases Requirement Pre-project Analysis & Quite

Analysis phase Design
System Design Feasibility Demonstrate
Implementation phase Refine
System Testing Foundations Build
System phase Testing
Deployment Exploration Implementation
System phase
Maintenance Deployment
phase
Post-project
62
phase
Time & Cost Time and cost are can be Short as it practices Time is short whereas
managed easily. time boxing which its cost of development is
optimum length is low. (depends on changes
typically between two and requirements).
and four weeks.
Risk of Unbearable to change, the The software project is Risk is low. Changes of
Changes project outcome and an allowed to be requirement is based on
extensive plan are reversible if there are old version of prototype.
predictable at the changes spotted during
beginning. the process of
developing software
project.
User Users are not allowed to It allows users to High user involvement.
Involvement review and provide seriously involved in Developer usually get
feedback on a software the development feedback for every stages
product. The users signed process which causes of projects.
off the requirements high level of user
documents only which involvement as it
lead to low level of user concerns what user
involvement. needs the most.
Suitability Short projects which the Small straightforward Suitable for small to
requirements are very solutions or large medium size projects.
famous, clear and fixed. complex corporate
projects.
Drawbacks The high The team RAD focus on
possibility level of assembled for strong team and
the users will be development of individual
dissatisfied with software performances. This
the delivered project has not approach demands
63
software product been given highly skilled
because the autonomy developers and
deliverables are which can designer’s team.
based on cause excessive Inapplicable to
documented time being cheaper projects as
requirements spent in cost of modeling
which the users are decision and automated
unable to know making. code generator is
what will be The very high and it
delivered until the development will increase the
completion of the team must have complexity of
software project. high level of management.
Difficult to go experience and
back to change skills in both
something the business
and technical
areas.
64
6.2 Rapid Application Development
RAD means to Rapid Application Development. This model is suitable for MyCloths as
it is a small project. RAD is created to provide faster development (Rapid Application
Development, 2016) and higher quality systems than the traditional life cycle with a lower cost.
It is designed to take advantage of powerful development software such as CASE tools and
prototyping tools. RAD methodology is the most ideal methodology to be implemented in this
projects compare to DSDM and SDLC.
Rapid Application Development model focus on prototyping and rapid cycles of iterative
development to speed up development and elicit early feedback from business users (Wave
Maker, 2016). RAD starts with understanding requirement from customer, then proceed to
analyzing and gathering requirement before prototyping. The main purpose of RAD is to
emphasizes on its speed and it is designed to deliver the product at the earliest. In this case the
customer will be actively involved in the prototyping phase where the developers proceed to
build. RAD projects follow the iterative model that consists of small teams including developers,
domain experts, customer and other IT resources working continuously on their prototype
(SDLC - RAD Model, 2016). RAD highly dependence on code generators and prototyping tools.
As a result, RAD methodology is the most ideal methodology to be used in projects small
businesses just like Mycloths.
65
Diagram 1: Rapid Application Model (Jyoti, 2015)

Requirement Planning
The planning team conducts meetings with client concerning their requirements and
achieve mutual understanding of objectives of the entire project. The task will start from research
and familiar with the current situation and finalize requirements and get approval to proceed with
prototype.
User Design
It is an outline design for system which has been confirmed and finalized. They will
have a meeting on justifying each component of the system. They complete the analysis by
creating activity diagrams that defines the correspondence between processes and data. The
implementation for the system is considered and reviewed and a plan for implementing the
system is prepared.
66
Construction
For Construction stage, the developers working precisely with users to finalize the design
and build the software system. The design of each function is completed and in this stage there is
a cutover production, which allows user to make minor changes on the software. Also,
construction phrase will generate test data and system documentation to operate new application.
Implementation
This stage consists of integrating the new system into the business. The design team will
provide training for the system users while the users perform acceptance testing. The design
team also helps the users to transfer from their old procedures to new ones that involve the new
system, troubleshoots after the deployment, and identifies potential enhancements.
67
7.0 References
"Rapid Application Development". Blueink.biz. N.p., 2016. Web. Available at:

http://www.blueink.biz/RapidApplicationDevelopment.aspx [Accessed 18 Aug. 2016].
"SDLC - RAD Model". www.tutorialspoint.com. N.p., 2016. Web. Available at:

http://www.tutorialspoint.com/sdlc/sdlc_rad_model.htm [Accessed 18 Aug. 2016].
Agilistapm (2016). Differences between Waterfall, Iterative Waterfall, Scrum and Lean Software
Development (In Pictures!) | The Agilista PM. [Online]. 2016. Agilistapm.com. Available from:
http://www.agilistapm.com/differences-between-waterfall-iterative-waterfall-scrum-and-lean-
software-development-in-pictures/. [Accessed: 8 September 2016]
Anon, (2016). [online] Available at: http://www.ftms.edu.my/images/Document/IMM006%20-

%20RAPID%20APPLICATION%20DEVELOPMENT/Chapter%202nnote.pdf [Accessed
9 Sep. 2016].
Buttice, Matthew. (2015). Scrum Methodology vs Agile Methodology. [Online] Available at:
http://www.onedesk.com/scrum-methodology-vs-agile-methodology/ [Accessed 03 September
2016]
CMS (2005). SELECTING A DEVELOPMENT APPROACH. [pdf] USA: Department of Health

& Human Services. Available from: https://www.cms.gov/research-statistics-data-and-
systems/cms-information-technology/xlc/downloads/selectingdevelopmentapproach.pdf
[Accessed: 26th July 2016]
Dennis, Wixom, Roth. (2009) System Analysis & Design [Online] Available
at:http://www.uoitc.edu.iq/images/documents/informatics-
institute/Competitive_exam/Systemanalysisanddesign.pdf [Accessed 09 September 2016]
68
Dennis, Wixom, Tegarden. (2009). Systems Analysis and Design with UML. 3rd Edition. John
Wiley & Sons, Inc.
Harnek Singh, P. K. (2016). System Deployment Approaches, CT046-3-2. [Lecture notes]

System Development Methods CT00046-3-2. System Development Methods. Asia Pacific
University of Technology & Innovation, TPM L2-5, 20th August
Istqbexamcertification. (n.d) What is RAD model- advantages, disadvantages and when to use it?
[Online] Available at:http://istqbexamcertification.com/what-is-rad-model-advantages-
disadvantages-and-when-to-use-it/ [Accessed 09 September 2016]
Istqbexamcertification. (n.d) What is Spiral model- advantages, disadvantages and when to use
it? [Online] Available at:http://istqbexamcertification.com/what-is-spiral-model-advantages-
disadvantages-and-when-to-use-it/ [Accessed 09 September 2016]
Istqbexamcertification.com. (2016). What is Software Testing?. [online] Available at:

http://istqbexamcertification.com/what-is-a-software-testing/ [Accessed 9 Sep. 2016].
Kumar, M. (2015). A Detail Study of Agile Software Developnment with Extreme

Programming. International Journal of Advanced Research in Computer Science and
Software Engineering. [Online] 5 (10). p. 719-725. Available from:
http://www.ijarcsse.com/docs/papers/Volume_5/10_October2015/V5I10-0113.pdf [Accessed:
27th July 2016]
Libweb.surrey.ac.uk. (2012). Analysing Qualitative Research Data. [online] Available at:

http://libweb.surrey.ac.uk/library/skills/Introduction%20to%20Research%20and%20Managing%
20Information%20Leicester/page_75.htm [Accessed 3 Sep. 2016].
McKay, V. (2015). What is DSDM? | Process Maturity | FAQ. [online] Selectbs.com. Available
at: http://www.selectbs.com/process-maturity/what-is-dsdm [Accessed 5 Sep. 2016].
69
Merriam-webster.com, (2016). Definition of OBSERVATION. [online] Available at:
http://www.merriam-webster.com/dictionary/observation [Accessed 1 September. 2016].
Mind Tools Editorial Team. (n.d.). Business Requirements Analysis. [Online]. Available from:
https://www.mindtools.com/pages/article/newPPM_77.htm [Accessed: 13 July 2016]
Project Smart. (2016). Requirements Gathering 101. [online] Available at:

https://www.projectsmart.co.uk/requirements-gathering.php [Accessed 9 Sep. 2016].
Quotium.com. (2013). Quotium | DSDM Project Lifecycle. [online] Available at:

http://www.quotium.com/performance/dsdm-project-lifecycle/ [Accessed 4 Sep. 2016].
S.Valacich, Joseph. F.George, Joey. and A.Hoffer, Jeffrey. (2006) Essentials Of Systems
Analysis And Design. 3rd Edition. Upper Saddle River: Pearson Prentice Hall
Scrum Alliance (2016). The Scrum Guide. [Online] Available from:

https://www.scrumalliance.org/why-scrum/scrum-guide [Accessed: 26th July 2016]
Sincero, S. (2016). Explorable. [Online]. 2016. Explorable.com. Available from:

https://explorable.com/personal-interview-survey. [Accessed: 1 September 2016].
Sofia. (2010). Requirements analysis. [Online]. Available from:

http://www.uacg.bg/filebank/acadstaff/userfiles/publ_bg_397_SDP_activities_and_steps.pdf
[Accessed: 13 July 2016]
ukessays.com. (2015). Uk Essays. [online] Available at:

https://www.ukessays.com/essays/computer-science/dynamic-systems-development-method.php
[Accessed 6 Sep. 2016].
Umsl. (n.d). Scrum. [Online] Available

at:http://www.umsl.edu/~sauterv/analysis/6840_f09_papers/Nat/Agile.html#Scrum [Accessed 03
September 2016]
70
Volere Requirements Resources. 2016. Volere Requirements Specification Template. [ONLINE]
Available at: http://www.volere.co.uk/template.htm. [Accessed 22 August 2016].
WaveMaker. (2016). Rapid Application Development Model | WaveMaker. [online] Available at:
http://www.wavemaker.com/rapid-application-development-model/ [Accessed 9 Sep. 2016].
WebsiteToolTester.com. (2016). Wix Review 2016: When (and when not) to use Wix!. [online]
Available at: http://www.websitetooltester.com/en/reviews/wix-review/ [Accessed 9 Sep.
2016].
Wyse, S. (2014). Advantages and Disadvantages of Face-to-Face Data Collection. [Online].

2014. Snap Surveys Blog. Available from: http://www.snapsurveys.com/blog/advantages-
disadvantages-facetoface-data-collection/. [Accessed: 1 September 2016].
Zailan. 2016. Scrum Methodology [Lecture to System Development Methods], CT046-3-2-SDM:

IS Development Methodologies Part-2.[Slideshow] Asia Pacific University. 19 July.
71

Prototype E Commerce Website PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Prototype E Commerce Website PDF

Uploaded by

Copyright:

Available Formats

CT046-3-2 System Development Method

1.0 PROJECT PLANNING 2

2.0 SYSTEM ANALYSIS 11

2.1 REQUIREMENT ANALYSIS 11

1.0 Project Planning

What are the ‘resources’ in a typical IT Project? Resource planning is important,

Figure 1.1(a) Work Breakdown Structure (WBS)

Figure 1.1(b) Gantt Chart

Figure 1.2 Waterfall Methodology

Requirements gathering is an essential part of any project and project management.

4) How do you keep all of the shop’s records?

Benefits and Setbacks of Observation

2.1 Requirement Analysis

2.2.1 Functional Requirements

This defines how this MyCloths online system is suppose to be.

Look and Feel

Cultural and Political

3.1 Conceptual Design

Figure 3.1 MyCloths Online System Use Case Diagram

Use Case Register

Actors Non Member

Alternative 1. System returns “Invalid mail” message when email input is

Exit ● Submit button is clicked.

3.1.2 Use Case Descriptions (Chai Jia Jiun)

Use Case Order List of Needed Product

Preconditions Member is login in the system

Basic Flow 1. Member is logged in into the system.

Exit ● Navigate to other button.

3.1.3 Use Case Descriptions (Chuah Siew Yiing)

Use Case Verify Order List of Needed Product

Preconditions Supplier is login and has clicked “SUP” button.

1. System retrieves Supplier’s button request.

● Navigate to other buttons

3.1.4 Use Case Descriptions (Jasmine Toh Sheau-mint)

Use Case Manage Member Delivery Order

Extends Update Website

Basic Flow 5. Staff is logged in into the system.

Post 1. Homepage is shown.

Exit ● Return page button is clicked

3.2 Object Diagram

Figure 3.2.1 Class Diagram for MyCloths Online System

3.3.1 Behaviour Diagram (Akashdeep Singh TP034684)

Figure 3.3.1 Register State Behaviour Diagram

Figure 3.3.2 Add to Shopping Cart State Behaviour Diagram

3.3.3 Behaviour Diagram (Chuah Siew Yiing)

3.3.4 Behaviour Diagram (Jasmine Toh Sheau-mint TP034709)

Figure 3.3.4 Manage Member Delivery Order State Behaviour Diagram

In this assignment students were advised to create a prototype of MyCloths website.

Diagram 4.1.1 Homepage

Diagram 4.1.2 Quick Review and Compare

Diagram 4.1.3 Product Details

Diagram 4.1.4 Sign up for non-member

Diagram 4.1.5 View cart

Diagram 4.1.6 Shopping Cart

Diagram 4.1.7 Checkout Page

Diagram 4.1.8 Receipt

Diagram 4.1.9 Where to buy

It shows the location and map of Mycloths.

It provides member some frequently asked questions to solve their doubts.

Diagram 4.1.11 Contact

Members can drop by messages for inquiries.

Diagram 4.1.12 Update Account Information

Diagram 4.1.13 Rewards