Stakeholder Analysis Exercise Spreadsheet Using the DMV Case Study and the Stakeholder Analysis Exercise spreadsheetprovided, you are to complete the colum
Stakeholder Analysis Exercise Spreadsheet Using the DMV Case Study and the Stakeholder Analysis Exercise spreadsheetprovided, you are to complete the columns of the spreadsheet for each of the ten stakeholder groups listed on the spreadsheet.More detailed instructions are attached along with resources Stakeholder Analysis Assignment
This assignment uses two provided documents:
•
•
Stakeholder_Analysis_Exercise.xls (spreadsheet)
DMV Case Study
Purpose of this Assignment
This assignment gives you the opportunity to apply your understanding of the course
concepts to analyze how the enterprise architecture (EA) affects various elements of the
organization. This assignment specifically addresses the following course outcome:
•
conduct stakeholder analysis to identify concerns and appropriate viewpoints
Background
One of the keys to successful enterprise architecture (EA) implementation is the support
offered by important stakeholders.
Stakeholders are those with an interest in a given project. There are varying degrees of
stakeholder involvement, which may be described as being in the following groups:
•
•
•
•
Key Players—These are the most important stakeholders; they have a vested
interest in the approach, content, and output of the EA.
Keep Satisfied—The next most significant group are those who must obtain what
they need from the EA and are less concerned with the construction and specific
content of the EA.
Keep Informed—This group has a need to know what is being done and how it will
benefit the organization overall; they have little interest in any of the details of how
the EA is developed and used.
Minimal Effort—This group has little interest in the EA and requires little attention
during the EA development effort.
The benefits of successfully managing stakeholders include the following:
•
•
•
•
Obtaining support from the most influential stakeholders will help ensure that they
both help to shape the EA and to improve its content and products.
Influential stakeholders are in a position to allocate human and financial resources to
the EA effort, making it more likely to succeed.
Ongoing communication with stakeholders ensures their understanding of the
process and benefits of EA, and enables their support if needed.
Successful management allows the EA team to draw on the support of stakeholders
with a positive view of the process if they need to address negative reactions or
setbacks in the organization.
(Concepts contained herein were derived in part from The Open Group Architecture
Framework (TOGAF), v. 9.)
12/04/2018
Assignment
Using the DMV Case Study and the Stakeholder Analysis Exercise spreadsheet provided, you
are to complete the columns of the spreadsheet for each of the ten stakeholder groups
listed on the spreadsheet.
Please refer to the reading link in your Course 5 content area called: TOGAF Standard:
Stakeholder Management. This link provides some excellent insights into the different roles
and influences of the stakeholders to assist in your assignment. Again, this is just a
reference for your benefit.
First, explain the interest or concern that the stakeholder has in the development of the EA.
Then, identify their “class” or role in the EA as one of the four shown above (Key Player,
Keep Satisfied, Keep Informed, or Minimal Effort). Finally, explain your reasoning for
selecting the class/role that you did.
Important: You are not being graded on whether you picked the “correct” stakeholder
involvement (i.e. key player, keep satisfied, keep informed or minimal effort). You might
see your Security Officer as a key player or as a stakeholder needing to be kept informed.
This is fine. What is important is that you provide a solid reason for why you chose this
classification as it relates to the interest/concern area. Please only pick one “class” or role
per stakeholder.
Complete the spreadsheet and submit it via your Assignments Folder by the due date shown
in the class schedule. Note: The filename of your submission should include your last name.
An example would be: Smith_Stakeholder_Analysis.xls.
Reference
The Open Group. (2018). TOGAF version 9.2: The Open Group architecture framework
(TOGAF). Retrieved from http://www.opengroup.org/togaf
The TOGAF Standard, Version 9.2: Part III: ADM Guidelines & Techniques; Stakeholder
Management. Retrieved from: http://pubs.opengroup.org/architecture/togaf9doc/arch/index.html
Grading Rubric
Your grade will be determined by the strength and validity of your analysis, rather than
what specific class/role you selected. Your work will be graded according to the grading
rubric below.
Criteria
90-100%
Far Above
Standards
80-89%
Above
Standards
70-79%
Meets
Standards
60-69%
Below
Standards
< 60%
Well
Below
Standards
Possible
Points
Stakeholder
Analysis
Interest/Concern
and Class/Role of
the stakeholder
are correctly
identified.
Interest/Concern
and Class/Role of
the stakeholder
are correctly
identified. Reason
Interest/Concern
and Class/Role of
the stakeholder
are adequately
identified. Reason
Interest/Concern
and/or Class/Role
for the
stakeholder may
be inadequately
No entries
for this
stakeholder
or little
9 points
for each
Stakeholder
12/04/2018
90-100%
Far Above
Standards
80-89%
Above
Standards
70-79%
Meets
Standards
60-69%
Below
Standards
< 60%
Well
Below
Standards
Possible
Points
Reason for
Classification
provides a full
explanation with
convincing
justification; each
is clearly
applicable to the
case study;
demonstrates a
sophisticated
understanding of
course concepts,
analysis, and/or
critical thinking.
for Classification
provides a clear
explanation with
justification; each
is applicable to
the case study;
demonstrates an
understanding of
course concepts,
analysis, and/or
critical thinking.
for Classification
is adequately
explained; each is
related to the
case study;
demonstrates an
adequate
understanding of
course concepts,
analysis, and/or
critical thinking.
identified; and/or
Reason for
Classification may
not be adequately
explained; and/or
may not relate to
the case study;
and/or
demonstrates an
inadequate
understanding of
course concepts,
analysis, and/or
critical thinking.
information
provided.
(see
below)
Head,
Dept. of
Motor
Vehicles
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Chief
Financial
Officer
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Program
Management
Office
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Line
Managers
for Service
Delivery
Areas
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Credentialing and
Tax
Processing
Specialists
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Customer
Service
Specialist
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Security
Officer
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Criteria
12/04/2018
90-100%
Far Above
Standards
80-89%
Above
Standards
70-79%
Meets
Standards
60-69%
Below
Standards
< 60%
Well
Below
Standards
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
Application
Software
Developer
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
IT Operations
Manager
9 Points
8 Points
7 Points
6 Points
0-5
Points
9
9-10 Points
8 Points
7 Points
6 Points
0-5 Points
Spreadsheet
reflects effective
organization and
sophisticated
writing; correct
structure,
grammar, and
spelling;
presented in a
professional
format using
Excel.
Spreadsheet
reflects effective
organization and
clear writing;
correct structure,
grammar, and
spelling;
presented in a
professional
format using
Excel.
Spreadsheet is
organized; and/or
may contain some
grammatical or
spelling errors;
presented in Excel
format.
Spreadsheet is
somewhat
organized, and/or
contains
grammatical or
spelling errors;
and/or does not
use Excel
template.
Spreadsheet
content is
extremely
poorly
constructed
and does
not convey
the
information.
Criteria
CIO
Spreadsheet
Format
TOTAL
Points
Possible
12/04/2018
Possible
Points
10
100
Stakeholder
Program Executive Sponsor (Example)
Head, Dept. of Motor Vehicles
Chief Financial Officer
Program Management Office
Line Managers for Service Delivery Areas
Credentialing and Tax Processing Specialists
Customer Service Specialist
Security Officer
CIO
Application Software Developer
IT Operations Manager
Interest or Concern
This stakeholder is interested in on-time, on-budget delivery of
the CSI system to realize expected benefits for the DMV and its
customers.
Class/Role in EA Process (Key Player, Keep
Satisfied, Keep Informed, Minimal Effort)
Reason for Classification
Keep Informed
This stakeholder is interested in overall bottom line results vs. the
specific content of the EA.
DMV Case Study
Purpose of this Assignment
(The information below is excerpted from the Virginia Department of Motor Vehicles’ RFP
154:7-061, DMV CSI Systems Redesign Project, available from under Content>Course
Resources>DMV_CSI_RFP_083107_Final_Release. Corresponding page numbers from the
RFP are given in parentheses at the end of each lettered section heading.)
A. DMV Organizational Overview (p. 2)
The Department of Motor Vehicles (DMV) is a governmental agency in the Executive Branch of
Virginia state government. Under the direction of the Secretary of Transportation, DMV
administers motor vehicle and tax related laws for the continued benefit of all citizens of the
Commonwealth of Virginia. Specifically, DMV administers motor vehicle titling and licensing
laws, driver’s licensing laws, transportation safety laws, tax laws, and other motor vehiclerelated laws and regulations as directed by the Code of Virginia and Federal laws, as amended.
DMV employs nearly 2000 full and part-time employees to meet its daily mission of providing
transportation services to customers in Virginia. These employees provide services via one
centralized administrative Headquarters located in Richmond, Virginia as well as 74 Customer
Service Centers (CSC’s) and 13 Motor Carrier Service Centers/Weigh Stations (MCSC’s)
dispersed throughout the state. In addition, some services are provided at more than 40 DMV
Select offices located throughout the state. DMV Selects are a service alternative to visiting a
full-service DMV Customer Service Center. Local governments and private entities contract with
DMV to provide secure, select DMV transactions at convenient locations.
DMV provides a multitude of services to private citizens, transportation entities, courts, law
enforcement agencies, government agencies, insurance companies, and related transportation
clients. The most commonly provided DMV services include:
Credentialing – This includes the provision of driver testing and licensing, vehicle
titling and registration, credentialing of commercial motor carriers, and regulatory
licensing functions such as fuel distributors, rental car companies, dealers,
commercial driver training schools, driver improvement clinics, and 3rd party
testers.
Tax processing – This includes support for the calculation, collection, accounting,
and reporting statistics for all tax filings (including IFTA, tax on fuel, and tax on
motor vehicle rentals) as well as support for an external/taxpayer audit function.
Oversight of related programs such as transportation safety and information
management
Due to the nature of DMV business processes, the type of work performed by the agency
requires substantial use of automated systems. It is imperative that the agency operate its
programs and facilities in an efficient manner, incorporating into its operation those
July 2014
1
technological developments and automated solutions that will enhance the delivery of services to
DMV’s various transportation clients.
B. The Opportunity (p. 1, pp. 2-3)
DMV has decided to undertake a systems redesign they are calling CSI:
Customer-centric
Service Oriented
State-of-the-art
Secure
Intelligent
…..CSI
The DMV CSI Systems Redesign project focuses on the fragmented processing of DMV’s core
business areas of credentialing, tax processing, and financial management. The purpose of the
CSI effort is to transform these fragmented and outdated systems into one modernized system
that is responsive to the ever-changing needs relating to internal security, homeland security,
legislative mandates, and customer relationship management.
As we move forward with this endeavor, DMV has a unique opportunity to revolutionize the
agency’s approach to fulfilling its mission, carrying out core functions, and delivering service.
DMV intends to fully integrate processing while incorporating and leveraging the full
functionality and benefits of proposed technology solutions as well as the technology already in
place.
The scope of the DMV CSI Systems Redesign project is based on utilizing a fully integrated
system to serve and manage our customers, our contractual business partners, and our
stakeholders. The scope includes, but is not limited to credentialing, tax processing, and financial
management.
The CSI Redesign consists of the following components:
July 2014
User interfaces for Headquarters, Weigh Station, and Customer Service Center
staff, DMV Selects, Internet, Touchtone, cyber sites, and selected business
partners (online dealers, Commissioners of the Revenue, insurance companies,
motor carrier companies, etc.)
Core business services
Infrastructure services to manage access rights, perform audit and system logging
functions, a business rules engine, a message broker to facilitate communication
between components and with external system interfaces, transaction suspense
capability, and a correspondence module.
Data stores, business intelligence to provide regular and ad hoc management
reports, audit reports and fraud alerts, and other applications, and
Interfaces to other systems, such as DMV’s Purchasing, Inventory, and Payables
System (PIPS), Department of Accounts (DOA), Treasury, Unified Carrier
2
Register (UCR) repository, Centralized Accident Processing System (CAP),
Traffic Records Electronic Data System (TREDS) which will replace CAP,
Hauling Permits, Virginia Criminal Information Network (VCIN), DMV’s
Human Resource system, etc.
C. The Current Environment (pp. 6-7)
1. Overview of Existing Customer Service Center (CSC) Environment
Each CSC has the capability to house its own hardware and software supporting the
citizens of the Commonwealth utilizing server virtualization and operating system
streaming to reduce the support costs associated with distributed systems.
The main technologies utilized are based on Ardence Desktop Edition
(www.ardence.com) to stream the Windows operating system to the desktops. VMWare
ESX server is utilized to host virtual Windows 2003 based servers.
DMV CSCs are connected to the DMV HQ via T1 speed circuits. The HQ WAN
connections are enhanced by the use of F5 WANjet appliances. DMV CSC’s also have
frame relay circuits connecting them to the Virginia Information Technologies Agency
(VITA) data center for SNA Mainframe traffic only.
All servers in each branch must support being virtual servers. This allows DMV to
centrally manage and deploy servers without having to procure or replace server
hardware as systems are introduced, upgraded, or replaced. Servers can be deployed from
the central DMV support system utilizing the existing DMV Virtual Server Farm. DMV
has a pair of HP Proliant DL360s fiber connected to an HP MSA1000 SAN for Virtual
Machines. All connections to the SAN are through the DL360s and Virtual Servers. The
current storage capacity of the MSA1000 is approx 1TB of storage. Disk space can be
provided via Windows 2003 Virtual Servers.
All workstations have the operating system streamed (OSS) via Ardence Desktop
Edition. This allows DMV to centrally manage and update one system image for all
machines at the DMV CSCs. The internal hard disk on each workstation has been
deactivated as the operating system is streamed but can be enabled if necessary. Also,
Ardence Desktop Edition provides a full Windows XP Pro Operating system, not an XP
embedded or thin client OS. This allows any device with the proper drivers installed in
the master image to work on the DMV OSS Workstations. DMV has deployed HP
dc7600 slim line PC’s for the OSS Workstations.
User authentication, authorization, file and print, and group policies are provided locally
at each CSC via Virtual Windows 2003 Servers.
Each CSC presently has its own software to support the citizens of the Commonwealth
for driver licensing and vehicle registration utilizing CSCNet (Customer Service Center
Network) written in the Software AG language Natural, in a Unix environment.
July 2014
3
2. Overview of Existing DMV HQ Computing Environment
At its Headquarters location, DMV operates a Novell v6.5 LAN.
Customer Service Center PC’s connect to the HQ LAN via the WAN. DMV PC’s operate
in either a Windows 2000 or XP Pro SP2 environment.
Novell GroupWise v7.x is used for e-mail. Netware for SAA is used for 3270 emulation
with the use of Powerterm to access CSS.
3. Overview of Existing Citizen Services System (CSS)
The CSS System is a mainframe application system running in the OS/390 environment
at VITA. DMV’s application programs are built using the Software AG products
ADABAS, Natural, and COMPLETE. CSS is DMV’s primary information system that is
used for storing information on customers, their addresses, their driver history, vehicle
registration and titling information, etc.
This system is accessed from the CSCs via a private Frame-Relay network, and from the
DMV Headquarters location via a private DS3 serial connection. CSS is also accessible
via the EAI layer described below via XML web services.
4. Overview of Current DMV Enterprise Application Infrastructure (EAI)
DMV’s current EAI is a service-based architecture utilizing a variety of techniques. The
preferred mechanism to interact to DMV’s EAI is via web services. DMV provides highavailability services to the mainframe, databases, and a variety of other DMV systems.
Presently DMV utilizes Windows based servers as Presentation, Business Logic, and
Data Access servers. DMV Servers are secured based on current industry standards
provided by the NSA, SANS Institute, etc, as well as those published by VITA. Servers
are designed with standardization across all machines. DMV utilizes both physical and
virtual servers (VMWare ESX Server) based on need and activity.
Document and image management, storage, retrieval, and workflow services are provided
by Hyland Systems OnBase application.
DMV’s present enterprise database platform consists of a high-availability Oracle 10g
RAC 2 node cluster and a SQL Server 2005 failover cluster both utilizing fibre channel
storage.
The DMV Enterprise Application Infrastructure (DMV-EAI) is designed with security
and standardization as the core set of principles required to provide maximum uptime to
applications and customers.
July 2014
4
DMV’s present development environment for enterprise applications is based on the
Microsoft .NET development platform (VB.NET and C#).
5. Overview of Other Outlets
DMV has several outlets that utilize a combination of technologies defined above. These
outlets and systems provide core services to internal and external customers of DMV.
They are highlighted below and are not all-inclusive of all outlets, yet provide the
necessary sampling of technology implementation for reference purposes:
DMV Select: DMV Select allows selected business partners to provide core DMV
services to the citizens of the Commonwealth. They utilize a smart client application to
perform vehicle related transaction processing. Select offices utilize the public Internet
over a secure channel to access the core services available on CSS. The access is
provided by the EAI listed above to interact with CSS.
MCSC (Motor Carrier Service Center): The MCSC offices utilize a variety of
applications to perform their daily activities. They have access to CSCNet as well as
several intranet applications that interact with CSS via the EAI listed above. They utilize
a combination of smart client, intranet web applications and Powerterm to access CSS via
a…
Purchase answer to see full
attachment
