Deliverable C - Requirements Analysis and Specification Document
Purpose
The purpose of this document is to define the technical requirements and specify the user interactions for OrangeMusic.com
1. Project Description
Orange Music School (OMS) is a not-for profit organization that provides musical instruction and training to local, national and international students. There are a number of different programs that are designed for musicians that want to be professional, serve in local churches or communities, or just learn an instrument for their own leisure. The mission of Orange Music School is to give any person that would like to be a musician, in any form, the opportunity to do so.
1.1 Objectives
- OMS's objective is to provide the opportunity for anyone that wants musical training the ability to achieve their goal no matter their varying degree of knowledge/skill from beginner to genius. The website would give the opportunity to both students and professors to interact and help each other achieve a greater learning experience.
1.1.1 Goals and Message
- Orange Music School is the ideal place for people in the north side of Chicago to attend and gain knowledge in any area of music
- Additional Goals
- Increase the exposure by providing online classes and material.
- Make it user friendly for both professors and students, so they can access and manage their courses.
- Promote events that will help the school financially.
1.1.2 Content
The site will contain the following elements:
- Home page
- About OMS
- Contact information
- Admissions
- Courses
- Ensembles
- Faculty
- Students
- Events Calendar
- Workshops
- Resources
- Online Store
- Online reservations
- Online reservations
- Ad space sold to related/partner organizations
- Guestbook / customer reviews
- Fees
1.1.3 Structure and Interpretation
- Students will be able to view pricing and schedules on the website.
- Students/Faculty/Guests will be able to view the special events calendar.
- Tickets for events can be reserved and/or bought online.
- Students can view some classes online.
- Customers can register in order to keep informed of upcoming events, promotions etc.
- Guests can register to receive promotions and special events info.
- Registered students can view their account/study/events information.
- Faculty can input their hours and check class schedules and upcoming events.
- Guests can access online store for different products.
1.1.4 Sensorial design
- OMS.com will follow standard web conventions in navigation and layout
- The colors will be simple and not disturbing, and images will be used to help interpret the real meaning of the page
1.1.5 Market testing
- Our main competitors are some prestigious and history rich Music Schools that offer many different programs for all skills and ages of students that also maintain a web presence. They are as follows:
- American Music Institute
- Merit School of Music
- Midwest Conservatory of Music
- Sherwood Conservatory of Music
- Wheaton College Community School of the Arts
1.1.6 Potential Challenges
- Established history rich Competition.
- Highly niche target demographic.
- Selling a new service.
1.1.7 Strengths
- Flexibility in providing the service.
- Offers a program for any level or age.
- Social-based family activity among and between families.
- Reaches well beyond local boundaries.
1.1.8 Opportunities
- Gives community an alternative to education.
- Gives serious musicians an exposure to different faculty and players around the world.
- Brings communities together for special events.
- Optimizes a musician's ability to exceed their learning potential.
1.1.9 Target demographic
- Primary target is children and teens.
- Secondary target is young adults involved in church or community musically.
- Musicians that want to become professionals.
- Beginners that would like to play for leisure.
- World renowned faculty.
1.2 Critical Success Factors
- Conduct Market Research and Surveys to determine usability and website friendliness.
- Provide funding for building/hosting/maintaining the site.
- Implement and Utilize appropriate payment and billing tools.
- Set very high QA guidelines and expectations, especially for video learning/tutoring.
- Choose an appropriate host for this site, which will provide 24/7 technical support and site metrics.
- Conduct Training on the use of the Site for current employees.
- Create and provide online Tutorial/Training for users (Students and Teachers) of the system.
- Provide a 24/7 support system for questions and concerns on features of the site.
2. Impact Assessment
The impact of this project should be minimal. However, it will still require the need for the purchase of some high end servers to house a database for online lessons and tutorials. It will tie into authentication systems for users' registration and security systems for secure authentication to the network, it will also utilize the billing and payment systems for accounting purposes.
- Large enough data storage space will be needed for the lessons and online tutorials.
- Enhanced Servers will be utilized to display the output of the lessons and tutorials.
- Optimum network speeds on the backbone will be necessary to increase performance for users.
- Connections to the different systems will have to be made at optimum speeds for real-time applications.
- A large database will be necessary for the housing of the lessons and online tutorials.
3. Implementation Strategy
3.1 Planning - September 10th- 24th
- Identify team roles.
- Select project.
- Develop business case statement and document strategy.
3.2 Analysis September 24th - October 1st
- Establish requirements and specifications including more detailed user demographics.
- Sitemap.
- Flow diagrams/use cases.
- Wireframes.
- Initial page comps.
- Create test plans.
- Conduct initial round of user testing.
3.3 Design - October 1st - October 15th
The site will contain the following elements:
- Refine wireframes, design comps and interaction specifications based on user feedback and integrate into design specification.
- User testing round 2.
- Refine wires, comps and design spec.
- Create site prototype.
- User testing round 3.
- Revise design spec and site if needed based on testing results.
3.4 Implementation October 15th - November 19th
The site will contain the following elements:
- Integration of select functionality.
- System testing.
- Beta testing.
- Performance testing.
- Revise site design if needed based on testing results.
4. Functional Requirements
4.1 Functional Requirements
- TR 4.1.1 Users will be able to browse course descriptions.
- TR 4.1.2 Users will be able to search courses by date/time, name, instructor, and category.
- TR 4.1.3 Users will be able to register and pay for courses.
- TR 4.1.4 Users will be able to browse faculty profile information.
- TR 4.1.5 Users will be able to browse a calendar of concerts and events.
- TR 4.1.6 Users will be able to register with the site in order to be informed of upcoming events.
- TR 4.1.7 Users will be able to search the website through a standard search box powered by Google.
- TR 4.1.8 Users will be able to purchase course material, event tickets, and gift cards.
- TR 4.1.9 Students will be able to create accounts to manage all transactions.
- TR 4.1.10 Students will be able to sign on to their accounts with an email and password.
- TR 4.1.11 Students will be able to access their current schedule and course history.
- TR 4.1.12 Students will be able to update their profiles and contact information.
- TR 4.1.13 Students will be able to view video courses online.
- TR 4.1.14 Faculty will be able to manage the calendar of events.
- TR 4.1.15 Faculty will be able to manage their list of students.
- TR 4.1.16 Users will be able to receive reminders to their mobile devices of upcoming classes.
- TR 4.1.17 Users can browse the site's navigation to all the sites elements.
- TR 4.1.18 All site sections will contain relevant imagery.
5. Information Architecture
5.1 High-Level Site Map
5.2 High-Level Process Flows
5.2.1 Use Case
5.2.2 Register for Course (TR 4.1.3)
5.2.3 Create Account (TR 4.1.9)
5.2.4 Student Sign On (TR 4.1.10)
5.2.5 Update Profile (TR 4.1.12)
5.2.6 Manage Events (TR 4.1.14)
6. Interface Requirements/Specifications
6.1 User Interface
- TR 6.1.1 The site will be optimized for 1024x768 screen resolution.
- TR 6.2.2 The site will primarily be created using XHTML 1.0 for content.
- TR 6.1.3 The presentation layer will be controlled by CSS.
6.1.5 High-Level Wireframe: Home/Main
- ID 1: Animated Flash movie with music related graphics and text.
- ID 2: Display visitor's name after they sign on for personalized homepage.
- ID 3: Main navigation buttons. The second tier navigation buttons will appear when the mouse hovers over the main link.
- ID 4: Welcome messages or music related articles.
- ID 5: Ad space sold to related/partner organizations or more music articles.
- ID 6: Upcoming new events or Calendar or Ads Spaces.
6.1.6 High-Level Wireframe: Section Layout
- ID 1: Some text about course description or event details.
- ID 2: Visitor's current course schedule.
- ID 3: Visitor's Course History.
6.1.7 High-Level Wireframe: Mobile Devices
- ID 1: Some text about course description or event details.
- ID 2: Visitor's current course schedule.
- ID 3: Visitor's Course History.
6.2 Hardware Interfaces
- TR 6.2.1 Use Microsoft IIS 6.0 server.
- TR 6.2.2 .Net Framework 2.0 will be utilized.
- TR 6.2.3 Load Balancing IP Router will be used.
6.3 Software Interfaces
- TR 6.3.1 Connect to MS Access Database.
- TR 6.3.2 Website created by Visual Studio .Net.
- TR 6.3.3 Coding done in ASP.Net.
6.4 Communications Interfaces
- TR 6.4.1 Email service provided by Microsoft exchange server.
- TR 6.4.2 Order processing will be done via HTTPS.
- TR 6.4.3 Non-order processing pages will be through HTTP.
- TR 6.4.4 File transfers to upload or download content will be done via FTP.
7. Information and Data Requirements
7.1 Data Requirements
- TR 7.1.1 Tables for Orangemusic.com.
- TR 7.1.1.1 Customer_TBL (ID, Name ,Address, E-mail, Phone Number)
- TR 7.1.1.2 Faculty_TBL (ID, Name, Subject, Classroom#, )
- TR 7.1.1.3 Schedule_TBL (Registration ID, Customer ID, Faculty ID, Course ID, Register date)
- TR 7.1.1.4 Product_TBL (ID, Product Name Description, Price, Quantity)
- TR 7.1.1.5 Event_TBL (ID, name, type ,date)
- TR 7.1.1.6 Course_TBL(ID, Course name, category, Building, time, instructor)
- TR 7.1.2 Catch incomplete data exceptions and note in log files
8. Non-Functional and Support Requirements
8.1 Operational Requirements
8.1.1 Availability
- TR 8.1.1.1 System will be available 24 x 7, 365 days.
- TR 8.1.1.2 Contact form is an option for customers to contact the site after service hour.
- TR 8.1.1.3 Website content will be available during maintenance and upgrade period.
8.1.2 Capacity Requirements
- TR 8.1.2.1 Approximately 0-150 concurrent users will use the system from 11:00pm-6:00am.
- TR 8.1.2.2 Approximately 200-500 concurrent users will use the system from 7:00am-3:30pm.
- TR 8.1.2.2 Approximately 1,500-2,000 users will use the system from 3:30pm-11:00PM.
8.1.3 Maintenance and Production Support
- TR 8.1.3.1 Scheduled maintenance and upgrades to take place between 1-4AM every Sunday.
- TR 8.1.3.2 Ticket will be issued after 1 hour of outage.
8.2 Security Requirements
- TR 8.2.1 All input is analyzed for valid data including alpha or numeric formats, number of characters or data ranges.
- TR 8.2.2 Users are authenticated before access personal data modification.
- TR 8.2.3 Private data, such as credit card info, are not written to system, application or security logs.
- TR 8.2.4 Transactions will be logged in case of problems.
- TR 8.2.5 Provide SSL transactions for online purchases.
8.3 Approvals of Technical Requirements
- Stelu Aioanei, Project Lead: 10/12/08
- Lucas Gatling, Analyst: 10/12/08
- JJ Sandvig, Analyst: 10/12/08
- Nicole Adachi, Media/Graphic Designer: 10/12/08
- Roland Landrey, Programmer/DBA: 10/12/08
- Tom O'Malley, Programmer/DBA: 10/12/08
Team Contributions
Stelu Aioanei
- Document Creation and First Draft
Lucas Gatling
- Added Data Requirements, Non-functional and Support Requirements
JJ Sandvig
- Site Map, Use Cases, and Process Flows, Reworked Functional Requirements
Nicole Adachi
- Added Main Page Design, Section Page Design, Mobile Device Design, Hardware, Software and Communication Interfaces
Tom O'Malley
- Developed and Posted Web Deliverable Page
Roland Landry
- Added Market Testing, Critical Success Factors, Impact Assessment, modified Strengths and Opportunities, Proofread Document
