Systems Scenarios Using UML Diagrams Computer Science Essay

Published: Last Edited:

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

This chapter outlines the functional system and system requirements specification and describes the system's scenarios using UML diagrams (use cases, activity, class, and collaboration where appropriate). All the structure and design of the system will be design according to structure and the needs of M-Farm. The justifications and description about the system architecture solution and the design of each part of the system deployed.

4-1 Functional System and System Requirements Specification

Functional System defines what function does a system have or its component should perform. Functional System supported by System Requirements Specification that defines how the function performed. For example, System Requirements Specification imposed by quality requirements on the implementation or design.

4-2 Functional System Specification

The system provides network login username and password for the user to access M-Farm.

The system provides two type of accessing farm method, which is search by Graphical M-Farm and Numerical M-Farm.

User can access the farm condition based on the different node number, which deployed in the farm.

The system will list out all the farm condition, the status and advice given.

Action is taken listed when the farm condition having extreme climate change.

The system provides the graphical feature which enable user to see the farm condition through the camera deployed in the farm.

The system should provide the farm information.

User can retrieve information from database on mobile device using application installed.

User can access the farm using mobile device.

User can view date and time of each captured data.

4-3 System Requirement Specification

4-3-1 Efficiency Requirements

Type of speed


Response time

The system must respond directly after the user finish enters the network username and password in order to go into the system.

The system must respond directly after the user finish enters the node number of the sensor node.

The response time should not more than 5 seconds.

Refresh time

The refreshing rate must be fast after each change in the database done.

The refresh time is done every 5 seconds.

Processing time

The processing process must be fast so that the user no needs to wait so long time for the respond.

Table 4-3-T1: Efficiency Requirements

4-3-2 Applicability Requirement

The system is user friendly so that user does not take long time to learn how to use the system.

The system provides all the tickers, which will guide the user.

The system must be simple and equipped with the function needed.

The system can enable the user to connect to the Internet by accessing the farm anywhere and anytime to the farm condition.

The interface of the M-Farm kept as simple and neat as possible.

4-3-3 Security Requirement

The information of the farm condition can only change and updated by the administrator of the system.

Only the administrator can give the professional advice and action taken for the farmer to take immediate action for the farm.

The system must secure from unauthorized access, meaning that parts of the system should be available to users who has a valid network username and password.

The network login username and password, which are stored in database, cannot expose to others.

4-3-4 Reliability Requirement

The system must provide the most recently information regarding the farm condition to ensure the consistency of the result. The information will be updated, if the farm condition having climate change.

The system can update all the node number information which have climate change and the information will be updated from time to time when it is necessary

The rate of failure of the system is low as it can update the information from time to time

4-3-5 Robustness Requirement

Time to recover after the failure of the system will be around 1-2 minutes.

After that, the system can continue to operate as usual.

4-4 Unified Modeling Language (UML)

UML is a standardized general purpose modeling language in the field of software engineering. UML is a tool-supported modeling language, tools are readily available to support the application of the language to specify, visualize, construct, and document systems (Sinan, 2011).

There are some important diagrams are:

1. The Use Case Diagram: How the systems interact with the outside world/user

2. The Class Diagram: What objects do we need and how they be related

3. Activity Diagram: How the activities carried out

4. Collaboration Diagram: How the objects interact

4-4-1 Use Case Diagrams

Administrator is able to login the MySQL database named phpMyAdmin (PMA). PMA is a tool that will help to administer database. Administrator creates a database to view the data, insert, create and delete the database information. Figure 4-4-F1 shows the administrator node data use case.

Figure 4-4-F1: Administrator Node Data Use Case

Administrator is able to login the database PMA to view the users, add and delete username and password. Figure 4-4-F2 shows the administrator users use case.

Figure 4-4-F2: Administrator Users Use Case

Administrator is able to login the Web based FTP client (FTP server) to view the PHP information and the way the user select the information from the database. Figure 4-4-F3 shows the administrator web based FTP use case.

Figure 4-4-F3: Administrator Web based FTP Use Case

Web based FTP client system is the interface which can view by the administrator for the design and creation of the database table. It may link to mobile-based application for user to access the farm. Hence, the mobile can retrieve the information from the database as in Figure 4-4-F4.

Figure 4-4-F4: Web based FTP Client Use Case

Mobile Application System is able to interface with PHP and select the farm information from the PMA database. The design of the M-Farm is enable the user to login into the network, browse and search farm information in Figure 4-4-F5.

Figure 4-4-F5: Mobile Application System Use Case

4-4-2 Class Diagrams

The structures of the classes are the class of the java program for the JTWI of the mobile device project and the database entities are shown in Figure 4-4-F6.

The main program of the mobile application in the JTWI

Figure 4-4-F6: Main Program Class of the Mobile Application in the JTWI

The database entities in the PMA are shown in Figure 4-4-F7.

Figure 4-4-F7: Database Entities in the PMA

4-4-3 Activity Diagrams

1. Administrator Activity is shown in Figure 4-4-F8.

Figure 4-4-F8: Administrator Activity

2. Web based FTP client system is shown in Figure 4-4-F9.

Figure 4-4-F9: Web based FTP Client System

3. Mobile Application System is shown in Figure 4-4-F10.

Figure 4-4-F10: Mobile Application System

4-4-4 Collaboration Diagrams

User Login shown in Figure 4-4-F11.

Figure 4-4-F11: User Login Collaboration

Option selection for Numerical M-Farm and Graphical M-Farm shown in Figure 4-4-F12.

Figure 4-4-F12: Option Selection Collaboration

Administrator to access the database and the web server shown in Figure 4-4-F13.

Figure 4-4-F13: Admin Access Collaboration

4-5 Structure of the M-Farm System

The M-Farm mobile application based on the idea that farmers need to monitor the farm in anywhere and at anytime and provide a fast and accurate farm accessing system that can help the farmer.

4-5-1 Knowledge Base

The knowledge base also called as the memory of the information and it will match with the information in the database. It contains the domain knowledge which will provide the information for the farmer to access the farm data with the knowledge which representing the farm condition.

4-5-2 Database

The database is a storage, which includes a set of raw data, which used to match against the data (node number and the user information provided). This will enable the system to provide the correct information for the system during the farm accessing.

4-5-3 Advice Facilities

The facility is able to explain the system come with the status of the farm and the action taken if the farm is facing extreme climate change. The farm needs to give the advice and some information to the farmer.

4-5-4 User Interface

The user interface is the mechanism that the user and the system communicate. It is the interfaces where an end user seeks information about the farm condition by enter the farm login system and check the farm condition by entering the appropriate username and password and the node number into the system. This will enable the farmer to access the information regarding the farm at anywhere and anytime.

4-5-5 External Interface

The external interface allows the system to work with external data files and programs written in other languages. The system will communicate with PHP web server and PMA database.

4-6 M-Farm Architecture

In this part, there are some important topic such as knowledge representation and inner part design for "Accessing Your Farm Anywhere and Anytime (M-Farm)". The inner part of the program discussed in this part. Figure 4-6-F1 shows the architecture of M-Farm.


Sun Java Mobile


Login Using Network Username and Password

Select Options

Accessing the farm anywhere and anytime

Status and action to be take


Login (Users) Node Data





Figure 4-6-F1:

Architecture of "Accessing Your Farm Anywhere and Anytime (M-Farm)"

4-7 Farm Accessing Work Flow

Farm accessing is an important part in this system, M-Farm. The farmer will able accessing farm anywhere and anytime to access the farm condition, water level, temperature, humidity and observe the farm condition and the status of the farm is stated and action taken is given to the farmer as a reference to reduce the loss in the farm. The farmer needs to include the node number of the sensors which are deployed in the farm. With the information gathered, the system will return with result after the accessing. Work flow of Farm Accessing in Figure 4-7-F1.








Figure 4-7-F1: Work Flow of Farm Accessing

4-8 Explanation and Suggestions




Graphical M-Farm

Numerical M-Farm

Enter Node


Select Options


Allow Access


Enter Network Username and Password

Network Access

Verify Username and Password

Suitable output message

All the explanation and suggestions are given. The farm condition listed in the result and the suggestion given to the farmer. The detail includes the status of the farm and suggestions for the farm condition in Figure 4-8-F1.

Figure 4-8-F1:

"Accessing Your Farm Anywhere and Anytime (M-Farm)"

4-9 Overall Process Flow of the M-Farm


Knowledge acquisition

Choose Knowledge Representation Method

Put in the consideration of the farm condition

The design phase for M-Farm system will go through several stages, which begin with knowledge acquisition until the very last stage, maintenance. The Figure 4-9-F1 is showing the flow chart of design in M-Farm. Knowledge in an M-Farm system are derive from many sources, such as books, reading documents, case studies, databases and human experts which based on personal experiences. In this system, knowledge acquired from journals and several websites from Internet.

Testing OK?

Build User Interface




Figure 4-9-F1:

"Accessing Your Farm Anywhere and Anytime (M-Farm)" Testing

Figure 4-9-F1: Overall Process Flow of the M-Farm