The Digital Transformation Consulting Project Service
Introduction
In order to ensure that the IT system serving business activities of the enterprise is planned in a methodical and effective way, meeting all the concerns and requirements of the stakeholders, The Architects uses TOGAF – is the overall architecture development framework of the leading prestigious and popular Open Group organization in the world to build an overall IT architecture with the main tasks as follows:
1. Work directly with, define and refine stakeholder requirements.
2. Build viewpoints and opinions of the architecture, thereby showing how concerns and requirements will be addressed.
3. Make recommendations for improvement, point out the trade-offs to balance the conflicting criteria of stakeholders.
Bases of The Proposal
The Architects uses TOGAF – The Open Group Architecture Framework - to develop the existing architecture and the to-be architecture for your organization. According to TOGAF, the effectiveness of an IT system is measured by its ability to address the concerns of key people in the organization. The unit responsible for designing the enterprise architecture for a business will be the enterprise architect's office operating independently or a separate department within the business reporting directly to the General Director. Therefore, in order to be able to advise and design an effective IT system that meets all the concerns and requirements of stakeholders, the Enterprise architect and his/her team will have to perform the following 3 tasks:
1. Work directly, identify and refine stakeholder requirements.
2. Develop views and architectural perspectives that show how stakeholders' concerns and requirements will be addressed.
3. Make suggestions for improvements, pointing out trade-off points to reconcile conflicting criteria of different stakeholders.
An effective Enterprise Architecture can bring important benefits to your organization such as:
1. More effective and efficient Digital Transformation and IT operations:
a. Lower software development, support, and maintenance costs
b. Bringing all components of the enterprise into a harmonized environment.
c. Improved interoperability and easier system and network management.
d. Improved ability to address critical enterprise-wide issues like security.
2. Better return on existing investment, reduced risk for future investment:
a. Reduced complexity in the business and IT
b. Maximum return on investment in existing business and IT infrastructure.
c. The flexibility to make, buy, or out-source business and IT solutions.
3. Faster, simpler, and cheaper procurement:
a. Buying decisions are simpler, because the information governing procurement is readily available in a coherent plan.
b. The procurement process is faster – maximizing procurement speed and flexibility without sacrificing architectural coherence.
c. The ability to procure heterogeneous, multi-vendor open systems
Expert team driving project success
Project Team Members
Based on project requirements, The Architects will establish a team including international and local experts, scientists and experts in related fields.
1. Methodology: TOGAF – The Open Group Architecture Framework.
2. Research and information gathering methods:
a. [REQUIRED] Interview the board of directors at your organization office, Hanoi to identify and refine the requirements and concerns of each member of the board of directors regarding the IT system. The Architects will need to directly interview directors and department heads:
i. CEO
ii. Director of Marketing & Sales
iii. Director of Manufacturing
iv. Accounting Manager
v. R&D Manager
vi. HR Manager
vii. IT Manager
b. [REQUIRED] Review the production activities at your organization factory cluster.
c. [REQUIRED] Surveyed electronics and home appliance stores in 3 wards in Hanoi and directly interviewed staff in charge of selling your organization products.
d. [OPTIONAL] Work with your organization’s main IT partners/vendors at The Architects office, Hanoi.
e. [OPTIONAL] Research reports on the manufacturing industry, kitchen equipment and household electrical appliances at The Architects office, Hanoi.
f. [OPTIONAL] Purchase and try some products directly.
g. [REQUIRED] Work with the IT department to review the list of hardware, software, network currently used.
Project Duration: 12 weeks
Comprehensive services tailored to your needs
Scope Of Work
1. Prelimary & Architecture Vision
2. Business Architecture
3. Application Architecture
4. Data Architecture
5. Technology Architecture
6. Opportunities & Solution
Defining strategic goals with architecture vision
1. Prelimary & Architecture Vision
Principles Catalog
List of immutable principles of architecture and governance used
Stakeholders Map Matrix
Identify the stakeholders for the architecture engagement, their influence over the engagement, and their key questions, issues, or concerns that must be addressed.
Solution Concept Diagram
A high-level orientation of the solution that is envisaged to meet the objectives of the architecture engagement.
Aligning business strategy with architecture solutions
2. Business Architecture
a. Organization/Actor Catalog:
The organization/actor category is to record an accurate list of all participants interacting with IT, including users and owners of the IT system.
b. Business Capabilities Catalog:
List of specific capabilities that the business owns directly or through a third party.
c. Location Catalog:
Locations directory provides a list of all locations where the business conducts business or contains architecturally relevant assets, such as data centers or end-user computing devices.
d. Strategy/Capability Matrix:
The purpose of the matrix is to display the capabilities needed to support each specific strategy.
e. Business Interaction Matrix:
The matrix describes the interactive relationships between organizations and business functions throughout the enterprise.
f. Business Footprint Diagram:
The diagram depicts the links between business goals, organizational units, business functions and corresponding services, and maps these functions to technological components that provide this capability.
g. Functional Decomposition Diagram:
The diagram displays on a single page all the critical capabilities of the business. By looking at the capabilities from the perspective of the required support function, we can quickly develop models of what the business can do without getting drawn into lengthy debates about how to do it.
h. Process Flow Diagram:
The diagram describes all the models and mappings involved in a process. Process flow diagrams show sequential flows of control between activities and can use swim-lane techniques to demonstrate ownership and execution of process steps.
Designing robust and scalable application architecture
3. Application Architecture
a. Application Portfolio Catalog:
The purpose of this catalog is to identify and maintain a list of all the applications in the enterprise. This list helps to define the horizontal scope of change initiatives that may impact particular kinds of applications.
b. Interface Catalog:
The purpose of the Interface catalog is to scope and document the interfaces between applications to enable the overall dependencies between applications to be scoped as early as possible.
c. Application/Organization Matrix:
The purpose of this matrix is to depict the relationship between systems (i.e., application components) and organizational units within the enterprise.
d. Application Function Matrix:
The matrix describes the relationship between applications and business functions in the enterprise.
e. Application Communication Diagram:
It shows application components and interfaces between components. Interfaces may be associated with data entities where appropriate.
f. Application Use-case Diagram:
The diagram shows the relationship between the user and the provider of the application’s services. Application services are used by Actors or other application services. This diagram provides additional richness in describing application function.
Structuring and managing data for better insights
4. Data Architecture
- a. Application/Data Matrix:
The matrix describes the relationship between applications (i.e. application components) and the data entities they access and update.
- b. Logical Data Diagram:
The diagram logical views of the relationships between important data entities in the business.
Structuring and managing data for better insights
5. Technology Architecture
01
Technology Standards Catalog
The catalog documents the agreed standards for technology across the enterprise covering technologies, and versions, the technology lifecycles, and the refresh cycles for the technology.
02
Technology
Portfolio Catalog
The purpose of this catalog is to identify and maintain a list of all the technology in use across the enterprise, including hardware, infrastructure software, and application software.
03
Application/ Technology Matrix
The matrix documents the mapping of applications to the underlying supporting technology platform.
04
Environments & Location Diagram
The diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally identifies the locations from which business users typically interact with the applications.
Innovative solutions for emerging opportunities
6. Opportunities & Solution
- a. Project Context Diagram
A Project Context diagram shows the scope of a work package to be implemented as a part of a broader transformation roadmap. The Project Context diagram links a work package to the organizations, functions, services, processes, applications, data, and technology that will be added, removed, or impacted by the project.
- b. Benefit Diagram
The Benefits Diagram shows opportunities identified in an architecture definition, classified according to their relative size, benefit, and complexity. This diagram can be used by stakeholders to make selection, prioritization, and sequencing decisions on identified opportunities.
