Reference no: EM133413466

Assignment - Smart Farm Project Hardware Stream

Project Topic: Smart Farm

Background
So far in the 20th era a lot of research has been initiated in the multi-disciplinary field of "smart cities" (Fig. 1). The smart city concept tries to create a research platform for scientists to investigate and share ideas about how to manage our ever-growing cities in the future. Around 70% of earth's population will be receding in major cities within the year 2050 [1]. This concern requires attention because the way our cities are structured currently is not sustainable enough to handle the load that the increase in population will pose. Therefore, research regarding smart cites has been conducted heavily, and it can be recognized as research using new technology and optimization in conjunction with the concept of internet of things and WSN to create an intelligent management systems for the future cities to handle the incoming strain.

In this project, you will work on a subsystem of the smart city concept, namely smart agriculture (Fig. 2 and Fig. 3). Smart Farming represents the application of modern Information and Communication Technologies (ICT) into agriculture. A smart farm is a farm that may use concepts such as IoT, WSN, and optimization. Smart agriculture helps in automated farming, collection of data from the field and then analyses it so that the farmer can make accurate decision in order to grow high quality crop.... Smart Farming has a real potential to deliver a more productive and sustainable agricultural production, based on a more preciseand resource-efficient approach.

WSN project aims to .....

Use of IoT and WSN technologies in smart farm is becoming increasingly popular in the followings:

• Soil quality monitoring; controlling water usage for optimal plant growth, determining custom fertilizer profiles based on soil chemistry (Fig. 3). Typical solutions involve monitoring of the soil minerals, moisture, PH. Soil sensing can be performed using a variety of sensors (water, gas, temp, etc) connect to a microcontroller and sending data into the cloud (could use Elastic or Azure for visualization), and possibly actuation (either send an email to notify an event or enable some lights on a separate microcontroller as notification).
• Crop maturity; determining the optimal time to plant and harvest.
• Animals monitoring; livestock sensors can notify ranchers when animals have roamed from the herd so that ranch hands can round them up. Animals monitoring can be used to identify sick animals so they can be pulled from the herd, preventing the spread ofdisease.
• Reporting weather conditions.
• Farm facility and equipment monitoring; check if pumps are actually running,

A WSN-based solution should support upload/download of data to the cloud, farm server/web site and/or smart phone.

Architectural Models and Typical Configuration Organisation
For all Assignments, students are expected to form teams of three or four in order to create a basic prototype for smart farm monitoring and management system that involves sensors, actuators and control devices that are safely placed on the animals' body, plants, the farm equipment, in the soil, .... In order to test its functionality, a demonstration shall be held on last day/session of 49227 WSN in Autumn 2022. A practical exam/demo shall be conducted based on the outcome of the demonstration. Further details for this shall be provided closer to the due date. The design and implementation technique is entirely up to the development team; however it is necessary to justify any design decisions made.

Assignment Deliverables:

The task involves teamwork and aims to provide the main project development package that includes a set of final requirements and design documentation which includes the following:
• The Architecture/High Level and Low Level Designs;
• Test/integration plans; and any documentation related to implementation for the assigned project and a Team presentation which includes a discussion on the deliverable plus its conformance to the major functional abstractions/components identified.
The assignment should be completed by the cooperating small teams (of approximately 3-4 students) and integrated by the Team as a seamless Team deliverable. Project Teams should provide WSN Architecture/Design and possibly a mock-up for UI. Consideration should be given to use of Open Source hardware/software and COTS components (hardware toolkits, IDEs, frameworks, DBMS, libraries, and middleware, test tools, etc.). Students should comment on design constraints and possible limitations of the technology.

The initial phase of this project consists of two main parts:

Part 1: Project Scope
The main purpose of this part is to scope the problem

Principles underlying the project's scope should include, but not necessarily in this order:
• The what - A demonstration to the customer that the project problem is well understood and what shall be the final deliverable.
• The how - A proper, realisable schedule for achieving the project, how the budget is to be managed and spent, the project approach and methodology, etc.
• The when - A discussion of milestones and what is the outcome of those milestones.
• The who - Discussion on participants, how they are organised, any re-structuring issues, etc. You might include a discussion on the resources you intend to use such as CASE tools, COTs, platforms, customer supplied resources, etc.

Part 2: Selection of Sensor /Actuator Technology
The second part focuses on the rationale behind the choice of your sensor(s)/actuators(s).
Typically this part of the report would include:
• What is your selected sensor or set of sensors and application?
• Elaborate what the selected sensor (s) supposed to do in WSN-based application
• Discuss range of input and output (for example input in degC output in microV... etc.)
• Elaborate on linearization issues
• Discuss what is the accuracy/stability desired (i.e., over what range is this accuracy or stability required?
• Discuss what sensitivity is required
• Describe what is the impedance at the output
• Comment on the error sources in the transducer, single ended output, differential output, noise considerations, offsetting required?
• Supplementary data sheets
• Typical applications
• Other comments?

It is assumed the project documentation deliverable will be divided into the following sections and appendices and be handed in a pdf file form. The pdf file should contain page dividers. Dividers should separate each appendix. The first portion of the deliverable shall contain a "road map" that accurately defines the layout of the deliverable and which section/appendix/portion is contained behind each divider.

The deliverable document can be tailored as follows (not all sections are required):

Section 1 Introduction and Scope of the project- light version
Aims to explain the problem, its context and provide an overview of the project and would include a "roadmap" / table of content.

Section 2 System Requirements Specification - light version
• Paragraph (s) defining the team's understanding of the assigned problem relevant to the SRS, supported by a context or boundary diagram and complete with explanatory text. The diagram should include: operational processes (sub-systems/components) and control/data connectivity. This has to be consistent with the development methodology, which must be strictly applied.

• Presentation of requirements categorised into functional, non-functional, performance, behavioural and designconstraints.
• Analysis including diagrams and one formal method representative of the methodology expressed for the project.
• Test/validation components, including degree of planned testing and classes of the test.

Section 3 Architecture / Design (Models, Views, Simulation, Mock-up UIs)
• Paragraph (s) defining the team's understanding of the assigned problem supported by a context or boundary diagram, complete with explanatory text, strictly for architecture purposes. This has to be consistent with the development methodology, which must be strictly applied.
• System's/Architectural model semantics.
• There shall be depictions (graphs, tables, descriptions, etc.) of how the requirements are being "mapped" to the various subsystems, components, etc. The requirements must be directly derived from the SRS, validation/traceability matrix.

Section 4 Project Plan(s)
System Development Plan (SDP).
• SDP semantics.
• Typically the plan should cover, but not be limited to:
o SDP Scope and objective;
o Team Organisation and Managerial Approach;
o Work Breakdown Structure - WBS;
o Schedule
o Roles and Responsibilities structure;
o Time estimation issues;
o Cost estimation and budgeting; and
o Critical Risk Identification plus mitigation strategies.

System Test/Integration Plan (STP).
• STP semantics.
• The plan should cover, but not be limited to:
o Testing approaches and criteria;
o Scheduling approaches;
o Resources and Manpower;
o Managerial issues;
o Responsibilities;
o Discrimination between Low Level, Integration and Validation testing, etc.
• Pro-forma validation testing report, including separate pages describing each and every test/group of tests.
• Make provisions for subsystem/system integration tests and the final acceptance tests (i.e FQT)

System Quality Assurance Plan (SQAP).
• SQAP semantics.
• The plan should cover, but not be limited to:
o Process and Product Quality issues and measurement criteria;

o Managerial Approach and procedures for assuring the quality of the process and the product;
o Policy issues, including the definitions of Risk, Configuration Management, Defect Management, Change Control, Critical event handling, etc.

Section 5 Conclusion.
• This section should be structured but not be limited to:
o Summary - Summary of your findings.
Section 6 Appendices.
• Administration records - including minutes of meetings, action sheets, review results, walkthrough
• Other Appendices - containing any other information regarded as relevant i.e. Bibliography.

Attachment:- Smart Farm Project Hardware Stream.rar