Friday, June 20, 2014

TOGAF: Practical Implementation-3: Requirement Gathering-Information Systems Architecture, Technology architecture and Opportunities=> Solution

TOGAF: Practical Implementation-3: Requirement Gathering-Information Systems Architecture, Technology architecture and Opportunities=>  Solution
Once we have created business principles and we know Business goals and drivers, we now have an idea what is the issue we need to solve. In other words we now know what the solution should address.
So we go to next step.
When we are talking about Information systems architecture and technology architecture, we need to understand that instead of focusing on technology, the focus should on solving the business problem.
It can be broken into Functional and Technology View or strategy.
For the Functional strategy

We need to FIRST ask what the solution should do.
§  How will it be used?
§  What services will it provide?
§  What information will it provide? To whom?
§  Who are the users?
§  What qualities must the solution have?
Here we are thinking from the end user perspective.
As in the Business Architecture we asked the question WHY, In this we need to ask WHAT
An example
- why

Business goals with associated metrics (in no particular order)
·         Strengthen the team and make sure that they are capable to provide satisfied IT service system by end of 2014 (focus on team building, serving for. (BG1)
·         Expand service capability
o   We categorize our services components hierarchically into physical groups and logical groups, to minimize business impact to each other (e.g. to avoid minor business transaction to impact the key business)
·         We ensure customer understands total offering by end of 2014.
·         Customer-care process to be in place and implemented by end of 2014.
·         Internal operation process to be in place and implemented by end of 2004.
·         Cost-effective IT investment aligned with business strategy
o   BG1
o   Scalable architecture design to maximize the utilization of IT investment.
·         SLA is defined and implemented by end of 2014.

Functional principles
- what

Customer Care
·         Quickly respond to service requests from customers, and give feedback in time
·         Show the hospitality of kindness, care and patience, use simple, standard and professional language
·         Customers can get required information through a simple process

SLA (Service Level Agreement)
·         SLA must be categorized and negotiated with customers, then documented

·         SLA should be evaluated, traceable, operable and measurable

·         Make SLA knowledge popular and acceptable in UTStarcom

IT Operation Process
·         Establish and introduce/advertise service oriented processes for IT Operations
·         Processes of IT Operations should be simple, clear, operable, and can be tracked easily
·         Periodically review processes of IT Operations


Technical Strategy/Technology Architecture

The technical view asks how the solution should work.
§  How will the solution be structured and constructed?
§  What are the interfaces and other constraints?
§  What applications and data are needed?
§  What does the infrastructure look like?
§  What technical standards will apply?
§  How will the system qualities be achieved?
This is the place of Architects and designers. Here the high level solution and Defines the structure of the solution from a constructor’s perspective.
For example
Technical principles
- how
·         Network (LAN and WAN) must be stable and reliable
·         Network Bandwidth should meet requirement of business growth
·         Set subnet reasonably, ensure network security, efficiency and scalability
  • Improve the scalability of servers and storage

  • Improve scalability of system
  • Improve performance of system
  • Improve the efficiency of system backup and recovery

IT Management
·         We should have an integrated IT management platform for global network, system and application
·         We should have an integrated report system for IT management
·         We should have a tool for monitoring and managing end user/client devices
·         IT management platform should be integrated with helpdesk platform


The final part of the whole solution is Implementation strategy
The implementation view asks with what the solution will be built.
§  What specific products and components, from which vendors, are needed to build the solution?
§  How will the solution be developed and deployed?
§  What timeframes are “frozen” (not available for deployment)?
§  What validation methods will be used?
§  How will the solution be managed?
§  What is the source of funding?
This is from Deployers Perspective
Implementation principles
- with
IT Operations
·         Strictly follow the change management process during IT operations
·         Unified role and responsibility definition for all management processes
·         Implement job role backup policy
·         Establish the mechanism to conduct customer satisfaction survey

Product Selection
·         The price performance must be optimized

·         Products must be manageable and securable

·         Products must have good Brand name and direct post-sale service

Data Center Implementation
·         Design project plan and follow the plan strictly
·         Reduce the impact to end users during implementation
·         Reduce downtime during system relocation

Once you have all these information, Solution is a piece of cake

No comments:

Post a Comment

Featured Post

Amazon Route 53

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.Route 53  perform three main functions in any...