Refined ECSS Software Process Model for Critical SW Critical SW Case Study.

Slides:



Advertisements
Similar presentations
Rice Cooker Project Integration Phase Integration of Hardware and Software.
Advertisements

1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
Mahmut Ali GÖKÇEIndustrial Systems Engineering Lecture 2 System Identification ISE102 Spring 2007.
System Integration Verification and Validation
S Y S T E M S E N G I N E E R I N G.
Lecture # 2 : Process Models
Chapter 2 Software Processes (1/2) Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.
Chapter 2 – Software Processes
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Software Engineering 1 Evolutionary Processes Lesson 11.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
1 SYSTEM and MODULE DESIGN Elements and Definitions.
1 Introduction to System Engineering G. Nacouzi ME 155B.
Systems Engineering Management
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.
1 REQUIREMENTS ENGINEERING and SYSTEMS ANALYSIS Elements and Definitions.
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Software Engineering 1 The Life Cicle of Software Lesson 5.
ECSS Software Process M odel
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
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
Software System Engineering: A tutorial
1 Configuration Management “The Cookbook Approach”
Instructor: Peter Clarke
INTRODUCTION What is software? What is software engineering?
1 Lecture 5.2a: SEF Ch 8 SE Outputs Dr. John MacCarthy UMBC CMSC 615 Fall, 2006.
VST: dome THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS Ing. Davide Fierro THE LIFE CYCLE OF MODERN TECHNOLOGICAL PROJECTS.
NASA’s Goddard Space Flight Center Systems Engineering Mike Pryzby Swales Aerospace August 16-17, 2005.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Requirements Engineering ments_analysis.
Michael deLamare Requirements Management Program Functions R-9.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Project Life Cycles.
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
ECSS Software Process Model Implementation Examples
DPE CSSW Process Model Annex A WP-400 ECSS Case Study.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Software Engineering - Abdul Majeed. What is software? Definition of Software Engineering Software Process Generic view of Software Engineering Software.
NCSX Systems Engineering Management Plan Peer Review Bob Simmons May 15, 2003.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
Requirements Engineering ments_analysis.
Product development Engineering & Regulatory Raj Agrawal InnAccel.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
CMSC 2021 Software Development. CMSC 2022 Software Development Life Cycle Five phases: –Analysis –Design –Implementation –Testing –Maintenance.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
An Iterative Method For System Integration
SQA project process standards IEEE software engineering standards
Session 10 Dr. Dan C. Surber, ESEP
Supportability Design Considerations
SQA project process standards IEEE software engineering standards
Lockheed Martin Canada’s SMB Mentoring Program
Software Development Process
Software Engineering Lecture #45
המחלקה להנדסת חשמל ומחשבים תשע"ט (2019)
Chapter 11: Software Configuration Management
Instrument PDR Summary of Objectives
HART Technologies Process Overview
PSS verification and validation
GLAST Large Area Telescope:
Web Service Security support in the SSE Toolbox
UML Design for an Automated Registration System
Presentation transcript:

Refined ECSS Software Process Model for Critical SW Critical SW Case Study

Critical Software Critical Software Process Model Elements Project Phasing & Planning Critical Software System Requirements Engineering SW Criticality analysis Critical Software Requirements Engineering Process System Requirements Analysis of Critical Software

Critical Software - Tailored Project Phasing & Planning ProcessT Elements of SW Maintenance Plan Requirements Baseline at SRR Documentation Standards Design Standards Verification and Validation Standards Software Project Development Plan Parent: Critical Software Development Process Perspective: Software Engineering Activity: Project Phasing and Planning Diagram: 4 / CRT External References: ECSS-E-40, ECSS-Q-80 In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Plan Review EI2: SW PA Procedures & Standards Review EI3: SW PA Life Cycle Review External Outputs (EO) Requirements Baseline at SRR Software Project Development Plan (Life cycle, tools and methods definition) Software Life Cycle Definition (milestones, reviews and maintenance planning) SLC-1 E-40: Documentation/Inputs- Output Process definition for each phase and Milestone SLC-3 E-40: SRR SUPPLIER ECSS-M-30 PROJECT RQMTS ECSS-E_40 Sec 4.5 System vs Software Requirements Requirements Baseline SW Project Development Plan SUPPLIER Definition of Software Engineering Standards SLC-2 E-40: Requirements Baseline SW Project Development Plan SUPPLIER Software Project Development Plan Review EI1 EI2 EI3 Analysis of applicability of critical SW standards to the project T Dependability & Safety specific Standards & Process Requirements (CUSTOMER) / SUPPLIER

Critical Software - Tailored Software System Requirements Engineering ProcessT Overall System Requirements RB (inputs to) IRD (inputs to) Electrical Design Spec PICA Spec Parent: Critical Software Development ProcessPerspective: Software Engineering Activity: Critical SW System Requirements Eng.ng Diagram: 12 / CRT External References: ECSS-E-40 sec , 5.2.3, 5.2.4, In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) System level Rqmts for SW Verification and Validation SE –3 E-40 sec SRR Critical SW System Requirements Analyis SE –1 E-40 sec System Partitioning SE-2 E-40 sec CUSTOMER System level Integration of Software SE –4 E-40 sec CUSTOMER SRR Data Package RB, IRD DJF RB: V&V Process requirements, including Test Requirements for Critical SW RB (inputs to) IRD (inputs to) Reviewed SRR Data Package RB, IRD DJF Software Criticality Analysis T Test Planning for Critical Software T Software Criticality Analysis Consolidation T SW Support Spec SW Criticality analysis Inputs to SW Project development plan

Critical Software - TailoredT Parent: Critical SW System Requirements Engineering Perspective: Software Engineering Activity:SW Criticality analysis Diagram: 12.1/ CRT External References: In Triggers (IT)Out Triggers (OT)External Inputs (EI)External Outputs (EO) SUPPLIERCUSTOMER Definition of SW Categorization Check Of Categorization applicability to projected SW System Spec (PICA Spec) Proposed categorization Supplier feedbacks SW Criticality analysis Inputs to SW Project development plan

Activity: Critical SW System Requirements Analysis Diagram: 13 / CRT Critical Software - Tailored System Requirements Analysis ProcessT RB: Functions & Performance Rqmts IRD: Interface Rqmts Parent: Critical SW System Requirement Engineering Process Perspective: Software Engineering External References: ECSS-E-40 sec , , In Triggers (IT) Out Triggers (OT) External Inputs (EI)External Outputs (EO) Definition of system functionalities and interfaces SYS-1 E-40 sec Overall system reqmts Operations and Maintenance Requirements Definition SYS-2 E-40 sec , V&V Rqmts and Design Constraints SYS-3 E-40 sec System Criticality / Critical Functions Definition SYS-4 E-40 sec RB:- Safety & Reliability Rqmts - Critical functions identification RB: Design Constraints V&V requirements - SW Eng. Standards RB: Operations and maintenance requirement RB (inputs to) IRD (inputs to) CUSTOMER Dependability & Safety Specific Requirements Definition for Critical Software T RB: Dependability/Safety Requirements for Critical SW Requirements CUSTOMER

Critical Software - Tailored Software Requirements Engineering ProcessT Activity: SW Requirements Engineering Process DIAG.#15 / CRT TCS SRD SUPPLIER External References: ECSS-E-40 sec.5.4.2, 5.4.3, Parent: Critical Software Development Process Perspective: Software Engineering In Triggers (IT)Out Triggers (OT)External Inputs (EI) EI1: SW PA Requirements (diag. 26) External Outputs (EO) Software Requirements Analysis R-1 E-40 sec SUPPLIER SW Support Spec PICA Spec EI1 Preliminary Design Review E-40 sec Delivered PDR DP Reviewed PDR DP PDR Data Package PDR Report Reliability and System Analysis Q-80 sec e System Level Functional Analysis SW RAMS Analysis Higher Level Safety Plan Software Top Level Architectural Design R-2 E-40 sec SW Prototyping for Critical Components T SW Criticality analysis Use of Petri Nets for dynamic aspects and concurrent feature of TCS SW T