To build a system through which the user can apply for local group registration, the user can apply for membership in the local group. The County Council user must enter key field training details; the County Council user must set weekly attendance details, verify local group and local group member ship. The system should have the provision for the Farmer to be able to make an application to the local PGS group.
The system must have a provision so that the RC can verify the farmer's entry application to the PGS local group. The system must be able to enter the information for registering the local group with the regional council. The system must be able to enter the information for approval by the local group with the regional council.
The system must have the ability to verify the information entered for registration of the local group with the regional council. The system must have the ability to enter group information on the worksheet for certification of the local group.
Screen Elements Application Form Annexure 1
DEFINITION
DATA
- Screen Interface Annexure I
- Output for annexure I:-
- Process Flow Registration to Local Group:-
- FR 1.2 Farm history
- Screen Elements Farm History DEFINITION DEFINITION
- Screen Interface Annexure II-farm history
- Output for Annexure II-farm history
- Process Flow Farm History
- Verification of Farmer to PGS local Group
The farmer fills in the following to form the season: - o The farmer selects the season. The farmer must enter the following information for livestock for one year: - o The farmer must enter the name of the livestock. The farmer must enter the information contamination control. o The farmer must enter the buffer zone information.
If the farmer has offered the whole farm, the farmer must upload the plan for converting the farm into a whole farm for organic farming.
Access to: - Regional Council
Screen Element -Verification DEFINITION
Screen Interface- Verification
Process Flow Verification
Organic Farmer Pledge
- Screen Interface-Organic Pledge
- Output for Organic Pledge
- Process Flow Organic Pledge
- FR 1.5 Key field day training
- Screen Interface-Key Field Day
- S CREEN E LEMENTS K EY FIELD DAY T RAINING
- OUTPUT format key field training
- Process Flow Key FIELD DAY Training:-
- FR 1.6 Weekly Attendance
- Screen Interface-Weekly Attendance
- Output Format –Weekly Attendance
- Screen Element Attendance Register DEFINITION
- Process Flow Attendance Register
The system should display the organic pledge with the farmer's name, surname, village name, district name. The system will also display the day, month, year. But the farmer will have an option to change the date value. This is used by the County Council to enter information about key field training.
The District Council user must enter the name of the member who was present at the training. Key field training information is recorded in Appendix V and stored in the system. The district council will enter the proceedings of the weekly meeting and register the attendance register.
The regional council user will be able to enter the number of local group members present 4. The regional council user must enter the date and time of the weekly meeting. The Regional Council's user must enter the important topics that are discussed and planned.
The regional council chooses the name of the member who attends the weekly meetings. The Regional Council user saves the weekly meeting information and records the information regarding attendance. This will be used by the Regional Council to record information with the weekly attendance record DATA.
Information for Peer Inspection/Appraisal Worksheet
- Screen Interface for Peer Inspection/Appraisal Worksheet
- Screen Elements – Peer Inspection/Appraisal Worksheet DEFINITION
- Output for Peer Inspection/Appraisal Worksheet
- Process Flow Peer Review for Season:-
Are you satisfied that adequate measures have been taken to prevent pollution from water flow? Are you satisfied that veterinary medicines meet PGS standards and have only been administered. Are you satisfied that all requirements for animal production have been met according to PGS standards.
Information for peer inspection/Appraisal worksheet for processing and handling
- Screen Elements for peer inspection/appraisal worksheet for processing and handling
Are you satisfied that no prohibited substances have been used in the treatment o The local member group must enter information on Are you fully satisfied that the treatment. The local group member must enter the production information as follows: o The local group member must select the type of finished product. SRS PGS Draft V0.01 Page 53 3.7.8 Input screen format for peer inspection/assessment worksheet for processing and handling.
This screen will be used to enter the values related to the peer inspection/assessment sheet for processing and handling.
SCREEN
Process Flow Peer Inspection/Appraisal worksheet for processing and handling
Local Group registration
- Screen Interface – LOCAL group registration
- Screen Element for Annexure X DEFINITION
- Output for Annexure X
- Process Flow Local Group Registration:-
- FR 2.0 ENDORSEMENT OF LOCAL GROUP:-
- Screen Interface Endorsement:-
- Screen Elements- Endorsement DEFINITION
- Output of Endorsement
- Process Flow Endorsement:-
This screen will be used to enter the values related to the registration of the local group in the regional council. The regional council user must sign the information on the application for registration of a local group with the regional council. Is the approved group/agency satisfied that the group is competent enough to implement the PGS-India program as per the guidelines.
Is the group/supporting agency satisfied that the group constitution meets the requirements of the PGS-India program and members are entrusted with proven commitment to organics. Is the support group/agency satisfied that at least a few members of the group are fully aware of PGS standards, operational requirements and can undertake peer reviews.
Verify Local group
- Screen Interface –Verification:-
- Screen Element-Verification DEFINITION
- Process Flow -Verify Local Group:-
The system will provide for the following screen data elements Screen Element Screen Element Data.
Local Group Summary Worksheet:-
- Screen Interface for Local Group Summary Work Sheet (Annexure IX):-
- Screen Element ANNEXURE IX DEFINITION
- Output for Local Group Summary Work Sheet:-
- Process Flow Work Sheet:-
- FR 2.3 Certification
- Input Screen Interface Certification:-
- Screen Element Certification:- DEFINITION DEFINITION
- Output Certification:-
- Process Flow Certification
- FR 2.3 Agreement
- Input Screen Interface Agreement:-
- Screen Element for Agreement DEFINITION
- Output Format for Annexure XI
- Process Flow Agreement:-
- Non-Compliance Guidelines-Catalogue of sanctions
The regional council user selects the local group from the list of local groups to be certified. 3. The regional council user must enter regional council witness details and local group witness information. Describe the information stored in this entity and how it will be used.
TITLE Annexure VIII
CONTENTS
FREQUENCY
- User Characteristics
- Constraints
- Assumptions and Dependencies
- S PECIFIC R EQUIREMENTS
- External Interface Requirements
- Performance Requirements
- Design Constraints
- Software System Attributes
- Logical Database Requirements
- Other Requirements
This subsection of the SRS should provide a general description of any other items that limit the developer's options. These factors are not design limitations, but areas where future changes may lead to changes in requirements. This section should describe all software requirements at a sufficient level of detail so that designers can design a system that meets the requirements, and so that testers can verify that the system meets the requirements.
At a minimum, these requirements must describe each input to the software, each output from the software, and each function performed by the software in response to an input or in support of an output. The remainder of this sample document is organized according to A.5 Template of SRS Section 3 Organized according to Feature shown in the Schedule of Std 830-1998. This section should complement the interface descriptions under section 2.1 and should not repeat information there.
Determine static and dynamic numerical requirements for software or human interaction with software. Static numerical requirements may include the number of terminals supported, the number of concurrent users to be supported, and the amount and type of information to be handled. Dynamic numerical requirements can include the number of transactions and tasks and the amount of data to be processed over a period of time for normal and peak workloads.
The following items provide a partial list of system characteristics that may serve as requirements to be objectively verified. Specify the factors that will protect the software against accidental or malicious access, misuse or modification. Requirements should not be placed here simply because they are considered good design practice.
Specify software attributes related to the ease of transferring the software to other host machines and/or operating systems.
