IT Solution Stage
Stage 01: Requirements Document Instructions
Introduction (Please see attachment also)
Before you begin this assignment, be sure you have read the attached 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.
FYI.
Stage 2 - Data & Process Models
Stage 3 - Decision Table & Decision Tree
Stage 4 - Systems Deployment Decision Paper
Stage 5 - Change Control Board Memo
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 modelling 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.
· 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
Ø "As-Is" refers to the current system as described in the case study that does not meet the company's administrative needs
Ø This should include a brief commentary describing the existing information system and its shortcomings.
Ø This should include a process diagram. (See example in Helpful Resources, below)
· "To-Be" process
Ø "To-Be" refers to the new billing and payment system that meets the company's administrative needs as described in the case study
Ø This should include a brief commentary describing the proposed billing and payment system.
Ø This should include a process diagram.
· Functional Decomposition Diagram (FDD) of the new billing and payment system
Ø The FDD should be broken down to three levels as shown in the following link": https://it.toolbox.com/blogs/enterprise-solutions/levels-of-detail-forfunctional-decomposition-1462
· System Requirements Checklist for the new billing and payment system
Ø 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.
Helpful Resource
· "As-Is" and "To-Be" Business Process Modelling
https://www.businessballs.com/business-process-modelling.htm
· Functional Decomposition Diagram (FDD)
https://academic.regis.edu/ladams/Diagramming%20101.html
· Textbook "Systems Analysis and Design," Chapter 4, Requirements Modelling
Tools that can assist you in developing the graphics for this project:
· "As-Is" and "To-Be" graphic
Ø Microsoft Visio
· Functional Decomposition Diagram (FDD)
Ø Microsoft Visio
Ø The file "Graphics That Can be Used for Drawing Diagrams" in the Course
· Systems Requirements Checklist
Ø Microsoft Excel
Ø Microsoft Word