Reference no: EM132304541

Case Study: Australian Electric Supply

Background:

Australian Electric Supply (OZES) is a young business that supplies and distributes electrical equipment throughout Australia. In addition to selling brand new equipment, OZES has casual employees known as associate brokers that buy and sell second hand electrical equipment. They do this trading through online retail and auction portals such as eBay and Gumtree, and part of the brokers job is to choose the best portal for an item, the listing price and reserve in negotiation with the customer and the length of time the item would be listed for. They list the items for sale under OZES but they earn income by taking 20%-40% of the sales profit as a commission depending on the sales price. Before an item is put up for sale the item is delivered to OZES by the broker for quality control and then OZES will post to the purchaser once sold.

Currently OZES has few brokers who each store their own record of sales in their own way. Some brokers use spreadsheets, some a database and others keep paper records. Each broker considers different data to be worth saving. The brokers have seen this data as an important asset which belongs to them and gives them a competitive advantage. OZES records the details of brokers including their bank account details so that the proceeds can be deposited to the accounts. This account information can change from time to time.

OZES finds value in this type of business and are planning to hire new full-time brokers on a base salary plus 2.5% of the sales profit of sold items. However, OZES has become concerned that it is not gaining a benefit from the data generated from each sale and are beginning to recognize that the ability to aggregate and analyse all the item data would add value given its rapid growth. The existing associate brokers are concerned about this idea as they see how they use their data as driving the commission they earn.

OZES gets its business for second hand equipment in one of several ways: Customers respond to advertisements placed by brokers in specialist magazines and websites (that includes the associated broker's ID) or customers contact OZES because of recommendations from past customers. OZES wants this information stored as part of the customer detail. When customers initially contact OZES, they are asked to complete a questionnaire detailing their name, address, email and phone contact details. They also need to state the broker's ID or the referrer's name.

Items can be purchased in joint names.

Once the items have been deposited at OZES, they are checked, logged and placed in OZES's secure storage. The storage area is looked after by two staff and once an item is sold and paid for they pack and send the item. It is very important that the items are tracked accurately once they have been received and that the customer details are clearly associated with the sold item. Currently, associate brokers come out to the counter to drop off items or negotiate about their commission.

This means that a broker is interrupted many times a day to go to the counter, although multiple items from one or multiple original owners may be included in one listing. The full details of original owners of equipment including their name, address, email and phone contact number are kept by the brokers. OZES is also interested in accessing and recoding these details against each item received.

Once an item is sold an email report is sent to the broker associated with the item including details of the sale price and the commission. Once the item is paid for another email is sent to the broker to inform them. The buyer pays the purchase price for the item into a trust account run by OZES. Three working days after the item was paid for by the buyer, proceeds of the sale are paid to the broker. The trust account must be able to be balanced at any time. OZES wants to retain for each sale, the broker, item number, original owner and purchaser details, and the sale amount.

In your role as a Business Analyst you have been approached by the owner of OZES for guidance on evaluating and selecting a suitable information system solution for their business.

Business Processes:

OZES wants to receive a standard sales report on volume of sales and commissions earnt at the end of every month and be able to run this report for custom dates and for individual customers and brokers. They also want to include a provision for brokers to run monthly sales reports.

A JAD session with key stakeholders revealed the following information to take OZES to a bigger level. The business processes described below are the system requirements for this information system solution:

• A sale item system which will gather all the data from the sales items, this data would then be used by all brokers to assist in negotiations with sellers. OZES wants brokers to gauge if data elements such as a type of item description or included postage would attract higher selling prices.

• A customer relationship management system which would allow OZES to offer selling offers to customers such as lower commission. OZES would also like to be able to track high value customers.

• The warehouse staff will now receive items for sale, with the brokers ringing the customer later to discuss the sale requirements. For returning original owners, OZES would like them to be able to complete a form which could be attached to the items with the receiving person just quickly checking. The idea is that this will decrease the time taken to drop off items.

• Each of the several types of items will require different attributes to be listed, you may look at online auction sites to gain those attributes.

End of Case Study

Assignment Requirements and Deliverables

You are required to write a report for the OZES management team, which must include the following information, and is organized in a professional and meaningful structure. Please note standard report structure including an executive summary must be adhered to.

1. Consultation
The OZES management team has heard of agile and iterative systems development methodologies but is unsure of their effectiveness for their project as there is little knowledge about these in the organisation. Therefore, they want you to compare at least four (4) various methodologies of agile and iterative developments that could be adopted for OZES needs. State under what circumstances each one would be used and then make a recommendation for this project. To do well in this report you must use the details from the case study in your report as examples, rather than giving general information.

This part could be started with a general introduction to the agile and iterative methodologies relevant to the case study. For each chosen methodology you may use the following structure, which are then followed by a recommendations section:
• Methodology X
o Discussions
o Advantages
o Disadvantages
Your target audience is executive business people, who have extensive business experience but limited computing knowledge.
This part should be no less than seven hundred and fifty (750) words and it would be best to be no longer than one thousand (1000) words long. Appropriate referencing is required.
The textbook Satzinger et al. is a valid resource, however it is expected that at least five (5) other resources will also be used and cited.

2. Analysis of the case
Review the OZES case study and analyse the case by professionally demonstrating the following modelling tables and diagrams for the information system solution to support the business processes as per the case study.
• An Event Table
o For the event table, use at least the following headings: Event / Event Type / Trigger / Source / Activity or Use Case / System Response or Output / Destination
• A Use Case Diagram
o Should be compatible with the event table solution.
o Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 3-12 and 3-15.
• Use Case Description (intermediate)
o For the ' Sell Second-hand Item ' use case only, as documented in the event table solution and the use case diagram solution.

o Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components as shown in Figure 5-2.
• A Domain Model Class Diagram
o Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to show:
• The class name and attributes list for each class and sub class as required
• All required associations
• All attributes as specifically mentioned in the case study must be reflected
• Other attributes as needed to support the described functionality.
o It is not necessary to show methods, however you may include them if you wish. Solutions are expected to align with the components as shown in Figure 4-23 of the Satzinger et al. textbook.
• Design Class Diagrams
o For the ‘Associate Broker' and ‘Order' classes ONLY. These classes should be part of the Domain model class diagram solution.
o Each of these design class diagrams are expected to have a complete list of attributes and a comprehensive list of methods, which supports the specified functionality as described in the case study.
o Solutions must follow the methodology as outlined within the Satzinger et al. textbook. Solutions are expected to align with the components for the ‘Design class diagram for Student' as shown on the right hand of Figure 12- 4.

Do NOT extend the scope for any of the solutions beyond that specifically described in the case study above. You are however permitted to make reasonable assumptions where necessary, but these should be noted.

It is recommended that you review all documentation for this case study before finalising any single solution. Ensure that the required consistency has been included within and between all solutions. You may use a tool such as Microsoft Visio or www.draw.io to draw the models or neatly hand draw and scan into a pdf document. However, you should submit only one document.

3. Memo on pertinent issues

Currently there is not a strong reliance from OZES on computers to get their work done outside standard applications. Therefore, acceptance of the new system is a concern for the management team. They have requested that you write a brief memorandum commenting on adopting a User Centred Design (UCD) approach and setting a plan for the development of the Human Computer Interaction (HCI) when considering the CRM application. Briefly discuss UCD and HCI in general and investigate the implications of adopting a UCD

approach on the project, introduce your plan supported by the principles of UCD and HCI, and then state why you would recommend this plan. You are expected to use theory in your response.

Review the OZES case study to complete the memo with reference to the information in the case study. Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Attach this memo to your report as an appendix.

There is limited information available to you now but you are required to make reasonable assumptions based on the information that you have. Assumptions should be noted and specifically mentioned within your memo. Your memo should be no less than five hundred
(500) words and it would be best to be no longer than seven hundred and fifty (750) words long.

Attachment:- Systems Analysis.rar