SYSE 802 John D. McGregor Module 4 Session 0 Where are we?

Slides:



Advertisements
Similar presentations
Transportation Waste Definition: the unnecessary act of taking or carrying someone or something from one place to another Office example: Movement of paperwork;
Advertisements

COM606 Software Systems Engineering and on the Portal Introduction.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
EYYUP ORAK Material requirements planning (MRP) is a computer-based inventory management system designed to assist production managers in.
SYSE 802 John D. McGregor Module 2 Session 2 Method Tailoring.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
IBM Engineering & Technology Services © 2002 IBM Corporation Page 1 IBM Engineering & Technology Services BlueGene/L Production: From Prototype to Customer.
Multiple V-model. Introduction In embedded systems, the test object is not just executable code. First a model of the system is built on a PC, which simulates.
Practical Approach to Teaching Software Testing Sashko Ristov 11th Workshop on “Software Engineering Education and Reverse Engineering” – August 22-27,
® IBM Software Group © 2007 IBM Corporation Achieving Harmony IBM's Platform and Methodology for Systems Engineering and Embedded Software Development.
Software Testing Name: Madam Currie Course: Swen5431 Semester: Summer 2K.
CSE Senior Design II Test Planning Mike O’Dell Based on an earlier presentation by Mike O’Dell, UTA.
Improving Productivity on an SEI Level IV Project presented by Kelly Ohlhausen.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 22Slide 1 Verification and Validation u Assuring that a software system meets a user's.
CPSC 871 John D. McGregor Processes – a first iteration Module 1 Session 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
ISO Layer Model Lecture 9 October 16, The Need for Protocols Multiple hardware platforms need to have the ability to communicate. Writing communications.
Software Engineering 2003 Jyrki Nummenmaa 1 REQUIREMENT SPECIFICATION Today: Requirements Specification Requirements tell us what the system should.
SYSE 802 John D. McGregor Module 0 Session 1 Course Introduction.
SE-02 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it. Requirements.
John D. McGregor Module 6 Session 2 Tailoring Processes
SYSE 802 John D. McGregor Module 6 Session 1 Systems Engineering Analyses II.
S Q A.
SYSE 802 John D. McGregor Module 3, Session 3 Assignment.
Application Health Reporting Overview. Application Performance Occam’s approach has always been; first understand “what it is the client would like to.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix B Rapid Application.
SEI CMM Robert Johnson Bobby Kolski Rafi Seddiqi Kumeel Alsmail.
CPSC 871 John D. McGregor Module 2 Session 4 CMMI & assignment.
COM606 Software Process Engineering and on the Portal Introduction.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Capability Maturity Model by Hardeep Atwal (hsa06u)
1 Introduction to Software Testing. Reading Assignment P. Ammann and J. Offutt “Introduction to Software Testing” ◦ Chapter 1 2.
Examination of the Interplay of Reliability and Security using System Modeling Language (SysML). By Venkateswara Reddy Tallapu.
OHTO -01 SOFTWARE ENGINEERING LECTURE 3 Today: Requirements Analysis Requirements tell us what the system should do - not how it should do it.
CPSC 873 John D. McGregor Session 9 Testing Vocabulary.
SYSE 802 John D. McGregor Module 1 Session 2 Requirements Modeling in SysML.
Author Software Engineering Institute
Software Testing 1Software testing. V model Software testing2.
SYSE 802 John D. McGregor Module 2 Session 3 Assignment.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Assoc. Prof. Dr. Ahmet Turan ÖZCERİT.  System and Software  System Engineering  Software Engineering  Software Engineering Standards  Software Development.
CPSC 871 John D. McGregor Module 8 Session 1 Testing.
CPSC 871 John D. McGregor Process – an introduction Module 0 Session 3.
CPSC 871 John D. McGregor Module 6 Session 2 Validation and Verification.
How to develop E/E/PESs to IEC 61508?
CPSC 372 John D. McGregor More EPF Module 2 Session 4.
Chapter 1 Software Engineering Principles. Problem analysis Requirements elicitation Software specification High- and low-level design Implementation.
CPSC 372 John D. McGregor Module 1 Session 2 Process Measurement.
CPSC 873 John D. McGregor Session 3 Requirements V & V.
Systems Development Life Cycle
SYSE 802 John D. McGregor Module 0 Session 3 Systems Engineering QuickView.
CPSC 372 John D. McGregor Module 8 Session 1 Testing.
SYSE 802 John D. McGregor Module 0 Session 2 Model-based methods.
Transportation Waste Definition: the unnecessary act of taking or carrying someone or something from one place to another Office example: Movement of paperwork;
School of Business Administration
Modern Systems Analysis and Design Third Edition
John D. McGregor Eclipse Process Framework Module 2 Session 4
DT249/4 Information Systems Engineering Lecture 0
John D. McGregor Session 3 Requirements V & V
Manfred Huber Based on an earlier presentation by Mike O’Dell, UTA
Software engineering – 1
Software Design Methodology
Andy Nolan1, Silvia Abrahão2 Paul Clements3,
Test Planning Mike O’Dell (some edits by Vassilis Athitsos)
Modern Systems Analysis and Design Third Edition
Systems Engineering Concept Model (SECM) Status Update
Modern Systems Analysis and Design Third Edition
Learning Intention I will learn about the iterative software development process with a focus on the Analysis stage.
Juha-Pekka Tolvanen MetaCase
Presentation transcript:

SYSE 802 John D. McGregor Module 4 Session 0 Where are we?

V model I was asked about how what we are doing compares to the traditional V Model process of systems engineering. I was confused since we are explicitly following that model til I followed the reference I was given to page 10 of the Buede book. That V model is only the design and integration portions of the full V model shown on page 6.

V Model - 2 Two responses: – Waiting until the upward bound leg of the V model to do verification and validation is too late. You have already wasted work on incorrect requirements. Taking the model-driven approach that we are is much more likely to find defects earlier but does not negate the overall V. – Second response, we are following a V-Model. The standard given in ISO is shown first…

V Model from ISO – Systems Engineering Module 0 Module 1,2 Module 3,4 Module 5

V model -3 This picture is the high level V Model used by the US Dept of Transportation Module 0 Module 1,2 Module 3,4 Module 5

MIT’s V Model for Systems Engineering Module 0 Module 1,2 Module 3,4 Module 5

Tools The EPF tool is equivalent to IBM’s Composer tool. A large number of companies, in order to meet multiple demands, blend ISO 9000, CMMI, and a variety of other criteria. They build a unique method for each project to include tools, techniques, and processes. EPF, Composer, and other similar tools give the ability to take the V model and develop explicit process definitions for each project.

Tools - 2 Topcased including SysML and AADL support a model-driven approach to systems engineering. After a very large (billions of dollars) mistake Airbus vowed not to make that mistake again and began development of an environment for end-to-end systems engineering including hardware and software. They have selected specific standards such as SysML and AADL to build dependable systems.

More questions? Keep the questions coming