Showing posts with label Solution architecture. Show all posts
Showing posts with label Solution architecture. Show all posts

Wednesday, October 15, 2014

Microsoft Private Cloud part 1: VMM2012 Architecture


This series is about Microsoft Private Cloud.
We will start by discussing VMM 2012 architecture, topology and ports . This is the one of the most important aspect of Microsoft private cloud
We are not discussing VMM2012 features or capabilities.



VMM 2012 Architecture




VMM2012 Topology




Now we need to look at the Ports. Below are the default ports for VMM2012



Now is the VMM Architecture with ports







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
Business
- 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
Networking
·         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
System
  • 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

o 




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
o 
\


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

Sunday, May 25, 2014

TOGAF: Practical implementation-1




TOGAF is a generic framework. I believe no enterprise uses the TOGAF in its generic form. Every enterprise customizes the TOGAF as per its needs. TOGAF can be used in two ways: Enterprise level and Individual level. Individual level means how a professional can use on a project level in more practical manner. This topic covers individual level TOGAF usage. How TOGAF is used practically instead of just being a theory. This whole discussion is about using a framework in a real environment, a practical implementation. TOGAF is an enterprise framework. We will break down TOGAF and use it as  a solution framework.It No more will be a TOGAF. It will more of a stripped down TOGAF.
First, we will divide the TOGAF framework into different sections and then we will go deep in each section.
I have divided TOGAF under following categories
1)      Requirements

2) Solutioning


3)   Delivery

4)       Governance/Change Management
As part of our discussion, we will go through different phases. This topic will be complete in multiple blogs. I
Now we have down the ground work of breaking and stripping of TOGAF into different parts. In my next blog, we will start with Requirements section. This is the most important and the biggest part. This section will be further divided into 4 parts. Each part tells us how to get requirements. Once the requirement section is done, then rest is easy.

So For Requirements
1) Business Architucture- http://technologyandarchitecture.blogspot.in/2014/05/togaf-practical-implementation-2.html 





TOGAF: Practical Implementation-2: Requirement Gathering- Business Architecture






Requirements are core to any solution. If you don't have right requirements, then the solution created will be wrong. You won’t be able to address the problem or an opportunity. Requirements show what elements and functions are necessary for the particular project.
Requirements has 4 parts
1)    Business Architecture
2)    Information and systems Architecture
3)    Technology Architecture
4)    Opportunities

In this section we will discuss Business Architecture.
Before, we start, I advise anyone reading this blog to keep an open mind. Here the attempt is to use TOGAF an enterprise level framework as a solution framework which can be used by anyone in his or her projects.
As per TOGAF, development of a business architecture to support an agreed Architecture vision. It includes process and people, Principles and their relationships to each other.
I believe, from solution framework point of view, we need to understand
·         What is the business strategy ?
·         What are the internal and external drivers?
·         What are the business models and processes?
·         Who participates in the business processes?
·         What are the project goals?
·         How will the success of the solution be measured?
·         Why is the project important to you now?
·          What is so compelling that a new solution is needed?

Answer to these questions helps us to create an overall business requirement. It gives us a big picture.
Primary stakeholders are
–  Business managers
–  System acquirer
–  Business analyst

 It further tells us

So lets describe them in detail 

A business driver is a business condition that motivates the customer to seek a solution. They might be an external force or an internal effort to take advantage of an external condition. Business drivers are statements about changes in the marketplace or environment that present problems and/or opportunities.

A business goal is an objective of the solution – what the solution must accomplish in
Business terms.

 A business Metrics
–        A clearly measurable test for a business goal
–        A numeric value or other testable criterion for assessing the degree to which a business goal has been achieved
•         Used as a key component of acceptance criteria
•         Generally applies to full scope of architecture
Example business metrics:
•         15% of sales will be web-based electronic commerce by the end of the calendar year
•         Certify compliance with regulation ABCD at least a month before deadline
•         Merge payrolls and expense systems within 8 months

A business principle is an approach or means for achieving a goal.

Let me try to explain each of these in detail.

Business Goal and Business drivers are the driving force for any solution. Below is an example of Goals and drivers



Once we have collected this information, we now know the challenges an organization is facing. We know its goals and drivers. Our Objectives get clarity and now we know what the solution should deliver.


Principle
•         A fundamental approach or means for achieving
a goal
•         Timeless; how the system is meant to work
−        Constrain and identify decisions about the solution and its realization
−        Provide an agreed reference framework for evaluation
of alternatives and decisions
−        Require input from stakeholders to define effective principles
Example business principles:
−        Allow customers to transact business directly through web-based access to our information systems without the need for a customer representative intermediary
−        Our existing dealers are an integral part of our future business strategy
Tests of a good principle
–        Clear, concise, and stated in present tense
–        Prescriptive
•         Describes an overall approach for achieving the future state, i.e., a means, not an end
•         Not a short-term action
–        Constructive
•         Helps you make decisions and progress toward future solution
•         Specific enough to drive behavior
–        Testable
•         You can tell if the principle is being practiced
–        Compelling
•         Strongly motivated by drivers, goals, and other principles
•         Avoids truisms and trivialities (realistic alternatives exist)
•         Likely to result in many right decisions if followed
–        Memorable
Every Principle has

Rationale
–        The motivation behind the principle, the business benefit of achieving the principle, or the cost/business impact of not achieving it (why this is a good principle)
Implication
–        An explicit statement of work or condition needed to achieve this principle (what must be done to implement the principle in terms of IT, process, and people)
Obstacle
–        Known issues, problems, or constraints that may impede the achievement of a principle (what can get in the way of progress)
Action
–        Specific tasks to address an obstacle or carry out an implication of a principle (what, when, who)

An example of Principle

Principle:
–        Extend web shopping to include nearby store information and services
Rationale:
–        Unique capability that will attract & retain customers
Implication:
–        Business must support merging of web business information and store business information
Obstacle:
–        If web business is directly connected to store, online shopping must charge local tax
Action:

–        Determine greatest level of integration possible while retaining tax independence








VERIFICATION
• Analysis
  • Does each goal help address one or more drivers?
  • Does each principle help achieve one or more goals?
  • Will achieving the goals address each driver adequately?
  • Will following each principle achieve each of the goals?


•Discussion
  • Does this feel right?
  • Are these the most useful principles for this area?
  • Are there other important principles that need to be added?
  • Are there some of these that are questionable?
  • How close is this view to what’s needed?
  • Is it compelling?
Now we have the Business principles. Any solution that will be made will take in consider these principles which are based on Goals and drivers for a business.





































































































Featured Post

Ichimoku cloud

Here how you read a ichimoku cloud 1) Blue Converse line: It measures short term trend. it also shows minor support or resistance. Its ve...