Systems Analysis and Design: Requirements Document Instructions
Systems Analysis and Design
Stage 01: Requirements Document Instructions
Introduction
Before you begin this assignment, be sure you have read the Udo, Marian, &Uduak Corporation Case Study. Also, you should review your Stages 2 – 5 individual assignments to get an understanding of the future projects that build on this initial stage.
Purpose of this Assignment
This assignment gives you the opportunity to apply the course concepts to document system requirements. This assignment specifically addresses the following course outcomes to enable you to:
• Achieve successful systems design, development, and implementation by effectively applying the role of systems engineering and integrating with project management
• Effectively communicate with stakeholders to determine, manage, and document business requirements throughout the SDLC
• Perform modeling to assist with analysis and decision making
• Translate business requirements into systems by applying appropriate SDLC methodologies and incorporating industry best practices
The Deliverable
Using the Udo, Marian, &Uduak Corporation Case Study, develop and deliver a Requirements Document for a new billing and payment system. The document will include a high-level description of the current information system that handles some of the company’s administrative and financial tasks and identify the requirements for the new system (as is/to be). It will also provide a high-level functional decomposition diagram (FDD) of the new system. And, it will include a systems requirements checklist for the new billing and payment system that includes five (5) key parameters for output, input, process, performance, and control.
The Requirements Document must include the following:
• The paper should be 2 – 4 pages in length, plus diagrams and a checklist, responding to the bulleted items below. The diagrams and checklist are not included in the page count.
• Cover and a Works Cited page are also required. These are not included in the page count.
• The Cover page must include an appropriate title and your name.
Page 1 of 5
Systems Analysis and Design
Stage 01: Requirements Document Instructions
• Use the Works Cited page to correctly cite and reference any sources you use with APA format.
• Use the Grading Rubric to be sure you have covered everything.
• Submit your paper via your Assignment Folder as a Microsoft Word document with your last name included in the filename.
• “As-Is” Process
o “As-Is” refers to the current system as described in the case study that does not meet the company’s administrative needs
o This should include a brief commentary describing the existing information system and its shortcomings.
o This should include a process diagram. (See example in Helpful Resources, below)
• “To-Be” process
o “To-Be” refers to the new billing and payment system that meets the company’s administrative needs as described in the case study
o This should include a brief commentary describing the proposed billing and payment system.
o This should include a process diagram.
• Functional Decomposition Diagram (FDD) of the new billing and payment system
o The FDD should be broken down to three levels as shown in the following link”: http://it.toolbox.com/blogs/enterprise-solutions/levels-of-detail-for-functional-decomposition-14626
• System Requirements Checklist for the new billing and payment system
o You should have a complete statement for each requirement in each of the following categories of the new system:
Process Output Input
Performance Control
o Each requirement should be individually numbered within the category.
Page 2 of 5
Systems Analysis and Design
Stage 01: Requirements Document Instructions
Helpful Resources
• “As-Is” and “To-Be” Business Process Modeling http://www.businessballs.com/business-process-modelling.htm
• Functional Decomposition Diagram (FDD) http://academic.regis.edu/ladams/Diagramming%20101.html
• Textbook “Systems Analysis and Design,” Chapter 4, Requirements Modeling
Tools that can assist you in developing the graphics for this project:
• The file “Graphics That Can be Used for Drawing Diagrams” in the Course Content section of WebTycho has symbols you may be able to copy and paste
• “As-Is” and “To-Be” graphics
o Microsoft Visio
• Functional Decomposition Diagram (FDD)
o Microsoft Visio
o The file “Graphics That Can be Used for Drawing Diagrams” in the Course Content section of WebTycho has symbols you may be able to copy and paste
• Systems Requirements Checklist
o Microsoft Excel
o Microsoft Word
Page 3 of 5
Systems Analysis and Design
Stage 01: Requirements Document Instructions
Stage 1: Requirements Document Rubric
Criteria Superior to Substandard to Good Inadequate Points
Outstanding
“As-Is” Process The “As-Is” or current The “As-Is” or current The “As-Is” or 2
information system is information system is not current information
described in a high-level described in sufficient system is not
detail. Process diagram detail or may be unclear; described.
is included and and/or may be lacking
accurately reflects the process diagram.
current process.
Sufficient detail is
provided to demonstrate
difference from “to-be”
process.
“To-Be” Process The “To-Be” or proposed The “To-Be” or proposed The “To-Be” or 2
new billing and payment new billing and payment proposed system
system is described in a system is not described is not described.
high-level of detail. in a high-level detail or
Process diagram is may be unclear, and/or
included and accurately may be lacking process
reflects the new diagram.
process. Sufficient
detail is provided to
demonstrate difference
from “as-is” process.
FDD of the The high-level functional The high-level functional FDD not included 2.5
New System decomposition diagram decomposition diagram
(FDD) of the new billing (FDD) of the new billing
and payment system and payment system
covers all required does not contain all
system functions and is required system –
accurately decomposed functions and/or may not
to three levels. be (correctly)
decomposed to three
levels.
Page 4 of 5
Systems Analysis and Design
Stage 01: Requirements Document Instructions
Criteria Superior to Substandard to Good Inadequate Points
Outstanding
Systems The systems The systems The systems 2.5
Requirements requirements checklist requirements checklist requirements
Checklist for the new system – is for the new system does checklist is not
complete and includes not contain a complete included.
requirements for output, list of requirements and/
input, process, does not include
performance, and requirements for output,
control, with each input, process,
requirement numbered. performance, control
Requirements are and/or each requirement
appropriate to the is not numbered.
UMUC Case Study. Requirements may not
be appropriate to UMUC
Case Study.
Report and Report and diagrams Report and Diagrams Report and 1
Diagram Format reflect effective are not well organized, Diagrams are
organization; correct and/or contains grammar extremely poorly
sentence structure, and/or spelling errors; constructed and
grammar, and spelling; and/or do not follow APA do not convey the
presented in a style for any references information.
professional format; any used and citations.
references used are
appropriately
incorporated and cited
using APA style.
Total Points: 10