Unit 3

developing an
enterprise architecture
a. Current Architectural Views

Getting computers to operate together can be difficult due to a

variety of factors such as various operating systems, different
programming and database languages, and older systems that no
longer have vendor support. Poor integration can potentially have a
variety of consequences. On one extreme, company activities may
be inefficient. On the opposite end of the spectrum, there may be
security breaches or faulty equipment.
This is why system integrators are so important.
1. Planning Engineering
/System Integrator Engineer View

 Systems integrators are concerned with interoperability – with getting

software (and sometimes hardware) to work together.
 The work of the integration engineers ensures that new information is
disseminated quickly, that everyone benefits from it, and that users have a
common interface to work with.
 Job duties can include conducting project reviews, evaluating patches,
designing automation software, and planning for release management. At the
higher levels, the job might include project management and system
integration architecture. The system integration engineer might work with
various development teams to ensure interoperability.
2. System Integrator view
 Successful system integrators share characteristics and approaches. Whether
you are a system integrator (SI) or an end-user, understanding the qualities
that make a SI effective could make a significant impact in your organization.
 A SI is an enterprise that takes an end-user’s requirement for a piece of
equipment, determines what components are needed to meet the requirements,
constructs an assembly that combines the components correctly, and adds some
value through programming the application requirements.
 Some system integrators are exclusively machine vision integrators. They
supply the camera, optics, lighting, processor, software, and interfaces to
external equipment along with the mounting for the components, but they do
not supply material handling, such as a conveyor, or any other process
equipment.
2. System Integrator view
 System integrators often differentiate themselves by focusing on certain
industries. One system integrator might specialize in medical devices where
another system integrator specializes in food processing and yet another
specializes in the automotive industry.
 The reasons an end-user comes to a SI is twofold:
 First, they cannot find any commercial piece of equipment to meet their
needs.
 Second, they recognize to undertake designing and building the equipment
takes resources they do not have and entails risks beyond what they are
comfortable with.
 What the SI brings to the project is resources and the ability to manage the
risks.
Managing risks
 What are large risks for the end-user are smaller risks to SI.
 The effective SI brings specialized skills to the project.
 These skills include knowledge of and experience with machine vision technology that
reduces risk and an excellent ability to manage risk so the adverse impact is minimized.
 Risks are inherent in business and especially inherent in any engineering
activity such as system integration.
 The chief mitigators of risk are knowledge and experience.
 The SI should have a process for quickly identifying and dealing with risks.
 The SI and the end-user must partner in creating a comprehensive
specification.
Skills and resources
 Resources consist of staff, skills, facility, and relationships.
 The size of the staff required depends on the difficulty of the systems
the SI undertakes and the number of projects the SI plans to handle
at one time.
 A SI with only a few people can work successfully if they devote all
their resources to one project at a time.
 Most SIs are equipped to handle multiple projects and their staffing
levels correspond to the number of projects undertaken.
Skills and resources
 Skills often needed by a  The effective SI can describe
machine vision SI are: their project management
 Optics work flow processes:
 Motion control or
 Electronics
robotics
 Image processing  Process engineering
 Software development  Documentation
 Training
 IT
 Maintenance
 Mechanical  Project management
 Controls  Problem solving
2. System Developer view
 A systems developer is a type of software developer.
 They develop and implement applications and programs
for the backend processing systems used in businesses and
organizations.
 Backend processing systems are the behind-the-scenes
parts of software that don’t have a user interface, except
for administration purposes.
 They
are used a lot in online banking and HR systems, for
example.
2. System Developer view
Typical responsibilities of a systems developer include:
 discussing the client’s requirements and the proposed solution with a senior
developer (for developers at mid-skill level and below)
 using development tools to write and test code to develop these solutions
 writing documentation and operating manuals
 testing and modifying systems to ensure that they operate reliably
 user training and support
 responding to feedback
 fault finding, diagnosing and fixing bugs
2. System Developer view
Top transferable skills for software developers:
1. Problem-solving ability
The whole point of developing software is to create programs that solve the
user’s problem. If you’re the type who tends to identify issues and figure out the
best way to approach a solution, you may be a perfect fit for a software
development career. Not only that, but programming alone is often an exercise in
problem-solving and troubleshooting—being able to patiently and strategically
tackle potential bugs or issues in code is a big part of their work.
2. System Developer view
Top transferable skills for software developers:
2. Teamwork
Contrary to what’s commonly assumed, software developers aren’t secluded
at their desk with no contact with the outside world. In reality, they spend a lot of
time teaming up with other developers and programmers to create a prime
product for the user. Great communication, empathy and a knack for collaborating
with others is a must.
3. Analytical and strategic
Coding and software are enigmas of a sort, and if you’re someone who likes
solving a mystery by looking at the big picture as well as the smaller steps along
the way, you’ll be right at home developing software.
2. System Developer view
Top transferable skills for software developers:
4. Intrinsic motivation
Creating software can be tricky, tedious work, so it’s important that
you don’t get bogged down or discouraged when you don’t succeed
the first time you try something. If you’re the type of person who is
naturally determined to finish everything you start, you’ll be well-
suited for a career in software development.
b. Future architectural views
Architecture views are representations of the overall architecture that are
significant to one or more system stakeholders. The architect selects and designs a
set of viewpoints that will allow the architecture to be communicated to and
understood by all stakeholders, allowing them to verify that the system will meet
their problems.

Developing Views in the ADM (Architecture Development Method)

The evolution of architectural perspectives is an iterative process. The
traditional path is from business to technology, utilizing a strategy such as business
scenarios to adequately identify all relevant problems; and from high-level
overview to lower-level detail, always going back to the stakeholders' concerns
and requirements throughout the process.
Core taxonomy of architecture views

1. Business Architecture views 

 address the concerns of users, planners, and business managers, and
focus on the functional aspects of the system from the perspective of the
users of the system.
 The People view focuses on the human resource aspects of the system. It
examines the human actors involved in the system.
 The Business Process view deals with the user processes involved in the
system.
 The Business Function view deals with the functions required to support
the processes.
Core taxonomy of architecture views

1. Business Architecture views 

 The Business Information view deals with the information required to
flow in support of the processes.
 The Usability view considers the usability aspects of the system and its
environment.
 The Business Performance view considers the performance aspects of
the system and its environment.
Core taxonomy of architecture views

2. Data Architecture Views and Application

Architecture Views
 address the concerns of the database designers and administrators, and
the system and software engineers of the system.
 They focus on how the system is implemented from the perspective of
different types of engineers (security, software, data, computing
components, communications).
 how that affects its properties
Core taxonomy of architecture views

2. Data Architecture Views and Application

Architecture Views
 Systems and software engineers are typically concerned with
modifiability, re-usability, and availability of other services.
 The Data Flow view deals with the architecture of the storage, retrieval,
processing, archiving, and security of data.
 The Software Engineering view deals with aspects of interest to software
developers.
 The System Engineering view presents a number of different ways in which
software and hardware components can be assembled into a working system.
Core taxonomy of architecture views

3. Technology Architecture views

 address the concerns of the acquirers, operators, communications engineers,
administrators, and managers of the system.
The Communications Engineering view addresses the concerns of
the communications engineers
Acquirer's views address the needs of an acquirer or procurer,
providing appropriate guidance for purchasing components that "fit"
the architecture.
 The Cost View
 The Standards View
Core taxonomy of architecture views

4. Composite Views
 The Enterprise Manageability view addresses the concerns of the operations, administration,
and management of the system, and concentrates more on the details of location, type, and power
of the equipment and software in order to manage the health and availability of the system. It
covers issues such as initial deployment, upgrading, availability, security, performance, asset
management, fault and event management of system components, from the management
perspective of the following subject matters:
 Security
 Software
 Data
 Computing/Hardware
 Communications
Core taxonomy of architecture views

4. Composite Views
 The Enterprise Security view focuses on the security aspects of the
system for the protection of information within the organization. It
examines the system to establish what information is stored and
processed, how valuable it is, what threats exist, and how they can be
addressed.
Topic 3.2. management plan
What is Enterprise Architecture?
 Enterprise architecture is a strategic and comprehensive blueprint
for how IT infrastructure will be used across an organization to
help meet that organization’s goals.
 According to the professional association Enterprise Architecture
Center of Excellence (EACOE), this blueprint can help a business
establish a clear framework for the technology solutions, policies,
and standards the company will use to align IT initiatives with its
business objectives.
Topic 3.2. management plan
 From an IT perspective, enterprise architecture refers to
prioritizing a set of initiatives and IT roadmaps to shape how an
organization will use technology. This is done to optimize
operations and to communicate the strategies to stakeholders.
 From a business perspective, enterprise architecture illuminates
how an organization can achieve its goals through the creation of a
series of engineered models and projects that can be easily
understood by everyone associated with the organization.
What Are the Benefits of Enterprise
Architecture Planning?
1. It improves a company’s operations
 Implementing enterprise architecture can give a business a
clearer picture of how all of its IT components work together
most effectively. This can improve staff productivity and
communication, eliminate redundant and unnecessary
technology solutions, and can improve the ROI on the IT
solutions the organization has invested in.
What Are the Benefits of Enterprise
Architecture Planning?
2. It improves business agility
 When an organization has developed a holistic view of its IT
infrastructure, and how all of the pieces fit together, the technology team
will be able to adjust both more quickly and less disruptively when they
need to add new solutions or make changes to existing ones. This is
because an enterprise architecture view allows the IT team to understand
how a proposed change could have a ripple effect across the business —
and how to proceed to minimize disruptions and other issues.
What Are the Benefits of Enterprise
Architecture Planning?
3. It can help the IT team earn stakeholder buy-in
 Enterprise architecture planning typically involves all relevant
stakeholders across the organization — not only IT but also the heads of
other departments and the senior management team — because this
architecture planning will affect everyone across the company. With this
cross-functional group all working together, discussing how proposed
architectural changes can benefit their teams and the company, and
prioritizing these plans on an enterprise architecture roadmap (or
other technology roadmaps), the initiative will be more likely to earn
executive buy-in than if the IT team created a plan without input from
these other groups.