BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS115-01 By Leigh Watton Friday 27th July 2001.

Slides:



Advertisements
Similar presentations
Systems Engineering From a Life Cycle Perspective John Groenenboom Director Engineering – Mesa Boeing Rotorcraft Dec 12, 2007.
Advertisements

Interfacing Risk and Systems Engineering – Left Shift Risk Management
Technical System Options
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
S Y S T E M S E N G I N E E R I N G.
1 Requirements and the Software Lifecycle The traditional software process models Waterfall model Spiral model The iterative approach Chapter 3.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Project management Project manager must;
BAE SYSTEMS Example of Applied Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 5/19/2015/MS By Keith Minnican Friday 27th July 2001.
Introduction to Software Engineering Dr. Basem Alkazemi
EMIS Chapter 6. EMIS Chapter 6 EMIS Chapter 6 Fig 6.2 shows where the SEMP fits into the earliest program stages. Fig 6.5 has an.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Software Engineering CSE470: Systems Engineering 35 Computer System Engineering Computer System Engineering is a problem-solving activity. Itemize desired.
TECH 101 Product Design and Manufacturing. TECH 1012 System Life-Cycle Engineering 2 Major phases in almost all products and in many cases services –Acquisition.
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
Software Engineering Institute Capability Maturity Model (CMM)
Engineering Systems of.
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Web Development Process Description
S/W Project Management
Introduction to ISO New and modified requirements.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
From Research Prototype to Production
Refined ECSS Software Process Model for Critical SW Critical SW Case Study.
Instructor: Peter Clarke
SENG521 (Fall SENG 521 Software Reliability & Testing Software Product & process Improvement using ISO (Part 3d) Department.
Best Systems Engineering Products Drive CMMI NDIA 6th Annual Systems Engineering Supportability & Interoperability Conference October 21, 2003 Dr. Tom.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Configuration Management Non Government Std: EIA Standard-649 “A management process for establishing and maintaining consistency of a product’s performance,
Approaching a Problem Where do we start? How do we proceed?
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
Paul Hardiman and Rob Brown SMMT IF Planning and organising an audit.
Bill Fournier Nov 2014 Systems Engineer for Non SE Bill Fournier
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
Smart Home Technologies
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Project management Topic 2 Product based planning.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
1 Lecture 2.3: SE Process (SEF Ch 3) Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
Alex Ezrakhovich Process Approach for an Integrated Management System Change driven.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Installation and Commisioning SE view point Romuald Duperrier ESS SE manager.
Advanced Software Engineering Dr. Cheng
Camera PDR/CD1 Planning 19 September 2008
Session 10 Dr. Dan C. Surber, ESEP
Supportability Design Considerations
Chapter 10 Software Quality Assurance& Test Plan Software Testing
Software and Systems Integration
THE PROCESS OF EMBEDDED SYSTEM DEVELOPMENT
Development Projects / Analysis Projects / On-site Service Projects
Software Requirements
Level - 3 Process Areas (CMMI-DEV)
Software Prototyping Animating and demonstrating system requirements.
Raytheon Parts Management
MRL 6 Artifacts (at End of TMRR) Page 1 of 6
Software Development Process
EMIS 7307 Chapter 6.
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
Lecture # 7 System Requirements
Presentation transcript:

BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001

BAE SYSTEMS WOOLLY BIT The Total Engineering Process Currently Includes : Project Manager Customer With Money And Perceived Need Customer With Expectation Product Manufacture Detail Design The Woolly Bit

BAE SYSTEMS The total complexity of the system exceeds one person’s ‘Brainful’ Complexity Scale Width

BAE SYSTEMS The Concept of Left Shift

BAE SYSTEMS £ Cost of Changes Production Stage specifications drawings interface specs test specs schedule procurement specs purchase orders packaging test equipment tooling reviewing design proving tests operational trials EMC tests environmental trials cost estimates simulation and modelling component selection reliability assessment safety assessment design certificates pink wire mods configuration management Time Design Stage concept design plans/strategies estimates requirements analysis/modelling Late Changes => Bigger Impact

BAE SYSTEMS Systems Engineering Generic Activity Sequence (SEGAS) RBDFBDSBDPDDD Customer Acceptance TRR SRRFDRSDRPDRCDR ImpT&IA&C FCA PCA 3A3B45,6,7 Typical Phase Review correspondence for a development programme

BAE SYSTEMS System / Sub-System Interaction

BAE SYSTEMS The Basic RFS Loop System Analysis & Control (Balance) Requirements Loop Design Loop Verification R equirements Analysis F unctional Analysis and Allocation Design S ynthesis Process Input - Requirements Process Output - System Architecture - Specs and Baseline System Analysis and Control

BAE SYSTEMS The Core Design Process - 1 RF S S = C + D Customer Requirements System Requirements Specification System Requirements Specification System Functional Structure System Response Specification Sub System Requirements Specifications System Acceptance Specification Integration and Test Specifications

BAE SYSTEMS The Core Design Process - 2 RF Cust Req Sys Req Spec Sys Fun Struc Sys Resp Spec Sub Sys Req Specs Sys Acc Spec Int & Test Specs Sys Req Spec CD Sys Fun Struc Chosen Sol

BAE SYSTEMS The Core Design Process - 3 RF Cust Req Sys Req Spec Sys Fun Struc Sys Resp Spec Sub Sys Req Specs Sys Acc Spec Int & Test Specs Sys Req Spec CD Sys Fun Struc Chosen Sol Sol Concs Sys Fun Struc Concerns Sol Concs

BAE SYSTEMS Concurrency reduces the risk all round Bid System Engineer/Design Procure, Manufacture and Test Deliver Contract Supra System Engineer Research Maintain Operate Train Accept Procure System(s) In Service Use (User) Procure (Customer) Develop System (Contractor) Applied Research Risk Mitigation Feedback Support Replace or Upgrade The Product Lifecycle

BAE SYSTEMS Design and Specification Manufacture Parts Integrate and Test TIME LEVELLEVEL The ‘V’ Diagram

BAE SYSTEMS The ‘V’ Diagram - cont Tested and Partially-Proven System Accept Validated System and Sub Systems Customer Equipment and Operational Environment Customer's Development Activities System Engineering Activities Trials Integrate with Customer's Equipment Integrate and Test System Response Specification and Drawings System Reqts Spec Sub System Reqts Spec Response Specification and Drawings TIME L E V E L Customer Equipment and Operational Environment

BAE SYSTEMS The ‘V’ Diagram - cont Tested and Partially-Proven Sub System Tested and Partially-Proven System Accept Validated System and Sub Systems Customer Equipment and Operational Environment Customer's Development Activities System Engineering Activities Sub System Engineering Activities Trials Integrate with Customer's Equipment Integrate and Test System Integrate and Test Sub Systems Response Specification and Drawings Response Specification and Drawings Building Block Reqts Spec System Reqts Spec Sub System Reqts Spec Response Specification and Drawings TIME L E V E L Customer Equipment and Operational Environment

BAE SYSTEMS The ‘V’ Diagram - cont Detail Drawings and Plans Tested and Partially-Proven Building Blocks Tested and Partially-Proven Sub System Tested and Partially-Proven System Accept Validated System and Sub Systems Customer Equipment and Operational Environment Customer's Development Activities System Engineering Activities Sub System Engineering Activities Design Building Blocks Test Building Blocks Trials Integrate with Customer's Equipment Integrate and Test System Integrate and Test Sub Systems Response Specification and Drawings Response Specification and Drawings Building Block Reqts Spec Response Specification and Drawings System Reqts Spec Sub System Reqts Spec Response Specification and Drawings TIME L E V E L Customer Equipment and Operational Environment

BAE SYSTEMS The ‘V’ Diagram - cont Detail Drawings and Plans Building Blocks Tested and Partially-Proven Building Blocks Tested and Partially-Proven Sub System Tested and Partially-Proven System Accept Validated System and Sub Systems Customer Equipment and Operational Environment Customer's Development Activities System Engineering Activities Sub System Engineering Activities Design Building Blocks Produce Building Blocks Test Building Blocks Trials Integrate with Customer's Equipment Integrate and Test System Integrate and Test Sub Systems Response Specification and Drawings Response Specification and Drawings Building Block Reqts Spec Response Specification and Drawings System Reqts Spec Sub System Reqts Spec Response Specification and Drawings TIME L E V E L

BAE SYSTEMS The smallest System shown is at 'Building Block' level (e.g. a circuit board), made up from 'Components' System Hierarchy

BAE SYSTEMS Concurrency Highly serial, very little concurrency Highly concurrent The steepness of the “V” represents the level of concurrency

BAE SYSTEMS Refined Drawings and Test Equipment The ‘W’ Diagram - cont System Specification and Manufacture Detail Drawings and Plans Accept Validated System Customer Equipment and Operational Environment Customer's Development Activities System Engineering Activities Sub System Engineering Activities Design Building Blocks Trials Integrate with Customer's Equipment Response Specification and Drawings Response Building Block Reqts Spec System Reqts Spec Sub System Reqts Spec Produce Building Blocks Test Building Blocks Integrate and Test System Integrate and Test Sub Systems Specification and Drawings Response Specification and Drawings Response Specification and Drawings TIME L E V E L Produce Building Blocks Test Building Blocks Integrate and Test System Integrate and Test Sub Systems Specification and Drawings DEVELOPMENT PROTOTYPES PRODUCTION Refined Drawings and Test Equipment Refined Drawings and Test Equipment Refined Detail Drawings and Plans Production Acceptance Deliver Systems

BAE SYSTEMS Production Development Concept Demonstrator Concept Demonstrator In order to ‘gain hindsight’ early, a concept demonstrator is built before main development, shown as a narrow V The VW Diagram

BAE SYSTEMS The Process Model and the ‘V’ Diagram System Engineering Process Model Waterfall ‘V’ Diagram Product Hierarchy Time (process, product, time)

BAE SYSTEMS System Engineering Process Models ‘V’ Diagram It Applies at Each Level in the System Hierarchy The Process Model is Recursive

BAE SYSTEMS Prototype System and Support Equipment Plans Other Engineering Functions (Project Management, Production, Sub Systems etc.) Stated Requirements, Acceptance Agreement Support, Resources Sub System Suppliers Management Data, Agreed Requirements and acceptance criteria, Plans, Sub System Designs and Material, Design Proving Evidence, Design Certificate Test Equipment Requirements, Plans Test and Support Equipment Suppliers Customer Company Infrastructure Sub System Requirements, Plans Plans, System Design Procedures, Support, Management Data World User (Higher Level Tests/Trials) Constraints Compliance Evidence Management Data, Agreed Requirements and acceptance criteria, Plans, System Design, Design Proving Evidence, Design Certificate Facilities Test Records Perform System Engineering Project Management Data, Agreed Requirements and acceptance criteria,, Plans, Test and Support Equipment Designs and Material, Design Proving Evidence, Design Certificate Notes 1. The diagram is schematic only a few of the inputs and outputs are shown. 2. Sub system suppliers may be internal or external to own company. 3. The interface to sub system suppliers mirrors that with the customer and user when shown in detail. Records Support System Engineering Context Diagram

BAE SYSTEMS AC SECURE ACCEPTANCE AND CERTIFICATION SUB SYSTEM ENGINEERING AND IMPLEMENTATION T SUPPORT HIGHER LEVEL TESTS (TRIALS) SYSTEM TEST EQUIPMENT PROVIDE IN SERVICE SUPPORT ISS E ACCEPTANCE PROVIDE SPECIALIST DESIGN SUPPORT SS PERFORM SYSTEM ANALYSIS A HARMONISE SUB SYSTEM IMPLEMENTATIONS H START FMANAGE SYSTEM ENGINEERINGM DESIGN REVIEWS CREATE CANDIDATE SOLUTION CONCEPTS C A PERFORM FUNCTIONAL ANALYSIS F I INTEGRATE AND TEST SYSTEM D DESIGN SYSTEM AND SPECIFY SUB SYSTEMS R DETERMINE REQUIREMENTS SS M H SE Process Model (Level 2)

BAE SYSTEMS Perform Functional Analysis F Perform System Analysis A Determine Requirements R M Manage System Engineering Create Candidate Solution Concepts Provide Specialist Design Support Integrate and Test System Perform System Engineering Harmonise Sub Systems Implementations Support Higher Level Tests(Trials) CSSIAC Design System and Specify Sub Systems DHT Secure Acceptance and Certification LEVEL 1 LEVEL 2 Provide In Service Support ISS Level 3 Level 4

BAE SYSTEMS R Specify and Agree System Requirements Specify and Agree System Acceptance Criteria Determine Requirements Prepare for R Capture Requirements R1R2R3R4R5 Identify required skills and personnel Select methods and tools to manage requirements Produce plan, work breakdown, and programme Produce cost estimates Establish points of contact with customer/user organisation Define Supra System and interfaces Define required functions (see F2) Determine required performance Determine constraints on the system Determine support requirements Determine cost, numbers and timescale Determine customer’s selection criteria Determine customer’s requirements for Design Proving Determine non customer requirements Collect and collate requirement data Analyse requirements data for completeness Analyse functional requirements (see F2, F3) Use modeling and simulation to analyse requirements (see A) Develop understanding of requirements Explore impact of non-compliance Refine requirements Highlight risks Determine requirement specification format Produce requirement specification Demonstrate traceability from higher level specifications Review, agree and control requirement specification Determine conditions for acceptance Identify customer supplied items Produce system acceptance specification Review and agree system acceptance specification Analyse Requirements