IT510 Final Project Guidelines and Rubric
Question # 00500806
Posted By:
Updated on: 03/15/2017 06:31 PM Due on: 03/16/2017
IT 510 Final Project Guidelines and Rubric
Overview
The final project for this course is the creation of a System Proposal Document.
In any modern enterprise, it is crucial that all of the different stakeholders, users, inputs, and outputs that relate to the business’s IT systems coalesce in a logical
and cohesive way for the systems to be effective. As a member of an IT team, your overarching goal is to ensure that the IT systems ultimately do what the
business needs them to do. In this course, you have learned about the key principles and practices underlying the analysis, design, implementation, and
management of IT systems. In this final project, you will apply this knowledge by creating a systems proposal document.
The project is divided into four milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final
submissions. These milestones will be submitted in Module Two, Module Four, Module Six, and Module Eight. The final submission will occur in Module Nine.
In this assignment, you will demonstrate your mastery of the following course outcomes: Assess the relationship of systems analysis, design, implementation, and development processes as they relate to the management of information
technology systems
Communicate the paradigms, processes, and activities of systems development to diverse audiences
Apply structure and object oriented analysis modeling techniques to analyze, design, and manage information technology systems
Construct written and visual representations of the analysis, design, implementation, and management of information technology systems based on the
systems development life cycle Prompt
You will select your own case study and will apply the content provided, describing the business process to complete the final project. Alternate sources for case
studies include the case studies found in the textbook with the exception of the Personal Trainer Case. You can additionally search the internet for business case
ideas.
You will complete an analysis of an existing information technology system and make recommendations for updates to meet business goals based on your chosen
case study. Your final submission will include an introduction, systems requirements, systems design specifications, and an implementation plan. All of the
components listed below should be submitted as a single, organized systems proposal document and include screenshots of all relevant diagrams, charts, and
tables.
I. Introduction: Provide an overview of your selected case. Be sure to provide appropriate citations and reference to the case study you have selected. a) Background: Establish a context for understanding your systems proposal. Specifically, explain any essential paradigms, processes, and activities
of the existing information technology systems.
b) Problem Statement: What is the problem that needs to be solved? Why is it a problem? What are the impacts to the enterprise?
c) Audience: Who are your audiences for this systems proposal? How will you effectively communicate the information of your proposal to these
diverse groups?
II. Systems 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 Diagrams: 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.
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 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.
IV. Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams, charts,
and tables.
a) Work Breakdown Structure: Describe all of the essential roles and functions required for implementing the solution. Who will be doing the work
and what, specifically, will they need to do?
b) Project Monitoring and Control Plan: How are you going to ensure that the project is going smoothly? What is your plan of attack to ensure that
all controls are adhered to? What is the defined critical path? Be sure that you frame your response for communicating effectively to your target
audiences.
c) Timeline: What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Gantt
chart) based on the systems development life cycle. Milestones
Milestone One: Business Case Proposal and Introduction
In Module Two, you will submit a business case proposal, which is a summary of your selected business case for the course project. The business case proposal
will be submitted as a Word document and in paragraph form. This business case proposal provides your instructor insight into the project you are selecting and
allows for instructor feedback and guidance in terms of the scope of the business case for the purpose of this course. The first milestone of the course project is
an introduction. This milestone is graded with the Milestone One Rubric.
Milestone Two: Project Plan
In Module Four, you will submit your project plan. The project plan is a Word document that is a combination of a written explanation of the project plan and
the explanation of the control plan. The WBS and timeline are represented with screenshots of the Gantt chart, resource chart, and cost table. Ensure each chart
and graph is properly noted and has text explanation. This milestone is graded with the Milestone Two Rubric.
Milestone Three: System Requirements
In Module Six, 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. This milestone is graded with the Milestone Three Rubric.
Milestone Four: System Design
In Module Eight, 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 the sections Systems Architecture and
Feasibility Analysis. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Four Rubric.
Final Submission: System Proposal Document
In Module Nine, you will submit a systems proposal document. It should be a complete, polished artifact containing all of the critical elements of the final
product. It should reflect the incorporation of feedback gained throughout the course. This milestone will be graded using the Final Project Rubric. Deliverable Milestones
Milestone
1 Deliverables Module Due Grading Two Graded separately; Milestone One Rubric Four Graded separately; Milestone Two Rubric Six Graded separately; Milestone Three Rubric 2 Business Case Proposal and
Introduction
Project Plan 3 System Requirements 4 System Design Eight Graded separately; Milestone Four Rubric Final Product: System Proposal
Document Nine Graded separately; Final Project Rubric Final Project Rubric
Guidelines for Submission: Written components of projects must follow these formatting guidelines when applicable: double spacing, 12-point Times New
Roman font, one-inch margins, and APA citations. The paper should be 30 to 40 pages, not including cover page and resources.
Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information,
review these instructions.
Critical Elements
Overview
The final project for this course is the creation of a System Proposal Document.
In any modern enterprise, it is crucial that all of the different stakeholders, users, inputs, and outputs that relate to the business’s IT systems coalesce in a logical
and cohesive way for the systems to be effective. As a member of an IT team, your overarching goal is to ensure that the IT systems ultimately do what the
business needs them to do. In this course, you have learned about the key principles and practices underlying the analysis, design, implementation, and
management of IT systems. In this final project, you will apply this knowledge by creating a systems proposal document.
The project is divided into four milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final
submissions. These milestones will be submitted in Module Two, Module Four, Module Six, and Module Eight. The final submission will occur in Module Nine.
In this assignment, you will demonstrate your mastery of the following course outcomes: Assess the relationship of systems analysis, design, implementation, and development processes as they relate to the management of information
technology systems
Communicate the paradigms, processes, and activities of systems development to diverse audiences
Apply structure and object oriented analysis modeling techniques to analyze, design, and manage information technology systems
Construct written and visual representations of the analysis, design, implementation, and management of information technology systems based on the
systems development life cycle Prompt
You will select your own case study and will apply the content provided, describing the business process to complete the final project. Alternate sources for case
studies include the case studies found in the textbook with the exception of the Personal Trainer Case. You can additionally search the internet for business case
ideas.
You will complete an analysis of an existing information technology system and make recommendations for updates to meet business goals based on your chosen
case study. Your final submission will include an introduction, systems requirements, systems design specifications, and an implementation plan. All of the
components listed below should be submitted as a single, organized systems proposal document and include screenshots of all relevant diagrams, charts, and
tables.
I. Introduction: Provide an overview of your selected case. Be sure to provide appropriate citations and reference to the case study you have selected. a) Background: Establish a context for understanding your systems proposal. Specifically, explain any essential paradigms, processes, and activities
of the existing information technology systems.
b) Problem Statement: What is the problem that needs to be solved? Why is it a problem? What are the impacts to the enterprise?
c) Audience: Who are your audiences for this systems proposal? How will you effectively communicate the information of your proposal to these
diverse groups?
II. Systems 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 Diagrams: 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.
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 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.
IV. Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams, charts,
and tables.
a) Work Breakdown Structure: Describe all of the essential roles and functions required for implementing the solution. Who will be doing the work
and what, specifically, will they need to do?
b) Project Monitoring and Control Plan: How are you going to ensure that the project is going smoothly? What is your plan of attack to ensure that
all controls are adhered to? What is the defined critical path? Be sure that you frame your response for communicating effectively to your target
audiences.
c) Timeline: What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Gantt
chart) based on the systems development life cycle. Milestones
Milestone One: Business Case Proposal and Introduction
In Module Two, you will submit a business case proposal, which is a summary of your selected business case for the course project. The business case proposal
will be submitted as a Word document and in paragraph form. This business case proposal provides your instructor insight into the project you are selecting and
allows for instructor feedback and guidance in terms of the scope of the business case for the purpose of this course. The first milestone of the course project is
an introduction. This milestone is graded with the Milestone One Rubric.
Milestone Two: Project Plan
In Module Four, you will submit your project plan. The project plan is a Word document that is a combination of a written explanation of the project plan and
the explanation of the control plan. The WBS and timeline are represented with screenshots of the Gantt chart, resource chart, and cost table. Ensure each chart
and graph is properly noted and has text explanation. This milestone is graded with the Milestone Two Rubric.
Milestone Three: System Requirements
In Module Six, 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. This milestone is graded with the Milestone Three Rubric.
Milestone Four: System Design
In Module Eight, 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 the sections Systems Architecture and
Feasibility Analysis. Your audience is IT management and the IT project team. This milestone is graded with the Milestone Four Rubric.
Final Submission: System Proposal Document
In Module Nine, you will submit a systems proposal document. It should be a complete, polished artifact containing all of the critical elements of the final
product. It should reflect the incorporation of feedback gained throughout the course. This milestone will be graded using the Final Project Rubric. Deliverable Milestones
Milestone
1 Deliverables Module Due Grading Two Graded separately; Milestone One Rubric Four Graded separately; Milestone Two Rubric Six Graded separately; Milestone Three Rubric 2 Business Case Proposal and
Introduction
Project Plan 3 System Requirements 4 System Design Eight Graded separately; Milestone Four Rubric Final Product: System Proposal
Document Nine Graded separately; Final Project Rubric Final Project Rubric
Guidelines for Submission: Written components of projects must follow these formatting guidelines when applicable: double spacing, 12-point Times New
Roman font, one-inch margins, and APA citations. The paper should be 30 to 40 pages, not including cover page and resources.
Instructor Feedback: This activity uses an integrated rubric in Blackboard. Students can view instructor feedback in the Grade Center. For more information,
review these instructions.
Critical Elements
-
Rating:
/5
Solution: IT510 Final Project Guidelines and Rubric