420 likes | 649 Views
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.
E N D
H. O. P. E.(Helping “Our” People Easily) TEAM NAME : ANDROMEDA Instructor: Prof. Dr. Lawrence Chung
AarthiGiridharan (lead) • BalajiShanmugam • GovindarajanPanneerselvam • KumaranSenapathy • Neha Malloli • SriramSridharan • VigneshSwaminathan Crew Members
System Requirements Specification – Synopsis • Project Outline • Requirement Engineering Process • Problems & Proposed Solutions • Requirement Analysis • Writing Specifications • Model Development • Future Enhancements Project : Phase 1 (Interim)
Present Scenario 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 • 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. Why this project?
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. What the project deals with?
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. How is this possible?
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. Process
Phase 0 / Phase 1 Phase 2 Understand Problems Establish Outline Requirement Select Prototyping System Develop Prototype Evaluate Prototype ReqEnggDomain Expert ReqEnggEnd User Software Engg.Project Mgr ReqEnggSoftware Engg Domain ExpertEnd-User Software EnggReqEngg Role Actor Diagram
Incompleteness • Undefined terms • Incomplete list • Uncertainty • Dubious terms • Unclear phrases • Inconsistency • Contradictory Statements Possible Problems
Detect the problem • Suggest appropriate solutions • Use different approaches to solve • List the essential requirements for solving Problem Detection & Solution Proposal
Requirements Domain Functional Non Functional Requirement Types Reflects the set of inputs, its behaviors and resulting outputs Criteria to judge the operation of the system Reflects the environment in which the system operates
DR-01 : Emergency DR-02 : Speech2Text DR-04 : FaceLook DR-03 : Text2Speech Domain Requirements
DR-05 : MyPage DR-06 : PillTracker DR-07 : MyShelf DR-08 : DietManager Domain Requirements
DR-09 : Walk-O-Meter DR-10 : PicTalk Domain Requirements
NON FUNCTIONAL REQUIREMENTS USER SPECIFIC SYSTEM SPECIFIC Non-Functional Requirements
RELIABILITY EMERGENCY SPEECH2TEXT PILLTRACKER USER SPECIFIED NFR SCALABILITY PICTALK MYSHELF FACELOOK User Specific NFR USABILITY ALL THE DRs
TESTABILITY CHECK AGAINST VARIOUS HYPOTHESIS SYSTEM SPECIFIED NFR INTEROPERABILITY SHOULD WORK ON VARIOUS PLATFORMS System Specific NFR EXTENSIBILITY IMPORTING/ 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 Better Analysis
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 Guidelines
Sample prototype of the app “Speech2Text” STEP 1 A prototype of the application Speach2Text – STEP 1 Sample Application Layout
Sample prototype of the app “Speech2Text” STEP 2 Sample Application Layout
Self Explanatory – Icons/App Names User Friendly Layout Why we stand out of the crowd?? Unique Apps Wide Area of Service V Model
One Touch Emergency Text/ Voice Message Wireless Medical Report Transmission Profile Retrieval Using Image Recognition