Institut für Technische Informatik Fakultät für Informatik Universität der Bundeswehr München ITIS e.V. Institut für Technik Intelligenter Systeme an der.

Slides:



Advertisements
Similar presentations
Applying the Human Views for MODAF to the conception of energy-saving work solutions Dr Anne Bruseberg Systems Engineering & Assessment Ltd, UK on behalf.
Advertisements

Lecture # 2 : Process Models
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
Software Process Models
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
e-Framework Components and Responsibilities.
Asa MacWilliams Lehrstuhl für Angewandte Softwaretechnik Institut für Informatik Technische Universität München Dec Software.
Design Creative Process of transferring the problem into a solution
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Lecture 13 Revision IMS Systems Analysis and Design.
1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.
- 1 - Component Based Development R&D SDM Theo Schouten.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Jump to first page 30/06/ Chapter 1 System Development Environment.
Introduction to Software Testing
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems.
What is Business Analysis Planning & Monitoring?
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 2- Software Process Models and Project.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
1 Validation & Verification Chapter VALIDATION & VERIFICATION Very Difficult Very Important Conceptually distinct, but performed simultaneously.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 2 (Chapter 2) Information System Building Blocks.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Asa MacWilliams Lehrstuhl für Angewandte Softwaretechnik Institut für Informatik Technische Universität München June 27, 2005 A Decentralized.
OBJECT ORIENTED SYSTEM ANALYSIS AND DESIGN. COURSE OUTLINE The world of the Information Systems Analyst Approaches to System Development The Analyst as.
IT Requirements Management Balancing Needs and Expectations.
Copyright 2002 Prentice-Hall, Inc. 1.1 Modern Systems Analysis and Design Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 1 The Systems Development.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
1 Introduction to Software Engineering Lecture 1.
P1516.4: VV&A Overlay to the FEDEP 20 September 2007 Briefing for the VV&A Summit Simone Youngblood Simone Youngblood M&S CO VV&A Proponency Leader
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
IT Directors Group 13 & 14 October 2008 Item of the Agenda Seasonal Adjustment software Cristina Calizzani - Unit B5.
1 Advanced Collaborative Environments Kris Brown Carmel Conaty Johnny Medina.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
SOFTWARE ENGINEERING. Objectives Have a basic understanding of the origins of Software development, in particular the problems faced in the Software Crisis.
Smart Home Technologies
© Fraunhofer IESE Fraunhofer IESE Multi-Language Development of Embedded Systems Dr. Thomas Kuhn Tel.:
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
ISWG / SIF / GEOSS OOSSIW - November, 2008 GEOSS “Interoperability” Steven F. Browdy (ISWG, SIF, SCC)
Accreditation of study programs at the Faculty of information technologies Tempus SMGR BE ESABIH EU standards for accreditation of study.
Final Review Systems Analysis and Design in a Changing World, 4th Edition 1 Final Review u Chapters 1-6, 8-10, 13, 14, 15 u Multiple choice, short answer,
Decisive Themes, July, JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011.
Moon Fleet Management Six Sigma Supervisor: Nguyễn Trường Long Members: - Lê Hoàng - Nguyễn Đăng Phượng - Nguyễn Thanh Tùng - Phạm Phương Duy - Vũ Quang.
Faculty Economics & Business EBS 2033 Systems Development Lecture 1 The Systems Development Environment Lecturer: Puan Asleena Helmi.
Chapter 1 The Systems Development Environment
Review of last class Software Engineering Modeling Problem Solving
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
IEEE Std 1074: Standard for Software Lifecycle
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
Overview of System Engineering
MBI 630: Systems Analysis and Design
Introduction to Software Testing
CS 8532: Advanced Software Engineering
.NET vs. J2EE Architecture
Dept. of Computation, UMIST
Chapter 1 The Systems Development Environment
Presentation transcript:

Institut für Technische Informatik Fakultät für Informatik Universität der Bundeswehr München ITIS e.V. Institut für Technik Intelligenter Systeme an der Universität der Bundeswehr München NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, Verification, Validation and Accreditation of Simulation Models and Applications Axel Lehmann

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Technology Trends  Rapid technological innovations  information and communication technologies  computer-assisted tools, e.g. for  Design & analysis support  Planing & decision support  Education & training  Increasing systems complexity & lifetime  embedded systems  networked components / systems  distributed systems  Increasing productivity & cost-benefit relations  Decreasing cycle times for system’s innovations

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Major Challenges  “Mastering” of system(s) complexity over lifetime w.r.t. multiple aspects/ goals? (safety, reliability, performance,…)  Approach: Goal-oriented, efficient, effective and dependable models!  “Mastering” of model(s) complexity !?  STRATEGIC approach: “Devide and Conquer”!  MODEL-ENGINEERING approach!!

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 M&S-Approach: “Divide and Conquer” improving EFFICENCY increasing CREDIBILITY Multi-Phase M&S process(es) (intermediate products) verification and validation correctness; suitability reusability; distributed execution M&S „components“

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Outline 1.M&S: A Multiple-Phase Development & Application 2.Improving M&S-Efficiency by Component-Based M&S 3.Increasing Credibility through M&S-Verification & Validation 4.Conclusion

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, M&S – A Multiple-Phase Development and Application Process  Analyses goals e.g.:  processing time per transaction  client/server utilization  queueing  How to approach this (complex) problem?  “Divide and Conquer”:  A Multiple-Phase M&S Process  Example:Effectivness and efficiency of a „Booking System“ (e.g. client-server architecture)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 M&S – Development Team (Skills) Modeling Expertise Experimental Design and Analysis Domain Knowledge (HW-)SW- Expertise User Knowledge Problem Definition System Analysis Model Formalization Implementation Experimentation Programmer Modeller Domain Expert User Customer Project Manager (Contractor)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Phases & Products in the M&S- Development Process Model Input Data Solution Techniques Modeling Method System Observations Experimental req.&constr. Technical req.&constr. Formal req.&constr. Conceptual req.&constr. Examination Aim Input: Problem Definition System Analysis Model Formalization Implementation Experimentation Phase: Model Documen- tation Objekt I n t e r a k t i o n Systemgrenze “Umwelt- objekt“ “Hauptobjekt” mit Modellattributen Communicative Conceptual Model, Project Objectives Structured Problem Description Formal Model Executable Model Results Intermediate Products:

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Example: „Booking System“ I/O device 1 CPU T 1 T n I/O device n Server Clients  Conceptual Model:

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Example: „Booking System“  Formal Model: peripheral devices

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Example: „Booking System“  Executable model: Performance measures  Little´s law: k = + t ; with: response time t, queueing time w, service rate µ t = w + ; µ 1 1      m service rate arrival rate  State probability p(k): k =  k p (k)  Utilization  ( m service stations):

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, Model “Component”-Based Approach:  Executable Model(s): e.g.  analytic solution  simulation reusable SW- “components“ (e.g. regarding the example „Booking System“)  Problem Description:  pragmatism/ goal specification  Conceptual Model:  structural & functional description of “components”  different levels of abstraction  Formal Model:  formal specification of “components” (  selected modeling paradigm(s))  hierarchical modeling approach (  decomposition into submodels/ “components”)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Phases & Products in the M&S- Development Process t M&S- „components“: X X XX X Model Input Data Solution Techniques Modeling Method System Observations Experimental req.&constr. Technical req.&constr. Formal req.&constr. Conceptual req.&constr. Examination Aim Input: Model Documen- tation Objekt I n t e r a k i o n Systemgrenze “Umwelt- objekt“ “Hauptobjekt” mit Modellattributen Communicative Conceptual Model, Project Objectives Structured Problem Description Formal Model Executable Model Results Intermediate Products: Problem Definition System Analysis Model Formalization Implementation Experimentation Phase:

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Model („Component“) Specification Levels Model repository  Model Federation Level: „Black Boxes“ Library of submodels & communication infrastructure  Model Level: Autonomous, interoperable models Library of objects/methods (for interaction)  Submodel/ Object Level: Submodels/ Object structures  60und0mit :0 0)(wenn:),()()(         sni sonst tlttzttrftl tls isiisiissiis is Program Library  Function Level: Coded basic functions/ algorithms

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, Increasing M&S-Credibility M&S- Credibility Perceived suitability Perceived correctness Correctness (specification  Implementation) ConsistencyCompleteness Verification (  Formalisms, specifications, transformation rules) Suitability (requirements, constraints) CapabilityFidelityAccuracy Validation

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Influences:V&V Framework Model knowledge Risk System knowledge V&V Credibility indicators Results:

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Multi-phase M&S-process  intermediate products, Structured problem description Model Documen- tation Objekt I n t e r a k t i o n Systemgrenze “Umwelt- objekt“ “Hauptobjekt” mit Modellattributen Conceptual model Formal model Executable model Simulation results Project Objectives Problem definition System analysis Formalization Implementation Experimentation Interpretation Internal consistency & completeness Consistency of transformation (pairwise comparison)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Our Approach: „The V&V Triangle“ V&V Phase Intermediate Results

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Model Development & V&V I t

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 V&V - Process „Tailoring“ I t

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Our Contribution to International Efforts on V&V:  ITOP:International Test Operations Procedure (Working Group of Experts WGE 7.2: V&V)  NMSG:Nato Modeling and Simulation Group (019 Task Group 016: “V&V of Federations”)  SISO PDG:SISO Product Development Group: (V&V of Federations)  V&V – CONVENTION (October 20-24, 2004, Munich-Germany) EU-COST 285 – Action „..M&S in innovative telecommunications...“ ( 2003 – 2007)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, Conclusions  Strategic approach: „Divide and Conquer“ !   M&S as a Multi-Phase Engineering Process:  Efficient M&S-design by component-based modeling  Credibility assurance by risk-based V&V  Summary:  How to improve M&S-credibility and efficiency for increasingly complex simulation applications?

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Focus of our research efforts  Model engineering process:  Re-useability of model components  Tailored model documentation  (Risk analysis)  tailored V&V (&A)  M&S performance & reliability:  Parallel and distributed M&S  (Collaborative modeling)

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 I t Thank you very much for your interest and attention!

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 M&S – Source of Knowledge and Expertise Modeling Expertise (HW-)SW- Expertise Experimental Design and Analysis Domain Knowledge User- Knowledge System Analysis Model Formalization Implementation Experimentation Problem Definition

Axel Lehmann NATO Advanced Research Workshop Velingrad, Bulgaria, Oct. 24, 2006 Example: „Booking System“ Formal Model (Version 1): queuing net