SRS The Adventure Island android Application

8/10/2019 SRS The Adventure Island android Application

1/15

The Adventure Island - App Document ID: TAI-SRS Version: 1.0

System Requirement Specification - SRS Version Date: Oct 15,2014

(TAI)

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)

The Adventure Island

Version 1.0


2/15



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 Use case Diagram and Non-functionalrequirements

FA, CN

Oct 15,2014 1.0 System Requirement Specification JAS, NS, FA,CN

Table of ContentsTable of Figures

1.IntroductionThe section introduces the Adventure Island Application

1.1.Specification ManagementThis specification documents the system-level requirements for the TAI Application.


3/15



1.2.

Specification ObjectivesThe 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 audienceThe 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.

ReferencesThe specification references or complies with the following documents/sites:

https://www.facebook.com/groups/TheAdventureMakers/

1.5.

Specification OverviewThis specification is organized into the following sections:

Introduction, which introduces the specification for the TAI Application to itsreaders.

System Overview, which provides a brief, high level description of the TAIApplication 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 OverviewThis section provides a high level description of The Adventure Island Application (TAI) -

system including its definition, primary goal, objectives, context, and capabilities.

2.1.

DefinitionTAI 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 andandroid to ease the event registration process for both participants and the managers of

the group.

2.2.GoalThe goal TAI is to take advantage of modern smart phones having Android OperatingSystems 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


4/15



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 externalhardware:

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 casesand their associated use case paths. The use case model is primarily organized in terms of theexternals that benefit from the use cases.

3.1.

TAI Use Case DiagramThe following use case diagrams summarize the functional requirements for the TAI:


5/15




6/15



3.2.

Use Case DescriptionThe section describes use cases and their basic functionalities:

3.2.1.

Use Case: Create EventUse Case Name: Create new event in TAI

Priority Essential

Trigger Menu selection

Precondition Event Manager have logged in to the

application

Basic Path 1. Event Manager selects new event option

from the menu

2. Manager is shown a form where he

provides detail about the event3. Manager fills the form and press Create

button

Alternate Path N/APostcondition The event is created successfully

Exception Path If there is a connection failure then errormessage is shown to the manager

Other

Reference SRS V1.0

3.2.2.Use Case: Send InvitationUse Case Name: Send Event Invitation

Priority Essential

Trigger Event Creation

Precondition New event is createdBasic Path TAI fetch list of all the users in database and

send them invitation of the newly created

event

Alternate Path N/A

Postcondition The event invitation is sent successfully

Exception Path N/A

Other

Reference SRS V1.0

3.2.3.

Use Case: Invitation via ApplicationUse Case Name: Send Invitation on TAI Application interfacePriority Essential


Precondition New event is created

Basic Path TAI fetch list of all the devices stored indatabase and sends them an application

notification indicating creation of new event


7/15



Alternate Path Notification is sent via Email

Postcondition Notification sent successfully

Exception Path N/A

Other

Reference SRS V1.0

3.2.4.

Use Case: Invitation via EmailUse Case Name: Send Invitation via Email

Priority Normal


Precondition New event is created

Basic Path TAI fetch list of all email addresses stored in

database and sends event invitation on them

Alternate Path Notification is sent via application interface

Postcondition Notification sent successfully


Other

Reference SRS V1.0

3.2.5.

Use Case: Check Event ListUse Case Name: Check the list of events

Priority Essential



application

Basic Path 1.

Event Manager selects check event

option from the menu2. Manager is shown a list of events

3. Manager can select an event to check its

details

Alternate Path N/A

Postcondition The event list is shown successfully

Exception Path If there is a connection failure then error

message is shown to the manager

Other

Reference SRS V1.0

3.2.6.Use Case: Check Past EventsUse Case Name: Check the list of all past events

Priority Normal



application


8/15



Basic Path 1. Event Manager selects check past events

option from the menu

2. Manager is shown a list of events thathave execution date before current date

3. Manager can select an event from the list

to check its detailsAlternate Path N/A

Postcondition The event list is shown successfully



Other

Reference SRS V1.0

3.2.7.Use Case: Check Current EventsUse Case Name: Check events that are to be executed

Priority EssentialTrigger Menu selection


application

Basic Path 1. Event Manager selects check current

events option from the menu2. 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

Alternate Path N/A

Postcondition The event list is shown successfullyException Path If there is a connection failure then error


Other

Reference SRS V1.0

3.2.8.

Use Case: Make DecisionUse Case Name: Make Decision

Priority Essential

Trigger Click accepts or reject invitation button.

Precondition The application must be connected to the

Internet and invitations have been sent to allparticipants.

Basic Path 1. The participant receives event invitation.2. The participant has an option to accept or

reject the event invitation.

3. The participant accepts the eventinvitation and an event registration form

will appear.


9/15



Alternate Path If a participant rejects the event invitation,

then the participant will not receive further

notifications about event.

Post condition Event registration form will appear after

accepting the event invitation.

Exception Path If there is a connection failure then errormessage is shown to the event manager

Other

Reference: SRS V1.0

3.2.9.

Use Case: Event RegistrationUse Case Name: Event Registration

Priority Essential

Trigger Event Registration


Internet and participants accept the eventinvitation.

Basic Path 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.

Alternate Path N/A

Post condition The participant is registered successfully

Exception Path If there is a connection failure then errormessage is shown to the event manager

OtherReference: SRS V1.0

3.2.10. Use Case: Check Participants ListUse Case Name: Check Participants list

Priority Essential

Trigger Click Participants list option

Precondition The event must be created successfully and

invitations have been sent to all participants.

Basic Path 1. The event manager requests the event

participants list.

2.

Event participants lists are displayed.

Alternate Path If no participant registrations for an event,then a message will appear that No registered

participants yet.

Post condition



10/15



message is shown to the event manager.

Other

Reference: SRS V1.0

3.2.11.

Use Case: Confirmation RequestUse Case Name: Confirmation RequestPriority Essential

Trigger Send Confirmation Request.


Internet and the participant should haveregistered for the event.

Basic Path 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 thepayment.

2. Error Message: Invalid/incompleteinformation.

Post condition


message is shown to the event manager.

Other

Reference: SRS V1.0

3.2.12. Use Case: Confirm RegistrationUse Case Name: Confirm registration

Priority Essential

Trigger Confirm registration event

Precondition Participant has sent the confirmation request.

Basic Path 1. Event Manager checks the participant

information.

2. Manager receives the payment.

3. Confirms the participant.

Alternate Path' 1. Error Message: Manager doesn't get the

payment.

2. Error Message: Invalid/incomplete

information.

Post condition Confirm registration of participant.


Other


11/15



Reference SRS V1.0

3.2.13.

Use Case: Send NotificationUse Case Name: Send notification

Priority EssentialTrigger Send notification event

Precondition Participant registration is confirmed.

Basic Path 1. Manager notifies the registered participant

about the confirmation.

Alternate Path N/A

Post condition Participant receives the notification.



Other

Reference SRS V1.0

3.2.14.

Use Case: Submit FeedbackUse Case Name: Submit feedback

Priority Optional

Trigger Submit feedback event

Precondition Participant has attended the event.

Basic Path 1. The participant requests to submit the

feedback.

2. Participant gives his reviews about theevent.

3. Submits the feedback.

4. The feedback gets stored in database.Alternate Path N/A

Post condition Feedback has been stored in database.


message is shown to the participant.

Other

Reference SRS V1.0

3.2.15.

Use Case: Check FeedbackUse Case Name: Check feedback

Priority OptionalTrigger View feedback event

Precondition The feedback comments from participants

are already present in the system.

Basic Path 1. The manager requests to check the

feedback.2. Feedback comments are displayed on the

UI.


12/15



Alternate Path N/A

Post condition Feedback comments have been displayed.

Exception Path If there is a connection failure then errormessage is shown to the manager.

Other

Reference SRS V1.0

5.

Data RequirementsThis section specifies the data requirements on the TAI system.

5.1.Event InformationInformation 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 InformationAt 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 theparticipants

Registration completed message to the participants.

Feedback done message toparticipants

5.4.ReportsThis section specifies the data requirements concerning reports generated by the TAI.

5.4.1. All Participants ReportThe 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


13/15



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 ReportThis 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 Requirements6.1.

AccessibilityThis subsection specifies the following requirements associated with the degree to whichthe 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.AuditabilityThe 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 andfeedbacks for as long as they are required.

6.3.

ConfigurabilityThis subsection specifies the following requirements associated with the degree to whichthe 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. InternationalizationThere are no requirements for internationalization envisioned because The

Adventure Island is only using English as a language of communication.

6.4.

CorrectnessThis subsection specifies the following requirements concerning the degree to which thesystem can contain defects and still be acceptable to the customer.

6.4.1. Latent defectsThis 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.


14/15



COR-2) the latent defects needs to be categorized as and when found intoMinor, Critical and Significant bugs.

6.4.2. AccuracyThis subsection specifies the following requirements concerning the degree of

correctness of the systemsoutputs:

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 doesmake a difference.

6.5.

EfficiencyThis subsection specifies the following requirements associated with the degree to whichthe system effectively uses its resources:

EFF-1) The TAI shall not require users to do heavy downloads to theirsmartphones and no heavy internet usage.

6.6.ExtensibilityThis subsection specifies the following requirements associated with the degree to which

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.InstallationThis subsection specifies the following usability requirements associated with the easewith which the system can be installed.

INS-1) itsan android application which will be available on Google app storeand can be easily installed from app store.

INS-2) updates can easily be installed by just selecting update when updates areavailable

6.8.Operational availabilityThis 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 operationalavailability of 99%.

6.9.

PerformanceThis 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 minimumnumber 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 simultaneousinteractions.

6.9.2. Latency


15/15



This subsection specifies the following requirements concerning the maximum time

that is permitted for the system to execute specific tasks (i.e., system operations) oruse case paths end to end:

PER-4) The typical manager shall be able to create an event within 2minutes.

PER-5) The typical manager shall be able to confirm registration within halfminute

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 timeThis 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.

ReliabilityThis 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.

ReusabilityThis subsection specifies the following requirements associated with the degree to which

the system can be used for purposes other than originally intended (e.g., as part of other

applications).

REU-1) The TAI shall reuseparticipants information for event registration.

6.12.

SafetyThis subsection specifies the following requirements associated with the degree to whichthe 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:

ManagerA minimum of 99.999% of the time, the TAI shall verify theidentity of the Manager.

6.13. TestabilityThis 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.

Date post:	02-Jun-2018
Category:	Documents
Upload:	jawadshah
View:	232 times
Download:	0 times

SRS The Adventure Island android Application

Documents