Building Systems for Today’s Dynamic Networked Environments

1. Building Systems for Today’s Dynamic Networked Environments A Methodology for Building Sustainable Enterprises in Dynamic Environments through knowledge sharing, collaboration and innovation Emphasis is on service design to support evolution Create initial infrastructure and adapt to evolving system Provide services for users to compose processes from collaborative services to support large scale collaborative systems. New User Requirement Support evolution Support complex Take a holistic approach Focus on business architecture

2. The challenge of complexity in the business environment Emphasis on knowledge creation Emphasis on innovation Collaboration to innovate and share knowledge within the business process Knowledge management integrated into the business process Create new spaces for innovation Design must provide the social structures to facilitate knowledge creation and sharing within the business process Social structure Learning Knowledge capture Knowledge sharing Provide ways to create new knowledge through social innovation The goal is to develop a methodology to support systems in complex environments

3. Creating a Business Network to Manage Evolution Communities self organize but coordinate activities with other communities through infrastructure Community 2 Community 3 Community 1 Sharing knowledge to act locally while thinking globally Community 4 Software to support knowledge sharing between people Finds neighbors or similar groups Establishes contacts Coordinator assists to make connections

4. Overview 1: Main Objective Focusing on large scale collaboration to support knowledge sharing and collaboration New approach to requirements capture for complex evolving systems – Incomplete and emerging requirements Managing in complex environments Bringing together people and knowledge to address emerging issues Managing community sustainability within the business system Creating new relationships as system emerges User driven emergence Ultimate goal – User operates on model with changes made on system

5. Overview 2: Who is the User Knowledge workers Requires knowledge to make response Requires knowledge to make response Access to transaction processes How to Analyze (Architects setting up initial System) User process driven by events that need responses New foundation for evolution Manage complexity How to Build (Architects set up infrastructure users evolve system as needed) Infrastructure to support user driven evolution

6. Overview 3: Encouraging emergence and innovationImproving quality Changing model during execution Supporting emergence through Learning Relationships Feedback Control elements Methods are needed to provide the structures that encourge innovative behaviour.

7. Overview 4: Use a method engineering approach Select perspectives Select method for defining perspectives Select modeling tools for each perspective Select analysis method

8. Collaborating network of service suppliers Make arrangements to create a service kind involving a subset of clients and customers Discusses issues of general requirements Supplier network Make arrangements and create contracts. Agree on costs and delivery schedules Customer network Maintain contact and report on progress. Maintain contact and report on progress. Emerging group Ways organizational units interact AN OVERVIEW OF THE METHOD Organizational Model The structure of business activities Ways people interact Ways we learn and share knowledge Business Activity Model Enterprise Social Network Team member Knowledge Model Reviewer c1 Team member Coordinator t1 Reviewer a3 Idea generation Evaluation t2 a2 a1 t3 t4 Ideas Evaluation Coordinator Idea generation team Assessor team I I I I Who do I work with on this I I I have to improve my practices I I I must learn about my clients What is the best tool for the problem Choosing perspectives and modeling methods Workspaces

9. Process Recording Model Constructs Structure of Site Overview 3. Evolving the system 1. Model description 2. Design process 1.1 Organizational arrangements Business activities 2.1 Define intention 1.2 Business activities Social network 2.2 Business architecture 1.3 Social network Knowledge 2.3 Select technical infrastructure Guidelines Patterns 1.4 Knowledge 1.5 Services

10. 1.0 Initial Model DescriptionCreating the Infrastructure Defining large collaborative systems requires models that show the interaction between a number of perspectives. Constructing a business architecture for large scale collaboration is approached from a number of perspectives Combine models for each perspective to create a holistic model Organizational structure Social Knowledge Organization Business activity

11. 1.1 Organizational Model Our unit Their unit Identifies client requirements Identifies client requirements Identifies client requirements Enterprise Relationships Role Artifact Type Subactivity/Service Scenario External information source Artifact

12. Unit Unit 1.1.1 Choose organizational model Responsibility Responsible for material acquisition Concepts Organizational unit Organizational activity and responsibility Interactions between organizations Interaction Negotiates contracts UML Model UNITS INTERACTIONS Unit-name Interaction-id Unit-responsibility Unit-1 Unit-interactions Unit-2

13. 1.2 Business Activity Model Defining services needed in the organizations Business activity Business activity Role Artifact Type Subactivity/Service Scenario TYPE: Transactive Integrative Collaborative Expert Artifact Mission statement

14. 1.4 Knowledge Focus on learning, innovation and setting up relationships Here are some ideas I must learn about my clients I have to improve my practices Who do I work with on this Is this consistent with vision

15. 1.4.1 Recording information

16. Method 2 Method 1 Method 5 Method 3 Method 4 2.0 Design Process: Overview Design activities 2.1 Methods to define intention 2.2 Methods to design the business architecture 2.3 Methods to choose services 2.4 Methods for implementation Guideline 1 A method oriented approach Methods classified by stage Guidelines provided for each stage Methods focus on perspectives Methods chosen as needed in the design activity Use guidelines in methods Guideline 2

17. Identify stakeholder needs Define scope Impact Draw application type Define knowledge requirements 2.1 Defining Intentions 2.1.1 Requirements guidelines for emergence Innovation metaphors 2.1.2 Impact guidelines Defining the intention Application types General infrastructure also indentified here?

18. 2.1.1 Process for intentions Guidelines Guidelines for identifying trends Client (society) values Industry, environment and economic trends New products likely to emerge New services Enter goal What is the industry What are industry trends What are the sources of trends Enter specific goals Trends and their source What new capability is needed Who are the organizational units What are objectives What do they produce What knowledge do they need (learn) What expertise is needed Where is the expertise How do they interact and collaborate Any assumptions Goals Guidelines for defining emergence What new knowledge do you expect later Which way is the industry going What new skills will be needed Business unit objectives Guidelines for work relationships How do you expect to be working with clients, How do you expect to be interacting with co-workers Knowledge needs Guidelines for organizational units Depends on industry Interactions

19. Collaboration patterns Define scope and goals Culture theories Create new role structures Define business activities Define application type Scenarios Draw enterprise social network Define knowledge requirements Knowledge enablers 2.2 Design methods for business architecture design Innovation metaphors Business architecture design Communities

20. 2.2.1 Identify business activities Look at goal What activities – sketch activity Which activities get trends How are trends distributed Where is knowledge captured and created Which roles are involved in knowledge capture What needs to be done – choose activity roles What knowledge is needed and created and expertise developed What kinds of changes need to be catered for What are the interactions – sketch ESN How is coordination between units What are the process innovations What services do roles need Where is the responsibility for change Guidelines What are the business activities What are potential changes Guidelines for defining emergence Identify potential directions in knowledge creation. Where does it come from? Does it need to be created? Choice of ESN structures

21. 2.2.2 Recording information

22. 2.3 Service Description Features of each service Role 2 responsibility Role 1 responsibility Interaction between roles X1 Individual occupying role X2 Individual occupying role Role 1 Role 2 Support for interactions Access to databases

23. 2.3.1 Enterprise Social Network (ESN) Options – reactive look at current networking and adapt proactive create an ESN Role Responsibility Interaction Interaction type Role 2 responsibility Role 1 responsibility Interaction between roles X1 Individual occupying role X2 Individual occupying role Role 1 Role 2

24. 2.3.2 Choose modeling construct Concepts Activity Role Artifact Lightweight Roles Activity-name Artifact UML ARTIFACTS ACTIVITIES ROLES Role-name Activity-name Role-name Unit-1 Artifact Unit-1 Unit-2 Roles Unit-2

25. Lightweight workspaces Define scope Social software Choosing social software Design workspaces Define application type Scenarios Select infrastructure Define interactions Available databases 2.4 Service Infrastructure Design Innovation metaphors Service design

26. 2.3.1 Identify technical services Guidelines What services are needed to capture trends What services are needed to evaluate trends and their impact What services are needed for knowledge creation What services are needed for role interactions What are the business activities What are potential changes Matching service to technology