The document discusses situational method engineering and describes methods as units of modeling and description for work allocation, coordination, and execution. It notes the abundance of methods used in different domains and problems with comparing and combining methods. Situational method engineering is proposed as an approach to generate methods tailored to specific situations by selecting appropriate elements from a reference library of methods. Key aspects discussed include method representation using models and ontologies, roles in situational method engineering such as methodologists and method engineers, and enacting methods with tools and through reflection and improvement cycles.
3. Example: methods in management ( endeavour management : enterprise , program , project ) 140 organisational fashions and fads , 2003. Thomas H.Davenport, Laurence Prusak, "What's the Big Idea?: Creating and Capitalizing in the Best Management Thinking"
4.
5.
6.
7.
8.
9. Model = instrument ( to see invisible ) Where is throughput ?!
10. Two views of life cycle (pic .17 from ISO TR 19760:2007 ) In the standard « enterprise view » and « management view » are mixed up.
11. ( Meta ) model of method element : to provide at least 4 views/viewpoints Model knowledge ( schema , metamodel ) Method element Management ( project , resources) Engineering (process , roles ) Organizational ( agreements , actors - transactions ) Client/value (system/product) Project/workflow model System/product/facility model System and life cycle information model System and system life cycle (process/project) models are assembled from method elements System/product/plant model is dependant on methods used! Functional models Logical Models Physical Models Requirements Re. parameters
12. Method content vs. process/life cycle (SPEM 2.0) RUP (Rational Unified Process) MFESA (Method Framework for Engineering of System Architecture) t Activities = method content use
13. Method element Schema ( Metamodel ) STA-methodology (G.P.Schedrovitsky): Act of activity OPF (Open process framework): method element goal knowledge means A1 … An source materials product transformation Awareness display
14. Metamodel standards for methods Metamodel standard Definition of « activity » ISO 24774 , 15288 The activities are a list of actions that may be used to achieve the outcomes. Each activity may be further elaborated as a grouping of related lower level actions. Rather than describing the results of executing a process, activities describe a set of actions that might be undertaken to execute the process. ISO 24744 (ProcessKind) A process kind is a specific kind of process, characterized by the area of expertise in which it occurs. ProcessKind is a subclass of WorkUnitKind. SPEM 2 An Activity is a Work Breakdown Element and Work Definition that defines basic units of work within a Process as well as a Process itself. In other words, every Activity represents a Process in SPEM 2.0. It relates to Work Product Use instances via instances of the Process Parameter class and Role Use instances via Process Performer instances. BPMN 2 An Activity is work that is performed within a Business Process. An Activity can be atomic or non-atomic (compound). The types of Activities that are a part of a Process are: Task, Sub-Process, and Call Activity, which allows the inclusion of re-usable Tasks and Processes in the diagram. However, a Process is not a specific graphical object. Instead, it is a set of graphical objects. The following sections will focus on the graphical objects Sub-Process and Task. ISO 15926 A 15926-4 actual individual that brings about change by causing the event that marks the beginning, or the event that marks the ending of an individual. NOTE: Behavior is a term used to describe an activity either where there are preconditions and the activity is a response to those preconditions, e.g. reaction to touching a hot surface, or where the way an activity occurs is described by some property or function, e.g. fluid flow being described by the viscosity of the fluid. OPF the highest-level work unit consisting of a cohesive collection of tasks that are performed by one or more collaborating producers when producing a set of related work products or providing one or more related services.
19. Solution for models incompatibility : ISO 15926 ( life cycle data integration ) Integration ontology : reference data library ISO 15926-3 , 4 Method 1 model Method 2 model + library amendments rules ISO 15926-6 + notations of ontology representation ISO 15926-7,8 + computer application interoperability rules ISO 15926-9 Model integration Model interoperability categories ISO 15926-2 Ontologist, logician Methodologist Method engineer
20. Data model pyramid ISO15926 : Not only product/plant model, also project/method/practices/process/activities models Challenge : process/method ontology almost non-existent in RDL ISO 15926 !!! Douglas Lenat : « blue-collar philosophers » role , entity , individual General engineering concepts : connection, detail, flow ... 201 categories and concepts 10 ths. items : requirement , pump, heat exchanger ISO 15926-2 ISO 15926-4 Rules for addition ISO 15926- 7,8 100 ths . 1 ml . 10 ml .
25. Example: Method choice in Project planning Process management in manufacturing ( queue to « work station ») Traditional project management ( one multitasked worker ) Critical chain (TOC) (common time buffer for task group) Activity with 3 tasks Using data from Eli Schragenheim и Daniel P.Walsh
26. Software tools for situational method engineering ( method composers and modelers ) ISO 15288:2008 processes in Eclipse Process Framework Composer Difference between « method composers » and process/project management tools : integrated support of many views/viewpoints (according to method metamodel) – role, project, process, product, guidance, etc.
27.
28. Reflection in process enactment: maturity levels 1. Method applied ad hoc , outcomes usually achieved 2. Method applied and described (modeled) , method model disscussed (reflected). 3. Method modeled and activities are defined by model (disciplined execution). 4. Method systematically reviewing in the cycle of continuous method improvement. Life cycle stages of situational method
29.
Notas del editor
Management fashion theory was suggested by Eric Abrahamsson