In this Chapter, we look at Outlining/Playwrighting Subprocesses. In Section 4.1, we outline the binders or data produced. In Section 4.2, we outline the roles. In Section 4.3, we outline the steps of the subprocess. In Section 4.4, we outline the files of the subprocess. In Sections 4.5 thru 4.10, we examine many of these steps in more detail. In Section 4.11, we outline some sample Subprocess Developments. The subprocesses described in Chapters 2 - 7 strongly interact and iterate with one another.
We outiine here the key web items or binders that result from the Outlining/Playwrighting Subprocesses subprocess-namely, Requirements Capture Tools (RCTs). These will be described in more detail further in the chapter.
Requirements Capture Tools (RCTs). Requirements Capture Tools (RCTs) facilitiate subprocess development and are the repository of all of the documentation for EHBs development for that subprocess. Requirements Capture Tools are comprised of several elements:
- Home, which is a link to the top of the RCT. See Figure 4.1 (a))
- Binders, which provide examples of binders or data that the entire subprocess will produce. See Figure 4.1 (b).
- Process: (Example), which provides the example Process/Play with actors which describes the temporal flow of the subprocess. See Figure 4.1 (c).
- Process: (Implementation), which provides the implementation Process/Play with actors which describes the temporal flow of the subprocess. See Figure 4.1 (d).
- User EHBs: (Example), which provides examples of user EHBs for the entire subprocess. See Figure 4.1 (e).
- User EHBs: (Implementation), which provides implementations of user EHBs for the entire subprocess. See Figure 4.1 (f).
- Home Pages: (Example), which provides examples web page where uses get their EHBs for the subprocess. See Figure 4.1 (g).
- Home Pages: (Implementation), which provides an implementations of the web pages where users get their EHBs for the subprocess. See Figure 4.1 (h).
- Files: (Example), which provides files for the examples for EHBs for the subprocess. See Figure 4.1 (i).
- Files: (Implementation), which provides files for the implementation for EHBs for the subprocess. See Figure 4.1 (j).
- Suggestions, which provides a vehicle for users to make suggestions on improving the examples and implementations. See Figure 4.1 (k).
Building EHBs corresponds to putting on a production of a play- Outlining/Playwrighting, Example/Rehearsal, Implementation/Staging, Utilization/Performance, and Revision/New Production.
Exercises.
1. Browse around the Requirements Capture Tools (RCTs)link on the EHBs home page http://ehbs.org/.
Figure 4.1 (a) . NASA SBIR Outlining/Playwrighting Requirements Capture Tool (RCT).
Figure 4.1 (b). NASA SBIR Outlining/Playwrighting Binders
Figure 4.1 (c). NASA SBIR Outlining/Playwrighting Process/Play
Figure 4.1 (d). NASA SBIR Outlining/Playwrighting EHB.
Figure 4.1 (e). NASA SBIR Outlining/Playwrighting User EHBs
Figure 4.1 (f). NASA SBIR Outlining/Playwrighting Home Pages
Figure 4.1 (g). NASA SBIR Outlining/Playwrighting Files
Figure 4.1 (h). NASA SBIR Suggestion Files
We look at some of the types of roles the Outlining/Playwrighting Subprocesses subprocess.
Development Lead. This is the chief player who manages the Outlining/Playwrighting Subprocesses Subprocess.
Developer. This is the player who develops the EHBs and updates the Requirements Capture Tool.
Demonstrator is the key player of this process who peforms most of the steps above in Demonstrating EHBs. During this subprocess, the Demonstator reads the Suggestions forms to make changes to the Demonstration Tool and its components.
Customer. This is the chief player for which the Requirements Capture Tool is built. He or she is the one with the money for development. During this subprocess,the Customer also uses the Suggestions form to make suggestions on changing the Requirements Capture Tool and its components.
User. This is a player for which the Requirements Capture Tool is also demonstrated. During this subprocess, the User also uses the Suggestions form to make suggestions on changing the Requirements Capture Tool and its components.Exercises.
1. Browse around the home White Paper link on the EHBs home page http://ehbs.org.
We outline here, the Outlining/Playwrighting Subprocesses subprocess. The key steps form the major part of the rest of this chapter.
Creating Initial Requirements Capture Tools. This task involves the developer and customer who create initial subprocess Requirements Capture Tools corresponding to Product Development, Product Distribution, Support and Improvement subprocesses. These will be updated by the Organizations in the subsequent sections 4.6- 4.10. (See Section 4.4.)
Updating Binders. The first task involves the developer and customer who update the Binders or data component of the Requirements Capture Tools. (See Section 4.6.)
Updating Process/Play . This task involves the developer and customer who update the Process or Play component of the Requirements Capture Tools. (See Section 4.7.)
Updating EHBs. This task involves the developer and customer who update the EHBs component of the Requirements Capture Tools. (See Section 4.8.)
Updating Home Pages. This task involves the developer and customer who update the Home Pages component of the Requirements Capture Tools. (See Section 4.9.)
Updating Files. This task involves the developer and customer who update the Files component of the Requirements Capture Tools. (See Section 4.10.)
We look at some of the types of files used in the Outlining/Playwrighting Subprocesses subprocess. See Figure 4.2. These represent the files for the NASA SBIR Requirements Capture Tool for Contract Administration and Closeout. Notice that there is a subdirectory corresponding to each of the pieces of the Requirements Capture Tool.
Figure 4.2 (a). NASA SBIR Process Library (PL) files.
Figure 4.2 (b). NASA SBIR Requirements Capture Tool (RCT) Classifications files.
Figure 4.2 (c). NASA SBIR Product Realization Subprocesses Requirements Capture Tool (RCT) files.
Figure 4.2 (d). NASA SBIR Contract Administration and Closeout RCT files.
We show here how the developer and customer create initial subprocess Requirements Capture Tools corresponding to Product Development, Product Distribution, Support and Improvement subprocesses. These will be updated by the Organizations in the subsequent sections 4.6- 4.10.
Problem. Create an initial Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
All these steps are performed on the local and server computers.
1. Create An Initial Local Requirements Capture Tool. Copy a sample Requirements Capture Tool zip file from the Appendix and unzip it into the local Requirements Capture Tool subdirectory. See Figure 4.2. Browse the local SBIR Requirements Capture Tool in a web browser.
2. Edit the RCT Title. The file rct_main.htm contains the title of the Requirements Capture Tool. Edit this file so that it reflects the name of the subprocess and the fact that it is in the Outline/Playwrighting stage of development. See Figure 4.1 (a). Browse the Subprocess Requirements Capture Tool on your server computer in a web browser.
3. Copy Local Requirements Capture Tool To Server . Copy the local Requirements Capture Tool to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to outline/playwright Contact Administration and Closeout subprocess for the NASA SBIR Process Library.
2. Follow the above steps to outline/playwright subprocess Organization Documents in your organization's Process Library.
Figure 4.3 (a). NASA SBIR Outlining/Playwrighting RCT
Figure 4.3 (b) A NASA SBIR Outlining/Playwrighting Example User EHB
We show here how the developer and customer update the Binders or data component of the Requirements Capture Tools.
Problem. Update the Binders component of the Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
All these steps are performed on the local and server computers.
1. Edit the Binders. A binder in the Outlining/Playwrighting stage is represented by a set of web pages which illustrates the contents of that binder. See Figure 4.1 (b). The binders subdirectory contains files corresponding to the binders that result from subprocess. The left.htm file contains names of the different binders. Each binder name is linked to an access file having the name of that binder. Each access file provides instructions on how to access that binder. Browse the Subprocess Requirements Capture Tool on your local computer in a web browser.
2. Copy Local Binders Files To Server . Copy the local Binders Files to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to update the binders files in the Contact Administration and Closeout subprocess for the NASA SBIR Requirements Capture Tool.
2. Follow the above steps to update the binders files in in your organization's Requirements Capture Tool.
We show here how the developer and customer update the Process or Play component of the Requirements Capture Tools.
Problem. Update the Process/Play component of the Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
All these steps are performed on the local and server computers.
3. Edit the Process/Play. A Process/Play in the Outlining/Playwrighting stage is represented by a set of web pages which points to the Example EHBs below. See Figure 4.1 (c). The process subdirectory contains files corresponding to the Process/Play which defines the subprocess. The index.html file contains the Process/Play and the names of the different EHBs. Each EHB name is linked to that EHB. Browse the Subprocess Requirements Capture Tool on your local computer in a web browser.
2. Copy Local Process/Play Files To Server . Copy the local Process/Play Files to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to update the process/play files in the Contact Administration and Closeout subprocess for the NASA SBIR Requirements Capture Tool.
2. Follow the above steps to update the process/play files in in your organization's Requirements Capture Tool.
We show here how the developer and customer update the EHBs component of the Requirements Capture Tools.
Problem. Update the EHBs component of the Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
1. Edit the Example EHBs. An Example EHB in the Outlining/Playwrighting stage is represented by a set of web pages which illustrates the steps in that EHB. See Figures 4.1 (d) and (e). The example_uehbs subdirectory contains files corresponding to the example User EHBs for the subprocess. The left.htm file contains names of the different EHBs.. Each EHB name is linked to an access file having the name of that EHB. Each access file provides instructions on how to access that EHB. Browse the Subprocess Requirements Capture Tool on your local computer in a web browser.
2. Copy Local EHBs Files To Server . Copy the local EHBs Files to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to update the EHBs files in the Contact Administration and Closeout subprocess for the NASA SBIR Requirements Capture Tool.
2. Follow the above steps to update the EHBs files in in your organization's Requirements Capture Tool.
We show here how the developer and customer update the Home Pages component of the Requirements Capture Tools.
Problem. Update the Home Pages component of the Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
All these steps are performed on the local and server computers.
1. Edit the Example Home Pages. A home pages for an EHB is the location in the subprocess where the user's role is initiated. See Figure 4.1 (f). This could be a public home page or the EHB of another role that registers the user to an EHB. An Example Home Page in the example/rehearsalstage is represented by a set of example web pages which illustrates either the public home page or the EHB of the role of the initiator. The example_home_pages subdirectory contains files corresponding to the Home Pages for the subprocess. The left.htm file contains names of the different EHBs. Each EHB name is linked to an access file having the name of that EHB. Each access file provides instructions on how to access that home page for that EHB. Browse the Subprocess Requirements Capture Tool on your local computer in a web browser.
2. Copy Local Home Page Files To Server . Copy the local Home Page Files to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to update the Home Page files in the Contact Administration and Closeout subprocess for the NASA SBIR Requirements Capture Tool.
2. Follow the above steps to update the Home Page files in in your organization's Requirements Capture Tool.
We show here how the developer and customer update the Files component of the Requirements Capture Tools.
Problem. Update the Files component of the Requirements Capture Tool for the NASA SBIR Contact Administration and Closeout subprocess.
Solution.
1. Edit the Example Files. An Example Files in the Outlining/Playwrightingstage is represented by a set of web pages which illustrates the contents of the files for that EHB. See Figure 4.1 (g). The example_files subdirectory contains files corresponding to the User example internal filesfor the subprocess. The left.htm file contains names of the different EHBs.. Each EHB name is linked to an access file having the name of that EHB. Each access file provides instructions on how to access the example files for that EHB. Browse the Subprocess Requirements Capture Tool on your local computer in a web browser.
2. Copy Local Files Files To Server . Copy the local Files Files to the server. Browse the server Requirements Capture Tool in a web browser.
Exercises.
1. Follow the above steps to update the Files files in the Contact Administration and Closeout subprocess for the NASA SBIR Requirements Capture Tool.
2. Follow the above steps to update the Files files in in your organization's Requirements Capture Tool.
We outiine here a sample subprocess development. These are found in Appendix A2. See Figure 4.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, 4. Advisors, 4. Modifications, 4. 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/Playwrighting,
Example/Rehearsal,
Implementation/Staging,
Utilization/Performance, and
Revision/New Production.
Figure 4.9 Subprocess Development Samples.
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.
