Information System Analysis and Design Project: Best and Less Clothing

Verified

Added on  2023/06/05

|15
|2091
|423
Project
AI Summary
This project provides a comprehensive analysis and design of an information system for Best and Less clothing retail. It begins with an executive summary outlining the project's scope, which includes analyzing functional requirements using the FURPS methodology, identifying stakeholders (internal, external, operational, and executive), and gathering user requirements through questionnaires. The project details the development of a domain model class diagram to represent entities and attributes. It includes brief and fully developed use case descriptions, alongside use case diagrams, activity diagrams, and sequence diagrams to illustrate the flow of activities and messages within the system. The analysis covers functional and non-functional requirements, a detailed stakeholder analysis, and concludes with a discussion of the system's design and functionality.
Document Page
Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s Note
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
1
SYSTEM ANALYSIS AND DESIGN
Executive Summary
For the development of the information system for Best and Less clothing the functional
requirement of the organization is analysed and the stakeholders associated with the project is
identified for management of the external entities. The functional requirement is analysed
with the application of FURPS methodology and the internal and the external operation of the
stakeholders are identified for the development of the information system. The questionnaire
is prepared for the targeted group of users for the identification of their requirement and
develop the information system according to their needs. The entities and attributes involved
for the management of the flow of information should be identified for the development of
the class diagram. The users involved in the process should be identified for the development
of the use case. A brief and detailed use case description is created for the demonstration of
the flow of activities. An activity diagram and sequence diagram is created for demonstration
of the flow of message between the different objects.
Document Page
2
SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction................................................................................................................................3
Functional and Non Functional Requirement500......................................................................3
Identification of Stakeholders....................................................................................................4
Questionnaire.............................................................................................................................4
Domain Model Class Diagram...................................................................................................5
Brief Use case description..........................................................................................................6
Use case diagram........................................................................................................................8
Fully developed use case description.........................................................................................8
Activity Diagram......................................................................................................................11
System Sequence Diagram.......................................................................................................12
Conclusion................................................................................................................................12
Reference..................................................................................................................................13
Document Page
3
SYSTEM ANALYSIS AND DESIGN
Introduction
The development of the information system for Best and Less clothing would help the
users and the employees of the organization to reduce the effort. The requirement of the
information system is analysed based on the functionality, usability, reliability, performance
and security requirement. The stakeholders associated with the development of the
information system are identified and are grouped into internal, external, operational and
executive stakeholders. The questionnaires prepared for the stakeholders are kept close ended
such that information is collected from them and helps in development process and reducing
the errors in the system development process.
Functional and Non Functional Requirement500
For the identification of the functional and non-functional requirement for the
implementation of the information system for Best & Less clothing retail store are given
below:
Functionality – The information system should be used as a platform for the user and
the management team for improvement of the business process and reduce the manual effort
of the employees. It improves the scalability and security of data and makes the data available
from remote location.
Usability – The system should have a simple user interface and the user should not
face any difficulty while using the information system. The system should be responsive and
message should be displayed returning feedback for the wrong input of the user.
Reliability – The user should be guided to the purchase page and navigation panel
should be added such that user can return to the previous page. Different product and service
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
4
SYSTEM ANALYSIS AND DESIGN
should be offered to the customer for increasing the loyalty of the customer and attract them
to use the information system.
Performance – The server performance should no get down with the increase in the
number of user and more number of users can be handled at a time. The response time of the
servers should be kept minimum such that user does not have to wait for a long time.
Supportability – Email and message service should be enabled for providing support
to the user. The user feedback should be taken from them and improvement should be done in
the information system for increasing the sustainability.
Identification of Stakeholders
The stakeholders are identified according to Internal, external, operation and
executive. The following is the list of stakeholders:
Internal Operation Internal Executive
Management of the business infrastructure Manager
Management of the inventory Stock Accountant
Management of the Sales Sales Personnel
External Operation External Executive
Insurance Company Insurance agents
Networking Network Administrator
Advertisement Promotional agents
Document Page
5
SYSTEM ANALYSIS AND DESIGN
Questionnaire
There are different data gathering activities involved for finding the information that are
essential for the development of the information system. The following set of questionnaires
is developed for finding the requirement and an interview should be arranged with the
stakeholders and the questionnaire should be distributed among the for finding the
requirement.
ď‚· What is the normal procedure followed for collecting the orders from the customers?
ď‚· How does the staffs confirms the availability of the order given by the customer?
ď‚· How do you record the orders that are given by the customer?
ď‚· How do you differentiate the unprocessed orders and the new orders placed by the
customer?
ď‚· How do you records the details of the orders that has been already paid?
ď‚· What are the new things that would help you for the management of the current
business process?
ď‚· What is the method followed by your organization for delivering the products to the
customers door step?
ď‚· How to you maintain a track on the orders that are needed to be delivered urgently to
the customer?
ď‚· What procedure do you follow to maintain a good relationship with the customers?
Document Page
6
SYSTEM ANALYSIS AND DESIGN
Domain Model Class Diagram
Brief Use case description
Use Case Brief Use Case Description
Approves The customer needs to register and into the information system for using the
system
Add
Account
The administrator s given the permission to add new accounts
Login The customer can login into the system for search for items and place order
Register The details of the customer needs to be provided for registering into the
information system.
Search
Product
The search option is used for searching available products from the database
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
7
SYSTEM ANALYSIS AND DESIGN
Places
Order
The order is placed by adding item in the cart and completion of the
payment options
Change or
cancel order
The customer can cancel or change order and if the service is not
satisfactory to the customer.
Check
Order status
The status of order is updated in the database and shared with the customer
for viewing the details
Make
Payment
The customer can choose different option for payment for getting the
product delivered.
Sales Visit The sales employees makes sales visit for checking the quality and reduce
the complaint of the customers.
Check in The product is verified and marked after the completion of the check and
delivered to the customer.
Create order
summary
report
The summary report is created and management of the stocks and finding
the returns from the business.
Publish
report
The accountant is responsible to manage the supply chain and the inventory
and publish report and upload in the database
Generate
report
The data residing in the database of the information system should be used
for generating report and management of the information and maintain a
track on the growth of the business.
Document Page
8
SYSTEM ANALYSIS AND DESIGN
Use case diagram
Fully developed use case description
Use Case
Diagram:
Best & Less Information System
Scenario: To sell cloths and accessories
Triggering event: To record the details of the inventory and the customers in the
information system
Brief Description: Add new customer, product details in the information system and
eliminate the manual procedure
Actor: Stock accountant, Manager, Customer, Sales person
Stakeholders: The staffs and the customers are the main stakeholders identified for
the development of the information system.
Preconditions: The availability of the products is important for the working of the
information system.
Postconditions: The user must have knowledge of using a information system and the
Document Page
9
SYSTEM ANALYSIS AND DESIGN
interface must be usable
Flow of Activities Actor System
The registration details are filled
by the customer for registering
into the system
The user details are stored in the
information system
A new account is created in the
system
The product are viewed by the
customers after logging into the
account
The username and password is
validated for logging into the
account.
Error message is displayed for
invalid input.
The products details should be
checked by the customer before
placing order
The system returns the details of
the product.
The product that are unavailable
are displayed to the user.
The order details are viewed by
the user
The details of the order are
stored in the information system
and displayed to the user
The items that are unavailable
are listed
Payment process is completed
by the user
The order is dispatched after the
completion of the payment
process
The total cost is calculated
including the delivery and the
taxes
Payment is validated from the
accounts department
An invoice is generated after
completion of the verification
Approval of the payment The invoice is stored with the
details of the product
The invoice is printed and
attached with the product during
delivering to the customer
The packaging staff checks the For ensuring delivery the
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
10
SYSTEM ANALYSIS AND DESIGN
order before dispatching verification of the order is
necessary
A ID is generated and attached
with the order for tracking the
details.
A delivery schedule is created The delivery is done
maintaining the schedule
The final details are recorded for
management of the delivery
Excepted
Condition
1. Low or no internet connection
2. Unavailability of the customer details
3. Database corruption.
Document Page
11
SYSTEM ANALYSIS AND DESIGN
Activity Diagram
Document Page
12
SYSTEM ANALYSIS AND DESIGN
System Sequence Diagram
Conclusion
It can be concluded that for the development of the information system an analysis
should be done on the requirement and different procedures should be used for the
identification of the requirements. For the development of the use case a brief and detailed
use case description is created that helps in identifying the flow of information between the
actors and the user cases. The triggers and the alternative paths that can be used for getting
the desired outputs can also be found from the use case. The sequence diagram and the
activity diagram is create for the identification of the exchange of message between the
different objects necessary for the development of the information system.
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
13
SYSTEM ANALYSIS AND DESIGN
Bibliography
Azar, A.T. and Vaidyanathan, S. eds., 2015. Chaos modeling and control systems
design (Vol. 581). Germany: Springer.
Chopra, A.K., 2017. Dynamics of Structures. Theory and Applications to. Earthquake
Engineering.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John wiley & sons.
Eason, K.D., 2014. Information technology and organisational change. CRC Press.
Endsley, M.R., 2016. Designing for situation awareness: An approach to user-centered
design. CRC press.
Hollnagel, E., 2017. FRAM: the functional resonance analysis method: modelling complex
socio-technical systems. CRC Press.
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education
India.
Oinas-Kukkonen, H. and Harjumaa, M., 2018. Persuasive systems design: key issues, process
model and system features. In Routledge Handbook of Policy Design (pp. 105-123).
Routledge.
Pedrycz, W., 2016. Granular computing: analysis and design of intelligent systems. CRC
press.
Urquhart, C. and Fernandez, W., 2016. Using grounded theory method in information
systems: the researcher as blank slate and other myths. In Enacting Research Methods in
Information Systems: Volume 1 (pp. 129-156). Palgrave Macmillan, Cham.
Document Page
14
SYSTEM ANALYSIS AND DESIGN
Vaishnavi, V.K. and Kuechler, W., 2015. Design science research methods and patterns:
innovating information and communication technology. Crc Press.
Valacich, J., George, J. and Hoffer, J., 2014. Essentials of systems analysis and design.
Prentice Hall Press.
chevron_up_icon
1 out of 15
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]