Detailed Systems Analysis and Design Project for a Toy Ordering System

This project undertakes a comprehensive systems analysis and design for a toy ordering system, addressing the challenges faced by a family-owned business. It begins with a planning phase, encompassing project identification, feasibility studies (technical, economic, and organizational), and the selection of the Agile SDLC methodology. The analysis phase details functional requirements (registration, login, search, order, receipt) and non-functional requirements (accessibility, integrability, extensibility, portability), alongside use case diagrams, data flow diagrams, and ER modeling. Finally, the design phase covers architecture and data storage design, specifically proposing a relational database approach. The project incorporates relevant literature to support the proposed design and analysis, providing a complete solution for the assignment.

Running head: Systems Analysis and Design
SYSTEM ANALYSIS AND DESIGN
Name of the Student
Name of the University
Author Note

1SYSTEMS ANALYSIS AND DESIGN
Table of Contents
Part 1: Planning Phase: -............................................................................................................2
Project identification:.............................................................................................................2
Feasibility studies:..................................................................................................................3
SDLC development methodology:.........................................................................................3
Work plan:..............................................................................................................................4
Part 2: Analysis Phase: -............................................................................................................5
List the functional and nonfunctional business requirements for the system:.......................5
Use cases:...............................................................................................................................7
Model Processes (Data Flow Diagramming):........................................................................8
Model data (ER modeling).....................................................................................................9
Part 3: Design Phase:...............................................................................................................10
Architecture Design:............................................................................................................10
Data Storage Design:............................................................................................................10

2SYSTEMS ANALYSIS AND DESIGN
Part 1: Planning Phase: -
Project identification:
Project Title: Information System Management.
Project Description:
Mr. and Mrs. Khan took over their family business in Riyadh. They are producing
handmade toys and deliver it across the country through a delivery service. They have many
loyal customers across the country. Few of their customer order their product by Email and
some of them are using their phone to get their product. But at the same time, they are facing
several issues. They find out that their competitors using an advanced system that provides
the same products in less price and provides better delivery options. Mr. and Mrs. khan
believe that with the help of a new information system, they can make more profit and offer
better delivery options among users.
Currently, they are using a manual system where a staff take customer phone call and
write down their details in the spreadsheet such as customer name, phone number, email and
address. Then he/she goes to the shop and find the product, pack it and send it to the delivery
partner. In this scenario, customer phone is the trigger the order process. For the payment,
they are taking credit card details from the customer over the phone.
From a few months, they are facing a new problem that in holidays they are unable to
maintain the workloads and its impact on the business. Few challenges are discussed below:
 The orders are going to the wrong person.
 Orders are not delivered at time.
 Unable to handle multiple customers at a time.
 Can not provide handwritten receipt to customers.

3SYSTEMS ANALYSIS AND DESIGN
To eliminate the above problem Mr. and Mrs. Khan decided to implement a new system that
can automate the Toys ordering system. Mr. and Mrs. Khan decided to employ a system
analyst to provide few courses of actions.
Feasibility studies:
This section of this project includes the Technical Feasibility, Economic Feasibility
and Organizational Feasibility that can determine the strategies. Process and design.
Technical Feasibility:
It can measure the possibility of a specific technical solution and technical resource
availability. This study is helpful to determine the solution is practical or not. And the
importance of implementing new technology in the existing system. A system analyst
develops a prototype to determine the new system is technically feasible.
Economic Feasibility:
It helps to measure the cost-effectiveness of the project. Sometimes it can be called
cost-benefit analysis. After determining the user and requirements Mr. and Mrs. Khan can
working of economic feasibility of this project.
Organizational Feasibility:
It can measure the Mr. and Mrs. Khan has sufficient management expertise,
organizational capability to successfully implement the new system to increase the
productivity. This analysis can be done in the area. Resource sufficiency and management
prowess.
SDLC development methodology:
SDLC offers many models and methods agile methodology is most appropriate in this
organization.

4SYSTEMS ANALYSIS AND DESIGN
Agile methodology for information system development principles helps a small team
or an individual to develop a system. this methodology combines all process that can help a
developer, organization management and customers. The work process is divided into 2-4
weeks it is known as “sprints”. In this phase, a small team of developer looks after the
customer need and perform various testing. This methodology is best for this organization
because it is appropriate for a small company. in this organization speed and flexibility is
required that only agile can provide.
The benefit of agile methodology in an information system is, it can deal with the
rapid user requirement changes. With Frequent upgrades, an organization can implement a
new feature in this system.
Work plan:
ID Task
Mode
Task Name Duration Start Finish Predecessors
0 Information System
Management
18 days Fri 3/27/20 Tue 4/21/20
1 Planing Phase 3 days Fri 3/27/20 Tue 3/31/20
2 Meeting with workers 1 day Fri 3/27/20 Fri 3/27/20
3 Creating project plan 2 days Mon 3/30/20 Tue 3/31/20 2
4 Determine budget for the
project
1 day Mon 3/30/20 Mon 3/30/20
5 Approval from the owners 1 day Tue 3/31/20 Tue 3/31/20 4
6 Analysis Phase 5 days Wed 4/1/20 Tue 4/7/20
7 Identification system type 2 days Wed 4/1/20 Thu 4/2/20 5,3,4
8 Identification name of the
system
1 day Wed 4/1/20 Wed 4/1/20 5
9 Hire Software Analysist 3 days Fri 4/3/20 Tue 4/7/20 8,7
10 Developing the system 4 days Wed 4/8/20 Mon 4/13/20
11 Implement ordering system 2 days Wed 4/8/20 Thu 4/9/20 9
12 Customer payment system 2 days Fri 4/10/20 Mon 4/13/20 11
13 Customer Details recording
system
2 days Fri 4/10/20 Mon 4/13/20 11
14 Developing the Product 1 day Tue 4/14/20 Tue 4/14/20
15 Choosing programming
language
1 day Tue 4/14/20 Tue 4/14/20 13,12
16 Choosing database system 1 day Tue 4/14/20 Tue 4/14/20 13
17 Testing the Product 2 days Wed 4/15/20 Thu 4/16/20
18 Functional Testing 1 day Wed 4/15/20 Wed 4/15/20 15,16
19 Non-Functional Testing 1 day Thu 4/16/20 Thu 4/16/20 18
20 Deployment in the Market
and Maintence
3 days Fri 4/17/20 Tue 4/21/20
21 Deploy code to test servers 1 day Fri 4/17/20 Fri 4/17/20 19
22 Publish system 1 day Mon 4/20/20 Mon 4/20/20 21
23 project Closure 1 day Tue 4/21/20 Tue 4/21/20 22
T S M W F S T T S M W F S T T
Mar 22, '20 Mar 29, '20 Apr 5, '20 Apr 12, '20 Apr 19, '20

5SYSTEMS ANALYSIS AND DESIGN
Part 2: Analysis Phase: -
List the functional and nonfunctional business requirements for the system:
Functional and nonfunctional requirements can determine the system and its
component and it provides the functions that a system can perform when a user uses the
system. This section of this report provides the functional and nonfunctional business
requirements.
Functional requirements:
Registration:
To use the system, a customer needs to log in first. They need to provide their email,
phone number and essential details for the login. due to this functionality, organization can
have every user detail.
Login:
after registration, a customer or admin can log into the system. This system consists of
two login option for customer can admin. After login, a customer and admin can perform
many tasks. With this functionality, an organization can track the user activity.
Search an order:
A customer can search for a specific product by providing the toy name.
Order online:
After selecting a product, a customer can order a product by providing their card
details and address. Multiple payment options are available in the system.
Receipt generator:

6SYSTEMS ANALYSIS AND DESIGN
After payment, a user can download the receipt, this system can also send the receipt
to every user email.
Nonfunctional requirements:
Accessibility:
This system is can accessible by any person. a disabled person or any child can order
a toy by using this system.
Integrability:
This system contains many subsystems. few subsystems are helpful to handle and
manage the workloads.
Extensibility:
This system is easily extensible. A software developer can easily add new feature
when required.
Portability:
This system can perform the same when a user uses it in their mobile phone or
desktops.

7SYSTEMS ANALYSIS AND DESIGN
Use cases:
Figure 1: Use case diagram of toys management system
(Source: Created by Author)

8SYSTEMS ANALYSIS AND DESIGN
Model Processes (Data Flow Diagramming):
Figure 2: data flow diagram of toys management information system
(source: created by author)

9SYSTEMS ANALYSIS AND DESIGN
Model data (ER modelling)
Figure 3: ER model Diagram for toys management information system
(Source: Created by Author)

10SYSTEMS ANALYSIS AND DESIGN
Part 3: Design Phase:
Architecture Design:
Figure 4: Architecture Design of toy management information system
(Source: Created by author)
Data Storage Design:
There are two types of database storage formats are available. Database format and
file format. Files are mostly electronic lists of data that are developed for a specific
transaction. But a database is a huge collection of data. in the database, every data is logically
interconnected. A database management system a special type of software that can create the
populate the vast amount of data.

11SYSTEMS ANALYSIS AND DESIGN
A file data contains electronic lists of data. the example of news file format is CSV
file. In this project, Mr and Mrs. Khan using a CSV file for their old system.
There are many types of database such as relational, legacy, multidimensional and object can
be used here. The relational database is most appropriate here.
The relational database is the most popular database for this development process.
This is efficient and user friendly. This is the based-on collection of multiple tables. Every
table can have a primary key that can uniquely identify an object. Every table can be
connected with the help of foreign key in this data storage.

12SYSTEMS ANALYSIS AND DESIGN
Bibliography:
Arrey, D.A., 2019. Exploring the Integration of Security into Software Development Life
Cycle (SDLC) Methodology (Doctoral dissertation, Colorado Technical University).
Chauhan, B.D., Rana, A. and Sharma, N.K., 2017, September. Impact of development
methodology on cost & risk for development projects. In 2017 6th International Conference
on Reliability, Infocom Technologies and Optimization (Trends and Future Directions)
(ICRITO) (pp. 267-272). IEEE.
de Sousa, T.C., Kelvin, L., Neto, C.D. and de Carvalho, C.G.N., 2017. A Formal Semantics
for Use Case Diagram Via Event-B. JSW, 12(3), pp.189-200.
de Vicente Mohino, J., Bermejo Higuera, J., Bermejo Higuera, J.R. and Sicilia Montalvo,
J.A., 2019. The Application of a New Secure Software Development Life Cycle (S-SDLC)
with Agile Methodologies. Electronics, 8(11), p.1218.
Dora, S.K. and Dubey, P., 2015. Software Development Life Cycle (SDLC) Analytical
Comparison and Survey on Traditional and Agile Methodology. National Monthly Referred
Journal of Research Science and Technology, 2(8).
Rao, P.V., Kumar, V.P. and Reddy, B.P.K., 2018. Applying Agile Software Methodology for
the Development of Software Development Life Cycle Process (SDLC). Journal for
Research| Volume, 4(02).
Vachharajani, V., Vasant, S. and Pareek, J., 2016. Feasibility Study of Proposed Architecture
for Automatic Assessment of Use-Case Diagram. In Proceedings of International
Conference on ICT for Sustainable Development (pp. 97-104). Springer, Singapore.
Xiong, H., Zhang, H., Dong, X., Meng, L. and Zhao, W., 2017, September. DFDVis: A
Visual Analytics System for Understanding the Semantics of Data Flow Diagram.

13SYSTEMS ANALYSIS AND DESIGN
In International Conference of Pioneering Computer Scientists, Engineers and
Educators (pp. 660-673). Springer, Singapore.