1. www.swassociatesint.com Independent Guidance for SOAINT Services Architecture Series: Business Service Architecture Module 3: Identifying Core Business Services

2. www.swassociatesint.com Objectives 2 Learning Objectives  To identify core business services.  To determine dependencies within the core business layer.  To define policies for the core business layer. Where we’ve been  Service-Oriented Architecture (SOA)  SOAINT Services Architecture (SSA)  Business Service Architecture  Classification  Layering Agenda  Understanding business semantics – business type model  First-cut design – one service for each core business type  Detailing and classifying types  Semantic decoupling

3. www.swassociatesint.com Recap: A taxonomy of services 3 Service differentiatingstablecontextual capability service UI process service process control process activity business utility underlying external generic implementation -leaking system utility identity presence securitydata access core business

4. www.swassociatesint.com Recap: What is a Core Business Service? Purpose  Business representation of business resource - 360° view  Information capture and retrieval  Shared across multiple processes  Common business rules 4 Similar Concepts  Entity Services  Core Services  Domain Services Examples  Employees Services  Products Services  Purchase Orders Services  Customers Services  General Ledger Services  Locations Services

5. www.swassociatesint.com Business Type Model What Are Business Types?  Tangible  Less Tangible  Collection Also Known As  Class (UML)  Entity (ERD) Diagram (UML) 5 Building Employee Training Course Raw Material Purchase Order Budget Order Line Item Line of Address Delivery Schedule Item works from * 1contains 1 * EmployeeBuilding Room -id -name -birth date -address -purpose -number -size Training Attended Customer Complaint

6. www.swassociatesint.com Implementing Joined-Up Government Using Shared Services 6 Apply for parole Citizen Portal Apply for student loan Apply for childcare Apply for student place Student Portal Justice SectorEducation Sector Social Services University ClearingFinance Education Service Bus Resource Service Student Resource Service Citizen Resource Service Application Resource Service Place Resource Service Nursery Place Resource Service Univ Place Resource Service Parole Resource Service Univ Application Resource Service Prisoner Government Service Bus Resource Service Allocation Resource Service Identity

7. www.swassociatesint.com To Support Shared Services, We Need Shared Concepts 7 APPLICATION PRISONERSTUDENT UNIVERSITY APPLICATION CITIZEN PAROLE APPLICATION LOAN APPLICATION CHILDCARE APPLICATION ****

8. www.swassociatesint.com Canonical Business Type Model  The canonical business type model for TaxPayer provides a single semantics for all references to taxpayers across all systems and interfaces.  For Tax Authority  Interactions with taxpayers  Interactions about taxpayers with other agencies and third parties  For TaxPayer  Interactions with Tax Authority  Interactions with other agencies and third parties that may affect tax 8 Tax AuthorityTaxPayer TaxPayer’s Agent Commercial Enterprise External Tax Authority Public Sector Agency

9. www.swassociatesint.com Why Business Type Model? The business type model should be  Strategic, High-Level  Canonical  Industry-Standard (if possible) The business type model should yield  Stable, Enduring, Architectural  Common Basis for Shared Services  Common Basis for Interoperability and Joined-Up Management 9

10. www.swassociatesint.com Business Type Modeling  Draw business type model  Cluster into domains  Produce more detailed model for selected domains  Divide business types into categories  Core  Detailing  Classifying  Review core business types  Increase generalization?  Reduce coupling? 10 Domain Detailing Type Classifying Type Core Business Type ? ?

11. www.swassociatesint.com Core, Detailing and Classifying Types Core Business Type  Stand-alone, independent Detailing Type  Dependent  Purpose: detail Classifying Type  Category or group  Purpose: differentiation 11 Company Location Type * 1 belongs to Training Course Category * 1 assigned to CustomerAddress 1 1 Lives at

12. www.swassociatesint.com Business Type Model produces Core Business Services 12 Domain Detailing Type Classifying Type Core Business Type «service» OrdersService «service» CustomersService «service» ProductsService

13. www.swassociatesint.com Simple Example 13 Manuf- acturing Data Product Group Product Price Order Item OrderAddress Line History Customer 1 1 1 1 1 1 1 1 1 1..* * * * * * 0..1 1..* {id} {sa-id} Business types Associations Identifier (attribute) Identifier (association)

14. www.swassociatesint.com Categorize Business Types 14 Manuf- acturing Data Product Group Product Price Order Item OrderAddress Line History Customer 1 1 1 1 1 1 1 1 1 1..* * * * * * 0..1 1..* {id} {sa-id} independent type with laundry ticket “laundry ticket” independent type with “laundry ticket”

15. www.swassociatesint.com Assign Detailing Business Types 15 Manuf- acturing Data «core» Product «classifying» Product Group Product Price Order Item «core» Order Address Line History «core» Customer 1 1 1 1 1 1 1 1 1 1..* * * * * * 0..1 1..* {id} Associating Type

16. www.swassociatesint.com Placing Associating Types Guidelines 1. Mandatory association 2. Composition association 3. Identifying association 4. Name extension 5. Modification extension 16 Product Order Item Order 1 1 1..* * {id}

17. www.swassociatesint.com Service Design Guidelines Service Responsibilities  Operations  CRUD  Queries: list, search, detail  Persistent data storage  may be delegated  Process-independent business rules  Validation  Data integrity  lifecycle state changes Service Dependencies  Delegation  Data storage and retrieval delegated to lower layers  Cross-reference  A service may reference and update data owned by other services 17 … subject to architectural and design policy …

18. www.swassociatesint.com Propose Core Business Services and Dependencies 18 Manuf- acturing Data «core» Product «classifying» Product Group Product Price Order Item «core» Order Address Line History «core» Customer 1 1 1 1 1 1 1 1 1 1..* * * * * * 0..1 1..* {id} «service» CustomersService «service» OrdersService «service» ProductsService

19. www.swassociatesint.com Why base Core Business Services on Core Business Types?  Generalize by adding attributes for future use  Generalize – instances could be streets, parks, bridges, residences in future  Generalize – so non- employee data can be supported by this service in future 19 code description unit type retail price per unit cost price per unit Product name location description Building id name address start date birth date Employee code description unit type retail price per unit cost price per unit current state code note 1 note 2 Product name position description Location name category code address birth date Person id start date Employee

20. www.swassociatesint.com Service Independency – an Architecture Policy Decision How much dependency? None (Independent)  Simple operations – limited functionality  High reuse  Complexity in consuming service / application Limited (Acyclic)  More powerful operations  Easier to use  May be more complex to build and maintain Full (Cyclic)  Highly complex  Low reuse 20 «service domain» Supply Chain Products Service Orders Service Customers Service our example assumes this policy

21. www.swassociatesint.com Layered Business Service Architecture 21 Aggregate Risk Profile Manage Capital Adequacy Business Loan Application Risk Service Compliance Loans Credit Check Regulatory Framework Standard Calculations Customers Product Rules Engine Products Retail Loan Application Customer Financial Portfolio Visibility PROCESS LAYER CAPABILITY LAYER CORE BUSINESS LAYER UTILITY LAYER

22. www.swassociatesint.com Summary Business Type Model (High Level) Scope  Enterprise or Domain Content  Primary types identified and described  Primary associations  Identifying and differentiating attributes 22 Business Service Architecture Identify Service Business Type Model (Detailed) Scope  Domain or Project Content  All types identified and described  All associations  All attributes Rich Service Specification Specify Service