Create a sequence diagram that shows the generation of a report regarding the total costs and hire income to date for any bike purchased in 2014. The report should show : - The bicycle's Asset ID - The total of all costs for that bicycle, including it's purchase and service costs - The total of all income attributable to that bicycle Your diagram MUST demonstrate: Consistency with the provided class diagram structure (this includes associations and class names) Completeness of scenario and consistency with the scope Use of existing attributes where appropriate Consideration of logical design principals as discussed in lecture 5 (Appendix C) Correct demonstration of the following sequence diagram concepts o Participants (objects), lifelines, and activations o Participant creation or destruction if required o Appropriate Messages, named as operations for use in task 5 o The use of frames o At least one example of a return message Your diagram MUST NOT Use notation not covered by the CPT230 lecture notes Include additional functionality to that mentioned. You should create a communication diagram for the generation of a report showing the average time \ each bicycle is hired for. The report should show : - The bicycle's Asset ID - The average period that the bicycle is hired for Your diagram MUST demonstrate: Consistency with the provided class diagram structure (this includes associations and class names) Completeness of scenario and consistency with the scope Use of existing attributes where appropriate Consideration of logical design principals as discussed in lecture 5 (Appendix C) Correct demonstration of the following communication diagram concepts o Participants o Participant creation or destruction if required o Appropriate Messages, named as operations for use in task 5 o Ordering and labelling of interactions o Guards or iteration markers if needed Your diagram MUST NOT Use notation not covered by the CPT230 lecture notes Include additional functionality to that mentioned. Create a state diagram that represents a Bicycle object (Appendix B). Your diagram MUST demonstrate: Only notation covered by CPT230 lecture notes Correct use of each of the following state diagram concepts o Appropriate identification and use of entry & exit notation (no more than one of each) o Appropriate identification and naming of states o Identification of all relevant transitions, each with at least an event or guard specified o At least one example of a relevant internal action. o An example of each aspect of a transition label (you may demonstrate each aspect individually or combined on one transition). Notation style MUST be correct. Appropriate naming of actions and events – these should be named as operations for use in task 5, where you will be required to place these actions and events in the class diagram. Create an activity diagram describes the whole hire transaction process – it should include both the hire and return of the bike. (Appendix B) Your diagram MUST demonstrate: Completeness of scenario and consistency with scope Only notation covered by CPT230 lecture notes Demonstrates good practice for activity diagrams Correct use of each of the following activity diagram concepts o Actions, documented at a relevant level of detail o Decisions and merges o Forks with joins o Swimlanes by role o Logical flow paths - There should be only one flow into any action o Object nodes indicating state changes o Appropriate identification and use of entry & exit notation (no more than one of each) o Appropriate UML notation 5. Amend the class diagram Update the provided class diagram so that it now includes the operations used by the diagrams you have just created. Your diagram MUST : Show the operations located in the appropriate class o Operations do not need a full signature, just the name Include operations used in both interaction diagrams as well as the state diagram Include any accessors/modifiers used in the prior diagrams, in order to illustrate your comprehension of how these are used to achieve a task A reminder that your response MUST NOT Use notation or concepts not covered by the CPT230 lecture notes Include information not required or beyond the scenario scope Add/ remove/ rename the provided classes or relationships. No dependencies should be used. Show information not relevant to the problem domain – e.g. arrays, foreign keys, storage, etc.