Gryphon SOW by pOYowRkL

VIEWS: 6 PAGES: 13

									Carnegie Mellon University           CMU-MSE-GRYPHON-SOW–2.0
School of Computer Science                         Spring 2000
Master of Software Engineering




                                             Gryphon

                                 Statement of Work
                                            Version 2.0
                                           May 11, 2000



                                                  Zia Syed
                                              George Tsang
                                                   Sid Kaul
Document Information

Title                 Statement of Work
Author(s)             George Tsang
Reviewer(s)           All Team Members, Technical Writer
Team name             Gryphon
Team members          Andy Zhou, Bob Lindman, George Tsang, Sid Kaul, Steve Schirripa, Zia Syed
Project mentors       Anthony Lattanze, Cliff Huff
Editor                George Tsang
Type of report        Managerial
Software used         MS Word 2000
Templates used        Gryphon Document Template
Style guide           Software Engineering Institute Style Guide




Gryphon  SOW version 2.0                                                                         2
Document Revisions

     Rev.    Date             Author(s)                       Comment
     1.0     Nov. 18, 1999    Zia Syed (smzia@cs.cmu.edu)     Initial creation
     1.11    Nov. 23, 1999    Zia Syed                        Changes suggested in the internal inspection
                                                              incorporated.
     1.3     Nov. 23, 1999    Robin Senor
     1.4     Nov. 29, 1999    Zia Syed                        Mainly changed GAPS to GZAPS, the developers to
                                                              the Gryphon team and few other capitalization
                                                              changes.
     1.5     Dec. 6, 1999     Zia Syed                        Changes suggested in external inspection
                                                              incorporated.
     1.6     Apr. 23, 2000    George Tsang (get@cs.cmu.edu)   Changes made due to the change of the project scope
                                                              and the final deliverables. Incorporate additional
                                                              parties that are related to the project.
     1.7     April 25, 2000   Anne Jackson                    Made editing corrections; moved acronyms to
                              (annej@andrew.cmu.edu)          beginning; no major content changes
     1.8     April 27, 2000   George Tsang                    Incorporated changes suggested by mentor Cliff Huff
                                                              and technical writer Anne Jackson, added RRLOE
                                                              information
     1.9     May 11, 2000     Sid Kaul (kaulsid@cs.cmu.edu)   Incorporated changes that came out of the review of
                                                              the SOW, also made some structural and stylistic
                                                              changes in the document. Finalized the version 2.0




Gryphon  SOW version 2.0                                                                                           3
Document Approvals

The following signatures are required for approval of this document. Note, however, that since the
MSE Studio role assignments will change during the course of the project, the respective names should
be updated as needed.




___________________________________________               ______________________
KD Van Drie, Volant Systems                               Date
Client


___________________________________________               ______________________
Bob Lindman, CMU MSE Program                              Date
Gryphon Team Lead


___________________________________________               ______________________
Sid Kaul, CMU MSE Program                                 Date
Gryphon Quality Assurance Manager


___________________________________________               ______________________
Tony Lattanze,                                            Date
CMU School of Computer Science faculty
Studio Mentor


___________________________________________               ______________________
Cliff Huff, SEI Technical Staff                           Date
Studio Mentor




Gryphon  SOW version 2.0                                                                           4
1           Acronyms .................................................................................................................... 6

2           Introduction ................................................................................................................. 7
 2.1        Purpose....................................................................................................................................................................... 7
 2.2        Audience .................................................................................................................................................................... 7
 2.3        Scope .......................................................................................................................................................................... 7
 2.4        References .................................................................................................................................................................. 7


3           Project Overview ......................................................................................................... 8
 3.1        Background ................................................................................................................................................................ 8
  3.1.1       Advanced Qualification Program (AQP) .............................................................................................................. 8
  3.1.2       Zephyr AQP System (ZAPS) ................................................................................................................................ 8
 3.2        Ongoing Development of ZAPS ................................................................................................................................ 8
 3.3        RRLOE by University of Central Florida .................................................................................................................. 8
 3.4        Gryphon Zephyr AQP System (GZAPS) ................................................................................................................... 9


4           Project Organization ................................................................................................. 10
 4.1    Resources ................................................................................................................................................................. 10
  4.1.1   Personnel ............................................................................................................................................................. 10
  4.1.2   Time .................................................................................................................................................................... 10
 4.2    Deliverables ............................................................................................................................................................. 11


5           Responsibilities ........................................................................................................ 12
 5.1    Joint Responsibilities ............................................................................................................................................... 12
  5.1.1    Points of Contact ................................................................................................................................................. 12
  5.1.2    Meeting Management .......................................................................................................................................... 12
 5.2    Gryphon Team ......................................................................................................................................................... 13
 5.3    Client ........................................................................................................................................................................ 13




Gryphon  SOW version 2.0                                                                                                                                                                  5
1 Acronyms

          AQP               Advanced Qualification Program
          CMU               Carnegie Mellon University
          ER                Entity-Relationship
          FAA               Federal Aviation Administration
          GZAPS             Gryphon Zephyr AQP System
          HLA               High Level Architecture
          HLD               High Level Design
          MSE               Master of Software Engineering
          QA                Quality Assurance
          SCM               Software Configuration Management
          SEI               Software Engineering Institute
          SOW               Statement of Work
          SPMP              Software Project Management Plan
          SRS               Software Requirements Specification
          ZAPS              Zephyr AQP System




Gryphon  SOW version 2.0                                         6
2 Introduction

2.1    Purpose
This document establishes a written agreement between Volant Systems, represented by KD Van Drie,
hereafter referred to as the client, and the members of the 1999-2000 Masters of Software Engineering
(MSE) Gryphon studio project team at Carnegie Mellon University (CMU), hereafter referred to as the
Gryphon team.

By accepting this document, the parties agree to provide products and services subject to the conditions and
limitations described in the sections below. While the statement of work is not a legal contract, both parties
are expected to observe the terms of this document in good faith.

2.2    Audience
The readers of the document include the Gryphon team, the client and the mentors of the Gryphon team.

2.3    Scope
The provisions stated in this agreement shall be in effect for the duration of the 1999-2000 MSE studio
project. The project shall end on Aug. 4, 2000.

After Aug. 4, 2000, all executables, source code, documentation, and other work products developed by the
Gryphon team will become the intellectual property of Volant Systems, and the Gryphon team will have no
further responsibilities for software development or maintenance.


2.4    References
[1]      Gryphon; Software Project Management Plan (SPMP): CMU-MSE-GRYPHON-SPMP-1.0, 1999
[2]      MSE Studio; Studio Process Handbook: CMU-MSE-STUDIO-PROCESSHBK-1.0, 1997
[3]      Gryphon; Risks and Goals (Draft): CMU-MSE-GRYPHON-RISKS&GOALS-DRAFT, 1999




Gryphon  SOW version 2.0                                                                                   7
3 Project Overview

3.1    Background

3.1.1 Advanced Qualification Program (AQP)
In the United States, the Federal Aviation Administration (FAA) governs the training of aircrew. Each year
the FAA, responding to technological advances and safety incidents, adds additional matter to their existing
list of training requirements. Pilots need to retrain to cope with these changes. For many airlines, low-cost
regional carriers in particular, training in the manner prescribed by the FAA requirements is difficult and
too expensive. To address the growing number of complaints about this training system, the FAA
introduced the Advanced Qualification Program (AQP).
AQP is a voluntary, alternative means of qualifying, certifying, training and otherwise ensuring the
competency of flight personnel. Its purpose is to increase airline safety through higher qualification
standards, while at the same time encouraging innovation and regulatory flexibility. This goal is
accomplished by giving airlines the power to create and maintain their own customized training programs
based on instructional objectives derived from aircraft-specific task analyses. The FAA oversees the AQP
program by requiring the airlines to periodically submit training documents for review and approval.

3.1.2 Zephyr AQP System (ZAPS)
During the 1998–1999 MSE studio project, the Zephyr Team worked with Volant Systems to develop the
Task Analysis component of the AQP System, called the Zephyr AQP System (ZAPS).
ZAPS’ goals were to give airlines the ability to:

1.    Create and maintain task analyses for each type of aircraft in the airline’s fleet.
2.    Create and maintain the qualification standards associated with each task analysis.
3.    Manage standardization issues both within and across task analyses.
4.    Develop and manage the curriculum outlines used to teach the airline’s proficiency objectives.
5.    Collect and analyze data generated by the training activities within the AQP.
6.    Generate the required AQP documentation for submission to the FAA.

The Zephyr team accomplished part of the first three goals—they developed a data model for task analysis,
qualification standards and curriculum development—however, the data model needs to be both validated
and performance-tuned.


3.2    Ongoing Development of ZAPS
Due to the fact that Zephyr team only finished part of the first 3 goals, one of the Zephyr team’s member,
Dave Smith, made an agreement with the client to continue working on ZAPS.


3.3    RRLOE by University of Central Florida
Rapidly Reconfigurable Event-Set Based Line-Oriented Evaluations Generator (RRLOE) is a tool
developed by University of Central Florida. RRLOE provides some of the functional requirements for line
oriented evaluation and it can be a good reference in the requirements elicitation process.




Gryphon  SOW version 2.0                                                                                    8
3.4    Gryphon Zephyr AQP System (GZAPS)

For the 1999 – 2000 year, Gryphon is continuing development on the AQP system; this project will be
called the Gryphon Zephyr AQP System (GZAPS). The first stage of the requirement elicitation was
finished in late March. Based on the findings during the requirements elicitation and a comprehensive risk
analysis done by Gryphon [3], Gryphon team and the client came to an agreement to develop part of the
AQP that is capable of developing and managing the curriculum outlines used to teach the airline’s
proficiency objectives as the final deliverable, the following goals are set for GZAPS:

1.    Conduct the second stage of requirements elicitation of the final deliverable using rapid prototyping.
2.    Develop a data model for use with the final deliverable.
3.    Fine-tune and validate the data model.
4.    Develop an SRS to document the requirements elicitation.
5.    Develop user documentation.
6.    Develop and document a high-level design / high-level architecture (HLD/HLA) for GZAPS.
7.    Provided the Gryphon team receives all the necessary source code, documentation of the code and
      data model of Dave’s application by July 1, 2000, Gryphon team will integrate the Dave’s application
      with our application.
8.    Provided the Gryphon team receives all the necessary detailed development documentation and timely
      cooperation of the RRLOE developers by June 10, 2000, the team will integrate or incorporate the
      features of the RRLOE tool into the GZAPS tool.




Gryphon  SOW version 2.0                                                                                      9
4 Project Organization

4.1     Resources
The primary resources available to the Gryphon team are the time and effort of the Gryphon team
members.

Additional resources include the personal computers in the MSE work area and a limited library of
software applications. Any software purchased for the completion of the project will remain the property of
the purchaser at the completion of the project.

4.1.1 Personnel
The Gryphon team is composed of six MSE graduate students. Additional resources include the client,
MSE studio staff, advisors, mentors, a technical writer (for two semesters) and supporting MSE studio
process groups. Table 1 (below) gives a complete listing of the personnel available to the Gryphon Project.

      PERSONNEL                RESOURCE                     COMMENT
      Client                   KD Van Drie                  Co-founder – Volant Systems
      Gryphon Team             Sid Kaul                     MSE student
                               Bob Lindman                  MSE student
                               Steve Schirripa              MSE student
                               Zia Syed                     MSE student
                               George Tsang                 MSE student
                               Andy Zhou                    MSE student
      MSE Staff/Advisors       James Tomayko                Director, CMU MSE program
                               Linda Hutz Pesante           SEI – Mentor, Oral and written
                                                            communication
      Mentors                  Anthony Lattanze             Senior Lecturer, CMU MSE program
                               Cliff Huff                   Member of SEI technical staff
      Studio Resources         Technical Writer             MAPW student assigned on a semester
                                                            basis
                               Studio Matrix Roles          Quality Assurance, SCM, Process, etc.
        Table 1: Project Personnel


4.1.2 Time
As a student in the MSE studio class, each Gryphon team member has a fixed amount of time available for
the project. During Fall 1999 and Spring 2000 semesters, each student is expected to devote a total of 12
hours per week to the Gryphon project, their MSE matrix roles, and studio training. During the Summer
2000 semester, each student is expected to devote 48 hours per week to the project. These hours include the
time spent with mentors, studio classes and time spent working on any studio-related tasks (document
inspections, team meetings, tool development, etc.)

The scope of the project is somewhat limited in that the required development effort must fit into the
available time of the studio project.




Gryphon  SOW version 2.0                                                                                10
4.2    Deliverables
The following information is intended to give a high-level overview of the planned deliverables for
GZAPS. A more detailed schedule is contained in the GZAPS Software Project Management Plan [1].
The Gryphon team will provide the client with the following work products on or before the dates listed
below in Table 2.

         DELIVERABLE                                         DATE
         Draft Software Requirements Specification           May 5, 2000
         (SRS) for Curriculum Development
         Final Software Requirements Specification (SRS)     August 4, 2000
         for Curriculum Development
         Software Architecture Design                        August 4, 2000
         Data Model (ER diagram and database design)
         Development environment                             August 4, 2000
         Developers Guide
         Users Manual
         Source code, executables, database schema
         Description of build environment
       Table 2: Gryphon Team Deliverables




Gryphon  SOW version 2.0                                                                                 11
5 Responsibilities

5.1       Joint Responsibilities

5.1.1 Point of Contact
Specific individuals have been designated to serve as the points of contact for each party. Sid Kaul will
serve as the Gryphon team’s client liaison. Bob Lindman will be the backup client liaison. KD Van Drie,
co-founder of Volant Systems, will represent the client. These assignments will be in effect for the duration
of the project.

Project-related decisions and administrative details will be communicated between the points of contact.
For technical questions and issues, individual Gryphon team members will be encouraged to communicate
directly with the person most able to provide the necessary information. Any decision and commitments
made during such interactions will be communicated to all the Gryphon team members, their mentors and
to the client.


5.1.2 Meeting Management
The Gryphon team will use meeting management techniques to encourage and facilitate efficient meetings.
Common meeting management techniques include the following:
          Either the client or the Gryphon team can initiate meetings.
          The person who calls the meeting will distribute a detailed agenda at least 24 hours, preferably 48
           hours, in advance.
          Prior to arriving at the meeting, attendees are expected to have read the agenda and completed any
           requested pre-meeting preparation.
          Attendees who cannot attend the meeting should notify the caller of the meeting, especially if they
           appear on the agenda or their presence is required to make a decision .

Additional details regarding meeting management can be found in the MSE Studio Process Handbook [2].




Gryphon  SOW version 2.0                                                                                  12
5.2    Gryphon Team
The Gryphon team members’ responsibilities under this agreement are as follows:

1.    Provide all the deliverables described in the Gryphon SRS.
2.    Provide the documentation and any additional artifacts relevant to GZAPS as specified in the GZAPS
      Software Project Management Plan [1].
3.    Provide the client with the findings of the Gryphon team’s technical investigations upon request in a
      format agreed by both the client and the Gryphon team.
4.    Reply to change requests from the client within one week in a format agreed by both the client and the
      Gryphon team. This reply will include an assessment of the impact of the change on project schedule
      and/or functionality.

5.3    Client
The project schedule relies on the client fulfilling the responsibilities listed below. Failure to do so may
prevent the Gryphon team from achieving its promised delivery dates. The client’s responsibilities under
this agreement are as follows:

1.    Maintain timely and regular communication with the Gryphon team via the team client liaison,
      replying to their requests within two (if urgent or critical) or five (if non-critical) business days of
      identifying the issue.
2.    Keep the Gryphon team informed of all issues and events that might affect the development of the
      Gryphon Project. The client shall provide change requests in writing (e-mail or written memo) to
      Gryphon team within one week of the identification of the need for a change.
3.    Work closely with the Gryphon team throughout the project lifecycle. In particular, the client will
      provide timely input to Gryphon team at those points in the project life cycle when client-driven
      choices must be made.
4.    Prepare for and attend meetings as agreed by both the Gryphon team and the client. This will allow
      the client to track development progress and be an accessible resource for the developers.
5.    Develop acceptance criteria for all software deliverables with input from the Gryphon team. These
      criteria will be documented in the Gryphon SRS.
6.    Provide the Gryphon team with access to any domain-specific resources that are pertinent to the
      project. Examples of resources may include usability test subjects, data format specifications, or
      sample reports.




Gryphon  SOW version 2.0                                                                                        13

								
To top