The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI,

Slides:



Advertisements
Similar presentations
Use cases Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself A set.
Advertisements

ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Information System Engineering
BUSINESS MODELING BY UML PROFILE VISA ISSUING SYSTEM Dražen Brđanin, Slavko Marić Faculty of Electrical Engineering Banja.
Use-case Modeling.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing systems process: Use Case Diagram.
Use Case Systems Analysis & DesignUse Case1 Use case refers to A system’s behavior (functionality) A set of activities that produce some output.
Lecturer: Dr. AJ Bieszczad Chapter 66-1 Object-Oriented analysis and design Special nature of OO development Use cases Design with UML OO system design.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Sharif University of Technology Session # 7.  Contents  Systems Analysis and Design  Planning the approach  Asking questions and collecting data 
Use Case Diagram.
Use Case Modeling. Use case diagram For each use case we develop  Object class diagram (with attributes only)  System sequence diagram (analysis) 
Unified Modeling Language
UML Sequence Diagrams Michael L. Collard, Ph.D. Department of Computer Science Kent State University.
Page 1 What is the UML? UML stands for Unified Modeling Language The UML combines the best of the best from – Data Modeling concepts (Entity Relationship.
Chapter 6 A Use-Case-Driven Process. 2 Definitions The choice of models and the choice of techniques used to express them have a significant impact on.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
UML Diagrams: Sequence Diagrams The Requirements Model, and The Dynamic Analysis Model Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
1 Interaction diagrams and activity diagrams Speaker: 陳 奕 全 Real-time and Embedded System Lab 15 August 2002.
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Engineering Lab Use Cases Faculty of Information system Technology.
The Unified Modeling Language Part II Omar Meqdadi SE 2730 Lecture 9 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU.
Interaction Diagram Notation
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
Concern Architecture View and Aspect-Oriented Design Mika Katara and Shmuel Katz Tampere U. T. Technion, Haifa.
OOP Review CS 124.
22 August, 2007Information System Design IT60105, Autumn 2007 Information System Design IT60105 Lecture 8 Use Case Diagrams.
Winter 2007SEG2101 Chapter 31 Chapter 3 Requirements Specifications.
Essentials of Modeling with IBM Rational Software Architect V7.5
Chapter 3: Introducing the UML
Spring 2007 Week 10: Object Modeling (1)Use Case Model IFS410: Advanced Analysis and Design.
UML - Development Process 1 Software Development Process Using UML.
 What to do if you want to build a new house? › Buy a bunch of wood and nails and start immediately. › Or, put some blueprints to follow, and plan of.
Refining the Use Cases 1. How Use Cases Evolve  Early efforts typically define most of the major use cases.  The refining stages complete the process.
Session 5 Object Model Development. OOAD with UML / Session 5 / 2 of 19 Review A class icon is a rectangle with three sections within it An object is.
Objective: Learn to describe the relationships and extend the terms in arithmetic sequence.
Synthesis Synchronous Sequential Circuits synthesis procedure –Word description of problem /hardest; art, not science/ –Derive state diagram & state table.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
Communication Diagrams Lecture 8. Introduction  Interaction Diagrams are used to model system dynamics  How do objects change state?  How do objects.
1 BTS330 Visual Modeling. What is Visual Modeling? 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship.
Business Models and Information Flow 10 th Meeting Course Name: Business Intelligence Year: 2009.
Diagrams. Typically, we view the static parts of a system using one of the four following diagrams. 1. Class diagram 2. Object diagram 3. Component diagram.
UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Page 1  Copyright © 1997 by Rational Software Corporation Putting the UML to Work The ESU University wants to computerize their registration system –
1 IS 0020 Program Design and Software Tools Unified Modeling Language Lecture 13 April 13, 2005.
1 IS 0020 Program Design and Software Tools Unified Modeling Language Lecture 13 November 30, 2004.
Chapter 1: Introduction to Systems Analysis and Design
UNIT 1.
Object-Oriented Analysis (OOA)
Object-Oriented Systems Analysis and Design Using UML
SNSCT_CSE_PROGRAMMING PARADIGM_CS206
Unified Modeling Language
Interaction diagrams.
Object Oriented Analysis and Design
COP 4331 Recitation #1 University of Central Florida
COP 4331 Recitation #1 University of Central Florida
Object oriented analysis and design
Software Design Lecture : 15.
Arithmetic Sequence Objective:
Chapter 1: Introduction to Systems Analysis and Design
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Sample Test Questions Please identify the use cases of the system that cover all the behaviors described in the system specification. Please identify.
Chapter 1: Introduction to Systems Analysis and Design
General Workflow of Use-Case Driven Development
Presentation transcript:

The Transition from Business Modeling to Requirements Specification Svatopluk Štolfa Tuesday, August 18, 2015 VŠB - Technical University of Ostrava FEEI, Dept. of Computer Science

Business Process and Use Case Model BP is a set of one or more linked procedures or activities which collectively realize a business objective or policy goal BP is a set of one or more linked procedures or activities which collectively realize a business objective or policy goal UC model - examines the system functionality from the perspective of actors and use cases UC model - examines the system functionality from the perspective of actors and use cases – Actor: – Actor: someone (user) or something (other system) that must interact with the system being developed – Use case: – Use case: a pattern of behavior the system exhibits. Each use case is a sequence of related transactions performed by an actor and the system in a dialog

Activity and Use Case Diagram Notation

Business Process Definition Define business process Define business process – Example: Returning process Returning process Lending Process Lending Process Modify BP Modify BP – Exclude activities that will not be provided by system

Business Process Definition - example

Mapping several activities to one use case

Mapping one atomic activity to one use case

Sequential Pattern Organize use cases derived from sequential activities by “include” relationships.

Optional Pattern Organize use cases derived from optional activities by “extends” relationships.

Applying Patterns to Example

Conclusions Analysts may use this method for support their intuition Analysts may use this method for support their intuition Future research is focused on improvement, extension and formalization of this method Future research is focused on improvement, extension and formalization of this method Method for semi-automatized use case creation Method for semi-automatized use case creation