Project Management This example emphasises the embedding of logic in a model.

Slides:



Advertisements
Similar presentations
Chapter 7 Managing Risk.
Advertisements

Chapter 10: Designing Databases
Defining activities – Activity list containing activity name, identifier, attributes, and brief description Sequencing activities – determining the dependencies.
Lecture 8- Analysis Modeling The Elements of Anaylsis Model The Elements of Anaylsis Model Data Modeling, Functional Modeling and Information Flow Data.
PROFESSIONAL PORTFOLIO REVIEW IALD PROFESSIONAL PORTFOLIO REVIEW This template has been prepared to assist you with the process of the professional portfolio.
Information System Engineering
Program Management Program management has similarities to the management of an ecosystem - not just the biggest fish are important.
Prof. Ing. M. Dassisti Enterprise modelling for networked enterprise: interaction aspects for a training organisation 16th IFAC World Congress, Prague.
Orion Philosophy and Rationale. If it really is structure, what sort of structure is it? We are asserting that it is active dynamic undirected structure.
Software Testing and Quality Assurance
Use cases and requirement specification - 1 Use case diagrams 3 use cases System boundaries Remember: Use case diagramming is a tool, not the requirements.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
Analysis Concepts and Principle.
UML Sequence Diagrams Eileen Kraemer CSE 335 Michigan State University.
Orion Overview. We build an internal model of the world, so we can predict future behaviour - we make the model out of active structure so it is interoperable.
Chapter 10: Architectural Design
The chapter will address the following questions:
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
What is Software Architecture?
Annual SERC Research Review - Student Presentation, October 5-6, Extending Model Based System Engineering to Utilize 3D Virtual Environments Peter.
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
Systems Thinking and Systems Engineering Introduction to the course 22 January 2013 Francois Christophe Galina Medyna Eric Coatanéa.
Chapter 7 Structuring System Process Requirements
1.eCognition Overview. 1 eCognition eCognition is a knowledge utilisation platform based on Active Knowledge Network technology eCognition covers the.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
The Concept Convert free text into a structure that captures objects, relations, existential, propositional and temporal logic – the whole thing, no excuses.
1 On to Object Design Chapter 14 Applying UML and Patterns.
More on “The Huddersfield Method” A lightweight, pattern-driven method based on SSM, Domain Driven Design and Naked Objects.
Content The system development life cycle
Operational Logistics. Useful New Abilities The abilities to: embed alternatives, contingencies switch on/off different chains dynamically extend the.
Introduction to Projects. Presentation Outline What is Project Management? What is Project Management? What is a Project? What is a Project? Projects.
Home Work. Design Principles and Weak Entity Sets.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Organizational Project Management Maturity Organizational Project Management Maturity Model (OPM3) PMI-MN Breakfast sessions Improvement Planning.
Knowledge Networks or “The Rise of the Machines”.
Managing programs that promote personal effectiveness.
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
Managing Schedule Slack/Float PMI Scheduling Forum January 6, 2015 January 6, 2015 Presented by: Ric Albani, PMP, PMI-SP, PMI-RMP, MCTS.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
Test Taking Skills Make sure you prove what you know!
ECognition Model Components. 2. eCognition Model Components1 Model Components Variables and Constants Operators and Functions Links Logical States Messages.
Sequence diagrams Lecture 5. Main terms  Interaction  Life line  Activation  Executable behavior and derived behavior  Messages  Trajectory  Frame.
1 Design and evaluation methods: Objectives n Design life cycle: HF input and neglect n Levels of system design: Going beyond the interface n Sources of.
1 Team Skill 3 Defining the System Part 1: Use Case Modeling Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and.
Modeling with UML – Class Diagrams
Analysis Classes Unit 5.
Software Architecture
Learning in Design and Technologies
Working with Client-Side Scripting
Unified Modeling Language
Rumbaugh’s Objectmodeling Technique
Process Modelling Chapter 6.
Interactions.
Object Oriented Analysis and Design
Requirements To Design In This Iteration
Agile Process: Overview
And now for something completely different . . .
Chapter 20 Object-Oriented Analysis and Design
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
BPMN - Business Process Modeling Notations
An Introduction to Software Architecture
Applying Use Cases (Chapters 25,26)
Applying Use Cases (Chapters 25,26)
Use Case Modeling Part of the unified modeling language (U M L)
Nicholas J. Di Liberto 20 June 2011
Segments Introduction: slides minutes
Software Architecture
Presentation transcript:

Project Management This example emphasises the embedding of logic in a model

What New Abilities does PM Need The abilities to: embed alternatives, backup activities, contingencies switch on/off activities, resources, budgets dynamically extend the model the model to learn from simulations model what the project is about - what as well as when More descriptive structure - more states - more flexibility

Basic Element - The Activity Existence of the activity is logically controllable. Values for Start, Finish, Duration can be discontiguous ranges.

A Linkable Object Activities have attributes - Start, Duration etc. - which are linkable objects. The ranges on these attributes are consistently maintained.

No Need for Multiple Passes Transmission of ranges through operators eliminates the need for an Early Start pass and a Late Finish pass - the ranges tell the story. Logic responding to these ranges and working in all directions allows the model to be a “live” representation of the project - change something and everything else changes to suit. MAX

Constraints Constraints are logically controllable entities

All Sorts of Constraints No real limit on the complexity of the constraints you can embed to reflect project reality

Differing Views - Each Important Constraints come from everywhere

Undirected Structure The constraint logic on starts and finishes follows how we reason

Embedding Logic IF Project_Duration < 1000 THEN Bonus = ELSE Bonus = 0 Changing the Project Duration changes the Project Cost and vice versa - the structure is undirected

Controlling Existence Influences flow through the network A FALSE state coming out of one ACTIVITY will cause the XOR to switch the control pin on another activity to TRUE

Disabling Activities Sending a FALSE into an activity disables the connection between Start and Finish so constraints from this activity are no longer active - existence is under logical control

Jumping About The examples refer to Constraint Reasoning - staying within consistent states. Most planning is about jumping from one state to a new state inconsistent with the last. The project model needs to be useful in evaluating scenarios inconsistent with the current plan - of reorganising itself so some new plan is consistent. The model structure is active, uncommitted and self-modifying.

The system is more comprehensible because it uses logical states in uncommitted structure to guide its actions and it responds dynamically to changes in its structure The System as a Thinking Tool

Planning Spectrum The technology supports the entire acquisition process, from bubble diagrams to detailed project plans, maintaining consistency and visibility

Stitching We can stitch the different worlds together with undirected logical thread, so a change goes anywhere it needs to The project manger has limited responsibilities, with other actors responsible for many other aspects of the project

Impact On Project Management The Project Manager is often disconnected from the content of the project, dealing only with committed activities, resources, budgets. The ability to blend an activity view - the “when” and “how” - with the “what” and “why” and the overall risk - allows a more holistic view both of individual projects and programs for multiple projects.