Pill Assisted Living (PAL)
Process Specification
Version 2.2
Revision History
Name
Date
Reason For Changes
Version
Outline
11/4/12
More details added
1.0
Rough Interim Phase II
Vision
11/11/12
Edited and revised
1.1
Final Interim Phase II Vision
11/13/12
Final of phase II has
begun
1.2
Updated Phase II Vision
11/19/12
More details added
2.0
Rough Final Phase II Vision
11/30/12
Edited and revised
2.1
Final Final Phase II Vision
12/4/12
No Changes
2.2
Table of Contents
Revision History
Table of Contents
1. Introduction
1.1 Spiral Model
1.2 AGILE
1.3 Deliverables
1.4 Team Members
1.5 Team Lead Schedule
2. Functional Requirements
3. Non-Functional Requirements
3.1 Privacy/Security
3.2 Accountability
3.3 Availability/Accessibility
1. Introduction
1.1 Spiral Model
We are using a two phase Spiral Model for this project. The phases will each have all
four activities of Elicitation, Negotiation, Specification, and Validation. This approach is
iterative and will help modularize the process of developing an application for effective
time and resource use.
1.2 AGILE
We are using the AGILE technique for this project. Since we are working with a smaller
project, the low documentation requirements of AGILE are very convenient for us, and
we can meet the requirement for high levels of communication by holding regular group
meetings and by using email and text messaging to contact each other outside of group
meetings.
1.3 Deliverables
○ 9/8/12 - Preliminary Project Plan
○ 10/2/12 - Phase I Interim presentation and Interim WRS document
○ 10/18/12 - Phase I Final WRS document
○ 11/13/12 - Phase II Interim Project submission
○ 12/4/12 - 12/6/12 - Phase II Final Project submission, presentation, and demo
1.4 Team Members
Daniel Zinni
Nicholas Charlton
Brendan Shaklovitz
Camron Salisbury
Garrett Leach
Kevin Mott
Jonathon Kozak
Jia You (Justin)
Eric Hsu
1.5 Team Lead Schedule
There will be a different set of team leads for each phase of the project. Each team
member must be a team lead at least once during the project.
PHASE I
a) Interim:
Brendan Shaklovitz
Nicholas Charlton
Daniel Zinni
b) Final:
Kevin Mott
Jia You
PHASE II
a) Interim:
Camron Salisbury
Jonathon Kozak
b) Final:
Garrett Leach
Eric Hsu
2. Functional Requirements
The Functional Requirements for the Phase II are everything we hope to produce. They include
the WRS document, the Vision document (which together make up the Product Specification),
the Process Specification (this document), the Final Project Plan, the final Presentation, and of
course, our application. They are shown in more detail in the IDEF model below.
Figure 1: Process Functional Requirements IDEF model
3.
Non-Functional Requirements
3.1 Privacy/Security
Don’t allow other teams to know what we are planning and producing.
Figure 2: Security NFR Framework Model
3.2 Accountability
Create and adhere to guidelines of what we want done by each meeting. These guidelines can
be created from the meeting minutes.
Figure 3: Accountability NFR Framework Model
3.3 Availability/Accessibility
Always be able to get in contact with one another (through e-mail, texting, meetings, and
Google docs)
Figure 4: Availability NFR Framework Model