IMPROVING PROJECTMANAGEMENT USINGFORMAL MODELS ANDARCHITECTURES Theodore Kahn firstname.lastname@example.org Ian Sturken email@example.com Project Management Challenge February 9-10, 2011 Making Modeling Work
Problem Statement2 Project information is stored in various documents, spreadsheets and systems with little consistency and/or formal structure A lack of common understanding of a project’s organizations, roles, objectives, behaviors and constraints .
Agenda3 Theory of: Enterprise and Business Architecture Formal modeling Applying EA and Modeling to Project Management Case studies: MODEAR Flight Readiness System Ares development Ames process modeling Making Modeling Work for You Today Future Trends and Closing Remarks Q&A
Four Modeling Perspectives4 Model Based Systems Engineering (MBSE)
Standards: Languages & AFs5
6 Enterprise Architecture
What is the Scope of an Enterprise7 Architecture? Most Restrictive Several ideas are in common use: • An accounting of an organization’s IT artifacts and their application to lines of business. (Lists of IT things.) • The relationships and behaviors of an organization’s IT artifacts and their application to lines of business. (Lists and Life-cycle of IT things.) • An accounting of an organization’s meaningful artifacts and their application to lines of business. (Lists of “all” things.) • The relationships and behaviors of an organization’s meaningful artifacts and their application to lines of business. (Lists and Life-cycle of “all” things.) Most Expansive
FEA and DoDAF EA Definition8 A strategic information asset base, which defines the mission, the information necessary to perform the mission, the technologies necessary to perform the mission, and the transitional processes for implementing new technologies in response to changing mission needs. EA includes a baseline architecture, a target architecture, and a sequencing plan.
How did we use an Enterprise Architecture?9 To organize the information about our processes, products, people and systems To relate these entities to one another To provide different diagrams and reports of the information suitable to each of the stakeholders in the project To export information to other tools for analysis and simulations
Benefits of Enterprise Architecture10
Zachman Framework What How Who (Data) (Function or (People) Process) Scope •List of things •Function List of important to Hierarchy OrganizationsTechnology business •Functions to Org MatrixAgnostic Technology Business •Conceptual •Process Model •Org to Function Agnostic - Model Data Model mapping (roles) Understand ConOps The Business System •Logical Data •Use Case •Process to Role Model Model Matrix Requirements •Activity Diagram System Requirements Technology Technology •Physical Data •Activity Diagram •Roles/Access Design Model Model •Sequence Matrix Specific – Specifications Diagram Specify and Design theSystems to Support Detailed •Technology •Technology •Technology Design Specific Specific Specific The Business 11
DoDAF 2.0 Framework12
Which EAF do I Use?13 Zachman Easier to grasp and get started with. Can start with lists of “things” and start relating these to other parts of the business Hierarchical in nature, provides good mechanism for abstracting levels of detail from executive to engineer More IT centric DoDAF More prescriptive in nature – specific products to fill different purposes Separate different viewpoints – business processes from systems that support them Supported by many tools Has a modeling language specifically designed for it: UPDM General purpose Create your own If you don’t use a standard framework – you will create your own mechanisms for organizing and relating information in your models!
Use Standard Architecture14 Framework, Model or Both? Architecture Frameworks: Can range from simple (lists) to complex Useful for providing an outline of what information to gather and how to organize that information Can customize this outline to fit your needs Can be used to compare different systems from different vendors Can be used to study “as-is” states to “to-be” states Can leverage modeling languages such as UML, SysML, and Archimate Modeling Standards Can range from simple to complex Quick to build a few diagrams For larger projects will need to organize model Formal language/annotations used Both Provides guidance on what modeling artifacts you will need and how to organize them according to a standard framework
15 Modeling Models, Formal Models and SysML
What is a Model?16 An Abstraction of the Physical World Around Us • An electrical schematic of a radio • An economic model • A mathematical model • A model student • A non working model airplane • A written description of a pencil • A diagram • A spreadsheet • Music • Art • Natural languages
Sample of Modeling Languages17 Language Purpose IDEFx Business UML Software BPN Software AADL Hardware, software, realtime (avionics, aerospace, automotive, and robotics). Simulink Simulation and analysis of multidomain dynamic systems Archimate Business SysML Systems of systems
Modeling Language Attributes18 Formality More formality = less ambiguity, more accuracy Less abstraction = more detail, Abstraction more precision
Abstraction Levels19 La Joconde Femme au Chapeau Orné
What is a Formal Model?20 The degree to which the model adheres to: • Well defined semantics: model components have precise interpretations. • Well defined grammar: model components can only be related using precise structural rules.
Modeling and PM25 Projects are now modeled using spreadsheets, diagrams and documents to represent different parts (components) of the project. A formal model does not change this. Instead, your project components must now be represented using formal grammar and semantics. And, if you are using a standardized framework, your project follows a well known architecture.
System Engineering and Project26 Management From NASA System Engineering Handbook - NASA/SP-2007-6105
Review Entrance Criteria (NASA Systems Engineering Handbook)27 Milestone Artifacts System Concept Review System Goals And Objectives Concept of Operations System Requirements Review System Requirements System Functionality Description Concept of Operations Preliminary System Requirements Preliminary Design Review Preliminary subsystem design Specs Operational Concept Interface Control Documents Requirements Traceability Matrix These can all be described in one model!
Building ConOps from Model28 Conops Section DoDAF product SYSML Model Scenarios OV-5 Activity Diagram Use Case Diagram, Activity Diagram Conceptual Overview OV-1 High Level Concept Block Definition Diagram Event sequence OV-6c Sequence Diagram Connectivity OV-2 Node Connectivity Block Definition Diagram Architecture Diagram, OV-3 Information Exchanges, SV-1 System Interface, SV-2 System Communication Glossary AV-2 Integrated Dictionary Block Definition Diagram
Formal Modeling and Six Sigma (Complementary Technologies.)30 Six Sigma Formal Models Both Together Methodology Yes No Yes Formal Data No Yes Yes Semantics & Grammar Data Persistence No Yes Yes
31 Case Studies
MOD Flight Production Process Re-32 engineering Goal: MOD needs to transform into an agile organization to be able to quickly meet needs and opportunities that arise in the next decade. Challenge: Currently, most information about how we conduct business is housed in different documents, spreadsheets, systems and other repositories. It is difficult to gain a comprehensive, integrated, common view of the way we conduct business and what the impact of changes are on our people, processes and systems. Approach: An enterprise architecture provides a framework that will allow us to organize information about our people, processes and systems in an organized, structured and integrated manner. Benefits: An organization that can quickly assess the impact of external events saving $$$$ and reducing risk.
MOD EA Repository33
Use Architecture Information for34 Several Purposes System DoDAF Architect DiagramsPerformers Mission EA Repository Discrete Operations Event timeline, critical Simulator path determination Tabular reports
DoDAF Connectivity Diagram (OV-2)35
Flight Readiness System36 Goal: Develop a new system to support certification of flight readiness for Cx Challenge: How do we specify the components of our system with varying levels of detail while maintaining consistency throughout Approach: Use DoDAF/UPDM to describe the ‘as-is’ process and systems for shuttle. Then design a new set of processes and supporting systems for Constellation as a ‘to-be’. Benefits: Information is organized and represented consistently with various levels of detail appropriate to different stakeholders
As-Is and To-Be Templates37 As-Is To-Be
Flight Readiness “As-Is” OV-538
Flight Readiness “To-Be” OV-539
Flight Readiness System Model40 Connectivity Activity Diagram Diagram Sending node activity Activity Information Element Exchange Data Report Model Information Element
Modeling Ares Development41 Problem Definition: 1. Large amount of data… 2. maintained in three separate artifacts: document, spreadsheet and diagram… 3. to meet different stakeholder needs. Lead to the following concerns: 1. Time consuming and error prone to modify data as Ares program changes. 2. Not easy to meet new stakeholder needs.
Ares Model Architecture (UPDM)42
Ares Document Attributes43
Ares Document Relations44
UPDM OV7 Diagram (Structure)45
UPDM OV2 Diagram (Behavior)46
UPDM Exchange Types47
Ames and EBA48
SysML Activity Diagram52
55 Making Modeling Work for You Today Practical Information for achieving quick ROI
Modeling is an Engineering Task56 Approach it systematically Know what resources you will need Define milestones, a roadmap Be pragmatic
What Makes a Good Formal Model?57 Model those aspects of the project required to answer stakeholder questions, and no more. Model the degree of precision required to answer stakeholder questions, and no more. Models must always be accurate.
Why is modeling hard? (It Requires Five Knowledge Domains)58 Need to know Need to know Architectural modeling tool Framework Need to Impediments Need to know understand to Modeling project/system modeling domain semantics
Four Modeling Steps (Do only one at a time.)59 Questions & Project knowledge translate to Architectural Framework Knowledge apply to Modeling Language knowledge apply Tool knowledge
Modeling Tools Encompass Two Areas (Do only one at a time.)60 Database program Drawing program
Think Small, Think Focused (Get ROI in Weeks!)61 What questions should your model answer? Select a modeling language. Determine the architecture. Select a tool.
You’re in Front of your Computer (Now what do you do?)62 Your tool is running You created a new project (in this case, SysML) And… You create packages to organize your project
A “Template” SysML Model63
Extending SysML64 Use English to document each entity. Use diagram notes to highlight explain diagram elements. Use SysML Profiles to extend SysML semantics to meet your own domain specific needs.
Modeling Tips65 What if you don’t know something? Make your best guess, its easy to change. What should go on a diagram? Itshould tell a story, answer a question, address a specific stakeholder need. Look to see how a set of diagrams might meet a stakeholder’s need in some specific area. Model only those elements for which you know there is a value.
Culture Issues (Modeling is about sharing information.)66 Some people do not necessarily want to share their information Job security They don’t know the information, and perhaps reluctant to say so. Its time-consuming to get the information, what’s in it for them? Some people like to work independently
Modeling Summary67 Think small, know what questions your model should answer. Keep the architecture simple. Learn your modeling language semantics. Pro actively manage the modeling task: Engineering effort Cultural issues
68 Future Trends and Closing Remarks
Future Trends69 Fully defined semantics Prescriptive methodologies Improved tooling Analytical integration EA Frameworks are adding behavior and project management representations
Closing Remarks70 Approach modeling as an engineering task Determine the architecture (structure) Determine the modeling language Think small and focused Make sure you understand stakeholder needs Be aware of cultural issues
Project Management Information: Gantt Chart, Event Chain Diagram, ISO 10006, Six Sigma …producing strategic …leading to better estimates for PM artifacts... schedule, scope and resources..73 Schedule Resources Scope …and also used for aligning project …maintaining a consistent, feasible schedule, scope and resources… project and a refined model… Formal Model Formal semantic relationships + consistent representations improved common understandings & decisions. …providing consistent operational …used for creating SysML model… information used by all stakeholders… …which encompasses project data… Text Docs Spreadsheets Diagrams Represented by… Projects are defined and change mostly due to external events: Continuously.