View MODAF:SV-10a Resource Constraints Specification View

mod_logo_60.jpg

Overview

The SV-10a Resource Constraints Specification View is part of the MODAF System Viewpoint and one of the 47 MODAF views*.

Version & Date

Version 1.2.004.

* =  changed at 1.2.004

+ =  new at 1.2.004

The change history is derived from the definition of each MODAF view within the The MODAF System Viewpoint viewpoint defining document from www.mod.uk/modaf.

See MODAF Release History.

Purpose

From The MODAF System Viewpoint (SV) p37:

The SV-10a Resource Constraints Specification specifies functional and non-functional constraints on the implementation aspects of the architecture (i.e. the structural and behavioural elements of the Strategic Viewpoint).

Subject to Crown Copyright

Note: ‘Strategic Viewpoint’ is incorrect - implementation - therefore should be System Viewpoint.

Background

From The MODAF System Viewpoint (SV) p37:

The SV-10a describes constraints on the resources, functions, data and ports that make up the SV physical architecture. The constraints are specified in text and may be functional or structural (i.e. non-functional).

Subject to Crown Copyright

Description

From The MODAF System Viewpoint (SV) p37:

The SV10-a Resource Constraints Specification describes the rules that control, constrain or otherwise guide the implementation aspects of the architecture. Resource constraints are statements that define or constrain some aspect of the business, and may be applied to:

OV-6a, Operational Rules Model, provides a specification of logical constraints (i.e. rules that will apply in general, regardless of what resources are used). The SV-10a provides a set of resource- specific constraints that are applied in order to satisfy the general constraints from OV-6a.

MODAF categorises resource constraints as follows:

  • Structural assertions –– non-functional constraints governing some physical aspect of the architecture
  • Action assertions –– functional constraints governing the behaviour of resources (constraints on functions)
  • Derivations –– these involve algorithms used to compute facts. Where a resource constraint is based on some standard, then that standard should be listed in the Standards Profile (TV-1).

Subject to Crown Copyright

Data Objects

From The MODAF System Viewpoint (SV) p37:

The data in an SV-10a can include:

MODAF_SV10a_mm_dataobjects.gif

Subject to Crown Copyright

Presentation

From The MODAF System Viewpoint (SV) p37:

  • Text (preferably specified in a computer-interpretable constraint language such as Object Constraint Language (OCL).
  • Tabular

Subject to Crown Copyright

Configuration History

Comments

Since at 1.2.004 any Resource can have a Port it seems a mistake to restrict constraints to System Ports.

References

 

Other Frameworks

See also:

 

Category:Framework -> View
Category:MODAF -> View
Category:Solution

Categories:

 

© 2010 Eclectica Systems Ltd.