musical empowerment systems analysis & design, december 2016
TRANSCRIPT
Claudiel Tejeda, Chenoa Capasso, Maria De Leon
DECEMBER 5, 2016
UNIVERSITY OF MASSACHUSETTS LOWELL
1 University Ave. Lowell, Ma 01851
1
Index
Content Page Number
Milestone I
Project Scenario
2
Project Alternatives 3
Project Feasibility & Economic
Feasibility Analysis
4
Operational, Technical, Schedule,
Legal and Contractual, and Political
Feasibilities
5
Manageable Tasks: Gantt Chart 6-7
Manageable Tasks: PERT results
Manageable Tasks: Network Diagram
8-9
Tangible Cost and Benefits Worksheet 10
Plans and Budget & Communication
Plan
11
Project Standards and Procedures &
Project Risk
12
Baseline Project Plan 13-14
Project Scope 15-16
User Requirements & System
Requirements
16-17
Milestone II
Data Flow Diagrams
18-19
Entity Relationship Diagram 20
Data Dictionary 21-22
Milestone III
Form and Report Designs
23
Interface and Dialogue Designs 24-31
Working System (screen shots) 32-35
Documentations 36-38
2
Milestone I
1.2 - Project Scenario
Project Name: Musical Empowerment
Project Managers: Claudiel Tejeda, Maria De Leon, Chenoa Capasso
Customer: The University of Massachusetts Lowell
Project Sponsor: University of Massachusetts School of Music
Project Start/End (projected) dates: September 21, 2016 – December 21, 2017
1.2.1 - Project overview and scope:
The project will implement a music lesson system, which will teach students how to play the
major string instruments (guitar and piano), and provide them with basic music lessons so that
they can stay enrolled in the undergraduate program. The program will be offered online and will
provide instructors with means to record and upload videos for their students. Students will be
able to record themselves as well, so their instructors can see teach during live/ interactive
lessons. The program will allow students to access music materials and lessons on-demand. As
well as offer optional lessons in person with approved instructors for a small monthly fee.
Objectives:
- Reduce the turnover rate amongst music majors
- Teach students fundamentals of playing (i.e. how to hold guitar, how to strum)
- Increase undergraduate music program awareness
- Improve classroom performance
Key Assumptions:
- System will have access to student and faculty database
- Lessons and content will be available 24/7 on the web
- There will be a monthly fee for the in-person lessons
Stakeholders and Responsibilities:
Stakeholder: Role: Responsibility: Signatures:
Eddie Van Halen VP of Marketing Advertising, Social Media
Jeff Beck CIO Technology, HW, SW
Robert Plant CFO Budget, Finances
Thomas Mars CEO Project Scope
Chenoa Capasso Project Manager Management, Direction
Claude Tejeda Systems Analyst Analytics, Design, Implementation
Maria De Leon Project Manager Management, Direction
3
1.2.2 - Project Alternatives
Alternative 1 Alternative 2 Alternative 3
Musical Empowerment Online Lessons on
Blackboard
In-Class Lessons
Pros
❖Reduce the turnover rate
amongst music majors
❖ Teach students
fundamentals of playing
(how to hold guitar, how to
strum)
❖Increase undergraduate
music program awareness
❖Improve classroom
performance
❖Generate revenue for the
university
Pros
❖Eliminates the costs for
creating and maintaining a
new web-site
❖Allows students to use
Blackboard tools
❖Low Cost
❖Easy to use
❖Generate Revenue for
creating a new optional
course
Pros
❖Eliminates the costs for
creating and maintaining a
new web-site
❖Students will have in-person
lessons
❖Allows students to receive
instant feedback
❖Eliminates Blackboard use
❖Generate Revenue for
creating a new course
Implementation
❖System will have access to
student and faculty database
❖Systems Development Life
Cycle Methodology
❖System will be web based
so that students can have
access to the website 24/7
Implementation
❖Students will enroll in this
course through SIS
❖University must hire part-
time instructors for music
lessons
❖Content will be share in
Blackboard
❖Content will be available
only for a semester
Implementation
❖ Students will enroll in this
course through SIS
❖ Students cannot sign up for
this course if they do not meet
the requirements
❖Students will meet with
instructor twice a week
(UMASS Lowell Calendar
Basis).
❖ University must hire full-
time instructor for music
lessons
❖ Content will be share in-
class and through e-mail
4
1.2.3 - Project Feasibility
Economic Feasibility:
(Please see Benefits and Costs analysis as well as Break Even Analysis)
1.2.3.1 - Economic Feasibility Analysis
The break-even occurs between Year 1 and 2, which happens roughly during the month of
March in 2019.
ROI- 40.3%
5
1.2.3.2 - Operational Feasibility:
Our instrument fundamentals system will improve the undergraduate music program operation
across the board on all levels. Not only will students perform better in their music courses but it
will also attract more freshmen students into the program.
1.2.3.3 - Technical Feasibility:
Our top-notch IT team and excellent systems analyst will identify the necessary technology and
challenges, design the right system, and implement it with superb results.
1.2.3.4 - Schedule Feasibility:
We have enough time to create the system, test it, and deploy it in time for the fall 2017
semester. Targeted milestones and timeframes will be developed and followed using Project
Management Software. Milestones and tasks will be tracked using Gantt charts and Network
Diagrams.
1.2.3.5 - Legal and Contractual Feasibility:
Our team is under contract with the University of Massachusetts. Its president, Marty Meehan,
has hired us; we have little to worry about in regards to legal and contractual feasibility. This
project will follow the same legal procedures of other on-line implemented programs at the
University.
1.2.3.6 - Political Feasibility:
System will be politically feasible. We will attain permission from the CEO of the University of
Massachusetts Lowell’s Music Department. The CIO will provide us with the necessary
hardware and software that will allow our operation to become a reality. In addition, the VP of
Marketing will help spread the word through social media.
6
1.3 - Manageable Tasks: Gantt Chart
7
8
1.3 - Manageable Tasks: PERT results
1.3 - Manageable Tasks: Network Diagram
9
10
1.4 - Tangible Cost and Benefits Worksheet
11
1.5 - Plans and Budget
Preliminary Plan:
Our preliminary plan is to implement this website system and make it available for students in
the 2017 Spring Semester. We believe that the benefits will be much greater than the costs.
Preliminary Budget:
The budget for this project will be $60,000. This includes our one-time startup costs as well as
the first year’s expected incurred costs.
1.6 - Communication Plan
Stakeholder Document Format Team Contact Date Due
Team Members Project Status
Report
Project Intranet Claudiel
Chenoa
September 26,
2016
Management
Supervisor
Project Status
Report
Hard Copy Claudiel
Maria
October 10, 2016
User Project Status
Report
Hard Copy Maria
Chenoa
October 24, 2016
Internal IT Staff Project Status
Report
E-mail Maria
Claudiel
November 7,
2016
IT Manager Project Status
Report
Hard Copy Chenoa
Claudiel
November 21,
2016
Contract
Programmers
Software
Specification
E-mail/Project
Intranet
Chenoa
Maria
December 5,
2016
Training
Subcontractor
Implementation
and Training Plan
Hard Copy Claudiel
Chenoa
December 19,
2016
12
1.7 - Project Standards and Procedures
Project Standards and Procedures:
Throughout the scope of the project, we will strictly adhere to the guidelines of the Systems
Development Life Cycle, including careful planning, selection, systems analysis, design and
finally implementation. We will focus on developing the systems with Agile Methodologies
ensuring the system runs efficiently and is consistently updated to enhance user experience. The
project will follow the timeline implemented.
1.8 - Project Risk
Project Risks:
The only risk for this project to fail is time constraint. There is a great risk if the project does not
meet the critical path. Therefore, delaying the project can incur more costs.
13
1.9 - Baseline Project Plan
Introduction
The University of Massachusetts Lowell Music School has very low turnover rates, and thus, the
music program is diminishing and losing its reputation. Musical Empowerment is a system that
will offer a virtual classroom for music lessons. The system will be developed, implemented,
and ready for use coming spring 2017. The schedule has been structured using Microsoft Project
(a project management software). Such tasks on the timeline include Design, Implementation,
Testing, Installation, User Training, etc. We plan to have the System Design completed by
March 10, 2017 and the System
Implementation completed by December 21, 2016 (see Gantt chart for further detail).
The program will be compatible with the University’s existing computer software as well as
standard recording equipment. This makes use easy for both students and instructors.
The budget established will be enough to complete given tasks.
System Description
System Description:
The project will implement a music lesson system, which will teach students how to play the
major string instruments (guitar and piano), and provide them with basic music lessons so that
they can stay enrolled in the undergraduate program. The program will be offered online and
will provide instructors with means to record and upload videos for their students. Students will
be able to record themselves as well, so their instructors can see teach during live/ interactive
lessons. The program will allow students to access music materials and lessons on command. As
well as offer optional lessons in person with approved instructors for a small monthly fee.
Alternatives:
Online alternative already offered at UMass Lowell, Blackboard. Using the structure of
Blackboard to host a similar Online Music School, but it will be less advanced and not music
specified.
In-class lessons
Feasibility Assessment
The budget we have come up with for this project is $60,000. Between startup costs and
the first year’s projected costs, the amount totals $58,050. We rounded up just in case any minor
costs along the way arise. To implement an entire new system that will in turn increase the
awareness and overall capabilities of the Music School, we see that the price of the initial
development and then yearly costs are a small price to pay. (Please Costs/Benefits analysis and
Break Even Analysis for further detail)
14
The schedule we have laid the development down on, for the span of a year, is feasible and offers
sufficient time for each task to be done. Fall 2016- Spring 2017. (Please see the Gantt chart for
further detail)
Management Issues
The project is aiming to be ran smoothly and efficiently. The project will be following
the specific timeline that has been projected. There are tasks that are going to be more difficult
and take significantly longer than others, and during those times we will have all hands-on deck.
The development of our system will be carefully watched over and made sure that everything is
followed to protocol. If we stray from the timeline, run into staffing issues, or have a mishap in
the development, the project could be delayed.
15
1.10 - Scope Statement
University of Massachusetts Lowell Prepared by: Chenoa, Claudiel,
Maria
Project Scope Statement Date: December 21, 2016
General Project Information:
Project Name: Musical Empowerment
Sponsor: University of Massachusetts School of Music
Project Manager(s): Chenoa, Claudiel, Maria
Problem/ Opportunity Statement:
The Music School at the University of Massachusetts Lowell has a very high turnover
rate amongst undergraduate students. Students are learning musical theory in class, but
are entering the program lacking the fundamental ability to play their instrument.
Thus, enrollment into the music program is diminishing and revenue is being lost.
Project Objectives:
o Teach students fundamentals of playing (i.e. how to hold guitar, how to strum)
o Increase undergraduate music program awareness
o Improve classroom performance
o Implement virtual classroom
Project Description:
The project will implement a music lesson system which will teach students how to play
the major string instruments (guitar and piano), and provide them with basic music
lessons so that they can stay enrolled in the undergraduate program. As well as offer
optional lessons in person with approved instructors for a small monthly fee.
Business Benefits:
o Attract a higher number of undergraduate and graduate students to the Music School
o Increase revenue for the University
o Reduce the turnover rate amongst music majors.
o Increase productivity of students enrolled in the program
Project Deliverables:
o Virtual music classroom featuring string instruments
o Video lessons
o Student and instructor communication via web
16
Estimated Project Duration:
3 months- 90 days
2.0 - User Requirements
User Requirements:
We estimate that User Training will be a one-time cost and will estimate to $750. We must train
the instructors who are assigned to use the program to record and then upload their lessons,
videos, and other interactive materials to the website. We must ensure we train them thoroughly
enough so they can then show their students how to navigate the website. We will also give a
brief user tutorial to members of the Music Program so they are aware of the programs being
utilized by their staff. The website will be an easy navigation and will have a similar setup to
Blackboard, therefore training should not be that extensive.
3.0 - System Requirements
System Requirements:
The system requirements include the cost of the software, storage, and equipment (which is a
one-time cost roughly totaling $16,000). The hardware we currently have available is enough for
students to visit the website and browse through it. As well as, powerful enough for instructors
to offer online lessons.
Key System Requirements:
Software
Storage
Equipment
17
Milestone II
1.0 Data Flow Diagrams
1.1 Context Diagram
18
1.2 Level-0 Diagram
19
1.3 Level-1 Diagram
20
2.0 Entity Relationship Diagram
21
3.0 Data Dictionary
22
23
Milestone III
1.0 Form and Report Designs
1.1 Specifications-deliverables and outcomes
Lesson Request Form Specifications
1.1.1 Narrative Overview
a) Title: Lesson Request Form
b) User Characteristics: Students, Instructors
c) Task Characteristics: Enable students to request a lesson from the Musical
Empowerment Program, by entering their student information and their needs.
d) System Characteristics: Microsoft Windows, Mac OS, Google Chrome, IE, Firefox,
Safari
e) Environmental Characteristics: Standard University or home environment
1.1.2 Sample Design
24
1.1.3 Testing and Usability Assessment
a) Testing Objectives: Ensuring the system is in proper working order and delivers to
specifications.
b) Testing Procedures: Requesting sample reports, transcripting fields in the form,
requesting sample lessons, approving lessons
c) Testing Results:
Requested reports accurately came through
Speed of performance was efficient
Rate of Errors was none
2.0 Interface and Dialogue Designs
2.1 Specifications-deliverables and outcomes
Lesson Content Specifications
2.1.1 Narrative Overview
a) Title: Type of Instrument (i.e. Guitar) Lessons
b) User Characteristics: Mainly students, some Instructor use
c) Task Characteristics: Allows the Student to access said lesson materials, scroll through,
read, and play videos.
d) System Characteristics: Microsoft Windows, Mac OS, Google Chrome, IE, Firefox,
Safari
e) Environmental Characteristics: Standard University or home environment
25
2.1.2 Sample Design
26
27
2.1.3 Testing and Usability Assessment
a) Testing Objectives: Ensuring the system is in proper working order, proper format,
videos play/contain correct material, and delivers to specifications.
b) Testing Procedures: Opening up/viewing lesson material, playing video material,
signing into each specific lesson
c) Testing Results:
Each lesson is complete in material
Videos play and do not buffer
Rate of Errors was none
28
2.2 Guidelines
2.2.1 Structure data entry fields
29
2.2.2 Control data input
All-important fields on the form must be filled out before advancing and submitting the form.
For Example: the screenshot below shows students unable to advance without entering their ID,
name, etc...
Also, when entering invalid data into each field:
2.2.3 Provide feedback
Warning Messages in forms provide feedback:
Also:
30
2.2.4 Provide help and online assistance
All key fields in the form provide hints on what input is required:
For Student ID, “Enter your 8-digit Student ID”; for Name, “Enter First/Last Name”; etc...
31
2.2.5 Design the dialogue sequence diagram
32
3.0 Working System
3.1 Data Input (Forms)
33
34
3.3 Data Outputs (Reports)
Cognito Form List of Entrees
Access Database
35
Reports
36
4.0 Documentations
4.1 User manual, user reference, and user training materials
User Manual
Requesting Lessons
Students- To request a music lesson from Musical Empowerment, on the homepage, navigate the
“Request Lesson” link. Once to this screen, fill out all necessary fields. You will receive a
confirmation email stating the system has accepted your request. The instructor that meets your
needs will receive this information directly and send you a secondary e-mail stating whether your
lesson will be approved.
Accessing Materials
Students- Once you have been granted access to materials you will receive a link to the lesson
that you have requested, which includes the content, lesson videos, pictures, and other
information.
User Reference
All material and content can be directly accessed from the homepage. Please refer to the User
Manual as reference to accessing materials and requesting lessons.
Meeting Staff
To see the staff of the University of Massachusetts Lowell Music Department, please navigate to
the “Staff” link. Here you can see a description of all participating staff.
Location
The interactive map on the home web page shows where the University located.
Contact Information
All contact information, including address, telephone number and social media can be found on
the homepage.
Training Materials
Instructors- All staff instructors will be trained in-person how to navigate the system, upload
lesson materials, and accept lesson requests.
All communication with students will be done outside the system.
37
Students- Musical Empowerment is to follow the same website format as other University web
pages and should be navigated in the same way. The User Reference and User Material will
show you where to access your materials and request lessons. Any further training needed,
please contact the University of Massachusetts Lowell Music Department.
All communication with instructors regarding material and lessons will be done outside the
system.
4.2 System documents—technical report, maintenance manual, and testing data.
Technical Report
Server Requirements:
Random Access Memory should be at least 1,75 GB RAM
Hard Disk Drive should be at least 1x 40 GB of available space for the web shop data and for the
software it should be at least 1x 40 GB of available space.
Client Requirements:
Clients must have access to internet to access the website
Web Page is responsive and compatible with a variety of different browsers and screen sizes
including mobile and tablet devices.
Scalability:
The musical Empowerment webpage is available to thousands of users. It has the same speed as
the University of Massachusetts website. Also, the content is visible to everyone, the navigation
is user friendly and visible, Website Link loads quickly, and it has consistency with current
University of Massachusetts website, same design, font, and style.
Maintenance Manual
Security:
Set up a regular monitoring service so that if the system gets infected or has any site errors they
can be fix as soon as possible. Also, having regular monitoring will help to detect any hacker
activity.
Backup:
Have a regular backup because if the system gets updated regularly the edits will be saved in the
backup system rather than losing the updates due to system errors, malware, or hackers.
Updated Software:
Use WordPress to keep the system updated and more secure regularly. Having all types of
updates will help to keep the system more secure.
38
Updated Content:
Have the content of every lesson material updated, publish relevant information to students and
do it often. It is very important to always check for broken links, the 404 or Not Found error
message, and the speed of the site; As well as fixing these types of problems as soon as possible.
Testing Data
Manual Testing:
This project was divided into three milestones review by instructor Edward Chen at the
University of Massachusetts Lowell. For each milestone, we received feedback such as if there
was any problem with our data. Also, colleague students contributed with us by providing more
feedback and asking questions.
Coverage Testing:
We tested our data and found our actual and expected data set size to create our system.
Completeness Testing:
We measured the website columns to see which ones needed something in there and which ones
did not. We tested the link of the website and any other links within it and checked for errors,
and currently there are no broken links or errors.
Data Type Testing:
We determined the data type for each property or column field (look at data dictionary) and did
changes to the data type based on the instructor Chen’s recommendation.