Milestone Four IT510

IT 510 Milestone Four Guidelines and Rubric You will submit your system design via a Word document. The system design will include visual presentations of each of the following: modeling for specifications, data design, and user interface design. Each of the diagrams will visually represent your design. The system design additionally will include each explanation and supporting detail of the system design execution, in a complete and comprehensive write up. These are sections systems architecture and feasibility analysis. Your audience is IT management and the IT project team. References for Review For a template reference, review your textbook, Systems Analysis and Design, Chapter 2.

 Step 6: Present results and recommendations to management. Next, review Toolkit Part A: Communication Tools. You may also research on the internet for a systems analysis template for a reference.

 Use the example templates to develop your deliverable. Ensure you cover the specifics outlined in the Final Project Document. Specifically the following critical elements must be addressed:

III. Systems Design: Propose a solution that addresses the identified problem in your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.

a) Specifications: Provide a physical design that will meet the specifications outlined in the systems requirement document. b) Data Design: Create entity relationship diagrams (ERDs) that accurately describe the proposed solution, including 3NF table designs. c) User Interface Design: Illustrate the user interface design. Specifically, be sure to address your proposed human computer interactions (HCIs) and

graphical user interfaces (GUIs). Your proposals should follow user-centered design principles and address all design requirements. d) System Architecture: Describe the system architecture. Specifically, be sure to address the corporate organization and culture, enterprise

resource planning, total cost of ownership, scalability, integration and interface requirements, and security. e) Feasibility Analysis: Provide supporting details that justify why your proposed solution is appropriate for solving the problem. In your defense, be

sure to address operational, technical, economic, and scheduling feasibility. Be sure that you frame your response for communicating effectively to your target audiences.

Rubric Guidelines for Submission: Milestone Four 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

Specifications

Meets “Proficient” criteria and physical design reflects an in- depth analysis of the Systems Development Life Cycle

Provides a physical design that comprehensively meets the specifications outlined in the systems requirement document

Provides a physical design, but does not comprehensively meet the specifications outlined in the systems requirement document

Does not provide a physical design

20

Data Design

Meets “Proficient” criteria and diagrams reflect in-depth evaluation of structure and object oriented analysis modeling

Creates ERDs that accurately describe the proposed solution, including 3NF table designs

Creates ERDs, but there are gaps or inaccuracies in describing the solution or does not include 3NF table designs

Does not create ERDs 20

User Interface Design

Meets “Proficient” criteria and user interface design reflects an in-depth examination of structure and object oriented analysis modeling

Illustrates the user interface design (including HCIs and GUIs) that follow user-centered design principles and address all design requirements

Illustrates the user interface design, but does not include HCIs and GUIs, does not follow user-centered design principles, or does not address all design requirements

Does not illustrate the user interface design

15

System Architecture

Meets “Proficient” criteria and system architecture reflects an in-depth assessment of the Systems Development Life Cycle

Describes the system architecture by addressing the corporate organization and culture, enterprise resource planning, total cost of ownership, scalability, integration and interface requirements, and security in specific detail

Describes the system architecture, but does not address either the corporate organization and culture, enterprise resource planning, total cost of ownership, scalability, integration and interface requirements, or security in specific detail

Does not describe the system architecture

20

Feasibility Analysis

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

Justifies the proposed solution by addressing operational, technical, economic, and scheduling feasibility in a manner suitable for the target audiences

Justifies the proposed solution, but does not fully address operational, technical, economic, or scheduling feasibility in a manner suitable for their target audiences

Does not justify the proposed solution in terms of its feasibility

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%