SEA Design, Testing, and Validation

Background

The SEA Design, Testing, and Validation record combines iterative technology, scoping, and design data into a single record. This creates consistency by using the CDOT ITS Architecture Plan, which establishes basic requirements for each type of technology system. 

Note: For more detailed information that is not specific to PMWeb, please visit the SEA Document Web Page and the SEA Information Web Page.

Access: This record is located in the Records module of PMWeb under "Custom Forms".

Related Pages: SEA Maintenance Plan, SEA Standard Operating Procedures (SOP), SEA Agreements with Partners Tracking, Technology/SEA Assessment.

Job Aids

The following job aids and reference guides are relevant to the SEA Design, Testing, and Validation record: 

• Using the SEA Design, Testing, and Validation record

To request additional training or documentation, please submit a Help Request in PMWeb.

Record Guidance

Technology Apps:

In the Tech Apps sub-tab, PMWeb imports the proposed and existing technology applications and SEA documentation reference information from the Technology/SEA Assessment record's Technology Applications sub-tab. If necessary, Project Managers review and edit the tables before continuing to the Alt Analysis sub-tab.

Alternative Analysis:

In the Alt Analysis sub-tab, Project Managers evaluate different project alternatives with a cost-benefit analysis and explain why an alternative was or wasn't selected. The submitting PM and the ITS Lead should each download the record report and review the Decision Matrix total scores results once this sub-tab has been completed. The ITS Lead must approve this sub-tab in Workflow before PMs can continue.

Concept of Operations:

In the Concept of Ops sub-tab, PMs enter a high-level description of how the system will operate and its basic functions. PMs, along with input from the project team, identify relevant stakeholders and designate whether or not commonly identified wants/needs should be included in the project scope. PMs should document all of the discussed wants and needs of the stakeholders and users to fulfill the vision of the proposed project. It is important to document all items discussed so that there can be historical knowledge why an item was not selected. PMs must request Team Input and the ITS Lead must approve the this sub-tab in Workflow before PMs can continue. 

System Functional Requirements and High-Level Design:

In the System Functional Requirements sub-tab, PMs identify functional requirements related to Technology Apps and any additional functional requirements related to the project. PMs describe how any functional requirements will be implemented and provide verification of how they will be integrated into the project.

In the High-Level Design sub-tab, PMs do not need to enter any information. Instead, Project Managers must attach a high-level communications diagram using the Attachments tab of the record. For detailed information on the Attachments tab, reference the job aid on adding attachments to a record.

Detailed Design:

In the Detailed Design sub-tab, PMs enter information about the technical design aspects of the project, including hardware, networking components, software, and roles and responsibilities. Project Managers also document the anticipated start dates of ITS milestones and identify responsible parties for security documents. The ITS Lead must approve the this sub-tab in Workflow before PMs can continue.

Testing and Integration:

In the Testing and Integration sub-tab, PMs outline the testing and integration plan, including roles and responsibilities and specific procedures. Project Managers should ensure that all procedures are documented and acknowledged. The ITS Lead must approve the this sub-tab in Workflow before PMs can continue.

Validation Plan:

In the Validation Plan sub-tab, PMs ensure that all project wants and needs are either included or excluded from the project scope with appropriate rationale. The ITS Lead must thoroughly review and approve this sub-tab in Workflow before the project can be finalized.

Additional Notes

The SEA Design, Testing, and Validation record contains several tabs in addition to the Main tab.

• Users may add notes to associate with the record in the Notes tab.

• Users may add supplemental information in the Attachments tab.

  • A high-level communications diagram should be included in the Attachments tab for this record.

• Users may add other individuals to notify of record changes or updates in the Notifications tab.

• Users submit the record to workflow for review and approval in the Workflow tab.

For more information on standard tab types, please reference the Records Navigation page.

Report Guidance

After the Alternative Analysis has been entered, PMs should view the record report and evaluate the Decision Matrix results found in the SEA Design Testing and Validation report. The lowest total score represents the most attractive alternative.

After receiving the Validation plan for review and prior to giving the record their final approval, the ITS Lead should download and review the complete record report. The output of a completed and final approved SEA Design, Testing, and Validation record is the Form 1180.

FAQs

What is the order of document submission for the SEA Design, Testing, and Validation record?

The order of document submission is the same as the form's tab order: Tech Apps, Alternative Analysis, Concept of Operations, System Functional Requirements, High-Level Design, Detailed Design, and Testing/Integration. The Validation Plan tab can only be completed after the SEA Maintenance Plan record, SEA Agreements with Partners Tracking record, and SEA Standard Operating Procedures (SOP) records have been submitted and approved.

What are the prerequisites for starting the SEA Design, Testing, and Validation record?

The Technology Assessment must be completed before starting the SEA Design, Testing, and Validation record. Additionally, the Maintenance Plan, Agreements with Partners Tracking, and Standard Operating Procedures records must be approved before the Validation Plan can be submitted.

How does the workflow handle the Utility Matrix attachment?

If the Utility Matrix is required, the workflow will check for an attachment. If no attachment is found, PMWeb will return the record to the submitter with a warning to add the attachment or change the Utility Matrix requirement to "No".

How does the Team Input process work?

The team input is restricted to project members. The submitter can send team input requests to multiple people at once, but they will only receive a notification when the team input is complete, not for individual comments. The submitter must review the team input comments before moving the record forward. For more information, refer to the Team Input page.

Where can I see the Decision Matrix scores for the identified alternatives?

The Decision Matrix displays the scores from the Alternative Analysis sub-tab. PMs and ITS Leads can download the record report to view the Decision Matrix total scores table and evaluate the identified project alternatives.