Southern Cross University - Case Study

SOUTHERN CROSS UNIVERSITY
ASSIGNMENT COVER
Student Name:
Student ID No.:
Unit Name:
Unit Code:
Tutor’s name:
Assignment No.:
Assignment Title:
Due date:
Date submitted:
Declaration:
I have read and understand the Rules Relating to Awards (Rule 3 Section 18 –
Academic Misconduct Including Plagiarism) as contained in the SCU Policy
Library. I understand the penalties that apply for plagiarism and agree to be
bound by these rules. The work I am submitting electronically is entirely my
own work.
Signed:
(please type
your name)
Date:

Table of Contents
PART B.......................................................................................................................................................3
Introduction.................................................................................................................................................3
5. Data Gathering Activities.........................................................................................................................4
How interview is conducted..............................................................................................................4
Interview Questions...........................................................................................................................5
Advantage of the interview...............................................................................................................8
Disadvantage of the interview...........................................................................................................8
6.Use Case Descriptions and Diagram; Activity Diagrams.........................................................................9
Brief use case description......................................................................................................................9
Table 1 below shows brief use case descriptions for the kevin’s Farm information system.........9
A Full Use case description.................................................................................................................10
Table 2 below shows full use case description of the purchase Kevin’s farm produce...............10
Use Case Diagram................................................................................................................................12
Figure 1 below show the use case diagram for the Kevin’s farm information system................12
Activity Diagram.................................................................................................................................13
Figure 2 below shows the activity diagram for the Kevin’s farm information system..............13
7.ERD and Domain Model Class Diagram................................................................................................15
Entity Relationship Diagram..............................................................................................................15
Figure 3 below shows ERD and database schemas for the Kevin’s farm information system...15
Domain Model Class Diagram............................................................................................................17
Figure 4 below shows a Domain Model class diagram for the Kevin’s farm information system
...........................................................................................................................................................17
8. System Sequence Diagram..............................................................................................................19
Figure 5 below shows the sequence diagram for the Kevin’s farm information system.............19
Conclusion.................................................................................................................................................20
Reference...................................................................................................................................................21

PART B.
Introduction.
The Kevin is the owner of the farm and was initial started by Kevin and his friend. The farm is
run by Kevin and his wife Mary. They also have other workers who help in the operation of the
farm. The farm started in their home later it expanded. The Kevin’s farm produce is produced
organically and these produces are certified vegetables, fruit and nuts, honey, decorative plants
and eggs. The permaculture principles and biodynamic soils is used to grow these farm produce.
The farm was started at Kevin’s home. The farm was started as a need of organic grown food by
the community.
The farm has expended from being domestic farm with small number of customers into the huge
commercial farm producing a lot of farm produce. Kevin has decided to use one of the spaces of
their home farm which was used for grazing cattle to expand on his farming activities. Kevin
works with his friend, wife and has workers who he recent employed from the Southern Cross
University’s Plant Science faculty to help in managing a farm.
Due to increase in produce of large volume of farm produce, animal output and in the increase of
customers name and demand of the Kevin’s farm produces. Kevin find it difficult to monitor and
track farm activities well. So, there is need to develop the information system that shall help in
managing the increased farm complexities.
There is need to automate farm activities by developing the farm information system that shall
make farm activities more efficient, effective and secure while making their customer satisfied
This report shall explain data gathering techniques such as interview(Satzinger et al. 2016).. The
data collecting is to be done and analyzation of the collected data. Different UML diagrams shall
be drawn after analysing the data collected and case study of the Kevin’s farm (Lethbridge and
Laganiere,2016). This report shall have facts from the analyzation of the business need and
suggestions to the required changes. This report shall be used as a tool to implement the
information system (Sommerville, 2016).

5. Data Gathering Activities.
The interview is to be conducted between consultant and the workers to collect vital information
that shall help in the development process of the system (Agarwal and Goel, 2014).
How interview is conducted.
Determining the goal of the interview is being established.
What kind of information is needed to be obtained?
Is information able to help in improving the system?
Is the interview information solution to the research?
Identify the interviewee.
The participant should have knowledge about the information you need to obtain.
The goal of the interview is also considered during identifying the interviewee (Sommerville,
2016)..
Schedule appointment with the interviewee.
Obtain appropriate date and time for the interview.
Prepare the interview guide.
The open-ended questions are formulated.
There is need to avoid leading questions.
There is need to create clear and easy to understand interview questions.
The interview questions are to be focusing on the goal of the interview and should have a room
to be adjusted thus make them flexible.
The interview questions should be in align with data gathering and analysing goals.

Conducting interview.
Meet the interviewee at the scheduled place, time and date (Sommerville, 2016).
Giving interviewee the interview questions.
Start interviewing the interviewee.
Recorded the interview.
The interview can be recorded on the piece of paper, recorded using audio or video (Satzinger et
al. 2016).
Transcribe and analysing the interview.
After obtaining the recorded data from the interview there is need to analysis the data to
obtaining useful data that is helpful in the implementation of the Kevin’s information
system(Satzinger et al. 2016)..
Gathering process ends.
The data is finally gathered and this data meets the system requirement.
Interview Questions
Dear Participant.
I am a consultant conducted to gather requirements for the system and analyze the system
requirements for the project. The requirements collected are helpful during the implementation
of the Kevin’s farm information system(Satzinger et al. 2016).. I kindly request you to cooperate
and provide detailed information in your area of expert. Kindly feel free to provide all detailed
information you may know in your field. The objective of this interview is to collect information
that shall help in analyzing of the system requirement and ensure all the requirements are

involved and also to ensure different stakeholder participate in the development process (Agarwal
and Goel, 2014). The response of this interview shall be kept with a lot of confidential and
integrity. The interview shall take few of your minutes not more than 30minutes.
The following below are the interview questions kindly take 5 minutes to read understand before
we start with the interview.
Can you allow us we proceed with the interview 1=N0[] 2=No [
Section I
1.What is your position at the farm?
2. Kindly tick by ticking in the brackets below.
Manager [] worker [] owner[]
3. What are your roles at the farm?
4. What activities do you participate in at the farm?
5.what kind of produces does a farm deal in?
6.Can you tell me about the Kevin’s farm in you own way?
7. How many customers do you receive per day?
8.Do you interact with customers?
If yes how often is this interaction?
Daily[] weekly[] monthly[]
8.what are the problems have the customer raise?
9.what are your suggestions about customer problem?
10. what is the solution to customer problems?
11.what are the produce that customer orders mostly?
Fruits [] Honey[]
12. How do the customer places order?
13 .How fast are your produce get ready for the market?
14.How do you track and monitor customer orders?
15.Have you every interacted with the any information system?
16.How was interaction with information system?

SECTION 2
Kindly select YES or No
Usability YES NO
Have you ever used the new Kevin’s information system?
Is the Kevin’s information system protype user-friendly?
Is the system simple to use?
Is the system easy to learn how to use?
Is the system information about the produce easy to understand?
Do you think the information system is productive to use and has value?
RELIABILITY
Is the system prototype having errors?
Does the prototype perform correctly?
Are the fields validated to capture intended data?
AVAILABILITY
Is the system available always
How often does system go off .
SATISFACTION AND FUTURE USE
Is the Kevin’s farm information system productive and can it help in keeping
data and track transactions for customer?
Do you think the system shall be of help to the farm?
Will the system help farm increase profit and make customer satisfied?
SECTION III
Kindly make your suggestions and recommendations for you would like we work on.

Kindly identify issues with system you are using and what changes do you suggest we
make?
Thank you for taking your time.
Advantage of the interview.
The interview is flexible because the interviewer can adjust on the type of the question to ask but
the questionnaires the questions are fixed nothing can be added again (Dick et al. 2008)
There is high response rate during interview because workers how are not able to write and read
are able to take part in the interview by answering questions (Dick et al. 2008).
The interviews help in capturing the no-verbal behavior of the participant because there is face to
face interaction with the respondent (Agarwal and Goel, 2014).
The interviews help in obtaining detained data because the interviewee is able to provide extra
information in his/her area of expert that the interviewer may not have knowledge with.
Disadvantage of the interview.
Expensive
The interview is costly because it requires employees to enable interview to take place.
The information collected mostly depends on the interviewer’s ability and skills in conducting
interview and gathering information well (Agarwal and Goel, 2014)..
Most interviews are conducted manually and information collected is transferred into soft copies.
Small sample size.
Most interview are conducted on small group of people as compared to the questionnaire which
cover a lot of people. This make interview to have limited size (Dick et al. 2008).
Limited time

Interview are time consuming because there is need to schedule and plan for the interview.
6.Use Case Descriptions and Diagram; Activity Diagrams.
Brief use case description.
Table 1 below shows brief use case descriptions for the kevin’s Farm information system.
Use Case Brief Use Case Description
Register customer The new customer enters details on the
system registration form and submits the
system then verifies the customer registration
and provide customer with login details.
Customer login. The customer login on the system using
username and password to access system
main features.
Search produces The customer searches for the Kevin’s farm
produce on the system by produce id or name.
View farm produce The customer views the available farm
produce on the system.
Place order The customer places order by adding
produces on the shopping cart.
Book The customer provides the details of the
produce he/she need to purchase by booking.
Confirm order The worker confirms the availability of the
order
Confirm booking The worker confirms the customer booking
Make bill The worker processes the bills for the
customer order
Make Payment The customer selects the payment option
either by cash or credit to settle payments
Receive payment The worker receives the payment from

customer.
Make produce change The worker makes some changes on the
produces availability
Purchase produce The customer buys the farm produce.
Purchase confirmation The customer receives a notification for the
confirmation of the purchase of the order
Deliver order The customer orders are delivered to
customer at the preferred date and time.
Pick up order Some customers prefer to come and pick their
orders on their preferred time and date.
A Full Use case description.
Table 2 below shows full use case description of the purchase Kevin’s farm produce.
Full Use Case Description purchase
Use Case Name Purchase Farm produce
Scenario Success Scenario: The farm produce is
successfully purchased.
Fail to purchase produces because produces
are not available.
Failed to purchase produce because
customer do not have enough money in the
account.
Triggering Event The customer wants to buy Kevin’s farm
produce
Actors Customer and Worker
Purpose To purchase farm produce.
Overview/Description The use case demonstrates how the
customer purchases produces on the
information system.
Type Study and implementation Requirement.

Stakeholders Mary, Kevin, customer, regulation board,
government and worker
Pre-Conditions The system is working well. The farm
produce is available on the system. The
customer has not yet login.
Post-Conditions The customer has purchased farm produces
and received purchase complete
notification.
Special Requirements
Flow of Events
Actor Action System Response
Customer login on the system and
purchases produce on the system then
logout on after buying
System verifies purchase details and notify
customer of the purchase complete.
Alternate Flow of Events/Exceptional Conditions
Customer purchases produces by making
payment of the produce
Incorrect produce details.
Produce not available on system.
System error.

Use Case Diagram.
Figure 1 below show the use case diagram for the Kevin’s farm information system.
The actors.
The use case actors include customer, Regular and worker.
The use cases
The following are the use cases for the Kevin’s farm information system.
Place order, buy farm produce, login, register, search produce, produce available, make
payments, collection list, automatic discount off, receive payments, make bills, manage
bookings, customer book, add produce list, make change and deliver order.
Assumptions: The regular is a customer who buys farm produce regularly and normal customer
take time to buy produce.

Activity Diagram.
Figure 2 below shows the activity diagram for the Kevin’s farm information system.
The smimlane include customer, Kevin’s information system, and staff.
The customer is the smimlane that needs the farm produce and interacts with the system.
The Kevin’s information system it is the smimlane that provide a platform for customer and staff
to interact with (Penzenstadler et al. 2014).
The staff is the smimlane that offers customers services and interacts with the system.

The activities.
The activities include login, validation, search produce, check produce availability, place order,
confirm order, Book, confirm booking, purchase produce, confirm purchase, make payment,
confirm payment and login out.
The activities start when the customer wants to buy the farm produce from Kevin’s firm. The
customer starts by login and provide user name and password to login. The system checks if
login details are valid. When the login details are not valid the user is informed to login with
correct login details. When the login details are correct. The customer searches for the farm
produce on the system, when the produce is not available the customer is redirected to search
with correct id, or to wait for produce and search again. when the farm produce is available. The
customer places order on the system by entering the details of his/her order (Petre, 2013). The
staff confirms order. On receiving confirmation, the customer makes bookings of the order. The
staff confirms order bookings. The customer purchases produce and make payments for the
order. On receiving the payments, the staffs confirm payments. The staff the delivers the produce
to the customer. When the customer receives the order. The customer logout. The process ends
when customers has successfully received order (Wiegers and Beatty, 2013).
Assumptions.
There is assumption that to access the Kevin’s farm information system all the system users have
to be registered and have username and password (Petre, 2013).
There is assumption that most produce are available on the system and the staff can add more
produce. The produce is always available unless out of stock or not yet ready for the market
(Satzinger et al. 2016).

7.ERD and Domain Model Class Diagram
Entity Relationship Diagram.
Figure 3 below shows ERD and database schemas for the Kevin’s farm information system.
Entities.
The entities for the Kevin’s farm information system include; Payment,Order,Book,
Produce,customer,Worker, Normal Customer, Regular Customer.
The attributes
The attributes for the entity Payment include PaymentNo,name,type,date and time.
The attributes for the entity Order include OrderNo,Name,date and time
The attributes for the entity FarmProduce include Name,type,Description, ProduceNo and price.
The attributes for the entity Customer include Firstname,lastname,Address, Type,customerNo
and PhoneNumber
The attributes for the entity Normal customer include
Firstname,lastname,Address,Type,customerNo and PhoneNumber

The attributes for the entity Regular Customer include
Firstname,lastname,Address,Type,customerNo and PhoneNumber.
The attributes for the entity Booking includes BookingNo, Name, Type, Date and Time.
The attributes for the entity Worker include FirstName, LastName,PhoneNumber,address, type
and workeId)
Schemas
Payment (Payment No(pk), name, type, date, time)
Order (OrderNo, Name, date, time)
FarmProduce (Name, type, Description, ProduceNo, price)
Customer (Firstname, lastname, Address,Type,customerNo, PhoneNumber)
NormalCustomer (Firstname, lastname, Address, Type, customer No, PhoneNumber)
RegularCustomer (Firstname, lastname, Address, Type, customerNo, PhoneNumber)
Booking (BookingNo, Name,Type,Date, Time)
Worker (FirstName, LastName, PhoneNumber, address, type, workeId)
Relationships
There is confirm payment relationship between entity worker and payment entity.
There is make payment relationship between entity customer and payment entity.
There is place relationship between entity customer and entity order.
There is purchase relationship between entity customer and Farm produce entity.
There is make book relationship between entity customer and entity booking.
There is sale relationship between entity worker and Farm produce entity.
There is confirm order relationship between entity worker and entity order.
There is confirm booking relationship between entity worker and entity booking.

There is confirm payment relationship between entity worker and payment entity.
Domain Model Class Diagram.
Figure 4 below shows a Domain Model class diagram for the Kevin’s farm information
system
The classes.
The classes are Payment, Order, Book, Produce,customer,Worker, NormalCustomer,
RegularCustomer
The attributes
The attributes for the Payment include PaymentNo, name, type, date and time.
The attributes for the class Order include OrderNo, Name, date and time
The attributes for the class FarmProduce include Name, type, Description, ProduceNo and price.
The attributes for the class Customer include Firstname, lastname, Address, Type, customerNo
and PhoneNumber

The attributes for the class Normal customer include Firstname, lastname, Address, Type,
customerNo and PhoneNumber
The attributes for the class Regular Customer include Firstname, lastname, Address, Type,
customerNo and PhoneNumber.
The attributes for the class Booking include BookingNo, Name, Type, Date and Time.
The attributes for the class Worker include FirstName, LastName, PhoneNumber, address, type
and workeId)
Assumption.
The customer can be a normal or Regular.
The class customer is the super class of class Normal and Regular.
The class Normal and Class Regular are subclasses of the Class customer.
The class Normal and class Regular inherits some properties of the class customer.
There is assumption that farm produces are always available on the system.

8. System Sequence Diagram.
Figure 5 below shows the sequence diagram for the Kevin’s farm information system.
Object lifeline.
The object life lines are as follows; customer, Kevin’s farm information system. And workers.
Sequence steps.
1. Customer registers on Kevin’s farm information system.

2. Registration details are verified and customer gets confirmation of successful registration or in
case registration not allowed customer also gets notification of failure of registration.
3. Login customer enters username and password.
4. Verification of login details username and password are verified (Wiegers and Beatty, 2013).
5. Validation valid login details are successful allowed to login and proceed to next sequence but
invalid logins. customer needs to input correct details in case customer forgot details he/she can
reset password or username name (Satzinger et al. 2016).
6. Customer search produce.
7. Customer View available produce.
8. Customer Make payments.
9. Receive payments.
10. Worker take orders.
11. Make some changes on the produce about availability.
12. Collect list.
13. Confirm order
14. Confirm booking
15. Confirm payment
16. Allow auto discount.
17. Buy produce.
18. Deliver or pick up produce.
Assumption.
The Kevin’s farm information system is always available and operating normally to enable
customer and workers to interact with it.
Conclusion
This report when adopted is very vital and can easy the development process of the farm
information system (Pressman, 2018). The report is detailed and most of the requirements of the
system has been captured in the report after analyzing the case study and collecting data from the
worker. The UML diagrams has been drawn (Satzinger et al. 2016). This report is detailed enough
to be used in the implementation of the system.

Reference.
Agarwal, M. and Goel, S 2014, Expert system and its requirement engineering process. In International
Conference on Recent Advances and Innovations in Engineering (ICRAIE-2014) . IEEE.
Dick, J., Hull, E. and Jackson, K 2017. Requirements Engineering, Springer.
Penzenstadler, B., Raturi, A., and Tomlinson, B.2014. Safety, security, now sustainability: The
nonfunctional requirement for the 21st century. IEEE software.
Petre, M., 2013. UML in practice. In 2013 35th International Conference on Software Engineering (ICSE).
IEEE.
Wiegers, K. and Beatty, J., 2013. Software requirements. Pearson Education.
Satzinger, J, w, Jackson, R, B and Burd, S, D. 2016. System Analysis and Design in A changing World .6th
edn, Boston Course Technology.
Sommerville, I.2016. Software engineering .10th edn, University of St Andrews, Scotland: Pearson.
Pressman, S, R.2018. Software Engineering. Practitioner’s Approach.8th edn, Inc., 1221 Avenue of the
Americas, New York, McGraw-Hill2018.
Lethbridge, T, C and Laganiere,R.2016.Object-Oriented Software Engineering: Practical Software
Development Using UML and Java. 3nd edn., New York, McGraw-Hill.2016