ENTD268 week 3 This assignment will address the following objectives: CO-2: Anal

ENTD268 week 3
This assignment will address the following objectives:
CO-2: Analyze a business case study by applying Systems Analysis and Design concepts, principles, processes, and techniques
CO-3: Apply industry driven techniques for designing, developing, deploying, and securing enterprise applications.
CO-4: Develop major life cycle deliverables like Vision Document, SRS (Software Requirements Specification) , or SDD (System Design Document).
CO-6: Create models using Structured Analysis and Design (SAD).
Assignment 3 Analysis: SRS Nonfunctional, Other Requirements and DFD
Purpose
The purpose of this assignment is to complete SRS Sections 5. Other Nonfunctional Requirements and 6. Other Requirements, for the Case Study and develop and apply the Structured Analysis and Design (SAD) technique to create DataFlow Diagrams that represents the major processes of the Case Study.
Assignment Directions
1. Rename your last submitted SRS.
Use your last corrected SRS from your previous assignment and rename it Assignment3AnalysisSRSDFDLastnameFirstname replacing the names with your name. Make certain that you have made any corrections to your SRS before completing this assignment. Place the DFDs and tables for this assignment in your SRS.
2. Complete Section 5. Nonfunctional Requirements in your SRS.
Nonfunctional requirement categories for this document include Safety, Security,, Software Quality, and Business Rules. Each requirement must have a unique number, name and description.
2.1 Complete Section 5.1 Safety Requirements
Specify those requirements that are concerned with possible loss, damage, or harm that could result from the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be prevented. Refer to any external policies or regulations that state safety issues that affect the product’s design or use. Define any safety certifications that must be satisfied.
2.2 Complete Section 5.2 Security Requirements
Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.
2.3 Complete Section 5.3 Software Quality Attributes
Specify any additional quality characteristics for the product that will be important to either the customers or the developers. Some to consider are adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability. Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative preferences for various attributes, such as ease of use over ease of learning.
2.4 Complete Section 5.4 Business Rules
List any operating principles about the product, such as which individuals or roles can perform which functions under specific circumstances. These are not functional requirements in themselves, but they may imply certain functional requirements to enforce the rules.
3. Complete Section 6. Other Requirements in your SRS.
Define any other requirements not covered elsewhere in the SRS. This might include database requirements, internationalization requirements, legal requirements, reuse objectives for the project, and so on. Add any new sections that are pertinent to the project. Follow the numbering convention use in other sections. Include the unique ID, name, and description.
3.1 Complete Section 6.1 Performance Requirements
List each performance requirement for the product components. Include a unique identifier, the name of each requirement, and a description for each requirement.
4. Create a Context DFD for the Case Study
4.1 Create a Context DFD and place it in Appendix C.1.1 of your SRS.
Using diagrams.net (https://www.diagrams.net/index.html) create a Context DFD for your Case Study and place it in Appendix C.1.1 in your SRS. Note that the drawing website is also known as draw.io. See the example Tune Source Context Diagram in Figure 5.15, p. 211 in your textbook. Numbering conventions in the literature for DFDs varies. We will not number the Context Diagram. The next level of decomposition is referred to as Level 0.
Details aboutdiagrams.net (draw.io) and videos on how to use it to create DFDs are in the Overview section of the course. Detailed information about the DFDs is in the Content modules and your textbook. See the SRS Appendix C for additional details before you start this assignment.
4.2 Discuss your DFD and place it in Appendix C.1.2 in your SRS.
5. Create a Level 0 DFD (first level of decomposition) for the Case Study
5.1 Using draw.io create a Level 0 DFD for the Case Study and place it in Appendix C.2.1 of your SRS.
Remember that for Level 0 you break the system into sub processes that show the flow of data from process to process and data stores. The elements of the dataflows must balance between levels–you cannot lose data from one level to the next. For example if you have a dataflow named “Request appointment” in the context diagram, it must also be represented in the Level 0 diagram. So you enter a dataflow and its structure in the Data Dictionary tables. More levels of decomposition can be completed, as necessary. Remember that processes and data stores are numbered.
A technique you can use to create DFDs is to use the use cases, create fragments of DFDs, and then combine the fragments to create a full DFD.
5.2 Discuss your Level 0 DFD in Appendix C.2.2 in your SRS.
6. Complete Appendix C.3 Data Dictionary Entries for DFDs for your DFDs.
SRS Appendix C.3 is for your Data Dictionary entries for Data Flows , Processes, External Entities, and DataStores (DataStores only appear on your Level 0 DFD. Enter them in alphabetical order.
6.1 Complete C.3.1 Process Table
Add process names and numbers as well as process description. List data lows and their source or destination for the process.
6.2 Complete C.3.2 External Entity Table
Add the names of external Entities and a description of each.
6.3 Complete C.3.3 DataStore Table
Add the names and number of the DataStores and include a description. Include a list of all elements in the DataStore.
6.4 Complete C.3.4 DataFlow Table
Include the name of the DataFlow, DataFlow description and a list all elements in each DataFlow.
Submission Directions
Grading Rubric
1. SRS Section 5. Nonfunctional Requirements and SRS Section 6. Other Requirements in your SRS (25)
Complete Section 5. Nonfunctional Requirements in your SRS and Section 6.Other Requirements
1.1 Complete Section 5.1 Safety Requirements.
1.2 Complete Section 5.2 Security Requirements.
1.3 Complete Section 5.3 Software Quality Attributes.
1.4 Complete Section 5.4 Business Rules.
1.5 Complete Section 6. Other Requirements in your SRS.
1.6 Complete Section 6.1 Performance Requirements
2. SRS Context DFD in Appendix C.1 (25)
Create a Context DFD for the Case Study.
3.1 Create a Context DFD including External Entities, Process, and DataFlows using draw.io and place it in Appendix C.1.1 of your SRS.
3.2 Discuss your DFD in Appendix C.1.2 in your SRS.
3. SRS Level 0 DFD (first level of decomposition) in Appendix C.2 (20)
Create a Level 0 DFD (first level of decomposition) for the Case Study
4.1 Using draw.io create a Level 0 DFD for the Case Study and place it in Appendix C.2.1 of your SRS.
4.2 Discuss your Level 0 DFD in section C.2.2 in your SRS.
4. SRS Data Dictionary for DFDs in Appendix C.3 (20)
Complete Appendix C.3 Data Dictionary Entries for DFDs.
5.1 Complete C.3.1 Process Table.
5.2 Complete C.3.2 External Entity Table.
5.3 Complete C.3.3 DataStore Table.
5.4 Complete C.3.4 DataFlow Table.
5. Writing Format (10)
Prepare the document in APA format. Grammatical, spelling or punctuation—the writing is grammatically correct, clear and concise. The response is well formulated and easy to read and understand. Correct terminology was used when needed. Original formatting is maintained. Entries are in alphabetical order.