Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

PrimaryScape Introduction

545 views

Published on

This presentation introduces PrimaryScape, a new modeling notation to describe enterprises, systems, teams, and project/program outcomes.

Published in: Business, Technology
  • Be the first to comment

PrimaryScape Introduction

  1. 1. PRIMARYSCAPE TM 1
  2. 2. PRIMARYSCAPE A New Modeling Notation TM 1 structure behavior information data access data transfer functional access functional transfer organization A network file share systemteam A team B create a report report reportable information create reports read write query analyze report email notification read organization C team C process report report transfer network file share team A system team B create a report report reportable information create reports read write query analyze report email notification read Person/Team/System/ Business Unit/Organization Supplier Consumer Input OutputProcess reference information transactional information read write structure [basic notation] Team [extended notation] Organization [extended notation] information [basic notation] information of record [extended notation] transient information [extended notation] behavior [basic notation] emphasized behavior [extended notation] transient behavior [extended notation]
  3. 3. PRIMARYSCAPE IS A NEW SIMPLE MODELING NOTATION THAT CAN BE USED TO MODEL ANY SYSTEM Teams - Companies - Enterprises Information Systems - People - Applications Programs - Batch Scripts - File Transfers ... or any other type of system 2
  4. 4. PRIMARYSCAPE It is Simple It is Easy to Understand It is Expressive 3
  5. 5. PRIMARYSCAPE It is Simple It Helps Bridge the Business-IT Divide It Scales to Any Level It is Easy to Understand It is Expressive 3
  6. 6. PRIMARYSCAPE It is Simple It Helps Bridge the Business-IT Divide It Scales to Any Level It is Easy to Understand It Shows Teams Together with Systems It is Expressive It shows Process Together with Information 3
  7. 7. PRIMARYSCAPE This modeling notation was created ... to be simple enough ... for just about anyone to understand ... with only a brief introduction.  4
  8. 8. PRIMARYSCAPE This modeling notation was created ... to be simple enough ... for just about anyone to understand ... with only a brief introduction.  It is a modeling notation that makes it easy ... to describe systems visually. 4
  9. 9. PRIMARYSCAPE This modeling notation was created ... to be simple enough ... for just about anyone to understand ... with only a brief introduction.  It is a modeling notation that makes it easy ... to describe systems visually. It is a lot more expressive ... than most typical box and line diagrams ... used in many presentations. 4
  10. 10. 5 INTRODUCTION Andreas Amundin Enterprise, Business, and Technology Architect Creator of the PrimaryScape Modeling Notation
  11. 11. 5 INTRODUCTION Andreas Amundin Enterprise, Business, and Technology Architect Creator of the PrimaryScape Modeling Notation My Background Over the years I have worked both as a consultant and employee in roles including: • enterprise, business, & technology architecture • professional trainer • integration architect • software architect • business analyst • technical lead • software developer
  12. 12. 5 INTRODUCTION Origin of PrimaryScape In creating PrimaryScape I have drawn from my experience over the last 20 years covering: • object oriented programming and design • unified modeling language • use cases and use case based requirements • business information and data modeling • business process management and modeling • functional decompositions • capability modeling • enterprise architecture methodologies Andreas Amundin Enterprise, Business, and Technology Architect Creator of the PrimaryScape Modeling Notation My Background Over the years I have worked both as a consultant and employee in roles including: • enterprise, business, & technology architecture • professional trainer • integration architect • software architect • business analyst • technical lead • software developer
  13. 13. 5 INTRODUCTION Origin of PrimaryScape In creating PrimaryScape I have drawn from my experience over the last 20 years covering: • object oriented programming and design • unified modeling language • use cases and use case based requirements • business information and data modeling • business process management and modeling • functional decompositions • capability modeling • enterprise architecture methodologies For more information about PrimaryScape http://www.primaryscape.com Contact info@primaryscape.com to request • additional information • on site presentations • training • collaborative work sessions Andreas Amundin Enterprise, Business, and Technology Architect Creator of the PrimaryScape Modeling Notation My Background Over the years I have worked both as a consultant and employee in roles including: • enterprise, business, & technology architecture • professional trainer • integration architect • software architect • business analyst • technical lead • software developer
  14. 14. PRIMARYSCAPE NOTATION The PrimaryScape notation is simply made up of 3 concepts and 4 relationships. 6 The 3 concepts are represented by behavior and information realized in structure. structure behavior information
  15. 15. PRIMARYSCAPE NOTATION The PrimaryScape notation is simply made up of 3 concepts and 4 relationships. 6 The 3 concepts are represented by behavior and information realized in structure. The 4 relationships are data access, data transfer, functional access, and functional transfer. structure behavior information data access data transfer functional access functional transfer
  16. 16. PRIMARYSCAPE CONCEPTS Behavior represents any activity, process, or function.  Basically if anything happens it is behavior. 7
  17. 17. PRIMARYSCAPE CONCEPTS Behavior represents any activity, process, or function.  Basically if anything happens it is behavior. Information represents any set of information, data, or material.  Basically if it is acted on, used by, or produced by some kind of behavior then it is considered information. 7
  18. 18. PRIMARYSCAPE CONCEPTS Behavior represents any activity, process, or function.  Basically if anything happens it is behavior. Information represents any set of information, data, or material.  Basically if it is acted on, used by, or produced by some kind of behavior then it is considered information. Structure represents the tangible things which realizes behavior and information.  Structure is basically anything which has to be created, configured, or set up before behavior can occur or information stored.   7
  19. 19. PRIMARYSCAPE RELATIONSHIPS Relationships are used to show interactions between behavior and information. Relationships can also be divided into two types, access and transfer.   With behavior+information & access+transfer we get a 2×2 matrix of relationships. access transfer information behavior 8
  20. 20. PRIMARYSCAPE RELATIONSHIPS Relationships are used to show interactions between behavior and information. Relationships can also be divided into two types, access and transfer.   With behavior+information & access+transfer we get a 2×2 matrix of relationships. access transfer information behavior 8 data access informational access data transfer informational transfer functional access behavioral access functional transfer behavioral transfer
  21. 21. PRIMARYSCAPE RELATIONSHIPS Data access is a relationship primarily between behavior and information.  The direction of the arrow should indicate the main direction of the flow of information. 9
  22. 22. PRIMARYSCAPE RELATIONSHIPS Data access is a relationship primarily between behavior and information.  The direction of the arrow should indicate the main direction of the flow of information. Data transfer is a relationship mainly between two sets of information.  Think of data transfers as sending letters or packages via mail as compared to the data access relationship which is more like picking up a phone to exchange the information while you wait. 9
  23. 23. PRIMARYSCAPE RELATIONSHIPS Data access is a relationship primarily between behavior and information.  The direction of the arrow should indicate the main direction of the flow of information. Data transfer is a relationship mainly between two sets of information.  Think of data transfers as sending letters or packages via mail as compared to the data access relationship which is more like picking up a phone to exchange the information while you wait. Functional access is a relationship between two functions (behaviors). A weight or anchor indicates which function initiates the access. The direction of the arrow should indicate the main direction of the flow of information. 9
  24. 24. PRIMARYSCAPE RELATIONSHIPS Data access is a relationship primarily between behavior and information.  The direction of the arrow should indicate the main direction of the flow of information. Data transfer is a relationship mainly between two sets of information.  Think of data transfers as sending letters or packages via mail as compared to the data access relationship which is more like picking up a phone to exchange the information while you wait. Functional transfer is a relationship between two functions (behaviors).  Functional transfers show how one behavior triggers another behavior.  The most common use of a functional transfer is to show the order in which behaviors take place, one function (behavior) handing off to the next. Functional access is a relationship between two functions (behaviors). A weight or anchor indicates which function initiates the access. The direction of the arrow should indicate the main direction of the flow of information. 9
  25. 25. A Simple Example 10
  26. 26. PRIMARYSCAPE - A SIMPLE EXAMPLE 11 network file share team A system team B create a report report reportable information create reports read write query analyze report email notification read Even without knowing the different relationship the behavior, information, and structure provides the context which makes the overall diagram intuitively understandable. The next set of slides will walk through this simple example using a chronological story board approach. This is an example of the simplicity and expressiveness the PrimaryScape modeling notation. A new audience only need to understand that behavior/ functionality is represented using yellow shapes, information is represented using green shapes, and structure is represented using blue shapes.
  27. 27. PRIMARYSCAPE - A SIMPLE EXAMPLE 12 team A This example starts with Team A. Team A is a structure ... a team. This is the structure where something first happens.
  28. 28. PRIMARYSCAPE - A SIMPLE EXAMPLE 13 team A create a report Team A is going to create a report.
  29. 29. PRIMARYSCAPE - A SIMPLE EXAMPLE 14 team A system create a report create reports query When creating a report Team A is accessing the functionality of a system to create reports.
  30. 30. PRIMARYSCAPE - A SIMPLE EXAMPLE 15 team A system create a report reportable information create reports read query The system functionality accesses the data it maintains. When creating a report the system only reads the information, i.e. the information flows into the function as indicated by the data access arrow.
  31. 31. PRIMARYSCAPE - A SIMPLE EXAMPLE 16 team A system create a report reportable information create reports read query The arrow of the functional access between Team A and the system is used to show the main flow of information. In this case the created report is returned to Team A.
  32. 32. PRIMARYSCAPE - A SIMPLE EXAMPLE 17 network file share team A system create a report report reportable information create reports read write query As part of the activity to create a report Team A is supposed to save the report into a shared folder on the network.
  33. 33. PRIMARYSCAPE - A SIMPLE EXAMPLE 18 network file share team A system team B create a report report reportable information create reports read write query analyze report email notification As part of the activity to create a report Team A is also supposed to notify Team B. Team A doesn’t need to wait for Team B to do anything. Team A just needs to let Team B know that it is done creating a report.
  34. 34. PRIMARYSCAPE - A SIMPLE EXAMPLE 19 network file share team A system team B create a report report reportable information create reports read write query analyze report email notification read As part of analyzing the report Team B reads the report from the shared folder on the network.
  35. 35. PRIMARYSCAPE - A SIMPLE EXAMPLE 20 network file share team A system team B create a report report reportable information create reports read write query analyze report email notification read With this simple example of the PrimaryScape modeling notation you now know enough to at a glance be able to spot in any PrimaryScape diagram where information is stored and where behavior takes place. All you have to remember is that • yellow shows behavior • green shows information • blue shows structure It doesn’t get any easier than this.
  36. 36. A Practical Notation 21
  37. 37. 22 CREATED FOR WHITEBOARD USE PrimaryScape was created to work on whiteboards and plain old paper. Each shape is unique both in form and in color. This also means all the different shapes are distinguishable when printed or copied in grayscale.
  38. 38. Wrapping Up 23
  39. 39. 24 PRIMARYSCAPE REFERENCE INFORMATION Videos PrimaryScape Introduction PrimaryScape Extended Notation For more information about PrimaryScape http://www.primaryscape.com Contact info@primaryscape.com to request • additional information • on site presentations • training • collaborative work sessions Andreas Amundin Enterprise, Business, and Technology Architect Creator of the PrimaryScape Modeling Notation Links PrimaryScape Website Introduction Legend and Simple Example Extended Notation PrimaryScape™ by Andreas Amundin is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License.
  40. 40. PRIMARYSCAPE A New Modeling Notation TM 25 structure behavior information data access data transfer functional access functional transfer organization A network file share systemteam A team B create a report report reportable information create reports read write query analyze report email notification read organization C team C process report report transfer network file share team A system team B create a report report reportable information create reports read write query analyze report email notification read Person/Team/System/ Business Unit/Organization Supplier Consumer Input OutputProcess reference information transactional information read write structure [basic notation] Team [extended notation] Organization [extended notation] information [basic notation] information of record [extended notation] transient information [extended notation] behavior [basic notation] emphasized behavior [extended notation] transient behavior [extended notation]

×