Cattle Management System: A Case of Pakistan

The aim of the project is to provide various services to the buyers like they can select the cattle of their choice to buy or also they can sell any of their cattle on the website at the desirable selling price. Cattle Management System is a web based application that allows the administrator to handle all the activities online like selling and purchasing of various animals by the needful people quickly and safely. Using Interactive GUI anyone can quickly learn to use the complete system. Using this, the administrator doesn’t have to sit and manage the entire activities on paper and at the same time, the head will feel comfortable to keep check of the whole system just with the availability of internet. This system will give him power and flexibility to manage the entire system from the single online portal.


Introduction
The purpose of the document is to collect and analyze all assorted ideas that have come up to define the system, its requirements with respect to users. The aim of the project is to provide various services to the buyers like he can select the cattle of their choice to buy or also they can sell any of their cattle on the website at the desirable selling price [1].
The current system is offline system. So this current system is very difficult because its time consuming. So our project aims at creating a web application which tracks cattle records, online purchasing, online selling etc [2].

Objectives
1. The system should have a user registration process in order to get login into the system. 2. The system should have a administrator login page . 3. The system will show cattle which available on web. 4. Administrator can display the request of user successful.

Technical Feasibility
Technically, this project is very feasible because of use of current and latest techniques. I have already done this type of projects using latest technologies like making front end in the bootstrap, Html 5, CSS 3, java script and JQuery and backend development will be done in very efficient tool MySQL database. So this project is technically feasible.

Existing System: Data Analysis Objectives
• To document the physical existing current system. • Helps to determine who the users are • Ensures that no functionality is inadvertently omitted • Indicates areas potentially impacted by the introduction of a new system • Helps users become comfortable working with DFD's since their terminology and concepts • Is a tangible demonstration to users of the analyst's understanding of the existing environment • When documented competently, helps to increase the users' confidence it the analyst and, consequently, in the project.

Responsibilities
• Identify the files, which represent the existing data entities, and the Data Flows (inputs and outputs), which represent the physical User Views of the existing system. These should be used to produce a rough Data Model of the data used by the existing system.

Working Documents • Physical Existing Data Flow Diagrams Function Charts (hierarchical representation of system processes) • Preliminary (Current/Existing) Logical Data Flow Diagrams Tools
Only use these tools if the DFD's will be presented to the users, otherwise hand-drawn diagrams are sufficient. A lot of effort is required to draw a DFD regardless of the tool used. However, automated tools make it possible to make changes to DFD's more quickly. Analysts should assume that changes will be made since drawing DFD's is still somewhat of an art, and analysis is an iterative process [4].

Deliverables
Function Charts Data Model of physical existing data usage. Physical Data Flow Diagram of the existing system. Preliminary logical Data Flow Diagrams of the existing system.

Variations
Although data gathering and the production of Function Charts and DFD's are presented here as separate tasks in chronological order, they in fact occur concurrently. Analysts draw DFD's as they are collecting data, and return to gather more data as they are drawing DFD's.

Data Flow Diagrams (DFDs)
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information system, modeling its process aspects. A DFD is often used as a preliminary step to create an overview of the system, which can later be elaborated. DFDs can also be used for the visualization of data processing (structured design). Data flow diagrams are also known as bubble charts. DFD is a designing tool used in the top-down approach to Systems Design. This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the detail of the system being modeled. The Level 1 DFD shows how the system is divided into sub-systems (processes), each of which deals with one or more of the data flows to or from an external agent, and which 23 together provide all of the functionality of the system as a whole. It also identifies internal data stores that must be present in order for the system to do its job, and shows the flow of data between the various parts of the system [5].  24 developed and the specific practices of the organization(s) involved. These may include: 1. Requirements inception or requirements elicitation 2. Requirements identification -identifying new requirements 3. Requirements analysis and negotiation -checking requirements and resolving stakeholder conflicts 4. Requirements specification (e.g., software requirements specification; SRS) -documenting the requirements in a requirements document 5. Systems modeling -deriving models of the system, often using a notation such as the Unified Modeling Language (UML) or the Lifecycle Modeling Language (LML) 6. Requirements validation -checking that the documented requirements and models are consistent and meet stakeholder needs 7. Requirements management -managing changes to the requirements as the system is developed and put into use These are sometimes presented as chronological stages although, in practice, there is considerable interleaving of these activities.

Use Case Diagram
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted. The main purpose of a use case diagram is to show what system functions are performed for which actor. Roles of the actors in the system can be depicted.

Admin Side
As this application is actor based so the site plan is according to the roles of the actors.
1. Admin Login 2. Edit Cattle Details.  Table: All database tables that I used in my project details are following

Test Results
Fallowing results has been shown:

Conclusion
The Cattle Management system is concerned with enhanced, secure and authorized availability of Ghazi Farm with the fully utilization of the internet (online connectivity) and combined talent and skills do entire workforce of the Farm. Ghazi Farm system must today reinvent itself to cope with the demands of a global economy. In which buyer purchase the cattle but also the facility that is seller can also sale their cattle here.