System Analysis and Design Report: Family Farm Fresh Foods Case Study

This report presents a system analysis and design case study for Family Farm Fresh Foods (F4). It begins with an overview of the system's main functions, including customer registration, order management, and delivery processes. The report details the roles interacting with the system, primarily the admin, delivery personnel, and customers, followed by a use case diagram illustrating key functionalities like placing orders, signing credit slips, and handling payments. The report provides a detailed use case description for placing orders, outlining preconditions, postconditions, normal course of events, and alternative scenarios. Part 7 critically analyzes the system, identifying potential data duplication and inconsistency issues, and presents an Entity-Relationship Diagram (ERD) along with table designs and data population examples. Part 8 explores system sequence diagrams and discusses commercial packages like Maintenance Connection and GetSwift. It then evaluates new system options, including in-house systems, Management Information Systems (MIS), and Enterprise Resource Planning (ERP), concluding with recommendations for stakeholder inclusion, change management, and security measures.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
1. Case Study Part 6:........................................................................................................................2
1.1 Main Functions of System:....................................................................................................2
1.2 Roles Interacting with the System:........................................................................................2
1.3 Use Case Diagram:................................................................................................................3
1.4 Use Case Brief Description:..................................................................................................4
1.5 Full Use Case Description:....................................................................................................4
2. Case Study Part 7:........................................................................................................................8
2.1 Critical Analysis:...................................................................................................................8
2.2 ERD:......................................................................................................................................9
2.3 Table Designs:.....................................................................................................................10
2.4 Data Populate:......................................................................................................................11
3. Case Study Part 8:......................................................................................................................13
3.1 System Sequence Diagram:.................................................................................................13
3.2 Commercial Packages:.........................................................................................................14
3.3 New System Options:..........................................................................................................14
3.4 Conclusion:..........................................................................................................................15
3.5 Recommendations:..............................................................................................................15
Bibliography:.................................................................................................................................17

2SYSTEM ANALYSIS AND DESIGN
1. Case Study Part 6:
1.1 Main Functions of System:
The system will be maintaining functions like registering the customers, calculating their
type, order maintenance, assigning delivery personnel, payment handling and many more. The
customers will be providing their personal details and the system will be storing it into the
database. At the registration period the customer will be normal but as he/she starts purchasing
regularly the system automatically mark them as regular customers. The system will be handling
the inventory related activities of the farms. The delivery man will get message regarding the
order details and customer details who has placed the order.
1.2 Roles Interacting with the System:
The most interaction with the system will be done by the admin. The admin will be
responsible for managing most of the manual processes. The admin will be handling cases like
placing order by phone, contacting delivery man in case system is unable, updating data that are
not able to identify by system and many more. The delivery man will be providing status of the
delivery. The customer who places order may not be home at the time delivery man reaches or
delivery is delayed. In such cases the data regarding status of delivery will be provided by
deliver man.

3SYSTEM ANALYSIS AND DESIGN
1.3 Use Case Diagram:
Figure 1: Use Case Diagram of F4
(Source: Created by Author)

4SYSTEM ANALYSIS AND DESIGN
1.4 Use Case Brief Description:
Sign Paper Credit Slip: The system will be creating a paper based credit slip for each
order. The customer will be signing the credit slip after delivery is complete. The slips will be
provided to the customer at the end of each month.
Delivery: The deliveryman is responsible for delivering the places order. Customer and
deliveryman both are associated actors. The delivery can be done by two ways such as to home
of the customer who placed order and local store from where the customer will collect order.
Payment: The payment will be done by the customer after each delivery. The payment
will be calculated using the order cost and discount. The payment can be done through two ways
such as using cash or credit.
Local Daily Activity Report: The system will be generating daily activity report based on
the day to day business processes. These reports will be sent to the head office for decision
making and business process tracking purpose.
1.5 Full Use Case Description:
Use Case ID: User_UC_2
Use Case
Name:
Place Order
Created By: <Please Fill> Last Updated By: <Please Fill>
Date Created: <Please Fill> Date Last
Updated:
<Please Fill>

5SYSTEM ANALYSIS AND DESIGN
Actor: Customer
Description: The customer will be placing order to Family Farm Fresh
Foods system through phone call or online submission form.
Preconditions: The customer must be registered
Post conditions: The customer address must be valid
Priority: High
Frequency of Use: Daily
Normal Course of
Events:
The customer will provide all the details of vegetables or
other products that he/she intends to purchase
The system will find the items in a farm near the customer
The system will confirm order after the products are available
Alternative Courses: If the products are not available in the farm, it will be
delivered there
The deliveryman will be holding the delivery till the customer
confirms the order delivery date
Exceptions: The customer will get the delivery by expected time and order
process will be adequate
Includes: Calculate Benefit
Special Requirements: Addition of vegetables after placing orders

6SYSTEM ANALYSIS AND DESIGN
Assumptions: The customer is already registered
Notes and Issues: Change of address

7SYSTEM ANALYSIS AND DESIGN
Figure 2: Activity Diagram of F4 Order Place
(Source: Created by Author)

8SYSTEM ANALYSIS AND DESIGN
2. Case Study Part 7:
2.1 Critical Analysis:
Duplication and inconsistency can be see for customer as the customer can be moving
from one place to another without informing the organization. In this case the organization
delivery service will be hampered. The same customer can get registered into the system using
different verification proof. In such cases chance of duplication of data is very high. The data
duplications can be seen in terms of products that the organization sell. Various farms sell the
same products to the nearby customers. The name of the products may vary (regarding few
products) for farm to farm. Data inconsistency can be seen in various parts of business operations
also.

9SYSTEM ANALYSIS AND DESIGN
2.2 ERD:
Figure 2: ERD of F4
(Source: Created by Author)

10SYSTEM ANALYSIS AND DESIGN
2.3 Table Designs:
Table: Customer
Attribute Key Code format
custID Primary Selection of customer from
all the customer list
Name None None
Address None None
Contact_Number None None
Email None None
Type None None
Table: Order
Attribute Key Code format
orderID Primary Selection of orders made by a
customer from all the orders
custID Foreign None
orderdate None None
deliverydate None None
status None None

11SYSTEM ANALYSIS AND DESIGN
amount None None
Table: Payment
Attribute Key Code format
paymentID Primary Selection of payment made
by a customer against an
order from all the payment
list
orderID Foreign None
paymentDate None None
totalamount None None
discount None None
pay None None
2.4 Data Populate:
Table: Customer
custID Name Address Contact_Numbe
r
Email Type

12SYSTEM ANALYSIS AND DESIGN
Cust101 Roger
Jenkins
12 Main
Street
8976543 [e-mail] Regular
Cust102 James
Princep
4, Camac
Street
4567123 [e-mail] Normal
Cust103 Anna
Moria
12/34,
Hover
Street
09872345 [e-mail] Normal
Table: Order
orderID custID orderdate deliverydate status amount
Order801 Cust101 1/21/2018 1/22/2018 Que 1233
Order802 Cust103 3/18/2018 3/21/2018 Delivered 245
Order803 Cust102 3/3/2018 3/7/2018 Cancelled 455
Table: Payment
paymentI
D
orderID paymentDat
e
totalamoun
t
discount pay
Pay401 Order80
1
1/22/2018 1233 0 1233

13SYSTEM ANALYSIS AND DESIGN
Pay402 Order80
3
3/21/2018 245 10 221.50
Pay403 Order80
2
Null 455 0 0

14SYSTEM ANALYSIS AND DESIGN
3. Case Study Part 8:
3.1 System Sequence Diagram:
Figure 2: System Sequence of F4
(Source: Created by Author)

15SYSTEM ANALYSIS AND DESIGN
3.2 Commercial Packages:
Maintenance Connection: It is a cloud based software framework utilized in the business
with the purpose of handing maintenance. As the software package is suitable for SME, Family
Farm Fresh Foods can use this package within its environment (Maintenance Connection 2018).
The organization can edit the home page of the system as per the role of the end users. It is very
supportive in terms of customer support and training. Tracking assets can be done through
various ways.
Get Swift: The package is very good in terms of cut costs, speed up and reducing path
covered in terms of delivery of product. The package is able to provide enhance efficiencies
within F4 customer support center (GetSwift 2018). The staff needed to handle delivery of
products needs not be increased as the organization will grow for certain enhancement in
business area coverage.
3.3 New System Options:
In House System: In house system is the IT framework in which all the IT assets are own
by the organization itself. The hardware will be purchased by F4 and the organization will be
responsible for maintaining the system (Kessel et al. 2016). In case the organization is looking
forward to using the in-house system for a long time, it is the best solution but for a short period
of use it is very costly.
Management Information System: The management information system will be
controlling all activities of the organization that are related to management (Laudon and Laudon
2016). The system will be handling delivery process through the GetSwift software package.

16SYSTEM ANALYSIS AND DESIGN
Enterprise Resource Planning: ERP will be using for establishing a proper
communication organization wide. All the aspects of the business from farms to delivery man to
customers will be under the supervision of ERP (Leon 2014). ERP is more costly than MIS. It
can be cloud or in-house system.
3.4 Conclusion:
From the above study it can be concluded that the new system can be a great source of
innovating business for Family Farm Fresh Foods. The use case diagram has provided the
understanding of end-user interactions. The activity diagram has been done for only one use
case, an activity diagram consist of all the activities done by the end users and system will be
able to provide better understanding of system functionalities. The database is comprised of all
the data that are relevant for business, there is a scope of improving the database. The system can
be using various packages like customer relationship management, inventory management,
delivery management and much more. As the organization is medium sized, the delivery
software package and business maintenance software package is required most.
3.5 Recommendations:
Including all the Stakeholders: Family Farm Fresh Foods has various internal and
external stakeholders like customer, employees, suppliers and man more. Considering the impact
of all the stakeholders during development of system is crucial. The stakeholders will be
included in various processes of development where they are most appropriate.
Making Change Management Plan: Implementing a system at Family Farm Fresh
Foods’s environment will result into changes in business process. The organization must create a
change management plan so that these changes can be handled properly.