® ibm software group © 2007 ibm corporation achieving harmony ibm's platform and methodology...

®

IBM Software Group

© 2007 IBM Corporation

Achieving Harmony

IBM's Platform and Methodology for Systems Engineering and Embedded Software Development

IBM Software Group | Rational software

2

Agenda

A Systems Perspective

Challenges in Systems Engineering

How Model Based Systems Engineering Helps

Harmony – A Model-Based Systems Engineering Approach


3

Systems Engineering

Systems engineering Entire lifecycle

Defines / refines requirements

The holistic view

Overall architecture

Interplay between components


4

A Systems Perspective

The systems approach focuses on systems taken as a whole, not on the parts taken separately.

It assumes that some properties of systems can only be treated adequately by taking into account all facets of the system. These system properties derive from the relationships between the parts of

systems: how the parts interact and fit together.

A basic assumption of systems engineering is that optimization of individual components or subsystems will not in general lead to a optimum system.

Similarly, individual component behavior cannot be understood without considering the components’ role and interaction within the system as a whole.


5

Challenges of Systems Engineering (1)

Increased system complexity Due to languages, technology, and global information flow capabilities.

Greater pace of change Time required to deliver solutions is reduced.

Systems development has not kept pace with the demands to deliver more capability in less time Using traditional methods, development teams often deliver late, or fail to

deliver at all.


6

Challenges of Systems Engineering (2)

Increasingly system failures arises from the interactions among components . High levels of interactive complexity is unmanageable using traditional

techniques.

The drive toward tightly coupled systems is fueled by a desire for higher levels of efficiency and functionality.

Software allows us now to achieve these higher levels of coupling and interaction that were previously impossible with pure electromechanical devices.


7

How Model Based Systems Engineering Helps

Modeling helps to: Manage complexity.

Simplify and abstract essential aspects of a system.

Increase understanding.

Enhance team communication.

Usable by engineers across multiple disciplines.

Common language promotes common understanding.

Reduce risk.

Model execution increases knowledge and reduces uncertainty and risk.

Provide traceability.

Models document what you have done.

Assess impact of change.


8

Benefits of Modeling

‘Better’ Systems – identify ‘defects’ earlier. Models may be verified and validated:

Statically – checking for consistency.

Dynamically – execution of models allows identification of missing, conflicting or overlapping requirements.

Increased productivity. Automation of workflows.

Re-use of intellectual property.

Model Based Systems Engineering leads to a more robust design. Reduced development time.

Fewer recalls.


9

Harmony – A Model Based Systems Engineering Workflow Model-driven hybrid iterative workflow, supporting:

Top-down systems engineering ( Rational HARMONY SE )

Incremental software engineering ( Rational HARMONY ESW )

Seamless transition from systems engineering to software engineering by using the SysML as paradigm independent modeling language. (“Same language, different dialects”)


10

Integrated system / software development process“V” Development Lifecycle

ModuleIntegration & Test


SystemAcceptance

SystemAcceptance

RequirementsAnalysis


Design SynthesisDesign Synthesis

System Functional Analysis


SWAnalysis & Design

SWAnalysis & Design

SW Implementation& Unit Test


System ChangesSystem Changes

(Sub-)SystemIntegration & Test


Requirements &Test Scenarios

Mo

de

l /

Re

qu

ire

me

nts

Re

po

sit

ory

*

StakeholderRequirements

System ArchitectureBaseline

* Configuration Controlled Knowledge of the System Under Development:

• Requirements Documentation • Requirements Traceability• Design Documentation• Test Definitions




Harmony forSystems

Engineering

Harmony forEmbedded RTDevelopment


11

Integrated system / software development processModel-driven development of embedded systems



SystemAcceptance

SystemAcceptance

Harmony forSystems

Engineering

Harmony forEmbedded RTDevelopment



Design SynthesisDesign Synthesis



SWAnalysis & Design

SWAnalysis & Design





Requirements &Test Scenarios

Mo

de

l / R

eq

uir

em

en

ts R

ep

os

ito

ry*

StakeholderRequirements

System ArchitectureBaseline

SoftwareImplementation

Model

Executable System Use Case Models

Requirements Models,System Use Cases Model

Architectural Analysis Model(s),System Architecture Model






System ChangesSystem Changes


12

Help every step of the way …

Every step of the workflow is fully documented

The Systems Engineering Toolkit automates many otherwise time consuming tasks


13

Customization, Consulting and Best Practices


14

Customizable Deployment in RMC/EPF


16

Jazz Integration Architecture

Search and Query

In Context Collaboration

Team Awareness

Events Notification

SecurityDashboards

RequirementsDefinition &Management

Analysis & Design

Quality Management

Release Management

Construction

Configuration & Change Mgmt

Asset Discovery,

Management & Reuse

Production / Operations

Enterprise Architecture/Architectural Frameworks

Measurement &Reporting

Product, Project &Portfolio Management

Rational Portfolio for Integrated System Delivery Lifecycle Management for Software and Systems Delivery

Systems IT

Rational System Architect

Rational Focal Point

Rational Insight

Rational DOORSRational Requirements Composer

Rational Rhapsody

Rational Team ConcertRational ClearCaseRational ClearQuestRational Synergy

Rational Asset ManagerRational Quality ManagerRational Logiscope

Rational BuildForge

EclipseRational Rhapsody

System Lifecycle Process ManagementRational Method Composer, Harmony


1717

© Copyright IBM Corporation 2009. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

® ibm software group © 2007 ibm corporation achieving harmony ibm's platform and methodology...

Documents

systems engineering

systems development

parts of systems

systems approach

properties of systems

systems perspective

ibm corporation

system properties