2 Dechazelles Fraboulet

  • 236 views
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
236
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
1
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Use of Requirement Engineering Discipline in support of A/C Engineering Presented by: Gaëlle Fraboulet, Seditec Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 2. Objectives l Some definitions of Requirement Engineering l Highlight motivation for using Requirement Engineering l Understand Requirement Engineering process across levels l Understand the application of Requirement Engineering to Product and Sub-product l First conclusions on Deployment of Requirement Engineering for Airbus A380 Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 2
  • 3. Requirement Engineering Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 4. What is Requirement Engineering? l Discipline which addresses requirements as objects all along a system development process l Discipline that provides a set of processes to identify and engineer requirements, not only manage but also analyse, validate , trace... Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 4
  • 5. What is a requirement? RATIONALE STAKEHOLDER Emitted_by Supported_by ASSUMPTION Conditioned_by Associated_with REQUIREMENT RISK Result_from Verified_by TRADE_OFF Allocated_to VERIFICATION PRODUCT PROCEDURE Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 5
  • 6. Requirement structure & richness Example: BNEY-SER-038-1 When producing requirements in Word document, Developer shall use iSEF CARE Macro V5 or any iSEF tool agreed by BNE. Element Definition Minimum Example elements 1 Actor of action Subject of the sentence Mandatory Developer When producing 2.Condition for Conditions under which requirements in Word action the action takes place document 3. Action A verb Mandatory shall use 4. Constraints of Qualification of the action action 5. Object of Thing acted upon by the Mandatory iSEF CARE Macro V5 action actor 6. Object Or any iSEF tool agreed Qualification of the object Refinement by BNE 7. Action Further qualification of Refinement the action 8. Other Non requirement material Most requirements should have 5-7 elements Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 6
  • 7. Motivation for using Requirement Engineering Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 8. Motivation Requirements Engineering eases the V&V and certification process Ä By supporting a rigorous , traceable means of compliance (Requirements management, traceability, verification) Ä By contributing to fulfil ARP 4754 recommendations (ARP 4754: Certification Considerations for Highly-Integrated or Complex Aircraft Systems) Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 8
  • 9. Considerations for Highly Integrated or Complex Aircraft Systems (ARP4754) Aircraft Functions Aircraft Level Functional Failure Condition, Effects, Requirements Classification, Safety Objectives Systems Functions Allocation of Aircraft Functions to Systems Failure Condition, Effects, Safety Classification, Safety Objectives Development of System Processes Architectural Requirements Architecture System Architecture Allocation of Item Requirements Item Requirements to Hardware & Software Implementation System Implementation Results Physical System Certification Safety Assessment Process System Development Process Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 9
  • 10. Identified expectations for Systems Development from ARP4754 l Added design discipline and development structure to ensure that safety and operational requirements are fully realized and substantiated (cf & 1.1 Purpose) l Functional requirements to obtain the desired performance of the system under the conditions specified. They are a combination of customer desires, operational constraints, regulatory restrictions, and implementation realities. (cf &5.2.2 Functional Requirements) l Traceability one of the mean for validation: The requirement should either be traceable to a parent requirement, or by identification of the specific design decision or data from which the requirement was derived. Ä Airbus has developed and deployed a C.A.R.E Capability that covers Process/Method/Tools as a means to comply with ARP4754 requirements Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 10
  • 11. Requirement Flowdown across Development levels Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 12. Engineering Process Flow in support of A/C Product Development according to EIA 632 Airlines needs Feedback A/C Design Level N+1 Other Stakeholders process Requirements Assigned Feedback Specified Requirements Major Comp Level N Design Other process Stakeholders Requirements Assigned Feedback Specified Requirements Item Design Level N-1 Other process Stakeholders Requirements Feedback Assigned Specified Requirements Sub-item Other Design Stakeholders process Requirements Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 12
  • 13. Representation of complex product breakdown (EIA 632) Performs Performs associated operational life-cycle Complex process functions product Functions End-products Enabling-products Consists of Development products End-Product Production products Test products Deployment Main Comp. Main Comp. Main Comp. Main Comp. products or system or system or system or system Training products Support This representation of complex product apply products at any level where product decomposition occurs! Disposal products Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 13
  • 14. Relation between development level and product breakdown Complex product End-products Enabling-products Airlines Development products needs End-Product Production products Test products Deployment Main Comp. Main Comp. Main Comp. Main Comp. products A/C or system or system or system or system Design Training products process Support products Disposal products Major Comp Design process Item Design process The result of architecting the product at one level Sub-item Design is a set of sub-products description process at lower level Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 14
  • 15. A380 Requirements cascade objective Program Aircraft A/C components Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 15
  • 16. V&V Strategy • V&V activity depends on the assurance level required. • The V&V assurance level assigned is based on : • Certification consideration based on the most severe failure condition classification set for safety objectives for each function • Maturity consideration based on events, which could lead to flight interruption or a delay. • Example: For a system that could be level D for safety issue, if the novelty risk is high, the V&V assurance level becomes B’. Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 16
  • 17. Application of Requirement Engineering to Product and Sub-products Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 18. Requirements flowdown attached to each product or sub-product (EIA 632) Acquirer Requirements Other Technical Assigned to Stakeholder Requirements Requirements Assigned to Assigned to Physical Logical Solution solution representation representation source of drive drive Derived Design Solution Assigned to Technical Specified by Requirements Specified Requirements Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 18
  • 19. A/C Physical Architecture TLRs PRODUCT BREAKDOWN √ √ √ √– 1 ACCOMODATE PAYLOAD √– √ √ √ 2 MOVE FROM DEPARTURE TO ARRIVAL A/C √3 – - √ √ √ Functional ACCOMODAT E COMMON RESSOURCE Architecture S 4 – SUPPORT √ OPERATION, FDD FRD MAINTENANC E AND √ √ √ √ AIRLINE PROMOTION 5 –√ ENSURE SAFETY / √ √ √ SECURITY OF OPERATIONS TLSRD or TLStRD Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 19
  • 20. Requirements Flow across Layers Application to A380 Development Process TLRs FRD FDD A/C Level TLSRD « Systems/structure » Level System A System B Structure element C SRD SDD SRD SDD PTS PTS Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 20
  • 21. Conclusion - Reminder - Status & wayforward Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus
  • 22. Strategy for Establishment and Deployment of Requirement Engineering • Observation Requirement Engineering is a new discipline that requires time to be understood and deployed. • Strategy Focus has been made on how to engineer a requirement rather than how to manage requirements. •Impact: Priority has been given to the process and method deployment rather than tool deployment. •Schedule ØSept. 1999: First Draft of process established commonly by previous Airbus partners: Aerospatial (France), Daimler-Chrysler Airbus (Germany), BAe Systems (UK), CASA (Spain) ØMid 2000: First Word Macro ØEarly 2001: Decision to deploy widely Process and Macro ØUntil today: Requirement Management tool under deployment Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 22
  • 23. Status & way forward • Current Status •Requirement Engineering is now a corner stone of Aircraft Engineering at all levels for the A380 •Way forward •Continuous improvement and training are necessary to move from a document oriented approach to a Requirement Engineering as part of System Engineering approach Prepared by G. Fraboulet, Seditec and P. de Chazelles, Airbus Page 23