Systems Analysis and Design | Assignment-1

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

1SYSTEMS ANALYSIS AND DESIGN
Table of Contents
Question 3:.................................................................................................................................2
Agile Philosophy of the Software Development:...................................................................2
Waterfall Philosophy of the Software Development:............................................................4
Question 4:.................................................................................................................................5
Question 5:...............................................................................................................................16
Bibliography:............................................................................................................................18

2SYSTEMS ANALYSIS AND DESIGN
Question 3:
For the purpose of software development, both of the agile and the waterfall methods
of software development are used widely. Here a contrast and a comparison are done between
these software development methodologies for developing the application for the St. John
Ambulance.
Agile Philosophy of the Software Development:
The agile philosophy of the software is comparatively more than the software
development frameworks. The agile software development methodologies include various of
important approaches regarding the software development. Under these approaches the
requirements and the solutions are evolved. The agile method of software development is
actually centered around the main idea of iterative development (Alahyari, Svensson and
Gorschek 2017). The main value that is provided by the agile software development is that it
enables software development team to deliver the value in much faster way while not
compromising with quality. Also, in this aspect, the project team achieves a greater aptitude
regarding the respond to any type of changes. Within the agile method of software
development, the Kanban and the Scrum are the mostly used technology for the software
development purpose.
As mentioned above, the Scrum and the Kanban is the mostly used technique in agile
software development methodology (Hiekata et al. 2016). Rather than these two, the other
techniques that are used in this context are the lean, crystal, extreme programming, dynamic
system development method and feature driven development.
While considering the agile methodology of software development the developers
archives several of strengths of choosing this software development methodology

3SYSTEMS ANALYSIS AND DESIGN
(Abrahamsson et al. 2017). The main strengths of using the agile software development
methodologies are the:
 This software development methodology improves the satisfaction of the customer by
a rapid and continuous delivery of the projected software.
 The frequency of delivering the software increases while the agile software
development methodology is used.
 While the agile method of software development is selected the face to face
conversation is mainly used which is the best way of communication. In this way no
communication related issues occur in the project (Hiekata et al. 2016).
 Also, through the use of agile software development method close cooperation is
achieved among the developers and the project clients, which helps to clear any type
of doubts regarding the project.
 Through this way, easy adoption can be achieved for any type of changing
circumstances.
 Any type changes in the last stage of developments can be handled easily through the
use of agile methodology of software development (Alahyari, Svensson and Gorschek
2017).
With the strengths, the agile software development methodology also faces some
critical weaknesses. These are the:
 Handling the large projects using the agile software development methodology is
quite difficult as calculation of the required effort at the very beginning of software
development life cycle is hard.
 In agile methodology of the software development there is lack of emphasis regarding
the documentation and the designing process (Abrahamsson et al. 2017).

4SYSTEMS ANALYSIS AND DESIGN
 While using the agile methodology the project can get off the track if the project
client is not sure about the outcome of the project.
The agile methods of the software development are very much suitable for such
application which requires the development in a rapid pace. Therefore, if the project of St.
John Ambulance requires a rapid development, then they can consider the agile methodology.
Waterfall Philosophy of the Software Development:
The waterfall model is another important method that is used for the software
development purposes. In fact, the waterfall model was the first ever introduced model for the
software development purposes. The waterfall philosophy of the software development is
very much popular as it very easy to understand and use (Chari and Agrawal 2018). In this
model, each of the phase needs to be completed before execution of the next stage can be
performed and there is no overlapping among each of the phases. In the waterfall model of
software development, the overall process of the software development is divided within
several of phases and outcome of each of the phases is used for the input of the next phase.
The main techniques that is used for waterfall model of software development are the
V-model and the Spiral model.
Compared with the agile philosophy of the software development the waterfall
philosophy of the software development does have also several of strengths (Steinke et al.
2018). The main strengths of the waterfall software development methodology are the:
 The clear structure of the waterfall model is one important advantage of it.
 Through the waterfall model of software development, end goal can be determined
very early.
 Information is transferred very wisely in this model.

5SYSTEMS ANALYSIS AND DESIGN
Some of the weaknesses are also associated with the current waterfall model of
software development. The main disadvantages of the waterfall model are the:
 Making changes in the already completed phases are extremely difficult for the
waterfall methodology (Hiekata et al. 2016).
 In this type of software development method, the client is always excluded from the
active involvement in the project.
 There is a huge delay in the testing until after completion.
The waterfall model of software development is very much suitable when the project
uses plan driven model. Thus St. John Ambulance can consider the waterfall model if their
targeted application uses a plan-driven model.
Question 4:
Purpose of Chosen Application: Technological changes in the recent past years has forced
the organizations to change its business process. Along with that increase in capacity and
popularity of mobile devices, is now forcing most of the organization to rethink about mobile
presence. St John Ambulance uses geo location services for providing their courses. The use
of geo location so vital that user have to look for courses available near to them before
booking one. Mobile application has proven to be the best technology for applying the geo
marketing strategy that St John Ambulance is using for courses. Mobile applications are more
popular and effective. In spite of being small, mobile application can provide great
interaction features as well mobiles are more used than desktop devices. The services that St
John Ambulance is providing to their customers can be easily accessed through the mobile
applications. More application users will mean for St John Ambulance more brand
recognition and loyal customers.

6SYSTEMS ANALYSIS AND DESIGN
In today’s technological era, customers are shifting their thoughts rapidly. But one
thing customers are not changing so frequently is their opinion about the mobile applications.
Currently, big organizations are creating their websites to generate awareness among the
customers. But most of their users and sales are coming through mobile applications. Users
can easily use the mobile applications to check for their courses, purchase medical kits or
donate money. They do not have to wait for a browser to open the website of St John
Ambulance. This mobile application can be a great opportunity for St John Ambulance to
stand out from the crowed. Its competitors are still using the traditional websites to
communicate with customers. A new trend is always a great factor in increasing awareness
and build brand recognition. If St John Ambulancesuccessfully build this mobile application,
current and potential both customers will be accessing a new way of communicating with St
John Ambulance as well as in this industry.
So, the main purpose of the proposed application is building brand recognition,
increase in medical kit sales, promote donations as well as improving geo location-based
course offerings.
Stakeholders: The application will mainly be developed for customers. Therefore, the
application will be user centric. However, it is also essential to make sure that application is
monitored and controlled by a person who can track potential threats to the application.
Customers are the stakeholders has less power over the application and less internet
also. Therefore, they come under the category of monitor in the stakeholder map. Customers
will be using the application for three major operation such as donations, course booking and
product purchase. Customer can also contact support team, get advice, involve in
volunteering and many more. However, those secondary operations will be done manually.
Almost ninety percent of the interactions will be associated with the three major operations.

7SYSTEMS ANALYSIS AND DESIGN
In order to use those service, customer have to validate him/herself. Registration and login
procedures will be there for completing that operation. Customers are the primary source of
income and they have a great impact on the profit St John Ambulance makes. They will not
have any power over how the application will be developed or maintained but their feedbacks
will be used as a reference.
Administrator of the system is another user of the system. Admin is not a regular user
who uses the application service. Rather he/she is the person who manages the services.
Admin tracks and control the flow of information. Admin has the power to stop the
application server is potential threat is sensed. Admin has more power and less interest.
Admin can manage the customers. If any customer is caught doing suspicious activities,
admin can block that customer’s account.
Functional and Non-Functional Requirements: Functional requirements of the system are
as following.
i. Authentication: System must authentication its users before allowing them to
the system. Authentication is the process of verifying the user through
credentials stored in the system. User will provide the email address and
password stored in the application into login form. After user submit the login
form, the combination of email and password will be passed to server. In
server, system will try to match the same combination of password and email
against stored users. If match is successful, then user authentication will be
successful, if not matched then user will be shown error.
ii. Authorization: Authorization is known as the process of checking user
privileges for requested information or operation. Each user will be allowed to
access set of information and functions. Taken as an example, a user can

8SYSTEMS ANALYSIS AND DESIGN
access history of transactions of that user only. Authorization levels are
assigned to the user during registration process. The user registers through the
application will get authorization level of normal user. Admin will get their
authorization from the service providers. Authorization maintains the data
integrity of the system.
iii. Product Presentation: Customer can purchase medical kits from the
application. Under the menu link called shop, all the category of products that
St John Ambulance sales will be listed. Some of the featured products will be
listed under that category. User can choose to check the product details or add
product directly to cart. Clicking on a category will open the list of products
under that category. In order to purchase a product, user have to add that
product to basket. In the list of products, product name, image, price and add
to product option will be visible for each product. If user opens the product
then all the details like in stock, add to basket, short description, detailed
description, about and many more details will be available on the screen.
iv. Manage Basket: User can manage the basket information. The quantity of
products in the basket can be increased or decreased. User can also remove a
product from the basket. The cost of chosen products will automatically
change when a user alter the basket data. If user wants to remove all the
products from the basket then ‘empty basket’ button can be clicked. This will
delete all the chosen products from the basket.
v. Donations: User can donate money as charity to St John Ambulance. There
will be two categories donations such as single time and monthly donations.
Single donations will have three default values such as 10, 20 and 40 pounds.
User can also user choose amount other than default ones. In order to donate,

9SYSTEMS ANALYSIS AND DESIGN
user have to check some of the things mentioned in comment. I terms of
monthly donation, user can choose between 5, 10 or 20 pounds. Custom
donation amount is also available here. No terms have to be checked for
monthly donations. User do not need to login to application in order to donate.
vi. Payment for Order, Course or Donations: Once, user is satisfied or
confirmed with the selected order, user can proceed to pay for the order. One
condition that will be applied is that user cannot pay for the selected items
unless user is logged in. For the payment, user can choose one of the many
methods provided in the list. The organization will use third party payment
services for this purpose.
vii. Course Booking: User can see the list of the courses offered by St John
Ambulance. St John Ambulance offers courses based on the location service.
User can also find courses near him/her by typing the location details.
Non-functional requirements of application are as following.
i. Security: Security is primary feature of this application. As the system will be
completing transactions and store customer payment details, it is necessary to
make the application secure. If any cyber-criminal get access to core data of
the system, data can be misused. System security is indirectly related to
customer loyalty also. If users are not feeling secure while accessing the
application they may not return this organization. Along with that, system
server should be capable of handling DDoS attacks.
ii. Usability: Usability of the system refers to many things such as learnability,
user interaction and many others. The application should have a consistent
navigation structure that can provide a way to user to access main pages. The
usability of the system can be increased by preventing the user from doing any

10SYSTEMS ANALYSIS AND DESIGN
mistake such as. Application can check for password strength and prevent the
user from registering that password.
iii. Accessibility: Accessibility can be one of the greatest features of the system if
properly maintained. Administrator must identify the time period when lowest
number of users are accessing the system. That time must be chosen for taking
the server down for maintenance purposes. Moreover, the system should be
designed such as a way that it can accessed in any size of mobile device
screens.
Figure 1: Context Diagram
(Source: Created by Author)

11SYSTEMS ANALYSIS AND DESIGN
Figure 2: Level 1 Data Flow Diagram
(Source: Created by Author)

12SYSTEMS ANALYSIS AND DESIGN
Figure 3: Level 2 Data Flow Diagram on Product Shop
(Source: Created by Author)
Level two diagram has been created based on user purchasing product. Here medical
equipment is referred as the product. User chose product to add to cart, application customer,
orders and products data object to complete this process. Customer data object is used to
check user authorization. Orders object is used to create a new order. Products object is used
to get product and price related details. If user update basket then only the OrderedProducts
object is updated which store the ordered products details such as quantity and cost. Then for
checkout process, orders data object is used to update orders.

13SYSTEMS ANALYSIS AND DESIGN
Figure 4: Use Case Diagram for User Management
(Source: Created by Author)

14SYSTEMS ANALYSIS AND DESIGN
Figure 5: Use Case Diagram for Purchase Product
(Source: Created by Author)

15SYSTEMS ANALYSIS AND DESIGN
Figure 6: Entity Relationship Diagram
(Source: Created by Author)

16SYSTEMS ANALYSIS AND DESIGN
Question 5:
Understanding both the structural and behavioural pattern of the system is very
important for application development. Proposed diagram has provided the dynamic and
static elements of the system perfectly. The UML use case diagrams shows how the end user
will be interacting with the application. Dataflow diagrams has shown dynamic data
requirements. On the other hand, context and entity relationship diagram are for showing the
static data requirement of the application. Showing the information is half of the work. The
other half is verifying that proposed data is valid.
In terms of context diagram, the information shown to user and data input from user
has been shown. This diagram shows application in the centre and user at outside. This
diagram does not provide flow of information in sequence. The data coming from users are
information required for registration, login details, donation details, selected course or
product and selected volunteer options. The system will show the available products, basket
details, advices and many other information to the system. All these information flow to and
from user and application will be fetched from database or store into database. Any static
information is not mentioned in the system.
In order to show the data flow in a much dynamic and sequential manner, the data
flow diagrams has been generated. Level one data flow diagram consists of the high level of
information. It does not concern over the inner workings of the application. It shows high
level view of the data flow. As per the level one diagram, user registers first into application
and then login to access the core functionality. In terms of registration, details are store in
database and for login details are fetched from the database. After that user can purchase
product or course from the system. In order to make a purchase, application fetched the
course or product details to show options to user. Once purchase list is confirmed, user makes
payment. As logins is done as per data flow sequence, the user does not need to worry about

17SYSTEMS ANALYSIS AND DESIGN
authentication any more. In the payment process, order data object is used to update status of
order and fetch total amount details. User donation store details in donations data object.
Only thing that can be better in the diagrams is adding sequence diagram that can
show more dynamic nature of the application. It can show communication between the
objects of the application.

18SYSTEMS ANALYSIS AND DESIGN
Bibliography:
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Alahyari, H., Svensson, R.B. and Gorschek, T., 2017. A study of value in agile software
development organizations. Journal of Systems and Software, 125, pp.271-288.
Bhuiyan, M., Haque, F., Shabnam, L., Mekami, H., Benabderrahmane, S., Bounoua, A.,
Taleb-Ahmed, A., Torii, I., Ohtani, K., Niwa, T. and Ishii, N., 2018. Integration of
organisational models and UML Use Case diagrams. Journal of Computers, 13, pp.1-18.
Chari, K. and Agrawal, M., 2018. Impact of incorrect and new requirements on waterfall
software project outcomes. Empirical Software Engineering, 23(1), pp.165-185.
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.
Hiekata, K., Mitsuyuki, T., Goto, T. and Moser, B.R., 2016, October. Design of Software
Development Architecture Comparison of Waterfall and Agile Using Reliability Growth
Model. In ISPE TE (pp. 471-480).
Hoda, R., Salleh, N. and Grundy, J., 2018. The rise and evolution of agile software
development. IEEE software, 35(5), pp.58-63.
Kuitunen, M., 2019. Cross-Platform Mobile Application Development with React
Native (Bachelor's thesis).
Kumar, N.A., Krishna, K.H. and Manjula, R., 2016. Challenges and best practices in mobile
application development. Imperial Journal of Interdisciplinary Research, 2, p.12.

19SYSTEMS ANALYSIS AND DESIGN
Kurtanović, Z. and Maalej, W., 2017, September. Automatically classifying functional and
non-functional requirements using supervised machine learning. In 2017 IEEE 25th
International Requirements Engineering Conference (RE) (pp. 490-495). IEEE.
Lindsjørn, Y., Sjøberg, D.I., Dingsøyr, T., Bergersen, G.R. and Dybå, T., 2016. Teamwork
quality and project success in software development: A survey of agile development
teams. Journal of Systems and Software, 122, pp.274-286.
Mabelo, P.B., 2020. How to Manage Project Stakeholders: Effective Strategies for Successful
Large Infrastructure Projects.
Mitsuyuki, T., Hiekata, K., Goto, T. and Moser, B., 2017. Evaluation of project architecture
in software development mixing waterfall and agile by using process simulation. Journal of
Industrial Integration and Management, 2(02), p.1750007.
Morgan, J.D., 2018. Applying 1970 Waterfall Lessons Learned Within Today’s Agile
Development Process.
Olsina, L. and Becker, P., 2018. Linking business and information need goals with functional
and non-functional requirements. In Proceed. of the XXI Conferencia Iberoamericana en
Software Engineering (CIbSE’18), Bogotá, Colombia, Published by Curran Associates (pp.
381-394).
Panhale, M., 2016. Beginning hybrid mobile application development. Apress.
Rahman, M.M., Ali, M., Malik, N., Ahmad, M.S. and Asmi, F., 2017. Essential Skills for
Project Stakeholders Identification: Sustainability Perspective. International Journal of
Business and Social Research, 7(08), pp.43-55.

20SYSTEMS ANALYSIS AND DESIGN
Steinke, G.H., Al-Deen, M.S. and LaBrie, R.C., 2018, September. Innovating Information
System Development Methodologies with Design Thinking. In Titel: Proceedings of the 5th
Conference in Innovations in IT, Volume Nr. 5. Bibliothek, Hochschule Anhalt.