Software Projects with Agile Techniques: UML Modelling Assignment

On completion of this assessment you will have had the outcomes:opportunity to:

A1 - Derive a software specification and design from a brief user requirement using various UML modelling techniques such as activity diagrams class diagrams, data flow diagrams, state machines and interaction diagrams.Transferable/Key Skills and other Attributes.  

B1 - design and implement a software application, using appropriate class libraries, etc., documenting to a professional standard.

The aim of this assignment is to perform requirements analysis modelling for a software solution using the Unified Modelling Language (UML). You are presented with a business scenario where a software solution is sought to help providing services to users and allowing future expansion. You are expected to use materials provided to you in the lecture series in the course plus information obtained from external sources for doing this assignment.

A combined cycle gas turbine power station requires a webbased system to manage the storage and installation of spare parts and the acquisition of new parts from the Central Storage Warehouse (the CSW). The power station maintains an inventory of all the parts it owns comprising: part name, description and specification. There are many copies of some parts – each part has a unique ID, known as an asset tag number. The asset tag number is used when there damage to particular parts. The power station also keeps a catalogue of all the possible spare parts types used.

Only registered maintenance engineers and team leaders are allowed to install and repair parts on the plant. Maintenance engineers and team leaders can use the parts catalogue to search for part types and can also search the parts inventory. Maintenance engineers work in teams, currently: electrical, mechanical and environmental. Each team has its own team lead. However, the system needs to be flexible enough to allow creation of new teams in the future.  

Maintenance engineers are allowed to take spare parts from the CSW, up to a value of £50,000. Higher value items need authorisation from a team leader. Spare parts are issued from the CSW by a Store Manager.  

Occasionally a maintenance engineer needs to sign parts back into the CSW. Such “returns” maybe because time has run out on the shift to install the part or because the part is no longer required.  

Whenever a new part is installed in the power station an old part is removed. The old part must either be returned to the CSW for refurbishment or disposed of as scrap.  

After store managers receive requisitions from team leaders, they produce purchase orders to purchase spare parts from suppliers. The purchase orders contain part names and descriptions and are sent suppliers. Suppliers then send the spare parts along with an invoice to the CSW. The store managers then reconcile the invoices against the purchase orders to authorise payments for suppliers.

The store managers also handle spare parts returned to suppliers for refurbishment. When a spare part is returned to the CSW, the store managers produce a purchase order. Again, suppliers send refurbished goods (spare parts) to the CSW,where the store managers then reconcile invoices and authorise payments.

After the store managers authorise payments for suppliers, the payment transactions are actually implemented by the power station financial management system (FMS). A message passing interface is used to payment transactions. Each payment transaction must include: supplier name, address, phone number, email address, invoice number, order number, authorising store manager name and payment amount (in GBP).

Produce a Use Case Model of the system. Your use case model should describe the users’ view of interaction scenarios with the system and should include the following:

? Read the scenario in order to identify and name the actors of the system.

? For each actor you have found in the system, identify and name the use cases for the actor.

? Use straight lines (with arrowheads) to show actor and use case relationships.

? Indicate primary and secondary actors.

? Use Case Title  

? Primary Actor

? Goal

? Scope

? Preconditions

? Postconditions

? Main Success Scenario

? Extensions

? Use the class diagram illustrate various relationships between classes, such as inheritance, association and aggregation.

? Show example method and attribute names in classes, (think about encapsulation, make sure methods go with the attributes encapsulated by the class)  

? Try to include method call and return parameters, where appropriate.

Your report should include the following:

-Use case diagram.

-Two textual use cases.

-Simple system class diagram.

-References – the sources used in your report (and cite them in the body of your report).