Manufacturing Routing Network

Purpose: The purpose of the Manufacturing Routing Network is to specify the steps used in manufacturing a product. Below is an example of a Manufacturing Routing Network of an Item including Assembly, test and final control. At the right-hand side, you can see that different specifications have been attached as well:

ManufacturingRoutingNetwork_2

Core concerns: The Manufacturing Routing Network template enables you to model Work Operations, Products, Business Objects, General Concepts, and Production Lines. You are also able to distinguish between Activity Paths, Assembly Flows and Transport Systems. If you wish to attach External Documents, they should be attached to the Work Operations they pertain to. Below is another example of a Manufacturing Routing Network that describes the process from assembly to shipping:

ManufacturingRoutingNetwork_1

Relation to other templates: The Manufacturing Routing Network template is related to the various different models for products such as the Product Viewpoint template, the Product Variant Master template, the Product Rule Table, the Product Roadmap and the Product Canvas. Each template offers a different viewpoint of the product in various stages of its lifecycle.

Properties and metadata: The Manufacturing Routing Network template can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the accuracy of the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram
  • Project status: information about budgeted and actual man-hours spent, percentage completed and the latest milestone, result and quality control of a change process.

In the picture below you can see the Manufacturing Routing Network’s properties dialogue window, where the properties can be viewed and edited:

 

Integration View

Purpose: The purpose of the Integration View template is to document the routing of integrations between systems.

Core concerns: The Integration View template enables you to model Information Systems, System Components and External Entities (a source to or a receiver of information from a system), and connect them using Integration Flows.

Below is an example of an Integration View concerning the flow of test data:

Relation to other templates: The Integration View belongs to the Application layer of the architecture and is as such related to the Application Architecture Diagram, the Data Flow Diagram and the Component Diagram.

Properties and metadata: The Integration View template can for example retain the following information:

  • A description of the model
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

The above picture shows the properties dialogue window for the Integration View template where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

 

Infrastructure Diagram

Purpose: The purpose of the Infrastructure Diagram template is to document the physical infrastructure of the enterprise, which includes but is not limited to databases, wires, firewalls, computers etc.

Core concerns: The Infrastructure Diagram enables you to model your organizations infrastructure including: Computer Categories, Computers, Firewalls, Printers, Networks, Connection Points, Peripherals, Locations, Information Systems, System Components, Databases, Network Connections, Object Dependencies, Technology Domains, Technology Capabilities and Technology Components.

The models below exemplify how you would construct this type of diagram:

InfraStructureDiagram_1

InfraStructureDiagram_2

Relation to other templates: The Infrastructure Diagram template should not be used to document logical architecture, as the connections available in an Infrastructure Diagram are predominately geared towards documenting physical information about IT infrastructure. The Infrastructure Diagram can through its components be linked to other architectural diagrams such as the Application Architecture Diagram, and the data they contain. This way, if a firewall is breached, you would be able to very quickly identify what data has been vulnerable.

Properties and metadata: The Infrastructure Diagram can for example retain the following information:

  • A description of the diagram
  • Link to the owner of the diagram
  • Link to the one responsible for the diagram
  • Audits (auto generated information regarding its current state and access rights)
  • Associated documents, diagrams and other objects
  • Inherent Risk detailing risk considerations
  • Governance information detailing information about the published diagram and who has been involved in the approval of the diagram

 

The above picture shows the properties dialogue window for the Infrastructure Diagram, where you can view and edit the diagram’s properties in QualiWare Lifecycle Manager.

Requirements Realization Viewpoint

Concerns: Architecture strategy and tactics, motivation
Purpose: Designing, deciding, informing
Scope: Motivation

The requirements realization viewpoint allows the designer to model the realization of requirements by the core elements, such as business actors, business services, business processes, application services, application components, etc. Typically, the requirements result from the goal refinement viewpoint.

In addition, this viewpoint can be used to refine requirements into more detailed requirements. The aggregation relationship is used for this purpose.