Mobile Development Fundamental

This document discusses the fundamentals of mobile development and focuses on designing an app for a tennis club. It covers the scenario, expected users, app functions, and requirements.

Running head: MOBILE DEVELOPMENT FUNDAMENTAL
COVER PAGE

2MOBILE DEVELOPMENT FUNDAMENTAL
Mobile Development Fundamental
Name of Student-
Name of University-
Author’s Note-

3MOBILE DEVELOPMENT FUNDAMENTAL
Table of Contents
Task 1 – Decide on a scenario for an app that you will make the design for..................................3
a. Description of the scenario:.....................................................................................................3
b. Expected users:........................................................................................................................3
c. App functions/requirements.....................................................................................................3
d. Chosen scenario that will address the requirements of the application...................................3
Task 2 – Use Case Diagram.............................................................................................................5
Task 3 – Storyboards.......................................................................................................................6
Task 4 – Sample Inputs / Test Data.................................................................................................9
Bibliography..................................................................................................................................10

4MOBILE DEVELOPMENT FUNDAMENTAL
Task 1 – Decide on a scenario for an app that you will make the design for.
a. Description of the scenario:
The scenario that is undertaken for this report is the development of a mobile based
application for the members of the tennis club. The mobile application helps to keep track on all
the members who are associated with the club, keep track on the membership annual payment of
the club members, keep a track on the player listing which player will play in the match, and also
keep a track on storing the scores of the matches that are held every week in the club.
b. Expected users:
The expected users of the Tennis Club app will be the administrator of the club, and the
members associated with the club.
c. App functions/requirements
The application of the tennis club will allow the user to do the following functions:
 The system will take the details of the club members as input and will show the result of
the club members details when report is required.
 The system will store the details of the matches played every week.
 The system will also store roaster of each match listing who will play the match.
 The score details of the match will be kept by the app of the tennis club.
d. Chosen scenario that will address the requirements of the application
The scenario that defines the requirements of the application is that:
 As a club member, the user will be able to register themselves in the data of the system
and the store details about them.

5MOBILE DEVELOPMENT FUNDAMENTAL
 As a club member, the club member can update the number of matches that are played by
them.
 The club member should store their phone number as an evidence so that they can be
contacted when needed.
 The club member can get the details of the match from the application every week.
 The user can get the match result from the app that is being developed for the system.
 The administrator that is the committee of the club selects the player who will play for a
particular week.
 The committee can upload the result of the match.
 The admin can generate the reports.

6MOBILE DEVELOPMENT FUNDAMENTAL
Task 2 – Use Case Diagram
Figure 1: Use Case diagram
(Source: Created by author using Visio)

7MOBILE DEVELOPMENT FUNDAMENTAL
Task 3 – Storyboards
Functionality one: Registering in the system
Storyboard 1: Registration for Club members
Explanation: The above diagram shows the registration process of the club member. The
club member in order to participate in the matches needs to register in the system. Each club
member need to sign up with their names, address, and contact number. After registering
themselves they can view the match details or can view the match results by selecting the date.

8MOBILE DEVELOPMENT FUNDAMENTAL
Functionality two: Sign up System
Storyboard 2: Registration for Club members
Explanation: For old members of the club, the member needs to login with the username
and password. After login only, they can view the details of the match.

9MOBILE DEVELOPMENT FUNDAMENTAL
Functionality three: Login unsuccessful
Storyboard 3: Login Functionality Unsuccessful
Explanation: When the user provide wrong user name and password that is not saved in
the database. When the user provides wrong credentials, the system shows that the username or
password is wrong and instructs the user to login again with valid username and password.

10MOBILE DEVELOPMENT FUNDAMENTAL
Task 4 – Sample Inputs / Test Data
Test Case Test Case Description Test Steps Test data
1 Provide valid
password
Enter valid password
with proper
credentials that is
there should be a
number, and a special
character
Abh12ibj
2 Provide valid email The email should be
validated
[e-mail]
3 Provide valid date The date should be
validated in valid
format
12/09/2019

11MOBILE DEVELOPMENT FUNDAMENTAL
Bibliography
Blobel, B. and Roger-France, F., 2001. A systematic approach for analysis and design of secure
health information systems. International journal of medical informatics, 62(1), pp.51-78.
Eertink, H., Janssen, W., Luttighuis, P.O., Teeuw, W. and Vissers, C., 1999, September. A
business process design language. In International Symposium on Formal Methods(pp. 76-95).
Springer, Berlin, Heidelberg.
Maylawati, D.S., Darmalaksana, W. and Ramdhani, M.A., 2018, January. Systematic Design of
Expert System Using Unified Modelling Language. In IOP Conference Series: Materials
Science and Engineering (Vol. 288, No. 1, p. 012047). IOP Publishing.
Roux-Rouquié, M., Caritey, N., Gaubert, L. and Rosenthal-Sabroux, C., 2004. Using the Unified
Modelling Language (UML) to guide the systemic description of biological processes and
systems. Biosystems, 75(1-3), pp.3-14.