Introduction to Systems Engineering Abd-El-Kader SAHRAOUI ([email protected]) Industrial Dept Toulouse University: www.iut-blagnac.fr and Laboratoire d‘Analyse et d‘Architecture des Systems LAAS du CNRS, Toulouse France : www.laas.fr

• • • • • • •

Systems Engineering I Systems Engineering II Systems Engineering Standards : EIA 632 Requirements management I Requirements managements II : Traceability Verification and Validation (V&V) Case studies

• 1. Grasp the importance of SE • 2. Knowledge about the context and SE Framework • 3. Stimulus for further SE Knowledge acquisition

What is the systems engineering : produce an impression or create a rabbit

Systems engineering is also an art without magicic

System Engineering: Definition (Incose) Systems Engineering is an interdisciplinary approach and means to enable the realization of successful systems. It focuses on defining customer needs and required functionality early in the development cycle, documenting requirements, then proceeding with design synthesis and system validation while considering the complete problem: •Operations •Performance •Test •Manufacturing •Cost & Schedule •Training & Support •Disposal

System Engineering: Definition (Incose) Systems Engineering integrates • All the disciplines and • specialty groups into a team effort forming a structured development process that proceeds from concept to production to operation. Systems Engineering considers both • The business and • The technical needs of all customers with the goal of providing a quality product that meets the user needs.

A simple example : A pen We need : why a new pen • Its primary function • The stakeholders : writers, designers, salesman, … • Cost constraints and related data (market) • Accumulated knowledge (the writing have been with for centuries ..) • More detailled requirements • related discipline • Chemistry (Ink) • Mechanics/metallurgy, manufacturing

System Engineering and System integration Integrated Integratedengineering engineering

methodology methodology

? Standard Standard processes processes

Project Projectmanagement management

? Systems Systemstheory theory

?

?

?

? ? quality quality

Maîtrise Maîtrised’ouvrage d’ouvrage Maîtrise Maîtrised’œuvre d’œuvre

? integration integration

Technical Technicalsystem system

Control Controlsystem system

système système d’organisation d’organisation

Information Information System System

Sub-system technology Sub-system human

Sub-system Information

Technological System Logistic

Information and Decision System

Standards IEEE 1220 EIA 632 ISO 15288

System engineering

System Integration

Expertise for specific domain

Chemical

Soft-Eng ISO 12207

Mechanical

Implementation of each component

External Environment • LAWS & REGULATIONS • LEGAL LIABILITIES • SOCIAL RESPONSIBILITIES • TECHNOLOGY BASE • LABOR POOL • COMPETING PRODUCTS • STANDARDS & SPECIFICATIONS • PUBLIC CULTURE

Enterprise Environment • POLICIES & PROCEDURES • STANDARDS & SPECIFICATIONS • GUIDELINES • DOMAIN TECHNOLOGIES • LOCAL CULTURE

Project Environment Enterprise Support

• DIRECTIVES & PROCEDURES • PLANS • TOOLS • PROJECT REVIEWS • METRICS

Process Groups for Engineering Systems

Project Support • Project Management • Agreement Support

Project A Project B Project C

• • • • •

Acquisition & Supply Technical Management System Design Product Realization Technical Evaluation

• • • • • • •

Investment Decisions External Agreements Infrastructure Support Resource Management Process Management Production Field Support

Layer N Building Block System ••• End Product

Subsystem

Test Products

Development Products

Subsystem

Support Products

Deployment Products

Production Products

Disposal Products

Training Products

Layer N+1 Building Blocks System

System •••

••• End Product

Development Products

••• Subsystem

Subsystem

Test Products

Production Products

Training Products

Deployment Products

Disposal Products

Support Products

End Product

Development Products

••• Subsystem

Subsystem

Test Products

Production Products

Training Products

Deployment Products

Disposal Products

Support Products

Elicitation and ... Acquisition ... • •

Elicitation versus acquisition Main issues about elicitation : ethno and sociological

Requirement elicitation is a team effort

Requirements management • • • • •

What do we manage Managing to objective Traceability Requirements prioritisation Problems with metrics

Manage your Requirements => Manage your time

Requirement expression • • • •

Maturity levels for expression Standard languages and methods Dedicated methods Others

Intended message and perceived message : That´s all about semantics !! Pragmatics and Syntactic issues have a role

Requirements exchange • •

The exchange process The rationale behind

Exchange is a must : Easiness of requirement validation statement

Where do you come from ? Do you mean which country or which University I come from ? No I mean which place have you been before !!

Requirement validation • • •

Importance of Validation V&V Techniques Case studies

Eureka, It Works !! It means it corresponds to What You requested , What You required What You needed

Standards • • • •

IEEE-1220 INCOSE/EIA-632 ISO 15288 Specific : aeronautic . ARP and space ECSS-E10 Standard are guideline for common understanding and Good Practice

Case Studies • •

Requirements expression case with Statemate (Lab) Traceability issues with RTM (Lab)

Why SE : A Bad Experiences with SoftEng (source NASA)

(4) IN S T IT U T IO N A L USERS p r o v id e o b je c tiv e s O PERATO RS ( O p e ra tin g T r a f fic C o n tro l S y s te m s )

p ro v id e T ra ff ic C o n tr o l S t

p ro v id e tra f fic c o n tr o l s e r v ic e s F IN A L U S E R S

P ro fe s s io n a l U s e r s (ta x is , e tc .)

C itiz e n s a n d a s s o c ia tio n s

B U S IN E S S U S E R S (C o m p a n ie s )

(2) : The Jackson View

• A View based on environment and context • • • •

A machine (system) to be developped Machine interacts with environment User needs make abstraction on system internal The environment exist; the machine to be developped • Shared phenomen : The machine (Private)

Shared

The Environment (Private)

Requirement and concept of operation (3) • The concept of operations (ConOps) document is a bridge between the operational requirements (events occurring over time) and the technical requirements (static, hierarchical description). It is written in narrative prose that is in the user's language. It states priorities, it uses visual images and leads to sofware requirements. • IEEE Standard 1362, IEEE Guide for Concept of Operations Document, 1998.

Needs, requirement and specification

Concept of operations (the mission)

NEEDS

Requirements

Specification (Software requirements)

Challenges in SE • A System View : Global View • An interdisplinary • Comparative methodologies • From In House to General approach

Basic Introduction System Engineering

System Engineering Engineering II System