SCS Framework

Structural Control System (SCS)

Concept

SCS is a SARL framework for architectural project management. It was developed by Joe Van Steen in the 1970’s.  It was developed for use as a cyber development cost and risk calculator.  While SCS predates the Object Management Group (OMG), it is useful to understand project mapping as a Domain Specific Language (DSL), a Metamodel, on an OMG MetaObject Facility (MOF) schema.  OMG is an industry group that defines standards, used as technical languages, for consistent understanding across participants when integrating cyber products in similar domains.

The function of the DSL is to translate between the framework defined in the MOF Domain as a universal understanding of how things work, and why; and the understanding defined by the M1 model of the system.

The actual activities of the project are the domain specific tracked tasks of the project, using their routine information sets about people, assignments, skills, resources, etc.

OMG Engineering SARL Project Architecture
OMG MOF Level OMG Domain Object Domain Process Domain
M3 MOF UML Information Facility Domain Objects Domain Activities
M2 DSL Metamodel UML Model of Model Project Knowledge SCS Computations
M1 System Model Model of System Objects Resources Model Project Plan
M0 Objects [Actual Objects1Out of Scope] Project Resources Project Activities

The value of mapping is that the MOF Schema, with UML as a DSL, is the framework used for the specification and mechanization of OMG’s Model Driven Architecture® (MDA®). MDA®, using OMG UML (XMI) and Eclipse technologies is actively used in the automated development of CyberPhysical systems according to defined ISO 42010 specified architectures. 

Model Driven Architecture®

Diagram

OMG’s MDA is an industry-standard architecture. It is based on series of MOF-enabled transformations. The transformations are first enabled by the conceptual segmentation of the MOF layers, and then implemented as generated, automated machine (computer) language instructions from consistent, and independent models  for business logic, transformation mapping, and device and use specific model to functional cyber applications.

The process follows a top-down driven process.

  1. Modeling Space Development Process
    1. Create a machine comprehendible model of a business function with desired behaviors. MDA defines this model as a PIM, a Platform Independent Model. It defines the cyber application’s business functionality and behavior.  Specify the PIM in a machine comprehensible form, validate and verify the machine generated PIM.
      1. Iterate design variations2Go to step 1.1 for changes. of the PIM architecture based on architectural intent to accomplish business mission.
    2. Generate a Platform Specific Model of the cyber application, a configuration specification.
      1. Iterate design variations3Go to step 1.1 for changes. of the PIM architecture based on architectural intent to accomplish business mission. Validate and verify the machine generated PSM configuration.
  2. Operational Space Process
    1. Generate and deploy an operational implementations of the CyberPhysical application from the PSM.
      1. Iterate operational activities using the CyberPhysical application to engage in real Physical activities.

The PIM remains stable as technology evolves, extending and thereby maximizing ROI. Portability and interoperability are built into the architecture. MDA relies on the MOF to integrate the modeling layers.

SARL, MOF, and MDA

SARL uses the MOF and as a universal model transformer, as it was designed to be.  The primary distinction is scope.

MOF Four Layer Architecture

builds two views (perspectives, viewpoints, models) of the same data as information sets, one perspective from the outside in, and the second perspective from the inside out.

 

Architecture

Behavior = Architecture * Content4Project SOAR documents

 

Practice = Concept * Architecture * Mechanism[Object*Process]5SARL

Mechanisms

Practice

Reason Situation
Purpose Execution