TEAM NAME : ANDROMEDA

Instructor: Prof. Dr. Lawrence Chung

Aarthi Giridharan (lead)
Balaji Shanmugam
Govindarajan Panneerselvam
Kumaran Senapathy
Neha Malloli
Sriram Sridharan
Vignesh Swaminathan
System Requirements Specification – Synopsis

Project Outline
Requirement Engineering Process
Problems & Proposed Solutions
Requirement Analysis
Writing Specifications
Model Development
Future Enhancements
There is need for devices to help the A mobile communication device is
speech, hearing and vision impaired. the best option to use as a Single
tool to serve as a multi-functional
help device.

Devices currently developed by

Augmentative and Alternative All the day-to-day needs could be
Communication (AAC) are bulky to communicated to the one who is
handle and are not multi-functional. helping by using just one device
A classic approach definition to an “all-in-one” solution where the user
need not depend on any other device but the mobile phone to meet most of
the basic needs.

Drastically reducing the level of dependency on a third person as many of

the services are available in a pocket device.

 Developing user friendly application to support features like emergency

contacts, speed dialing, drug reminders, speech recognition, profiles, etc.
Designing comprehensible GUI helps the users to access any of the
applications with a just a click or touch on the main screen.

Implementing HOPE on a smart phone that uses the ANDROID

platform to run these applications with the help of other JAVA
based applications.

Developing HOPE applications with the ultimate goal of meeting

the need of an elderly person who might require assistance in
times of emergency.
Analyze the essential requirements for the project development and
discussing with the other co-developers.

Build the deliverables.

Check for correctness and completeness in the deliverables.

Before final submission, review and check the deliverables.

Phase Deliverable Start Date End Date
Phase 0 PRELIMINARY PROJECT PLAN Jan 24, 2012 Jan 25, 2012

Phase 1 INTERIM PROJECT 1 Jan 27, 2012 Feb 29, 2012

 REQUIREMENT SPECIFICATION
 REQUIREMENT ANALYSIS
 PRESENTATION
Phase 1 FINAL PROJECT 1 Mar 02, 2012 Mar 26, 2012
 IMPROVED REQUIREMENT SPECIFICATION
 IMPROVED REQUIREMENT ANALYSIS
 PRESENTATION
Phase 2 INTERIM PROJECT 2 Mar 28, 2012 Apr 16, 2012
 IMPROVED REQUIREMENT SPECIFICATION/ANALYSIS
 IMPLEMENTATION
 TESTING
 PRESENTATION
Phase 2 FINAL PROJECT 2 Apr 18, 2012 Apr 30,2012
 MODIFIED IMPLEMENTATION
 MODIFIED TESTING
 PRESENTATION
 Phase 0 / Phase 1 Phase 2

Establish Select
Understand Develop Evaluate
Outline Prototyping
Problems Prototype Prototype
Requirement System

Domain Expert
Req Engg Software Req Engg
Req Engg End-User
Domain Engg. Software
End User Software Engg
Expert Project Mgr Engg
Req Engg
Phase Deliverable Developers Reviewers
PHASE 0 SOFTWARE PROJECT KUMARAN AARTHI
MANAGEMENT PLAN BALAJI
GOVINDARAJAN

PHASE 1 REQUIREMENTS SPECIFICATION SRIRAM BALAJI

VIGNESH
NEHA
PHASE 1 ANALYSIS MODEL BALAJI SRIRAM
AARTHI
KUMARAN
PHASE 2 CODE AARTHI VIGNESH, NEHA
BALAJI
GOVINDARAJAN
KUMARAN
NEHA
SRIRAM
VIGNESH
PHASE 2 SYSTEM TEST KUMARAN GOVINDARAJAN
SRIRAM
NEHA
PHASE 2 USER DOCUMENTATION BALAJI KUMARAN
VIGNESH
GOVINDARAJAN
 FUNCTIONAL
PHASE MANAGEMENT RESPONSIBLE
DUTY

GOVINDARAJAN,
AARTHI,
BALAJI,
PRELIMINARY PROJECT
GOVINDARAJAN DOCUMENTATION NEHA,
PLAN
KUMARAN,
SRIRAM,
VIGNESH

AARTHI,
SRIRAM,
DOCUMENTATION
BALAJI,
KUMARAN, VIGNESH
INTERIM PHASE I
VIGNESH
GOVINDARAJAN,
PRESENTATION NEHA,
KUMARAN
Incompleteness
 Undefined terms
 Incomplete list

Uncertainty
 Dubious terms
 Unclear phrases

Inconsistency
 Contradictory Statements
Detect the problem

Suggest appropriate solutions

Use different approaches to solve

List the essential requirements for solving

 Requirements

Non
Domain Functional
Functional

Reflects the Reflects the

Criteria to
environment set of inputs,
judge the
in which the its behaviors
operation of
system and resulting
the system
operates outputs
DR-01 : Emergency DR-02 : Speech2Text

DR-03 : Text2Speech DR-04 : FaceLook

DR-05 : MyPage DR-06 : PillTracker

DR-07 : MyShelf DR-08 : DietManager

DR-09 : Walk-O-Meter DR-10 : PicTalk
 Domain Functional Event Generated by End-User System Response to the
Requirement Requirement Event
(DR) (FR)
DR-01 FR-01 Touch on the Emergency Icon Displays list of Emergency
contacts that could be
called by a single touch
DR-02 FR-02 Touch the Speech2Text Icon Voice input is converted in
and feed the voice input textual form
DR-03 FR-03 Touch the Text2Speech Icon Textual input is processed
and feed the textual input into a voice output
DR-04 FR-04 Touch the FaceLook Icon to Displays all the details of
search contacts by the selected contact
pictures/names
DR-05 FR-05 Touch the MyPage Icon to Displays all personal
retrieve information about information stored by the
one’s self user
 Domain Functional Event Generated by End-User
Requirement Requirement
(DR) (FR)
DR-06 FR-06 Touch the PillTracker Icon
to store the medicine stock and
the intake timings
DR-07 FR-07 Touch the MyShelf Icon to
store the information about
the location of the frequently
used items at home.
DR-08 FR-08 Touch the DietManager Icon to
specify the blood sugar level,
cholesterol level, etc.
DR-09 FR-09 Touch the Walk-O-Meter Icon
to specify the start time/end
time of a walking session
DR-10 FR-10 Touch the PicTalk Icon to
convey a message by choosing
the pictures available
System Response to the
Event
Alerts the user at the stored
time to consume the
medicine and updates
medicine stock.
Prompts the user about the
location on selecting the
item
Displays the list of food
items one should and should
not consume
Displays the distance
covered and calories burnt
in that session
Displays and produces the
sound for the chosen picture
 NON FUNCTIONAL
REQUIREMENTS

USER SPECIFIC SYSTEM SPECIFIC

 EMERGENCY
RELIABILITY SPEECH2TEXT
PILLTRACKER

USER PICTALK
SPECIFIED SCALABILITY MYSHELF
NFR FACELOOK

USABILITY ALL THE DRs

 CHECK
AGAINST
TESTABILITY
VARIOUS
HYPOTHESIS

SHOULD
SYSTEM
WORK ON
SPECIFIED INTEROPERABILITY
VARIOUS
NFR
PLATFORMS

IMPORTING/
EXTENSIBILITY EXPORTING
DATA
Unambiguous: Each requirement definition shall
have no more than one interpretation

Concise: Minimal words yet maximum information

Wholeness: The specification contains all

requirements known

Stableness: There are no conflicting requirements

Systematized: Organized into meaningful groups

Follow uniquely recognizable naming convention

Maintain a solitary storage spot for all SRS

Use a single standard document format

Abide by the customary rules for writing a good WRS

Make an accommodative/adaptive document quality

 Sample
A prototype
prototype of
of the
the application
app
Speach2Text
“Speech2Text”–
STEP
STEP 11
 Sample
prototype of the
app
“Speech2Text”
STEP 2
Self Explanatory –
User Friendly Layout
Icons/App Names

Unique Apps

V Model Wide Area of Service

One Touch Emergency
Text/ Voice Message

Wireless Medical
Report Transmission

Profile Retrieval Using

Image Recognition
Project Status (completed stage) Accommodation Percentage

Requirement 40-55%

Analysis 15-40%

Design 10-15%

Implementation 0-10%