Avancier Methods (AM) Solution level Business Architecture

Size: px

Start display at page:

Download "Avancier Methods (AM) Solution level Business Architecture"

Garry Poole
5 years ago
Views:

1 Methods (AM) Solution level Architecture Scenario driven analysis and design It is illegal to copy, share or show this document without the written permission of the copyright holder

2 Where in the AM process? Initiate Govern Manage Architect Understand the baseline Review initiation outputs Review NFRs Design the target Plan

3 Skills Framework for the Information Age suggests 7 views SFIA defines EA and BA as inter-relationships between 7 views (Capability view added below) Environment External environs view view Function Capability view Data Data/Info view Data Entity Atomic Activity Org Unit Organisation view Apps & Technology Technology view App Applicat n Role People view Actor Technol gy

4 Scenario-driven analysis and design 1. Identify required 2. Encapsulate as a 3. Decompose to OPOPOT activities 4. Assign activities to Roles 5. Define Data created and used 6. Define App s needed 7. Define Applications 8. Define Infrastructure Note: before technology External before internal Behaviour before structure The level and rigor of decomposition needed varies Data Entity App Applicat n Technol gy Atomic Activity 4 Function Role Org Unit Actor

5 view 1. Identify required EA as Strategy: Define your operating model Identify processes that distinguish you competitively Envision your customer s experience as it ought to be Decide how you your company will grow Define services to be provided by the process or system to be designed 1 E.g. The required business service is The capture of an order by a salesman at a customer s premises

6 2. Encapsulate as a Define end and/or output of the process - and post conditions Define trigger and/or input to the process - and preconditions 1 Order capture Signature Name Order Capture Input / trigger Output / result Salesman given sales visit details Salesman confirms order to interested parties Functional rules Preconditions Sales visit to customer premises has been agreed and scheduled Non-Functional requirements Post conditions Duration Throughput Commission Order and Customer Details captured 2 days 10 per minute 30 percent of order value

7 view 3. Decompose to OPOPOT activities Initially, define the straight-thru or happy path to the desired result Precondition: Sales visit to customer premises has been agreed and scheduled 1 1 Initiate sales process with the customer 2 Discuss customer requirements 3 Work with customer to create a product configuration 4 Verify that the desired configuration can be delivered 2 3 Atomic Activity 5 Determine price of requested configuration 6 Confirm customer desire to purchase 7 Place an order 8 Capture customer signature Post condition: Order captured

8 Sooner or later, detailed analysis must be done Given the straight-thru or happy path Examine every step What else could happen? What else could an actor do - other than what is expected? What if they don t do anything at all? Is there a time out? What could wrong? What resources created or used at this step are vulnerable to being exposed, lost or corrupted? What security measures need to be put in place? These questions may be asked at any and every level of process decomposition, but here, the focus is on the first pass design.

9 More pictorial style You don t have to draw a formal process flow chart to begin with People like pictures

10 People view 4. Assign activities to Roles 1 2 Function 3 Atomic Activity Org Unit 4 Role Actor

11 Assign activities to Roles Role Cust Sender Driver Sorter Driver Recvr process Order Delivery Collect from Sender Deliver to Depot Sort Collect from Depot Deliver to Receiver Record Receipt Application use case Application

12 Assign activities to Roles Precondition: Sales visit to customer premises has been agreed and scheduled Human actors (roles) Customer Sales person 1 Initiate sales process with the customer Accept sales person Greet customer 2 Discuss customer requirements Explain problems & requirements 3 Work with customer to create a product configuration 4 Verify that the desired configuration can be delivered Select one option based on capabilities Accept Listen Show product and configuration options Show availability to customer Show delivery date to customer 5 Determine price of requested configuration Accept Accesses price system and Shows price to customer 6 Confirm customer desire to purchase Accept Show offer 7 Place an order Captures order details and prints out fax 8 Capture customer signature Sign Requests signature Post condition: Order captured

13 Data/Info view 5. Define Data created and used Define data groups or items that each process step a) Needs or uses b) Creates or updates 1 Initiate sales process with the customer 2 Discuss customer requirements Data created and used 3 Work with customer to create a product configuration Product description Configuration assembly 4 Verify that the desired configuration can be delivered Configuration availability Delivery date 5 Determine price of requested configuration Price of configuration 6 Confirm customer desire to purchase 7 Place an order Customer details Data Entity 8 Capture customer signature Paper copy of order Signature Atomic Activity

14 Data/Info view Technology view 6. Define App s needed Identify steps at which actors use applications and technologies to do the activity and create/use the data. Define the services needed from applications at each step List these as use cases 1 2 Data Entity 5 3 Atomic Activity 6 App

15 Define Application s needed Precondition: Sales visit to customer premises has been agreed and scheduled Human actors (roles) Computer actors (roles) Customer Sales person Client app use case 1 Initiate sales process with the customer Accept sales person Greet customer 2 Discuss customer requirements Explain problems & requirements 3 Work with customer to create a product configuration 4 Verify that the desired configuration can be delivered 5 Determine price of requested configuration Select one option based on capabilities Listen Show product and configuration options Show availability to customer Get product description Assemble configuration Check configuration availability Accept Show delivery date to customer Get delivery date Accept 6 Confirm customer desire to purchase Accept Show offer Accesses price system and Shows price to customer Price configuration 7 Place an order Captures order details and prints out fax 8 Capture customer signature Sign Requests signature Post condition: Order captured Enter order Get fax response

16 Technology view 7. Define Applications Given the required use cases Identify applications to be bought Do not say ERP! You could however name ERP modules you know provide the required use cases 1 Or scope applications to be built If you end up identifying a hundred use cases, either your system should be broken down into a number of smaller projects, or you are modelling use case pathways rather than use cases. If you end up with one use case, then you need to move down a level of abstraction or get a bigger project. After Ivar Jacobsen Data Entity App Applicat n 2 3 Atomic Activity

17 Example tailored from one in TOGAF 8 Precondition: Sales visit to customer premises has been agreed and scheduled Human actors (roles) Customer Sales person Client app use case 1 Initiate sales process with the customer Accept sales person 2 Discuss customer requirements Explain problems & requirements 3 Work with customer to create a product configuration 4 Verify that the desired configuration can be delivered Select one option based on capabilities Greet customer Listen Show product and configuration options Show availability to customer Computer actors (roles) Get product description Assemble configuration Check configuration availability Data centre app Product Configurator App Inventory App Accept Show delivery date to customer Get delivery date Scheduling App 5 Determine price of requested configuration 6 Confirm customer desire to purchase Accept Accept Accesses price system and Shows price to customer Show offer 7 Place an order Captures order details and prints out fax 8 Capture customer signature Sign Requests signature Post condition: Order captured Price configuration Enter order Get fax response Pricing App Order App

18 Technology view 8. Define Infrastructure List Infrastructure Technology components needed to enable the Applications Platform technologies Networks Etc. 1 2 Data Entity 5 3 Atomic Activity 6 7 App Applicat n 8 Technol gy

19 When to stop? The level and rigor of decomposition needed varies If a process step is coarse-grained and not defined in sufficient detail for application procurers or designers And there remains more time, budget and resources for analysis Then divide that process step into shorter process steps and cycle through the earlier analysis process Else, stop the analysis

20 Decomposition from business process to application process architecture Applications architecture Use Case Automated Catalogue Top-down definition of required services Bottom up definition of provided services

21 Where does business architecture stop and data and/or application architecture start? A human process is typically decomposed to the level where an OPOPOT process at the human computer interface (HCI) is definable in an application use case. Consider the process called calculate insurance premium This might be documented a pre or post condition of a business process step a derivation rule for a business data item a pre or post condition of an application service or use case You decide which architecture domain to document the process in

22 Scenario-driven analysis and design (RECAP) 1. Identify required 2. Encapsulate as a 3. Decompose to OPOPOT activities 4. Assign activities to Roles 5. Define Data created and used 6. Define App s needed 7. Define Applications 8. Define Infrastructure Note: before technology External before internal Behaviour before structure The level and rigor of decomposition needed varies Data Entity App Applicat n Technol gy Atomic Activity 4 Function Role Org Unit Actor

23 Scenario-driven analysis and design Beware: managers like to short cut the analysis! 1 2 Function 3 Data Entity 5 Atomic Activity Org Unit 6 App 4 Role Actor 7 Applicat n 8 Technol gy

24 Principle: assign structures to perform required behaviours Define required behaviour Uncover requirements thru process decomposition: What does the business do? What do people do? What must be automated or supported by creating and using data? Define end-to-end processes which are triggered by events and produce results Design the structure Design the capability Considering non-functional requirements such as flexibility and performance Define actors/components needed to perform the processes Function Capability view Data Entity Atomic Activity Org Unit Organisation view App Role Actor Applicat n People view Technol gy

Processes and Techniques

Methods (AM) Processes and Techniques Noting those in Architect training It is illegal to copy, share or show this document (or other document published at http://avancier.co.uk) without the written permission