The purpose of this assignment is to encourage you and the children to move beyond the basic, classic self-expressive experiences, such as standard easel painting or block play, and to present some variation of a self-expressive activity that is appropriate and interesting for young children. This will provide variety for them as well as furnishing you with an opportunity to try out your own inspiration.
Remember that self-expression occurs in play as well as with “art” materials, so the activity could be any of the following: blocks, carpentry, easel painting (with variations from the standard form), creative dramatic play, dance, or a multitude of additional possibilities, providing these lend themselves to free-form experiences, not copying models or making things according to an adult-determined plan. Do your best to keep it a “Column One, Maximum Creative Potential” activity if using self-expressive materials. Also, avoid spending a lot of money on extra things. It’s far better to have plenty of whatever you offer than a small, costly dab of something you could never afford to use when you are teaching professionally.
1. Briefly describe the project.
2. Describe two (2) ways the project allows the children to express themselves.
3. List the other four (4) selves (social, emotional, cognitive, and physical) and explain how this project benefited those selves.
4. List four (4) things you would say or do that are intended to make the project creative for the children.
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
