Skip to main content

CobiT

Go Search
Home
  
CobiT > Wiki Pages > WorkDefinition - Identify Automated Solutions  

WorkDefinition - Identify Automated Solutions

WorkDefinition Information

Identify Automated Solutions

Description

Management of the process of Identify automated solutions that satisfies the business requirement for IT of translating business functional and control requirements into an effective and efficient design of automated solutions is:

0 Non-existent when
The organisation does not require the identification of functional and operational requirements for development, implementation or modification of solutions, such as system, service, infrastructure, software and data. The organisation does not maintain an awareness of available technology solutions potentially relevant to its business.

1 Initial/Ad Hoc when
There is an awareness of the need to define requirements and identify technology solutions. Individual groups meet to discuss needs informally, and requirements are sometimes documented. Solutions are identified by individuals based on limited market awareness or in response to vendor offerings. There is minimal structured research or analysis of available technology.

2 Repeatable but Intuitive when
Some intuitive approaches to identify IT solutions exist and vary across the business. Solutions are identified informally based on the internal experience and knowledge of the IT function. The success of each project depends on the expertise of a few key individuals. The quality of documentation and decision making varies considerably. Unstructured approaches are used to define requirements and identify technology solutions.

3 Defined when
Clear and structured approaches in determining IT solutions exist. The approach to the determination of IT solutions requires the consideration of alternatives evaluated against business or user requirements, technological opportunities, economic feasibility, risk assessments, and other factors. The process for determining IT solutions is applied for some projects based on factors such as the decisions made by the individual staff members involved, the amount of management time committed, and the size and priority of the original business requirement. Structured approaches are used to define requirements and identify IT solutions.

4 Managed and Measurable when
An established methodology for identification and assessment of IT solutions exists and is used for most projects. Project documentation is of good quality, and each stage is properly approved. Requirements are well articulated and in accordance with predefined structures. Solution alternatives are considered, including the analysis of costs and benefits. The methodology is clear,defined, generally understood and measurable. There is a clearly defined interface between IT management and business in the identification and assessment of IT solutions.

5 Optimised when
The methodology for identification and assessment of IT solutions is subjected to continuous improvement. The acquisition and implementation methodology has the flexibility for large- and small-scale projects. The methodology is supported by internal and external knowledge databases containing reference materials on technology solutions. The methodology itself produces documentation in a predefined structure that makes production and maintenance efficient. New opportunities are often identified to utilise technology to gain competitive advantage, influence business process re-engineering and improve overall efficiency. Management detects and acts if IT solutions are approved without consideration of alternative technologies or business functional requirements.

Conduct a feasibility study/impact assessment in respect of implementing proposed business requirementsEstablish processes for integrity/currency of requirementsDevelop a requirements approval processDefine business functional and technical requirementsAssess business benefits of proposed solutionsApprove and sign off on solutions proposedIdentify, document and analyse business process risk.Assess IT operational benefits of proposed solutions

Attributes

Element CategoriesAI1.2 Risk Analysis Report, AI1 Identify Automated Solutions, AI1.4 Requirements and Feasibility Decision and Approval, AI1.3 Feasibility Study and Formulation of Alt Courses of Action, AI1.1 Def and Maintenance of Business Func and Tech Requirements
IT ResourcesApplication, Infrastructure
Primary Business RequirementsEffectiveness
Secondary Business RequirementsEfficiency
Primary IT Governance Focus AreasStrategic alignment, Value delivery
Secondary IT Governance Focus AreasResource management, Risk management
Goals and Metrics

IT Goals
-Define how business functional and control requirements are translated into effective and efficient automated solutions
-Respond to business requirements in alignment with the business strategy

IT Metrics
-Number of projects where stated benefits were not achieved due to incorrectfeasibility assumptions
-Percent of users satisfied with the functionality delivered


Process Goals
-Identify solutions that meet user requirements
-Identify solutions that are technically feasible and cost effective
-Make a decision on ‘buy vs. build’ that optimises value and minimises risk

Process Metrics
-Percent of stakeholders satisfied with the accuracy of the feasibility study
-Extent to which a benefit’s definition changes from feasibility study through implementation
-Percent of the application portfolio not consistent with architecture
-Percent of feasibility studies delivered on time and on budget Activities


Activity Goals
-Defining business and technical requirements
-Undertaking feasibility studies as defined in the development standards
-Considering security and control requirements early
-Approving (or rejecting) requirements and feasibility study results

Activity Metrics
-Percent of projects in the annual IT plan subject to the feasibility study
-Percent of feasibility studies signed off on by the business process owner

Inputs and Outputs

WorkProductInputOutputAllowable States
Business requirements feasibility study(none)

Last modified at 12/10/2007 3:51 PM  by Administrator