Docstoc

Title of Document

Document Sample
Title of Document Powered By Docstoc
					Carnegie Mellon University School of Computer Science Master of Software Engineering

Statement of Work

Statement of Work
Version 2.2 March 15, 2002

The Borg Team

Andrew Guletsky Chiharu Kawatake Mike Lewis Darby Mitchell Kate Langdon Kimberly Callaghan

Document Information
Title Author(s) Reviewer(s) Team name Team members Statement of Work Mike Lewis, Darby Mitchell All team members, Kate Langdon, Kimberly Callaghan The Borg Andrew Guletsky, Chiharu Kawatake, Mike Lewis, Darby Mitchell, Kate Langdon (Fall Technical Writer), Kimberly Callaghan (Spring Technical Writer) David Root, Jim Tomayko Kate Langdon, Kimberly Callaghan Managerial MS Word 2000 Borg Document Template Software Engineering Institute Style Guide

Project mentors Editor(s) Type of report Software used Templates used Style guide

Document Revisions
Revision 1.0 2.0 2.1 2.2 Date 11/07/01 02/03/02 03/01/02 03/14/02 Author(s) Mike Lewis Mike Lewis Darby Mitchell Darby Mitchell and Mike Lewis Comments Updated with spring semester changes and incorporated client milestone information Added target dates for all milestones per client request. Revised the M5 guidelines to reflect continuous evolution throughout the project. Added parallelism to deadlines for M2-M4. Added process for M1 modification requests by the client.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

ii

Document Approvals
The following signatures are required for approval of this document. Note, however, that since the MSE Studio roles will change during the course of the project, the respective names should be updated as needed.
___________________________________________ Mike Freed NASA – Client Representative ___________________________________________ Bonnie John Client Representative ___________________________________________ Andrew Guletsky Development Manager ___________________________________________ Chiharu Kawatake Planning and Support Manager ___________________________________________ Mike Lewis Quality Assurance and Process Manager ___________________________________________ Darby Mitchell Team Lead and Client Liaison ___________________________________________ David Root Studio Mentor ___________________________________________ Jim Tomayko Studio Mentor _____________ Date _____________ Date _____________ Date _____________ Date _____________ Date _____________ Date _____________ Date _____________ Date

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

iii

Table of Contents
1 Acronyms ............................................................................................. 1 2 Introduction .......................................................................................... 2
2.1 Purpose ........................................................................................................ 2 2.2 Audience ...................................................................................................... 2 2.3 Scope ........................................................................................................... 2

3 Project Overview .................................................................................. 3
3.1 Apex ............................................................................................................. 3 3.2 Client Goals.................................................................................................. 3 3.3 Project Goals ................................................................................................ 4

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

5 Responsibilities ................................................................................... 6
5.1 Joint Responsibilities .................................................................................... 6 5.1.1 Point of Contact .................................................................................. 6 5.1.2 Meeting Management ......................................................................... 6 5.2 The Borg Team ............................................................................................ 6 5.3 Client ............................................................................................................ 7

6 References............................................................................................ 8 Appendix A ............................................................................................... 9

List of Tables Table 1: Deliverables ...............................................................................................5

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

iv

1 Acronyms
AMBR ARC CM HLA HTML MSE NASA SRS WYSIWYG Agent-based Modeling and Behavior Representation Ames Research Center Configuration Management High Level Architecture HyperText Mark-up Language Master in Software Engineering National Aeronautics and Space Administration Software Requirements Specification What You See Is What You Get

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

1

2 Introduction
2.1 Purpose
This document establishes a written agreement between the National Aeronautics and Space Administration (NASA), with Mike Freed and Bonnie John as the client representatives, hereafter referred to as the client, and the members of the 2001-2002 Master in Software Engineering (MSE) Borg Studio project team at Carnegie Mellon University (CMU), hereafter referred to as the Borg 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 this document include the Borg team, the client, and the project mentors. A secondary audience includes cognitive modelers, user interface designers, and other computer scientists.

2.3 Scope
The provisions stated in this document shall be in effect for the duration of the 2001-2002 MSE studio project. The project shall end on August 9, 2002. After August 9, 2002, all executables, source code, documentation, and other work products developed by the Borg team will become the intellectual property of NASA. The Borg team will not be responsible for future development or maintenance of the software.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

2

3 Project Overview
3.1 Apex
Apex is a simulation environment developed by the NASA Cognition Lab at Ames Research Center (ARC). Its goal is to simulate human behavior in order to assess the potential usability of user interfaces and instructional procedures. To accomplish this task, Apex handles input that describes:     Objects that exist in the simulated world Body parts that humans use to interact with those objects Skill sets that allow the objects to be manipulated Scenarios for using the skill sets

Apex then uses this input to determine a set of actions for the simulated human.

3.2 Client Goals
The client would like to achieve interoperability between Apex and several “useful” applications. The term “useful” designates both tools that would facilitate the creation of simulated worlds and simulation packages that have already created their own simulation worlds. In either case, the goal is to reduce the time and knowledge a modeler would need to create (and use) a simulation world within Apex. Ultimately, the client wishes to lay the groundwork for a general-purpose interoperability solution. The client has indicated several technical challenge areas that need to be considered in order to achieve this goal. They include the following:      Packaging and translating data sent and received by Apex Inter-process communication between Apex and other applications Synchronization between Apex and other applications Adherence to an interoperability standard Creation of general interoperability mechanisms/tools/techniques

The client has proposed the following milestones as a way to address these challenge areas: 1. Allow Apex to interact with an HTML “storyboard.” This addresses a small, but significant data packaging problem in isolation. The system should take HTML output from a standard tool (e.g. Dreamweaver) and translate it into an Apex-usable format. A simple interaction model that avoids communication and synchronization issues is to output a file in the Apex’s LISP-based environment model notation. 2. Identify and allow Apex to interact with an interactive but non-real-time application (e.g. Netscape browser). This addresses issues related to communication but not to synchronization.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

3

3. Allow Apex to interact correctly with some highly interactive application such as XPlane (or other flight simulators). This will require addressing real-time synchronization issues. 4. Allow Apex to interact with AMBR, an HLA-based application. This will be a useful step towards a general interoperability solution for Apex, but will hopefully pose few novel technical problems. 5. Write a manual on the best practices for achieving Apex interoperability. This document shall contain an examination of the challenges encountered for each of the milestones, along with reflections on best practices and a process for achieving the solutions.

3.3 Project Goals
The Borg Team is committed to completing a baseline for M1 as a simple storyboard. A simple storyboard consists of a series of HTML pages with a single image per page. Each image may have one or more hotspots which contain links to other HTML pages. The Borg Team is committed to completing the M5 manual of best practices based on its experiences with the other milestones. This document will be continuously updated as progress is made on each milestone. The document will be periodically reviewed with the client to gather feedback. The Borg Team is committed to initiating M2-M4 in a parallel fashion as prescribed by the client. All milestones (2-4) will be prototyped before design and implementation begins for any of the milestones. Each prototype will be presented to the clients for feedback upon completion. After all the prototypes have been completed, the Borg Team will proceed to design and implementation of M2-M4 incorporating the feedback provided by the clients. Additional iterations will be included as schedule permits. The client has expressed an interest in having a means of adding functionality to the M1 application as additional requirements become available. The following process outlines how the client may initiate these changes:   The client provides a request by email detailing the changes or additions to be made to the M1 application. The Borg team reviews the request and provides an impact assessment to the client outlining how the additional work will be integrated into the current schedule. This will include potential changes to other milestone deadlines and/or reduction of scope for the remainder of the project to accommodate the additional work. At the next client meeting, the client and the Borg Team will discuss the changes and the impact, and arrive at a consensus on changes to the milestone plan to include the additional functionality for M1.



____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

4

4 Project Organization
4.1 Resources
The primary resources available to the Borg team are the time and effort of the Borg 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 Borg team is composed of 4 MSE graduate students. Additional resources include the client representatives, the MSE studio staff, advisors, mentors, a technical writer (for two semesters), and supporting MSE studio process groups. 4.1.2 Time As a student in the MSE Studio class, each Borg team member has a fixed amount of time available for the project. During the Fall 2001 and Spring 2002 semesters, each student is expected to devote a total of 12 hours per week to the Borg project, their MSE Studio roles, and Studio training. This work includes time spent with the mentors and time spent working on any studio-related tasks, such as team meetings, client meetings, document preparation and inspection, tool development, and others. During the Summer 2002 semester, each student is expected to devote 48 hours per week to the project.

4.2 Deliverables The Borg team will target delivery of the following work products to the client on or before the dates listed below in Table 1. The client recognizes that these are target dates and are therefore subject to change based on availability of resources, changes in scope, or changes in requirements. This deliverable schedule will be revisited with the completion of each milestone to include any changes to the schedule.
Deliverable Milestone 1 SRS Milestone 1 Baseline Milestone 5 Update for M1 Milestone 2 Prototype Milestone 5 Update for M2 Milestone 3 Prototype Milestone 5 Update for M3 Milestone 4 Prototype Milestone 5 Update for M4 Milestone 2 SRS Milestone 2 Baseline Milestone 5 Update for M2 Milestone 3 SRS Milestone 3 Baseline Milestone 5 Update for M3 Target Date March 15, 2002 March 29, 2002 April 12, 2002 May 24, 2002 May 29, 2002 June 7, 2002 June 11, 2002 June 21, 2002 June 25, 2002 June 28, 2002 July 12, 2002 July 16, 2002 July 19, 2002 August 2, 2002 August 9, 2002

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

5

Table 1: Borg Team Deliverables

5 Responsibilities
5.1 Joint Responsibilities
5.1.1 Point of Contact Specific team members have been designated to serve as the point contacts for each party. Mike Lewis will serve as the client liaison for the Fall 2001 semester, and Darby Mitchell will serve as the client liaison for the Spring 2002 semester. Mike Freed and Bonnie John will serve as the primary contacts for the client for the duration of the project. Mike Dalal, Rob Harris, and Mike Matessa will serve as secondary contacts for the client. The client will provide the contact information for any additional domain experts. Project-related decisions and administrative details will be communicated between the point contacts. In the absence of the client liaison, individual Borg team members will communicate directly with the person most able to provide the necessary information. Any decisions and commitments made during these interactions will be communicated to all Borg team members and to the client. 5.1.2 Meeting Management The Borg team will use meeting management techniques to encourage and facilitate efficient meetings. Common meeting management techniques include the following: Either the client or the Borg team may initiate meetings. The person who initiates the meeting will distribute a detailed agenda 48 hours before the meeting time.  Prior to arriving at the meeting, attendees are expected to have read the agenda and completed any requestedprerequisites. The initiator of the meeting will provide copies of the agenda for the attendees.  Attendees who cannot attend the meeting should notify the initiator of the meeting, especially if they appear on the agenda or if their presence is required to make a decision. Additional details regarding meeting management can be found in the MSE Studio Process Handbook [1].  

5.2 The Borg Team
The Borg team members’ responsibilities under this agreement are as follows: 1. Provide the software deliverables described in this document. 2. Provide the documentation and additional artifacts relevant to the project. 3. Provide change requests as will be specified in the Configuration Management (CM) document.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

6

5.3 Client
The project schedule relies on the client’s fulfillment of the responsibilities listed below. Failure to do so may prevent the Borg team from achieving its promised delivery dates. The client’s responsibilities under this agreement are as follows: 1. Reply to the Borg team’s requests via the team client liaison within two (if urgent or critical) or five (if non-critical) business days of identifying the issue. 2. Keep the Borg team informed of all issues and events that might affect the development of the Borg team project. The client shall provide change requests in writing (e-mail or written memo) to the Borg team within one week of the identification of the need for a change. 3. Work closely with the Borg team throughout the project lifecycle. In particular, the client will provide timely input to the Borg 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 Borg team and the client. Regular attendance 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 Borg team. 6. Provide the Borg team with access to any domain-specific resources that are pertinent to the project.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

7

6 References
[1] MSE Studio Process Handbook. CMU-MSE-STUDIO-PROCESSHBK-1.1, 2001 [online]. Available WWW: <URL: http://dogbert.mse.cs.cmu.edu/ProcessHandbook/ ProcessHandbook.doc> (2001).

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

8

Appendix A
This appendix provides a short description of several of the simulation packages/applications mentioned in this document. AMBR – A simulation for air-traffic control personnel that works using the HLA standard. Dreamweaver – A WYSIWYG application used for designing web pages. The user “draws” the web page and the application creates the underlying mark-up language representation. HLA – The High Level Architecture provides a set of interfaces that allow a group of simulated objects (called Federates) to communicate using the Runtime Infrastructure. The Runtime Infrastructure effectively handles all of the interaction between Federates to produce a simulation (also called a Federation). Netscape – An application used to browse through web pages, typically gathering them from the internet. X-Plane – A PC-based flight simulator.

____________________________________________________________________________________________________________ BORG/ SOW Version 2.0

9


				
DOCUMENT INFO