Archives: Templates

Templates and model types in the QualiWare platform.

Regulation

A Regulation contains a reference to a specific paragraph in the legislation controlling the business. It can also contain a reference in a specific relevant standard i.e. ISO or ANSI.

A regulation is used to relate an object (e.g. a Process) to a relevant Regulation. This relation is made with the “ComplianceWith” relation available on the complying object (e.g. a process). This will enable the user to trace the conformance to a specific Regulation in the Repository.

A regulation can be a part of a RegulationDiagram, and used document Compliance, e.g. in a Compliance Matrix.

 

 

Report

A report executed from a Document Fragment.

Requirement

A Requirement is a prioritized demand placed on the project by one of its interested parties. Often it is the buyer the user or the management that have Requirements to the scope or results of the projects. But it can also technical requirements that appears because of constraints in the physical equipment or the algorithmic solutions chosen.

It is recommended to build a Requirement hierarchy by relating one Requirement to the sub requirements that composes it.

Requirement can be modelled in a Requirement Model.

Requirement:Archimate

In the end, a business goal must be realized by a plan or concrete change goal, which may or may not require a new system or changes to an existing system.

The term “system” is used in its general meaning; i.e., as a group of (functionally) related elements, where each element may be considered as a system again. Therefore, a system may refer to any active structural element, behavior element, or passive structural element of some organization, such as a business actor, application component, business process, application service, business object, or data object.

Requirements model the properties of these elements that are needed to achieve the “ends” that are modeled by the goals. In this respect, requirements represent the “means” to realize goals.
During the design process, goals may be decomposed until the resulting sub-goals are sufficiently detailed to enable their realization by properties that can be exhibited by systems. At this point, goals can be realized by requirements that demand these properties from the systems.
For example, one may identify two alternative requirements to realize the goal to improve portfolio management:

  • By assigning a personal assistant to each customer, or
  • By introducing online portfolio management

The former requirement can be realized by a human actor and the latter by a software application. These requirements can be decomposed further to define the requirements on the human actor and the software application in more detail.

Resource:Archimate

Resources are a central concept in the field of strategic management, economics, computer science, portfolio management, and more. They are often considered, together with capabilities, to be sources of competitive advantage for organizations. Resources are analyzed in terms of strengths and weaknesses, and they are considered when implementing strategies. Due to resources being limited, they can often be a deciding factor for choosing which strategy, goal, and project to implement and in which order. Resources can be classified into tangible assets – financial assets (e.g., cash, securities, borrowing capacity), physical assets (e.g., plant, equipment, land, mineral reserves), intangible assets (technology; e.g., patents, copyrights, trade secrets; reputation; e.g., brand, relationships; culture), and human assets (skills/know-how, capacity for communication and collaboration, motivation). Resources are realized by active and passive structure elements. The name of a resource should preferably be a noun.

Responsibility

Responsibility refers to the assignment of tasks or duties to specific individuals or teams within a larger system or organization. Responsibility can include a range of activities, such as decision-making, task completion, quality assurance, or management.

Arrows or lines may be used to show the relationships and connections between these components. For example, a line might connect a manager to a team to represent how the manager is responsible for overseeing the work of the team. Similarly, a line might connect a team to a task to represent how the team is responsible for completing the task.