PROJECT TITLE: ORCHESTRA MANAGEMENT SYSTEM (OMS)
Author: Karen Maughan
Course: HND Computing (IT)
Email (Co-ordinator)
Email (Supervisor)
Proposer: Karen Maughan
Project environment:
The OMS is intended as an aid for the management committee of the Cleveland Philharmonic Orchestra. Committee members involved in the daily management of the orchestra would be expected to use the system as a tool for keeping up to date records of players, programmes and accounts.
Objectives:
The main objective of this project is to produce an orchestra management system (OMS) for the Cleveland Philharmonic Orchestra. The current system has a fragmented approach, with orchestra member details being held in a spreadsheet, with orchestral accounts and programme details stored disparately. The new system aims to provide a more efficient tool for the orchestra manager, treasurer, secretary and librarian to use in the management of the orchestra’s players, music and subscriptions.
Product Aims:
The aim is to produce a central database of orchestral players. It should provide information such as addresses, instrument played, whether the player is available for the next season/concert. A web interface will provide interrogation facilities for the Orchestra Manager, Librarian, Treasurer and Secretary (and any others as deemed necessary by the orchestra’s management committee).
A structured methodology will be adopted, and this will help to produce the project documentation through the stages of systems development, including analysis, design and implementation. Appropriate Computer Aided Software Engineering tools and techniques will be used to convey the proposed model.
Analysis: A full systems investigation will take place to determine what the system requirements are. A proposed model will be formulated, agreed and documented.
Design: This will determine how the requirements of the system (produced at analysis stage) are to be met and achieved. A design specification will be produced, and this will provide the information necessary to build the system.
Implementation: At this stage, it will be decided which system functions will be implemented in the time available. These components will be constructed by coding tables, forms, queries, reports and associated web access pages. Individual parts will be tested, along with the whole system, by following a test plan. Relevant test plans will be produced and results documented.
Maintenance: Documentation for system maintenance, which includes User Guides, strategy for changeover from current system to new one, maintenance (fine tuning/bug fixing/upgrade) and future enhancements.
Academic Aim:
Academic aims are:
· Utilise skills and knowledge gained so far in HND Computing (IT) modules, including: Applications in It, Systems Analysis & Design, Database Development and Web Authoring.
· Research and adopt a Systems Methodology for project development
· Gain further knowledge and skills in the area of web hosting
Resources and Constraints:
The project will conform to University of Teesside standards for coding and documentation. The choice of hardware and software will be restriced to that available in the School of Computing.
Schedule:
It is intended that all stages of the project will be completed within the time scale of 26 weeks/two semesters. An approximates schedule is: Analysis: 6 weeks; Design: 7 weeks; Implementation: 10 weeks. Documentation to be completed over the 26 week period.