Design Dependencies Deliverable Template
From MIKE2.0 Methodology
||This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
|This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
|Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.
Software components which are dependent on others will normally be implemented later, so in order to create the project plan, it is useful to identify dependencies between components. The output of the Design Dependencies task will be a dependency model showing which software components and subsystems will call upon services from which others.
Example Illustrating Design Dependencies
Desing depedencies are often complex in terms of their relationships. A well-architecture sytems can simplify these relationships.
- A Typical Software System: The figure below illustrates the tangled relationships between components in many software systems.
- An Ideal Software System: Note the linear relationship path between components in this application.