Systems Analysis and Design for 100% Organic Co.

This report analyzes and designs a new information system for 100% Organic Co., a company specializing in organic produce. The company faces challenges in managing product variety, quantity, and livestock production. This report explores the use of fact-finding techniques, interviews, and UML diagrams (Use Case, Activity, Sequence, and ERD) to develop a system that addresses these challenges. The report also includes recommendations for improving the system's effectiveness and ensuring its successful implementation.

SYSTEMS ANALYSIS AND DESIGN (ISY00243)
Student Name:
Student ID:
1

Executive Summary
The study is all about 100% Organic Business that manufactures fresh vegetables, nuts and
fruits, honey as well as eggs, which are grown from sustainable agriculture techniques and
permaculture soils. This began in the backyard of Richard Gherke. He alongside with his
friends began a vegetable garden and became a commercial enterprise due to the growing
need for quality fresh produce. In response to the large number of buyers, Richardis has
trouble keeping track of the product variety and quantity together with the production of
livestock. Thus, for this the report is going to be created for the analysis and design of the
new information system as this framework can help Richardis to navigate the company's
rising uncertainties.
2

Contents
Executive Summary...................................................................................................................2
Introduction................................................................................................................................4
Overview....................................................................................................................................5
Fact finding techniques..........................................................................................................5
Fact Finding Interview Plan...................................................................................................6
Use Case Diagram..................................................................................................................8
Use Case Description...........................................................................................................10
Activity Diagram..................................................................................................................13
ERD......................................................................................................................................15
Sequence Diagram...............................................................................................................19
Recommendations................................................................................................................20
Conclusion................................................................................................................................21
References................................................................................................................................22
List of Figures
Figure 1: Use Case Diagram......................................................................................................8
Figure 2: Activity Diagram......................................................................................................12
Figure 3: ERD..........................................................................................................................14
Figure 4: Sequence Diagram....................................................................................................18
3

Introduction
100% Organic Co. seems to be Richard Gherke’s company which specializes in organic
foods. This study is about thorough evaluations of the framework specifications for a new
information system that allows the business to provide its consumers with better service and
improve product development. In Richard’s backyard, what began to be small has developed
into a private company alongside his mother, Ardell, which embraces his theory and then
takes over the consumer relationship while Richard manages manufacturing and
development. Richard wanted to sell his goods throughout the producers' market. The
organization moved to home ground. This implied that within one specific case he could
concentrate on communicating with many clients. As the "certified organic" commodity has
gained traction, the databases and the use of farm hands have developed considerably and
buyers have taken orders, the requirement for an computer based system to cope with the
consumer base, order tracking and bills appears inevitable. Thus, the current report is going to
include the analysis and design of the new information system such as Usecase diagram,
activity diagram, sequence diagram, along with the ERD and use case description.
4

Overview
Fact finding techniques
Fact finding seems to be the evidence and knowledge gathering process focused on methods
like sampling, study, assessment, interviews, questionnaire, prototyping and the collaborative
preparation of specifications. Analyst uses appropriate insightful methods to create and
execute the current framework. It is really essential to acquire the necessary details to
implement the software in the lifespan system implementation since devices could not be
used accurately and successfully without sufficient data gathered. Early-stage strategies for
fact-finding include the system planning process, architecture, and post-implementation
evaluation of software development life cycle (Arora and Bhatia, 2018). Facts included in
any framework should be evaluated on the basis of the three steps: data facts for valuable
knowledge development, mechanism functions for the purposes and interface-designs for
user interaction. Below are three traditional finding techniques-
 Questionnaire - Questionnaires seem to be a valuable way of seeking information
from multiple people. Users complete the questions answered by system analyst and
return the responses to system analyst. People will fill the questionnaire and provide
the analyst with free responses. This seems to be a cheap form. Users are better
comfortable for specific answers when their private detail does not need to be
provided. Answers can be rapidly measured and evaluated.
 Interview -The most useful methodology for gathering knowledge from face-to - face
interactions seems to be the interview. The aim of the analysis is to discover and
validate evidence, to inspire the end-user to engage, to recognize demands and to
capture views and suggestions.
 Prototyping -Another method for seeking information is recognized as the prototype
that extracts the device criteria. Prototyping samples a little work model which is
more responsible for information system preliminary design.
Recommendation – This is to suggest to 100% Organic Company, that they must use the
interview fact finding method for collecting the relevant information from the users to
develop and design the new information system so that the business of Richard can attain the
height of success and they can be able to gain the huge attention of the customer by satisfying
their need and requirement timely and effectively. The interview method will help Richard to
be optimistic in addressing questions more quickly by inspiring the interviewees. The further
input from interviewees may be analyzed by Richard. Richard can plan interviewee questions
more relevant to each person, or can modify the questions for each person. By interpreted
body gestures and body posture, Richard may identify nonverbal interactions of interviewees
(Yang, et.al. 2017).
5

Fact Finding Interview Plan
The fact finding interview plan s designed for the two staff members of the company which
consists of approx 10 questions and that are outlined below –
Interview with the Accounts Manager (Betty) of 100% Organic Co.
Q.1 What is an information system as well as why it should be implemented in 100% Organic
Co.
Q.2 What are particular information technology maintenance activities?
Q.3 What are particular implications of Information System organization structure?
Q.4 How does the planning phase fulfill the specifications of Information System?
Q.5 What are some particular approaches used to execute Information Systems Management?
Q.6 How would you think that your business can be improved by the introduction of new
technologies or information?
Q.7 Have you prepared and made major improvements to the Its infrastructure of your
company? Offer your contribution a summary.
Q.8 Who are you really interested in becoming an information systems manager?
Q.9 How much detail is needed and will be incorporated in 100 % Organic Co.??
Q.10 What is the information technology architecture strategies?
Interview with the Owner (Richard) of 100% Organic Co.
Q.1 Why do you think that a new information system will help your business?
Q.2 What made you think that implementation of a new information system will be helpful?
Q.3 What flaws did you face with the old management system?
Q.4 Describe about your type of business and business model.
Q.5 What are the practical benefits that you assumed to be achieved after the
implementation?
Q.6 In case, if the information system won’t be able to work as per your requirements how
will you classify the work then?
Q.7 What do you expect from the Information system manager after implementation?
Q.8 What are the particular features that you require from this system?
6

Q.9 How are you going to test and maintain the system? Do you have particular department
for it?
Q.10 What if system fails or crashes in between?
7

Use Case Diagram
Figure 1: Use Case Diagram
8

Description-The above stated figure is the Usecase Diagram for the new information system,
which is a diagram of UML dynamics or behavior. The device functionality utilizes case
diagrams utilizing actors including case functions. The above diagram is showing the
collection in acts, programmes, and tasks to be carried out by the new information system.
The diagram consists of three actors named as Richard farm, customer and local store. The
various Usecases states that the customer and the local store can login to the new system or
register themselves to use the respective device. Both can be able to view the product menu
and the services available for the customer and local store such as delivery of the product. In
the similar manner, Richard farm will maintain and handle the payment records and can login
or logout the system respectively.
Functions of the new information system –Input data collection, retrieval, analysis, and
performance information are functionalities of information system. The roles also regulate the
flow of information and the input circuit. The applications can also be opened and closed
(Fernández-Sáez, et.al. 2016).
Input - There are two types of data into an information system:
o Comprehensive data is generated to collect and organize the output
o The customer shall decide of form of study is carried out
Output - In this case, the visual and descriptive production seem to be of two kinds:
o Graphical output is being used for displaying information on a wider scale and
is eventually displayed as tables, maps, diagrams and figures.
o The output of this new information system will assist Richard to track all the
orders of the customer and manage the details related to the orders.
Storage -The next function seems to be to store all data entered throughout the new
information system. Everything processed seems to be at the maximum level of
information, so that it could be viewed correctly and conveniently. In this proposed
system regular backups need to be made so that all saved data isn't really destroyed
throughout the event of any error/virus. In order to deter natural disasters, they can
often be maintained in various places. This storage impacts both the initial data
storage and the backup data management (Torre, et.al. 2018).
Processing - A process seems to be a functionality that converts data in information.
A clear procedure will be to add many elements, including the position of a shop, or
the goods, or date and time, which are marketed by a corporation. Functions which
measure and make any assumptions regarding incomplete information are more
complicated processes to construct insights from the system available.
Track order history and records – This system can track all the order and can also
maintain the history of these orders along with their records of the customer orders.
The history of orders seems to be a simple means for a consumer to control both
existing and past orders as well as the buying process. This helps the customer to have
the latest on-line stuff, along with tracking notifications, distribution and payment
specifics for each order made online.
Sales and return will be computerized - This device helps 100 % organic businesses
to track sales volumes all day long in real time. Company should be updated for
product orders, figures and sales, also recognized as order management tools.
All areas like supply management and distribution orders are computerized -
This system work according to common rules to manual, and are versatile and details
can be quickly accessed. The product evaluation can be achieved easily so that the
owner of the system can see how fast a specific object runs (Stone, et.al. 2017).
9

Use Case Description
Usecase 1
Usecase Name Customer information
Actors Customer, Local store
Usecase Description Customer Information usecase includes both customer information
and some structured information including all non-public
confidential customer information which the other side holds.
Through this, the customer can be able to add their necessary details
and the local store can view the details of the customer.
Usecase2
Usecase Name Product Menu
Actors Customer
Usecase Description This seems to be the case that displays the list of products that
Richard sells to consumers along with the prices. A menu can also
include a list of offerings for customers and a table showing the pre-
established series of items.
Usecase3
Usecase Name Registration
Actors Customer
Usecase Description This seems to be the case that displays that when the user is new to
the system then the customer can register themselves to use that
system effectively. After registration, the confirmation box will be
appeared to confirm their registration to the system.
10

Full usecase description
Usecase Name Delivery Information
Scenario In the respective case scenario, this is stated that the customer will
order the product or item and the system will accept the request of the
customer and saved their selection and deliver their product on time.
The special instructions can also add by the customer if any. Then the
information related to the delivery is recorded by the online based
information system.
Trigger Event Concrete actions made by the user within the system to start the
usecase.
Actors Customer
Stakeholders Local store will deliver the product which is ordered by the customer.
Pre-conditions The system must be connected to the web or internet.
Post-conditions The delivery information will be appearing after the product is
delivered to the customer.
Flow of Activities The customer will order the product and the system will accept it, and
then after delivering the product, delivery information will be appeared.
Description This usecase will display the information and details regarding the
delivery of the product such as the delivery time, delivery product,
payment mode, etc.
11

Activity Diagram
Figure 2: Activity Diagram
Description - The above is the activity diagram, which seems to be a behavioral map that
describes a system’s behavior. A diagram of operation displays the flow of control from start
to end, illustrating the different decision routes that occur during the task. Another main UML
diagram to illustrate diverse facets of the structure is the operation diagram. The activity
diagram seems to be simply a diagrammatic representation describing the flow from activity
one to the next. The action can be defined as a machine process. The above activity diagram
shows the flow of control between the customer and online system, this shows that the
customer will login into the system and then view the menu of the product and then choose
12

and select the product as per their choice and the selection is set and saved by the system and
the product list is generated by the system (Rainer, et.al. 2020).
13

ERD
Figure 3: ERD
Description -A form of structural diagram to be used on the database architecture, recognized
as an ERD, ER or ER model. An ERD includes two main details visualizing various symbols
and conations. The major actors throughout the device field, as well as the connections
between them. The relations of entities set in what seems like a database can be found
through an entity relationship diagram. (ERD) An individual seems to be an object, a part of
data throughout this sense. A group of related entities seems to be a series of entities. Such
entities may have characteristics which define their properties. In the above diagram there are
various entities which are related to the information system and these are named as online
system and having various sub-categories such as delivery person, local store, customer,
vegetable, Richard farm, order and payment (Laudon and Laudon, 2017).
Along with this, the above ERD diagram is representing the different types of relationship
such as the NLA is having the aggregation relationship with the online information system.
The Various entities are having the many to many or one too many relationships with one
another.
14

Tables –
Entity Attribute Type Relationship
Delivery Person Delivery_id Int Not Null
Person_name String Not Null
Delivery_address String Not Null
Delivery_phone Int Primary Key
Delivery_customer_name string Not Null
Local Store Store_id Int Primary Key
Store_name String Not Null
Store_address String Not Null
Store_phone Int Primary Key
Member_account_info string Not Null
Entity Attribute Type Relationship
Vegetable Vegetable_id Int Primary Key
Description String Not Null
Availability String Not Null
Unit_price Int Not Null
Organic_certificate String Not Null
Customer Customer_id Int Primary Key
Status String Not Null
Address String Not Null
Phone number Int Not Null
Credit_purchase String Not Null
email String Not Null
15

16

Entity Attribute Type Relationship
Order Order_id Int Primary Key
Order_status String Not Null
List_of_vegetables String Not Null
Total_amount Int Not Null
Special_instrucitons String Not Null
Delivery_option String Not Null
Payment Payment_id Int Primary Key
Payment_account_name String Not Null
Payment_status String Not Null
Payment_amount Int Not Null
Invoice String Not Null
Entity Attribute Type Relationship
Richard’s Farm Farm_id Int Primary Key
Farm_name String Not Null
Farm_address String Not Null
Farm_phone Int Not Null
Farm_email String Not Null
NLA NLA_id Int Primary Key
Member_name String Not Null
Cash/EFTPOS_details String Not Null
Sales_credit_details String Not Null
Dails_sales_transaction String Not Null
17

18

Entity Attribute Type Relationship
Online System Login_id Int Primary Key
Password String Not Null
Status_regular/standard String Not Null
Customer_info String Not Null
Local_store_info String Not Null
Transaction_details String Not Null
Product_details String Not Null
Product_price Int Not Null
19

Sequence Diagram
Figure 4: Sequence Diagram
Description - A sequence diagram presents the time-sequence relationships between objects.
This displays the objects that are involved throughout the case as well as the communications
interchanged between objects that are necessary to execute the scenario functionality. UML
sequence graphs are relationship diagrams that describe the execution of operations.
Throughout the sense of communication they record the interaction among objects. Sequence
Diagrams are the subject of time as well as visually display the order of process by vertical
axis of diagram. The above sequence diagram of new information system is showing the
sequence between the Customer, online system and the database (Pearlson, Saunders and
Galletta, 2019).
Packages
The two packages which are shown in the above respective diagram is listed below –
Display List of Products – In this package, the system will display the products sold
by the 100% Organic Co. and then the customer can view all of the items and selected
as per their needs and then the item selected by the customer is saved and booked by
the respective system.
Select Product – The customer can select the product as per their choice. This is the
package which is generally used to select the select the product which is displayed by
the online information system (Campean and Yildirim, 2017).
20

Recommendations
Specific feedback around human resource needs at local media organizations will help
to ensure that there are appropriate resources working on-site, as well as those mobile
app modules can be trained (and managed).
Design and engineering are not necessarily subject to the same specifications as well
as schedules. It is important that information on specifications, deadlines as well as
priorities is shared or explained in advance while organizations are operating together.
Primary best practice, including the monitoring of source code as well as structural
bugs should be widely followed, and therefore not effective applications should be
regarded as basis of production organizations that neglect to use these. Allow use of
powerful systems as well as systematic approaches for software creation (DeLone and
McLean, 2016).
21

Conclusion
From the above report, this has been concluded that the entire report was based on 100%
organic co., which seems to be a highly growing enterprise throughout the agricultural sector
that wants to work more efficiently and to add brand-new operations to enterprise. At the
launch of business nearly all operations are manually executed. And this has to be improved
as the industry evolves, where consumers have the ease of buying products and workers in
the sector to function more easily with order fulfillment and interoperate separate farms
divisions for the advice to the organization of IT system. The above report has stated all the
things which are to be required for the analysis and design of the new information system.
The above report had included all the UML diagrams such as Usecase, sequence, ERD,
activity, etc. The functions as well as the recommendations are also addressed related to the
information system.
22

References
DeLone, W.H. and McLean, E.R., 2016. Information systems success
measurement. Foundations and Trends® in Information Systems, 2(1), pp.1-116.
Pearlson, K.E., Saunders, C.S. and Galletta, D.F., 2019. Managing and using information
systems: A strategic approach. John Wiley & Sons.
Laudon, K.C. and Laudon, J.P., 2017. Management information systems: Managing the
digital firm, global edition. Pearson.
Rainer, R.K., Prince, B., Splettstoesser-Hogeterp, I., Sanchez-Rodriguez, C. and Ebrahimi, S.,
2020. Introduction to information systems. John Wiley & Sons.
Stone, M., Aravopoulou, E., Gerardi, G., Todeva, E., Weinzierl, L., Laughlin, P. and Stott, R.,
2017. How platforms are transforming customer information management. The Bottom Line.
Torre, D., Labiche, Y., Genero, M. and Elaasar, M., 2018. A systematic identification of
consistency rules for UML diagrams. Journal of Systems and Software, 144, pp.121-142.
Fernández-Sáez, A.M., Genero, M., Caivano, D. and Chaudron, M.R., 2016. Does the level of
detail of UML diagrams affect the maintainability of source code?: a family of
experiments. Empirical Software Engineering, 21(1), pp.212-259.
Yang, J., Lee, Y., Gandhi, D. and Valli, S.G., 2017, August. Synchronized UML diagrams for
object-oriented program comprehension. In 2017 12th International Conference on Computer
Science and Education (ICCSE) (pp. 12-17). IEEE.
Campean, F. and Yildirim, U., 2017. Enhanced sequence diagram for function modelling of
complex systems. Procedia Cirp, 60, pp.273-278.
Arora, P.K. and Bhatia, R., 2018. Agent-based regression test case generation using class
diagram, use cases and activity diagram. Procedia Computer Science, 125, pp.747-753.
23