![](media/image1.png){width="1.125in" height="1.0118055555555556in"}

ISD Process Template

**Number:** 580-TM-010-01 **Approved By: (signature)**

**Effective Date:** August 1, 2004 **Name:** Joe Hennessy

**Expiration Date:** August 1, 2009 **Title:** Chief, ISD

**Responsible Office:** 580/Information Systems Division (ISD) **Asset
Type:** Template

######### Title: Process Title PAL Number: 3.5.2.3

*GUIDANCE: This template can be used to define a process or
sub-process.\
The above header must be changed for new process or sub-process. Changes
include:\
Name (ISD (Sub-) Process Template) should be "ISD \[(sub-) process
title\]"\
Also change Number, Dates, Asset Type, Title, and PAL Number*

  -------------- --------------------------------------------------------
  **Purpose**    *GUIDANCE: State the purpose of the process.*

  -------------- --------------------------------------------------------

  -------------- --------------------------------------------------------
  **Scope**      *GUIDANCE: State the scope of the process. The scope is
                 defined as range of operation for the process; i.e. what
                 will be the extent of treatment, activity, or influence
                 of the process use.*

  -------------- --------------------------------------------------------

+-------------+--------------------------------------------------------+
| **Context   | *GUIDANCE: Create a simple box diagram showing the     |
| Diagram**   | process in relation to other processes with which it   |
|             | interacts. Show the flow of those interactions*.       |
|             |                                                        |
|             | \[Process (Category) Title\]                           |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Roles and | *GUIDANCE: List the primary role title of the person   |
| Respons     | who performs activities within the process along with  |
| ibilities** | their responsibilities. If there are additional roles  |
|             | involved, list them in Guidance for each Role Title.*  |
|             |                                                        |
|             | ***\[Role Title:\]*** *(Role title should be in        |
|             | **bold** text)*                                        |
|             |                                                        |
|             | -   *Description of responsibility*                    |
|             |                                                        |
|             | -   *Description of another responsibility*            |
|             |                                                        |
|             | ***\[Role Title:\]*** *(Role title should be in        |
|             | **bold** text)*                                        |
|             |                                                        |
|             | -   *Description of responsibility*                    |
|             |                                                        |
|             | ```{=html}                                             |
|             | <!-- -->                                               |
|             | ```                                                    |
|             | -   *Description of another responsibility*            |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Usage     | *GUIDANCE: Describe the circumstances under which this |
| Scenarios** | process is used which may include exceptions to        |
|             | inputs, entry criteria, exit criteria, and outputs. If |
|             | necessary, provide additional information and          |
|             | examples, as needed.*                                  |
|             |                                                        |
|             | *\[Primary or Initial or Other Descriptive Name\]*     |
|             | Usage Scenario:                                        |
|             |                                                        |
|             | ####### Description of Usage Scenario                  |
|             |                                                        |
|             | *\[Descriptive Alternative Name\]* Usage Scenario:     |
|             |                                                        |
|             | *Description of Alternative Usage Scenario, what makes |
|             | it different from the Primary Usage Scenario,          |
|             | examples, references, GUIDANCE, etc.*                  |
|             |                                                        |
|             | *Repeat for each \[Alternative\] Usage Scenario        |
|             | needed.*                                               |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Inputs**  | *GUIDANCE: List all Inputs needed for the process.*    |
|             |                                                        |
|             | *\[Primary or Initial or Other Descriptive Name\]      |
|             | Usage Scenario:*                                       |
|             |                                                        |
|             | -   *Input #1: description if necessary for clarity*   |
|             |                                                        |
|             | *\[Descriptive Alternative Name\] Usage Scenario:*     |
|             |                                                        |
|             | -   *Input #2: description if necessary for clarity*   |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Entry     | *GUIDANCE: List all conditions that must be satisfied  |
| Criteria**  | before the process can start. If a subset of the       |
|             | Inputs is required for startup, state that fact along  |
|             | with the required Inputs. Otherwise state that all     |
|             | Inputs are required for startup.*                      |
|             |                                                        |
|             | *\[Primary or Initial or Other Descriptive Name\]      |
|             | Usage Scenario:*                                       |
|             |                                                        |
|             | -   *Entry Criteria #1: description if necessary for   |
|             |     clarity*                                           |
|             |                                                        |
|             | *\[Descriptive Alternative Name\] Usage Scenario:*     |
|             |                                                        |
|             | -   *Entry Criteria #2: description if necessary for   |
|             |     clarity*                                           |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Exit      | *GUIDANCE: List of all conditions that must be         |
| Criteria**  | satisfied and outputs that must be produced or         |
|             | modified before the process can end.*                  |
|             |                                                        |
|             | *\[Primary or Initial or Other Descriptive Name\]      |
|             | Usage Scenario:*                                       |
|             |                                                        |
|             | -   *Exit Criteria #1: description if necessary for    |
|             |     clarity*                                           |
|             |                                                        |
|             | *\[Descriptive Alternative Name\] Usage Scenario:*     |
|             |                                                        |
|             | -   *Exit Criteria #2: description if necessary for    |
|             |     clarity*                                           |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| **Outputs** | *GUIDANCE: List all Outputs created or modified during |
|             | the process.*                                          |
|             |                                                        |
|             | *\[Primary or Initial or Other Descriptive Name\]      |
|             | Usage Scenario:*                                       |
|             |                                                        |
|             | -   *Output #1: description if necessary for clarity*  |
|             |                                                        |
|             | *\[Descriptive Alternative Name\] Usage Scenario:*     |
|             |                                                        |
|             | -   *Output #2: description if necessary for clarity*  |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| #####       | *GUIDANCE: Name the primary Role responsible and       |
| Major Tasks | whether these major tasks should be performed          |
|             | \[concurrently, sequential, parallel, iterative,       |
|             | etc.\] order. If the tasks are split between multiple  |
|             | Roles, then name the primary Role at the end of        |
|             | descriptive task name. List secondary role(s) in       |
|             | Guidance. If certain tasks are performed under special |
|             | circumstances, list those exceptions. An example is    |
|             | provided below but many more types are possible        |
|             | depending on the situation. Where appropriate, add     |
|             | **Verification** Tasks (to confirm that the product(s) |
|             | fulfill requirements and **Validation** Tasks (to      |
|             | confirm that the product(s) fulfill the specific       |
|             | intended use).*                                        |
|             |                                                        |
|             | The ***\[Primary Role Title\]*** shall perform         |
|             | *\[concurrently\]:*                                    |
|             |                                                        |
|             | 1.  *Descriptive name of task #1.*                     |
|             |                                                        |
|             | 2.  *Descriptive name of task #2.*                     |
|             |                                                        |
|             | ***OR,** if multiple Roles are involved*               |
|             |                                                        |
|             | The following tasks shall be performed *\[as           |
|             | needed\]:*                                             |
|             |                                                        |
|             | 3.  *Descriptive name of task #4. **\[Primary Role     |
|             |     Title\]***                                         |
|             |                                                        |
|             | 4.  *Descriptive name of task #5. **\[Primary Role     |
|             |     Title\]***                                         |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| ##          | *GUIDANCE: Describe each task's activities performed   |
| ### Task \# | during the process in order of occurrence. Each task   |
|             | description should be a series of activities (if there |
|             | are more than one), each of which can include several  |
|             | sentences to describe a complete body of work. Each    |
|             | activity should be numbered. Refer reader to           |
|             | appropriate sub-processes or procedures and provide    |
|             | hyper-link, if available. List secondary Role(s) in    |
|             | Guidance:*                                             |
|             |                                                        |
|             | *Descriptive name of task (in **bold text**) as used   |
|             | in Major Tasks section. **(\[Primary Role Title\])***  |
|             |                                                        |
|             | a)  *Description of activity, hyper-link to detailed   |
|             |     sub-process or procedure description, if           |
|             |     available*                                         |
|             |                                                        |
|             | b)  *Description of activity, hyper-link to detailed   |
|             |     sub-process or procedure description, if           |
|             |     available*                                         |
|             |                                                        |
|             | ***OR,** if multiple Roles are involved*               |
|             |                                                        |
|             | c)  *Description of activity, hyper-link to detailed   |
|             |     sub-process or procedure description, if           |
|             |     available, and **(\[Primary Role Title\])**        |
|             |     responsible.*                                      |
|             |                                                        |
|             | d)  *Description of activity, hyper-link to detailed   |
|             |     sub-process or procedure description, if           |
|             |     available, and **(\[Primary Role Title\])**        |
|             |     responsible**.***                                  |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------------------+
| *           | *GUIDANCE: List recommended Measures collected during  |
| *Measures** | execution of this process. If a measure is not used    |
|             | with the "Primary Usage Scenario" state that fact      |
|             | including which "Alternative Usage Scenario" it should |
|             | be used. If there are no measures, then add comment    |
|             | "No Measures identified".*                             |
|             |                                                        |
|             | **Recommended Measures:**                              |
|             |                                                        |
|             | -   *Measure #1: description with hyper-link, if       |
|             |     available*                                         |
|             |                                                        |
|             | -   Measure #2: description with hyper-link, if        |
|             |     available                                          |
|             |                                                        |
|             | **Required Measures** are found at *\[hyper-link to    |
|             | source\]*                                              |
+-------------+--------------------------------------------------------+

  -------------- ------------------- ------------------------------------
  **Tools and    *GUIDANCE: List all 
  Templates**    Tools available to  
                 perform the         
                 process. If a       
                 hyper-link to the   
                 Tool is available   
                 add that to the     
                 description. If a   
                 Tool is only used   
                 with a specific     
                 Usage Scenario then 
                 state that          
                 information.*       

                 **Name**            **Description**

                                     
  -------------- ------------------- ------------------------------------

  -------------- ------------------- ------------------------------------
  **Training**   *GUIDANCE: List all 
                 Training available  
                 to perform the      
                 process. If a       
                 hyper-link to the   
                 Training is         
                 available add that  
                 to the              
                 description.*       

                 **Course Name**     **Description**

                                     
  -------------- ------------------- ------------------------------------

> Training availability can be checked at
> <http://software.gsfc.nasa.gov/training.htm>.

+-------------+--------------------------------------------------------+
| **R         | *GUIDANCE: List all NASA standards relevant to this    |
| eferences** | particular process description. Include the ETVX       |
|             | (Entry-Task-Validation/Verification-eXit) diagram for  |
|             | this process as well as the Glossary and Process Asset |
|             | Library. Insert hyper-links to the document if this is |
|             | available and add a description, if needed.*           |
|             |                                                        |
|             | -   **Glossary:**                                      |
|             |     <http://software.gsfc.nasa.gov/glossary.cfm>\      |
|             |     Defines common terms used in ISD processes         |
|             |                                                        |
|             | -   **[ETVX Diagram]{.underline}:** A hyper-link to    |
|             |     this diagram can be found in the Process Asset     |
|             |     Library on-line version of this document.          |
|             |                                                        |
|             | -   **Process Asset Library:**                         |
|             |     <http://software.gsfc.nasa.gov/process.cfm>\       |
|             |     Library of all ISD process descriptions            |
|             |                                                        |
|             | -   ***Reference Name:** Insert a hyperlink where      |
|             |     reference can be found, Short description of the   |
|             |     reference, if needed.*                             |
+-------------+--------------------------------------------------------+

+-------------+--------------------------------------------+----------+
| **Quality   | *GUIDANCE: List the Name of the Controlled | **Record |
| Management  | Document / Description and Record          | Cus      |
| System      | Custodian for each QMS Record used during  | todian** |
| Records**   | the process. . If a hyper-link is          |          |
|             | available add that to the description.     |          |
|             | NOTE: Anything added here would become a   |          |
|             | required ISO document.*                    |          |
|             |                                            |          |
|             | **Controlled Document / Description**      |          |
+-------------+--------------------------------------------+----------+
|             | **Controlled Doc Name:** description and   | Role     |
|             | hyper-link                                 | Title    |
+-------------+--------------------------------------------+----------+
|             |                                            |          |
+-------------+--------------------------------------------+----------+

*GUIDANCE for Development History (Below): Description of major changes
to the process under development and the author performing the change.
Delete this section for final version.*

+-------------+-------+-------+---------------------------------------+
| **          | ####  | #     | **Description of Development          |
| Development | ## Ve | ##### | Changes**                             |
| History**   | rsion |  Date |                                       |
+-------------+-------+-------+---------------------------------------+
|             | ##### | Feb   | Created initial version of the User's |
|             | # 0.1 | 16,   | View Template                         |
|             |       | 2004  |                                       |
|             |       |       | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | ##### | Mar   | Added alternative formats for data    |
|             | # 0.2 | 16,   | tables. Dropped appendix, which was   |
|             |       | 2004  | not necessary. Added standards for    |
|             |       |       | asset numbering & formatting in a new |
|             |       |       | appendix. Added changes agreed to at  |
|             |       |       | March 16 ISD team meeting. PGArnold   |
+-------------+-------+-------+---------------------------------------+
|             | ##### | Mar   | Incorporated comments from reviewers  |
|             | # 0.3 | 24,   | at March 23 ISD team meeting. Dropped |
|             |       | 2004  | table format for most sections. Added |
|             |       |       | bulleted list format for most         |
|             |       |       | sections.                             |
|             |       |       |                                       |
|             |       |       | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | ##### | April | Incorporated comments from reviewers  |
|             | # 0.4 | 2,    | at March 30 ISD team meeting. Added   |
|             |       | 2004  | in QMS Records and table for          |
|             |       |       | Training. PGArnold                    |
+-------------+-------+-------+---------------------------------------+
|             | ##### | April | Incorporated comments from reviewers  |
|             | # 0.5 | 14,   | at April 2 ISD team meeting. This     |
|             |       | 2004  | included addition of mapping tables   |
|             |       |       | to various entry scenarios, addition  |
|             |       |       | of more tables for sections           |
|             |       |       | recommended, and rewording of some    |
|             |       |       | sections to delete mandatory          |
|             |       |       | language.                             |
|             |       |       |                                       |
|             |       |       | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | ##### | April | Incorporated comments from reviewers. |
|             | # 0.6 | 19,   |                                       |
|             |       | 2004  | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | ##### | April | Major rewrite to add comments from    |
|             | # 0.7 | 21,   | reviews, including dropping some      |
|             |       | 2004  | tables, reformatting of many          |
|             |       |       | sections, & addition of comments for  |
|             |       |       | section headers.                      |
|             |       |       |                                       |
|             |       |       | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | ##### | June  | Changes to address CCB and Sally      |
|             | # 0.8 | 21,   | Godfrey's comments. PGArnold          |
|             |       | 2004  |                                       |
+-------------+-------+-------+---------------------------------------+
|             | ##### | June  | Final changes to address ISD process  |
|             | # 0.9 | 23,   | team review                           |
|             |       | 2004  |                                       |
|             |       |       | PGArnold                              |
+-------------+-------+-------+---------------------------------------+
|             | #     | July  | Minor changes to improve formatting   |
|             | ##### | 2,    | and problems associated with grayed   |
|             |  0.91 | 2004  | backgrounds. PGArnold                 |
+-------------+-------+-------+---------------------------------------+
|             | #     | July  | Minor changes to improve formatting   |
|             | ##### | 30,   | and improve clarity with Usage        |
|             |  0.92 | 2004  | Scenarios. PGArnold                   |
+-------------+-------+-------+---------------------------------------+

*GUIDANCE for Change History (Below): Description of improvements to the
approved process document, the Change Request responsible, and the
author performing the change.*

+-------------+-------+-------+---------------------------------------+
| **Change    | ####  | #     | **Description of Improvements**       |
| History**   | ## Ve | ##### |                                       |
|             | rsion |  Date |                                       |
+-------------+-------+-------+---------------------------------------+
|             | ##### | ##### | Initial approved version by CCB       |
|             | # 1.0 | # TBD |                                       |
+-------------+-------+-------+---------------------------------------+

**Appendix A: Document Standards**

+-------------+--------------------------------------------------------+
| **C         | **Description**                                        |
| onvention** |                                                        |
+-------------+--------------------------------------------------------+
| Standard    | Look and feel should be the same as this template.     |
| Format      |                                                        |
+-------------+--------------------------------------------------------+
| Standard    | Arial or Helvetica 10-point normal text                |
| Font        |                                                        |
+-------------+--------------------------------------------------------+
| Subject     | Placed along left side of paper and should be standard |
| Headers     | font plus bold.                                        |
+-------------+--------------------------------------------------------+
| [Text in    | Designates hyper-links to additional relevant          |
| blue and    | information and detail. Text is standard font plus     |
| u           | color blue with underline.                             |
| nderlined]{ |                                                        |
| .underline} |                                                        |
+-------------+--------------------------------------------------------+
| *Text in    | Designates planned future hyper-links. This type       |
| blue and    | serves to flag those hyper-links not yet setup. Text   |
| italics*    | is standard font plus color blue plus italics.         |
+-------------+--------------------------------------------------------+
| *GUIDANCE   | Standard font plus italics with background (20%        |
| Text in     | shading fill) designates guidance or tailoring         |
| italics     | information for the user. It is recommended that       |
| with 20%    | GUIDANCE text be collected together into one area,     |
| gray        | preferably at the end of the section, not broken up    |
| background* | into several paragraphs or sentences that are          |
|             | scattered throughout the section.                      |
|             |                                                        |
|             | *GUIDANCE: Text of this type in this document should   |
|             | be deleted because it refers to use of this template.  |
|             | New text of this type should be added to the proposed  |
|             | document to provide guidance on document subject.*     |
+-------------+--------------------------------------------------------+
| Deletion of | No section may be deleted from this template when      |
| Template    | building a process or sub-process. If no data is       |
| Sections    | applicable for a section, then state that fact for the |
|             | relevant sections.                                     |
+-------------+--------------------------------------------------------+
| Section     | Each first section on a new page should include a      |
| separation  | separation line going across the whole page width. A   |
| on each     | similar line is needed at the end of each page. This   |
| page        | template includes this latter line as part of the      |
|             | footer.                                                |
+-------------+--------------------------------------------------------+
| Section     | Sections should **NOT** be broken across page          |
| boundary    | boundaries unless this would create excessive white    |
|             | space defined as 33% or more of a page.\               |
|             | A page break shall only be done at a logical boundary  |
|             | if it is to be broken across a page boundary.          |
+-------------+--------------------------------------------------------+

**Appendix B: Document Numbering Standard**

The document number is organized in the format:

##### Organization -- Type -- CCB Number -- Version Number

Where: **Organization** is always 580 to identify the Information
Systems Division, Code 580, as the source of the document.

**Type** is one of the following types of document:

Checklist **CK** Policy **PL** Template **TM**

ETVX Diagram **ED** Procedure **PR** Tool **TL**

Form **FM** Process **PC**

Guideline **GL** Sub Process **SP**

**CCB Number** is the number assigned by the CCB (item **CCB#** on front
page)

**Version Number** is the sequential version number (start with 1) of
the current version

**PAL Number** (Process Asset Library Number) can be found in the PAL
database. This item is on first page of this document and is listed
separately from the document number.