Editor Version Comment



Download 0.58 Mb.
Page1/9
Date30.06.2017
Size0.58 Mb.
  1   2   3   4   5   6   7   8   9
























Revision History

Editor

Version

Comment

Vignesh

0.31

Initial template created

Neha

0.32

Updated section 2

Govindarajan

0.33

First draft of section 3

Aarthi

0.34

Updated functional requirements

Sriram

0.35

Cleaned up world issues

Kumaran

0.36

Introduced a section for testing

Balaji

0.37

Inserted Screenshots for all the features implemented

Sriram

0.38

Defined feature specific creeping rate

Neha

0.39

Cleaned up content in many areas and formatting

Aarthi

0.40

Final Phase-II WRS document

PROCESS


We, the Andromeda team have followed a definite process in creating this HOPE system. We had gathered and discussed the requirements from lot of resources like web, by taking to elderly people who might use our system and based on our own experience from our grandparents and from the elderly people we had come across.

Any requirements which use the term shall indicate that that functionality is critical core functionality that will be implemented in the first version of the HOPE system. Other functionality that is identified by our requirements gathering process that is not considered critical core functionality and may be implemented instead in a later version of the HOPE system will be referenced using the word ‘will’.

The software process that we are using in this system is Spiral model. Change is inevitable in software projects so our process is designed to adapt to the changes and allow modification where necessary to the requirements and other documents.

Process Model

For the implementation of HOPE system, we will follow the Spiral Model. The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. This model of development combines the features of the prototyping and the waterfall model. The spiral model is intended for large, expensive and complicated projects. The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model. It allows for incremental releases of the product, or incremental refinement through each time around the spiral. The spiral model also explicitly includes risk management within software development. Identifying major risks, both technical and managerial, and determining how to lessen the risk helps keep the software development process under control.



capture

Figure 1: Spiral model




Directory: ~chung
~chung -> Advanced Requirements Engineering Human Reliability Analysis
~chung -> A goal-oriented simulation approach for obtaining good private cloud-based system architectures
~chung -> Hope project Plan Version 6 September 1, 2010
~chung -> Marvel Electronics and Home Entertainment e-store Project
~chung -> Se 4351. 001 Software Requirements
~chung -> Team Awesome hope
~chung -> Weekly Android irc with Android developers
~chung -> Hope (Helping Old People Easily) Phone Application System Preliminary Project Plan (Phase 0) se 4351 Section 001 Team Name: HelpSoft 9
~chung -> Hope (Helping Our People Easily) Mobile Phone Application System wrs document Phase 2 Final se 4351 Section 001 Team Name: Team Awesome
~chung -> Hope (Helping Our People Easily) Mobile Phone Application System Software Project Management Plan Phase 2 Final se 4351 Section 001 Team Name: Team Awesome

Download 0.58 Mb.

Share with your friends:
  1   2   3   4   5   6   7   8   9




The database is protected by copyright ©ininet.org 2020
send message

    Main page