Lesson

Develop a Systems Engineering Management Plan (SEMP) to achieve quality in project development and ultimately produce a successful ICMS.

Lessons from the ICM Implementation Guide.


February 2012
Nationwide,United States


Background (Show)

Lesson Learned

The purpose of the Systems Engineering Management Plan (SEMP) is to give the project owners/stakeholders a tool to manage the complexity of the project. The SEMP helps to lead the technical management effort for the ICMS and is the vehicle by which all project stakeholders stay informed about the project activities and how they will be managed. Stakeholders should be able to reference the SEMP to help them understand what tasks will be performed during the project and what roles and responsibilities they have in performing and/or reviewing those tasks. The following are lessons learned from the Pioneer Sites to assist with the development of a successful SEMP.
  • Define the systems engineering process. The systems engineering process that the system development team will use needs to be documented in detail. This includes identifying the system analysis methodology, the requirements documentation and management methodology, and the traceability mechanisms to be used, as well as how needs elicitation, walkthroughs, and testing will be conducted.
  • Define the semantics behind terminology. Often it is found that terminologies differ in meaning (e.g., high-level and detailed design; or system, subsystem, element, function), so it is critical to the success of the project that terms be well defined and understood and agreed upon among stakeholders.
  • Educate stakeholders. It has been found that if the stakeholders have little understanding of the project control processes then the project will suffer. It is critical that stakeholders understand the process and are prepared for their roles in defining the system and managing system development.
  • Maintain stakeholder engagement. The project and task leads need to make sure that stakeholders stay engaged in the process and are not "burned out" by the work. Activities need to be well organized and stakeholder roles need to be well communicated so expectations will be clear and time will not be wasted, especially when it comes to user needs workshops and system walkthroughs.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

Integrated Corridor Management: Implementation Guide and Lessons Learned

Author: Gonzalez, Paul: Dawn Hardesty; Greg Hatcher; Michael Mercer; Michael Waisley Noblis, Inc. 3150 Fairview Park Drive Falls Church, VA 22042 703-610-2000

Published By: U.S. DOT Federal Highway Administration

Source Date: February 2012

Other Reference Number: Report No. FHWA-JPO-12-075

URL: http://ntl.bts.gov/lib/47000/47600/47670/FHWA-JPO-12-075_FinalPKG_508.pdf

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Cheryl Lowrance
Noblis
202-863-2986
cheryl.lowrance
@noblis.org


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson ID: 2014-00668