Running Head: Lab1- STAT Product Description
Lab 1 – STAT Product Description
Blue Team
Christian Oakley
CS411
Janet Brunelle
October 1, 2013
Version 2
Lab 1: STAT Product Description
2
Table of Contents
1 INTRODUCTION ..................................................................................................................... 4
2 STAT PRODUCT DESCRIPTION ........................................................................................... 6
2.1 Key Product Features and Capabilities ............................................................................... 6
2.2 Major Components (Hardware/Software) ......................................................................... 10
3 IDENTIFICATION OF CASE STUDY .................................................................................. 11
4 STAT PROTOTYPE DESCRIPTION .................................................................................... 15
4.1 Prototype Architecture (Hardware/Software) ................................................................... 15
4.2 Prototype Features and Capabilities .................................................................................. 16
4.3 Prototype Development Challenges .................................................................................. 17
GLOSSARY ................................................................................................................................. 18
ACRONYMNS ............................................................................................................................. 18
REFERENCES ............................................................................................................................. 19
List of Figures
Figure 1. Manual stakeholder analysis example ........................................................................... 5
Figure 2. Classification Venn diagram ......................................................................................... 7
Figure 3. The recommended action matrix ................................................................................... 8
Figure 4. Stakeholder relationship map ........................................................................................ 8
Figure 5. Management plan .......................................................................................................... 8
Figure 6. STAT major functional components ........................................................................... 10
Figure 7. Prototype MFCD ......................................................................................................... 15
Lab 1: STAT Product Description
3
List of Tables
Table 1. Stakeholder classifications .............................................................................................. 12
Table 2. Stakeholder attitudes ....................................................................................................... 13
Table 3. Stakeholder relationships ................................................................................................ 14
Lab 1: STAT Product Description
4
1 INTRODUCTION
Every project aims to solve a problem. The keys to a problem lie within the entities
influencing the current situation and/or will be affected by the solution. These entities are known
as stakeholders. All aspects surrounding the project are in some way connected to various
stakeholders. They can be as largely important as the president of a company, or as minor to the
project as a supply truck driver. In any case, all stakeholders must be taken into consideration
when analyzing the project in its entirety. This can be accomplished by a method of examination
known as stakeholder analysis. Stakeholder analysis is the practice of evaluating a stakeholder’s
influence on a project based on various attributes such as the classification of a stakeholder, its
attitude towards the project, and its relationship among other stakeholders. (P. T. Hester).
Stakeholder analysis is not a new concept. It has been around for decades and is often
practiced by project teams starting at the analysis phase of the development life cycle.
Stakeholder analysis methods may vary from very complex to very simple with some much more
in depth than others. Regardless of the method, it is common practice to perform stakeholder
analysis manually (P. T. Hester). Project teams will brainstorm together and put their thoughts on
paper (Figure 1). Stakeholders and their information are written down, analyzed, and organized
to portray their relationships with one another and the influence they have on the project.
Unfortunately, stakeholders in systems problems seldom stay the same. Attitudes towards the
project may change and levels of influence fluctuate frequently. New stakeholders may also be
identified throughout the project duration. These changes may prove to be difficult to reflect in a
physical stakeholder analysis method without sacrificing organization and information
consistency. Any discrepancy, even the slightest, in stakeholder analysis could be disastrous to a
Lab 1: STAT Product Description
5
project. An electronic solution is needed to maintain the organization and proper analysis skills a
project needs to be successful.
Figure 1. Manual stakeholder analysis example
[This space intentionally left blank.]
Lab 1: STAT Product Description
6
2 STAT PRODUCT DESCRIPTION
The National Center for Systems of Systems Engineering (NCSOSE) has commissioned an
electronic version of their stakeholder analysis methods to be developed. This tool named
NCSOSE’s Stakeholder Analysis Tool (STAT) will incorporate their comprehensive methods of
analysis while also alleviating many of the problems associated with the currently popular
practice of manual stakeholder analysis. STAT will provide a dynamically changing visual
environment that can be accessed from a basic client computer. The design will be non-linear
and create a workflow where identification and attribute editing will not compromise project
consistency. Most important of all, STAT will implement the stakeholder analysis research of
NCSOSE that will feed into a proprietary algorithm and determine a stakeholder’s overall
influence on an individual project.
STAT will be a standalone application similar to other common desktop software such as
Word or Excel. The code will be generated in Java to ensure platform independence over various
operating systems including ports to portable devices. In keeping STAT as a single package
application, a database will not be utilized. Instead, projects will be saved on external XML files
with a .stat extension.
2.1 Key Product Features and Capabilities
The non-linearity of NCSOSE’s method of stakeholder analysis (SA) is a major focus of
STAT considering all the updates of information throughout the typical SA process. The
program will allow the addition of stakeholders at any time throughout the project duration. The
workspace area in STAT will capture the essence of this non-linear functionality by also
simplifying stakeholder editing. Stakeholders can be individually selected to display its
information and edited at any time.
Lab 1: STAT Product Description
7
One of the major features that will differentiate STAT from other analysis tools is the
collection of visual aids to reference the many processes in stakeholder analysis. A Venn
diagram structure (Figure 2) will help visualize the classifications that have been assigned to
each stakeholder. A recommended action diagram (Figure 3) will let the user see how a
stakeholder should be dealt with based on their classification and attitude. A stakeholder
relationship map (SRM) (Figure 4) will give the user an overview of the stakeholders involved in
the project. The visuals in the SRM will reflect each stakeholder’s classification, attitude, and
show how they are all related to one another. The final visual of STAT will be a stakeholder
management plan (SMP) (Figure 5) based on all of the collective information of the stakeholder
analysis throughout the project. This visual is less of a diagram and more of a synopsis and
guideline that will help project managers determine which stakeholders to focus their efforts on.
With stakeholder analysis information constantly updating, each visual will be able to conform to
every manipulation of a project and change its appearance accordingly. This will be
accomplished through the calculations of dynamic graphic encoding.
Figure 2. Classification Venn diagram
Lab 1: STAT Product Description
8
Figure 3. The recommended action matrix
Figure 4. Stakeholder relationship map
Figure 5. Management plan
Lab 1: STAT Product Description
9
The heart of STAT’s design is the analysis engine structure that will run in the
background. With each edit to a project, a particular process will be triggered to perform a
portion of the analysis aspect of the problem. The classification identification process will be
able to categorize each stakeholder based on three binary choices concerning the general
description of the stakeholder. The attitude identification process will label each stakeholder’s
attitude based on two binary choices that relate to the stakeholder’s view towards the project. A
relationship analysis algorithm will calculate relationship values by measuring the strength a
stakeholder has with each connected stakeholder. The products of the classification and attitude
identification will provide inputs to an overall project influence engine that will combine them
with each relationship value (P. T. Hester). The ending result will be a numerical value that
reflects a stakeholder’s influence on the project. This proprietary algorithm used to power the
project influence engine was developed by the engineers from NCSOSE.
Other small features are included in STAT to improve the overall user experience.
Aesthetic change options such as background color and font choices will be readily available to
assist with the visually impaired or simply conform to a user’s personal choice. These program
settings will be saved along with project information within the XML save file. All save files can
be optionally encrypted to enhance project security. Graphical tools for the various diagrams
such as the abilities to pan and zoom will also be included to refine visuals for projects of any
size. For users who have previously completed elements stakeholder analysis by methods other
than using the STAT program, stakeholder data will be able to be injected by user created scripts.
Lab 1: STAT Product Description
10
2.2 Major Components (Hardware/Software)
STAT is being designed to be a simple desktop application. The software and hardware
involved are not sophisticated and will not require any special technology to function. The
hardware required solely consists of a client computer. At this moment the minimum required
computer specifications are unknown and will not be determined until testing is complete. The
software aspect of STAT is comprised of the analysis engines and an embedded database that
will output information to XML data files. The user will be able to interact with STAT through a
graphic user interface (GUI). The entirety of the software will be programmed in Java to create
the standalone, platform independent, Java application STAT is designed to become.
Figure 6. STAT major functional components
[This space intentionally left blank.]
Lab 1: STAT Product Description
11
3 IDENTIFICATION OF CASE STUDY
The design of the STAT program is based on the extensive research accomplished by the
system engineers of NCSOSE. This research center focuses on the study and development of
new methodologies and technologies in system’s theory. One of the current projects is the focus
of new decision making efforts in the world of stakeholder analysis. A paper describing their
methodology by Patrick Hester, Joseph Bradley, and Kevin Adams was published in 2013 titled
“Stakeholders in Systems Problems”. This research combines the previous studies of R.
Freeman, R. Mitchell, G. Savage, and other researchers in the field of stakeholder analysis and
furthers the research by adding newly developed NCSOSE discoveries. The NCSOSE
stakeholder analysis method consists of first identifying each relevant stakeholder and then
analyzing three aspects of each one: classification, attitude, and relationships with other
stakeholders. The final product of this method is a management plan that summarizes the project
information and provides a recommended plan of action (P. T. Hester).
The NCSOSE methodology’s initial starting point is the identification of relevant
stakeholders. This is sometimes known as the “brainstorming” step. The goal of this activity is
to quickly identify participating stakeholders while refraining from in-depth analysis. To help
differentiate the relevancy of the identified stakeholders, the individual wants of each
stakeholder are also identified. In every problem, every stakeholder will affect or be affected by
the outcome of the project. It is important to identify each want and eventually put forth effort to
appease or compromise as much as possible to ensure the project’s success. Once all the
stakeholders and their wants have been identified, the analysis processes can begin.
The foundation of NCSOSE’s stakeholder analysis research extends the initial
groundwork set forth by Freeman in 1984. This work was later expanded by Mitchell, Agle, and
Lab 1: STAT Product Description
12
Wood in 1997 who introduced the concept of categorizing stakeholders into various classes
based on their attributes. The three attributes are power, legitimacy, and urgency and should be
measured in relation to the current project being developed (Mitchell). Either a stakeholder has
an attribute or does not have it. This leads to the possibility of the stakeholder being classified in
one of four different classes (Table 1).
Table 1. Stakeholder classifications
[This space intentionally left blank.]
Lab 1: STAT Product Description
13
The NCSOSE analysis method of determining a stakeholder’s attitude is derived from the
research of Savage, Nix, Whitehead, and Blair in 1992. They determined that a stakeholder’s
attitude can be placed in one of four categories (Table 2) based on the stakeholder’s potential of
threat to the project and the stakeholder’s potential of cooperation with the project (Savage). The
importance of realizing a stakeholder’s attitude is essential to eventually determining a
recommended strategy of engagement. Savage, Nix, Whitehead, and Blair determined four
strategies based on matching the stakeholder’s classification with their attitude (Figure 3).
NCSOSE added a fifth action to deal with stakeholders with little to no significance towards the
project (P. T. Hester). Stakeholders with little to no significance must also be taken into
consideration as their amount of influence may change throughout the course of the project.
Table 2. Stakeholder attitudes
Once the identification process has been completed and the classifications and attitudes
of each stakeholder has been determined, there is still a high chance the overall influence of each
stakeholder will be hard to distinguish from one another within the project. The levels of
influence need to be more unique to eventually create a precise management plan. Therefore, the
relationships between stakeholders (Table 3) must also be analyzed (P. T. Hester). The direction
and strength of every relationship a stakeholder has with other stakeholders are combined with
the information obtained from the classification and attitude analysis steps. Using an algorithm
developed by NCSOSE, the overall amount of influence a stakeholder has on the project can be
Lab 1: STAT Product Description
14
determined. Once each stakeholder’s level of influence has been determined, an accurate and
detailed management plan may be developed.
Table 3. Stakeholder relationships
The resulting product of the identification process and three analysis steps is a
recommended plan of action known as the stakeholder management plan (SMP). This synopsis
combines all of the information about each stakeholder and lists them in an organized matrix-like
visual (P. T. Hester). The rows of this matrix are comprised of the involved stakeholders. The
columns of the matrix consist of the name, wants, classification, attitude, influence, and strategy
which have been derived from the identification and analysis steps. Other columns are also
added to further assist the project managers with stakeholder management. These columns are:
method of engagement, proximity of engagement (Last Engaged), responsible party, and notes
(Figure 5). By default, the matrix is in descending order by their strategy but it is important to be
able to sort the matrix by other columns depending on the project team’s task at hand. Every
change in the overall analysis of the project’s stakeholders will change the SMP and could
potentially render a project management plan useless. Therefore, the SMP must be constantly
updated to incorporate these changes.
Lab 1: STAT Product Description
15
4 STAT PROTOTYPE DESCRIPTION
The stakeholder analysis and management (SAM) requirements have been identified
through multiple meetings with the project mentors from NCSOSE. The five steps
(identification, classification, attitude, relationships, and management) described in the NCSOSE
stakeholder analysis methodology (P. T. Hester) will be the main focus of creating a functional
prototype. Every project will also have the ability to encrypt the .stat XML data files. This will
heighten the security measures of any project that requires restricted access.
4.1 Prototype Architecture (Hardware/Software)
STAT will be programmed in the Java programming language. This will be accomplished
by utilizing Oracle’s Java Virtual Machine (JVM) on the individual client computers of the
development team. Five main areas of focus will comprise the architecture: the GUI, test
modules, SAM processes, project settings, and an XML based file format (Figure 7). The GUI
and visuals will be powered by various features of the Java swing API. The SAM processes will
be tested by a built in stakeholder generator and external XML files that will provide input to the
algorithms. Project settings will be developed in concurrence with the XML file format.
NCSOSE has expressed the desire to also use real data from actual previous stakeholder analysis
projects to compare results.
Figure 7. Prototype MFCD
Lab 1: STAT Product Description
16
Little hardware is required for the development of the STAT prototype. Being a
standalone desktop application, there is no need for a centralized server or external database. The
majority of work will be performed on the development team’s personal computers as mentioned
earlier. A virtual lab computer provided by the ODU computer science department will be set up
with an Ubuntu operating system strictly to act as a repository for the development team. Using
this setup, the development team should be able to focus on different areas of the program
simultaneously and maximize the permitted development time allotted.
4.2 Prototype Features and Capabilities
The STAT prototype will not differ too much from the real world product. The NCSOSE
designed method of identification and stakeholder analysis will be identical. The visual
representations of the SAM steps will also appear similar though perhaps less enhanced
graphically. Basically, all of the functionality of the five-part SAM process will be included in
the prototype. The program specific elements such as XML exportation, user settings, and
encryption options will also match the real world product (RWP) implementation. The vision of
STAT’s prototype design is to create a fully functional product with minor appearance changes
from the RWP.
The major difference between the STAT prototype and the RWP are the testing modules
that will be included in the prototype development. It is important to ensure the STAT design is
able to handle any discrepancy in functionality. Inner and outer input testing will be included to
test the limits of STAT project control. Inner testing will be performed by a built-in module that
will generate randomized stakeholders. They can also be modified to contain specific attributes
for testing the limits of the SAM processes. Outer testing will be accomplished by loading
Lab 1: STAT Product Description
17
external .stat files into the program. These files will be developer created, each with a focus to
check on situational error handling.
4.3 Prototype Development Challenges
The STAT prototype is being built as a standalone software product for client computers.
In theory, the design should allow for compatibility with mobile devices but it is not the focus of
the prototype development to ensure perfect mobile portability. The test modules will focus on
the functionality of the SAM processes as they perform on the developers’ client computers.
These tests may not cover any problems that may occur when porting to mobile operating
systems.
The encryption process will be a developer designed function to help enhance security
when needed. This will be a password controlled process that manipulates the XML bound save
data to be unintelligible. As with any other encryption process, the patterns may be potentially
deciphered and all encrypted STAT save files could be compromised. Encryption does add an
extra sense of security for STAT users but cannot guarantee complete confidentiality.
[This space intentionally left blank.]
Lab 1: STAT Product Description
18
GLOSSARY







Attributes - Attributes describe the stakeholder. These are defined as power, legitimacy,
and urgency.
Entity - An individual or organization involved in a project.
o Stakeholder
Project - A collaborative effort to accomplish a common goal.
o An effort to solve a problem
Relationship - The manner in which two entities are associated.
o Connection
o Link
Stakeholder - Someone who can affect or is affected by the achievement of the
organization's objectives.
o Anyone with an interest in a project
o Can be individuals or organizations
o Interests may be affected by project execution
o Have an influence over project objectives and outcomes
o Entities
User - Potential operator of the STAT software.
o Problem Solver
Visuals - Various methods that show information graphically.
o Display
ACRONYMNS












GUI – Graphical User Interface
JVM – Java Virtual Machine
MFCD – Major Functional Component Diagram
NCSOSE – National Centers for System of Systems Engineering
ODU – Old Dominion University
RWP – Real World Product
SA – Stakeholder Analysis
SAM – Stakeholder Analysis and Management
SMP – Stakeholder Management Plan
SRM – Stakeholder Relationship Map
STAT – Stakeholder Analysis Tool
XML – Extensible Markup Language
Lab 1: STAT Product Description
19
REFERENCES
Hester, P. T., Adams, K. M. "STAT development meeting." 2 April 2013.
Hester, P. T. "STAT development meeting 2." 26 April 2013.
Hester, P. T., Bradley, J. M., & Adams, K. M. "Stakeholders in Systems Problems. File last
modified 3 April 2013." 2013. Microsoft Powerpoint File.
Hester, P. T., Bradley, J. M., & Adams, K. M. "Stakeholders in systems problems." International
Journal of System of Systems Engineering, 3(3/4) (2012): 225-232.
Mitchell, R. K., Agle, B. R., & Wood, D. J. "Toward a theory of stakeholder identification and
salience: Defining the principle of who and what really counts." Academy of Management
Review, 22(4) (1997): 853-886.
Savage, G. T., Nix, T. W., Whitehead, C. J., & Blair, J. D. "Strategies for assessing and
managing orgainizational stakeholders." The Executive, 5(2) (1991): 61-75.