KEMBAR78
C++ Assignment | PDF | Databases | Interface (Computing)
0% found this document useful (0 votes)
59 views4 pages

C++ Assignment

Uploaded by

Monster Rider
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
59 views4 pages

C++ Assignment

Uploaded by

Monster Rider
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Project Journal: Farmer Assistance Interface

Project Overview
Objective: Build an interface for a foundation to provide underprivileged farmers with
essential information on pesticides, weather, and low-cost equipment rentals. The platform
aims to improve crop production and resource management.

Milestone 2: Requirements Identification


Date: November 1, 2024
Time: 14:00 to 16:00
Session Goals: Outline project requirements, determine core functionalities, and research
similar apps.

Activity Log:
14:00: Defined project focus areas (weather, pesticides, equipment lending).
14:30: Created initial list of core features:
Weather Information: Display local forecasts, warnings, and crop suitability.
Pesticide Guidance: Provide info on pesticide types, safety, and costs.
Equipment Lending: Search and booking for low-cost farming equipment.
15:00: Researched apps with similar features (Farm Rise, Kisan Suvidha).
Noted design elements that support low literacy levels.
Found a simple icon-based approach for nonliterate users.
15:30: Documented findings and outlined a potential tech stack.
Backend: SQLite for simplicity.
Frontend: C++/Qt for interface design.

Search/AI Queries Used:


Searched for "apps for farmers India" to study similar applications.
Used ChatGPT to help identify simple design features for low literacy users.

Summary of Session:
Outlined main features and identified basic user needs. Noted design elements for low
literacy, including icon usage and minimal text.

Next Steps:
Break down each core functionality into specific requirements.
Begin sketching interface ideas for intuitive design.

Date: November 3, 2024


Time: 13:00 15:30
Session Goals: Identify technical and user requirements, refine core functionalities.

Activity Log:
13:00: Detailed technical requirements for each core feature.
Weather Module: Requires reliable weather API.
Pesticide Info: Create a simple database for pesticide information.
Equipment Rental: Implement a basic search and booking system.
13:45: Specified user requirements:
Minimalistic design with icons.
Offline access feature for remote regions (database sync when online).
14:15: Noted challenges:
Ensuring interface is mobile friendly.
Managing offline data sync.
14:45: Documented technical requirements in project journal.

Search/AI Queries Used:


Looked up "best weather APIs for farmers".
Used ChatGPT to suggest data sync methods for offline access.

Summary of Session:
Established a clear set of technical and user requirements, finalized core features, and
documented constraints.

Next Steps:
Start sketching wireframes for the interface.
Explore potential APIs for weather and database options for offline functionality.

Date: November 9, 2024


Time: 10:00 12:30
Session Goals: Finalize requirement documentation and review progress for Milestone 2.

Activity Log:
10:00: Reviewed requirements and functionalities for each module.
10:30: Finalized project documentation for Milestone 2.
11:00: Updated project journal, including detailed notes on progress and challenges.
11:30: Prepared a summary of tool usage and searches for project submission.

Search/AI Queries Used:


No new queries for this session.

Summary of Session:
Reviewed and finalized requirements documentation for submission. Documented project
choices and completed journal entries.

Next Steps:
Submit the Milestone 2 report.
Begin planning for Milestone 3, focusing on initial implementation.

You might also like