1 University of West London School of Computing and Engineering Object-Oriented Software Development Title Object oriented Modelling Module Object-Oriented Software Development (Level 5) Module Code CP50076E Module Leader: Nasser Matoorian Set by: Nasser Matoorian Moderated by: Fehmida Mohamedali Assignment Assignment 1 Hand in arrangements This assignment must be submitted to the Assessments area of the module on Blackboard. Structure of assignment This assignment has one element. Each element has a specific weighting, and its own criteria. The assessments are described below. The learning outcomes of the module are assessed by a successful completion of all the elements. Element Type Weighting Due Date 1 Object oriented Modelling 100 marks Friday 11 Nov 2016 Extensions will only be granted in exceptional circumstances. Extensions will be for 10 days or less. Documentary evidence will be required. Extensions must be agreed before the deadline. Submissions up to one week late with no extension will be marked with a maximum mark of 40%.2 Learning outcomes 1 Write programs with the key object oriented concepts 2 Design and write software with design patterns 3 Design and develop a concurrent applications Element 1 Title Object Oriented Modelling Task details A case study accompanies this assignment. It describes the requirement for a system within a business context. You will need to make assumptions in the course of constructing your models. Ensure you submit a list of these assumptions with your assessment elements as appropriate. The case study will be used for all element(s) of the assignment. If you are at all unsure about the case study description you should ask questions within the seminars/workshops. The diagrams must be completed using a suitable CASE tool, such as StarUML. You are required to produce the following:  Use Case Model; actors and relationships.  Domain level class diagram showing attributes and their types, named associations, composition, and inheritance relationships as appropriate.  One use case scenario and sequence diagram.  An implementation for the UML models, related to the use case, using Java programming language. You need to submit:  One PDF file containing your models and full program listing Marking Guide Criteria Issues Mark Marking breakdown where appropriate Modelling Have you provided appropriate depth, coverage and precision in your models? Have you deployed appropriate modelling notations and techniques? Have you provided name, goal, precondition, and trigger for the 703 use cases? Have you produced a class diagram as a domain model, including relationship cardinality, aggregation and inheritance? Have you produced a detailed sequence diagram related to one use case scenario? Programing Have you produced an implementation based on your UML models? Have you correctly implemented association cardinality, composition and inheritance? Have you produced full program listing with explanation on how it relates to your class diagram and your sequence diagram? Note: Client application is not required. 304 Case Study Saxon Heritage Saxon Heritage is a charity that maintains buildings, gardens and monuments that are of national interest on behalf of the Government. Examples of sites of national importance are: Stonehenge and Tintagel Castle. The locations of sites are distributed across England. However from a marketing perspective, England is divided into a number of regions so the sites are actually located in a region. There are 6 regions: These are: South East; London; South-West; Midlands; North East and North West. Each site has its own charging structure for members, nonmembers; adult, child and family rates. These rates are based on popularity. Each heritage site is flagged as a Gold, Silver or Bronze site, which denotes the popularity of the site. Sites, which receive less than 10000 visitors per annum, are tagged as Bronze; Sites, which receive between 10000 and 30000 visitors, are tagged as Silver; Sites, which receive more than 30000 visitors, are tagged as Gold Sites. Each year on Dec 30th the tagging is required to be automatically set based on the preceding year's figures. During the tagging process, prioritisation for inclusion on any marketing campaigns is also decided. Periodically, each region will run its own advertising campaigns, which will focus on a number of sites. Each campaign has a specific focus. For example, "Castles in Wales" was the last focussed marketing campaign. The Marketing Manager is responsible for ensuring that no site features in two consecutive marketing campaigns. If a site features in a campaign, then the visitor targets for that site are updated with an additional percentage as there is historical evidence that marketed sites always do well. Once a campaign has been run, the visits to the featured site are monitored and senior management requires reports on visits. Senior management also require reports, which enable them to compare targets and performance of regions. Senior Management will set targets to regional directors on the number of visitors to each site and for the region as whole. The region target is based on the sum of the all the site targets and an additional 10%. Individual sites, which fail to meet their visitor targets by more than 20%, are priority sites for the first marketing campaign for the region in the next year. Saxon Heritage manages a membership scheme where membership of the charity is encouraged. Membership provides a number of benefits such as free entry to the sites; a monthly magazine; various promotions and half price entry to the equivalent Celtic Heritage Charity. Benefits are constantly updated to reflect the competitive nature of the charity industry. Members are encouraged to submit visitor reports. If they submit 5 reports they are entitled to free entry on their next visit. Reports on the visits to sites made by members are also monitored and updated for the website. There is a membership fee and a membership only becomes active if the fee has been paid. If the membership has been paid by direct debit then a letter is sent out to members letting them know that a payment has been collected. The administrator is responsible for this. If payment was received by cheque, then a reminder is sent to the member to renew their membership four weeks before the membership is due to expire. Members who renew their membership after the renewal date are charged an extra 5 pounds for administration. Sometimes a member may elect to suspend their membership for some reason (e.g. out of the country for period of time). They must state how long the suspension is for. The renewal date is consequently pushed back. If a member cancels a direct debit then the membership is also suspended. There is a requirement to design a new information system, which will handle reporting of site visits for regions; performance setting and membership. In addition there is a great desire to push as much responsibility to the customer wherever possible. So for example, it is preferable that members administer their own details.