• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

SE:  System Validation

Page history last edited by barbara gibson 14 years, 11 months ago

Return to Understanding Systems Engineering

Previous: System Verification and Deployment

Next:  Operations & Maintenance

 

System Validation Step Description

After the ITS has passed system verification and is installed in the operational environment, the system owner/operator whether the state DOT, a regional agency, or another entity-runs its own set of tests to make sure the deployed system meets the original needs identified in the Concept of Operations.

 

 

Purpose

The purpose of this step is to measure just how effective the system is in its operational environment.  Does the system meet the needs of the users, or more simply, was the right system built?

 

 

Activities

The following key activities will be performed:

 

  1. Plan validation.  An initial Validation Plan was actually created at the same time as the Concept of Operations.  The performance measures identified in the Concept of Operations forced early consideration and agreement on how system performance, and project success would be measured.  A Validation Plan may have been prepared that defined the consensus validation approach and outcomes that should be measured.  If it was not then a plan should be developed for validation to proceed.
  2. Validate system. The system is validated per the Validation Plan and the needs, goals, and objectives identified in the Concept of Operations.  The stakeholders (system owner and system users) actually conduct the system validation.  The validation activities are documented and the resulting data are collected, including system performance indicators as specified in the validation plan.  If validation procedures are used, then the as-run procedures should also be documented. 

 Related Resources

Chapter 4.9 System Validation Systems Engineering for Intelligent Transportation Systems, January 2007

http://ops.fhwa.dot.gov/publications/seitsguide/section4.htm#s4.9

Cost: Free

 

Chapter 3.7.1 System Validation

Systems Engineering Guidebook for ITS, California Department of Transportation Division of Research and Innovation, January 2007

http://www.fhwa.dot.gov/cadiv/segb/views/document/Sections/Section3/3_7_1.htm

Cost: Free

 

Buede D. M., The Engineering Design of Systems: Models and Methods, Wiley Inter-Science, 2000

Cost: (price may range from $54 - $110 depending on retail source)

 

Sage, A.P., Systems Management: for Information Technology and Software Engineering, Wiley Inter-Science, 1995

Cost: (price may range from $18 - $132 depending on retail source)

 

Note:  Much of the material on this page was extracted from  http://www.itslessons.its.dot.gov/its/benecost.nsf/LessonSystemsEng

 

Comments (0)

You don't have permission to comment on this page.