ILogix Business Profile

1
I-Logix Response to Systems
Engineering DSIG RFI
2
Who We Are

• Tool Vendor
• Established in 1987 - Statemate MAGNUM?
• Aerospace market origin
• Systems specification, analysis, design and
  validation
• Launched in 1998 - Rhapsody?
• Unified Modeling Language? (UML?) compliant
  software development platform
• Core competencies
• Real-time systems
• Visual behavioral modeling
• Formal verification
• Production quality code generation
• UML (one of the UML 2.0 U2 Partners)

3
Types of Systems and Products

• Experience and opinions expressed in RFI are
  based on years of working with our customer base.
• Types of systems we concentrate on are Real Time
  Embedded in the Aerospace, Defense, Automotive,
  Medical and Telecoms marketplace.
• Customer products include flight control systems,
  cockpit displays, weapon systems, automotive body
  electronics and medical equipment.

4
Classical V-Diagram of the Engineering
Lifecyclein a Model based Development
5
Modeling languages and viewpoints used by our
customers

• Object-Oriented Approach - Rhapsody
• Meeting the needs of systems and software
  engineering using standard UML
• Function-driven Approach Statemate
• Meeting the needs of systems and software
  engineering using functional decomposition
• Hybrid Development Approach
• Meeting the needs of functional systems
  engineering (Statemate) and object-oriented
  software development (Rhapsody)

6
Object-Oriented Approach

• Attached with RFI is Bruce Douglas paper entitled
  The UML for Systems Engineering.
• Uses standard UML use cases, scenario diagrams
  and Statecharts are used to capture an
  requirements model.
• Object/class, collaboration and deployment
  diagrams are used to show the structure of the
  system, with packages as a means of partitioning
  the system. Behavioral aspects are described with
  Statecharts and activity diagrams.

7
Function-driven Approach

• Uses cases, scenario diagrams and Statecharts are
  used to capture requirements.
• These are aggregated to produce a top level
  extended data flow diagram to show system
  context.
• Extended DFD are multi level data flow diagrams.
  They show the static structure of the system.
  Uses functional decomposition and is hierarchal.
• Basic functional blocks can be used to show
  behavior an example follows.
• In Statemate Extended data flow diagrams and
  behavior is a formal language with action
  language that can be executed for verification
  and validation.

8
Extended Data Flow Diagrams Summary

• Show Parent - Child relationship
• Show the context of the system under design
• Represent the system in terms of a functional
  decomposition
• Represent the system in terms of a physical
  breakdown
• Show the external elements of the system
• Capture data flow
• Capture continuous and discrete flow
• Distinguish between control and data flow
• Show how data is disseminated
• Capture the inputs and outputs of system
  functions
• Show data-stores
• Decompose data-stores and data-flows
• Associate basic activities with behavioral
  content
• Control the execution of activities through
  controlling Statecharts

9
Example

• Extended Data Flow Diagram
• 
  
  Continuous Chart
• Mini Spec/Pseudo Code
• started/

10
Hybrid Development Approach

• Attached to the RFI response is Peter Hoffmanns
  paper entitled From function-driven systems
  engineering to object orientated software
  engineering.
• Uses a mapping approach from Functional to
  Objected Orientated.

11
Translation Rules
1 UML Static reaction in one-state
statemachine Rh Reactive behavior copied into
the description field of the class 2 No mapping,
as Data Stores are used in Statemate to bundle
InfoFlows
12
Experience and Disciplines

• Our approaches have been used on small (5
  stakeholders) pilot projects to large (100
  stakeholders) production deployable systems.
• Part of the process is to use our tools within a
  concurrent engineering environment. All
  engineering stakeholders within the project were
  involved in the modeling activities including
  project management, domain experts, systems
  engineers, hardware engineers, electrical
  engineers, test engineers, software engineers,
  mechanical engineers ..

13
Tools used

• Statemate Magnum and/or Rhapsody Product Family.

14
Non UML Extensions Used

• Our Statemate customers have supplemented
  existing UML (Use cases, Scenarios, Statecharts)
  with Extended Data Flow Diagrams that can be
  executed.

15
Benefits of using UML

• Better communication between systems and software
  engineering through standardization of
  communication.
• Model interchange between systems and software
  with no loss of information.
• Producing executable models allows engineers to
  verify to find errors early on in the design
  process, both for systems and software
  engineering.

16
Limitations of UML syntax, semantics, usability

• Generally speaking systems engineers have been
  slow to adopt UML as it is today.
• Use cases and scenario diagrams have helped
  greatly in allowing systems engineers to capture
  requirements but is this enough?
• Not all behaviors can be captured, such as
  continuous time behaviors.
• Interface and data-flow definition is still in
  its early stages.
• System engineers would like to produce a model in
  UML that can be executed without writing code.

17
Potential solutions

• Adding a optional Extended data flow diagram with
  added behavioral views, continuous charts, lookup
  tables and truth tables.
• Action Language for systems engineers to allow
  UML model to be executable.

18
I-Logix Level of Interest

• We want to work with this team and the customer
  base to implement the requirements for UML for
  systems engineers.
• We will use the results.
• We want to participate in the SE DSIG effort.