Process Modeling. Bill Curtis, Marc I. Kellner and Jim Over. Communications of the ACM Chanhee Yi

Transcription

1 Process Modeling Bill Curtis, Marc I. Kellner and Jim Over Communications of the ACM Chanhee Yi

2 Contents Introduction Overview Conceptual framework Modeling paradigm Modeling issues Future growth Conclusion 2/23

3 Introduction(1/2) Process modeling Brief Definition Process Modeling Motivation of emergence Problems in traditional software description Ambiguous, unusable descriptions Failure to update the documentation with change Needs from the enterprise Business process reengineering Coordination technology Process-driven software development 3/23

4 Introduction(2/2) Process modeling (cont d) Goals Human understanding Process improvement Process management Automated execution Automated guidance 4/23

5 Overview Perspectives Process modeling Conceptual framework Future Directions Modeling Paradigm Formality Granularity Scriptive ness Terminology Modeling Issues? 5/23

6 Conceptual framework(1/2) Terminology Process element Any component of a process Process step Atomic action of a process Agent Role An actor who performs a process element A set of process elements assigned to an actor Artifact Product created or modified by process element execution 6/23

7 Conceptual framework(2/2) Perspectives in process representation Functional What elements are performed Behavioral When and how elements are performed Organizational Where and by whom elements are performed Informational Represent informational entities 7/23

8 Modeling paradigm(1/7) Representation with software languages General start point for process modeling Means for representing and enacting a process Resource of process evolution through feedback 8/23

9 Modeling paradigm(2/7) Programming models View of regarding a process as programming REBUS Support for the requirement specification 9/23

10 Modeling paradigm (3/7) Functional models Hierarchical and Functional Software Process(HFSP) Hierarchical process decomposition Concurrent processes and backtracking Flexible and dynamic execution mechanism 10/23

11 Modeling paradigm (4/7) Functional models(cont d) activity JSP( spec prog.out ) => MakeProgTree( spec progtree ) EnumerateOprs( spec oprs ).. spec JSP prog spec MakeProg Tree Prog Tree spec Enumerate Oper oprs oprs Prog Tree MakeProg prog prog DoProg Inversion prog 11/23

12 Modeling paradigm(5/7) Plan-based models Artificial intelligence approach to contingency GRAPPLE Constraint-based planning system Plan execution simulation system OPERATOR GOAL: PRECONDS: CONSTR: EFFECTS: release current-release(system) built(system) regression-tested(system) performance-tested(system) current-release(c) not-equal(c,system) DELETE current-release(c) ADD current-release(system) ADD customer-release(system) ADD prior-release(system,c) 12/23

13 Modeling paradigm(6/7) Petri-net models Coordination of the model s structure of roles Role interaction nets Method of coordinating the routing of artifacts Method of tracking progress Designer Send Document Review Team Leader Review Team Member Project Manager Receive Update status Announce and schedule Approve team membership Note schedule Plan review time 13/23

14 Modeling paradigm (7/7) Quantitative models System dynamics Application of feedback and control to social phenomena Manpower vs Hiring time delay L : Level (of people) R : Rate (hiring/firing) T : Average Time Delay Perceived Work Accomplished(PWA) VF*(% of Resource remained)+(1-vf)*(% of Work finished) VF : Visibility Factor 14/23

15 Modeling issues(1/2) Formality Specify Mathematical level of modeling languages Considered to control flexibility of task representation Granularity Consider precision with time and human Considered to provide multiple level of abstraction Precision Represents the degree of specifying process steps 15/23

16 Modeling issues(2/2) Scriptiveness involves prescriptive modeling Planned modeling Involves descriptive modeling Evolutionary modeling Involves proscriptive modeling Fitness Law-governed modeling Represents the degree of agent s fulfillment to steps Used to analyze prescriptive models 16/23

17 Future directions(1/6) Multi-paradigm representations Emphasis on diversity and suitability of a modeling STATEMATE DEV_MODULE_TESTS description: Task of planning and developing unit tests for a module. executed throughout: DEVELOP_TESTS carried out by: QA attributes: NAME: USES_FACILITY VALUE: DVLPMT_SUITE HAND_CARRIED_2 Contains: CODE_LISTINGS; TEST_PLANS Interconnections Textual Information Functional Perspective Activity Chart 17/23

18 Future directions(2/6) Multi-paradigm representations(cont d) FACILITY_MGMT DVLPMT_SUITE COMPUTER_FILES IO_1 IO_2 IO_3 IO_4 SW_ENGINEERING SW_DEVELOPERS HAND_CARRIED_1 QA HAND_CARRIED_2 UNIT_DEV_FOLDER DATA_MGMT Behavioral Perspective - State chart Organizational Perspective - Module Chart 18/23

19 Future directions(3/6) Process improvement Effects of a well-defined process Results of documentation and person training Foundation for quality and productivity Capability Maturity Model(CMM) The way for organization to improve schedules and budget Identification to the current maturity of process Improvement on top of documents 19/23

20 Future directions(4/6) Process improvement(cont d) 20/23

21 Future directions(5/6) Process-based software development Automated execution support and guidance Tools that support the entire process Tool integration with environment Design for work coordination 21/23

22 Future directions(6/6) Process-based software development(cont d) MARVEL Rule-based approach Backward-chaining and forward-chaining Emphasis on functional and behavioral perspectives strategy doc_tools_rules Imports none; Exports all; Objectbase DOC_HEAD :: superclass TOOL; doc_head : string = specify_header; End.. End_objectbase rules doc_head[?d : DOC_TYPES] : suchthat : { DOC_HEAD doc_head?d } (?d.head_created = HeadFileExists) ; (?d.head_created = HeadFileNonExists) ;.. 22/23

23 Conclusion Guidance to process modeling Concepts and perspectives in representation Five paradigms as an approach Future directions with field growth 23/23

24 Perspectives and Language Functional Behavioral Organizational Informational Procedural programming languages O O O System analysis and design O O O AI languages and approaches O O Events and triggers State transition and petri-nets O O O Control flow Functional languages Formal languages Data modeling Object modeling O O Precedence networks O O Perspectives O O O O 24/16

25 APPL/A Ada process programming language based on aspen Relations Program unit that provides for the storage of data Triggers Tasks that represent concurrent threads of control Predicates Named boolean expressions over relations 25/16

26 STATEMATE Multiple language paradigms State transitions with events and triggers System analysis and design diagrams Data-modeling Common denominator schema Loose incorporation between various paradigms Object-Oriented and entry-relationship schema 26/20

27 STATEMATE(cont d) Common denominator schema 27/20

28 Petri-net Models of concurrency, non-determinism and control flow Modeling framework for discrete event dynamically systems Sequential Execution Concurrency Synchronization 28/16