Running Head: Lab II – ICAT Prototype Product Specification
Lab II – ICAT Prototype Product Specification
Team Read
Abdulaziz A. Bin Taleb
CS411W
Janet Brunelle & G. H. Price
April 30th, 2014
Version III
1
Lab II – ICAT Prototype Product Specification
2
Table of Contents
1
INTRODUCTION .............................................................................................................................. 3
1.1
Purpose.......................................................................................................................................... 3
1.2 Scope ................................................................................................................................................... 4
1.3 Definitions, Acronyms, and Abbreviations......................................................................................... 4
1.4 References ........................................................................................................................................... 5
1.5 Overview ............................................................................................................................................. 6
2
GENERAL DESCRIPTION ................................................................................................................. 7
2.1
Prototype Architecture Description .............................................................................................. 7
2.2
Prototype Functional Description ................................................................................................. 9
2.3
External Interfaces ........................................................................................................................ 9
2.3.1
Hardware Interfaces .............................................................................................................. 9
2.3.2
Software Interfaces ............................................................................................................... 9
2.3.3
User Interface ........................................................................................................................ 9
List of Figures
Figure 1. Major Functional Component Diagram (MFCD) for the ICAT prototype……………..7
Figure 2. The Data Model of the ICAT prototype………………………………………...............8
Lab II – ICAT Prototype Product Specification
1 Introduction
Defining a problem is a very critical step of solving any issue. However, many people
forget to ask whether or not the underlying problem is being correctly addressed. Solving an
issue is often relies on ignoring the Type III errors, which is defined as obtaining the correct
answer for the wrong problem. The term Type III errors was first defined by Mitroff and
Featheringham back in 1974 (Yadav & Korukonda, 1985). This type of errors would often
results in a waste of resources and time.
Type III errors would often appear in more than 80% of human failures in organizations
and institutions. This frequent appearance has led to the introduction of the Interactive Context
Analysis Tool (ICAT). ICAT is a graphical tool that it was designed to reduce or eliminate the
risk of Type III errors.
1.1 Purpose
The purpose of the ICAT is to eliminate or minimize the risk of Type III errors. ICAT is
being developed for the System Engineer. ICAT is a graphical tool that will help the user to
visualize a problem domain. The problem domain will be modeled as a directed graph with the
problem’s Entities, which are objects within a data model that have a direct influence on the
problem domain. Furthermore, the user will have the ability to create Forces, which shows the
influence between Entities, and additional Entities for the problem domain. This will help the
user to visualize and have a better understanding of the problem domain. Eventually, the risk of
Type III errors will be reduced or eliminated.
(This space intentionally left blank.)
3
Lab II – ICAT Prototype Product Specification
4
1.2 Scope
The ICAT Prototype Structure will use the Model View Controller (MVC) design
principle. The ICAT Prototype Software can be categorized into three distinct elements, which
are the Analytic Engine, The Data Model, and the Controller. The Controller will maintain the
communications among the Graphical Interface, Analytic Engine, and the File System.
The ICAT Prototype will share the same features of the Real World Product (RWP).
Only the ICAT Prototype will have fewer features and capabilities than the RWP. The ICAT
Prototype will still have the capability to model a domain problem and produce the centrality
reports.
1.3 Definitions, Acronyms, and Abbreviations
Attribute: An Entity that represents some quality that exhibits an effect on other Entities
Entity: Object within a data model; types include: problem, stakeholder, objective, attribute, and
resource.
Force: Constraining or enabling Forces that show influence between Entities.
Influence: A measure of the effect that one Entity has on others in the system; also known as outcentrality.
Metadata: Data associated with Entities or Forces.
Objective: An Entity that represents a goal or target of the real world project.
Problem: An Entity that represents the issue or conflict that the solution is designed to address.
Project: The collection of metadata and associated diagram created by the user.
Prominence: A measure of the effect that other Entities in a system have on a specific Entity;
also known as in-centrality.
Resource: An Entity that represents a required good or service.
Lab II – ICAT Prototype Product Specification
Stakeholder: An individual or group affected in some way by the undertaking (Stevens Institute
of Technology, 2008).
Systems Approach: The application of a systematic disciplined engineering approach that
considers the system as a whole, its impact on its environment and continues throughout the
lifecycle of a project (Stevens Institute of Technology, 2008).
Systems Engineering: The orderly process of bringing a system into being using a systems
approach (Stevens Institute of Technology, 2008).
Type III Errors: The type of error described as “giving the right answer to the wrong problem”
(Kimball, 1957).
Workspace: The area within ICAT in which the user edits or views the project.
1.4 References
Bin Taleb, A. (Feb 12th, 2014). Lab I – ICAT Product Description. Old Dominion University
Kimball, A. (1957). Errors of the third kind in statistical consulting. Journal of the American
Statistical Association, 52(278), 133–142.
Stevens Institute of Technology. (2008). Core Concepts of Systems Engineering: Glossary.
Retrieved from The Center for Innovation in Engineering and Science Education:
http://www.ciese.org/curriculum/seproject/glossary.html
Yadav, S. B., & Korukonda, A. (1985). Management of Type III Error in Problem
Identification. Interfaces, 15(4), 55-61
(This space intentionally left blank.)
5
Lab II – ICAT Prototype Product Specification
1.5 Overview
This product specification provides the hardware and the software components of the
ICAT Prototype. Section 2 will provide a detailed description of the ICAT Prototype
architecture, a summary of the major functional components, and detailed information of the
external hardware and software required for the ICAT Prototype. Section 3 will provide the
functional requirements, assumptions and constraints, and the associated dependencies.
(This space intentionally left blank.)
6
Lab II – ICAT Prototype Product Specification
2
General Description
ICAT will be designed based on a standalone desktop application. It can be installed on
either a laptop or a desktop computer. ICAT primarily will be designed to work on the
Windows 7 operating system.
2.1 Prototype Architecture Description
The ICAT Prototype hardware architecture will be a single machine. The ICAT Prototype
Software Architecture will have a testing dashboard that will not exist in the real world product.
Figure 1 illustrates the ICAT Prototype Architecture components.
Figure 1: Major Functional Component Diagram (MFCD) for the ICAT Prototype
(This space intentionally left blank.)
7
Lab II – ICAT Prototype Product Specification
8
The Testing Dashboard is a very critical element during the development phase. It will
provide the developers with the necessary information for accurate results. Furthermore, the
Testing Dashboard will insure the efficiency of the ICAT product.
The Graphical Interface is where the user will interact with the ICAT. It will be categorized
into two parts, the Workspace, and the Dashboard. The Dashboard is where the user will open an
existing project or create a new one. The Workspace is where the user will model or edit the
directed graph of a problem domain.
The Analytic Engine is where the centrality reports are generated. It will have two sets of
algorithms, the in-centrality (Prominence) and the out-centrality (Influence). The user will have
the ability to choose either one of the centrality reports or both of them.
The Data Model component is where the Entities and Forces of a project are stored.
Furthermore, the Data Model will have the visual coordinates of every Entity in order to define
the visual representation of Each Entity. Figure 2 illustrates the Data Model of the ICAT
Prototype.
Figure 2: The Data Model of the ICAT Prototype
Lab II – ICAT Prototype Product Specification
2.2 Prototype Functional Description
The ICAT Prototype’s major functions are modeling a problem domain, and the centrality
reports. The user will model and edit a directed graph through the Graphical Interface of the
ICAT Prototype. Furthermore, the user will have all the necessary tools to model and edit the
diagram. Once the user creates the directed graph, the Analytic Engine will create the centrality
reports upon the user’s request.
Modeling a problem domain and the Centrality reports are the prime objectives of the
ICAT. Performing these two functions correctly will help the user examine every details of the
problem. Eventually, this will help eliminate or reduce the risk of Type III errors.
2.3 External Interfaces
The ICAT Prototype will only be limited to the User Interface. It will not require any
external Hardware or Software Interfaces. The ICAT Prototype will only need a single machine.
2.3.1 Hardware Interfaces
Not Applicable.
2.3.2 Software Interfaces
Not Applicable.
2.3.3 User Interface
The user will interact with ICAT through a regular monitor. The ICAT Prototype GUI
will display the outputs on the monitor. The user will need a keyboard to input the data into the
ICAT. A mouse will be needed in order to manipulate the graph.
9