USA: +1(669)289-8683 
Sign in
I have already completed the Stage 1, which i am also attaching for the guide. DFD Tips file is for Stage 2, and I am also attaching the case study. Attachment 3 is a case study
YOU CANNOT USE AI TO SOLVE THIS-CHECK BEFORE BIDDING
IFSM 461: Systems Analysis and Design
Precision Electronic Parts, Inc.
Case Study
Introduction
This case study will be used for a series of staged assignments. It should be thoroughly read and
understood prior to working on any of the assignments.
Setting
Precision Electronic Parts (PEP), Inc., is a small private business that has retained you to assist in the
development of a new billing and payment system and associated processes.
Background
PEP is a small, private specialized electronics company in Kansas. For the past 20 years, it has
manufactured a wide range of precision electronic components and replacement parts for medical
equipment used in hospitals, doctor’s offices, and pharmacies. Last year, the company began building
and delivering custom low voltage motors that reduced electricity costs and made older medical
equipment more environmentally friendly. More recently, PEP has added a new line of more efficient
low voltage motors that can be used in precision equipment outside the healthcare industry.
As a result, PEP is experiencing significant increases in orders for the motors. The manufacturing facility
has been expanded, and the sales and marketing teams have been enlarged. All of this is straining the
Ordering & Shipping Department and the Inventory Management Department, which have received no
increase in personnel. They are meeting the challenge, but the Executive Leadership Team (the CEO,
COO, CFO, and CIO) know that they are only treading water. The Finance Department, however, is
getting further and further behind in their invoice, billing and payment processes. The Business
Administration Department has stepped up to the task, but is at the breaking point.
IT Steering Committee
The IT Steering Committee (ITSC) at PEP is comprised of the Executive Leadership Team, the Senior Vice
President and Vice President.
• Carolyn West is the Chief Executive Officer (CEO). She has been at the company for 11 years. Carolyn
has a background working for and managing electronics companies. Like most CEOs, Carolyn is focused
on the strategic and long-term business health of PEP. She chairs the IT Steering Committee. Carolyn
and the committee members jointly make decisions about IT systems and major organizational business
process changes.
• Tim Uduak, Jr. is the Chief Operating Officer (COO) and the son of founding partner Tim Uduak, Sr. Tim
has been around the company since its inception in one capacity or another, except for four years of
college and a 3-year break to startup his own company. When his startup failed, Tim came back to PEP
as the SVP, Engineering & Manufacturing Operations. Last year, he was promoted to COO. While Tim has
PEP Case Study
1
a strategic focus and is not technology averse, he prefers to solve business challenges with processes
rather than information technology.
• Karl Manley is the Chief Financial Officer (CFO). He has been with the company for 9 years. Karl has a
background in accounting and finance, and is a certified public accountant (CPA). He tends to focus on
the company’s financial health to the exclusion of all other business concerns. While Karl is technology
fluent, he resists new IT purchases unless there is a clear and direct connection made between the
technology investment and improving the company’s financial profile. The Director, Accounts Receivable
(Mary Winston) and the Director, Accounts Payable (Amy Dole) report to the CFO, and together are
responsible for the financial operations of the business.
• Mark Temple is the Chief Information Officer (CIO) and head of the IT Department. He provides all IT
services to PEP. Prior to being hired as the CIO, Mark was an IT manager at a large multi-national
corporation responsible for providing IT services to their offices from the headquarters in Lincoln,
Nebraska. While in that position, Mark participated in very structured IT processes, and developed an
appreciation for working with the operational and management divisions to ensure success of IT
projects. When he arrived at PEP, he advised the CEO, COO and CFO that an IT Steering Committee
could help ensure they pursued the most beneficial IT projects. He is your primary point of contact for
dealing with PEP in analyzing their processes and systems.
• Susan Black is the Senior Vice President (SVP), Engineering & Manufacturing Operations and is Tim’s
replacement. Susan has worked for the company for 13 years. She started as a Senior Engineer, and
after six years was promoted to Director, Engineering, where she spearheaded the successful research
and development of the low voltage motors. Susan is a champion of information technology as long as it
is clearly focused on the core business.
• Jason Udo is the Vice President (VP), Business Administration. He oversees all departments, except
Engineering & Manufacturing, Finance, and IT. His responsibilities include key support functions such as
Sales, Marketing, Ordering & Shipping, Inventory, and Human Resources.
The ITSC has adopted the IT governance processes recommended by the CIO. They review proposals for
IT investments and determine where to invest their limited funds. Each of the members has particular
areas of interest, but all of them are focused on reducing the overall cost of running the business,
increasing sales, and managing the cost of IT for the company. The ITSC has established a series of
checkpoints at which they make go/no-go decisions on IT projects. At these decision points the
following documents are reviewed by the ITSC:
Preliminary Investigation Report – describes the problem/opportunity, identifies benefits of
a new system, and reports on various aspects of feasibility of the proposed project.
Requirements Specification – documents the requirements to be fulfilled by the proposed
system.
Systems Design Specification – translates the requirements into a logical design for the
proposed system.
Final System Report – compiles previous documents and lays out the way ahead if the
project is approved and funded.
PEP Case Study
2
As each report is approved, work on the following step begins. This controls the amount of time and
effort put into a request for a system. For example, if the Preliminary Investigation Report is not
accepted by the ITSC, no further work is performed on the system proposal.
Your Task
You are an independent Business and IT Systems Analyst, specializing in developing IT solutions for small
business needs. You have been contracted by the CIO to prepare the documentation required for the
ITSC as they consider replacing the information systems associated with operations, business
administration, and finance. Due to the backlog in the billing and payment processes, the ITSC wants to
start by replacing the current customer billing and payment system and processes. However, the ITSC
requires assurance that a new billing and payment system and processes can be interfaced with other
new IT systems and updated business processes as needed. While there is currently no money in the
budget allocated to replacing or upgrading these systems, the executives are committed to moving the
company forward and improving PEP’s ability to manage its growing business efficiently and effectively.
Your Activities
After interviewing each member of the ITSC, you have collected the following information regarding the
invoice, billing and payment processes and needs:
• Customer billing is handled by the Invoicing Department, which reports to the VP, Business
Administration.
• Customer payments are handled by the Accounts Receivable Department, which reports to
the
CFO.
• Customer billing and payments are managed and recorded in an in-house developed Microsoft
Access based solution. The solution was developed by the IT Department and is housed on a
server controlled and managed by the IT Department. The solution is updated on request from
the Invoicing and Accounts Receivable Departments.
• The Sales Department works with Invoicing to establish new customer accounts and update
and close existing accounts as needed.
• The Ordering & Shipping Department sends a monthly report to Invoicing where the products
ordered and shipped and their codes are entered into the invoicing module. Pricing is computed
based on the product codes and quantities entered.
• Invoicing is responsible for adding, updating, and maintaining the product codes and pricing
used by the invoicing database on the 15th of each calendar month. The monthly report
containing the updates is provided by the Marketing Department.
• Invoicing generates and mails customer bills on the last business day of each calendar month.
• Customer payments (lump sum) are due by the 10th of each calendar. Customers send the
payments to Accounts Receivable. Accounts Receivable is responsible for updating customer
account records when the payments are received.
• Invoicing is responsible for identifying accounts that are 30 days, 60 days or more overdue.
These reports are sent to Accounts Receivable and Sales. Accounts Receivable handles all
collections.
• There is a 2% fee added to all invoices that are 30 days or more overdue.
PEP Case Study
3
• Accounts Receivable notifies the Sales Department to assist with customers who are 60 days
or more delinquent. Ordering & Shipping is also notified so that no further shipments are made
until the outstanding invoice is paid in full. These situations are rare.
• Installation services are offered as a fixed price fee for small businesses (doctor’s offices,
individually owned pharmacies, etc.). Larger installations (hospitals, chain pharmacies,
pharmaceutical manufacturers, etc.) are billed on a pre-defined hourly rate.
• Volume discounts are not currently offered, but Marketing is planning to offer this discount
within the next six (6) months because the low voltage motors are increasingly being ordered in
quantities of five (5) or more. The following volume discounts will be offered:
o 5 or more: 2%
o 10 or more: 5%
o 25 or more: 10%
• Electronic invoicing via email is not currently offered, but Marketing and Invoicing plan to offer
this feature within the next six (6) months.
• Electronic payment to a lockbox account is not currently offered, but Marketing and Accounts
Receiving plan to offer this feature within the next six (6) months.
• The customer account data elements currently include:
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Primary Contact First Name
o Primary Contact Last Name
o Primary Contact Phone Number
o Primary Contact Email Address
o Secondary Contact First Name
o Secondary Contact Last Name
o Secondary Contact Phone Number
o Secondary Contact Email Address
o Products Ordered
o Product Ordered Date
o Products Shipped
o Product Ship Date
o Quantity
o Product Pricing
o Calculated Price (Calculated Field)
o Amount Due (Calculated Field)
o Amount Paid
o Date Paid
o Amount 30 Days Overdue (Calculated Field)
o Amount 60 Days Overdue (Calculated Field)
o Amount Greater Than 60 Days Overdue (Calculated Field)
o 2% Overdue Amount (Calculated Field)
• The customer account data elements required for near-term plans include:
PEP Case Study
4
o Quantity Discount (Calculated Field)
o Electronic Invoicing (Check Box)
o Electronic Payment (Check Box)
• Paper invoices currently contain the following data elements:
o Unique Serialized Invoice Number (System Generated?)
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Products Ordered
o Product Ordered Date
o Products Shipped
o Product Ship Date
o Quantity
o Product Pricing
o Calculated Price (Calculated Field)
o Amount Due (Calculated Field)
o Amount 30 Days Overdue (Calculated Field)
o Amount 60 Days Overdue (Calculated Field)
o Amount Greater Than 60 Days Overdue (Calculated Field)
o 2% Overdue Amount (Calculated Field)
• Paper invoice data points required for near-term plans include:
o Volume Discount (Calculated Field)
o Electronic Invoicing (Yes or No)
o Electronic Payment (Yes or No)
• When electronic invoices are offered, the same current and near-term data elements as
shown above will be included.
You have also documented the following additional considerations:
• All customer, invoicing, and payment data must be secured, but accessible to those
departments and personnel who have a need to know.
• PEP requires the ability to generate a receipt automatically at the time payments are
recorded. The receipt will be sent electronically to the organization’s primary contact email
address. The receipt must contain:
o Unique Serialized Invoice Number
o Customer Organization Name
o Customer Street Address
o Customer City
o Customer State
o Customer Zip Code + 4
o Amount Paid
o Date Paid
PEP Case Study
5
o Amount Outstanding
• The following company entities need to be able to generate their own reports as needed:
o COO
o CFO
o Director, Accounts Receivable
o Accounts Receivable Managers & Staff
o Director, Accounts Payable
o SVP, Engineering & Manufacturing Operations
o VP, Business Administration
o Invoicing Managers & Staff
o Sales Managers & Staff
o Marketing Managers & Staff
o Ordering & Shipping Managers & Staff
Your Deliverables
Your first task is to develop the Preliminary Investigation Report (PIR), which will examine the
problems/opportunities, identify benefits of a new system, and report on various aspects of feasibility of
such a project. You will draw upon the background and other information provided above to develop
the PIR. If that Report is accepted by the ITSC, you will analyze and organize the requirements you have
collected into a Requirements Specification. After receiving approval of the Requirements Specification,
you will develop the Systems Design Specification, which will translate the requirements into a logical
design of the proposed system. With a further decision to proceed, you will then develop the Final
System Report, which will combine your previously developed documents and lay out the way ahead if
the project is approved and funded.
PEP Case Study
6
Stage 4: Final System Report
Before you begin this assignment, be sure you have read the Case Study and the feedback you received
on your first three staged assignments.
Purpose of this Assignment
This assignment gives you the opportunity to explain and justify a system proposal to gain approval to
proceed with the project. This assignment addresses all of the course outcomes to enable you to:
•
•
•
•
plan, build, and maintain systems that meet organizational strategic goals by demonstrating the
use of enterprise architecture and applying enterprise governance principles and practices need
assessment
apply a systematic approach to translate requirements into an executable systems design
effectively communicate with stakeholders to determine, manage, and document business
requirements throughout the SDLC
perform modeling to assist with analysis and decision making
Assignment
The proposed systems design is documented in the form of a Final Systems Report. This report defines
objectives and how the proposed system design will satisfy them. The primary purpose of the report is to
inform and gain approval to proceed with the project. It should be presented in terms that management
and users understand. The Final System Report will be compiled from the previously submitted Staged
Assignments, supplemented with information about implementation personnel requirements and time and
cost estimates. Rather than paste together all of the previous assignments, the outline below should be
followed and will require you to re-arrange sections of the previous assignments.
All of the information you need to complete the projects in this class is not provided in the case study. In
the discussion area of the classroom, there is a discussion titled “Case Study Interview Questions” where
you can pose questions about the case study, as if you were interviewing the people in the case study
organization. Any information that you need that is not included in the case study should be asked about
in this discussion. Responses from the faculty member on behalf of the case study organization will be
available for everyone in the class.
Use the case study and the Case Study Interview Questions discussion, your previously submitted staged
assignments (including the feedback received), and resources and source documents (previously
submitted documents, as corrected) listed below to create a Final System Report in the format provided.
Note that sections are re-organized and some paragraphs may need to be re-written using earlier content
but presented as required here. Items highlighted in yellow indicate sections that need to be added to or
created for this Report.
Final System Report
I.
II.
Introduction to the full systems study. (This section will come from your Stage 1: Preliminary
Investigation Report, re-written or re-organized as appropriate.)
A. An overview of the events leading up to the study
B. The subject of the study
C. The objective and scope of the proposed system
D. A statement of recommendations and justifications for the proposed system
Description of the current process/system (This section will come from your Stage 1
Assignment: Preliminary Investigation Report.)
A. A brief description of the current process or the current system and how it is used
B. The purpose of the current process or system
C. The problems with the current process or system and the rationale for a new system
III.
IV.
V.
D. The operating cost of the present system, if applicable
Description of the proposed system (Sections A-E will come from your Stage 1 Assignment:
Preliminary Investigation Report; other sections from sources as indicated.)
A. An overview of the proposed system
B. The scope of the project
C. The tangible and intangible benefits of the proposed system
D. Feasibility Analyses
E. Time and cost estimates to implement the proposed system
F. Requirements Checklist (Stage 2 assignment: Requirements Specification)
G. Data Models (Stage 2 assignment: Requirements Specification)
H. Process Models (Stage 2 assignment: Requirements Specification
I. System Design Specification (Stage 3 assignment: System Design Specification)
J. Recommended Acquisition Strategy – Respond to each of the following and provide brief
explanations of your choices. (New, to be developed) [Week 6 Content reading on
Acquisition Strategy]
i. Identify scope of what to buy
1. Product or service?
2. Commercial-off-the-shelf or custom?
3. Use in-house or contractor support?
ii. Select hosting alternative (dedicated servers, data center, or cloud computing)
K. Implementation Plan (New, to be developed)
i. A list of personnel needs to develop, install and maintain the new system
ii. A proposed timetable for installing the proposed system and staff-hours required
to complete the project
Financial Information
A. The operating cost of the present system, if applicable (from Stage 1)
B. The estimated implementation cost of the proposed system (from Stage 1; updated with
any new information)
C. The estimated operating cost and the estimated useful life of the new system (New, to
be developed)
D. The tangible and intangible benefits of the proposed system (add to those listed in Stage
1 to include financial benefits)
Summary – A summary with a positive statement for implementing the proposed system. The
summary should include any concerns about the timetable, funds, software, hardware, or
personnel available for the project. (New, to be developed)
Submitting Your Assignment
Submit your document via your Assignment Folder as Microsoft Word document, or a document that can
be ready using MS Word, with your last name included in the filename. Use the Grading Rubric below to
be sure you have covered all aspects of the assignment.
GRADING RUBRIC:
Criteria
Introduction
Current
Process or
System
Proposed
System
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above
Standards
Above Standards
Meets Standards
Below Standards
Well Below
Standards
9-10 Points
8 Points
7 Points
6 Points
0-5 Points
Introduction
includes a wellwritten overview of
events and subject
of the study,
objective and
scope,
recommendations
and justification of
the proposed
system, is derived
from the Case
Study, and
demonstrates a
sophisticated level
of writing.
14-15 Points
Introduction
includes an
overview of events
and subject of the
study, objective
and scope,
recommendations
and justification of
the proposed
system, is derived
from the Case
Study, and
demonstrates a
clear understanding
of the course
concepts.
12-13 Points
Introduction
includes an
overview of events
and subject of the
study, objective
and scope,
recommendations
and justification of
the proposed
system, and is
related to the
Case Study.
Introduction may
not include an
overview of
events and
subject of the
study, objective
and scope,
recommendations
and/or
justification of
the proposed
system; and/or
may not be
derived from the
Case Study.
Introduction,
or significant
portions of the
introduction,
not included,
or
demonstrates
little effort.
10-11 Points
9 Points
0-8 Points
The description of
the current process
or system includes
what its purpose is
and how it is used,
the problems and
rationale for a new
system, and current
operating costs.
These are clearly
stated, are
convincing, and are
logically derived
from the Case
Study, and
demonstrate a
sophisticated level
of writing.
27-30 Points
The description of
the current process
or system includes
what its purpose is
and how it is used,
the problems and
rationale for a new
system, and current
operating costs.
These are clearly
stated and are
logically derived
from the Case
Study, and
demonstrate
effective writing.
The description of
the current
process or system
includes what its
purpose is and
how it is used, the
problems and
rationale for a new
system, and
current operating
costs.
The description
of the current
process or
system may not
include all of:
what its purpose
is and how it is
used, the
problems and
rationale for a
new system, and
current operating
costs.
The
description of
the current
process or
system is not
provided, is
very minimally
provided, or
little effort is
demonstrated.
24-26 Points
21-23 Points
18-20 Points
0-17 Points
The description of
the proposed
system contains all
the requisite
sections from
Stages 1, 2 and 3,
and the acquisition
strategy and
implementation
The description of
the proposed
system contains all
the requisite
sections from
Stages 1, 2 and 3,
and the acquisition
strategy and
implementation
The description of
the proposed
system contains all
the requisite
sections from
Stages 1, 2 and 3,
and the acquisition
strategy and
implementation
The description
of the proposed
system may not
contain all the
requisite sections
from Stages 1, 2
and 3; the
acquisition
strategy and
The
description of
the proposed
system is
severely
limited or
missing; or
little effort is
demonstrated.
Possible
Points
10
15
30
Financial
Information
Summary
Final System
Report
Format
plan are well
thought out,
thoroughly
explained, and
relevant to the
Case Study;
demonstrates a
sophisticated level
of analysis and
writing.
23-25 Points
plan are well
thought out, and
relevant to the
Case Study;
demonstrates
effective analysis
and writing.
plan are provided,
and relate to the
Case Study.
implementation
plan may be
inadequate or not
included; may
not relate to the
Case Study.
20-22 Points
18-19 Points
15-17 Points
0-14 Points
The financial
information
includes the current
operating costs;
estimated
implementation and
operating costs,
and useful life of
the proposed
system; tangible
(including financial)
and intangible
benefits; is highly
relevant to the
Case Study and
demonstrates a
sophisticated level
of analysis and
writing.
9-10 Points
The financial
information
includes the current
operating costs;
estimated
implementation and
operating costs,
and useful life of
the proposed
system; tangible
(including financial)
and intangible
benefits; is relevant
to the Case Study
and demonstrates
accurate analysis
and effective
writing.
The financial
information
includes the
current operating
costs; estimated
implementation
and operating
costs, and useful
life of the
proposed system;
tangible (including
financial) and
intangible
benefits; and is
appropriate to the
Case Study.
The financial
information may
not include all of:
the current
operating costs;
estimated
implementation
and operating
costs, and useful
life of the
proposed system;
tangible
(including
financial) and
intangible
benefits; may not
relate to the Case
Study.
The financial
information
provided is
severely
limited or
missing; or
little effort is
demonstrated.
8 Points
7 Points
6 Points
0-5 Points
The summary is
clear and
convincing, and
strongly justifies
the
recommendation to
implement the
system; is directly
tied to the Case
Study and
demonstrates a
sophisticated level
of analysis and
writing.
9-10 Points
The summary is
clear and
convincing, and
justifies the
recommendation to
implement the
system; is directly
related to the Case
Study and
demonstrates a
effective analysis
and writing.
The summary
provides a
rationale for
implementing the
proposed system
and is relevant to
the Case Study.
The summary
does not provide
sufficient
rationale for
implementing the
proposed system,
or is not relevant
to the Case
Study.
The summary
is not
included, or
demonstrates
little effort.
8 Points
7 Points
6 Points
0-5 Points
Final System
Report includes all
required sections,
effectively
organized and
Final System
Report includes all
required sections,
appropriately
organized and
Final System
Report includes all
required sections;
follows
instructions
Final System
Report may not
include all
required sections;
may not be well
Document is
extremely
poorly written
and does not
convey the
25
10
10
presented in a
sophisticated
manner; follows
instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
presented in a
professional
manner; follows
instructions
provided; uses
correct structure,
grammar, and
spelling; any
references used are
appropriately
incorporated and
cited using APA
style.
provided; contains
minimal grammar
and/or spelling
errors; and follows
APA style for any
references and
citations.
organized, and/or
does not follow
instructions
provided; and/or
contains
grammar and/or
spelling errors;
and/or does not
follow APA style
for any
references and
citations. May
demonstrate
inadequate level
of writing.
information.
TOTAL
Points
Possible
100
Stage 3: System Design Specification
Before you begin this assignment, be sure you have read the Case Study and all assignments for this
class, especially Stage 4: Final System Report. The feedback you received on your Stage 1 and Stage 2
assignments should be reviewed and used as you proceed with Stage 3.
Purpose of this Assignment
This assignment gives you the opportunity to apply a systematic approach to translate requirements into
a high-level logical system design. This assignment specifically addresses the following course outcomes
to enable you to:
•
•
apply a systematic approach to translate requirements into an executable systems design
effectively communicate with stakeholders to determine, manage, and document business
requirements throughout the SDLC
Assignment
The results of your systems analysis and design work in this class will be documented in a Final System
Report. The purpose of the Report is to inform management of your system proposal and gain approval
to proceed with the project. The Report will be developed and submitted in stages, which will be
compiled at the end of class into the Final System Report. Review the outline of the Final System Report
in the Stage 4 Assignment description. Note that it contains the analysis of the problem(s) and
requirements, and proposes what kind of a system solution is needed. It does not propose a specific
solution, but it does recommend why and how the organization should acquire the solution.
Following the Requirements Specification (Stage 2 assignment), the next step is to develop the System
Design Specification. The System Design Specification builds on the Requirements Specification to
illustrate how the files/database(s) will be laid out, how the output (forms, reports, and/or screens) and
input (forms and/or screens) should be designed. As you develop this assignment, you should refer to
your Stage 2 Requirements Specification (and the feedback you received) and use the inputs and outputs
you listed to create the input and output layouts and the file/database design.
All of the information you need to complete the projects in this class is not provided in the case study. In
the discussion area of the classroom, there is a discussion titled "Case Study Interview Questions" where
you can pose questions about the case study, as if you were interviewing the people in the case study
organization. Any information that you need that is not included in the case study should be asked about
in this discussion. Responses from the faculty member on behalf of the case study organization will be
available for everyone in the class.
Use the case study and the Case Study Interview Questions discussion, along with your Stage 2
Requirements Specification (including the feedback received), and resources below, to create a System
Design Specification in the format shown below. Include your corrected Stage 2 Requirements
Specifications as the first part of this assignment. Approximate lengths for each section of the Systems
Design Specification are provided as a guideline; be sure to provide all pertinent information. The
sources of explanatory materials can be found in the Week 5 Content readings.
Stage 3: System Design Specification
1
Requirements Specification
Include your Requirements Specification from Stage 2, with corrections from the feedback
included. This will establish the context for your System Design Specification to follow.
System Design Specification
I.
II.
III.
IV.
Introduction. Provide an appropriate introduction to this document. (one paragraph)
Output Layout. Begin with the three outputs listed in your Requirements Specification. For
each of them, create a diagram or table illustrating what the output would look like. (use a
short paragraph to introduce this section and each diagram, table or illustration should use
about ½ of a page)
A. Output Layout #1.
B. Output Layout #2.
C. Output Layout #3.
Input Layout. Using the data elements listed in your Requirements Specification, create a
diagram or table illustrating what the input screen would look like for each of the three sets
of input. (use a short paragraph to introduce this section and each diagram, table or
illustration should use about ½ of a page)
A. Input Layout #1.
B. Input Layout #2.
C. Input Layout #3.
File/database Design ERDs. For each of the three sets of outputs and inputs, create an
Entity Relationship Diagram showing how the data elements are related to each other [see
examples of ERD samples and types in the following
https://www.smartdraw.com/entity-relationshipdiagram/#:~:text=Attributes%2C%20which%20are%20represented%20by,have%20more%
20than%20one%20value
Depending on the inputs and outputs identified, there may be some overlap of the data
elements in the ERDs; a separate ERD should be developed for each pair of inputs/outputs.
(use a short paragraph to introduce this section, and each ERD should be on one page)
A. File/database Design ERD #1.
B. File/database Design ERD #2.
C. File/database Design ERD #3.
Submitting Your Assignment
Submit your Requirements Specification and System Design Specification as one document via your
Assignment Folder as Microsoft Word document, or a document that can be ready using MS Word, with
your last name included in the filename. Use the Grading Rubric below to be sure you have covered all
aspects of the assignment.
GRADING RUBRIC:
Stage 3: System Design Specification
2
Criteria
Introduction
Output
Layouts
Input Layouts
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above
Standards
Above Standards
Meets Standards
Below Standards
Well Below
Standards
5 Points
4 Points
3.5 Points
3 Points
0-2 Points
The corrected
Requirements
Specification is
included along with
a well-written
introduction to the
Systems Design
Specification;
demonstrates a
sophisticated level
of writing.
The corrected
Requirements
Specification is
included along with
an appropriate
introduction to the
Systems Design
Specification;
demonstrates clear
writing.
The corrected
Requirements
Specification is
included along
with an
introduction to the
Systems Design
Specification.
The corrected
Requirements
Specification
and/or the
introduction to
the Systems
Design
Specification may
not be included
or may not be
complete.
The corrected
Requirements
Specification
and
introduction to
the Systems
Design
Specification
are not
included, or
little effort is
demonstrated.
27-30 Points
24-26 Points
21-23 Points
18-20 Points
0-17 Points
30
Three output
layouts are clearly
and logically
presented; and
very clearly relate
to the output
requirements
previously defined.
Demonstrate a
sophisticated level
of analysis.
27-30 Points
Three output
layouts are clearly
presented; and
clearly relate to the
output
requirements
previously defined.
Demonstrate
accurate analysis.
Three output
layouts are
presented and
relate to output
requirements
previously defined.
Fewer than three
output layouts
may be provided,
and/or they may
not be
appropriate to
the previously
defined output
requirements.
24-26 Points
21-23 Points
18-20 Points
One or no
output layouts
are provided,
may not relate
to the
previously
defined output
requirements,
or little effort
is
demonstrated.
0-17 Points
30
Three input layouts
are clearly and
logically presented;
and very clearly
relate to the input
requirements
previously defined.
Demonstrate a
sophisticated level
of analysis.
Three input layouts
are clearly
presented; and
clearly relate to the
input requirements
previously defined.
Demonstrate
accurate analysis.
Three input
layouts are
presented and
relate to input
requirements
previously defined.
Stage 3: System Design Specification
Fewer than three
input layouts may
be provided,
and/or they may
not be
appropriate to
the previously
defined input
requirements.
Possible
Points
5
One or no
input layouts
are provided,
may not relate
to the
previously
defined input
requirements,
or little effort
is
demonstrated.
3
File/Database
Design ERDs
Format
27-30 Points
24-26 Points
21-23 Points
18-20 Points
0-17 Points
30
Three Entity
Relationship
Diagrams are
correctly
constructed,
logical, appropriate
to the
inputs/outputs, and
demonstrate a
sophisticated level
of analysis.
5 Points
Three Entity
Relationship
Diagrams are
correctly
constructed,
logical, appropriate
to the
inputs/outputs, and
demonstrate
accurate analysis.
Three Entity
Relationship
Diagrams are
adequately
constructed, and
appropriate to the
inputs/outputs.
Three Entity
Relationship
Diagrams may
not be included,
and/or may not
be appropriate to
the
inputs/outputs.
4 Points
3.5 Points
3 Points
Fewer than
three Entity
Relationship
Diagrams are
not provided,
are not
appropriate to
the inputs/
outputs or
little effort is
demonstrated.
0-2 Points
5
Submission reflects
effective
organization and
sophisticated
writing; follows
instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission reflects
effective
organization and
clear writing;
follows instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission is
adequate, is
somewhat
organized, follows
instructions
provided; contains
minimal grammar
and/or spelling
errors; and follows
APA style for any
references and
citations.
Submission is not
well organized,
and/or does not
follow
instructions
provided; and/or
contains
grammar and/or
spelling errors;
and/or does not
follow APA style
for any
references and
citations. May
demonstrate
inadequate level
of writing.
Document is
extremely
poorly written
and does not
convey the
information.
100
TOTAL
Points
Possible
Stage 3: System Design Specification
4
Data Flow Diagram (DFD) Tips
Process-to-Process
External Entity-to-Data Store
Process
Process
Process-to-Data Store
Data Store
External Entity-to-External Entity
Process
Data Store
Process-to-External Entity
Process
External
Entity
External
Entity
External
Entity
Data Store-to-Data Store
External
Entity
Processes: Verbs
Dataflows: Nouns
Data Stores: Nouns
External Entities: Nouns
Data Store
Data Store
1) Process’s input & output are different
2) Each data store should have at least
one data flow in and one data flow out
3) Each process should have at least one
data flow in and one data flow out
4) All inputs and outputs should be
labeled
5) Processes should have an identifier
(Ex., 1.0, 2.0, etc.)
Stage 2: Requirements Specification
Before you begin this assignment, be sure you have read the Case Study and all assignments for this
class, especially Stage 4: Final System Report. The feedback you received on your Stage 1 assignment
should be reviewed and used as you proceed with Stage 2.
Purpose of this Assignment
This assignment gives you the opportunity to specify clear and concise requirements, including the use of
data and process models, for a system that enables a productive change in a way the business is
conducted. This assignment specifically addresses the following course outcomes to enable you to:
•
•
•
apply a systematic approach to translate requirements into an executable systems design
effectively communicate with stakeholders to determine, manage, and document business
requirements throughout the SDLC
perform modeling to assist with analysis and decision making
Assignment
The results of your systems analysis and design work in this class will be documented in a Final System
Report. The purpose of the Report is to inform management of your system proposal and gain approval
to proceed with the project. The Report will be developed and submitted in stages, which will be
compiled at the end of class into the Final System Report. Review the outline of the Final System Report
in the Stage 4 Assignment description. Note that it contains the analysis of the problem(s) and
requirements, and proposes what kind of a system solution is needed. It does not propose a specific
solution, but it does recommend why and how the organization should acquire the solution.
Following the Preliminary Investigation Report (Stage 1 assignment), the next step is to identify the
requirements for a system, documenting them in the Requirements Specification document. The purpose
of the Requirements Specification is to clearly define what the proposed system will do in non-technical
user-oriented language. It should identify what data is entered into the system, what output is required,
what processes the system should perform, what protections and controls are needed, what performance
is expected, and what the business continuity needs are. In order to clearly express the requirements,
data and process models are used to communicate how the system should work.
All of the information you need to complete the projects in this class is not provided in the case study. In
the discussion area of the classroom, there is a discussion titled "Case Study Interview Questions" where
you can pose questions about the case study, as if you were interviewing the people in the case study
organization. Any information that you need that is not included in the case study should be asked about
in this discussion. Responses from the faculty member on behalf of the case study organization will be
available for everyone in the class.
Use the information provided in the case study and the Case Study Interview Questions discussion to
create a checklist of functional and technical requirements and the data and process models listed below.
Using the format and resources below, list three requirements for each of the areas shown in I and
II. Then, create two diagrams to illustrate the scope of the system: the context diagram and the use
case diagram. Then, create the data flow diagram to illustrate the flow of the inputs and outputs
listed as functional requirements in section I. You should then select a process or process step (from
those listed in section I.b – processing requirements) that has some decision associated with it to
create the three process models listed below. The same process/process step will be used for all
three of the process models; they are just different ways to represent the process and the decision
involved. Approximate lengths for each section are provided as a guideline; be sure to provide all
pertinent information. References in brackets are to the two e-textbooks (by authors Jawahar and
Conger) used in this class and the page on which the explanatory information begins. Use the
examples listed in the brackets to develop your diagrams. [Note: Every diagram/model needs to be
Stage 2: Requirements Specification
1
customized for the course scenario. Simply copying the example diagram(s) with little or no
customization will result in a zero for that diagram.] There are several different methodologies using
different symbols, but your diagrams will be graded for compliance with the examples listed. You are
required to use the symbols and diagramming methods illustrated in the examples, and follow any rules
for the diagram in the sources listed with each diagram.
Requirements Specification
Background: First, provide a brief description of your proposed system to establish the context for the
Requirements Specification.
I.
Functional Requirements. The input-processing-output requirements must relate to each other.
Start with three outputs you expect from the system, then determine what inputs are needed to create
each of those outputs, and finally specify what processing needs to occur for each input to create the
output. At least one of your processing requirements must have a decision associated with it so it can be
used for the Process Models below. You should have a complete statement for each requirement, and
each requirement should be numbered within the category. (introductory paragraph and list of 9 interrelated requirement statements) [Jawahar, p. 95 and the Week 3 Content, including reading on IEEE
Software Requirements Specifications] [another source of ideas and concepts is:
http://www.slideshare.net/ALATechSource/sample-project-requirements-document-library-blog]
a. Output requirements. List three different reports, results of a calculation, or other outputs.
i. Output #1
ii. Output #2
iii. Output #3
b. Input requirements.
i. List the main data elements required to create output #1
ii. List the main data elements required to create output #2
iii. List the main data elements required to create output #3
c. Processing requirements (at least one must have a decision associated with it)
i. Processing required to create Output #1
ii. Processing required to create Output #2
iii. Processing required to create Output #3
II.
Technical Requirements (introductory paragraph and 3 requirement statements listed for each
area below) [Jawahar, p. 95]
a. Security requirements
b. System control requirements
c. Performance requirements
d. Business continuity requirements (backup, restart, recovery)
III.
System Scope Diagrams (introductory/explanatory paragraph and 2 diagrams) [a good
explanation and example is at http://www.jamasoftware.com/blog/defining-project-scopecontext-use-case-diagrams/]
a. Context Diagram [explanation in Conger, p.228; use example in Conger, p.229. Figure 7.2]
b. Use Case Diagram [use example in weblink above]
IV.
Data Flow Diagram (introductory/explanatory paragraph and diagram) [Week 4 Content module
and weblinks]
a. Data Flow Diagram [explanation in Conger, p.228; use example in Conger, p.230, Figure 7.3;
use the tips located in the assignment folder (DFD_Tips.pdf)]
V.
Process Models (introductory/explanatory paragraph and 3 items below) [Week 4 Systems
Analysis Course Module]
a. Structured English [use example in Systems Analysis Course Module, Process Description
Tools]
b. Decision Table [use example in Systems Analysis Course Module, Process Description Tools]
c. Decision Tree [use example in Systems Analysis Course Module, Process Description Tools]
Stage 2: Requirements Specification
2
Submitting Your Assignment
Submit your document via your Assignment Folder as Microsoft Word document, or a document that can
be ready using MS Word, with your last name included in the filename. Use the Grading Rubric below to
be sure you have covered all aspects of the assignment.
GRADING RUBRIC:
Stage 2: Requirements Specification
3
Criteria
Functional
Requirements
Technical
Requirements
System
Scope
Diagrams
Data Flow
Diagram
90-100%
80-89%
70-79%
60-69%
< 60%
Far Above
Standards
Above Standards
Meets Standards
Below Standards
Well Below
Standards
16-18 Points
14-15 Points
12-13 Points
10-11 Points
0-9 Points
Three requirements
for input, output
and processing are
clearly stated and
correctly interrelated; are
logically derived
from the Case
Study, and
demonstrate a
sophisticated level
of writing.
Three requirements
for input, output
and processing are
clearly stated and
correctly interrelated; are
logically derived
from the Case
Study, and
demonstrate a clear
understanding of
the course
concepts.
9-10 Points
Three
requirements for
input, output and
processing are
stated and are
inter-related; and
are derived from
the Case Study.
May present
fewer than three
requirements for
input, output and
processing, or
they may not be
inter-related;
and/or may not
be derived from
the Case Study.
Functional
requirements
are not
included, or
demonstrate
little effort.
8 Points
7 Points
0-6 Points
Three requirements
each for security,
system control,
performance, and
business continuity
are clearly stated
and are logically
derived from the
Case Study, and
demonstrate a
sophisticated level
of writing.
9-10 Points
Three requirements
each for security,
system control,
performance, and
business continuity
are clearly stated
and are logically
derived from the
Case Study, and
demonstrate
effective writing.
Three
requirements each
for security,
system control,
performance, and
business
continuity are
provided and are
appropriate to the
Case Study.
Fewer than three
requirements
each for security,
control,
performance and
business
continuity may be
provided, and/or
they may not be
appropriate to
the Case Study.
Functional
requirements
are not
provided, or
little effort is
demonstrated.
8 Points
7 Points
6 Points
0-5 Points
Context diagram
and Use Case
diagram are
correctly
constructed,
logical, appropriate
to the Case Study
and demonstrate a
sophisticated level
of analysis.
9-10 Points
Context diagram
and Use Case
diagram are
correctly
constructed,
logical, appropriate
to the Case Study
and demonstrate
accurate analysis.
Context diagram
and Use Case
diagram are
provided, and are
appropriate to the
Case Study.
Both Context and
Use Case
diagrams may
not be provided,
and/or may not
be appropriate to
the Case Study.
Both Context
and Use Case
diagrams are
not provided,
or little effort
is
demonstrated.
8 Points
7 Points
6 Points
0-5 Points
Data Flow Diagram
is correctly
constructed,
logical, appropriate
to the Case Study
Data Flow Diagram
is correctly
constructed,
logical, appropriate
to the Case Study
Data Flow
Diagram is
provided, and are
appropriate to the
Case Study.
Data Flow
Diagram may not
be correctly
contructed,
and/or may not
Data Flow
Diagram is not
provided, or
little effort is
demonstrated.
11-12 Points
Stage 2: Requirements Specification
Possible
Points
18
12
10
10
4
Process
Models
Format
and demonstrate a
sophisticated level
of analysis.
36-40 Points
and demonstrate
accurate analysis.
be appropriate to
the Case Study.
32-35 Points
28-31 Points
24-27 Points
0-23 Points
All three process
models – structured
English, decision
table, and decision
tree – are correctly
constructed,
logical, appropriate
to the Case Study
and demonstrate a
sophisticated level
of analysis. All
three models
describe the same
decision process.
9-10 Points
All three process
models – structured
English, decision
table, and decision
tree – are correctly
constructed,
logical, appropriate
to the Case Study
and demonstrate
accurate analysis.
All three models
describe the same
decision process.
All three process
models –
structured English,
decision table, and
decision tree – are
provided, and are
appropriate to the
Case Study. All
three models
describe the same
decision process.
All three process
models may not
be provided, may
not describe the
same decision
process, and/or
may not be
appropriate to
the Case Study.
The three
process
models are
not provided,
or little effort
is
demonstrated.
8 Points
7 Points
6 Points
0-5 Points
Submission reflects
effective
organization and
sophisticated
writing; follows
instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission reflects
effective
organization and
clear writing;
follows instructions
provided; uses
correct structure,
grammar, and
spelling; presented
in a professional
format; any
references used are
appropriately
incorporated and
cited using APA
style.
Submission is
adequate, is
somewhat
organized, follows
instructions
provided; contains
minimal grammar
and/or spelling
errors; and follows
APA style for any
references and
citations.
Submission is not
well organized,
and/or does not
follow
instructions
provided; and/or
contains
grammar and/or
spelling errors;
and/or does not
follow APA style
for any
references and
citations. May
demonstrate
inadequate level
of writing.
Document is
extremely
poorly written
and does not
convey the
information.
10
TOTAL
Points
Possible
Stage 2: Requirements Specification
40
100
5
