Reference no: EM132118486

Case Study: Odd Jobs Limited.

Background:

Odd Jobs Limited (OJL) is a Sydney based business which has begun to offer casual labour to other businesses. The business offers skilled staff and vehicles for hourly hire with a three (3) minimum.

The business was started by the business owner, ColinGrey who undertook all the planning and management of staff to jobs however the business has now grown to include over 100 part-time and full-time employees. The organisation is also looking to expand further into other centres. Currently Colin and staff are trying to manage the staff, customer relationship systems and invoicing with off the shelf software which have worked well in the past and an off the shelf accounting system which is used to manage the accounts receivable and accounts payable of the business.

The staff of OJL drive a varied selection of vehicles which are owned by OJL. These vehicles range from motorbikes, cars/ utilities and heavy goods vehicles.As a requirement of their insurance policy, OJL must ensure that the staff have the appropriate licence for the vehicle they are assigned to and keep records on this(Required licence). This means that as part of their staff record keeping they must maintain details of a staff member's licence. They also need to maintain details of their name, address, contact details, tax file number and industry qualifications. There are contracting staff who work like private contractors (as required), these people are expected to maintain their own industry qualificationsand professional indemnity but OJL must maintain details of the licence. The office staff have set hoursand no record of their licences are maintained.

Although an off the shelf accounting package is used and email for communication with suppliers and customers there is currently a low level of computer use in the organisation. The contracting staff use anOJL supplied phone and their own laptops, tablets etc. while the office staff use supplied computing machinery as they are not required to be mobile. The contracting staff phone or email hours spent on a job and ask for details of their next job to head office. This means that currently some staff at head office almost exclusively handle telephone calls from contracting staff. The head office staff have got to know the contracting staff well as they have worked together for a long time and they often enjoy a chat about what is happening in head office, when the staff phone in job details. These phone calls are often lengthy as some staff only phone their job details in once a week, this concerns Colin Grey as he does not know the value of the daily hours of each staff and vehicle.

Although the manual systems for stock management and customer relationship management have worked in the past, Colin Grey and the new staff manager, Gary Tallent and customer manager Tom Smith feel a new system including a phone-based app could offer significant improvements to the work processes currently in place.

Tom Smith would like the contracting staff to update the job details as they complete the job. One of his requirements would be to enable the contracting staff to complete the customer invoice at the completion of the job by inputting hours and vehicle details (based on registration number). This is so he can check on jobs as there are completed. While Gary Tallent, would like to run a report once a month that showed job figures and the income generated by each vehicle.

Business Processes:

A JAD session with key stakeholders revealed the following information. The business processes described below are the system requirements for this information system solution:

- It has been decided to focus on the building and implementing the mobile based app for the contracting staff and run a separate project for the customer relationship management system later. Therefore, do not model any of the customer relationship managementsystem (this is where OJLmaintain details of their customers).

- However, OJLstill needs to record the following details for all customers: Name, Business number, Address, Telephone, Email, and Date of last job.

- OJLneeds to maintain vehicle details for the separate vehicle classes as per the licence requirements including maintenance details. OJL must be able to track the movements and drivers of all vehicles.

- Tom Smith wants to run a job report on the first of every month that shows the value amount of each job, type of job and per contracting staff member.

- Tom Smith also requires that the following information on each job be kept, the customer, the date of the job, contracting staff (maybe more than one), vehicles(‘s) used and amount of job.

- Any payments for salaries or expenses to staff are outside the scope of this system

Part A

Question 1: Report

Your manager Colin Grey is sure an adaptive systems development methodology would be useful in this project but there is little knowledge about these in the organisation. Therefore, they want you to write a report discussing adaptive development and two methodologies Scrum and XP. 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 detail from the case study in your report as examples, rather than given general information.

The following sections need to be included;
o Adaptive methodologies - general introduction to the methodologies, including when you would use an adaptive methodology.
- General discussion
- Advantages
- Disadvantages
o Scrum
- General discussion
- Advantages
- Disadvantages
o XP
- General discussion
- Advantages
- Disadvantages
o Recommendation
Your target audience is executive business people, who have extensive business experience but limited computing knowledge.
Your report should be no less than one thousand (1000) words and it would be best to be no longer than one thousand five hundred (1500) 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.

Question 2: Memo

Review the OJL case study and answer the following question with reference to the information in the case study.

OJL have requested that you write a brief memorandum commenting on and setting a plan for the requirements gathering. Briefly discuss requirements gathering in general, introduce your plan and then state why you would recommend this plan. You are expected to use information from the course in your answer, for instance lecture three such as how you will gather information, what questions will you ask. Please cover the make or buy decision, could you buy already existing software to solve OJL problem (you must justify your answer). It is expected that you use the detail from the case study in your essay and failure to do this will reduce your marks

Your target audience is executive business people, who have extensive business experience but limited computing knowledge. Attach this memo to your report from question 1 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 seven hundred and fifty (750) words and it would be best to be no longer than one thousand (1000) words long.

Part B - Modelling and Diagramming 

Review the OJLcase study and answer the following questions with reference to the information in the case study.

Do NOT extend the scope for any of the following solutions beyond that specifically described in the case study above.

You are 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 each question solution.

Question 3: Event Table

Review the OJL Limitedcase study and prepare an event table for the information system to support the business processes as described. Use at least the following headings for the Event Table:

Question 4: Domain Model Class Diagram

Review the OJL Limitedcase study to prepare a domain model class diagram for the supporting information system.

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.

It is not necessary to show methods, however you may include them if you wish. Solutions are expected to align with the components.

Question 5: Design Class Diagram

Prepare a Design class diagram for the Joband Staff memberclasses ONLY. These two classes should be part of the Domain model class diagram solution for the previous question.

Each of these design class diagrams are expected to have a complete attributes list and a comprehensive methods list which supports the specified functionality as described in the case study.

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.

Question 6: Use Case Diagram

Review the OJL Limitedcase study and your event table solution from question 1 to prepare a Use Case diagram for the supporting information system.

Solutions must follow the methodology as outlined within the Satzinger et al textbook. Solutions are expected to align with the components.

Question 7: Use Case Description (intermediate)

Prepare a Use Case intermediate description for the 'Creates job' use case, as documented in the event table solution and the use case diagram solution.

Solutions must follow the methodology as outlined within the Satzinger et al textbook. Solutions are expected to align with the components.

Attachment:- Task.rar