Chapter 5. Collecting Subprocess Requirements

In this Chapter, we look at Collecting Subprocess Requirements. In Section 5.1, we outline the binders or data produced. In Section 5.2, we outline the roles. In Section 5.3, we outline the steps of the subprocess. In Section 5.4, we outline the files of the subprocess. In Sections 5.5 thru 5.9, we examine many of these steps in more detail. In Section 5.10, we outline some sample Sample Requirement Collections. The subprocesses described in Chapters 2 - 7 strongly interact and iterate with one another.

5.1 Collecting Subprocess Requirements - Binders

We outiine here the key web items or binders that result from the Collecting Subprocess Requirements subprocess. These will be described in more detail further in the chapter.

View Tools (VTs) show how each organization views its subprocess. See Figure 5.1 (a). These are the ten NASA Field Centers Organizations for the Integrated Problem/Solution Database subprocess of the NASA SBIR Electronic Handbooks system. See Figures 5.1 (b). This is a View Tool for collecting the ways in which a NASA Field Center views the Integrated Problem/Solution Database subprocess of the NASA SBIR Electronic Handbooks system. View Tools contain:

Descriptions summarize subprocess execution. See Figure 5.1 (c). This is a Description for describing how an organization views the NASA SBIR Contract Administration and Closeout subprocess.

Plays describe subprocess execution. See Figure 5.1 (d). This is a Play/Process Tool for describing how an organization views the NASA SBIR Contract Administration and Closeout subprocess.

Documents describe subprocess data. See Figure 5.1 (e). This is a Document List for describing how an organization views the NASA SBIR Contract Administration and Closeout subprocess.

Guidelines describe an organization use of EHBs. See Figures 5.1 (f)-(g). This is a Guidelines List for describing how an organization views the NASA SBIR Contract Administration and Closeout subprocess EHBs.

Integration Tools facilitate subprocess document integration. See Figure 5.1 (h). This is a part of a Integration Tool for integrating all of the documents for the NASA SBIR Electronic Handbooks system.

Electronic Handbooks (EHBs), which facilitate the execution of subprocesses. See Figure 5.1 (i). This is an Electronic Handbook for an Advisor role for the NASA SBIR Contract Administration and Closeout subprocess.

Exercises.

1. Browse around the 8. Requirements Capture Tools (RCTs)link on the EHBs home page http://ehbs.org/.

Figure 5.1 (a). NASA Subprocess View Tools.

Figure 5.1 (b). NASA Organization View Tool.

Figure 5.1 (c). NASA Description.

Figure 5.1 (d). NASA SBIR Organization Play.

Figure 5.1 (e). NASA SBIR Organization Documents.

Figure 5.1 (f). NASA SBIR Organization
Guidelines.

Figure 5.1 (g). NASA SBIR Organization Electronic Handbooks Guidelines.


Figure 5.1 (h). NASA SBIR Integration Tool.

Figure 5.1 (i). NASA SBIR Electronic Handbooks (EHB).

5.2 Collecting Subprocess Requirements - Roles

We look at some of the types of roles of the Collecting Subprocess Requirements Subprocesses.

Collecting Subprocess Requirements Lead. This is the chief player who manages the Collecting Subprocess Requirements Subprocesses .

Customer. This is the chief player for which the Process Library is built. He or she is the one with the money for development. During this subprocess, the Customer uses the Suggestions form to make suggestions on changing the Process Library and its components.

User. This is a player for which the Process Library is also demonstrated. During this subprocess, the User also uses the Suggestions form to make suggestions on changing the Process Library and its components.

Demonstrator. This is the player who peforms most of the steps in Demonstrating EHBs. During this subprocess, the Demonstator reads the Suggestions forms to make changes to the Demonstration Tool and its components.

Developer. This is the player who helps develop the Process Library and its components.

Exercises.

1. Browse around the home White Paper link on the EHBs home page http://ehbs.org.

5.3 Collecting Subprocess Requirements - Subprocess

We outline here, the Collecting Subprocess Requirements subprocess. The key steps form the major part of the rest of this chapter.

Creating Initial Organization Views. This task involves the developer and customer who create initial model subprocess views corresponding Product Development, Product Distribution, Support and Improvement subprocesses. The model views are then copied as starting points for Organizations into the Process Library.(See Section 5.6.) These will be updated by the Organizations in the subsequent sections 5.6- 5-9.

Updating Organization Views. The first task involves the customer (and users) who update their Organization View Tools in the Product Development, Product Distribution, Support Improvement, and Common subprocesses into the Process Library. (See Section 5.6.)

Updating Organization Plays. This task involves the developer and customer who update their Organization Plays in the Product Development, Product Distribution, Support Improvement, and Common subprocesses into the Process Library. (See Section 5.7.)

Updating Organization Documents. This last task involves the customer (and developer) who update their Organization Documents in the Product Development, Product Distribution, Support, Improvement, and Common subprocesses into the Process Library. (See Section 5.8.)

Updating Organization Guidelines. This task involves the developer and customer who update their Organization Guidelines in the Product Development, Product Distribution, Support Improvement, and Common subprocesses into the Process Library. (See Section 5.9.)

5.4 Collecting Subprocess Requirements- Files

The Collecting Subprocess Requirements subprocess uses mostly database records and no standard file structures.

5.5 Creating Initial Organization Views

We discuss here how the developer and customer create model subprocess views corresponding Product Development, Product Distribution, Support and Improvement subprocesses. The model views are then copied as starting points for Organization Views into the Process Library. These will be updated by the Organizations in the subsequent sections 5.6- 5-9, integrated in Chapter 7, and improved in Chapter 8.

Problem. Create initial Contact Administration and Closeout subprocess Organization Views in the NASA SBIR Process Library.

Solution.

1. Create Model Organization View on Server. Within Product Realization Subprocesesses, for the Contact Administration and Closeout subprocess, the developer should create a "model" subprocess view, called Model View. This Contact Administration and Closeout subprocess model view will be used as a termplate for Contact Administration and Closeout subprocesses for all organizations. The model view should include:

See Figures 5.1 (b)-(e). Browse the model server SBIR Contact Administration and Closeout views in a web browser.

2. Copy Model Organization View Records to Organization Views on Server. Copy the model Contact Administration and Closeout view record to each organization. The copy operation will also copy the model play and document files. Browse the server SBIR Contact Administration and Closeout views in a web browser.

Exercises.

1. Follow the above steps to build Organization Views in the NASA SBIR Process Library.

2. Follow the above steps to build Organization Views in your organization's Process Library.

5.6 Updating Organization Views

We discuss here how to update a model Organization Views in the Process Library. See Figure 5.1 (b). The same holds for any organization view.

Problem. Update the model Contact Administration and Closeout subprocess in the NASA SBIR Process Library.

Solution.

1. Update Organization Views Records on Database Server. Update the model Contact Administration and Closeout view record. The fields include:

Exercises.

1. Follow the above steps to update the model Contact Administration and Closeout subprocess view in the NASA SBIR Process Library.

2. Follow the above steps to update subprocess Organization Views in your organization's Process Library.

5.7 Updating Organization Plays

We discuss here how to update a model Organization Play in the Process Library. See Figure 5.1 (c). The same holds for any organization play.

Problem. Update the model Contact Administration and Closeout subprocess play in the NASA SBIR Process Library.

Solution.

1. Edit Local Organization Plays Files. Edit the model Contact Administration and Closeout subprocess play in a word processor that generates HTML. Browse the local play in a web browser.

2. Upload Organization Plays to Database Server. Update the model Contact Administration and Closeout subprocess play to the server using the View tool. See Figure 5.2. Browse the server play in a web browser.

Exercises.

1. Follow the above steps to update the model Contact Administration and Closeout subprocess Play for the NASA SBIR Process Library.

2. Follow the above steps to update subprocess Organization Plays in your organization's Process Library.

Figure 5.2. Uploading the play using the View Tool.

5.8 Updating Organization Documents

We discuss here how to update a model Organization Documents in the Process Library. See Figure 5.1 (e). The same holds for any organization EHB.

Problem. Updatethe model Contact Administration and Closeout subprocess Documents in the NASA SBIR Process Library.

Solution.

1. Edit Local Organization Documents Files. Update local model Contact Administration and Closeout subprocess Documents. Browse the local Documents in a web browser.

2. Upload Organization Documents to Database Server. Update the model Contact Administration and Closeout subprocess Documents to the server using the View tool. See Figure 5.3. Browse the server Documents in a web browser.

Exercises.

1. Follow the above steps to update the model Contact Administration and Closeout subprocess Documents for the NASA SBIR Process Library.

2. Follow the above steps to update subprocess Organization Documents in your organization's Process Library.

Figure 5.3. Uploading the documents using the View Tool.

5.9 Updating Organization Guidelines

We discuss here how to update a model Organization Role Guidelines in the Process Library. See Figure 5.4 . The same holds for any organization.

Problem. Update the model Contact Administration and Closeout subprocess Guideliness in the NASA SBIR Process Library.

Solution.

1. Edit Local Organization Guidelines Files. Edit the model Contact Administration and Closeout subprocess EHBs by editing the Guidelines.Use the method of Section 5.7 to update the play. Browse the local play in a web browser.

2. Upload Organization Guidelines Files to Database Server. Update the model Contact Administration and Closeout subprocess Guidelines Files to the server using the View tool. Browse the server play in a web browser.

Exercises.

1. Follow the above steps to update the model Contact Administration and Closeout subprocess Organization Guidelines for the NASA SBIR Process Library.

2. Follow the above steps to update subprocess Organization Guidelines in your organization's Process Library.

Figure 5.3. Uploading the Guidelines using the View Tool

 

5.10 Sample Subprocess Requirements

We outiine here a sample Subprocess Requirement Collections. These are found in Appendix A2. See Figure 5.9. This sample represent the development of NASA's SBIR-STTR Contract Administration and Closeout subprocess.

NASA's SBIR-STTR Contract Administration and Closeout. The purpose of this subprocess is to manage the administration and closeout of NASA SBIR-STTR Contracts. The binders of this subprocess include the NASA SBIR-STTR Phase I and II: Contracts, Contract Award File Libraries, Deliverables Libraries, Users, Suggestions, and Reports. The Process/Play of this subprocess is divided into several acts: 1. Administrative Tools, 2. Deliverables, 3. Advisors, 5. Modifications, 5. Closeouts, and 6. Analysis. The roles of this subprocess include: Contract Specialist, Principal Investigator/Awardee Official, Contracting Officer Technical Representative (COTR), JPL Technical Monitor, Advisor, Field Center Program Manager, JPL Program Officer, Field Center Contracting Officer, Field Center Program Analyst, Field Center Accounting Officer, Field Center Closeout Specialist, Field Center New Technology Officer, Subtopic Manager, Topic Manager, Procurement Manager, Financial Manager, Strategic Enterprise Representative, Program Manager, CASI Officer, and TechTracs Officer.

Samples of the subprocess development of NASA's SBIR-STTR Contract Administration and Closeout subprocess are as follows:

Outlining/Playwriting,
Example/Rehearsal,
Implementation/Staging,
Utilization/Performance, and
Revision/New Production.

Related Reading

A number of sample Requirements Capture Tools can be in found in:

Requirements Capture Tools (RCTs) link on the EHBs home page http://ehbs.org.