Defining and validating high level design metrics

Constraining the number of sub-systems will also reduce the effort here and in the subsequent steps, such as integration and verification.What should I track in this process step to reduce project risks, and get what is expected? Sometimes, there is a tendency to insert design solutions to early in the process.[E.g., ramp metering decomposition includes loops, controller clock, fiber or twisted pair for communications, 2070 controllers, host computers, cabinets, and conduits].Finally, allocating these sub-functions to the physical elements of the system will form the complete project architecture.

In this step, internal and external interfaces are identified along with the needed industry standards.

OBJECTIVE: The high-level design defines the project level architecture of the system.

This architecture defines the sub-systems to be built, internal and external interfaces to be developed, and interface standards identified.

It is for the custom designed software application that tracing of functional and performance requirements are most important.

Other aspects of the high level software design may be dependent on the design methodology used.

Search for defining and validating high level design metrics:

defining and validating high level design metrics-15

Which activities are critical for the system’s owner to do? [Tailoring] The level of each activity should be appropriately scaled to the size and budget of the project.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “defining and validating high level design metrics”

  1. To help you make your decision, we’ve broken up our list by categories, so click the links below to jump to the section that’s most relevant to your wants and needs.