Www.wileyeurope.com/college/van lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons 1 Part 2: Building System Models for RE Introduction.

Slides:



Advertisements
Similar presentations
Documenting Software Architectures
Advertisements

Chapter 7 Goal Orientation in RE
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 1: Introduction.
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 12, 2001 Capturing.
Lecture # 2 : Process Models
Object-Oriented Software Development CS 3331 Fall 2009.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
lamsweerde Part 1: Introduction © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models to.
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
Introduction to Software Engineering Dr. Basem Alkazemi
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Software Testing and Quality Assurance
Software Testing and Quality Assurance
Amirkabir University of Technology, Computer Engineering Faculty, Intelligent Systems Laboratory,Requirements Engineering Course, Dr. Abdollahzadeh 1 Requirements.
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
IMS1805 Systems Analysis Topic 3: Doing Analysis (continued from previous weeks)
System behaviors: state machine diagrams
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Requirement Engineering – A Roadmap
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
1 درس مهندسي نيازمندي استاد دكتر عبداله زاده دانشجو خيرالنسا مرچانت RE in The Year 00: A Research Perspective.
Feb. 27, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #13 Tuesday, Feb. 27, 2001.
© Copyright 2011 John Wiley & Sons, Inc.
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
1 SWE Introduction to Software Engineering Lecture 11 - Requirements Engineering Processes.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Software Engineering CS B Prof. George Heineman.
Requirements Analysis
Karolina Muszyńska. Reverse engineering - looking at the solution to figure out how it works Reverse engineering - breaking something down in order to.
lamsweerde Requirements Engineering © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
lamsweerde Requirements Engineering © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models.
Object-Oriented Analysis and Design Lecture 1 Instructor: John Cole 1Object-Oriented Analysis and Design - Intro.
Chapter 13 Architectural Design
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
ARCH-2: UML From Design to Implementation using UML Frank Beusenberg Senior Technical Consultant.
♦ Use Case Model  Detailled use case - Important  Use case diagram- Refactoring Use case diagram  > 1 Last Lectures.
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Deriving Operational Software Specification from System Goals Xin Bai EEL 5881 Course Fall, 2003.
Slide 1 Systems Analysis and Design with UML Version 2.0, Second Edition Alan Dennis, Barbara Wixom, and David Tegarden Chapter 6: Functional Modeling.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Requirements Validation
Ch- 8. Class Diagrams Class diagrams are the most common diagram found in modeling object- oriented systems. Class diagrams are important not only for.
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
lamsweerde Chap.4: Formal Requirements Specification © 2009 John Wiley and Sons Fundamentals of RE Chapter 4 Requirements.
MNP1163/MANP1163 (Software Construction).  Minimizing complexity  Anticipating change  Constructing for verification  Reuse  Standards in software.
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
1 Requirements Engineering From System Goals to UML Models to Software Specifications Axel Van Lamsweerde.
® IBM Software Group © 2009 IBM Corporation Essentials of Modeling with the IBM Rational Software Architect, V7.5 Module 15: Traceability and Static Analysis.
Prof. Hany H. Ammar, CSEE, WVU, and
Inferring Declarative Requirements Specification from Operational Scenarios IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 24, NO. 12, DECEMBER, 1998.
Requirements Analysis
Chapter 13 설계 개념 Architectural Design 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book “Software Engineering: A Practitioner’s.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Requirement Elicitation Review – Class 8 Functional Requirements Nonfunctional Requirements Software Requirements document Requirements Validation and.
Object Oriented Analysis & Design By Rashid Mahmood.
WELCOME TO OUR PRESENTATION UNIFIED MODELING LANGUAGE (UML)
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Chapter 2 Object-Oriented Paradigm Overview
UML Diagrams By Daniel Damaris Novarianto S..
UML Diagrams Jung Woo.
Software Engineering Lecture #11.
Presentation transcript:

lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons 1 Part 2: Building System Models for RE Introduction

2 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons RE activities require focus and structure A recurrent problem... –focusing, structuring elicitation sessions & artefacts (Chap.2) –identifying items at common level of granularity for comparison, evaluation (Chap.3) –structuring large, complex specifications (Chap.4) –focusing inspection, validation, verification on structured specs (Chap.5) –identifying change units, granularities of traceable items, derivation links for reqs evolution (Chap.6)  Model-driven  Model-driven approach to RE

3 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons Model-Driven RE  Model: –abstract representation of system (as-is or to-be) –highlights, specifies, inter-relates key system features  Multi-view  Multi-view model: –different system facets for requirements completeness

4 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons Why models for RE ? key aspects  Focus on key aspects (abstraction from multiple details) structure  Provides structure for RE activities –target for what must be elicited, evaluated, specified, consolidated, modified –interface among RE activities: produce/consume model items analysis  Facilitates analysis –support for early detection and fix of errors  Support for understanding, explanation to stakeholders  Basis for making decisions –multiple options made explicit  Basis for generating the requirements document (with tool)

5 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons A goal-oriented approach to model-driven RE modeling generation of RE deliverables interviewsdocuments.html.rtf.pdf.mif existing systems analysis

6 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons techniques  Concentrates on solid, replicable RE techniques construction,  Emphasizes model construction, beyond mere use of diagrammatic notations –heuristic rules, tactics, modeling patterns, bad smells –UML compliance wherever possible UMLUnified Modeling Language, de facto standards Specific diagrams when not supported by UML ( e.g. goals)  Based on case studies in a variety of domains The lectures will summarize book chapters, see details there !

7 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? why ? Goals Goals (Chap. 7, 8)

8 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? Risks Risks (Chap.9) why ? 8 Goals (Chap. 7, 8)

9 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? Conceptual objects Conceptual objects (Chap.10) on what? why ? Risks (Chap.9) Goals (Chap. 7, 8)

10 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? Agents Agents (Chap.11) on what? why ? who ? Goals (Chap. 7, 8) Risks (Chap.9) Conceptual objects (Chap.10)

11 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? Operations Operations (Chap.12) what ?

12 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? what ? Behaviors - Scenarios Scenarios (Chap.13) Behaviors - State machines State machines (Chap.13) Operations (Chap.12)

13 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons What models for RE ? what ? I    Threats Threats (Chap. 16) Operations (Chap.12) Behaviors - Scenarios (Chap.13) Behaviors - State machines (Chap.13)

14 lamsweerde Part 2: Building System Models for RE © 2009 John Wiley and Sons Building system models for RE : more detailed outline Chap.8: Modeling system objectives with goal diagrams Chap.9: Risk analysis on goal models Chap.10: Modeling conceptual objects with class diagrams Chap.11: Modeling system agents and responsibilities Chap.12: Modeling system operations Chap.13: Modeling system behaviors: scenarios and state machines Integrating multiple system views Chap.14: Integrating multiple system views A Goal-oriented model building method in action Chap.15: A Goal-oriented model building method in action