The document outlines a series of assignments for a course focused on system analysis and design, specifically for the company Precision Electronic Parts. It involves creating preliminary investigation, requirement specifications, system design specifications, and a final system report, all aimed at addressing the need for a new customer billing and payment system. Each stage builds upon the previous one to develop a comprehensive proposal that includes problem analysis, requirements, feasibility assessments, and design layouts for the proposed system.

1. IFSM 461 Stage 1 Preliminary Investigation
Report (Precision Electronic Parts)
For more classes visit
www.snaptutorial.com
Stage 1: Preliminary Investigation Report
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.
Purpose of this Assignment
This assignment gives you the opportunity to use industry-standard
methodologies for analyzing a business situation, initiating a project, and
determining various aspects of feasibility of an IT project. This
assignment specifically addresses the following 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
· 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

2. 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.
The first step in the analysis process is to create a Preliminary
Investigation Report (PIR). The PIR documents the system planning
phase of the System Development Life Cycle (SDLC). During the
planning phase, the opportunities presented or problem(s) to be solved
with an information technology system are identified, investigation into
the current situation occurs, and various feasibility aspects of
implementing a system are analyzed. This results in a recommendation
for further action with estimated costs and schedule, and a list of
benefits. Once it is completed and approved, the PIR becomes the major
source document for use to begin the systems analysis phase.
To start, read the case study carefully. The case study tells you that the
executives at Precision Electronics Parts, Inc., have identified a need to
replace the current customer billing and payment system and re-engineer
the associated processes. As you review the case study, list the most
important relevant business problems and identify the information
presented that you will need to complete the sections of the Preliminary
Investigation Report shown below. 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.
Using the case study and the outline and resources listed below, develop
your Preliminary Investigation Report. 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

3. authors Jawahar and Conger) used in this class and the page on which
the explanatory information begins.
· Introduction (1 paragraph)
· Brief statement of the problem or system
· Name of person or group who initiated the investigation
· Name of person or group who performed the investigation
· Problem to be solved – The basis of the system request, including
an explanation of major problems or opportunities (1 paragraph)
· Findings
· Scope of proposed system (1 paragraph describing the system
boundaries – what is included, perhaps where it stops)
· Constraints (1 paragraph, including a short list of constraints)
[Jawahar, p. 61]
· Fact Finding – significant findings and conclusions (1 paragraph
with more than one finding and conclusion to be drawn; source is the
case study and responses to questions posed in the Case Study Interview
Questions discussion)
· Current Costs – cost of current system (1 short paragraph; source
is the case study and responses to questions posed in the Case Study
Interview Questions discussion)
· Feasibility Analysis: This is not a complete Feasibility Report;
instead it is a discussion of whether and how the proposed systems is
technically, financially and organizationally feasible. Describe what
aspects of the organization in the case study and the proposed system
make it technically, financially and organizationally feasible. [Jawahar,
p. 65]
· Technical Feasibility (1 paragraph)
· Financial Feasibility (1 paragraph)
· Organizational/Behavioral Feasibility (1 paragraph)
· Recommendation for further action
· An estimate of how long it would take to implement the system
and have it available for use, and a rough cost estimate for the entire
project (short paragraph with estimated time and cost)
·
Expected benefits – tangible (with estimated quantification) and intangi

4. ble benefits (introductory paragraph and list of tangible (quantified) and
intangible benefits) [Conger, p. 148]
Can provide screenshots of the book pages mentioned above if needed..
************************************
IFSM 461 Stage 2 Requirements Specification
(Precision Electronic Parts)
For more classes visit
www.snaptutorial.com
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

5. · 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

6. 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. 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

7. 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 inter-related
requirement statements) [Jawahar, p. 95 and the Week 3 Content,
including reading on IEEE Software Requirements Specifications]
[another source of ideas and concepts is:
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
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]

8. 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 rules at
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]
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.
************************************
IFSM 461 Stage 3 System Design Specification
(Precision Electronic Parts)
For more classes visit
www.snaptutorial.com

9. 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

10. 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.
Requirements Specification

11. 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. Introduction. Provide an appropriate introduction to this
document. (one paragraph)
II. 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.
III. 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.
IV. 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 explanation at
V. 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.

12. 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.
************************************
IFSM 461 Stage 4 Final System Report
(Precision Electronic Parts)
For more classes visit
www.snaptutorial.com
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

13. 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

14. 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. 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
II. Description of the current process/system (This section will
come from your Stage 1Assignment: 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
D. The operating cost of the present system, if applicable
III. 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

15. 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
IV. 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)
V. 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

16. last name included in the filename. Use the Grading Rubric below to be
sure you have covered all aspects of the assignment.
n
************************************