Detailed System Analysis and Design Report: School Supplies Pty LTD

This report presents a system analysis and design for School Supplies Pty LTD, a stationary shop in Brisbane. The report begins with an essay and memo discussing the business's operations, focusing on the high-volume back-to-school period and the need for an adaptive software system. The essay explores different software development life cycle (SDLC) approaches, including Scrum, Extreme Programming (XP), and Feature Driven Development (FDD), recommending Scrum as the best solution. The memo addresses the design of the Human-Computer Interface (HCI) for the online ordering system, emphasizing user-friendliness and consistency. The report then moves into modeling and diagramming, including an event table, a use case diagram, and use case descriptions to capture the system's behavior. A domain model class diagram and a class diagram are also provided to illustrate the system's structure and relationships. The report concludes with a bibliography of relevant sources.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Part A: Essay and Memo 2
Question 1: Essay 2
Question 2: Memo 3
Part B: Modelling and Diagramming 4
Question 3: Use Case Modelling 4
a. Event Table: 4
b. Use Case Diagram: 5
c. Use Case description: 6
Question 4: Domain Modelling 7
a. Domain Model Class Diagram 7
b. Class Diagram: 7
Bibliography: 8

2SYSTEM ANALYSIS AND DESIGN
Part A: Essay and Memo
Question 1: Essay
There is a stationary shop in Brisbane that goes by the name of school supplies Pty
LTD and is owned by Gerry Lane. Gerry Lane is the ex-school principal who bought the
School supplies in 2012 and has quite a reputation among the people of brisbane. The busiest
time for the School supply is from the month of November to February when annual Back to
School process goes on, when around 4500 school make their order through the School
supplies, in which they have to packet and delivered at a prescribed address in a hurry.
It would not be possible to send this many chunk of material to various school and
homes where the address is given. Therefore, an Adaptive Developmental software is used to
execute the long and tedious process of taking the order from the parents and sending it to the
respective address along with the verification of the payment that needs to be done for these
books. The most useful part of the technology is its adaptive and easy to modify feature. This
is done due to the different three phases in adaptive life cycle of development which are to
first speculate, then collaborate and then learn.
The approach of the Scrum is best for dealing with management of the development
of processes of the system. It is the basic need for application of the protocols for the
industrial application. There is no such predefined area for the implementation of this
software. The philosophy of the Scrum is that the team is able to change the application
process of the software without changing the core software of the system. It goals have been
around developing its technical as well as environmental aspect. This is going to help the
management to modify any situation with that of the system without facing any complexities.
Scrum, if utilised properly can be engaging for improvement of various engineering methods.
Scrum master is the one who be looking after the function of it in a system.

3SYSTEM ANALYSIS AND DESIGN
Because of the occurrence of large amount of problem, there is a surge in extreme
programming. XP has phases like Planning, exploration, maintenance and release. Although,
all the different kinds of purpose and task have been defined by its numerous responsibilities
and roles, there is a constant focus in the improvement of innovation of software that are
ought to be successful. The basic design of XP has been done keeping in mind medium and
small enterprises. The limitation for the application of XP is when the size of group is around
three to five.
The Feature Driven development (FDD) as the name suggest is an innovative and
agile methodology that are used in the different development system. They are governed by
the five process. Those are an accumulation of different techniques and roles. It is used to
modify any developmental system according to the desire of the operator and can be helpful
in amending the progress of a project. The approaches of FDD is being proven to be very
effective in many industry and the software.
As per the requirement of school supplies Pty LTD, the scrum SDLC approach would
be the best solution for developing the system. The scrum would allow the users to review the
system and get familiar with it. The system must be user centric rather than business centric,
therefore the scrum can provide the best final product.
Question 2: Memo
Memo
To: Owner Gerry Lane
From: << Student >>,

4SYSTEM ANALYSIS AND DESIGN
Date: 13-09-18
Sub: Providing various ways for design of Human Computer Interface for this Online
Ordering system.
The school supplies was bought by Gerry Lane in 2012.He has always worked for the
betterment of the society and has been respected for that in whole of Brisbane. The most
happening time of the year for the School Supplies store is during the process of Back To
School which is often done from November to February. This is the time when all the
student return back to school and it is during this time that order for over 4500 schools is
placed in the School supplies. The amount of this book has to be given to all the children
and teacher onto their respective addresses. The school supplies has allowed different and
effective ways to place an order for the stationary items. Parents can place the order
through the telephone line as well as through the use of internet directly from there portal.
The reason as to why the school supplies has immense growth in Brisbane is because of
their timely delivery mechanism. The process of the timely delivery is done because of an
online portal of the school supplies. Analytical aspect have to be kept in mind while
devising such a network of ordering. The interface should be user friendly and should not
be very complex for any user. Consistency along with simplicity and its structure are the
core strength of a successful system. Software layout should be such that a large number of
user can efficiently place an order on the system without any lagging. The technical aspects
of the software should not be visible to the user and should not make the system any less
interesting, The communication aspect should be kept to a minimal without too much stress
on such aspect which might be of no relevant in the future. The customer's satisfaction is

5SYSTEM ANALYSIS AND DESIGN
the utmost important aspect of this system. Interaction loop should be encouraged for
proper implementation of the system. It is the flow of data from the system to the user.
Part B: Modelling and Diagramming
Question 3: Use Case Modelling
a. Event Table:
Event Event
Type
Trigger Source Activity/
Use
Case
System
Response/Output
Destination
Order
placing
External Sales Parent Order
Placeme
nt
The parents will
make an order to
buy products
Parent
User
registra
tion
External New user End user Create
Online
Account
The end user will
provide the
required details to
register into the
system
End User
User
login
External New user
authenticati
on
End User Access
Online
Account
The end user will
input the login
credentials for
logging into the
system
End User

6SYSTEM ANALYSIS AND DESIGN
Receiv
e
Invoice
External Billing End User
Order
Get
Invoice
The system will
automatically
create the invoice
for each order
Parent
Transfe
r
capital
for
order
External Accounts Parent Online
Payment
The customer will
make the online
payment through
the payment
gateway or wallet
Parent
The
ordered
product
will be
deliver
ed to
the
custom
er
Internal Delivery Warehou
se
Courier After the order is
ready, the system
will generate the
consignment note
Parent

7SYSTEM ANALYSIS AND DESIGN
b. Use Case Diagram:
Figure 1: UML Use Case Diagram
(Source: Created by Author)
The use case diagram has been used for capturing the behaviour of the school supplies
Pty LTD system. The use case diagram illustrates that total five type of users will be
accessing the system. Most of the access options are available for the parents. The other users
will monitor specific or all activities within the system. Parents have to access online account
to place order and make payment.
c. Use Case description:
Name Create Online Account
ID UC_CUS_01

8SYSTEM ANALYSIS AND DESIGN
Description The end users will register into the system by providing the essential
data
Actors Parent
Organizational
Benefits
The increase in customer will result into more sales
Frequency of use Every time a new user visits the system for placing order needs to
register
Triggers Order placement from unregistered customer
Preconditions Customer should not be registered
Postconditions The customer will receive login credentials
Main Course 1. The user goes to register page
2. The system shows a form with input sections and buttons
3. The user enters the authentic data into the form and submit it
4. The system checks whether the data are as per predefined rules
5. The system store the user data into the database
Exceptions EX1: The delivery gets cancelled due to natural calamities
1. The admin will record the delivery details and manually process
them after situation comes under control

9SYSTEM ANALYSIS AND DESIGN
Question 4: Domain Modelling
a. Domain Model Class Diagram
Figure 2: Domain Model Class Diagram
(Source: Created by Author)
The domain model class diagram shows that total eight number of classes will be used
for the system. Each of the classes has its own attributes that can define its characteristics.
b. Class Diagram:
Figure 3: Class Diagram
(Source: Created by Author)
The class diagram is completely based on two attributes school and client. The client
means the parent admission their children to the school.

10SYSTEM ANALYSIS AND DESIGN
Bibliography:
Burman, E., 2015. Agile in action: Hybrid methodologies in practice.
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.
Chowdhury, A.Z.M., Bhowmik, A., Hasan, H. and Rahim, M.S., 2018. Analysis of the
Veracities of Industry Used Software Development Life Cycle Methodologies. arXiv preprint
arXiv:1805.08631.
Chowdhury, A.Z.M., Bhowmik, A., Hasan, H. and Rahim, M.S., 2018. Analysis of the
Veracities of Industry Used Software Development Life Cycle Methodologies. arXiv preprint
arXiv:1805.08631.
Cunha, A., Garis, A. and Riesco, D., 2015. Translating between Alloy specifications and
UML class diagrams annotated with OCL. Software & Systems Modeling, 14(1), pp.5-25.
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).
Gold, B. and Vassell, C., 2015, November. Using risk management to balance agile methods:
A study of the Scrum process. In Knowledge-Based Engineering and Innovation (KBEI),
2015 2nd International Conference on (pp. 49-54). IEEE.
Hameed, A., 2016. Software Development Lifecycle for Extreme Programming.
International Journal of Information Technology and Electrical Engineering, 5(1).

11SYSTEM ANALYSIS AND DESIGN
Jha, P., Jena, P.P. and Malu, R.K., 2014. Estimating software development effort using UML
use case point (UCP) method with a modified set of environmental factors. International
Journal of Computer Science and Information Technologies, 5(3), pp.2742-2744.
Kniberg, H., 2015. Scrum and XP from the Trenches. Lulu. com.
Lazar, J., Feng, J.H. and Hochheiser, H., 2017. Research methods in human-computer
interaction. Morgan Kaufmann.
Madanayake, R., Dias, G.K.A. and Kodikara, N.D., 2016. Use Stories vs UML Use Cases in
Modular Transformation. International Journal of Scientific Engineering and Applied
Science (IJSEAS)–Volume-3, Issue-1, ISSN, pp.2395-3470.
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile
software development methodologies: A comparative analysis. ACM SIGSOFT Software
Engineering Notes, 40(1), pp.1-6.
Mousaei, M. and Gandomani, T.J., 2018. A New Project Risk Management Model based on
Scrum Framework and Prince2 Methodology. development, 9(4).
Rautaray, S.S. and Agrawal, A., 2015. Vision based hand gesture recognition for human
computer interaction: a survey. Artificial Intelligence Review, 43(1), pp.1-54.
Schubert, P. and Glitsch, J.H., 2015. Adding structure to enterprise collaboration systems:
Identification of use cases and collaboration scenarios. Procedia Computer Science, 64,
pp.161-169.
Tabassum, A., Bhatti, S.N., Asghar, A.R., Manzoor, I. and Alam, I., 2017. Optimized Quality
Model for Agile Development: Extreme Programming (XP) as a Case Scenario.
INTERNATIONAL JOURNAL OF ADVANCED COMPUTER SCIENCE AND
APPLICATIONS, 8(4), pp.392-400.

12SYSTEM ANALYSIS AND DESIGN
Wu, H., 2017, September. MaxUSE: a tool for finding achievable constraints and conflicts
for inconsistent UML class diagrams. In International Conference on Integrated Formal
Methods (pp. 348-356). Springer, Cham.