Notas falsas sobre nada

Note: This document was created during an actual real-world software development effort of medium size. Names have been changed, but no attempt has been made to clean the artifact of imperfections, such as typos and the like. In the real world, the condition of software project documentation varies considerably, and there is educational value in working with actual artifacts from actualprojects—imperfections and all. Working with real-world documents allows you to experience the quality of documents you may encounter in your future software development career.

Zircon
Statement of Work
Version 1.0

September 20, 1998

Document Revisions
Rev.
0.1 0.2

Date
Oct. 13, 1999 Oct. 26, 1999

Author(s)
John Doe John Doe

Comment
Initial creation Rework in response to reviewfeedback • • removed unneeded sections clarified project deliverables corrected grammar applied document template

0.3

Nov. 19, 1999

John Doe

Rework in response to review feedback • •

1.0

Nov. 25, 1999

John Doe

Included comments from client

Document Approval

Client Representative:

L.E. Danvers
Name Date Signature

Team Lead:

John Doe
Name Date SignatureQuality Assurance Manager:

Mary Glacier
Name Date Signature

TABLE OF CONTENTS

1

Introduction 1.1 Purpose 1.2 Scope 1.3 References Project Overview 2.1 Background 2.2 Zircon AQP System (ZAPS) Project Organization 3.1 Resources 3.1.1 Personnel 3.1.2 Time 3.2 Deliverables Responsibilities 4.1 Joint Responsibilities 4.2 Developers 4.3 Client

4 5 5 5 6 6 6 8 8 8 9 9 10 10 11 11

2

34

LIST OF ACRONYMS
AQP ERD FAA FOIMS FOQA GUI JTA PADB PPDB QA SCM SDS SOW SPMP SRS ZAPS Advanced qualification program Entity-relation diagram Federal Aviation Administration Flight operations information management system Flight operations quality assurance Graphical user interface Job task analysis Performance audit database Performance proficiency database Quality assurance Softwareconfiguration management Software design specification Statement of work Software project management plan Software requirements specification Zircon AQP System

Introduction

Purpose
This document establishes a written agreement between Tavlon Systems, hereafter referred to as the client, and the Uranium Group, hereafter referred to as the developers. By accepting this document, the parties agreeto 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.

Scope
The provisions stated in this agreement shall be in effect for the duration of the Zircon project. The project shall begin when this document isaccepted and end at completion of the systems acceptance test, or December 31, 1999, whichever comes first. At the end of the project, all executables, source code, documentation, and other work products developed by the Zircon team shall be considered the intellectual property of Tavlon Systems. The Zircon Team will be freed from any software development or maintenance responsibilities. The UraniumGroup reserves the right, however, to use any of the above-mentioned materials for in-house educational purposes.

References
[1] [2] [3] Zircon; Software Project Management Plan (SPMP): ZIRCON-SPMP, 1998. Zircon; Software Requirements Specification (SRS): ZIRCON-SRS, 1998. Zircon; Process Handbook: ZIRCON-PROCESSHBK-1.0, 1996.

ZIRCON-SOW-1.0

-5-

Project Overview

Background
In theUnited States, the Federal Aviation Administration (FAA) governs the training of commercial airline pilots. Each year the FAA, responding to technological advances and safety incidents, adds to the list of training requirements. For many airlines, low-cost regional carriers in particular, training in the manner prescribed by the FAA requirements is difficult and costly. To address the growing...