TEAM NAME : ANDROMEDA Instructor: Prof. Dr. Lawrence Chung TA: Rutvij Mehta.

Slides:



Advertisements
Similar presentations
Morag Ferguson and Susan Shandley Educational Projects Managers
Advertisements

© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
System Requirements Specification INSTRUCTOR : Dr. LAWRENCE CHUNG
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
Martin Luther King, Jr. on Commitment Create a Noble Mission Around Which Everyone Can Rally.
Hestia: Aarthi Giridharan Govindarajan Panneerselvam Nirmal Chander Shesha Chandrika Moka Sriram Rajendran Suryanarayanan Ganesh Melarkode Vignesh Swaminathan.
Dynamic Systems Development Method (DSDM)
Final Presentation Team Crutch. Agenda Process – Justin Vision Document Issues Use Case Diagram Domain Diagram SIG Prototype Why Team Crutch?
Evaluation of A PDA Based Clinical Handover System Dr Marilyn R McGee-Lennon University of Glasgow SIHI, Portsmouth, Sept 2007 HECTOR.
Project Access Hope BIS 412 Systems Analysis and Design Applications Spring 2004 Project Developers: Philip Kelly Joseph Shaughnessy Daniel Vickers Project.
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Project BlueDate. The development team Petrus Bergman - Configuration manager Oskar Holmlund – Requirements manager Mikael Nilsson – Design manager Kristian.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
Chapter 3: The Project Management Process Groups
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
CSE Senior Design II Staged Delivery Instructor: Mike O’Dell.
Incremental Model Requirements phase Verify Specification phase Verify
Spencer “Pete” BrewerJason McKenzie Roberto CastrillonLong Ngo Mukhtar EsmailCuong Nguyen Bilal HasanOmeed Safi Nestor HernandezGrace St. Clair Bjorn Holm-PendersonThanh.
Office of Information Technology (OIT) PROJECT INITIATION DOCUMENTS - BUSINESS CASE, ALTERNATIVE ANALYSIS AND STATEMENT OF WORK (SOW)
SoNDa Sensor Network for Data Explore! 1. SoNDa Sensor Network for Data Explore! KEYWORDS Wireless Sensors Communication 2.
Design Problems  Limited Market  Too Many Other Devices  No Standard Design Among Devices.
Marbles Your Name. Project Phase 1 System Requirements Specification Instructor:Dr. Lawrence Chung Teaching Assistant:Rutvij Mehta Subject:Advanced Requirement.
Phase II Instructor: Dr. Lawrence Chung Rachel Bock, Ruben Cavazos, Chih-Lin Cheng, Victor Isbell, Swathi Kandimalla, Nikhil Mishra, Amy Polcari, Ramon.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
TEAM NAME : ANDROMEDA Instructor: Prof. Dr. Lawrence Chung.
Solution Overview for NIPDEC- CDAP July 15, 2005.
Team Crutch. Vision Statement Team crutch aims to develop portable, inexpensive, user-friendly software for the Android platform that mitigates communication.
By: HelpSoft9 Allen Helton, Chris Mudd, Aaron Jacobs, Jeff Allain, Jessi Cardoso, Matthew Jacobs, Prerak Patel, Richard Vanderdys, Saurav Shrestha.
Making Business Continuity Child’s Play Solutions Ltd Business Continuity Management Contact details: Contact : Mick O’Regan Mobile :
THE REGIONAL MUNICIPALITY OF YORK Information Technology Strategy & 5 Year Plan.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
IW:LEARN TDA/SAP Training Course
Software Development Process and Management (or how to be officious and unpopular)
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
CS Tutorial 4 Frid. Oct 16 th, 2009 Prototype Tutorial.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Ways of Augmenting Communication through Technology KEYCOMM-Lothian Communication Technology Service.
HOPE Helping Our People Easily Phase I - Interim Team KRAFT.
Audience Analysis & Usability. The Writing Process Focusing and Planning Drafting Assessing & Evaluating Assessing & Editing Publishing and Evaluating.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
The SSMP Process 1. The Servicing and Settlement Master Plan A plan to encompass the community’s visions and ideas, while approaching planning and servicing.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
PROC-1 1. Software Development Process. PROC-2 A Process Software Development Process User’s Requirements Software System Unified Process: Component Based.
Meeting Scheduler Carl Fernandes Mahbubur Rahman Haque Muaz Jamshed Rahul Kotian Ramakrishnan Jayavelu Sujith John Zachariah Interim Presentation -2 on.
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Team Skill 6: Building the Right System Assessing Requirements Quality (29)
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Global policy framework and standards on ICT accessibility UNDESA/DSPD FPRUM DISABILITY INCLUSION AND ACCESSIBLE URBAN DEVELOPMENT Nairobi, Kenya 28 October.
Stand Up Comedy Project/Product Management
© Bennett, McRobb and Farmer 2005
National Single Assessment Process Action Team Glenys Jones Director of Adult Services.
Sistemas de Información Agosto-Diciembre 2007 Sesión # 9.
James Catalano Tajkia Hasan Chris Hluchan Monish Modi Justin Olguin Swetha Ravikumar Brian Stiles Michael Sturm Requirements Engineering Fall 2010.
Mobile AAC Application for Sentence Creation Team Members: Kevin Greene, Christina Fries, Wei Liao, Hien Huynh, Jiho Kim, Apoorva Dewangan Mentor: James.
Lectures 2 & 3: Software Process Models Neelam Gupta.
44222: Information Systems Development
Rule-based Context-aware Adaptation Using a Goal-Oriented Ontology Hongyuan Wang (Jilin University, China) Rutvij Mehta (The University of Texas at Dallas,USA)
 Expensive, inconvenient, and it pollutes the environment.  And it is getting worse!
> Blueprint Executive Summary >. Presentation Purpose; This Executive Summary captures the key details and outputs which merit stakeholder alignment to.
Software Myths Software is easy to change
Business Writing Final Project
Information Systems Development (ISD) Systems Development Life Cycle
CS/SE ADVANCED SOFTWARE ARCHITECTURE AND DESIGN FALL 2015
Presentation transcript:

TEAM NAME : ANDROMEDA Instructor: Prof. Dr. Lawrence Chung TA: Rutvij Mehta

Aarthi Giridharan (lead) Balaji Shanmugam Govindarajan Panneerselvam Kumaran Senapathy Neha Malloli Sriram Sridharan Vignesh Swaminathan

Synopsis Problem and Vision Problem Statement Requirement Prioritization Implementation Details Demo Why we stand out… Creeping Rate

To-Be= As-Is – Problems HOPE = ( Devices currently developed by Augmentative and Alternative Communication (AAC ) – (bulky to handle and are not multi-functional) VISION – > Keep It Simple…

S. No.The Problem ofMemory loss 1AffectsElderly people The impact of which isUnable to remember things, people and places Solution for which isApplications like PillTracker, Facelook, MyShelf, MyPage S. No.The Problem ofImmobility 2AffectsElderly people (bedridden) The impact of which isInability to take care of themselves Solution for which isApplications like Help, Emergency

S. No.The Problem ofVision Impairment 4AffectsPeople with weak vision The impact of which isDifficulty in viewing Solution for which isApplications like Speech2Text S. No.The Problem ofSpeech Impairment 3AffectsPeople with speech imparity The impact of which isInability to orally communicate Solution for which isApplications like Help, Emergency, PicTalk, Text2Speech

S. No.The Problem ofUnable to monitor health 5AffectsHealth conscious people The impact of which isNeed for a doctor to be consulted every time Solution for which isApplications like Diet Manager, Walk-o-meter

VISION MEMORY SPEECHMOBILITYHEALTH

ANDROMEDA’s variant of HOPE uses: The SPIRAL MODEL with two spirals : Phase-1 and Phase-2  Phase-2: The Incremental and Iterative model to develop and implement the prototype

ISSUES CHANGED REQs TRACEABILITY ENSURED MAPPED WITH PHASE 1

ISSUERESTRICTED EMERGENCY CALL STATUSINADEQUATE REASONUNABLE TO CALL THE EMERGENCY CONTACT OPTIONS CONSIDERED1.INCLUDE A SEPARATE BUTTON THAT ENABLES CALLING THE EMERGENCY CONTACT. 2.REMOVE THE FEATURE. DECISIONOPTION 1 HOW DOES IT IMPROVEENABLES CALLING THE EMERGENCY CONTACT AS AN ALTERNATIVE TO CALL 911 TRACEABILITYFR-01

Considered the major problems that the user faces Traceability Systematic decision making Spiral model Pareto principle

Key Features: Help Button Emergency MyShelf PicTalk MyPage FaceLook

FeatureCreeping Rate Emergency0-10% Help0-10% FaceLook 0-10% PicTalk0-5% MyPage0-15% MyShelf0-10% Feature specific creeping rate Project Status (completed stage)Accommodation Percentage Final Phase-1: Final Product Specification. Changes in Product requirements have to freeze 15-40% Interim Phase-2: Final Design. Changes in requirement specification have to freeze 10-15% Final Phase-2: Final Implementation. Changes in design have to freeze 0-10%

“PEOPLE WITH SMARTPHONE WILL HAVE ANDROMEDA’S HOPE; PEOPLE WITHOUT ONE WILL HAVE ANDROMEDA’S LOVE!!”