Write some Software

The intention is that you should demonstrate the use of a range of UML diagrams, but that you do not need to exhaustively document the entire operation. Some aspects of your design will encompass an overview of the full range of activities, but you will also be homing in on the detailed specifics in certain areas. The station should be capable of both manned and unmanned operation. The service station should incorporate fuel sales and retail activities Try to incorporate as many of the ancillary systems such as CCTV, Tannoy, security, safety as you can. Identify which of them are isolated from software control and do not need to be incorporated into the design (you may want to think about ways they can be). Note that although detailed design for all of them will not be required. Expected Diagrams Incorporate as many UML: diagrams as you think appropriate. Would expect at least the following. • Use Case Diagram • Class Diagrams • Deployment Diagram • State Diagram • Sequence Diagram • Activity Diagram Suggested Approach Identify the system use cases. Use the resulting use cases and associated descriptions to fully describe the operation of the system. Identify candidate objects within the system and from these the required classes. You can then produce a corresponding object diagram A structured context diagram or deployment diagram will show the overall interconnection of the system, and sequence diagrams will help describe the timing aspects. Use other UML diagrams as appropriate. Deliverables Supply a brief report describing how the system functions, documenting the coverage of your analysis and in particular the limitations of the information you have been able to access. Include any UML Simon Pomeroy 2 20/03/2017 diagrams you have used. Where supplementary information – e.g. use case descriptions – have been included in your design make sure these have also been included in your report. There is no page limit, but aim for a maximum of five pages of explanation plus your UML diagrams.