ICT700 System Analysis and Design: Odd Jobs Limited System Report

This report presents a system analysis and design for Odd Jobs Limited, a Sydney-based business providing casual labor and vehicles to businesses. The current system relies on phone calls and emails for job updates, which is inefficient. The proposed solution is a mobile application for contracting staff to update job details and generate invoices. The report discusses adaptive methodologies like Scrum and Extreme Programming (XP), recommending XP for its cost and time savings. It also details requirements gathering techniques, including interviews, questionnaires, user observations, workshops, and prototyping. The report includes an event table, domain model class diagram, design class diagram, use case diagram, and use case description to illustrate the proposed system's functionality. Desklib offers similar solved assignments and study resources for students.

1
Odd Jobs Limited System Analysis and Design
:
ODD JOBS LIMITED SYSTEM ANALYSIS AND DESIGN
By (Student names)
[Course Name]
[Lecture Name]
[University Name]
[City where the university is located]
[Date]

2
Odd Jobs Limited System Analysis and Design
Table of Contents
Part A...............................................................................................................................................3
Introduction to Adaptive methodologies.....................................................................................3
Adaptive methodology.................................................................................................................4
Discussion................................................................................................................................4
Advantages..............................................................................................................................5
Disadvantages..........................................................................................................................5
Scrum methodology.....................................................................................................................5
Discussion................................................................................................................................5
Advantages..............................................................................................................................6
Disadvantages..........................................................................................................................7
Extreme programming (XP) methodology..................................................................................7
Discussion................................................................................................................................7
Advantages..............................................................................................................................8
Disadvantages..........................................................................................................................8
Recommendation.........................................................................................................................8
Memo...............................................................................................................................................9
Description of requirements gathering......................................................................................10
Plan for requirements gathering OJL.........................................................................................11
Discussion for OJL....................................................................................................................12
Recommendation.......................................................................................................................13
Part B.............................................................................................................................................13
Event Table................................................................................................................................13
Domain Model Class Diagram..................................................................................................14
Design Class Diagram...............................................................................................................15
Use Case Diagram.....................................................................................................................15
Use Case Description (intermediate).........................................................................................16
Reference.......................................................................................................................................17

3
Odd Jobs Limited System Analysis and Design
Part A
Introduction to Adaptive methodologies
The odd jobs limited is a Sydney based business and mainly offers services to their customers by
providing the staffs casual labour and vehicles to some businesses, the staffs offered are highly
skilled on the tasks hired for and is paid hourly.
Colin grey has been doing the planning and management of the business which is currently
having a total of 100 employees and currently the business will be expanding to various centers
and the main role being the staffs, customer’s relationship system and invoicing system
management.
Currently there are two types of employees who include the office staffs and the contracting
staffs where the contracting staffs do the jobs and update their details and the amount of job done
to the office through the phone calls and emails which tend to take too long.
The management lead by Tom Smith had decided to come up with a mobile application system
that will be used by the contracting staffs to update the details of the jobs that they had
completed and also to complete the customer’s invoices stating the hours taken and the number
of the vehicle used and thus Tom Smith will be able to see the jobs as they get completed easily,
however Gary Tallent will also be able to generate the report each month indicating the jobs
done and the income gained from each vehicle.
The development of the proposed mobile application system require to be done using the system
development life cycle method to ensure the system is developed well where all the requirements
are all meet and implemented.
The adaptive methodology is the proposed development methodology to be used by the
development of the proposed mobile application.
Adaptive methodology
Discussion
The adaptive software development is a process of software development that evolved from the
rapid application development process and it involves adaptations in a continuous form with the
normal states of affair.
The adaptive development cycle replaced the waterfall process and it uses three repeated
processes which includes speculate, collaborate and learn cycles as discussed below.

4
Odd Jobs Limited System Analysis and Design
i. Speculate: it is the planning process where the project gets initiated and the
conduction of the adaptive cycle planning is done.
ii. Collaboration: This is the process of balancing the efforts which are based on the
parts of the system environment that are predictable and can have some changes as a
result of new technology, requirements, stakeholders or the software vendor.
iii. Learning: This involves giving the challenge to the system stakeholders through the
interaction with the system designs building and also testing processes and therefore
the development team learn the mistakes and correct them and also make the stake
holders have great experience with the system developed.
The adaptive software development has various characteristics that eventually make it more
preferable compared to other development processes which includes the following:
i. Missions focused.
ii. Features based.
iii. Iterative nature.
iv. Time-boxed.
v. Risks driven.
vi. Changes tolerant.
The adaptive software development process is mainly used in the following areas:
i. When the system is required to be developed fast.
ii. When the system require being interactive with the stakeholders.
Advantages
i. It is able to produce a high quality system product. This is because the system gets tested
regularly in the course of the development process to ensure effective functionality of the
entire system.
ii. It offers high customers satisfactions. This is because the owners of the system developed
get involved in the entire development process and thus they are able to follow the
development process.
iii. It has increased project’s controls. This involves the sprints meeting, transparency and the
their usage for the project development steps.

5
Odd Jobs Limited System Analysis and Design
iv. It has reduced risk. This is good aspect as it is able to do the elimination of the failures of
the project.
v. It offers faster ROI. The system is developed in an iterative means and therefore the
features tend to be delivered in an incremental way.
Disadvantages
i. It is less predictable .This is because the developers are unable to quantify the efforts
needed to deliver software.
ii. It requires more time and commitments.
iii. It has great demand on the development team and the clients.
iv. There is no system documentation.
v. The project can fall on the development track.
Scrum methodology
Discussion
The scrum development methodology is one of the agile frameworks that emphasis on the
software development processes where it requires a development team of 3 to 9 members who
breaks the work in actions that can be completed within time-boxed iterations which are referred
to as sprints and keep track of the progress in the re-planning meetings called scrums.
This methodology is mainly used in the following areas:
i. While developing a system which is hard to state its business requirements.

6
Odd Jobs Limited System Analysis and Design
ii. While developing a small project.
iii. While there is a small development team members.
iv. While the system requires to be developed within a short period.
Advantages
i. It is used in enabling the development of projects which are hard to quantify their
business requirements.
ii. It’s a used to code and test the fast moving and the cut edges developments.
iii. It is lightly controlled and requires frequent updating of the progress.
iv. It is interactive in nature.
v. It easily copes with changes due to short sprints and feedback which is constant.
vi. It is easy to measure individual productivity as a result of daily meetings.
vii. It is easy to identify and resolve issues quickly due to the daily meetings.
viii. It makes it easy to deliver a quality system within set time frame.
ix. It is usually used in web applications and media projects that require moving fast.
x. The process has minimal overhead costs in the processes and managements and thus
leading to quick and cheap results (Wixom, 2016).
Disadvantages
i. The methodology may cause creeping of the development scopes due to lack of
definite date since the system owners may demand new requirements in the cause of
system development.
ii. Inaccuracy in the project cost and time due to poor definition of the tasks.
iii. Failure of the system development due to lack of committed team members.
iv. It is only appropriate for the small and fast moving project since it has small team
members.
v. The methodology only requires team members who have experience.
vi. The system development has huge inverse effect when some team members leave.

7
Odd Jobs Limited System Analysis and Design
Extreme programming (XP) methodology
Discussion
The extreme programming is a type of agile development that aims in the production of high
quality software and high life quality for developer’s team.
The figure below shows the various processes that are followed in the XP development
methodology
(Singh, 2016).
The extreme programming methodology is used in the following areas:
i. While the system requirements are changing dynamically.
ii. While there is a small development team.
iii. Where the technology used allows automatic testing of units and functions.
Advantages
i. It allows time and cost saving by the developers.
ii. There is reduction of risks that is related to programming or failure of the project.
iii. The methodology uses simplicity.
iv. The entire process is highly visible and is accountable.

8
Odd Jobs Limited System Analysis and Design
v. There is feedback that is constant.
vi. There is efficient detection of bugs in the entire development stages.
vii. It increases the employee’s satisfactions and retentions.
viii. It is able to facilitate teamwork in the system development process.
Disadvantages
i. This is a difficult methodology and it becomes hard to convince the developers to use
this methodology.
ii. There are very many factors relied on in system development.
iii. The methodology is code centric instead of design centric.
Recommendation
In the development of the proposed application system I recommend use of the extreme
programming methodology since it will enable the time and cost saving, there will be little risk
involved, there is visibility in the process and the employees will be satisfied which will result in
better service delivery in the company.

9
Odd Jobs Limited System Analysis and Design
Memo
MEMORANDUM
To: The OJL management
From: Developers Team
Date: 2/10/2018
Subject: Mobile Application Development
Description of requirements gathering
The system requirements gathering is a vital process in the system development which involves a
process of generating the list of system requirements which includes the functional, system, and
technical requirements and these requirements are obtained from the system stakeholders who
includes the customers, system users, the vendors and the IT staffs and all will be used as the
formal types of requirements.
In the requirements gathering there are various means of getting the system requirements from
the stakeholders and this entails the things that the users and stakeholders wants the system to
behave or do, however the main challenge is that most of the stake holders has no specific
requirements and therefore there are various means of gathering several requirements from
various stake holders, analyse them and them do the implementation.
Below are the various techniques to be used in the gathering of the system requirements.
i. Conducting Interviews.
The interview conducted requires covering all the system stakeholders in order to ensure all
requirements gathered will cover all the system functions.
ii. Use of questionnaires.

10
Odd Jobs Limited System Analysis and Design
In the requirements gathering the interview method limits the stakeholders to giving the possible
information that they are aware of, however the questionnaires are then used in order to use some
probing questions and the questions used are set to cover the area which the stakeholder is not
aware of its importance.
The questionnaires are either open ended questions which the respondent has freedom to give his
own views, or can be close ended where the respondent is required to mark the choice provided.
iii. The user’s observations.
This is another way of identifying the features required in the system where one can determine
the additional features that can be added in the existing system for better functionality.The
requirements written are used in the re-inventing of the processes instead of automating them.
iv. Through the workshops.
This is a method that is used in the reconciliation process of the system requirements where the
opinions that are divergent and have contrast are reconciled to ensure the proposed system is able
to meet all the system requirements of the system users.
v. The brainstorming.
This is an activity that is carried out in the workshop where the different system parts are
considered where the current and the future state is analysed and in this case the whiteboards and
mind –mappings software are used.
vi. Roles playing.
This is a requirement gathering method where the requirements are much dependant on the types
of users and the formal role playing is used to determine how the various system sections will be
functioning as an integrated system.
vii. Use case and scenario.
This is used when the high level functional requirement is defined and thus they are used in the
validation of the system functionalities in various instances.
viii. Through prototyping.

11
Odd Jobs Limited System Analysis and Design
This is used to select the items that the users don’t want in the system and therefore the
development team can present a developed prototype to the users and they select the unwanted
functionalities which are then eliminated while other proposed requirements are added.
Plan for requirements gathering OJL
The gathering of the system requirement requires to be planned in order to ensure that the entire
process is done successfully without skipping any step. Below is the system requirements
gathering plan.
Task Description
Selecting the respondents/stakeholders This is process where respondents are identified and they are
part of the stakeholders
Selecting the tool This is where the tool to be use in the data collection is
selected and it will be the questionnaire.
Preparing the questionnaire This is where the questions are written to be used in the
questionnaire to be subjected to respondents.
Subjecting questionnaire to respondents This is the stage where the questionnaire is given to the
respondents to fill in the questions for analysis.
Collecting the questionnaire This is the stage where the filled in questionnaires are
collected for analysis.
Recording the response data This is the stage where the data is recorded in the analysis tool
for further operations.
Cleaning the data This is the stage where the data captured is cleaned to remove
any form of anomalies.
Analysing the data This is the stage where the cleaned data is analysed to get the
specific system requirements.
Identifying the final system requirements This is where the requirements are identified ready for
implementation.
Discussion for OJL
After gathering and analysis of the system requirements below are some of the requirements that
require to be implemented in the proposed mobile applications.
i. The application should allow the users to register to create an account.

12
Odd Jobs Limited System Analysis and Design
ii. The application should allow the users to login top access the system.
iii. The application should allow the customers to send requests for services.
iv. The office staffs should be able to assign the contractor the customers to attend.
v. The contractor staffs should be able to update the completed tasks, hours taken and
the vehicle used.
vi. The management team should be able to view the daily completed tasks and the profit
made.
vii. The management should be able to generate a report of the monthly completed tasks
by each vehicle and the profit made.
viii. The office staffs should be able to update any new vehicle on the system.
Recommendation
In this company they are currently using the manual process of recording and doing transactions
which is tedious, takes more time and inhibits proper records management.
Therefore I recommend the implementation of the proposed system since it will improve the
service delivery, good customer relation, easy record keeping, enhance good daily profit analysis
and also enable generation of monthly report of the vehicles and the profit made by each.
Yours faithfully,
Team leader.

13
Odd Jobs Limited System Analysis and Design
Part B
Event Table
Event Event
Type
Trigger Source Activity/Use
Case
System
Response/
Output
Destination
Record
customers
Temp Want to record new
customer
customer Recording new
staffs
customers
saved in
system
database
Database
Record
vehicles
Temp Want to record new
vehicle
Office
staffs
Recording new
vehicles
Vehicle
details saved
in system
database
Database
Record vehicle
movements
Temp Want to record vehicle
movements
Office
staffs
Recording
vehicle
movements
Vehicle
movement
details saved
in system
database
Database
Record job
details
Temp Want to record new
job
customer Recording new
jobs
New job
details in the
system
database
Database
Update
complete job
details
Temp Want to update
completed job
Contractor
staffs
Updating
completed jobs
Saving details
in system
Database
Run job report Ext Want to run jobs
monthly reports
Tom
Smith
Running jobs
monthly
reports
The job report
displayed.
Tom smith
(Laplante, 2013).

14
DRIVERS
Driverid
Names
Vehicleid
VEHICLE
Vehicleid
Name
Registrationno
Year_manufactured
Last_mainatainace_date
MOVEMENT
Movementid
Departure_location
Destination_location
Date
Vehicleid
CUSTOMERS
Customerid
Name
Business_number Address Telephone Email
Date_of_last_job
JOBS
Jobid
Customerid
Date_of_job
Contracting_staff
Vehicleid
Amount_of_job
Staffid
STAFFS
Staffid
Names
Roles
Odd Jobs Limited System Analysis and Design
Domain Model Class Diagram
(Karumanchi, 2012).

15
JOBS
Jobid int(20)
Date_of_job Date
Contracting_staff varchar(200)
Amount_of_job int(20)
Staffid int(20)
STAFFS
Staffid int(20)
Names varchar(200)
Roles varchar(200)
Recording new staffs
Recording vehicle movements
Updating completed jobs
Recording new vehicles
Create new jobs
Running jobs monthly reports
ODD JOBS LIMITED USE CASE DIAGRAM
Office Staff
Customer
Tom Smith
Contracting Staff
Odd Jobs Limited System Analysis and Design
Design Class Diagram
(Gupta, 2015).
Use Case Diagram
(Goyal,2011).

16
Odd Jobs Limited System Analysis and Design
Use Case Description (intermediate)
Use case Name: Create job
Scenario: Create a new customer’s job
Triggering
Event:
Customer need to submit some work to be done
Brief
Descriptions:
The customer visits the offices , then the staffs offices opens the system and
enter his details and the details of the job to be done in the information system
Actors: Customer, office staff.
Related use
case:
Updating completed jobs
Stakeholders: Office Staff: To record the customer and job details
Customer: To provide the customers and job details to the staffs.
Pre-conditions: Customer has some job to be done
Post conditions: Customer’s job is done and updated in the system by contracting staffs.
(Award, 2013).

17
Odd Jobs Limited System Analysis and Design
Reference
Award,E.(2013) Systems Analysis and Design .3rd edn.Delhi:Galgotia Publications Pvt Ltd.
Gupta,B.(2015) Power System Analysis and Design.1st edn.New Delhi: S Chand & Company.
Goyal, A. (2011) systems Analysis and Design Paperback .2nd edn.INDIA:Prentice Hall India
Learning Private Limited.
Karumanchi,N.(2012) Peeling Design Patterns: For Beginners and Interviews.5th edn.New
York:CareerMonk Publications.
Laplante,P.(2013) Real-Time Systems Design and Analysis: Tools for the Practitioner.2nd
edn.New Jersey:Wiley.
Singh,B.(2016) Systems Analysis and Design.4th edn.Delhi:New Age International Private
Limited.
Wixom,D.(2016) Systems Analysis and Design.2nd edn. New Jersey: Wiley publishers.