Project Description
The Human-Computer Interaction Lab (HCIL) allows the iSchool to showcase its
proficiency in Human-Computer Interaction (HCI) research and provide information
about the University of Maryland’s range of degrees in HCI. Our project will fulfill the
client’s needs by applying HCI design principles to best serve their audience while
utilizing cost-effective means. This website must display current content created by the
iSchool as well as degree descriptions in an effective, easily navigable way. To achieve
optimal returns from the HCIL website, the project will apply HCI and User-Centered
Design principles as the main development framework. These principles will steer the
project towards developing a website that guarantees maximum customization and high
performance.
The website been analyzed:
https://dev.hcil.umd.edu/
Your team will be outlining and developing a project plan that will describe the major
milestones that will be completed this semester and the subtasks, deadlines, and team
members assigned to achieve those milestones. Successful project plans need to map
to your requirements document and the tasks that you will need to complete to deliver a
satisfactory project (whether it’s a series of reports, a website, a data management plan,
or user interface guidelines).
Project plans typically include the phases (milestones) of a project, activities in each
phase, task end and start dates, interdependencies between tasks, and the specific
individual assigned.
For this assignment, please upload your project plan, which should include the Abstract,
Scope, Schedule including resources, Communications Plan, and Deliverables. This
document should be professional, as if you were presenting it to an official client who
would pay for your services. It should also be extremely detailed as you will use it
throughout the semester in project check-in meetings.
Format:
1. Abstract
(Copy from Requirements Document)
2. Scope
(Include a very brief Introduction Statement)
3. Schedule
(Include a very brief Introduction Statement)
(Include a table with the schedule)
(Include a Gantt Chart)
Include assigned resources
4. Communication Plan
(Include a very brief Introduction Statement)
Include a table with:
Contact at Client site (with name | email | phone)
Contact at UMD (include Project Manager and Bill Kules/TA/Me/Sakshi)
5. Deliverables
(Bullet pointed list of deliverables for the project)
This is what I have so far:
CAPSTONE: Website Design for Human Computer Interaction Lab
1. Abstract
The Human-Computer Interaction (HCIL) lab at the iSchool needs a redesigned
website. This design will hopefully improve the interaction of the website between
alumni, current and future members, and anyone else who has an interest in joining
the HCIL. This document will explain the design process and what took place while
making the new website.
2. Scope
The project itself exists of taking selected parts of the older website and integrating
them into the new website, adding new elements, and taking out old elements that
Beth Domingo has deemed unnecessary. -sam
3. Schedule
(Include a very brief Introduction Statement)
This schedule is meant to show markers, milestones, and tasks that are meant to be
accomplished by a certain date. If we find it necessary to go to a previous task to
make edits, the schedule will indeed be adjusted. In addition to adjustments, this
schedule will also keep the team on track -sam
(Include a table with the schedule)
(Include a Gantt Chart)
Include assigned resources
4. Communication Plan
(Include a very brief Introduction Statement)
We plan on making Skype calls weekly on Wednesday nights. This time and day
seems to be the best for each team member, including Beth Domingo. Progress
reports will be made and concerns or suggestions made by Beth Domingo will be
addressed.
Include a table with:
Contact at Client site (with name | email | phone)
Contact at UMD (include Project Manager and Bill Kules/TA/Me/Sakshi)
5. Deliverables
(Bullet pointed list of deliverables for the project)
•
A new website with source code to show how the website operates( can change
later sam
ID Milestone
Propose New
Data to Collect
2
Configure
Microsoft
Dynamic
Task
1.1 Research Business
Intelligence and Contract
Bidding Literature
1.2 Examine Data
Currently Collected
1.3 Research Potential New
Data
1.4 Develop Standards for
Old and New Data
Collection
1.5 Propose New Data and
Standardizations
1.6 Document Research,
Data Proposal, and
Standardizations
2.1 Create Content Pages
2.2 Configure Partnering
Page
2.3 Configure Opportunity
Page
2.5 Configure Contacts
Page
2.5 Configure Document
Management Settings
2.6 Configure Data
Management Settings
Description
Research professional advice and
literature to determine valuable
data
Interview and examine current
data to determine missing data
Explore potential data for
business intelligence and
decisions
Design business rules and data
formatting for old and new data
Write small proposal report and
speak with client
Record all decisions, steps, and
rules for reference and future
report building
Content pages to be created:
1. Home Page
2. Instruction Page (placeholder)
Design and configure page to
collect, store, and display
partnering information
Design and configure page to
collect, store, and display
opportunity information
Interview and examine current
data to determine missing data
Implement and organize
document management settings
Implement and organize data
management rules
2.7 Create Forms
2.8 Configure Analytics
2.9 Configure Reporting
2.10 Perform Unit Testing
2.11 Perform Client User
Acceptance Testing
2.12 Fix Bugs
3
Migrate data
from existing
system to
Microsoft
Dynamics
2.13 Document steps,
decisions, problems, and
solutions
3.1 Accumulate data and
capability matrices
3.2 Import Data
3.3 Perform Unit Testing
3.4 Fix bugs
4
Test and Debug
System
3.5 Document steps,
decisions, problems, and
solutions
4.1 Test content pages
4.2 Test forms
4.3 Test links
4.4 Test cross-browser
functions
4.5 Test reporting
4.6 Test analytics
4.7 Test system with
DELTA’s information
process
4.8 Perform Client user
Acceptance Testing
4.9 Fix bugs
4.10 Document steps,
decisions, problems, and
solutions
Design and configure forms for
data entry
Design and configure statistical
tests for data
Design and configure graphs,
tables, and pdfs for reports
Test each page for functionality
or bugs
Demonstrate page for Client for
acceptance
Fix bugs or issues introduced
during testing
Record all decisions, steps, and
rules for reference and future
report building
Collect capability matrices from
Business Development Group
Import or enter data into
Dynamics
Test Data and Reports for
functionality or bugs
Fix bugs or issues introduced
during testing
Record all decisions, steps, and
rules for reference and future
report building
Enact final testing for system
Enact final testing for system
Enact final testing for system
Enact final testing for system
Enact final testing for system
Enact final testing for system
Enact final testing for system
with DELTA employee
Demonstrate system and
information process for client for
acceptance
Fix bugs or issues introduced
during testing
Record all decisions, steps, and
rules for reference and future
report building
5
Develop
Documentation
5.1 Prepare user manual
5.2 Client approval for user
manual
5.3 Prepare Building
Microsoft Dynamics report
5.4 Client approval for
report
5.5 Prepare DELTA’s
Information Process Report
6
Deploy
Microsoft
Dynamics
5.6 Client approval for
report
5.7 Develop training for
using Microsoft Dynamics
5.8 Client approval for
training
6.1 Train client and
stakeholders
6.2 Provide feedback and
assistance until semester is
complete
Accumulate all documentation
and knowledge to create user
manual for system
Send to client for approval
Accumulate all documentation
and knowledge to create report
discussing how system was built
Send to client for approval
Accumulate all documentation
and knowledge to create report
discussing DELTA’s Information
Process with system
Send to client for approval
Develop PowerPoint slides and
data dictionary for training
Send to client for approval
Present to client and Business
Development group
Remain available for questions,
issues, or problems
Schedule
The project schedule is a detailed plan for milestones and tasks; below lists
important planned start and end dates for the tasks.
Task
1.1 Research Business Intelligence and Contract
Bidding Literature
1.2 Examine Data Currently Collected
1.3 Research Potential New Data
1.4 Develop Standards for Old and New Data
Collection
1.5 Propose New Data and Standardizations
Start
Date
1/25/201
7
1/25/201
7
1/25/201
7
1/29/201
7
1/29/201
7
End Date
1/26/201
7
1/27/201
7
2/1/2017
2/3/2017
2/3/2017
1.6 Document Research, Data Proposal, and
Standardizations
2.1 Create Content Pages
2.2 Configure Partnering Page
2.3 Configure Opportunity Page
2.5 Configure Contacts Page
2.5 Configure Document Management Settings
2.6 Configure Data Management Settings
2.7 Create Forms
2.8 Configure Analytics
2.9 Configure Reporting
2/1/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/5/2017
2/3/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
3/5/2017
Purchase answer to see full
attachment
Why Choose Us
- 100% non-plagiarized Papers
- 24/7 /365 Service Available
- Affordable Prices
- Any Paper, Urgency, and Subject
- Will complete your papers in 6 hours
- On-time Delivery
- Money-back and Privacy guarantees
- Unlimited Amendments upon request
- Satisfaction guarantee
How it Works
- Click on the “Place Order” tab at the top menu or “Order Now” icon at the bottom and a new page will appear with an order form to be filled.
- Fill in your paper’s requirements in the "PAPER DETAILS" section.
- Fill in your paper’s academic level, deadline, and the required number of pages from the drop-down menus.
- Click “CREATE ACCOUNT & SIGN IN” to enter your registration details and get an account with us for record-keeping and then, click on “PROCEED TO CHECKOUT” at the bottom of the page.
- From there, the payment sections will show, follow the guided payment process and your order will be available for our writing team to work on it.