INFORMATION SYSTEMS PLAN

F.A.T.
Feedback Analysis Tool

submitted to
Dr. Erlan Burk
IS316 – Computer Systems Analysis & Design II
Park University

submitted by
Mike Quezada
Park University
IS316 Mike Quezada Feedback Analysis Tool

TABLE OF CONTENTS

I. System Description 3

II. Functional Description 5

III. Data Dictionary and Entity Relationships 6

IV. F.A.T. Data Level Diagram 7

V. F.A.T. Diagram 0 8

VI. System Input, Output Forms, and Interfaces 9

2
IS316 Mike Quezada Feedback Analysis Tool

SYSTEM DESCRIPTION

System Name: Feedback Analysis Tool

Project Description: This system will allow an organization to more efficiently and effectively
channel constructive criticisms and general feedback to the proper team during any projects
stage up to and including through maturation. As inputs are received, they will be processed
and retrieved by the team that controls that part of the project being analyzed. For instance, if
I have input as to the accuracy of my Sig Sauer Rifle, I don’t want my feedback to go to the optic
division, or the ammunition division, or the stock maker, or the trigger assembly team. While
these all play a role in my rifle’s accuracy, I want to talk to the barrel production folks first.

Type of System: The F.A.T. will be web based designed upon HTML framework. I see lots of
java in this system. Also, I’m thinking that MySQL will be employed with this system.

Key Benefits: A simplified, user intuitive and easy to use browser-based web GUI will simplify
the task of reporting and assessing the proper routing of feedback. Leaders and reviewers will
be able to ascertain an organizations ability to review, asses and then either implement or
simply store the feedback into some type of feedback repository.

Interrelations/Interdependencies:
 The system will be easily assessable via any internet capable device.
 Can be modeled to work independently if no other reporting systems are used by an
organization.
 The system can either be stored via cloud or local server.

Replacement/Upgrade: This system will be a replacement of currently existing reporting and

assessment systems.

Stakeholders:
 Any organization that implements/integrates the FAT system.
 The developers and maintainers of the FAT system.

Users:
 Any organization that deems it prudent to streamline their customer feedback processes.

3
IS316 Mike Quezada Feedback Analysis Tool

Functional Description

System Functions:
The F.A.T. is a solution meant to answer a project manager’s question of how to best
leverage indigenous talent to streamline and focus product developmental efforts. The system
will allow users to capture inputs from developers and users and convert these into real time
process injects. The system will also allow downstream team developers to adjust their
process(es) to better integrate with the revisions of the upstream development teams.

System boundaries:
The F.A.T. will be hosted on a local server that will be solely accessible by properly
credentialed personnel. The server can be hosted locally or geographically separated.

System interfaces external to the organization:

As of now, there will be no means to access the F.A.T. from an external resource.

System interfaces internal to the organization:

The F.A.T. support files and application files will reside on the internal server. This
interface will be secure. The system will be managed by properly vetted technicians and
operators.

How the system relates to the organizational mission:

The intent of the F.A.T. is to seamlessly integrate and operate with any organizations
feedback process. As any competitive organization desires to reduce waste and increase
efficiency, the F.A.T. will be a perfect complement to a company’s product management team
in that it (the F.A.T.) is designed to be a tool purposely designed for this role.

Organizational decisions the system must support:

The F.A.T. provides managers with a tool to not only hear and grasp of adjustments that
might be needed, but also help these managers in accepting and implementing and driving the
adjustments required for product/project maturation.

Information processing

Information input to the process:

The information that will be required to be input to the F.A.T. system will be the user’s
information (e.g. User ID, date/time input/input source [e.g. from developer, user,
manager, etc.]), team which controls the process that input should best be routed to
and, other pertinent product data deemed prudent by the company.

Process definition and information output:

Results of the product/process inputs. Where the inputs valid and implemented?

4
IS316 Mike Quezada Feedback Analysis Tool

CASE tool used for development:

The Visible Analyst CASE tool will be used to create the system diagrams needed to
design and explain the F.A.T. system.

5
IS316 Mike Quezada Feedback Analysis Tool

Data Dictionary and Entity Relationships

Data Dictionary

Data Special
Data Element Name Type Size Formatting Definition
FAT input_firstname A 20 none Base element
FAT input_lastname A 30 none Base element
FAT_userid A 8 none Base element
FAT_email AN 50 none Base element
phone AN 14 (###) ###-#### Base element
Street AN 20 none Base element
City A 10 none Base element
State A 20 none Base element
Zip N 5 ##### Base element
birthday D 7 DDMMMYY Base element
input_id N 8 none Auto-generated
input_entered A 2000 none Base element
date_entered D 7 DDMMMYY Auto-generated
date_closed D 7 DDMMMYY Auto-generated

Legend:
A – alpha N – numeric # - numbers AN - alpha-numeric
D- date

initiator record = initiator_firstname +

initiator_lastname +
initiator_email +
initiator_phone +
initiator input id

request_status = [new | in progress | complete]

completed_review = request_record +
customer_record +
process_revised +
date_closed

email_notification = customer_name +
customer_userid +
request_id +
request_status +
date_closed

6
IS316 Mike Quezada Feedback Analysis Tool

Context Level Data Flow Diagram

7
IS316 Mike Quezada Feedback Analysis Tool

Feedback Analysis Tool Diagram 0

8
IS316 Mike Quezada Feedback Analysis Tool

System Input and Interfaces

Screen 1, the New User Feedback Form, is the first user interface screen. New and returning
users will create an account that gives them access to the user input screen.

9
IS316 Mike Quezada Feedback Analysis Tool

System Input and Interfaces

Continued

Screen 2, this is the actual feedback input screen. This screen asks the user for pertinent and
prudent data about the product that the user felt required some type of feedback. The
information submitted with this form becomes the source of the request record and can be
included in an email that is generated and sent to the customer when the request is generated.

10
IS316 Mike Quezada Feedback Analysis Tool

System Input and Interfaces

Continued
Example of captured data
This is a sample report managers can pull to review feedback requests and status.

Date Initiated Request ID Customer Name Feedback Area Date Reviewed

02/16/2019 0000001 Schmagagee I B Product 02/16/2019

02/18/2019 0000002 Schmagagee U R Product 02/19/2019

02/19/2019 0000003 Warhammer I B Product 02/20/2019

11
IS316 Mike Quezada Feedback Analysis Tool

System Input and Interfaces

Continued

Sample System generated e-mail

This could be a sample email generated from the system and populated with the information
the FAT receives when they feedback initiators (customers) submit their requests into the
system. The receipt of this email lets the customer know that their request has been submitted
successfully.

Date: date_entered

Dear customer_firstname customer_lastname,

“Your feedback to Some Schmagagee Widget Company has been submitted successfully.
We at Some Schmagagee Widget Company are committed to providing you, the customer with
the best possible product. We will evaluate your feedback and update you as we process your
feedback. Here are the details of your request”.

customer_ID feedback_status
date_entered date_reviewed
port_number protocol_name

This is an automatically generated email, please do not reply.

Thank you.

Some Schmagagee Widget Company

12