Milestone Three IT510

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 data 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:

II. System Requirements: Detail the specific requirements of your case. Be sure to include screenshots of all relevant diagrams, charts, and tables. a) 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). b) Data 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. c) Data Flow Diagram: Create a visual representation of the data flow based on the systems development life cycle. d) Data Dictionary: Create a data dictionary that annotates your system requirements to build clarity in communicating with the relevant

audiences. e) Object Modeling: Use appropriate object modeling techniques and tools to describe the system requirements. f) Use Case Diagrams: Create (a) use case diagram(s) that outline the system requirements based on the systems development life cycle.

Rubric Guidelines for Submission: Milestone Three should follow these formatting guidelines: 4–6 pages, double-spacing, 12-point Times New Roman font, one-inch margins, and citations in APA.

Critical Elements Exemplary (100%) Proficient (90%) Needs Improvement (75%) Not Evident (0%) Value

Requirements Modeling

Meets “Proficient” criteria and selects particularly insightful examples and supporting evidence

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

15

Data Process Model

Meets “Proficient” criteria and visual representation of the systems development life cycle is substantiated with examples

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

15

Data Flow Diagram

Meets “Proficient” criteria and visual representation reflects an in-depth assessment of the systems development life cycle

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

15

Data Dictionary

Meets “Proficient” criteria and definitions reflect an in-depth evaluation of the paradigms, processes, and activities of IT systems

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

15

Object Modeling

Meets “Proficient” criteria and techniques and/or results demonstrate in-depth examination of structure and object-oriented analysis 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

15

Use Case Diagrams

Meets “Proficient” criteria and diagram(s) reflect(s) an in-depth assessment of the systems development life cycle

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)

15

Articulation of Response

Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy-to-read format

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

Earned Total 100%