Relationship between Prospectus and department Essay

In the final draft (Diagram 3) of the college prospectus I have added another class (department), since in reality a college will be sub divided in different departments and then these departments will have different courses.  Relationship between Prospectus and department:  Class Name: Department  Responsibility: â€Å"Department† provides information about the departments in the college and what courses are done in each of them. Collaborations: Every â€Å"Department† will be related to & have many courses.  Relationships: Prospectus to Departments, will be a â€Å"One to Many† i.e. one Prospectus can have many Departments.  Maintenance Plan for Final Version  For a good and successful system to be of any use in the long run, it requires a product that is easily maintained so that its future is ensured. Systems once delivered and implemented, always need someone to ensure that the system meets the user requirements & thus kept updated regularly. A survey done by Lieutz and Swanson from the U.S. says that up to 48% of the total development time can be spent on maintenance. For the online prospectus the maintenance may include some of the following points: Keeping the system up-to-date and posting any changes to the courses, constant backing up of the system in case of viruses or damage to system, links and websites updated and changes to courses posted on website. Maintenance is not always easy and encounters many problems during its cycle. However it has additional problems, as often the people carrying out the maintenance activities are not always the same as those producing the original software.  Poor documentation can present major problems for maintenance teams for example; when systems underwent changes to avoid the so-called â€Å"Millennium bug† problem. Systems that had been used for many years required modifications but this took time due to the lack of documentation. (Above Source: Hellingsworth, Hall & Anderson, 2001) It may be important to have a system in place for documenting requests for any changes to the system and responses that would come from a â€Å"change request form† to the maintenance teams. These may include:  Enhancements; including description of new requirements in detail, regular updates to college & course details. Maintenance teams should be striving for a user interface. Problem & Error Reports; including a full description of problems with website from email discrepancies to broken links of the website. A record of these would be carefully documented and reviewed regularly at maintenance team meetings. User Feedback; includes a system for the maintenance team to give feedback to user on any problems or errors with links & for any enhancements made. Timescale should be included of when the errors will be fixed. Structured Maintenance Plan For the maintenance plan to be effective I will be using the following structured plan. Having a good & complete software engineering documentation for the project helps a great deal with this plan. Any amendments or changes to the system will be documented professionally and kept safe in order to have a successful future system. An external contracting maintenance team will be in charge of updating the system & making sure it runs smoothly. Many companies can be found that specialised in just maintenance of other company’s software, databases & even their websites. Bibliography & References Using The Harvard Referencing System as a guide, these are my points of reference and the textbooks that I used to complete the assignment.  B.HELLINGSWORTH, P.HALL & H.ANDERSON (2001), â€Å"Higher National Computing†, Newnes:  http://www.askmen.com