Stage 2:\u00a0\u00a0 Requirements Specification\t\u00a0\tBefore you begin this assignment, be sure you have read the Case Study and all assignments for this class, especially Stage 4:\u00a0 Final System Report.\u00a0 The feedback you received on your Stage 1 assignment should be reviewed and used as you proceed with Stage 2.\tPurpose of this Assignment\tThis 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.\u00a0 This assignment specifically addresses the following course outcomes to enable you to:\t\u00a0\t\u00b7 \ufffd\u00a0\u00a0\u00a0 apply a systematic approach to translate requirements into an executable systems design\t\u00b7 \ufffd\u00a0\u00a0\u00a0 effectively communicate with stakeholders to determine, manage, and document business requirements throughout the SDLC\t\u00b7 \ufffd\u00a0\u00a0\u00a0 perform modeling to assist with analysis and decision making\t\u00a0\tAssignment\t\u00a0\tThe results of your systems analysis and design work in this class will be documented in a Final System Report.\u00a0 The purpose of the Report is to inform management of your system proposal and gain approval to proceed with the project.\u00a0 The Report will be developed and submitted in stages, which will be compiled at the end of class into the Final System Report.\u00a0 Review the outline of the Final System Report in the Stage 4 Assignment description.\u00a0 Note that it contains the analysis of the problem(s) and requirements, and proposes what kind of a system solution is needed.\u00a0 It does not propose a specific solution, but it does recommend why and how the organization should acquire the solution.\t\u00a0\tFollowing 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.\u00a0 The purpose of the Requirements Specification is to clearly define what the proposed system will do in non-technical user-oriented language.\u00a0 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.\u00a0 In order to clearly express the requirements, data and process models are used to communicate how the system should work.\t\u00a0\tAll of the information you need to complete the projects in this class is not provided in the case study.\u00a0 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.\u00a0 Any information that you need that is not included in the case study should be asked about in this discussion.\u00a0 Responses from the faculty member on behalf of the case study organization will be available for everyone in the class.\u00a0\t\u00a0\tUse 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.\u00a0 Using the format and resources below, list three requirements for each of the areas shown in I and II.\u00a0 Then, create two diagrams to illustrate the scope of the system:\u00a0 the context diagram and the use case diagram.\u00a0\u00a0 Then, create the data flow diagram to illustrate the flow of the inputs and outputs listed as functional requirements in section I.\u00a0 You should then select a process or process step (from those listed in section I.b “\ufffd processing requirements) that has some decision associated with it to create the three process models listed below.\u00a0 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.\u00a0 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.\u00a0 Use the examples listed in the brackets to develop your diagrams.\u00a0 There are several different methodologies using different symbols, but your diagrams will be graded for compliance with the examples listed.\u00a0 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.\t\u00a0\tRequirements Specification\t\u00a0\tBackground:\u00a0 First, provide a brief description of your proposed system to establish the context for the Requirements Specification.\t\u00a0\tI. \ufffd\u00a0\u00a0\u00a0\u00a0 Functional Requirements.\u00a0 The input-processing-output requirements must relate to each other.\u00a0 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.\u00a0 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]\u00a0\u00a0 [another source of ideas and concepts is:\ta.\u00a0\u00a0 Output requirements.\u00a0 List three different reports, results of a calculation, or other outputs.\t \ufffd i. Output #1\t \ufffd ii. Output #2\t \ufffd iii. Output #3\tb.\u00a0\u00a0 Input requirements.\ti. List the main data elements required to create output #1\tii. List the main data elements required to create output #2\tiii. List the main data elements required to create output #3\tc.\u00a0\u00a0 Processing requirements (at least one must have a decision associated with it)\t \ufffd i. Processing required to create Output #1\t \ufffd ii. Processing required to create Output #2\tiii. Processing required to create Output #3\tII. \ufffd\u00a0\u00a0 Technical Requirements (introductory paragraph and 3 requirement statements listed for each area below) [Jawahar, p. 95]\ta.\u00a0\u00a0 Security requirements\tb.\u00a0\u00a0 System control requirements\tc.\u00a0\u00a0 Performance requirements\td.\u00a0\u00a0 Business continuity requirements (backup, restart, recovery)\tIII. \ufffd\u00a0 System Scope Diagrams (introductory\/explanatory paragraph and 2 diagrams) [a good explanation and example is at\ta. \ufffd\u00a0 Context Diagram [explanation in Conger, p.228; use example in Conger, p.229. Figure 7.2]\tb. \ufffd Use Case Diagram [use example in weblink above]\tIV. \ufffd\u00a0 Data Flow Diagram (introductory\/explanatory paragraph and diagram) [Week 4 Content module and weblinks]\ta. \ufffd\u00a0 Data Flow Diagram [explanation in Conger, p.228; use example in Conger, p.230, Figure 7.3; use the rules at \ufffd\u00a0\t\u00a0V. \ufffd Process Models (introductory\/explanatory paragraph and 3 items below) [Week 4 Systems Analysis Course Module]\ta.\u00a0\u00a0 Structured English [use example in Systems Analysis Course Module, Process Description Tools]\tb.\u00a0\u00a0 Decision Table [use example in Systems Analysis Course Module, Process Description Tools]\tc.\u00a0\u00a0 Decision Tree [use example in Systems Analysis Course Module, Process Description Tools]\t\u00a0\t\u00a0\tSubmitting Your Assignment\tSubmit 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.\u00a0 Use the Grading Rubric below to be sure you have covered all aspects of the assignment.<\/p>\n","protected":false},"excerpt":{"rendered":"
Stage 2:\u00a0\u00a0 Requirements Specification \u00a0 Before you begin this assignment, be sure you have read the Case Study and all assignments for this class, especially Stage 4:\u00a0 Final System Report.\u00a0 The feedback you received on your Stage 1 assignment should Read More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-224836","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts\/224836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/comments?post=224836"}],"version-history":[{"count":0,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts\/224836\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/media?parent=224836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/categories?post=224836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/tags?post=224836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}