Develop a logical architecture as one key resource for describing what the Integrated Corridor Management System (ICMS) will do.

Lessons from the ICM Implementation Guide.

February 2012
Nationwide,United States

Background (Show)

Lesson Learned

System architectures can be described from many perspectives using various methods and modeling techniques. Some are described as logical or functional views, physical views, operational views, communications views, and security views. Details of these views can be captured in data, process, and behavior models to aid in the definition of the system. The logical view captures the functions, flows, controls, and decomposition of a system. The following lessons learned apply to developing a system architecture using the logical view for an ICM program.
  • Define system boundaries. Gaining agreement on the system boundaries is one of the first steps in initiating the architecture.
  • Develop a functional decomposition and requirements hierarchy. Sound methods for functional decomposition and requirements hierarchy should be defined in the SEP section of the SEMP. These methods will serve as the basis for developing the architecture and will be an important guide for reviewers and stakeholders that attend the walkthroughs. Make sure all subsystems are defined and decomposed logically, and make sure internal interfaces are defined for the system.
  • Develop a final draft logical architecture before conducting the requirements walkthrough. The final draft architecture will help walkthrough participants to visualize the system and help to verify the functional requirements.
  • Define the system and external systems. Do not get overwhelmed by the organization, documentation, and definition of external systems and then run out of gas on the definition of the system itself.
  • Maintain logical abstraction when developing the logical architecture. If put in the position where a portion of the system is being reverse engineered, maintain logical abstraction when developing the logical architecture. Do not label the functions in the logical architecture with names that were designated for a completed physical system.

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.


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: https://rosap.ntl.bts.gov/view/dot/3375

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Cheryl Lowrance


Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)

Lesson ID: 2014-00670