Walking App Project: System Design, Use Cases, & Project Plan F

This document presents a comprehensive system design document and project plan for the development of a walking application, named North Head F. It includes various diagrams such as package diagrams, class diagrams, sequence diagrams, and state diagrams to illustrate the system's architecture and functionality. The report layout outlines key elements like initial conversations, goal definitions, competitive audits, user feedback, and goal reviews. The document also features a program navigation diagram and a use case diagram, detailing the app's interactive map for suggesting walking routes and nearby checkpoints. User stories are provided to capture the user's perspective and needs, focusing on features like tracking footsteps, saving frequently navigated locations, and participating in challenges. The project plan covers aspects such as project purpose, scope, risk management, resource management, team organization, project schedule, and quality control mechanisms. This project aims to deliver a user-friendly walking app that promotes fitness and exploration.

Running head: SYSTEM DESIGN DOCUMENT
System Design Document
Name of the Student
Name of the University
Author’s Note

1
SYSTEM DESIGN DOCUMENT
Package Diagram showing subsystems

2
SYSTEM DESIGN DOCUMENT
Class Diagrams

3
SYSTEM DESIGN DOCUMENT
Sequence Diagrams

4
SYSTEM DESIGN DOCUMENT
State Diagram

5
SYSTEM DESIGN DOCUMENT
Structure Chart
Report Layout
The following are the 5 main elements that comprises to form the report that is needed to be
prepared for the development of the app.
 Initial conversation
 Goal Definition
 Competitive Audit
 User Feedback
 Goal Review

6
SYSTEM DESIGN DOCUMENT
Program Navigation Diagram

7
SYSTEM DESIGN DOCUMENT
Use Case Diagram
Use case Description (Walking APP Use case)
Short description
The use case diagram is created for walking app for managing the flows of inputs and outputs of
the application developed for guiding the user with the use of interactive map for decreasing the
confusion among them and reduce the potential overhead needed for current map. The map is
developed for suggesting interactive routes for walking and showing the nearby checkpoints that
the user can visit for reducing the stress.
Primary Actor

8
SYSTEM DESIGN DOCUMENT
The primary actor are the users searching for routes for walking and it can be in the evening or
morning and the application is developed depending on the needs of the users for suggesting
them routes and nearby check points using the application interface.
Stakeholders and Interests
The main stakeholder for the development of the walking application are listed below:
 Admin
 Guide
 User
 Google Map API
It is the role of the marketing manager to create relationship with the user and promote the
application benefits to the users for the improvement of relationship with the user
The guide is responsible for adding new places in the app and improve the calibration and
location for improving the usability of the application.
The user finds interest in finding new routes for walking and get the nearby check points for
visiting and eliminate the stress of their lives.
The admin plays the role of management of user account and get feedback from the user for
improving the interface and add new functionality in the application for improving the customer
relationship and deliver the best outcome from the app
Preconditions

9
SYSTEM DESIGN DOCUMENT
The user need to download the application from playstore and install in their device for using the
application. The device should have the minimum android version of 4.0 and the permission for
using the gps of the device should be turned on.
Post conditions
The application uses the google map API and tracks the current location of the user and suggests
a walking route that can be used by the user for staying fit and healthy. The route can be changed
by the user and new route can be selected from the application interface and it tracks the user and
records the kilometers travelled by the user.
Main Success Scenario
1. The user needs to enter their details in the application for getting the other features like
calorie burn and footstep.
2. The user can be able to view the kilometers travelled in the last 7 days and generate a
report from the application on weekly basis
3. The user can protect the information by creating an account and use the phone security to
lock the application.
4. The user would be able to view the nearby checkpoints that they can visit if they need to
while walking through the suggested route.
Alternative Flows of Events
The alternative flow for reaching the goal of the application is that the user can search for a
check point and select a suggested route to reach the check point. In this way the user can
completed their work at the check point and complete the walking distance they regularly need to
follow for keeping their health in control. The application maintains a track on the footsteps and
the distance travelled and alert the user if they are too far from their home location for staying
within the limit set by the user.

10
SYSTEM DESIGN DOCUMENT
User Stories
User Story 1:
As a normal user I want to view the footsteps in my journey because I want to closely hit my
goals
User Story 2:
As a user I want to save my frequently navigated locations because it would be easier to me to
select them as easier and quicker options
User Story 3:
As a user I want the app to learn the frequent destination as I want navigating to them quickly
without the need of defining them
User Story 4:
As a user I want to participate in the challenge and I want to see the remaining steps in my
journey for staying competitive
User Story 5:
As a walker I want the app to learn my speed of walking such that it can accurately provide the
estimated time
User Story 5:
As a new user I want the app to be synchronized with my activity tracker such that the progress
toward daily activity can be viewed
User Story 6:

11
SYSTEM DESIGN DOCUMENT
As a user not always reach the goals I want reminder for searching direction for meeting my
daily goals.

12
SYSTEM DESIGN DOCUMENT
Bibliography
Arora, P.K. and Bhatia, R., 2018. Agent-Based Regression Test Case Generation using Class
Diagram, Use cases and Activity Diagram. Procedia Computer Science, 125, pp.747-753.
Bashir, R.S., Lee, S.P., Khan, S.U.R., Chang, V. and Farid, S., 2016. UML models consistency
management: Guidelines for software quality manager. International Journal of Information
Management, 36(6), pp.883-899.
Carvalho, M.B., Bellotti, F., Berta, R., De Gloria, A., Sedano, C.I., Hauge, J.B., Hu, J. and
Rauterberg, M., 2015. An activity theory-based model for serious games analysis and conceptual
design. Computers & education, 87, pp.166-181.
Dick, J., Hull, E. and Jackson, K., 2017. Requirements engineering. Springer.
Felderer, M. and Herrmann, A., 2015. Manual test case derivation from UML activity diagrams
and state machines: A controlled experiment. Information and Software Technology, 61, pp.1-15.
Heng, C.H.E.N., Zhang, L., Jianzhong, M.O. and Martin, K.E., 2016. Synchrophasor-based real-
time state estimation and situational awareness system for power system operation. Journal of
Modern Power Systems and Clean Energy, 4(3), pp.370-382.
Lu, Y., Mao, X. and Li, Z., 2016. Assessing software maintainability based on class diagram
design: A preliminary case study. Lecture Notes on Software Engineering, 4(1), p.53.
Solomencevs, A. and Osis, J., 2015, April. The algorithm for getting a uml class diagram from
topological functioning model. In 2015 International Conference on Evaluation of Novel
Approaches to Software Engineering (ENASE) (pp. 341-351). IEEE.