Reference no: EM132306482

Part A

Case Study - SolarPower

Consider a project involving development of an Online SolarPower System for Bob Sparks.

System Information

Bob Sparks is a professional electrical engineer who works part time for a local coal-fired electricity power station. With the recent advent of government rebates, it has now become affordable for ordinary people to install solar power cells on the roof of their home to generate electricity and sell unused power back to the local electricity provider. Bob recently decided that he has the time and expertise to start a small business supplying and installing the solar panels and has registered the business name as SolarPower.

To date you have helped Bob through the planning and analysis phases of a computerised information system for his new business. Now Bob has asked you to help him with the design and implementation phases.

You have agreed with Bob that the system should be largely ‘form-driven'. For example, a potential customer may, through SolarPower's website, complete an online request for a free consultation and quote. Or they may apply by phone or in person, in which case one of the staff will complete the form.

One of Bob's staff members will arrange a mutually convenient date and time for Bob to call on the customer. Bob will discuss the customer's needs with them and supply the customer with a written quote for the desired system.

SolarPower currently have four systems on offer, based on the average amount of power they generate: 1.5 kilo-watts (kW), 2.3kW, 3.4kW and 4kW.

If the customer is willing to go ahead with a type of system, they are required to sign a ‘Solar Power Supply and Installation Agreement' form. When installation is complete SolarPower leave an invoice/statement with the customer, which must be paid in full within 7 days. Part payments are not allowed. Payment may be by cash, eftpos or credit card and customers are given a receipt.

Bob requires the system to provide him with regular reports showing:
• Appointment details for consultations
• Quotes accepted
• Job schedule (when installation at premises is to be carried out)
• Outstanding accounts (installation completed but not yet paid for) You may be able to suggest other more appropriate reports to Bob.

The Tasks
Consider the same case scenario for an Online SolarPower System for a web-based system project in Assignment 1, as a system analyst in a project team of four members.

With the above project in hand, you are to complete Tasks 1, 2, 3, 4 and 5 below.
Task 1 needs you to decide your ways to gather the critical information system requirements information from the related end-users and/or stakeholders, in order to model some important modelling diagrams that usefully demonstrate what the new system is technically about.

For Tasks 2, 3, 4 and 5, you need to fully explain each modelling diagram and clearly provide any useful assumptions supporting why a diagram is drawn the way you present it, e.g. you clear the doubts of readers by telling:
• Reasons for any inclusion of <<includes>> relationship in UCD,
• Selective use of new unknown useful attributes in CD,
• Selective use synchronisation bars for looping, join and/or split concepts to handle tasks in the system in AD, and
• Selective use of LOOP, OPT and ALT frame in SSD.

Task 1. Requirements Elicitations

There are six information gathering techniques covered in this unit. Select two most useful relevant information gathering techniques out of the six for the above scenario that would help you effectively investigate the new system requirements. You have to:
• Describe each of the two information gathering techniques in detail. Include tasks that would be performed using the technique for the Online SolarPower System project.
• Explain the advantages and disadvantages of each technique in the context of the Online SolarPower System project. The advantages/disadvantages are relative to all 5 other techniques (not just the selected techniques).

What to include in your report for this task?
1. Description of two techniques
2. Explanation of advantages/disadvantages of selected technique 1
3. Explanation of advantages/disadvantages of selected technique 2

Task 2. Use Case Diagram (UCD)
Draw a use case diagram for the entire system within the project.
What to include in your report for this task?
1. A screenshot or copy-and-paste of the diagram. You MUST also submit the original MS Visio file containing the diagram.
2. Succinct explanations and supporting assumptions for your UCD.

Task 3. Domain Class Diagram (DCD)
Draw a domain class diagram for the entire system. You must closely follow instructions below:
• Each class must have a primary key, e.g. customerID, productID, etc.
• Each class must have at least two or more other related attributes.
• On each association line, there must be a meaningful word reflecting the relationship in the association.
• Show inheritance for a superclass with TWO (2) different subclasses to handle the two credit card payment types (Visa card and Master card) as in the case scenario above.

• Indicate AT LEAST three common attributes as identified in the superclass. Indicate appropriate different attributes as identified for the subclasses.

What to include in your report for this task?
1. A screenshot or copy-and-paste of the diagram. You MUST also submit the original MS Visio file containing the diagram.
2. Succinct explanations of your CD (e.g. what the classes represent, why you have chosen certain relationships), and support assumptions for what you have made about the system (e.g. you add shipping address in addition to postal address for a customer user).

Task 4. Activity Diagram (AD)
Draw an activity diagram for a specific scenario that shows an online user entering his details to make an appointment for a consultation with Bob Sparks through the Online SolarPower System, and obtaining an appointment confirmation via email.
What to include in your report for this task?
1. A screenshot or copy-and-paste of the diagram. You MUST also submit the original MS Visio file containing the diagram.
2. Succinct explanations and supporting assumptions for your AD if any.

Task 5. System Sequence Diagram (SSD)
For the system in Task 4, draw a system sequence diagram based on a part of the scenario, showing "Bob Sparks hits a print button at the end of month. Subsequently, the system prints a receipt for all customers with outstanding accounts, i.e. installations completed but not paid."
Note: You are to keep your SSD as simple as in the task description above.

What to include in your report for this task?
1. A screenshot or copy-and-paste of the diagram. You MUST also submit the original MS Visio file containing the diagram.
2. Succinct explanations and supporting assumptions for your AD if any.

Attachment:- system analysis assignment.rar