Software Architecture

Size: px

Start display at page:

Download "Software Architecture"

Anne Wilkerson
6 years ago
Views:

1 Ingo Arnold Department Computer Science University of Basel Introduction Software «HR System» Case Study

2 HR System Case Study Case Study HR-System 2 (C) by Ingo Arnold IT HR System

3 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 0 HR System Case Study Introduction 1 Initiate the Project 2 Define the Enterprise Context 3 Refine Principles and Requirements 4 Develop Alternatives Initiation #1 #2 #3 #4 #5 #N Transition & Operation 3 (C) by Ingo Arnold IT HR System

Introductory Notes Roles and Disciplines Technology Architect Security Architect Project Manager Enterprise Architect Oversees the overall solution architecture (top-2-bottom and end-2-end).

Technology Architect Specialized Architect who is responsible for engaging with the and to come up with an operational enabling architecture to underpin application components.

4 Introductory Notes Roles and Disciplines Technology Architect Security Architect Project Manager Enterprise Architect Oversees the overall solution architecture (top-2-bottom and end-2-end). Engages specialized architects roles on a need-basis. Technology Architect Specialized Architect who is responsible for engaging with the and to come up with an operational enabling architecture to underpin application components. Security Architect Specialized Architect who is responsible for the security related concerns of the overall IT solution. Similar roles exist who specialize in fields like availability, or extensibility Project Manager Responsible for managing the overall project throughout its life-cycle. Focusses on resources, timelines, budget, scope and engages with. Enterprise Architect Has a portfolio and strategic planning point of view onto IT platforms of a broader domain (e.g. whole Enterprise). Provides contextual input to a respective project. 4 (C) by Ingo Arnold IT HR System

5 Introductory Notes Roles and Disciplines Business Representative Business Representative Placeholder role for everything that drives a given project from a business demand and decision perspective. From business requirements to risk taking decisions this role will be engaged 5 (C) by Ingo Arnold IT HR System

6 Introductory Notes Artifact Types This deck refers to artifacts that are related to a broader set of projectrelated work-products as well as architecture-specific artifacts Project Artifact Artifact Names of artifacts will be shown at the top-right corner of a respective slide <Artifact Name> 6 (C) by Ingo Arnold IT HR System

7 Introductory Notes Process Steps Each step that we move into will quickly be explained like outlined below 7 (C) by Ingo Arnold IT HR System

8 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective Introductory Notes View Model Also each step will be positioned from an architecture view model perspective Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 8 (C) by Ingo Arnold IT HR System

9 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 0 HR System Case Study Introduction 1 Initiate the Project 2 Define the Enterprise Context 3 Refine Principles and Requirements 4 Develop Alternatives Initiation #1 #2 #3 #4 #5 #N Transition & Operation 9 (C) by Ingo Arnold IT HR System

10 Problem Statement Activity Project Manager Problem Statement Company «improvehealth» recently spotted a significant gap in their services landscape: Lacking an IT-Systemt which is possibly internet-based and provides capabilities to life-cycle manage the company s associates By closing this gap the company wants to allow their HR departement to more effectively and efficiently.. Hire new employees Engage employees (e.g. train them) throughout their life-cycle Relocate employees Fire and forget employees etc. «improvehealth» has decided to launch a project called HR System that is expected to assess this first ideas value as well as feasibility 10 (C) by Ingo Arnold IT HR System

11 Problem Statement Activity Project Manager Problem Statement A project (called HR System ) is funded, staffed, and kick-started in order to Investigate the business value (cost-benefit ratio) Plan, implement, and deploy an appropriate solution (optional) The project manager invites to a constitutional workshop... Business Representative <other groups as appropriate> Project Manager Business Representative 11 (C) by Ingo Arnold IT HR System

12 Problem Statement Result Project Manager Problem Statement During the initial workshop the team drafts a first version of a problem statement 12 (C) by Ingo Arnold IT HR System

13 Analyse Stakeholders Activity Project Manager Stakeholder Analysis Then the team analyzes concerned stakeholders like for example Business Sponsor Quality and Compliance Representative Security Expert Service Management and Operations Representative During stakeholder analysis the s ensures that architecture-significant stakeholders are taken into account significance of «something» means that Business criticality of this «something» is considered high or severe Cost of change of this «something» is anticipated high Risk of this «something» is seen as high (high probability and impact) 13 (C) by Ingo Arnold IT HR System

14 Analyse Stakeholders Result Project Manager Stakeholder Analysis After intense discussions the results of the stakeholder analysis are caputed 14 (C) by Ingo Arnold IT HR System

15 Identify Customer Needs Activity Project Manager Customer Needs A few days later the «HR System» team invites key stakeholders to a «needs & requirements gathering» workshop At this workshop stakeholders could raise their views of the problem at hand Informally express their thoughts, concerns, and demands Key of the workshop is not to capture all requirements in all details but to stipulate a discussion and gather a first impression of needs The ensures that quality aspects are sufficiently taken into account (1) stakeholders understand the impacts of needs they express to - Cost - Risks - Future evolution 15 (C) by Ingo Arnold IT HR System (1) Often these are neglected or not adequately taken into account

16 Identify Customer Needs Result Project Manager Customer Needs Customer needs are semi-formally captured at the end of the workshop 16 (C) by Ingo Arnold IT HR System

17 Identify High-Level Functional Needs Activity Project Manager High-Level Functional Needs After a first set of needs was captured the team pays special attention to Key functional needs that stakeholders expressed Key functionality and processes that the solution has to provide Quality aspects relating to these processes and which are considered crucial Goal of this step is to understand the high-level functional needs (1) that «HR System» has to meet The following process was spotted as key Business Use Cases Life-Cycle Associate process 17 (C) by Ingo Arnold IT HR System (1) High-level functional need is used as a synonym for Business Use Cases here

18 Identify High-Level Functional Needs Result Project Manager High-Level Functional Needs The Supplier-Input-Process-Output-Consumer (SIPOC) technique (1) is used to capture the schema of the «HR Life-Cycle Management» process 18 (C) by Ingo Arnold IT HR System (1) Alternatively «Use Case» techniques could have been used here

19 Project Plan Activity Project Manager Project Plan A presentation to the «HR System» project s steering board is planned for tomorrow and the Project Manager has to present first results A project charter is drafted, which already includes a description of Underlying business needs Project s intended scope Business benefits, as well as impact of not doing Roles and responsibilities 19 (C) by Ingo Arnold IT HR System

20 Project Plan Result Project Manager Project Plan 20 (C) by Ingo Arnold IT HR System

21 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 0 HR System Case Study Introduction 1 Initiate the Project 2 Define the Enterprise Context 3 Refine Principles and Requirements 4 Develop Alternatives Initiation #1 #2 #3 #4 #5 #N Transition & Operation 21 (C) by Ingo Arnold IT HR System

outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the

22 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 22 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 22

23 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 23 (C) by Ingo Arnold IT HR System

24 Define EA Context Context Step 1: Enterprise Context Objective Roles Understand project and envisioned solution within a company s broader Enterprise and Domain context Analyse impacts and changes to the As-Is Enterprise architecture landscapes based on envisioned solution s future shape Understand gaps, overlaps, deficiencies, strengths of As-Is Enterprise architecture context regarding Capabilities Services Processes Information Applications Technologies -, Business Analyst, Enterprise Architect 24 (C) by Ingo Arnold IT HR System

25 Define EA Context Context Enterprise Architect 25 Very early in the project the «HR System» has to Understand the anticipated solution s broader enterprise architecture (1) context Understand an organization s standards, policies, and constraints The enterprise architecture assessment is based on the EA viewpoints Business (Capabilities and Processes) Information (Information and Data Structures) Application (Applications and their functionality) Technology (Technology platforms hosting applications) Outcomes of such an assessment could for example be Something is missing and not existing today (gap) Something is available but not perfectly fitting (extension, adjustment) Something is available and perfectly fitting (reuse) Several solutions already exist (overlap potential for decomission) (C) by Ingo Arnold IT HR System (1) «Enterprise» may refer to the architecture of an entire enterprise, the architecture of an entire sub-organization, the architecture of a selected domain (e.g. Network, CRM)

26 Define EA Context Activity Enterprise Architect During the capabilities assessment (1) the detects «HR Capabilities» are not available, yet «Id-Management» capabilities already exist During the application assessment the detects «HR Hiring policies» and «IAM platform» systems already exists «HR System» does not exist yet The performs similar assessments for Information Technology 26 (C) by Ingo Arnold IT HR System (1) Results of the EA assessments are outlined on the following slides

27 Define EA Context Result Enterprise Architect Business Capabilities Context 27 (C) by Ingo Arnold IT HR System

28 Define EA Context Result Enterprise Architect Application Context 28 (C) by Ingo Arnold IT HR System

29 Define EA Context Result Enterprise Architect Data Context 29 (C) by Ingo Arnold IT HR System

30 Define EA Context Result Enterprise Architect Technology Context 30 (C) by Ingo Arnold IT HR System

31 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 0 HR System Case Study Introduction 1 Initiate the Project 2 Define the Enterprise Context 3 Refine Principles and Requirements 4 Develop Alternatives Initiation #1 #2 #3 #4 #5 #N Transition & Operation 31 (C) by Ingo Arnold IT HR System

32 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 32 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 32

33 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 33 (C) by Ingo Arnold IT HR System

34 Refine Principles and Requirements Context Step 2: Refine Principles and Requirements Objective Roles This step is about generating and documenting a common understanding of what is expected and possible under the given conditions, taking into account all factors driving the architecture. Describe the quality attributes of the Computer System, and the constraints that the solution must satisfy to deliver the business goals, objectives, or capabilities. Assess sizing, cost, and viability of the proposed Computer System, which is very much driven by given non-functional requirements. Crucial within this step is to differentiate those requirements that are architecture significant from the ones that are not. -, Business Analyst, Enterprise Architect 34 (C) by Ingo Arnold IT HR System

35 Refine Principles and Requirements Context What happened so far Project Manager A first cut of Needs & Requirements had already been captured 35 (C) by Ingo Arnold IT HR System

36 Refine Principles and Requirements Context What happened so far (continued) Project Manager High-level functional needs were captured in the form of SIPOCs 36 (C) by Ingo Arnold IT HR System

37 Refine Principles and Requirements Context A SIPOCs main process steps indicate System Use Case candidates Hire Engage Fire Forget Project Manager 37 (C) by Ingo Arnold IT HR System

38 Refine Principles and Requirements Activity The creates a Use Case Overview diagram that Is based on the spotted Use Case candidates May further be based on - Needs that were captured in the «Needs & Requirements» session - Reference architectures Provides a very comprehensive overview of targeted functionality (1) Includes a list of Actors that are associated to targeted functionality Outlines dependencies that may exist among use cases Serves as a basis to conduct discussions with stakeholders in order to - Discuss and agree on completeness, correctness and relevance of functional vision - Define priorities with regards to standing up the system incrementally 38 (C) by Ingo Arnold IT HR System (1) Use Cases express functional needs / requirements

39 Refine Principles and Requirements Result System UC Overview 39 (C) by Ingo Arnold IT HR System

40 Refine Principles and Requirements Result A crucial Use Case is detailed out further right after the functional scope had been determined: «HR Life-Cycle Manage Person» 40 (C) by Ingo Arnold IT HR System

41 Refine Principles and Requirements Activity The will elaborate Use Case specific non-functional needs separately when further investigating respective Use Cases System-wide non-functional needs however must be managed as well The s ensures that system-wide non-functional needs are Captured Discussed Prioritized Tracked & traced The pays attention only to those requirements (functional as well as non-functional) that are assessed as architecture significant 41 (C) by Ingo Arnold IT HR System

42 Refine Principles and Requirements Result First sketch of significant non-functional requirements 42 (C) by Ingo Arnold IT HR System

43 Refine Principles and Requirements Activity Requirements express what an organization wants and needs Constraints however rather express crash barriers which determine a frame within which an organization is striving to meet its own needs Constraints Express framing conditions which a solution but also a project has respect Distinguish between organizational and technical constraints Usually have an impact on solution design and approach 43 (C) by Ingo Arnold IT HR System

44 Refine Principles and Requirements Result The «HR System Card» team has identified the following constraints 44 (C) by Ingo Arnold IT HR System

45 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 0 HR System Case Study Introduction 1 Initiate the Project 2 Define the Enterprise Context 3 Refine Principles and Requirements 4 Develop Alternatives Initiation #1 #2 #3 #4 #5 #N Transition & Operation 45 (C) by Ingo Arnold IT HR System

46 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 46 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 46

47 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 47 (C) by Ingo Arnold IT HR System

48 Develop Alternatives Context Step 3: Develop Alternatives Objective Roles Based on the driving factors that were identified in the previous step and taking into account the architecture context, this step supports the identification of architecture candidates which could potentially cope with the problem at hand Broaden the view to not overlook appealing but exceptional approaches to solve the actual business problem Create holistic information basis to be able to take sufficiently broad as well as grounded preferred solution -decision Document the alternative selection process so that it can be communicated to different stakeholder groups -, Business Analyst, Enterprise Architect 48 (C) by Ingo Arnold IT HR System

Develop Alternatives Context People, groups, whole organizations have a tendency to follow their own conditioning To break such conditioning and habits (at least counter balance them) is the

49 Develop Alternatives Context People, groups, whole organizations have a tendency to follow their own conditioning To break such conditioning and habits (at least counter balance them) is the key purpose of the «develop architecture alternatives» step «Many roads lead to rome» is true not just for rome but for all other problems that seek a solution 49 (C) by Ingo Arnold IT HR System

50 Develop Alternatives Activity The «HR System» team meets in order to develop alternative architecture approaches to creating the required solution The team uses the following quite helpful technique to systematically develop solution alternatives 1. Draw a topological sketch of the envisioned system s building blocks 2. Traverse all building blocks and determine dimensions that span alternatives - WHAT Vertical (data center, devices, communication stack, application middleware, app,..) Horizontal (break-down of components, alternative COTS products, architecture style,..) - WHO Plan ownership (internal, strategic partner,..) Build ownership (internal, strategic partner,..) Run ownership (internal, strategic partner,..) 50 (C) by Ingo Arnold IT HR System

51 Develop Alternatives Activity The team uses the following quite helpful technique to systematically develop solution alternatives (continued) 2. Traverse all building blocks and determine dimensions that span alternatives - WHERE Geography (global, regional, local) - HOW Security Availability Performance Extensibility Maintainability & Operability 3. Define aspirational forces along architecture principles, standards & strategic directions 4. Pick «thinkable» combinations along spotted dimensions and scales 5. Look at each of these combinations as an architecture alternative candidate and investigate them further 51 (C) by Ingo Arnold IT HR System

52 Develop Alternatives Activity 1. Draw a topological sketch of the envisioned system s building blocks 52 (C) by Ingo Arnold IT HR System

53 Develop Alternatives Activity 1. Draw a topological sketch of the envisioned system s building blocks 53 (C) by Ingo Arnold IT HR System

54 Develop Alternatives Activity 1. Draw a topological sketch of the envisioned system s building blocks 54 (C) by Ingo Arnold IT HR System

55 Develop Alternatives Activity 1. Draw a topological sketch of the envisioned system s building blocks 55 (C) by Ingo Arnold IT HR System

56 Develop Alternatives Activity Alternative «develop application» 4. Pick «thinkable» combinations along spotted dimensions WHAT Java Swing Application WHO Plan, Build: <Company> Run: Ops. Vendor WHERE Global / Internet HOW Security: PIN (1-factor) Availability: local caching Extensibility: future UI functions WHAT Java Swing Application JSDK Release 6.x WHO Plan, Build: <Company> Run: Ops. Vendor WHERE Global / Intranet HOW Security: gold cert-based Availability: Server Image Extensibility: country-specific roll-out WHAT Java Swing Applet Standard http-ua with JSDK Release 6.x plug-in WHO Plan, Build: Ops. Vendor Run: <Company> WHERE Global / Internet HOW Security: silver cert-based Availability: local DB Extensibility: future UI functions, future reports 56 (C) by Ingo Arnold IT HR System

57 Develop Alternatives Activity Alternative «COTS» 4. Pick «thinkable» combinations along spotted dimensions WHAT SAP HR Admin Module WHO Plan, Build: SAP Run: Ops Vendor WHERE Global / Internet HOW Security: SAP SCN Availability: SAP caching Extensibility: SAP release path WHAT SAP HR Core System SAP NetWeaver WHO Plan, Build: SAP Run: Ops. Vendor WHERE Global / Intranet HOW Security: SAP Security Availability: SAP availability Extensibility: country-specific rollout WHAT SAP self-service module WHO Plan, Build: SAP Run: Ops. Vendor WHERE Global / Internet HOW Security: SAP SCN Availability: local SAP DB Extensibility: future functions, future reports 57 (C) by Ingo Arnold IT HR System

58 Develop Alternatives Activity 5. Look at each of these combinations as an architecture alternative candidate and investigate them further Develop Application SAP-based COTS Solution <further alternatives> <HR Admin UI> Java Swing Application Security: PIN (1-factor) Availability: local caching Extensibility: future UI functions <HR Admin UI> SAP HR Admin Module Plan, Build: SAP Run: Ops Vendor <HR Admin UI>.. <Associate Self-Service UI> Java Swing Applet Standard http-ua with JSDK Release 6.x plug-in Plan, Build: Ops. Vendor Run: <Company> <HR System (Core) Platform> Java Swing Application JSDK Release 6.x Plan, Build: <Company> Run: Ops. Vendor <Associate Self-Service UI> SAP self-service module Plan, Build: SAP Run: Ops. Vendor Security: SAP SCN Availability: local SAP DB <HR System (Core) Platform> SAP HR Core System SAP NetWeaver Plan, Build: SAP Run: Ops. Vendor <Associate Self-Service UI>.. <HR System (Core) Platform>.. 58 (C) by Ingo Arnold IT HR System

59 Develop Alternatives Activity This alternatives brainstorming / developing session was intelectually challenging and quite intense for the team The developed alternatives cover broad ranges regarding Technology choices (application middleware, devices, communication stacks) Accountability and ownership of plan, build, and run stages Hosting strategy Strategies to cope with security, availability, extensibilty Results from an end-user perspective ( usability) The team explores all three alternatives further and along System Context Application, Data, Technology Cross-Cutting Perspectives 59 (C) by Ingo Arnold IT HR System

60 Develop Alternatives Activity During this quick exploration of each alternative s architectural impacts and effects, main focus is given to Requirements coverage - Functional - Non-Functional Cost Risk 60 (C) by Ingo Arnold IT HR System

61 Develop Alternatives Activity Alternative «develop application» As a first alternative the team choses to look at «develop application» The team further decided to develop a solution skeleton very quickly 61 (C) by Ingo Arnold IT HR System

62 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 5 Develop System Context These steps are repeated (time-boxed) for all spotted Alternatives Develop Vision Develop Application Develop Data 9 Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 62 (C) by Ingo Arnold IT HR System

63 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 63 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 63

64 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 64 (C) by Ingo Arnold IT HR System

65 Elaborate System Context Context Step 5: Elaborate System Context Objective Roles This step describes the solution as a whole and from a black-box perspective by capturing its highest level solution structures as well as relationships which exist between these and external entities crossing the given system s boundaries. To provide an overview of interfaces to be considered in the solution design. To verify that the information flows between the system and its external factors (i.e. external systems and actors) are in alignment with the external system owners expectations and commitments. To communicate at a high level the system boundaries to respective stakeholder groups. -, Business Analyst, Enterprise Architect 65 (C) by Ingo Arnold IT HR System

66 Elaborate System Context Activity Alternative «develop application» A System Context represents the entire system under design as a single element System Context identifies the information and control flows that cross the system boundary from / to from external entities (e.g. human actors, external systems) The System Context highlights important aspects of the system such as: External events to which the system must respond. Events the system generates and that affect external entities. Data that the system receives from external systems Data produced by the system and provided to external systems 66 (C) by Ingo Arnold IT HR System

67 Elaborate System Context Activity Alternative «develop application» The following system context diagram is sketched by the team 67 (C) by Ingo Arnold IT HR System

68 Elaborate System Context Activity Alternative «develop application» Next step from here is to white-box-zoom into the system The team pursues this step by sketching a high-level Vision for the system 68 (C) by Ingo Arnold IT HR System

69 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 5 Develop System Context These steps are repeated (time-boxed) for all spotted Alternatives Develop Vision Develop Application Develop Data 9 Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 69 (C) by Ingo Arnold IT HR System

70 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 70 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 70

71 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 71 (C) by Ingo Arnold IT HR System

72 Elaborate Vision Context Step 6: Elaborate Vision Objective Roles Where the System Context provides a black box view on the system(s) in scope of the solution, the Vision provides a very highlevel first white box view on it. Primary focus of this step is to provide the Architect a handy tool for communicating with a broad variety of different stakeholder groups. The Vision viewpoint combines multiple aspects which are captured in a more focussed fashion throughout the following steps. Be able to communicate a comprehensive overview of the envisioned architecture s future shape, its advantages, functional coverage, implications, and consequences to different stakeholder groups (C) by Ingo Arnold IT HR System

73 Elaborate Vision Context Alternative «develop application» The system context shows HR System from a black-box point of view As a next step the HR System sketches an overview of the envisioned solution s... corner stone elements ( different types can be shown since purpose is to provide a one-glance overview rather than a distinct viewpoint, only) relationships among these corner stone pillars of HR System An Overview Diagram might already include Candidate Subsystems Components Nodes Connections Data Stores Users External Systems Crucial architecture styles and patterns that the system is envisioned to be built upon 73 (C) by Ingo Arnold IT HR System

74 Elaborate Vision Activity Alternative «develop application» The following white box view is sketched by the team 74 (C) by Ingo Arnold IT HR System

75 LCM backbone process County- Specific Complements Elaborate Vision Activity Alternative «develop application» An important need the system is expected to meet is given an extra thought as well as depicted by the team, accordingly As a key feature the application skeleton has to support - standardization on the level of the LCM back-bone process - combined with flexibility and adaptability on the level of country-specific complements to the LCM back-bone process hire use fire forget HR System (Core) 75 (C) by Ingo Arnold IT HR System

76 Elaborate Vision Activity Alternative «develop application» Next step for the HR System project team is to zoom into each of the following architecture viewpoints Application Data Arcihtecture Technology 76 (C) by Ingo Arnold IT HR System

77 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 5 Develop System Context These steps are repeated (time-boxed) for all spotted Alternatives Develop Vision Develop Application Develop Data 9 Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 77 (C) by Ingo Arnold IT HR System

78 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 78 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 78

79 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 79 (C) by Ingo Arnold IT HR System

80 Elaborate Application Context Step 7: Elaborate Application Objective Roles In this step the architect develops a model, which depicts the solution s core functional building blocks (i.e. Application Components) as well as their inter-dependencies. Beyond the solution s functional decomposition, this step also elaborates the realization of use cases which were captured by use case descriptions in the functional requirements step. Identify potential or final Application Components that will be responsible to provide the required functionality. Outline the relationships that exist between Application Components (C) by Ingo Arnold IT HR System

81 Elaborate Application Context Alternative «develop application» This step includes a description of the Computer System s Functional elements Their main responsibilities Their interfaces and primary interactions among themselves The Application is described based on Functional Structure Model (modeling static aspects) Functional Behavior Model (modeling dynamic/collaborative aspects) First orientation for stakeholders regarding Functional scope Functional decomposition Functional cooperation and interaction 81 (C) by Ingo Arnold IT HR System

82 Elaborate Application Context Alternative «develop application» What happened so far A use case overview diagram as well as a first UC had been sketched already 82 (C) by Ingo Arnold IT HR System

83 Elaborate Application Activity Alternative «develop application» The HR team starts from the Use Case HR Life-Cycle Manage Person in order to develop a better understanding of required application components 83 (C) by Ingo Arnold IT HR System

84 Elaborate Application Activity Alternative «develop application» As a next step the team derives a functional structure model (detailing out respective application components) 84 (C) by Ingo Arnold IT HR System

85 Elaborate Application Activity Alternative «develop application» As a next step the team derives a functional structure model (detailing out respective application components) 85 (C) by Ingo Arnold IT HR System

86 Elaborate Application Activity Alternative «develop application» As a next step the team derives a functional structure model (detailing out respective application components) 86 (C) by Ingo Arnold IT HR System

87 Elaborate Application Activity Alternative «develop application» As a next step the team derives a functional structure model (detailing out respective application components) 87 (C) by Ingo Arnold IT HR System

88 Elaborate Application Activity Alternative «develop application» For an explorative prototype the team plans a high-level UI sketch is required as well HR-System LCM Process -- Country Implementation: <the LCM log is printed here> First Name: Last Name: Add Person 88 (C) by Ingo Arnold IT HR System

89 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 5 Develop System Context These steps are repeated (time-boxed) for all spotted Alternatives Develop Vision Develop Application Develop Data 9 Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 89 (C) by Ingo Arnold IT HR System

90 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 90 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 90

91 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 91 (C) by Ingo Arnold IT HR System

92 Elaborate Data Context Step 8: Elaborate Data Objective Roles This step observes and captures key information objects as well as their inter-relationships and ownership in scope of the solution. A Data s is THE corner stone of any IT solution, and this is why an Architect must pay serious attention to this step. Any function that a solution exposes at its outside is fully based on its Data s inherent information capabilities thus stays or falls with its quality, and completeness. Describe semantics, flows, structure as well as ownership of the managed information Investigate, understand, and describe approaches to data migration - 92 (C) by Ingo Arnold IT HR System

93 Elaborate Data Context Alternative «develop application» This step describes the way that the architecture Stores Manipulates Manages Dstributes information Data is represented based on Static Data Structure Model Data Placement Model 93 (C) by Ingo Arnold IT HR System

94 Elaborate Data Activity Alternative «develop application» At this early stage the team feels sufficiently confident that crucial data structures are either made available by existing systems or that they can be established easily within the custom development engagement 94 (C) by Ingo Arnold IT HR System

95 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution 5 Develop System Context These steps are repeated (time-boxed) for all spotted Alternatives Develop Vision Develop Application Develop Data 9 Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 95 (C) by Ingo Arnold IT HR System

96 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 96 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 96

97 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 97 (C) by Ingo Arnold IT HR System

98 Elaborate Technology Context Step 9: Elaborate Technology Objective Roles Where the Application describes a solution s key functional building blocks (aka: Application Components) and their interconnections, the Technology elaborates the Application Components operational underpinnings. With the Technology an Architect creates a model of System Components and their respective inter-connections. The Architect also develops a model that explains how each of the Application Components in the Application are mapped onto one or more System Components in the Technology An Architect uses the Technology mainly to verify coverage of all non-functional requirements and quality attributes the solution is expected to have (C) by Ingo Arnold IT HR System

99 Elaborate Technology Context Alternative «develop application» Technology describes the environment into which the Computer System will be deployed captures the dependencies a Computer System has on its runtime environment captures operational nodes that underpin and host your Computer System. Examples of such operational nodes are processing nodes like workstations, or servers (e.g. WAS, WS, TxS) network nodes disk and storage nodes back-up and recovery nodes systems management related nodes security nodes persistent system nodes (aka: file servers, databases), etc. 99 (C) by Ingo Arnold IT HR System

100 Elaborate Technology Activity Alternative «develop application» The HR System team (also due to the fact that there are only 60 minutes available for the whole system to be implemented) decides to deploy all application components into my Laptop 100 (C) by Ingo Arnold IT HR System

101 Elaborate Technology Activity Alternative «develop application» The HR System team (also due to the fact that there are only 60 minutes available for the whole system to be implemented) decides to deploy all application components into my Laptop 101 (C) by Ingo Arnold IT HR System

102 Elaborate Technology Activity Alternative «develop application» The HR System team (also due to the fact that there are only 60 minutes available for the whole system to be implemented) decides to deploy all application components into my Laptop 102 (C) by Ingo Arnold IT HR System

103 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution These steps are repeated (time-boxed) for all spotted Alternatives Develop Application Develop Data Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 103 (C) by Ingo Arnold IT HR System

104 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 104 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 104

105 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision (C) by Ingo Arnold IT HR System 105

106 Elaborate Application Context Step 7: Elaborate Application Objective Roles In this step the architect develops a model, which depicts the solution s core functional building blocks (i.e. Application Components) as well as their inter-dependencies. Beyond the solution s functional decomposition, this step also elaborates the realization of use cases which were captured by use case descriptions in the functional requirements step. Identify potential or final Application Components that will be responsible to provide the required functionality. Outline the relationships that exist between Application Components (C) by Ingo Arnold IT HR System

107 Elaborate Application Context Alternative «develop application» What happened so far Application Components have been identified (Functional Structure Model) which will now be implemented by the team. (C) by Ingo Arnold IT HR System 107

108 Elaborate Application Context Alternative «develop application» What happened so far Further Application Components which support realization of the UI are required as well on an implementation level HR-System LCM Process -- Country Implementation: <the LCM log is printed here> First Name: Last Name: Add Person (C) by Ingo Arnold IT HR System 108

109 Elaborate Application Activity Alternative «develop application» The HR team creates the UI frame first (C) by Ingo Arnold IT HR System 109

110 Elaborate Application Activity Alternative «develop application» The HR team creates the UI frame first HR System implementation for enrolling a new Person has to be snapped in here (C) by Ingo Arnold IT HR System 110

111 Elaborate Application Activity Alternative «develop application» The HR team creates the UI frame first the result of which is.. (C) by Ingo Arnold IT HR System 111

112 Elaborate Application Activity Alternative «develop application» Now the HR team implements HR System (core) application components A JTextArea component needs to be looped in as the outstream channel Made abstract to provide hooks for country specific implementations Country-specific complements and implementations of *how* a Person is hired, engaged, fired, and finally forgotten about (C) by Ingo Arnold IT HR System 112

113 Elaborate Application Activity Alternative «develop application» Simples and most fundamental components come first («Person», «HiringPolicySystem») (C) by Ingo Arnold IT HR System 113

114 Elaborate Application Activity Alternative «develop application» Next the team implements the HR System s back-bone process logic (C) by Ingo Arnold IT HR System 114

115 Elaborate Application Activity Alternative «develop application» Finally two country variants are implemented («CH» and «FR») (C) by Ingo Arnold IT HR System 115

116 Elaborate Application Activity Alternative «develop application» As a final step the HR System (Core) implementation needs to be snapped into the UI yet again HR System implementation for enrolling a new Person has to be snapped in here (C) by Ingo Arnold IT HR System 116

117 Elaborate Application Activity Alternative «develop application» Toggling between country-specific implementations can now be done at run-time We started with the Implementation of HR System in CH and added a Person «Ingo Arnold» (C) by Ingo Arnold IT HR System 117

118 Elaborate Application Activity Alternative «develop application» Toggling between country-specific implementations can now be done at run-time Next we tried to enroll a Person «Pascal Bouquet» in CH but the hiring policy didn t support this (C) by Ingo Arnold IT HR System 118

119 Elaborate Application Activity Alternative «develop application» Toggling between country-specific implementations can now be done at run-time Then we toggled to the FR implementation and tried again to add «Pascal Bouquet» (C) by Ingo Arnold IT HR System 119

120 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution These steps are repeated (time-boxed) for all spotted Alternatives Develop Application Develop Data Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 120 (C) by Ingo Arnold IT HR System

121 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 121 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 121

122 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision (C) by Ingo Arnold IT HR System 122

123 Elaborate Data Context Step 8: Elaborate Data Objective Roles This step observes and captures key information objects as well as their inter-relationships and ownership in scope of the solution. A Data s is THE corner stone of any IT solution, and this is why an Architect must pay serious attention to this step. Any function that a solution exposes at its outside is fully based on its Data s inherent information capabilities thus stays or falls with its quality, and completeness. Describe semantics, flows, structure as well as ownership of the managed information Investigate, understand, and describe approaches to data migration (C) by Ingo Arnold IT HR System

124 Elaborate Data Activity Alternative «develop application» All data the Team needed so far is encoded in classes thus for the Data proportion the Team moves into tea break!! (C) by Ingo Arnold IT HR System 124

125 Case Study HR System Steps Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution These steps are repeated (time-boxed) for all spotted Alternatives Develop Application Develop Data Develop Technology Initiation #1 #2 #3 #4 #5 #N Transition & Operation 125 (C) by Ingo Arnold IT HR System

126 Development Process Context Do the right thing Do the thing right Run it right Retire it right Plan Build Operate Retire Inception Elaboration Construction Transition Idea Creation & Verification Problem understanding & precision Conceptualize adequate solution outline Implemention of conceptual solution outline Transition of implemented solution & verification Operate the solution Retire the solution Initiation 126 (C) by Ingo Arnold IT HR System #1 #2 #3 #4 #N Transition & Operation Department of Computer Sciences University of Basel 126

Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles &

127 Security Perspective Availability & Reliability Perspective Performance & Scalability Perspective Extensibility Perspective View Model Context Enterprise Landscapes & Views Requirements Principles & Constraints Application Technology Data External Viewpoint Alternatives Functional Requirements Application Infrastructure System Context Non-Functional Requirements IT-Infrastructure Vision 127 (C) by Ingo Arnold IT HR System

128 Elaborate Technology Context Step 9: Elaborate Technology Objective Roles Where the Application describes a solution s key functional building blocks (aka: Application Components) and their interconnections, the Technology elaborates the Application Components operational underpinnings. With the Technology an Architect creates a model of System Components and their respective inter-connections. The Architect also develops a model that explains how each of the Application Components in the Application are mapped onto one or more System Components in the Technology An Architect uses the Technology mainly to verify coverage of all non-functional requirements and quality attributes the solution is expected to have (C) by Ingo Arnold IT HR System

129 Elaborate Technology Activity Alternative «develop application» All components below are included in the package dev.com.novartis.hrsystem 129 (C) by Ingo Arnold IT HR System

$prod, now Source files location «C:\Users\arnolin1\workspace\Novartis\src» 130 (C) by Ingo Arnold IT HR$

130 Elaborate Technology Activity Alternative «develop application» HR System has to be moved from dev to prod, now Source files location «C:\Users\arnolin1\workspace\Novartis\src» 130 (C) by Ingo Arnold IT HR System

$«C:\Users\arnolin1\workspace\Novartis\_deployed» 131 (C) by Ingo Arnold IT HR$

131 Elaborate Technology Activity Alternative «develop application» HR System has to be moved from dev to prod, now Source files are compiled by javac compiler and into respective class-files Compilation output (i.e. class files) are put into directory «C:\Users\arnolin1\workspace\Novartis\_deployed» 131 (C) by Ingo Arnold IT HR System

132 Elaborate Technology Activity Alternative «develop application» HR System has to be moved from dev to prod, now Finally the compiled HR System is run based on the java VM (JRE) 132 (C) by Ingo Arnold IT HR System

133 Questions? 133 (C) by Ingo Arnold IT HR System

Software Life-Cycle Management

Ingo Arnold Department Computer Science University of Basel Introduction Software Life-Cycle Management IT Governance and Process Overview Lecture Introduction IT Business The Problem Complexity Complex