Engineering cycle.

Slides:



Advertisements
Similar presentations
Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries.
Advertisements

CONTROL SYSTEMS: WHAT THEY ARE
Project management Project manager must;
System Analysis (Part 1)
Unit 231 Software Engineering Introduction to SWE What is SDLC Phases of SDLC.
Fundamentals of Information Systems, Second Edition
1 Simulation Modeling and Analysis Verification and Validation.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
©Ian Sommerville 2000Software Engineering, 6/e, Chapter 91 Formal Specification l Techniques for the unambiguous specification of software.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
Problem Solving Methodology
The Software Development Life Cycle: An Overview
Commercial Database Applications Testing. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered.
By the end of this chapter, you should:  Understand the properties of an engineering requirement and know how to develop well-formed requirements that.
SOFTWARE TESTING STRATEGIES CIS518001VA : ADVANCED SOFTWARE ENGINEERING TERM PAPER.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
Six Steps of Problem Solving And Engineering Design Process SVES Colleges of Engineering UML – ATP Lecture 2.
Software Development Cycle What is Software? Instructions (computer programs) that when executed provide desired function and performance Data structures.
Jan. 29, 2002Grand Challenges in Simulation Issues in Enhancing Model Reuse C. Michael Overstreet Richard E. Nance Osman Balci.
Effective Communication for Colleges, 10 th ed., by Brantley & Miller, 2005© Chapter 11 Chapter 11 – Slide 1 Reports, Proposals, and Instructions for the.
Introduction to Software Development. Systems Life Cycle Analysis  Collect and examine data  Analyze current system and data flow Design  Plan your.
Prepare by : Ihab shahtout.  Overview  To give an overview of fixed priority schedule  Scheduling and Fixed Priority Scheduling.
1 15 quality goals for requirements  Justified  Correct  Complete  Consistent  Unambiguous  Feasible  Abstract  Traceable  Delimited  Interfaced.
TESTING LEVELS Unit Testing Integration Testing System Testing Acceptance Testing.
Chapter 10 Verification and Validation of Simulation Models
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Design Report – Fall Semester. Title Page List name of project and team number List date List team members, advisor, sponsor Team logos.
Smart Home Technologies
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M37 8/20/2001Slide 1 SMU CSE 8314 /
Unit F451 Computer Fundamentals Components of a Computer System Software Data: Its representation, structure and management in information.
 System Requirement Specification and System Planning.
CHAPTER 2. Designing, implementing, deploying and operating systems which include hardware, software and people.
Finite State Machines ENGR 110 #7 2016
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
Instrument Clusters Topics covered in this presentation:
The System Development Life Cycle
Principles of Programming & Software Engineering
Formal Specification.
Software Testing.
Planetary Lander PDR Team Name
Design and Documentation
Control System Instrumentation
Software Engineering Lecture 4 System Modeling The Analysis Stage.
Software Testing.
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
The Risk Assessment in the Food Industry
OVERVIEW Impact of Modelling and simulation in Mechatronics system
Chapter 8 – Software Testing
Life Cycle Models PPT By :Dr. R. Mall.
CHAPTER 2 Testing Throughout the Software Life Cycle
Software Requirements analysis & specifications
Dynamic Controllers for Wind Turbines
Chapter 10 Verification and Validation of Simulation Models
The System Development Life Cycle
The Design Process & Technical Drawings
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Control System Instrumentation
Use Cases CS/SWE 421 Introduction to Software Engineering Dan Fleck
Issues in Enhancing Model Reuse
Eastern Mediterranean University Department of Mechanical Engineering
CS310 Software Engineering Lecturer Dr.Doaa Sami
Members: Keshava Shiva Sanjeeve Kareena
Working Drawings Legal Documents that Provide All the Visual, Numerical and Textural Information Required to Manufacture a Component, Mechanism or Structure.
Engineering Quality Software
Chapter 5 Understanding Requirements.
Project Closure And Termination
Chapter 1. Introduction to Control System
Chapter 13 Building Systems.
What to look at in fire engineering analysis
Chapter 1: Creating a Program.
Presentation transcript:

Engineering cycle

Basic overview

Specification A set of criteria that must be met by the system – it is the driving force of a project Used to evaluate the end product – must be measurable quantity Created using the objective behind the project The output of this stage is a specification document containing the list of requirements of the project

Contents of a specification Dimensions of system components Concentrations Rates of reaction Margin of error – tolerance Conditions – temperature, chemical conditions, pH, biocompatibility etc List of all inputs and the desired outputs

Example Aim: portable device to detect concentration of a H2O2 in breath to warn user of an imminent asthma attack Specification: Size of device ~ 10 x 5 cm Must have sensor able to detect concentration of H2O2 The sensitivity of the sensor must be between 0.1μM – 10 μM Uncertainty in measurements < 0.05μM Results must be displayed within 1 minute of measurement Display a warning message if the concentration of H2O2 too high or in the breath Batteries must have a life of at least 3 days

Design How the specification might be met A detailed plan of each component within the system and how the outputs may be achieved from the inputs May be in the form of drawings or detailed description May go back and change the specification if any of the specification is not feasible or unachievable according to the resources

Design Abstraction is usually used to design a system in a top to bottom manner First a plan of the overall system may be designed At the second level of abstraction each of the individual sub-units of the system would be designed in detail The level of detail in the design document depends on the level of standardisation of parts and their characterisation.

H2O2 sensor Design: Level 1: Level 2: biosensor: standard Sensor for H2O2 detection Processor to process information An LCD to display the results battery slot Casing – strong for protection of components within Place to inhale into the device Power button Level 2: biosensor: standard Size Electrode Reactive coating Enzymes Level 2: processor: standard speed

Modelling Predict system behaviour Consists of computer simulations or mathematical relations based on the design of the system May also be a mock-device made with slightly different materials or dimensions, but same basic design A cost-effective way to verify the design of a system – cheaper and faster Helps evaluate system completeness as well as improve the understanding of the mechanisms of the processes involved Assumptions may be made while modelling a system, but these need to be reasonable – must be documented and justified May need to modify the system design if an error is identified in the system design from the model

Modelling

Example – aerodynamic modelling Cheaper to simulate air flow around a wing than to actually build the wing and test it Numerical simulation of the flow around aerofoils performing arbitrary rigid body motions

Implementation The realisation of the system that has been designed and modelled The actual end product is constructed by the end of this stage

Testing/validation Verify whether the constructed system fulfils the requirements set by the specification Validation – the successful completion of testing The inputs, outputs and functions of each of the components, as well as the whole system, are compared with the specification values Test the system under the conditions it might be used in

Testing/validation Testing methods should be designed such that they can actually validate or invalidate the implementation Should have a testing protocol - formal documents that typically outline requirements, activities, resources, documentation and schedules to be completed 

Glossary Tolerance: the allowed variation in a physical dimension of the system or a value measured by the system Transfer function: a mathematical equation representing the relation between the input and output of a system