SRS The Adventure Island Android Application

The Adventure Island - App
System Requirement Specification - SRS
Document ID: TAI-SRS

Version Date: Oct 15,2014
Version: 1.0
The Adventure Island

(TAI)
Version 1.0
Produced for:
SEECS
NUST
H-12 Islamabad
Produced By:
Fatima Ambreen (MSIT-15)
Jawad Ali Shah (MSCS-2)
Numra Saeed (MSIT-15)
Capt. Naeem (MSCS-1)


Version: 1.0
Executive Overview
The Adventure Island is a non-profit organization that arranges different kind of adventure
activities in Islamabad and Rawalpindi. The activities include trips, hikes, skiing, paragliding,
rock climbing and archery.
The Management objectives for TAI application are:
Create events
Send Invitations to the clients
Send different notifications to the participants
Check past and upcoming events
Check participants of an event
Confirm registration for an event
Update event details
Check event details
The Participant objectives for TAI are:
Check Event detail

Join or reject event
Register for event
Check previous events
Ask for confirmation
Give feedback about an event
Revision History
Date
Version
Description
Author
Oct 3,2014
0.1
Functional requirements
JAS, NS
Oct 3,2014
0.2
FA, CN
Oct 15,2014
1.0
Use case Diagram and Non-functional

requirements
System Requirement Specification
JAS, NS, FA,

CN
Table of Contents
Table of Figures
1. Introduction
The section introduces the Adventure Island Application
1.1. Specification Management

This specification documents the system-level requirements for the TAI Application.


Version: 1.0
1.2. Specification Objectives

The objective of this specification is to:
Provide a system overview of the TAI Application including definition, goals,
objectives, context, and major capabilities.
To formally specify its associated:
o Functional Requirements
o Data requirements
o Quality requirements
1.3. Intended audience

The intended audiences of stakeholders for this specification of TAI Application include:
The Adventure Island(TAI) management
Participants who joins on events
Guests of participants
Banks
Transport companies
1.4. References
The specification references or complies with the following documents/sites:
https://www.facebook.com/groups/TheAdventureMakers/
1.5. Specification Overview

This specification is organized into the following sections:
Introduction, which introduces the specification for the TAI Application to its
readers.
System Overview, which provides a brief, high level description of the TAI
Application including its definition, business goals, business objectives, context,
and capabilities.
Functional Requirements, which specifies the functional system requirements in
terms of a use case model
Data Requirements, which specifies the system data requirements in terms of
required data components.
Quality Requirements, which specifies the required system quality factors.
Glossary.
2. The Adventure Island - Application Overview

This section provides a high level description of The Adventure Island Application (TAI) system including its definition, primary goal, objectives, context, and capabilities.
2.1. Definition
TAI is an android application specially designed for The Adventure Island which is a
non-profit adventure club in Islamabad. It takes the advantage of World Wide Web and
android to ease the event registration process for both participants and the managers of
the group.
2.2. Goal
The goal TAI is to take advantage of modern smart phones having Android Operating
Systems to speed up and ease the registration process where clients can be informed
about events at their mobile phones and they can register using their smartphones.
2.3. Objective


Version: 1.0
The objectives of the TAI are to provide the following benefits to TAI Management and
participants.
2.3.1. Management Objectives
Enable Management to be connected with all previous participants.
Enable Management to manage all events systematically.
Enable Management to manage all participants of a particular in an order.
Allows management to check all the events with their details
Allows management to check feedback of all events.
Allows management to invite all participants for new events.
2.3.2. Participants Objectives
Allows participants to check events
Allows participants to register for an event from their own device.
Allows participants to check details of an event.
Allows participants to give feedback for an event.
2.3.3. External Hardware
The TAI interacts, either directly or indirectly, with the following significant external
hardware:
Client Hardware
o Android Smartphones, which are the personal mobile phones used by
participants and managers to enter TAI.
o Database Server, which will store all information about participants and
events
Networks
o Internet, which is the global network used for communication among TAI
managers and participants.
3. Functional Requirements
The section of the SRS specifies the functional requirements of the TAI in terms of use cases
and their associated use case paths. The use case model is primarily organized in terms of the
externals that benefit from the use cases.
3.1. TAI Use Case Diagram

The following use case diagrams summarize the functional requirements for the TAI:


Version: 1.0


Version: 1.0
3.2. Use Case Description

The section describes use cases and their basic functionalities:
3.2.1. Use Case: Create Event

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Create new event in TAI

Essential
Menu selection
Event Manager have logged in to the
application
1. Event Manager selects new event option
from the menu
2. Manager is shown a form where he
provides detail about the event
3. Manager fills the form and press Create
button
N/A
The event is created successfully
If there is a connection failure then error
message is shown to the manager
SRS V1.0
3.2.2. Use Case: Send Invitation

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Send Event Invitation

Essential
Event Creation
New event is created
TAI fetch list of all the users in database and
send them invitation of the newly created
event
N/A
The event invitation is sent successfully
N/A
SRS V1.0
3.2.3. Use Case: Invitation via Application

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Send Invitation on TAI Application interface

Essential
Event Creation
TAI fetch list of all the devices stored in
database and sends them an application
notification indicating creation of new event

Alternate Path
Postcondition
Exception Path
Other
Reference

Version: 1.0
Notification is sent via Email

Notification sent successfully
N/A
SRS V1.0
3.2.4. Use Case: Invitation via Email

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Send Invitation via Email

Normal
Event Creation
TAI fetch list of all email addresses stored in
database and sends event invitation on them
Notification is sent via application interface
Notification sent successfully
SRS V1.0
3.2.5. Use Case: Check Event List

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Check the list of events

Essential
Menu selection
application
1. Event Manager selects check event
option from the menu
2. Manager is shown a list of events
3. Manager can select an event to check its
details
N/A
The event list is shown successfully
SRS V1.0
3.2.6. Use Case: Check Past Events

Use Case Name:
Priority
Trigger
Precondition
Check the list of all past events

Normal
Menu selection
application


Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Version: 1.0
1. Event Manager selects check past events

option from the menu
2. Manager is shown a list of events that
have execution date before current date
3. Manager can select an event from the list
to check its details
N/A
SRS V1.0
3.2.7. Use Case: Check Current Events

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Postcondition
Exception Path
Other
Reference
Check events that are to be executed

Essential
Menu selection
application
1. Event Manager selects check current
events option from the menu
2. Manager is shown a list of events that
have execution date after current date
3. Manager can select an event from the list
to check its details
N/A
SRS V1.0
3.2.8. Use Case: Make Decision

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Make Decision
Essential
Click accepts or reject invitation button.
The application must be connected to the
Internet and invitations have been sent to all
participants.
1. The participant receives event invitation.
2. The participant has an option to accept or
reject the event invitation.
3. The participant accepts the event
invitation and an event registration form
will appear.

Alternate Path
Post condition
Exception Path
Other
Reference:

Version: 1.0
If a participant rejects the event invitation,

then the participant will not receive further
notifications about event.
Event registration form will appear after
accepting the event invitation.
message is shown to the event manager
SRS V1.0
3.2.9. Use Case: Event Registration

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Post condition
Exception Path
Other
Reference:
3.2.10.
Event Registration
Essential
Event Registration
Internet and participants accept the event
invitation.
1. The participant view registration form.
2. The participant fills the basic information
required in the registration form.
3. The participant submits the registration
form.
N/A
The participant is registered successfully
message is shown to the event manager
SRS V1.0
Use Case: Check Participants List

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Post condition
Exception Path
Check Participants list

Essential
Click Participants list option
The event must be created successfully and
invitations have been sent to all participants.
1. The event manager requests the event
participants list.
2. Event participants lists are displayed.
If no participant registrations for an event,
then a message will appear that No registered
participants yet.


Version: 1.0
message is shown to the event manager.

Other
Reference:
3.2.11.
SRS V1.0
Use Case: Confirmation Request

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Confirmation Request
Essential
Send Confirmation Request.
Internet and the participant should have
registered for the event.
1. The participant sends request to event
manager for verification of event payment.
2. Event manager confirms the event
registration.
Alternate Path
1. Error Message: Manager doesn't get the

payment.
2. Error
Message:
information.
Post condition
Exception Path
Other
Reference:
3.2.12.
Invalid/incomplete

message is shown to the event manager.
SRS V1.0
Use Case: Confirm Registration

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path'
Confirm registration
Essential
Confirm registration event
Participant has sent the confirmation request.
1. Event Manager checks the participant
information.
2. Manager receives the payment.
3. Confirms the participant.
1. Error Message: Manager doesn't get the
payment.
2. Error
Message:
information.
Post condition
Exception Path
Other
Invalid/incomplete
Confirm registration of participant.


Reference
3.2.13.
Alternate Path
Post condition
Exception Path
Other
Reference
SRS V1.0
Send notification
Essential
Send notification event
Participant registration is confirmed.
1. Manager notifies the registered participant
about the confirmation.
N/A
Participant receives the notification.
SRS V1.0
Use Case: Submit Feedback

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Alternate Path
Post condition
Exception Path
Other
Reference
3.2.15.
Version: 1.0
Use Case: Send Notification

Use Case Name:
Priority
Trigger
Precondition
Basic Path
3.2.14.

Submit feedback
Optional
Submit feedback event
Participant has attended the event.
1. The participant requests to submit the
feedback.
2. Participant gives his reviews about the
event.
3. Submits the feedback.
4. The feedback gets stored in database.
N/A
Feedback has been stored in database.
message is shown to the participant.
SRS V1.0
Use Case: Check Feedback

Use Case Name:
Priority
Trigger
Precondition
Basic Path
Check feedback
Optional
View feedback event
The feedback comments from participants
are already present in the system.
1. The manager requests to check the
feedback.
2. Feedback comments are displayed on the
UI.

Alternate Path
Post condition
Exception Path
Other
Reference

Version: 1.0
N/A
Feedback comments have been displayed.
message is shown to the manager.
SRS V1.0
5. Data Requirements
This section specifies the data requirements on the TAI system.
5.1. Event Information

Information of all the events is required for creation. Minimum we need these values.
Event name
Event Date
Event Time
Location
Event Cost
Payment Methods
Last date of registration
Number of seats available
5.2. Participants Information

At the time of registration following information of participants is required.
Full name
Mobile number
Email Address
City
Picture (Optional)
Guests Names (If any)
5.3. Messages
New Event Created message to the managers.

New Event Available message to the participants
Registration completed message to the participants.
Feedback done message to participants
5.4. Reports
This section specifies the data requirements concerning reports generated by the TAI.
5.4.1. All Participants Report
The all participants report shall contain the following information:
participant picture
First name / Surname of the participant
Email Address of the participant
City / Town
Email Address
Cell phone number of the participant
5.4.2. Event Report


Version: 1.0
Managers can check event details the following information will be shown to the
manager
Event Name
Location
Event Date and time
Event charges
Max seats available
5.4.3. Feedback Report
This report has a graph showing marks given by participants against different questions
Event Name
Question on x-axis
Results on y-axis
5.4.4. Participants of an event report
The contents of this report are:
Event Name
Participant name
Participant mobile no
6. System Quality Requirements

6.1. Accessibility
This subsection specifies the following requirements associated with the degree to which
the system must be accessible to people with disabilities:
ACC-1) any graphical user interfaces of the TAI shall use an adequate font size
to be usable by persons with limited visual acuity
6.2. Auditability
The subsection specifies the following requirements associated with the degree to which
the system must support independent auditing of its data.
AUD-1) the system shall maintain the record of events their participants and
feedbacks for as long as they are required.
6.3. Configurability
the system must exist in multiple simultaneous configurations or variants:
6.3.1. Variant capabilities
There are no requirements for multiple variants of the TAI.
6.3.2. Internationalization
There are no requirements for internationalization envisioned because The
Adventure Island is only using English as a language of communication.
6.4. Correctness
This subsection specifies the following requirements concerning the degree to which the
system can contain defects and still be acceptable to the customer.
6.4.1. Latent defects
This subsection specifies the following requirements concerning the maximum
number of allowable latent defects in released work products.
COR-1) the maximum number of latent bugs per unit of software shall not
exceed too much and must not have an influence on results.


Version: 1.0
COR-2) the latent defects needs to be categorized as and when found into
Minor, Critical and Significant bugs.
6.4.2. Accuracy
This subsection specifies the following requirements concerning the degree of
correctness of the systems outputs:
COR-3) Values of email address shall be accurate so that system
COR-4) Values of time and date events shall be accurate.
6.4.3. Precision
This subsection specifies the following requirements concerning the resolution of
the systems numerical outputs:
COR-5) Values of event charges shall be precise as round of figures does
make a difference.
6.5. Efficiency
the system effectively uses its resources:
EFF-1) The TAI shall not require users to do heavy downloads to their
smartphones and no heavy internet usage.
6.6. Extensibility
the system can be modified to meet changing requirements or goals.
EXT-1) the system shall be easily extended by installing the updates.
6.7. Installation
This subsection specifies the following usability requirements associated with the ease
with which the system can be installed.
INS-1) its an android application which will be available on Google app store
and can be easily installed from app store.
INS-2) updates can easily be installed by just selecting update when updates are
available
6.8. Operational availability

This subsection specifies the following requirements associated with the percent of time
that the system must function correctly.
OA-1) by this release, the TAI shall provide actors with a minimum operational
availability of 99%.
6.9. Performance
This subsection specifies the following requirements associated with the speed with
which the system shall function.
6.9.1. Capacity
This subsection specifies the following requirements concerning the minimum
number of objects that the system can support:
PER-1) The system shall support a minimum of 500,000 users.
PER-2) The system shall support as many events as the manager creates.
PER-3) The system shall support a minimum of 1000 simultaneous
interactions.
6.9.2. Latency


Version: 1.0
This subsection specifies the following requirements concerning the maximum time
that is permitted for the system to execute specific tasks (i.e., system operations) or
use case paths end to end:
PER-4) The typical manager shall be able to create an event within 2
minutes.
PER-5) The typical manager shall be able to confirm registration within half
minute
PER-6) The typical participant can register for an event in less than a minute
PER-7) The typical participant can give feedback in less than 5 minutes
6.9.3. Response time
This subsection specifies the following requirements concerning the maximum time
that is permitted for the system to respond to requests:
PER-8) All system responses shall occur within 30 seconds.
6.10.
Reliability
This subsection specifies the following requirements associated with the reliability (e.g.,
mean time between failures, number of failures per unit time) of the system.
REL-1) The mean time between failures (MTBF) shall exceed 3 months.
6.11.
Reusability
the system can be used for purposes other than originally intended (e.g., as part of other
applications).
REU-1) The TAI shall reuse participants information for event registration.
6.12.
Safety
the system does not directly or indirectly (e.g., via inactivity) cause accidental harm to
property (e.g., loss of data).
SAF-1) The TAI shall not accidentally lose participants personal information.
6.12.1. Authentication requirements
This subsection documents the authentication requirements that specify the extent to
which the TAI shall verify the identity of its managers before interacting with TAI:
Manager A minimum of 99.999% of the time, the TAI shall verify the
identity of the Manager.
6.13.
Testability
This subsection specifies the following requirements associated with the ease with which
the system can be tested.
TST-1) the system shall be tested on a sample event.

SRS The Adventure Island Android Application

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SRS The Adventure Island Android Application

Uploaded by

Copyright:

Available Formats

The Adventure Island - App

System Requirement Specification - SRS

Document ID: TAI-SRS

The Adventure Island

The Adventure Island - App

Document ID: TAI-SRS

The Participant objectives for TAI are:

Check Event detail

Use case Diagram and Non-functional

JAS, NS, FA,

1.1. Specification Management

The Adventure Island - App

Document ID: TAI-SRS

1.2. Specification Objectives

1.3. Intended audience

1.5. Specification Overview

2. The Adventure Island - Application Overview

The Adventure Island - App

Document ID: TAI-SRS

3.1. TAI Use Case Diagram

The Adventure Island - App

Document ID: TAI-SRS

The Adventure Island - App

Document ID: TAI-SRS

3.2. Use Case Description

3.2.1. Use Case: Create Event

Create new event in TAI

3.2.2. Use Case: Send Invitation

Send Event Invitation

3.2.3. Use Case: Invitation via Application

Send Invitation on TAI Application interface

The Adventure Island - App

Document ID: TAI-SRS

Notification is sent via Email

3.2.4. Use Case: Invitation via Email

Send Invitation via Email

3.2.5. Use Case: Check Event List

Check the list of events

3.2.6. Use Case: Check Past Events

Check the list of all past events

The Adventure Island - App

Document ID: TAI-SRS

1. Event Manager selects check past events

3.2.7. Use Case: Check Current Events

Check events that are to be executed

3.2.8. Use Case: Make Decision

The Adventure Island - App

Document ID: TAI-SRS

If a participant rejects the event invitation,

3.2.9. Use Case: Event Registration

Use Case: Check Participants List

Check Participants list

The Adventure Island - App

Document ID: TAI-SRS

message is shown to the event manager.

Use Case: Confirmation Request

1. Error Message: Manager doesn't get the

If there is a connection failure then error

Use Case: Confirm Registration

Confirm registration of participant.

The Adventure Island - App

Use Case: Submit Feedback

Use Case: Send Notification