Stage : 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 stepis 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 formatand resourcesbelow, 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 theuse case diagram. Then, create thedata flow diagramto 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 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 requirementstatements) [Jawahar, p. 95 and the Week 3 Content, including reading on IEEE Software Requirements Specifications] [another source of ideas and concepts is:
https://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 requirementstatements 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
https://www.jamasoftware.com/blog/defining-project-scope-context-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 FlowDiagram [explanation in Conger, p.228; use example in Conger, p.230, Figure 7.3; use the rules at
https://www.dlsweb.rmit.edu.au/toolbox/ecommerce/tbn_respak/tbn_e2/html/tbn_e2_devsol/dfds/dfdrules.htm ]
V. Process Models (introductory/explanatory paragraph and 3 items below) [Week 4Systems 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]
Three requirements for input, output and processing are clearly stated and correctly inter-related; are logically derived from the Case Study, and demonstrate a clear understanding of the course concepts.
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.
Technical Requirements
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.
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 appropria to the Case Study.
Functional requirements are not provided, or little effort is demonstrated.
System Scope Diagrams
Context diagram and Use Case diagram are correctly constructed, logical, appropriateto the Case Study and demonstratea sophisticated level of analysis.
Context diagram and Use Case diagram are correctly constructed, logical, appropriateto the Case Study and demonstrate accurate analysis.
Attachment:- DATA.rar