View TRAK:SVp-07 Solution Sequence Viewpoint

TRAK_logo_60.jpg

Title

SVp-07 Solution Sequence Viewpoint

Version

11

Date

8th December 2017

Overview

The SVp-07 Solution Sequence viewpoint is part of the TRAK Solution Perspective and one of the 24 TRAK Architecture Viewpoints.

The SVp-07 Solution Sequence Viewpoint provides the means to describe the order or sequence in which things happen within the solution. It elaborates the behaviour described by the SVp-04 Solution Function Viewpoint where functions are defined and allocated to parts of the solution and the exchanges described in the SVp-02 Solution Resource Interaction Viewpoint.

The SVp-07 architecture viewpoint is the specification for the TRAK::SV-07 Solution Sequence architecture view.

Stakeholders Addressed

  • Owner of Solution
  • Developer of Solution
  • Acquirer of Solution
  • Operator of Solution
  • User of Solution
  • Trainer of Solution
  • Maintainer of Solution

Covered by TRAK IPR and licenses

Concerns Addressed

In what order do things need to happen?

Covered by TRAK IPR and licenses

Description

Describes the order in which functions or events occur.

Covered by TRAK IPR and licenses

Declared Tuples

Functional Sequence

Interaction Sequence

where Resource = System, Physical, SoftwareOrganisation, Job or Role

Covered by TRAK IPR and licenses

Consistency rules apply where any exchange between Resources or functionality shown wrt Function.

Optional Metamodel Tuples

Context:

To establish what ‘thing’ is performing functional or interaction sequence and where it sits in the bigger picture:

  • System is configured with Resource
  • Organisation has part Job
  • Organisation has part Organisation
  • Organisation is member of Organisation
  • Software has part Software
  • Job plays Role
  • Organisation plays Role
  • Function has part Function
  • Interaction Element has part Interaction Element

where Resource = System, Physical, Software, Organisation, Job or Role

Universal

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

Covered by TRAK IPR and licenses

Well-Formedness

A SV-07 view shall contain:

Function Sequence

  • at least one Resource (the subject of the view)
  • the subject Resource must have at least 2 Functions
  • every Function must be connected to another Function by EITHER (Function triggers Item triggers Function) OR (Function precedes Function)

Interaction Sequence

  • at least 2 Resources (the subject of the view)
  • each Resource pair is connected by a Resource Interaction

General

  • a means of identifying the order in which all Functions/Resource Interactions occur e.g. by numbering or explicit layout on a time line

Covered by TRAK IPR and licenses

Presentation

Any diagram capable of showing order/sequence of events, state transitions etc.

  • sequence diagram
  • communication diagram

Interaction Sequence

SV-07_presentationExample_interaction.gif

Note: labelling shown is of the form: sequence identifier:Resource Interaction Identifier.

Function Sequence

SV-07_presentationExample_functional.gif

showing the Function precedes Function tuple:

TRAK_SV-07_example_precedes.gif

Covered by TRAK IPR and licenses

Examples

Views Needed to Construct

See Minimum Allowed View Sets

Covered by TRAK IPR and licenses

Consistency Rules

  • any Interaction Elements and Resource Interactions needed to trigger Functions must be consistent with those defined on the SV-02:
    • IF (Resource performs Function triggers Interaction Element on SV-07) THEN ( Resource Interaction from (same) Resource carries (same) Interaction Element on SV-02)
    • IF (Interaction Element triggers Function performed by Resource SV-07) THEN ( Resource Interaction to (same) Resource carries (same) Interaction Element on SV-02)
  • any Functions shown must be consistent with those defined on the SV-04:

  • any interchange between resources must be consistent with those via
    Resource-Resource Interaction-Resource shown in SV-02

  • any linking of Resources using a Function and an Interaction Element to establish a sequence causes a SV-02 and SV-03 to be created if not already present :

    • Functional justification of resource interaction.: IF {Resource performs Function triggers Interaction Element (SV-07)} AND {(second) Resource performs (second) Function triggers (same) Interaction Element (SV-07) } THEN {{Resource Interaction from Resource to (second) Resource must be made in SV-02 AND (same) Resource Interaction supports Function and (same) Resource Interaction supports (second) Function must be made in SV-03}}.

SV_07_SV-02_SV-03_consistency_430.gif

Full size:File:SV 07 SV-02 SV-03 consistency.gif

Linking of 2 Resources’  Functions via Interaction Elements causes a SV-02 (asserting that a resource interaction between the 2 resources exists) and a SV-03 (mapping the resource interaction to the 2 functions involved in the sequence) to be created.

Covered by TRAK IPR and licenses

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

References

Other Frameworks

See also:


Category:Framework -> Viewpoint
Category:Framework -> Specification
Category:Solution

Categories:

  • Solution
  •  

    © 2010 Eclectica Systems Ltd.