IT 510 Milestone Three Guidelines and Rubric
You will submit your system requirements. The system requirements model is to be submitted as a Word document that is a combination of sections: a requirements model, a business process model, a data flow diagram, a data dictionary, an object model, and a use case diagram. Copy the image of your diagram into your Word document and include text to ensure that the diagram has proper context within the overall system requirements model through written explanations. Your audience is IT management and the IT project team.
Specifically the following critical elements must be addressed:
- System Requirements: Detail the specific requirements of your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.
- Requirements Modeling: Assess the current system to identify the requirements for the new system. Be sure to address each of the following aspects: outputs, inputs, processes, performance, and controls (i.e., security).
- Business Process Model: Create a visual representation of all relevant data processes that represents a logical model of the requirements of the system based on the systems development life cycle.
- Data Flow Diagram: Create a visual representation of the data flow based on the systems development life cycle.
- Data Dictionary: Create a data dictionary that annotates your system requirements to build clarity in communicating with the relevant audiences.
- Object Modeling: Use appropriate object modeling techniques and tools to describe the system requirements.
- Use Case Diagrams: Create (a) use case diagram(s) that outline the system requirements based on the systems development life cycle.
What to Submit
Milestone Three should follow these formatting guidelines: 46 pages, double-spacing, 12-point Times New Roman font, one-inch margins, and citations in APA.
Milestone Three Rubric
| Criteria | Proficient (100%) | Needs Improvement (70%) | Not Evident (0%) | Value |
|---|---|---|---|---|
| Requirements Modeling | Assesses the current system to accurately identify the requirements for the new system (including the outputs, inputs, processes, performance, and controls) using specific examples | Assesses the current system, but either does not accurately identify the requirements for the new system; does not address the outputs, inputs, processes, performance, or controls; or does not use specific examples | Does not assess the current system to identify the requirements for the new system | 13 |
| Business Process Model | Creates a visual representation of all relevant data processes, representing an accurate logical model of the requirements of the system based on the systems development life cycle | Creates a visual representation of data processes, but there are significant gaps or the logical model of the requirements of the system is not appropriately based in the systems development life cycle | Does not create a visual representation of data processes | 13 |
| Data Flow Diagram | Creates an accurate visual representation of the data flow based on the systems development life cycle | Creates a visual representation of the data flow, but there are significant gaps or inaccuracies based on the systems development life cycle | Does not create a visual representation of data flow | 13 |
| Data Dictionary | Creates a data dictionary that annotates the system requirements and would effectively build clarity with relevant audiences | Creates a data dictionary that annotates the system requirements, but there are gaps or clarity issues given the needs of relevant audiences | Does not create a data dictionary that annotates the system requirements | 13 |
| Object Modeling | Uses appropriate object modeling techniques and tools to effectively describe the system requirements | Uses object modeling techniques and tools, but either the tools or the description of the system requirements are ineffective | Does not use object modeling techniques and tools | 13 |
| Use Case Diagrams | Creates (a) use case diagram(s) that accurately outline the system requirements based on the systems development life cycle | Creates (a) use case diagram(s), but there are gaps or inaccuracies in the system requirements based on the systems development life cycle | Does not create (a) use case diagram(s) | 13 |
| Diagram Context and Explanation | Supports diagram(s) with proper context within the overall system requirements model through written explanations | Supports diagram(s) with improper context or not within the overall system requirements model | Does not supports diagram(s) | 12 |
| Articulation of Response | Submission has no major errors related to citations, grammar, spelling, syntax, or organization | Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas | Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas | 10 |
| Total: | 100% | |||
