Micro Focus Cloud Assessment 1.01 Concept Guide · Legalnotices Warranty TheonlywarrantiesforSeattleSpinCo,Inc.anditssubsidiaries(“Seattle”)productsandservicesareset

Cloud AssessmentSoftware Version: 1.01

Windows and Linux Operating System

Concepts Guide

Document Release Date: January 2018

Software Release Date: January 2018

Legal notices

WarrantyThe only warranties for Seattle SpinCo, Inc. and its subsidiaries (“Seattle”) products and services are setforth in the express warranty statements accompanying such products and services. Nothing herein shouldbe construed as constituting an additional warranty. Seattle shall not be liable for technical or editorial errorsor omissions contained herein. The information contained herein is subject to change without notice.

Restricted rights legendConfidential computer software. Except as specifically indicated, valid license from Seattle required forpossession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software,Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S.Government under vendor's standard commercial license.

Copyright notice© Copyright 2017 EntIT Software LLC, a Micro Focus company.

Trademark noticesAdobe™ is a trademark of Adobe Systems Incorporated.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Documentation updatesThe title page of this document contains the following identifying information:

l Software Version number, which indicates the software version.l Document Release Date, which changes each time the document is updated.l Software Release Date, which indicates the release date of this version of the software.

To verify you are using the most recent edition of a document, go tohttps://softwaresupport.hpe.com/manuals.

To check for new versions of software, go to https://www.hpe.com/software/entitlements. To check for recentsoftware patches, go to https://softwaresupport.hpe.com/patches.

You will also receive updated or new editions if you subscribe to the appropriate product support service.Contact your Micro Focus sales representative for details.

For information and details about the products, services, and support that Micro Focus offers, contact yourClient Director.

SupportVisit the Micro Focus Software Support Online web site at https://software.microfocus.com/en-us/software/customer-technical-support-services.

This web site provides contact information and details about the products, services, and support that MicroFocus offers.

Micro Focus online support provides customer self-solve capabilities. It provides a fast and efficient way toaccess interactive technical support tools needed to manage your business. As a valued support customer,you can benefit by using the support web site to:

l Search for knowledge documents of interestl Submit and track support cases and enhancement requestsl Manage software licensesl Download new versions of software or software patchesl Access product documentation

Concepts Guide

Cloud Assessment (1.01) Page 2 of 34

https://softwaresupport.hpe.com/manuals

https://www.hpe.com/software/entitlements

https://softwaresupport.hpe.com/patches

https://softwaresupport.hpe.com/

https://softwaresupport.hpe.com/

l Manage support contractsl Look up Micro Focus support contactsl Review information about available servicesl Enter into discussions with other software customersl Research and register for software training

Most of the support areas require you to register as a Passport user and sign in. Many also require a supportcontract.

To register for a Passport ID, go to https://cf.passport.softwaregrp.com/hppcf/login.do.

To find more information about access levels, go tohttps://softwaresupport.hpe.com/web/softwaresupport/access-levels.

To check for recent updates or to verify that you are using the most recent edition of a document, contactyour Client Director.

Concepts Guide


https://cf.passport.softwaregrp.com/hppcf/login.do

https://softwaresupport.hpe.com/web/softwaresupport/access-levels

Contents

Chapter 1: Concepts 6

Chapter 2: Document Map 9

Chapter 3: Build Enterprise Model Describing both Business and IT 10Data Import and Export 10

Product Integration 11

Business and IT Alignment 12Enterprise Portfolio Management and Business Alignment 12Business Alignment Assessment 13Enterprise Architect and Solution Architect Roles 13Business Capability 14

Business Capabilities and StructureMaps 15Business Capability Investment Analysis 16Business Capability Risk Map 16

Chapter 4: Define and Enforce Standardization of IT assets 18Lifecycle Overview 18

Artifact Validation 19

Chapter 5: Design and Roadmap IT Transformations 20Architecture Transformation 20

Shortcut Relationship 20

Survey Overview 22

Cloud Assessment 23

Cloud Transformation 23

Model Viewpoint 24

Impact and Dependency Analysis 25

RoadMap Implementation 26

Chapter 6: FinPlanner - Case Study 28FinPlanner Solution Design 28

Modeling Business Architecture 29Defining Core Business Functions 29

Concepts Guide


Defining Application Services Integration 30

Modeling Application Architecture 31

Modeling Technology Architecture 31

FinPlanner Initial Installation and Setup 31

FinPlanner Sparx EA Project 32

FinPlanner Summary 33

Concepts Guide


Chapter 1: ConceptsCloud Assessment is a software product that is an amalgamation of the IT infrastructure of an organizationaligned to its business strategies, and is based on Archimate 2.1 and TOGAF standards which defines a fullset of architecture elements.

Cloud Assessment plans and drives IT transformation roadmaps by mapping the overall IT landscape withbusiness outcomes. Using proven enterprise architecturemethods it accelerate respond to changing ofbusiness needs and identifies and stops wastage of resources.

Micro Focus Cloud Assessment (Cloud Assessment) logically constructs enterprise architecturemodelsaligned with projects, and enables you to capture and use information from various tools and across multiplelocations. You can use Cloud Assessment tools to manage your architecturemodel and establish a solidbaseline for making informed decisions about your IT assets and infrastructure. Investments can be plannedmore logically after detailed analysis, thus avoiding wastage of IT resources.

Prior to using the product you need to understand the objective and usage of the product. This guide explainsclearly and concisely the fundamentals of the Cloud Assessment product. It emphasizes upon thearchitecture and tools used in implementing the business strategies and themethodologies designed for thepurpose.

Micro Focus Cloud Assessment helps to address the following critical IT challenges:

l Identifies and stops the wastage of resourcesl Understand IT landscape to execute informed decisions and build roadmapsl Reduce It complexity and Project Risks through systematic standardizationl Assure consistency of IT challenged by changes in Business Strategy

Micro Focus Cloud Assessment key capabilities are based on the below proven standards:

l Certified as ArchiMate® 2 Tooll Incorporates principles from TOGAF®


http://pubs.opengroup.org/architecture/archimate2-doc/toc.html

http://pubs.opengroup.org/architecture/togaf8-doc/arch/

The key takeaways to expect fromMicro Focus Cloud Assessment are:

The Cloud Assessment product comes with a 60 days trial version. The licensed version can bepurchased online.

Cloud Assessment has been designed with the objective of providing a holistic solution for the ITinfrastructure lifecycle ensuring proper allocation of resources through artifacts and documents, linkingof inter-dependent elements via relationships and browsing through navigator, monitoring thedependencies through reporting across the enterprise, presenting new proposals for approval,integrating data from supported plug-ins and creating repositories and all this to bemanaged by rolebased profiles.

The Concept Guide provides an overview of the old and new features and functionality in CloudAssessment which are covered in the upcoming topics. Refer the Document Map, on page 9 to see thelist of topics.

Concepts GuideChapter 1: Concepts


Page 8 of 34Cloud Assessment (1.01)

Concepts GuideChapter 1: Concepts

Chapter 2: Document MapThe following topics are covered in this guide:

1. Build Enterprisemodel describing both Business and ITl Data import and Exportl Product Integrationl Business and IT Alignment

2. Define and Enforce Standardization of IT assetsl Lifecyclel Artifact Validation

3. Design and RoadMap IT Transformationsl Architecture Transformationl Shortcut Relationshipl Surveyl Cloud Assessmentl Cloud Transformationl Model Viewpointl Impact and Dependency analysisl RoadMap Implementation


Chapter 3: Build Enterprise Model Describingboth Business and ITMicro Focus Cloud Assessment integrates and imports data frommultiple types of resources, such as ,spreadsheet, PPM, uCMDB and database.

Micro Focus Cloud Assessment supports Cloud Assessment SparX add-in to model all the levels ofarchitecture easily.

By the virtualization of data, Cloud Assessment generates reports that can be associated with roles. Thereports helps you in decisionmaking.

Data Import and ExportCloud Assessment provides several methods for data import and export. These include Excel/CSV files,XML file importing, and direct imports from other Cloud Assessment instances. For more information see theinformation given below:

l Excel/CSV Files: You can import Excel/CSV files into Cloud Assessment directly using CloudAssessment UI or if you have installed Cloud Assessment on your local machine you can find a commandline tool for CSV file import in the following location: INSTALL_DIR\client\bin\csvImport.bat[sh]. Youcan also download the dedicated CSV importer distribution, which enables you to use the csvImportcommand line tool. The export option is available too. Use context action directly from Cloud Assessmenttables to export CVS files.


l XML Files: You can publish XML files into Cloud Assessment by using the File Import function. TheXML file is analyzed and decomposed into artifacts based on a configuration file stored within scriptartifacts. This configuration is customizable and you can define your own for your custom XMLschemas.

l Cloud Assessment Archives:You can selectively export some artifacts (a whole plateau forexample) from another Cloud Assessment instance by selecting the desired artifacts in the catalogbrowser and clicking the Export context action. An archive file is produced. You can import thearchive by using the Import Repository Archive feature. This enables you to transfer data betweenmultiple, even disconnected instances of Cloud Assessment. In a similar way, youmay exportwhole Cloud Assessment domains.

l WebDAV: Cloud Assessment supports standardWebDAV protocol for importing and exportingdocuments. You can copy documents attached to artifacts in a Cloud Assessment instance, thensimply paste them into another Cloud Assessment instance. The artifacts corresponding todocument names are reproduced in the target instance automatically.

Product IntegrationCloud Assessment includes integrations with many data sources that you can access directly from theCatalog tab catalog panel. These includemodeling tools, other Micro Focus solutions such as PPMand uCMDB, as well as CSV and XML file importing, and direct imports from other Cloud Assessmentinstances. Out of the box you can integrate with these tools, provided other systems are supported aswell. For more details, see "Product IntegrationManagement" in theAdministration Guide.

l Enterprise Architect Modeling Tools: You can edit the whole repository in an externaldiagramming tool where the data will be bidirectionally synchronized between Cloud Assessmentand the tool project space. For more information, see "Extensions for Sparx Systems EA" in theUser Guide.

l Project & Portfolio Management: You can connect Cloud Assessment to project and portfoliomanagement solutions to import project and financial information, which enables you to analyze datain a broader IT perspective, including the application and technology layers of the enterprisearchitecture.

l Configuration Management Database: To analyze the costs, impacts, and dependencies of ITinfrastructure on your business, you can integrate Cloud Assessment with a configurationmanagement database (CMDB). This allows the system to get information about servers andsoftware that are part of application and business architecture. This also enables you to control thelifecycle of these entities.

l Database: It is possible to import data from other systems into Cloud Assessment by integrationwith those system relational databases. A mapping between columns of database tables with CloudAssessment artifact types and properties must be created, and database connectionmust beconfigured as a data source in Cloud Assessment application server.

l Cloud Service: To fulfill Cloud transformation, you need to subscribe to cloud infrastructure andmake appropriate provisions to host the applications. The inputs come from Cloud Assessment forthese services.

NOTE:Contact your Micro Focus sales representative to request an extra integration connectorlicense.

Concepts GuideChapter 3: Build EnterpriseModel Describing both Business and IT


Business and IT AlignmentIn today's dynamic environment, business success requires alignment of strategic business objectiveswith the information technology transformation. The collaboration between business and IT helps inquicker decisionmaking once it is evident how IT impacts planned business objectives.

Objectives of business alignment include:

l Ensuring IT investment priorities are aligned with business strategyl Making DemandManagement transparentl Achieving effective and efficient IT deliveryl Maintaining a transparent view of IT supportBoth IT and business are evolving, hence instead of using outdated and incomplete enterprisearchitecture information stored in common sources such as diagrams, spreadsheets, or slide decks,Cloud Assessment makes it possible to align those and additionally fulfill the following towardsbusiness alignment:

l Comprehensive information: structured data which contains information for each area ofBusiness Alignment (business capability, projects, requirements, application, etc.)

l High quality information: continuously updated information that is mutually semanticallyconsistent

l Available information: information that is centrally stored, managed, and available for analysis,planning, and control purposes.

Once all of the above is achieved, the next step is to start with the implementation in line with theprocess.

This section covers the following topics:

l Enterprise Portfolio Management and Business Alignment , belowl Business Alignment Assessment, on the next pagel Enterprise Architect and Solution Architect Roles, on the next pagel Business Capability, on page 14

Enterprise Portfolio Management and BusinessAlignmentEnterprise Portfolio Management (EPM) implements business alignment strategy based on informationmodel called the Enterprise Portfolio InformationModel (EPI Model). Themodel consists of about 17information entities. The rest are codebooks. It is therefore not extremely complex and at the start ofimplementation, can be generated as a generic design, and later bemodified according to customerneeds.



Enterprise Portfolio Management and Enterprise Portfolio Information Model

The EPI model covers all areas falling under Enterprise Portfolio Management. In addition to theenterprise architecture, it comprises of associations with business strategy, business capability,business requirements, and projects.

Business Alignment AssessmentThe first step in business alignment is a diagnostic phase that focuses on critical IT gaps as defined bythe organization’s business components. The baseline state is shown diagrammatically as well as intabular form and both report types can be used to drive conducive discussions with seniormanagement. After the baseline reporting on the current state is complete, the next step is to specifyappropriate Key Performance Indicators (KPIs) andmetrics, and to configure the initial settings of yourenterprise portfolio management process and associated procedures.

The task flow of the business alignment assessment process is:

1. Identify mandatory assets in Enterprise Portfolio Information (EPI)2. Specify business capabilities (both current and planned)3. Analyze and import existing EPI4. Map business capabilities to IT resources, assets, investment and strategy, etc.5. Deliver the first business alignment assessment6. Define KPIs andmetrics for improvement

Enterprise Architect and Solution Architect RolesThe enterprise architect must ensure that the new design solution conforms to the accepted andendorsed principles of enterprise architecture governance and work with the solution architect to drivesuccessful solution delivery. The key activities of the enterprise architect role in the process of newbusiness capability delivery are to:

l Develop conceptl Assess alignment and impact



l Build into solution architecture approach (with vendor selection and contract negotiation as key sub-tasks)

l Develop solution architecture (after the solution architect defines development methodology)The enterprise architect‘s focus is the business and IT alignment and the successful execution of acommon approach to building enterprise architectures across the whole organization. Both enterprisearchitect and solution architect roles are critical to the new business capability delivery process.

The enterprise architect’s activities guarantee the establishment of a solution concept that conforms toEA governance rules as well as business needs, and defines the architectural approach. The controlfunction of the enterprise architect can also be shown by visualizing an individualized architecturalsolution.

Business CapabilityAs deemed important, business capability is defined in the list of necessary organization skillsavailable for actualizing business plans, regardless of whether they are supported by IT assets orinfrastructure. Planning the development of business capability is the first level towards implementingthe strategic business objectives of the enterprise.

The definition of business capability for your organizationmust cover the following:

l How to capture the business’s varied interestsl What are the building blocks of the businessl How to represent stable business functionsl Are the business lines unique and independent from each otherl Are the business lines abstracted from the organizational modelBasic EPI Entities, Relationships, and Business Alignment Areas



In Cloud Assessment business capability is represented in the following ways:

l Business Capabilities and StructureMaps, belowl Business Capability Investment Analysis, on the next pagel Business Capability Risk Map, on the next page

Business Capabilities and Structure Maps

A summary diagram of business capabilities for the business segment is represented below by abusiness structuremap. This map provides a comprehensive view of all the necessary business skillsgrouped into higher architectural segments (for example, sales andmarketing, risk management, etc.).Each industry segment has its own business structuremap that covers all businesses within thatsegment. Cloud Assessment (Cloud Assessment) helps you to prepare for and implement businessalignment strategies by providing a generic business structuremap that you can use.

Structure Map Showing Business Capabilities of Finance Organization



Business Capability Investment Analysis

Capability investment analysis requires many steps to complete. The diagrammatic view allows seniormanagement to easily see themeasures of investment conformity to the project (shown as shadedcolors) and strategically important capabilities (shown as highlighted areas). You can then provide drill-down to a list of concrete projects by a given capability. For more information, see "StructureMaps"under Reports in theUser Guide.

Diagrammatic View of Capability Investment Analysis

Business Capability Risk Map

The capability risk map or structuremap presents a summary of applications within individualcapabilities that are being evaluated for further support, any exception, dependency or architecturalrisks. Red shades show themeasure of risk for a given capability. Strategic capabilities are highlightedin different colors and you can generate background data for deeper analysis. You can then provide drill-down to a list of concrete projects by a given capability.

Capability Risk/Structure Map





Chapter 4: Define and EnforceStandardization of IT assetsThe following are the common problems found in government agencies:

l Loss of control of information systemsl Dependency on vendorsl Growing costs related to operation of infrastructure and applicationsl Growing and not transparent cost related to development and customization of existing systemsMicro Focus Cloud Assessment provides solution to these problems by means of:

l Standardization of architectureo Referencemodelso Approved technologieso Standards for security, backup andmonitoring

l Standardization of RFPo Templates and default inputs to RFP documentation

l Management of RFP document lifecycleo Validation and enforcement of standards

l Management based on TOGAF and Archimatel Supporting tool for central repository

Lifecycle OverviewArtifacts in Cloud Assessment go through several stages from candidate through development,implementation, and eventually deprecation and reuse. Each stage has ts own specific features, and theorganizations have specific requirements for the various stages. These stages can be split into developmentand run-time stages. Before an artifact is allowed tomove from one stage to another, all necessary policyrequirements and approvals must be in place.

In Cloud Assessment lifecycle processes are defined and the administrator provides the policy, task, andapproval requirements. These processes are then automatically or manually applied to artifacts. Manuallifecycle tasks can be assigned to different users and can have policies that must be validated before a taskis completed. Policies as well as permissions can be associated with the lifecycle process stage.

Once all the requirements and tasks are complete, the artifact owner makes a request to move the process tothe next stage. If the administrator has assigned approvers, they are notified and are required to vote forapproval. Depending on the transition type, the governed artifacts move to the next stage and lifecycleautomatic actions defined for these stages are triggered.


Artifact ValidationMicro Focus Cloud Assessment enables you to validate your Catalog content against publishedpolicies to ensure its consistency and conformance to your business policy.

Policy management and validation uses the following artifact types:

l Technical PolicyA technical policy consists of a set of assertions and references to other technical policies, andserves as the central point of reference for validation. References to other technical policies enableyou to collect a set of technical policies together into a larger policy enabling you to validate themcollectively.

l AssertionAn assertion is a validation check for a single piece of data which can either pass or fail. Forexample, an assertion can check the following attributes of an artifact:o Property Values

An assertion can check that a particular property has a value and what the value is. Typicalexamples include verifying that keywords are set when an artifact is created and verifying that anartifact is consumable before it enters the production lifecycle stage.

o Related ArtifactsAn assertion can check whether a particular artifact type is associated with the artifact beingverified and check property values of the related artifacts. A typical example is to verify that aservice has an attached document which is categorized as a business specification documentbefore the service is approved at the candidate lifecycle stage.

o Data ContentSome artifact types are expected to contain attached content. An assertion can verify that theattachment exists.

o Artifact StateAn assertion can check various status attributes of an artifact, For example, its lifecycle status orits compliance status.

Concepts GuideChapter 4: Define and Enforce Standardization of IT assets


Chapter 5: Design and Roadmap ITTransformationsTodays IT industry involves slow innovation, manual handoffs, complex processes andmany tools to handle.As a result of this, there is slow IT response, missed business opportunities, loss of control and pressure oncosts invested. Under such circumstances, Micro Focus Cloud Assessment provides an easy solution todesign and build a roadmap of the IT transformations.

Architecture TransformationArchitecture transformation is designed to offer cohesive business solution to stakeholders for their businessneeds. The objective is to provide a structure which is transparent, encourages wider involvement from thoseconcerned with architecture changes, enable better control, and facilitate interoperability. Cloud Assessment(Cloud Assessment) enables the enterprise architect to provision future states of an enterprise architecture inorder to evaluate new solution architecture designs. This enables the Enterprise Architect to maintain a viewof shared IT assets and tomake decisions regarding asset sharing through the approved solution design of anew project. The ability to create consolidated future views in selected time slices is made possible throughthe export of a new solution design layout to the Cloud Assessment repository during the SolutionArchitecture Design phase.

Cloud Assessment is capable of managing not only the current architecture (as-is) but also the futurearchitecture (to-be) provisioned for the enterprise. Cloud Assessment uses the same artifacts as inArchimate2® Implementation, andMigration andMotivation layers tomodel the transformation process.

The structure acts as a catalyst in bringing together the enterprise resources and reorganize them to present aless complicated, more logical structure. One that leads the organization towards amore efficient andsystematic approach in realizing the business goals.

l TheMicro Focus architecturemanagement provides a robust architecture keeping the entire business infocus. It integrates business strategies, architecture and projects by covering andmanaging therequirements, successfully negating the effects of a weak project planning present in other models.

l IT related project issues areminimized with the help of proper standards of governance, smoother crossproject inter-dependencies and a clear cut road-map. Thesemeasures result in saving time andmoney,thereby improving the overall organizational efficiency.

Shortcut RelationshipShortcut relationships (or shortcuts) are Cloud Assessment implementation of Archimate® derivedrelationships. For more details, readDerived Relationship in Archimate® documentation.

Shortcuts are introduced in Cloud Assessment for these purposes:

l Speed up ReportingThe performance of reports is improved by analyzing shortcuts instead of traversing the whole chain ofdirect relationships.

l Simplify the Architecture


Unimportant artifacts can be skipped whenmodeling the enterprise architecture while keeping itcompliant with Archimate® language specification. Forexample: modeling an application componentand its services without modeling its detailed functions. In another example, 'Server realizesInfrastructure Service' shortcut represents the required servers/VMs of a deployment model(infrastructure service).Shortcuts are defined as managed scripts by administrators. Due to performance reason, shortcutsmay not be updated immediately to reflect the latest changes of artifacts. To avoid thisinconsistency, the Shortcut Consolidation Task can be scheduled by administrators to updateshortcuts frequently. In addition, Catalog users can resolve shortcuts of an artifact immediately byclickingRecalculate Shortcuts from its context menu.

Shortcuts are displayed in Overview tab of an artifact in italic font so that they are distinguished withdirect relationships. If a shortcut is defined as editable, it can be created using the UI.

Concepts GuideChapter 5: Design and Roadmap IT Transformations


Survey OverviewCloud Assessment provides Survey as a tool to assess the enterprise architecture changes to furtherenhance the usability and feasibility of the artifacts. The survey is designed to encourage valuablefeedback from catalog users as per their user experience and expertise. The objective is to obtain aconclusive feedback so as to bring about improvements in the artifacts keeping in mind theorganization goals.

The survey results enthuse the stakeholders to arrive at a unanimous decision on the changes requiredfor the artifacts.

Workflow

l The survey is designed through a survey definition which is amanaged script on the AdministratorUI. This definition is also available for the survey manager on the catalog page called the SurveyDefinition artifact.

l Once the definition is created and completed, the survey manager can initiate a survey and createsurvey artifacts from it. The artifacts to be surveyed can be selected from the list (by default allartifacts are selected). A survey definitionmay be associated with multiple survey artifacts.

l After starting the survey, notification emails will be sent out to all the stakeholders defined in thecontact roles for each of the artifacts being surveyed. Following the email request, the stakeholderscan go through the survey wizard to complete the survey. Each survey is time bound and therespondents will not be able to access the survey once it has expired.

l A survey manager, besides having the rights to start the survey is also granted with the rights tomanage andmonitor the surveys. This allows for editing, marking the survey as complete or if



required canceling or deleting the surveys.

Cloud AssessmentCloud assessment is a functionality offered to support estimating cost of deployment. With the result ofassessment, Stakeholder will be easier to make decision of selecting and transforming ApplicationComponent to cloud.

Micro Focus Cloud Assessment provide two types of estimation:

l The estimation based on number of servers and their class or profilel The estimation based on deployment modelsBased on the type of estimation, there will be different prerequisites. For more information, seeEstimating Cost of Deployment inMicro Focus Cloud Assessment User Guide.

Micro Focus Cloud Assessment also provide the cost alternatives calculated for available data center,therefore customer could has the comparison andmaking decision to select themost suitable DataCenter.

All estimations of individual Application Component are automatically calculated values for reports.From these report, it will be easier for the Stakeholder to compare, prioritize andmake the decision oftransforming to cloud. For more information, seeCloud Transformation Reports inMicro Focus CloudAssessment User Guide.

Cloud TransformationCloud Assessment provides the capability to manage the Cloud transformation process forapplications. This process involves surveys from different perspectives, cost analysis, reportsvisualization and HCM (Cloud Service Automation). Cloud transformation features can be accessedvia Cloud Transformation Guide . For more details, see "Cloud Transformation Guide" inUser Guide.

Through surveys you can gather inputs from respective stakeholders, relevant to Cloud transformationperspectives namely technical, business and financial. The results help the CIO/CTO inmakingstrategic decisions related to the IT infrastructure of the organization. Through Cloud assessment, asurvey manager can take surveys on behalf of the respondents or inform them to take assignedsurveys. Once the survey results are gathered, the Cloud transformationmanager can view the results



in Cloud transformation reports and decide on the viability of migrating applications into Cloud. Formore details, see "Surveys" and "Cloud Transformation Report" inUser Guide.

Cost analysis helps compare real costs when deploying the applications into different Cloud datacenters such as AmazonWeb Service. Beside the already available data centers, others can be addedfor comparison tomaximize cost savings. The estimation is based on number of servers or as per thedeployment requirement. For more details, see "Estimating Cost of Deployment" and "CloudTransformation Tab" inUser Guide.

After completion of the assessment, integration with Micro Focus HCM (Cloud Service Automation),helps automate creation of service designs, which is the first step towards Cloud automatedprovisioning. For more details, see "HCM (CSA) Integration" inAdministration Guide andMicro FocusHCM (Cloud Service Automation) documentation.

Model ViewpointModel viewpoints (or viewpoint portlets) are Cloud Assessment implementation of Archimate®viewpoints. Viewpoint portlets are defined by Cloud Assessment managed server-side scripts. Thelayout of the viewpoint is specified by using an SVG file that you can create in Inkscape (seewww.inkscape.org).

Cloud Assessment distribution contains the Extension for Inkscape, which allows administrators tocreate and deploy new viewpoints. For more information, see Cloud Assessment Extension forInkscape inCustomization Guide.



http://www.inkscape.org/

Impact and Dependency AnalysisIn modeling, it is usually important to identify, characterize, and understand the impact of thedependencies that exist between the entities in themodel. To adapt this requirement, Micro FocusCloud Assessment allow tomanage relationships to understand impacted objects and dependencies ofa decision across the entire Enterprise.

l Reports ViewPoints: from this report, we could have the analysis impacted objects ordependencies of selected artifact through layers of model.



l Tree view: Cloud Assessment provide a Tree View Tab UI in artifact detail page. From this page,you can view the analysis of impacted objects or dependencies. For more information, see TreeView Tab inMicro Focus Cloud Assessment User Guide.

l Navigator: User also could see the impacted objects of selected artifact from Navigator view page.For more information, seeNavigator inMicro Focus Cloud Assessment User Guide.

Road Map ImplementationUnderstand IT landscape to execute informed decisions and build roadmaps is a critical IT challenge.To address this, Micro Focus Cloud Assessment offers below solution:

1. Build enterprise Model: Micro Focus Cloud Assessment provide an ability of utilize existinginformation by collecting portfolios and data from resources like PPM, data files, CMDB orModeling into centralizedmodel.



2. Understand Dependencies and Governance: Micro Focus Cloud Assessment provide Impactand Dependencies analysis reports and data qualities reports to help you have a general viewabout impact, dependency and quality of elements.

3. Role-based Visualization and Decision Making: Micro Focus Cloud Assessment providedifference types of reports and visualizations with different characteristics like: Artifact Reports,Policy Reports, BIRT Reports, and Dashboards with customizable. Based on working role, youcan find suitable reports easily. For more information, seeReports inMicro Focus CloudAssessment User Guide.

4. Implement Enterprise Architecture Process: Micro Focus Cloud Assessment providefunctionality like: As-is, to-be, andGAP analyzing andmeasuring data quality to help you getcorrect outputs to maintain the Enterprise Architecturemodels. For more information, seeEnterprise Architecture inMicro Focus Cloud Assessment User Guide

5. Lifecycle Planning Plateau: allows to automatically change the stages of lifecycle of the linkedartifacts. The change date is defined by the date attribute in the lifecycle planning plateau. It will bechanged only for the artifacts with lifecycle process havingChange Stages based on Plateausoption as enabled. For more information, see Lifecycle Plan RoadmapReport inMicro FocusCloud Assessment User Guide.



Chapter 6: FinPlanner - Case StudyThe content of the Case Study section is a project called FinPlanner. FinPlanner is a banking application,which, through themeans of an internet application, will empower clients to contract out their financial orinvestment aims.

This case study will show one approach, whichmatches the principles of building an agile enterprisearchitecture (Architecture Transformation), while simultaneously markedly reducing project risk connectedwith the definitions of scope, delivery strategy, delivery deadlines and costs.

Case Study Objectives:

l Demonstrate the approach to building an agile enterprise architecturel Show the role of the Enterprise Architect in this processl Show themeans of working out high-level design solutions.l Show the support of the EA application in working out a design solutionl Recapitulate the benefits for the projectl Recapitulate the benefits for the whole Enterprise Architecture.The Case Study covers the following topics:

l FinPlanner Solution Design , belowl Modeling Business Architecture , on the next pagel Modeling Application Architecture , on page 31l Modeling Technology Architecture , on page 31l FinPlanner Initial Installation and Setup , on page 31l FinPlanner Sparx EA Project , on page 32l FinPlanner Summary, on page 33

FinPlanner Solution DesignHigh-level design layers that are descriptive of the future solution design enable the enterprise architect andsolution architect to create a list of component solutions as well as descriptions of their mutual relations andinterfaces. For the FinPlanner case study, high-level design is created in layers using ArchiMate 2 notation,through the use of a strictly defined set of elements and relations that are also precisely defined. You can findmore details about the ArchiMatemeta-model in the ArchiMate® 2.0 Specification. The enterprisearchitecture has three layers: Business, Application, and Technology. The concept of services, when they


are being furnished on individual layers and that are consumed through various interfaces forms thebasis.

Basic List of Elements on All Layers and Relations

Modeling Business ArchitectureThe goal of modeling the business architecture is to create a comprehensive list of the following:

l Roles and Actorsl Business Services and Processesl Business Objectsl A list of application services, which will be needed by business processesl Create relationships between these elementsA list of business objects and their relations as an informationmodel is created incrementally. In thehigh-level design layer only a core list of business objects and their relations is created. It is only in thephase of detailedmodeling of business processes that the attributes are filled in with the help ofBusiness Process Modeling Notation (BPMN). This approach also applies for the detailed specificationof service integrations.

The business architecture in the FinPlanner case study was designed based on the client'sdocumentation. Workshops with user groups followed. The users participated directly in creating thebusiness architecturemodel.

Defining Core Business FunctionsTo create the high-level design, begin with defining your core business functions, and then continuewith a specification of business services. This must respond to the customer‘s vision and include the

Concepts GuideChapter 6: FinPlanner - Case Study


definitions of services by role that will be used to create the business capability list. In this phase, youcan go intomore detailed or revised specification of deliverables.

In the FinPlanner case study, in the area of collecting client information and facilitating web services forthe business service definition, questions aredeveloped and a dialog with the customer conducted tocollect the required information. For example, the customer responded that the applicationmust be abletomanage the client’s investment portfolio and update personal data. Information collected on roles andrelated services also helps to define the core business functions.

High-level Design of Business Functions

Once the core business functions are created in the high-level design, you will see the describedfunctional areas in the designmodel.

Defining Application Services IntegrationApart from the business architecture components there is also the creation of the integrationrequirements of a new solution with the existing application architecture. These requirements emergegradually and becomemore precise over time, eventually creating a detailed specification of the IN andOUT parameters of the service integration. On a high-level design, only the service names aredetected. These are then filled in with parameters on the detailed process description level (BPMN). Atthe end of the specification process, you will have a detailed service integration specification thatcorresponds to all application processes and all business contexts in which they are called.

The high-level design of application services and integrationmust constantly be updated so that it canserve as an actual view of the target solution. The high-level design diagram provides a consolidationspace for all parts of the business architecture, including the integration layers and the informationmodel.

In the FinPlanner case study, a single application service can be called in the context of a number ofbusiness processes. For example, the “Get Finbank products owned by client” application service iscalled within multiple business process contexts, including the Collecting Client Information businessprocess (shown) and two additional business process modules (partially shown). Themodel shows therelationships between application services and business processes and conforms to Governance in thearea of service design, concretely displaying definitions at a level of meaningful granularity.



Modeling Application ArchitectureAfter approving the high-level designmodel of the business layer, the next step is to create theapplication architecturemodel. The order of operations and required content at each step is designedaccording to the principles and recommendations of the TOGAF and other enterprise architectureframeworks. The goals for the design of the application layer architecturemodel are:

1. Transform the requirements into integration services2. Create instructions for the realization of the required integration services3. Fill in the existing application components, which will supply services to the business processes

and the functioning new application, in the high-level design diagram.4. Fill in the application component(s) in the high-level design diagram.5. Inside of the application component, create the basic decomposition on the level of application

functions.6. Create relations between the application components and the application services.7. In cooperation with the business architect create the relations between the application services

and business process and functions.Similar to business layer, in the application layer also you can provide constant updates by specifyingarchitecture solution that leads to stronger enterprise architecturemodel.

Modeling Technology ArchitectureThe goal of the technology layer is to describe the runtime environment of the application representedby the elements of the ArchiMate 2.0 technology layer. Themain building block is the node. It is acombination of a hardware device and system software. This represents an environment for executionartifacts, which are installed on a component node. The artifact represents a concrete physicalsoftware product element (application source code, source files, scripts, databases, etc). The task of asenior programmer is to gradually specify the technology layer model, with the key component being adetailed list of all artifacts that will be installed on a single node.

In the FinPlanner case study, you can see the first increment of the FinPlanner application’s technologylayer. Since the FinPlanner case study includes a classic three-tier architecture, the technology layercontains three nodes: database server, application server, and presentation layer.

The design of the techology layer must correspond to all the nonfunctioning requirements of theFinPlanner application andmust be in accord with the enterprise architecture governance rules andpolicies.

FinPlanner Initial Installation and SetupTo set up the FinPlanner case study, first a local installation of the Sparx Systems Enterprise Architectversion12modeling environment was made, and then a Cloud Assessment instance in anorganization‘s private cloud was set up. To access the Cloud Assessment application all that is neededis a standard web browser. Follow the instructions given inUser Guide under sectionExtension forSparx Systems EA.

A high-level view includes the following steps:



1. Install Sparx Systems EA, and then install the Cloud Assessment Sparx Systems EA. After youfinish the installation, the import and export functions are available in Sparx Systems EA.

2. Import the current architecture from Cloud Assessment into Sparx Systems EA. After you finishthe import, all elements from your current architecture are available for modeling high-level designand relationships. The elements are shown in layers corresponding to the ArchiMate 2.0 language.This availability accelerates the possibility of reusing existing IT artifacts.

FinPlanner Sparx EA ProjectThe FinPlanner high-level design is shownwithout a technological layer because it simplifies thediagrammatic view. Sparx Systems Enterprise Architecture version 12.1 is used as amodeling tool andincorporates the ArchiMate 2 toolbox. The diagram serves as an end-to-end view of the architecture ofthe future solution. The business architect creates the business layer and the integration architect theapplication layer. The solution architect works on the solution design as a whole and the enterprisearchitect works on the architectural design aspects. The technological layer (not shown) falls under thecompetence of a senior programmer.



Although the FinPlanner case study high-level design is created in Sparx Systems Enterprise Architectversion 12.1, you can also create high-level designs using other modeling Archimate2-compliant tools.For more information on tools for modeling in ArchiMate2, refer theMastering ArchiMate in theArchiMate 2 documentation set.

The FinPlanner high-level designmodel organization corresponds to the ArchiMate layers and elementgroups. This simplified view aids in synchronization with the enterprise architecture repository. Forcustomizing themodel, the ArchiMate2 toolbox is used. In the view area, elements of the businesslayer are shown. The toolbox also contains relational concepts for you to use in creating relationshipsbetween layout elements. Extension for Sparx Systems Enterprise Architect does not contain anycontrol of language rules, whichmeans that a strong practical understanding of themodeling languageis key. As a good starting point, it is recommended that you study existingmodeling patterns and thatyou and your team work through the high-level designmodel.

FinPlanner SummaryShared Application Services

An important part of the solution design of a new application is its integration into the current applicationand information architecture of the organization. Underestimation in this area is frequently a reason forthe failure of an entire project. Shared integration services (in the Service Oriented Architectureframework) are a subset of all application services and are likewise a part of the import from the Cloud



Assessment repository to themodeling environment. The business architect user of the FinPlannerapplication can use the instant view of integration services, including their input and output parametersand their data types.

The business architect user can also immediately evaluate the FinPlanner application needs within theexisting integration services, insert a concrete integration service into the application services layer, orcreate relations between the service and a given business process or business function. If a needarises, the business architect can create a request to modify an existing service or to create a designfor a new service. Cloud Assessment dynamically updates the response to these requests, therebyproviding guaranteed integration of services. This simplifies and improves the quality of the draftapplication design and automatically increases shared IT assets.

FinPlanner Shared Application Components

Similar to shared application services, after importing from Cloud Assessment repository, the architecthas immediate access to all existing enterprise architecture application components. These elementscan then be used directly in the design layer of the application architecture.

Components of the shared application layer can even include future components, which arise as a partof other projects. This makes it possible to evolve and plan shared IT assets even when they are notpart of the current architecture.

FinPlanner Standards Compliance

Maintaining defined architectural principles and standards largely impacts the effectiveness ofenterprise architecturemanagement. You can use Cloud Assessment to define the principles thatgovern compliance and to automatically enforce adherence to related rules and policies.

In the case of FinPlanner; synchronization with the Cloud Assessment repository, the case studyconcluded with maintaining principles and standards, which is also a part of the control of theArchiMate language rules. In cases where language rules are not adhered to, elements that are not incompliance are flagged in red in the high-level diagram.



Documents

Micro Focus Cloud Assessment 1.01 Concept Guide · Legalnotices Warranty TheonlywarrantiesforSeattleSpinCo,Inc.anditssubsidiaries(“Seattle”)productsandservicesareset