View TRAK:MVp-03 Requirements and Standards Viewpoint

TRAK_logo_60.jpg

Title

MVp-03 - Requirements and Standards Viewpoint

Version

10

Date

8th December 2017

Overview

The MVp-03 - Requirements and StandardsViewpoint is part of the Management Perspective and one of the 24 TRAK Architecture Viewpoints.

The MVp-03 Architecture Description Design Record Viewpoint provides a way of capturing normative requirements whether standards, requirement documents, government acts, or individual requirements.

It is the specification for the TRAK::MV-03 - Requirements and Standards architecture view.

Stakeholders Addressed

mvp03StakeholderConcern_400.jpg

Full size:File:mvp03StakeholderConcern.pdf

Concerns Addressed

What other constraints/requirements through normative documents/ standards apply (or will apply) to the system, project, enterprise?

Covered by TRAK IPR and licenses

Description

Describes the constraints that apply to an architecture element through requirements and standards or how standards depend on one another.

Covered by TRAK IPR and licenses

Declared Tuples

The 3 TRAK metamodel stereotypes that represent a requirement or a constraint are Contract, Requirement and Standard which can be applied to any architecture description element. Standard and Contract are both normative documents.

These represent any requirements/constraints applied to any element of the architecture being described or the architecture description or the task itself:

  • Contract governs Architecture Description Element
  • Requirement governs Architecture Description Element
  • Standard governs Architecture Description Element
  • Architecture Description Element satisfies Contract
  • Architecture Description Element satisfies Requirement
  • Architecture Description Element satisfiesStandard
  • Architecture Description Element traces to Contract
  • Architecture Description Element traces to Requirement
  • Architecture Description Element traces toStandard
  • Contract applies Standard
  • Contract depends on Contract
  • Contract supersedes Contract
  • Contract has part Contract
  • Contract has part Requirement
  • Standard has part Requirement
  • Standard depends on Standard
  • Standard enacts Standard
  • Standard equivalent to Standard
  • Standard applies Standard
  • Standard supersedes Standard
  • Standard has part Standard
  • Requirement has part Requirement
  • Requirement derived from Requirement
  • Contract issued by Organisation
  • Standardissued by Organisation

Optional Tuples

Covered by TRAK IPR and licenses

If any of these optional metamodel elements are added then the appropriate TRAK Master Architecture View must be provided.

Well-Formedness

The MV-03 must contain:

  • at least one (Contract, Requirement or Standard)
  • every Requirement must be connected to at least one other Architecture Description Element
  • every Standard must be connected to at least one other Architecture Description Element
  • every Contract must be connected to at least one other Architecture Description Element
  • every Architecture Description Element must be uniquely identified

Note:

  • If no issue or version number for Standard is identified it is assumed that the latest version applies (even if subsequently withdrawn). This allows an architect to declare that a standard applies before they’ve identified the version.
  • attributes should be used to add appropriate detail (TRAK Metamodel document)
    • Requirement has attributes that include requirement ID, compliance level (e.g. mandatory or desirable), priority, paragraph number, type (e.g. legal, commercial or technical)
    • Architecture Description Element has attributes that include security descriptors
    • Document has attributes that include Dublin Core Metadata elements
    • Standard has attributes that include issue date, part, number and withdrawal date

Covered by TRAK IPR and licenses

Presentation

  • block diagram
  • table

Showing constraints - requirements:

MV-03_examplePresentation_requirements.gif

Contract applying standards:

MV-03_examplePresentation_contractStandards.gif

Covered by TRAK IPR and licenses

Examples

Views Needed to Construct

The MV-03 will usually, but not always, be constructed after other views.  Depending on the area in which the constraints apply the following views will precede the MV-03 as they provide the ‘things’ to which the constraints attach to.

Capability constraints

Concept Constraints

Procurement Constraints

Solution Constraints

Management Constraints

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

Configuration History

The TRAK Viewpoints project on Sourceforge (trakviewpoints.sourceforge.net) maintains a version-controlled repository. The change record is at trakviewpoints.svn.sourceforge.net/viewvc/trakviewpoints/trunk/?view=log

Comments

The MV-03 is the master architecture view for Contract, Requirement, Standard.

The views produced are expected to focus primarily on standards or on requirements. Requirement-focussed views will make it possible to show how the architecture description links to products from requirement management tools such as DOORS and also act as a justification for the way in which the architecture has been represented in the architecture description.  It is not the purpose of an architecture framework to manage requirements. Is it the purpose of TRAK to provide a means of integrating architecture description with dedicated requirement management tools.

In selecting by TRAK perspective views can be used to correspond to Capability Requirement Documents, Operational Requirement Documents and System Requirement Documents. Requirements aren’t just technical - they may be commercial. Any constraint has at some stage to be formally captured by a requirement.

More complicated forms are possible by using the date of issue of the standard as a filter. Note that usually, with the exception of national law and safety, once a standard has been applied by contract it will preserve the issue of the standard applied irrespective of an more recent issues.

Covered by TRAK IPR and licenses

References

Other Frameworks

Representation of logical/operational or implementation-free constraints:

Constraints on services:

Representation of implementation or solution constraints:

Solution Performance characterisation:

or rules:

Representation of collections of constraints in Standards:


Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Management
Category:Architecture Perspective -> Management

Categories:

  • Management
  •  

    © 2010 Eclectica Systems Ltd.