Chapter 5 Process Modeling By Muna Shabaneh. What is a Model? What is a process? What is a Process modeling? What are the Perspectives in process representation.

Slides:



Advertisements
Similar presentations
2 Introduction A central issue in supporting interoperability is achieving type compatibility. Type compatibility allows (a) entities developed by various.
Advertisements

Chapter 2: Software Process
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
25 February 2009Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department.
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor Formal Methods in Software Engineering1.
OASIS Reference Model for Service Oriented Architecture 1.0
Software Testing and Quality Assurance
Architecture is More Than Just Meeting Requirements Ron Olaski SE510 Fall 2003.
Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.
Web Ontology Language for Service (OWL-S). Introduction OWL-S –OWL-based Web service ontology –a core set of markup language constructs for describing.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
© Copyright Eliyahu Brutman Programming Techniques Course.
Describing Syntax and Semantics
Dr. Kalpakis CMSC 461, Database Management Systems Introduction.
Chapter 1 The Systems Development Environment
Software Architecture premaster course 1.  Israa Mosatafa Islam  Neveen Adel Mohamed  Omnia Ibrahim Ahmed  Dr Hany Ammar 2.
Chapter 1 The Systems Development Environment
The chapter will address the following questions:
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
On Roles of Models in Information Systems (Arne Sølvberg) Gustavo Carvalho 26 de Agosto de 2010.
Enabling Organization-Decision Making
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Chapter 1 The Systems Development Environment
Chapter 7 Structuring System Process Requirements
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Lecture 9: Chapter 9 Architectural Design
Software Design Deriving a solution which satisfies software requirements.
CHAPTER 6 - MODELING ANH AU. BACKGROUND Architectural model – an artifact that captures some or all of the design decisions that comprise a system’s architecture.
1 Introduction to Software Engineering Lecture 1.
Illustrations and Answers for TDT4252 exam, June
Chapter 5 Models and UML Notation for The Object-Oriented Approach.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Design Concepts By Deepika Chaudhary.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
McGraw-Hill/Irwin ©2008 The McGraw-Hill Companies, All Rights Reserved CHAPTER 9 DECISION MAKING.
Modeling as a Design Technique Chapter 2 Part 1: Modeling Concepts Object-Oriented Modeling and Design Byung-Hyun Ha
What is Object-Oriented?  Organization of software as a collection of discreet objects that incorporate both data structure and behavior.
L To identify the services that the customer requires from a system and the constraints under which it operates and is developed.
© 2005 Prentice Hall1-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Human Computer Interaction
Chapter 2 Object-Oriented Paradigm Overview. Getting Acquainted with the Class Project Read the requirements specification carefully Make note of any.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
RULES Patty Nordstrom Hien Nguyen. "Cognitive Skills are Realized by Production Rules"
McGraw-Hill/Irwin © The McGraw-Hill Companies, All Rights Reserved CHAPTER 9 Enabling the Organization—Decision Making.
Introduction to Modeling Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh.
CSCI 383 Object-Oriented Programming & Design Lecture 7 Martin van Bommel.
ACCOUNTING THEORY AND STANDARDS
1 Software Requirements Descriptions and specifications of a system.
CS 389 – Software Engineering
Unified Modeling Language
SYSTEM ANALYSIS AND DESIGN
By Dr. Abdulrahman H. Altalhi
Chapter 2 – Software Processes
Chapter 2 Database Environment Pearson Education © 2009.
MANAGING KNOWLEDGE FOR THE DIGITAL FIRM
Lecture Software Process Definition and Management Chapter 3: Descriptive Process Models Dr. Jürgen Münch Fall
Authors: Barry Smyth, Mark T. Keane, Padraig Cunningham
Features of a Good Research Study
Enabling the Organization – Decision Making
Chapter 2 Database Environment Pearson Education © 2009.
Chapter 2 Database Environment Pearson Education © 2009.
Presentation transcript:

chapter 5 Process Modeling By Muna Shabaneh

What is a Model? What is a process? What is a Process modeling? What are the Perspectives in process representation ? Issues in process modeling. Objectives

What is a model? It is a simplification of reality It is an abstract representation of reality that excludes much of the world’s infinite detail. [1] Why it is important to create a model? To reduce complexity It is a way to understand or predict What is a process? Humphery and Feiler [1] A process “ a set of partially ordered steps intended to reach a goal”

Process modeling “It is an abstract description of an actual or proposed process that represents selected process elements that are considered important to the purpose of the model and can be enacted by a human or a machine.” [1] Process script Process program

Process modeling Modeling of Information systems: Traditionally: analyzing data flows and transformations Recently: It extended to coordination and communication. So we needed process modeling to integrate these systems together

Applications on process modeling Business process reengineering the redesign of a business Coordination technology managing dependencies among the agents Process-driven software development creating automated system for integrating all of the SW-related management and staff

Software life cycle descriptions are they a useful model ?????? NO, since they don’t correspond to the actual processes performed during SW development. They are “DREAMS” !!! They represent high level plans without stating HOW-TO reach there. The reasons behind this problem are: 1)High-level perspective processes 2)Imprecise, ambiguous, incomprehensible, or unusable descriptions of process to be performed. 3)Failure to update the documentation.

Perspectives in process representation People want to extract from a process model some answers for: What is going to be done, who is going to do it, when and where it will be done, how and why will it be done. Process modeling represents different perspectives related to the previous questions the most common ones:

Functional: What (process elements, data flows) Behavioral: When (process elements) How (process elements) Organizational: Where and By Whom (process elements) Informational: (informational entities) Its structure and the relationships among them

Although the different perspective processes are separated the interrelated among them is essential for analyzing and presenting process information. Hypothesize that when combined they will produce an integrated, consistent, and complete model of the process analyzed.

Process Modeling Paradigms Process-modeling languages can be evaluated by their ability to provide a model that represents and possible to reason about for various aspects of a process. The source for modeling languages is programming languages.

Osterweil pointed out chicken-and-egg problem: “ In order to find out what languages features we need, we need to write process programs; in order to write process programs, we need the appropriate language features”

The breadth of process modeling Programming models-process programming Functional models-HFSP Plan-based models-GRAPPLE Petri-net models-role interaction nets Quantitative models-system dynamics.

Programming models: - Osterweil “software processes are software, too” - process descriptions can be modeled as algorithms and can be analyzed accordingly. - Examples: APPL/A, Aspen - APPL/A provides both procedural and declarative capabilities so it is also supports multiple representational paradigms.

Functional models: - The Hierarchical and Functional Software Process (HFSP) description and enact ion language was developed by Katayama and his colleagues. Its goals are: 1. aid process understanding 2. support hierarchical process decomposition 3. describe concurrent processes and backtracking 4.provide a flexible and dynamic execution mechanism

Plan based models: - Huff and Lesser argue that modeling process execution in the real world is difficult because of all the contingencies that must be considered (Do you agree) - Example: GRAPPLE which has emerged from artificial intelligence research. It models SW development as a set of goals, sub goals, preconditions, constraints, and effects. - Requires the ability of the designer to code the knowledge about the environment.

Petri-Net Models: - The structure of roles and their interaction. - Analto Holt’s work in applying Petri nets to modeling coordination in the work place - Example: RADDLE - this kind of models are highly used in commercial products. - This model of coordination among role structure is difficult to use if an organization did not give basic description for its process

Quantitative Models: - Example: system dynamic, which applies feedback and control system techniques to social and industrial phenomena - When applied to project, it improved the productivity and reduced the cost by providing a feedback and dynamic system that responds to changes.

Issues in process Modeling Formality depend on the purpose served by the process model and the agent. That is, process programs enacted by machine should be quite formal, while the ones performed by humans may require less formality. Granularity and Precision It involves the process elements represented in the model and the degree to which a defined process specifies all the process steps needed to produce accurate results

Scriptiveness and Fitness - Fitness: the degree to which the agents performing the process can faithfully follow the process steps it specifies. 1. prescriptive modeling Implies the process should be performed a particular way 2. descriptive modeling try to determine the actual processes currently used to get work done 3. prospective modeling delineate behavior that is not allowed

Referances 1. Bill Curtis, Marc I. Kellner and Jim Over Process Modeling. 1992/vol. 35, No. 9./communications of the ACM.