Ω
Quality Assurance for Systems Engineering (INSE 6280/2-WW)
2
Ω
Course Outline
Preliminary Notions
Systems Engineering
Life Cycle Processes
Course Project
3
Ω
Instructor: Dr. J. Bentahar
Office: EV007.630
Lectures: Thursday, 17h45 – 20h15
Office Hours: Wednesday, 10h00 – 12h00 or by appointment
Phone: 848-2424 ext. 5382
E-Mail: [email protected]
4
Ω
Course Web:http://www.ciise.concordia.ca/~bentahar/inse6280.html
Lecture notes
Assignment
Useful links
Useful information
Printed with FinePrint - purchase at www.fineprint.com
5
Ω
Software Systems Procurement 6
Ω
Quality Assurance in Systems Engineering:Systems engineering process Quality assurance in this process
Objectives: To discover and learn various concepts and techniques in SE and quality assuranceTo learn to apply these techniquesTo develop critical thinking skills
7
Ω
Quality Assurance In Systems Engineering
Systems Engineering Quality Factors Quality Assurance
System
Verification ValidationSystem Modeling
SimulationAnd High
Level Architecture
Multi-Agent Systems
Reliability and Maintainability
8
Ω
There is no textbook that covers all the parts of this course
1) Systems Engineering and Analysis, (4th Edition), 2006
Part 1: Introduction to Systems Part 4: Design for Operational Feasibility
Reliability, Maintainability, Usability, Supportability
Printed with FinePrint - purchase at www.fineprint.com
9
Ω
2) Assurance Technologies Principles and Practices: A Product, Process, and System Safety Perspective, (2nd Edition), 2006
System quality, safety, reliability, maintainability, human engineering, logistics, software integrity, and system integration
10
Ω
3) Principles of Model Checking (2006)Verification and ValidationAvailable from the course web site
4) Multiagent Systems: A Modern Approach to Distributed Artificial Intelligence (1999)
Available from the course web site (Useful Link)
11
Ω
One individual/group assignment16%
One in-class mid-term exam (closed book)25%
One in-class final exam (closed book)25%
One team project (2~3 members, presentation + report)
17% + 17% = 34%
12
Ω
November 20, 2008Project Presentation
November 27, 2008 Final Exam
October 23, 2008 Midterm Exam
October 09, 2008 Assignment
October 02, 2008Project Proposal
December 04, 2008Project Report
Printed with FinePrint - purchase at www.fineprint.com
13
Ω
Course Outline
Preliminary Notions
Systems Engineering
Life Cycle Processes
Course Project
14
Ω
Systems engineering: an interdisciplinaryapproach enabling the realization and deployment of successful systems that satisfy customer needs
Interdisciplinarity: a type of academic collaboration in which specialists drawn from two or more academic disciplines work together in pursuit of common goals
15
Ω
Systems Engineering
Civil Engineering
Mechanical Engineering
Electrical Engineering
…Aeronautical Engineering
Chemical Engineering
16
Ω
System: an assemblage or combination of elements comprising a whole with each element related to other elements
Any element which has no relationship with any other element of the system, cannot be a part of that system
Printed with FinePrint - purchase at www.fineprint.com
17
Ω
Components: operating parts of a systemAttributes: properties of the componentsRelationships: links between components and attributes
System State: current value of a system's components, attributes, and/or relationships
18
Ω
Example: A food chain models the movement of energy in an ecosystemComponents: The Sun, Plants, Herbivores, and CarnivoresAttribute: units of energyRelationships:
The sun creates 100,000 Units of Energy Plants capture 1% of the energy from the sun (1,000 Units)Herbivores consume 10% of the energy produced by the plants (100 Units) Carnivores capture and consume 10% of the energy stored by the herbivores (10 Units)
19
Ω
Functional View
Input: addition of material, energy, or information to a systemProcess: Altering material, energy, or informationOutput: movement of matter, energy, or information out of a system
Input Output Process
20
Ω
Subsystem: a set of elements which are a proper subset of the whole system
A subsystem is a component of a system in an hierarchal view
Example: Air transportation systemSubsystems: aircrafts, terminals, ground support equipments
Printed with FinePrint - purchase at www.fineprint.com
21
Ω
Natural Systems vs. Design SystemsNatural Systems: came into being by natural processes (e.g. the ecosystem and solar system)Design Systems: man made systems (e.g. storage systems and tool boxes)
Physical Systems vs. Conceptual SystemsPhysical systems: based only on matter and energy (e.g. manufacturing systems)Conceptual systems: based on symbolic components (e.g. plans and computer programs)
22
Ω
Static Systems vs. Dynamic SystemsStatic Systems: having structure without activity (e.g. a bridge and a dam)Dynamic Systems: combine structural components with activity (e.g. University: buildings, libraries, students, professors, administration, etc.)
Open Systems vs. Closed SystemsOpen systems: Information, energy, and matter can pass the system boundaries (e.g. business organizations)Closed systems: do not interact with the environment. Information, energy, and matter are fixed by boundary conditions (e.g. a prison)
23
Ω
Course Outline
Preliminary Notions
Systems Engineering
Life Cycle Processes
Course Project
24
Ω
In 1990 a professional society for systems engineering, the National Council on Systems Engineering(NCOSE), was founded by representatives from a number of US corporations and organizationsINCOSE: International COSE
Printed with FinePrint - purchase at www.fineprint.com
25
Ω
Systems engineering focuses on:Defining customer needs and required functionality,Documenting requirements, Proceeding with design synthesis and system validation
Systems engineering considers both the business and the technical needs of all customers The goal of systems engineering is to provide a quality product that meets the user needs
26
Ω
Systems engineering: the art and science of creating a product or service based on phased efforts:
Definition, design, development, production and maintenance activities
The characteristics of the resulting product:
Functionality, high quality, reliability, maintainability, safety, etc.
27
Ω
Reliability engineering: the discipline of reducing the frequency of breakdownsMaintainability engineering: the discipline of dealing with the frequency of breakdowns to prevent the occurrence of downtimeSafety engineering: the discipline of minimizing the probability of critical failures and identifying safety hazards
28
Ω
Systems engineering: a management technology that controls a total system life cycle processSystems management: the strategic level of systems engineering A system life cycle process involves the
definition, development, and deployment of a new product or service
Printed with FinePrint - purchase at www.fineprint.com
29
Ω
Systems Management (Strategic Level)
Systems Engineering Processes
(Conceptual Level )
Systems Engineering Methods and Tools
(Development Level )
30
Ω
Systems engineers assist and support planning, decision making and resource allocation
Quantitative and qualitative formulation, analysis and Interpretation of the impact of action alternatives
31
Ω
Methods and Tools for Systems Engineering
Quality Control Simulation & Modeling
Programming Languages
Requirements Engineering
Economic Analysis
Communication Theory
32
Ω
Systems Engineering Processes
Life Cycle Analysis
Quality Assurance
Configuration Control
Performance Control
Cognitive Ergonomics
Systematic Measurements
Printed with FinePrint - purchase at www.fineprint.com
33
Ω
Course Outline
Preliminary Notions
Systems Engineering
Life Cycle Processes
Course Project
34
Ω
Product Use, Phase-out, and
Disposal
Production and/or
Construction
Detail Design and
Development
Conceptual and Preliminary
Design
Acquisition Phase Utilization Phase
NEED
35
Ω
Conceptual Design:1- Feasibility study:
Needs analysisSystem operational requirementsSystem maintenance concept
2- Specification3- Planning
36
Ω
Product Use, Phase-out, and
Disposal
Production and/or
Construction
Detail Design and
Development
Conceptual and Preliminary
Design
Acquisition Phase Utilization Phase
NEED
Printed with FinePrint - purchase at www.fineprint.com
37
Ω
Preliminary Design1- Functional Analysis
• Functional requirements
• Operational functions
• Maintenance functions
• Identification of alternative functions
2- Design Criteria
• Allocation of performance factors and design factors
• Allocation of system support requirements
3- Optimization
• Evaluation of alternatives
• System and subsystems analysis
4- Synthesis
• Design performance, configuration (data, physical models, testing, etc.
• Detail specifications
38
Ω
Product Use, Phase-out, and
Disposal
Production and/or
Construction
Detail Design and
Development
Conceptual and Preliminary
Design
Acquisition Phase Utilization Phase
NEED
39
Ω
Detail Design1- System Design
• Design of functional system
• Design support functions
• Design data and documentation
• Design review
2- Prototype Development
• Development of system prototype model
• Development of system logistic support requirements
3- Test and Evaluation
• Test preparation
• Prototype system testing
• Test data, analysis, and evaluation
• Test reporting
• Test review
40
Ω
Product Use, Phase-out, and
Disposal
Production and/or
Construction
Detail Design and
Development
Conceptual and Preliminary
Design
Acquisition Phase Utilization Phase
NEED
Printed with FinePrint - purchase at www.fineprint.com
41
Ω
Production and/or Construction:1- System assessment analysis and evaluation2- Modification for Corrective action
Utilization and Support:1- System assessment analysis and evaluation2- Modification for Corrective action
42
Ω
Proposed by A. T. Bahill and B. Gissing, 1998
43
Ω
State the problem: identifying and understanding customer needs, discovering requirements, and defining system functions Investigate alternatives: evaluating alternatives according to performance, cost, schedule and risk Model the system: modeling the system and sub-systems functions, running models to clarify requirementsIntegrate: designing interfaces and bringing system elements together so they work as a wholeLaunch the system: running the system and producing outputsAssess performance: using evaluation criteria to assess the system performanceRe-evaluation: re-evaluating the solution in a continual and iterative manner with many parallel loops
44
Ω
WaterfallVeeSpiralOthers
Printed with FinePrint - purchase at www.fineprint.com
45
Ω
Introduced by Royce in 1970
Each phase is carried out to completion in sequence until the product is delivered
This is not possible in all cases
46
Ω
The model starts with user needs and ends with a user validated system
Left side: the system architecture
Right side: Integration and verification
Middle side : testing
47
Ω
Developed by Boemfrom 1969 to 1986
Risk driven approach
Adaptation of the waterfall model (the use of prototypes)
Iterative application: each time a different type of prototype is developped
48
Ω
Computer-Aided Software Engineering(CASE)
The use of software tools to assist in the development and maintenance of software
All aspects of the software development life cycle can be supported by CASE tools
From project management software through tools for business and functional analysis, system design, code storage, compilers, translation tools, test software, and so on
Printed with FinePrint - purchase at www.fineprint.com
49
Ω
Course Outline
Preliminary Notions
Systems Engineering
Life Cycle Processes
Course Project
50
Ω
Three choicesSynthesis of a set of papers and/or book chapters
Case studies, for example, NASA, IBM, TOYOTA, …
Software demonstration
Topics: Quality, Validation, Verification, Reliability, Safety, Modeling, Simulation, MAS, and HLA
51
Ω
Project proposalDeadline: October 02, 2008Team membersTopic and titleMain reference
52
Ω
Lecture 1: Chapters 1 and 2 of Systems Engineering and Analysis
Lecture 2: Chapters 1 and 6 of Assurance Technologies, Principles and Practices
Printed with FinePrint - purchase at www.fineprint.com