View
50
Download
1
Category
Tags:
Preview:
DESCRIPTION
H. O. P. E. (Helping “Our” People Easily). TEAM NAME : ANDROMEDA Instructor: Prof. Dr. L awrence Chung. Aarthi Giridharan (lead) Balaji Shanmugam Govindarajan Panneerselvam Kumaran Senapathy Neha Malloli Sriram Sridharan Vignesh Swaminathan. Crew Members. - PowerPoint PPT Presentation
Citation preview
TEAM NAME : ANDROMEDAInstructor: Prof. Dr. Lawrence Chung
H. O. P. E.(Helping “Our” People Easily)
Crew Members
Aarthi Giridharan (lead)
Balaji Shanmugam
Govindarajan Panneerselvam
Kumaran Senapathy
Neha Malloli
Sriram Sridharan
Vignesh Swaminathan
Project : Phase 1 (Interim)
System Requirements Specification – Synopsis
Project Outline
Requirement Engineering Process
Problems & Proposed Solutions
Requirement Analysis
Writing Specifications
Model Development
Future Enhancements
PROJECT OUTLINE
Present Scenario
There is need for devices to help the speech, hearing and vision impaired.
Devices currently developed by Augmentative and Alternative Communication (AAC) are bulky to handle and are not multi-functional.
Proposed Idea
A mobile communication device is the best option to use as a Single tool to serve as a multi-functional help device.
All the day-to-day needs could be communicated to the one who is helping by using just one device
Why this project?
What the project deals with?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.
How is this possible?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.
REQUIREMENT ENGINEERING PROCESS
Process Model
ProcessAnalyze 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.
Project DeliverablesPhase Deliverable Start Date End Date
Phase 0 PRELIMINARY PROJECT PLAN Jan 24, 2012 Jan 25, 2012
Phase 1 INTERIM PROJECT 1 REQUIREMENT SPECIFICATION REQUIREMENT ANALYSIS PRESENTATION
Jan 27, 2012 Feb 29, 2012
Phase 1 FINAL PROJECT 1 IMPROVED REQUIREMENT SPECIFICATION IMPROVED REQUIREMENT ANALYSIS PRESENTATION
Mar 02, 2012 Mar 26, 2012
Phase 2 INTERIM PROJECT 2 IMPROVED REQUIREMENT SPECIFICATION/ANALYSIS IMPLEMENTATION TESTING PRESENTATION
Mar 28, 2012 Apr 16, 2012
Phase 2 FINAL PROJECT 2 MODIFIED IMPLEMENTATION MODIFIED TESTING PRESENTATION
Apr 18, 2012 Apr 30,2012
Role Actor Diagram
Understand Problems
Establish Outline
Requirement
Select Prototyping
System
Evaluate Prototype
Develop Prototype
Req Engg Domain Expert
Req EnggEnd User
Software Engg.
Project Mgr
Req EnggSoftware
Engg
Domain ExpertEnd-User Software Engg Req Engg
Phase 0 / Phase 1 Phase 2
Phase Deliverable Developers Reviewers
PHASE 0 SOFTWARE PROJECT MANAGEMENT PLAN
KUMARAN BALAJIGOVINDARAJAN
AARTHI
PHASE 1 REQUIREMENTS SPECIFICATION SRIRAMVIGNESHNEHA
BALAJI
PHASE 1 ANALYSIS MODEL BALAJIAARTHIKUMARAN
SRIRAM
PHASE 2 CODE AARTHIBALAJIGOVINDARAJANKUMARANNEHASRIRAMVIGNESH
VIGNESH, NEHA
PHASE 2 SYSTEM TEST KUMARANSRIRAMNEHA
GOVINDARAJAN
PHASE 2 USER DOCUMENTATION BALAJIVIGNESHGOVINDARAJAN
KUMARAN
Team Roles & Responsibilities
PHASE MANAGEMENTFUNCTIONAL
DUTY RESPONSIBLE
PRELIMINARY PROJECT PLAN
GOVINDARAJAN DOCUMENTATION
GOVINDARAJAN, AARTHI, BALAJI, NEHA,
KUMARAN, SRIRAM, VIGNESH
INTERIM PHASE IKUMARAN,
VIGNESH
DOCUMENTATION
AARTHI, SRIRAM, BALAJI,
VIGNESH
PRESENTATIONGOVINDARAJAN,
NEHA, KUMARAN
Team Functionality
PROBLEMS AND SOLUTIONS
Possible ProblemsIncompleteness
Undefined terms Incomplete list
UncertaintyDubious termsUnclear phrases
InconsistencyContradictory Statements
Problem Detection & Solution Proposal
Detect the problem
Suggest appropriate solutions
Use different approaches to solve
List the essential requirements for solving
REQUIREMENT ANALYSIS
Requirement Types
Requirements
Domain FunctionalNon
Functional
Reflects the environment in which the
system operates
Criteria to judge the
operation of the system
Reflects the set of inputs, its behaviors and resulting
outputs
Domain Requirements
DR-01 : Emergency DR-02 : Speech2Text
DR-03 : Text2Speech DR-04 : FaceLook
Domain RequirementsDR-05 : MyPage DR-06 : PillTracker
DR-07 : MyShelf DR-08 : DietManager
Domain Requirements
DR-09 : Walk-O-Meter DR-10 : PicTalk
Functional RequirementsDomain
Requirement(DR)
Functional Requirement
(FR)
Event Generated by End-User System Response to the Event
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 and feed the voice input
Voice input is converted in textual form
DR-03 FR-03 Touch the Text2Speech Icon and feed the textual input
Textual input is processed into a voice output
DR-04 FR-04 Touch the FaceLook Icon to search contacts by
pictures/names
Displays all the details of the selected contact
DR-05 FR-05 Touch the MyPage Icon to retrieve information about
one’s self
Displays all personal information stored by the
user
Functional RequirementsDomain
Requirement(DR)
Functional Requirement
(FR)
Event Generated by End-User System Response to the Event
DR-06 FR-06 Touch the PillTracker Iconto store the medicine stock and
the intake timings
Alerts the user at the stored time to consume the
medicine and updates medicine stock.
DR-07 FR-07 Touch the MyShelf Icon to store the information about the
location of the frequently used items at home.
Prompts the user about the location on selecting the
item
DR-08 FR-08 Touch the DietManager Icon to specify the blood sugar level,
cholesterol level, etc.
Displays the list of food items one should and should
not consume
DR-09 FR-09 Touch the Walk-O-Meter Icon to specify the start time/end
time of a walking session
Displays the distance covered and calories burnt
in that session
DR-10 FR-10 Touch the PicTalk Icon to convey a message by choosing
the pictures available
Displays and produces the sound for the chosen picture
Non-Functional Requirements
NON FUNCTIONAL REQUIREMENTS
SYSTEM SPECIFICUSER SPECIFIC
User Specific NFR
USER SPECIFIED
NFR
RELIABILITY
SCALABILITY
USABILITY
EMERGENCYSPEECH2TEXTPILLTRACKER
ALL THE DRs
PICTALKMYSHELF
FACELOOK
System Specific NFR
SYSTEM SPECIFIED
NFR
TESTABILITY
INTEROPERABILITY
EXTENSIBILITY
CHECK AGAINST VARIOUS
HYPOTHESIS
IMPORTING/EXPORTING
DATA
SHOULD WORK ON VARIOUS
PLATFORMS
Better AnalysisUnambiguous: 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
WRITING REQUIREMENT SPECIFICATIONS
Guidelines
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
MODEL DEVELOPMENT
H.O.P.E. Home Screen
Sample Application Layout
A prototype of the application Speach2Text –
STEP 1
Sample prototype of the
app “Speech2Text”
STEP 1
Sample Application Layout
Sample prototype of the
app “Speech2Text”
STEP 2
Why we stand out of the crowd??
Self Explanatory – Icons/App Names
Unique Apps
V Model Wide Area of Service
User Friendly Layout
FUTURE ENHANCEMENT
One Touch Emergency Text/ Voice Message
Wireless Medical Report Transmission
Profile Retrieval Using Image Recognition
Change Accommodation Percentage
Project Status (completed stage) Accommodation Percentage
Requirement 40-55%
Analysis 15-40%
Design 10-15%
Implementation 0-10%
Recommended