Quality Assurance for Systems Engineering (INSE 6280/2-WW)

Transcription

1 Course Outline Quality Assurance for Systems (INSE 6280/2-WW) Preliminary Notions Systems Life Cycle Processes Course Project 2 Instructor: Dr. J. Bentahar Office: EV Lectures: Thursday, 17h45 20h15 Office Hours: Wednesday, 10h00 12h00 or by appointment Phone: ext bentahar@ciise.concordia.ca Course Web: Lecture notes Assignment Useful links Useful information 3 4

2 Quality Assurance in Systems : Systems engineering process Quality assurance in this process Objectives: To discover and learn various concepts and techniques in SE and quality assurance To learn to apply these techniques To develop critical thinking skills Software Systems Procurement 5 6 Quality Assurance In Systems There is no textbook that covers all the parts of this course Systems Quality Factors Quality Assurance System 1) Systems and Analysis, (4th Edition), 2006 System Modeling Multi-Agent Systems Simulation And High Level Architecture Verification Validation Reliability and Maintainability Part 1: Introduction to Systems Part 4: Design for Operational Feasibility Reliability, Maintainability, Usability, Supportability 7 8

3 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 3) Principles of Model Checking (2006) Verification and Validation Available from the course web site 4) Multiagent Systems: A Modern Approach to Distributed Artificial Intelligence (1999) Available from the course web site (Useful Link) 9 10 One individual/group assignment 16% 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% Project Proposal Assignment Midterm Exam Final Exam Project Presentation Project Report October 02, 2008 October 09, 2008 October 23, 2008 November 27, 2008 November 20, 2008 December 04,

4 Course Outline Preliminary Notions Systems Life Cycle Processes Course Project Systems engineering: an interdisciplinary approach 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 Civil Mechanical Systems Electrical System: an assemblage or combination of elements comprising a whole with each element related to other elements Chemical Aeronautical Any element which has no relationship with any other element of the system, cannot be a part of that system 15 16

5 Components: operating parts of a system Attributes: properties of the components Relationships: links between components and attributes System State: current value of a system's components, attributes, and/or relationships Example: A food chain models the movement of energy in an ecosystem Components: The Sun, Plants, Herbivores, and Carnivores Attribute: units of energy Relationships: 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) Functional View Input Process Output Input: addition of material, energy, or information to a system Process: Altering material, energy, or information Output: movement of matter, energy, or information out of a system 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 system Subsystems: aircrafts, terminals, ground support equipments 19 20

6 Natural Systems vs. Design Systems Natural 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 Systems Physical systems: based only on matter and energy (e.g. manufacturing systems) Conceptual systems: based on symbolic components (e.g. plans and computer programs) Static Systems vs. Dynamic Systems Static 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 Systems Open 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) Course Outline Preliminary Notions Systems Life Cycle Processes Course Project In 1990 a professional society for systems engineering, the National Council on Systems (NCOSE), was founded by representatives from a number of US corporations and organizations INCOSE: International COSE 23 24

7 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 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 Reliability engineering: the discipline of reducing the frequency of breakdowns Maintainability engineering: the discipline of dealing with the frequency of breakdowns to prevent the occurrence of downtime Safety engineering: the discipline of minimizing the probability of critical failures and identifying safety hazards Systems engineering: a management technology that controls a total system life cycle process Systems management: the strategic level of systems engineering A system life cycle process involves the definition, development, and deployment of a new product or service 27 28

8 Systems Management (Strategic Level) Systems Processes (Conceptual Level ) Systems Methods and Tools (Development Level ) Systems engineers assist and support planning, decision making and resource allocation Quantitative and qualitative formulation, analysis and Interpretation of the impact of action alternatives Quality Control Simulation & Modeling Programming Languages Life Cycle Analysis Quality Assurance Configuration Control Methods and Tools for Systems Systems Processes Communication Theory Economic Analysis Requirements Systematic Measurements Cognitive Ergonomics Performance Control 31 32

9 Course Outline Acquisition Phase Utilization Phase Preliminary Notions Systems Conceptual and Preliminary Design Detail Design and Development Production and/or Construction Product Use, Phase-out, and Disposal Life Cycle Processes Course Project NEED Conceptual Design: Acquisition Phase Utilization Phase 1- Feasibility study: Needs analysis System operational requirements System maintenance concept 2- Specification Conceptual and Preliminary Design Detail Design and Development Production and/or Construction Product Use, Phase-out, and Disposal 3- Planning NEED 35 36

10 Preliminary Design Acquisition Phase Utilization Phase 1- Functional Analysis 2- Design Criteria 3- Optimization 4- Synthesis Functional requirements Operational functions Maintenance functions Identification of alternative functions Allocation of performance factors and design factors Allocation of system support requirements Evaluation of alternatives System and subsystems analysis Design performance, configuration (data, physical models, testing, etc. Detail specifications Conceptual and Preliminary Design NEED Detail Design and Development Production and/or Construction Product Use, Phase-out, and Disposal Detail Design Acquisition Phase Utilization Phase 1- System Design 2- Prototype Development 3- Test and Evaluation Design of functional system Design support functions Design data and documentation Design review Development of system prototype model Development of system logistic support requirements Test preparation Prototype system testing Test data, analysis, and evaluation Test reporting Test review Conceptual and Preliminary Design NEED Detail Design and Development Production and/or Construction Product Use, Phase-out, and Disposal 39 40

11 Production and/or Construction: 1- System assessment analysis and evaluation 2- Modification for Corrective action Proposed by A. T. Bahill and B. Gissing, 1998 Utilization and Support: 1- System assessment analysis and evaluation 2- Modification for Corrective action 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 requirements Integrate: designing interfaces and bringing system elements together so they work as a whole Launch the system: running the system and producing outputs Assess performance: using evaluation criteria to assess the system performance Re-evaluation: re-evaluating the solution in a continual and iterative manner with many parallel loops Waterfall Vee Spiral Others 43 44

12 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 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 Developed by Boem from 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 Computer-Aided Software (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 47 48

13 Course Outline Preliminary Notions Systems Life Cycle Processes Course Project Three choices Synthesis 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 Project proposal Deadline: October 02, 2008 Team members Topic and title Main reference Lecture 1: Chapters 1 and 2 of Systems and Analysis Lecture 2: Chapters 1 and 6 of Assurance Technologies, Principles and Practices 51 52