Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
An overview of a sugarcane farming system, including details on the organization profile, requirement engineering process, menu tree for users and administrators, sequence diagrams, and various forms and reports related to the system. It covers topics such as requirement gathering, software requirements, user interface design, and administrative functionalities. A technical specification or design document for a software system supporting sugarcane farming operations. It includes detailed information on the system's features, workflows, and data management, making it a potentially valuable resource for students or professionals interested in agricultural technology, software engineering, or business process automation in the context of sugarcane farming.
Typology: Schemes and Mind Maps
1 / 74
This page cannot be seen from the preview
Don't miss anything!
CERTIFICATE
Place: Date: Guide Examiner H.O.D
Place: Date:
INDEX Sr.No Content Page No. 1
1.1 Introduction to project 1.2 Existing System 1.3 Need for System 1.4 Organization Profile 1.5 About Data 1 To 2 2
2.1 Objective 2.2 Requirement Engineering
3.1 Table Specifications (Design) 3.2 Menu Tree (Web Site Map) 3.3 DFD 3.4 ERD 3.5 UML Diagram 13 To 27 4
4.1 Admin side 4.2 User Side 4.3 Reports 28 To 44 5
5.1 User Manual 5.2 System Module
6
6.1 Limitations of the system
7
7.1. Future Enhancements
8
8.1. Conclusion
9
49 To 65 10
Bibliography
S ugarcane Farming System 1.4 Organization Profile: Factory Name: Deshbhakta Ratnappanna kumbhar panchganga S.S.k.Ltd,ichalakarnji, maharashatra. Operational Status: Working Code: 16201 GST Number: 27AADCS1728B1ZQ Plant Make: BW,TEXMACO. Factory Nature: PVT. Project Title: “Sugarcane Farming System” 1.5 About data: Access to project information is possible from anywhere and at any time through the Internet. Team communication, collaboration and decision-making is improved through the increased transparency in the management process. Handling of data is cost effective and not prone to errors and delays caused in duplication. Project management is controlled and systematic. Updated information on progress is available to all and shared as soon as it is available. The quality of project data is high and meets the real needs of the professionals involved, as a result of the timely transmission of information between designated parties, use of specified task specific formats, data accuracy and backup in well-defined and powerful database repository. Historic data for past projects is available for retrieval for new applications, such as for project maintenance needs, new project planning etc. Within in 90 days of its establishment, the task Force produced an extensive background report on the state of technology in India and an IT Action plan with 108 recommendations. The task force could act quickly because it built upon the experience and frustration of state government central government agencies, universities, and the software industry. Much of what it proposed was also consistent with the thinking and recommendation of international bodies like the World Trade Organization (WTO), International Telecommunication Union (ITU), and World Bank. In addition, the Task Force incorporated the experience of Singapore and other nations, which implemented similar programs. It was less a task of invention than of sparking action on a consensus that had already evolved within networking community and government. YSPM’S YTC, Faculty of MCA, Satara. 2
S ugarcane Farming System
2.1 Objectives: Fast service providing capability is most important application. Time saving Application. Reducing manual working. Increase efficiency. To meet with the requirement of fast changing world. To get actual and accurate knowledge of the sugarcane farming system. A very powerful MIS (Management Information System) can be built using the data captured in the system. The use of Google Maps leads to sufficient and efficient access to the total view of our Registered cane, harvested cane and remaining cane. To check each Gat officer of his Gat Status regarding registration, harvesting program etc. 2.2 Requirement Engineering: The process to gather the software requirements from client, analyse and document them is known as requirement engineering. The goal of requirement engineering is to develop and maintain sophisticated and descriptive ‘System Requirements Specification’ document. 2.2.1 Requirement Engineering Process: Requirement Gathering Software Requirement 2.2.1.1 Requirement Gathering: YSPM’S YTC, Faculty of MCA, Satara. 3
S ugarcane Farming System Format of Forms and GUI screen prints. Conditional and mathematical notations for DFDs etc. 2.3 Module- Admin (Sugar Industry) module User (Farmer module) Counsellor register Counsellor / without Counsellor Sugarcane Todni booking 2.3.1 Admin module Admin Admin module- Admin log Admin profile - sugar cane Counsellor register list Booking list. Search by Counsellor name village farmer code Booking approval in Counsellor Counsellor sugarcane generated by cane slip Sugarcane Weight slip list Counsellor sugarcane process active After generated by payment Counsellor Counsellor bank details Admin cane be sent in weight sugarcane details. And generated by payment bill 2.3.2 User module Farmer code After payment is weight cane slip Payment bill active 2.4 Requirements Analysis: 2.4.1Hardware Requirements: YSPM’S YTC, Faculty of MCA, Satara. 5
S ugarcane Farming System The System program uses the following hardware components. Processor : AMD Ryzen 3 RAM : 4GB Printer : HP and Canon Printer Hard Disk : 500GB Keyboard : Multimedia Keyboard Mouse : Optical Scroll Mouse and Compatible 2.4.2 Software Requirements: Operating system : Windows 7,8,10. Front End : Microsoft Visual Studio 2010 Back End : Microsoft SQL Server 2008 R Reporting Tool : RDLC Report for Visual Studio Web Server : IIS 2.5 Development tool used: 2.5.1 ASP.NET [Front End]: ASP.NET is a Web application framework developed and marketed by Microsoft to allow programmers to build dynamic Web sites, Web applications and Web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. 2.5.1.1 Characteristics: ASP.NET Web pages, known officially as Web Forms, are the main building block for application development. Web forms are contained in files with an ".aspx" extension; these files typically contain static (X) HTML markup, as well as markup defining server-side YSPM’S YTC, Faculty of MCA, Satara. 6
S ugarcane Farming System memory for subsequent requests. User controls have their own events which are handled during the life of ASP.NET requests. An event bubbling mechanism provides the ability to pass an event fired by a user control up to its containing page. Unlike an ASP.NET page, a user control cannot be requested independently; one of its containing pages is requested instead. 2.5.1.1.3Custom controls Programmers can also build custom controls for ASP.NET applications. Unlike user controls, these controls do not have an ASCX markup file, having all their code compiled into a dynamic link library (DLL) file. Such custom controls can be used across multiple Web applications and Visual Studio projects. 2.5.1.1.4Rendering technique ASP.NET uses a visited composites rendering technique. During compilation, the template (.aspx) file is compiled into initialization code which builds a control tree (the composite) representing the original template. Literal text goes into instances of the Literal control class, and server controls are represented by instances of a specific control class. The initialization code is combined with user-written code (usually by the assembly of multiple partial classes) and results in a class specific for the page. The page doubles as the root of the control tree. Actual requests for the page are processed through a number of steps. First, during the initialization steps, an instance of the page class is created and the initialization code is executed. This produces the initial control tree which is now typically manipulated by the methods of the page in the following steps. As each node in the tree is a control represented as an instance of a class, the code may change the tree structure as well as manipulate the properties/methods of the individual nodes. Finally, during the rendering step a visitor is used to visit every node in the tree, asking each node to render itself using the methods of the visitor. The resulting HTML output is sent to the client. After the request has been processed, the instance of the page class is discarded and with it the entire control tree. This is a source of confusion among novice ASP.NET programmers who rely on class instance members that are lost with every page request/response cycle. 2.5.1.1.6State management YSPM’S YTC, Faculty of MCA, Satara. 8
S ugarcane Farming System ASP.NET applications are hosted by a Web server and are accessed using the stateless HTTP protocol. As such, if an application uses stateful interaction, it has to implement state management on its own. ASP.NET provides various functions for state management. Conceptually, Microsoft treats "state" as GUI state. Problems may arise if an application needs to keep track of "data state"; for example, a finite-state machine which may be in a transient state between requests (lazy evaluation) or which takes a long time to initialize. State management in ASP.NET pages with authentication can make Web scraping difficult or impossible. 2.5.1.1.7Application Application state is held by a collection of shared user-defined variables. These are set and initialized when the Application OnStar event fires on the loading of the first instance of the application and are available until the last instance exits. Application state variables are accessed using the Applications collection, which provides a wrapper for the application state. Application state variables are identified by name. 2.5.1.1.8Session state Server-side session state is held by a collection of user-defined session variables that are persistent during a user session. These variables, accessed using the Session collection, are unique to each session instance. The variables can be set to be automatically destroyed after a defined time of inactivity even if the session does not end. Client-side user session is maintained by either a cookie or by encoding the session ID in the URL itself. ASP.NET supports three modes of persistence for server-side session variables. 2.5.1.1.9In-Process Mode The session variables are maintained within the ASP.NET process. This is the fastest way; however, in this mode the variables are destroyed when the ASP.NET process is recycled or shut down. 2.5.1.2ASP State Mode ASP.NET runs a separate Windows service that maintains the state variables. Because state management happens outside the ASP.NET process, and because the ASP.NET engine accesses data using .NET remoting, ASP State is slower than InProcess. This mode allows an ASP.NET application to be load-balanced and scaled across multiple YSPM’S YTC, Faculty of MCA, Satara. 9
S ugarcane Farming System ASP.NET offers a "Cache" object that is shared across the application and can also be used to store various objects. The "Cache" object holds the data only for a specified amount of time and is automatically cleaned after the session time-limit elapses. 2.5.1.4.1Other Other means of state management that are supported by ASP.NET are cookies, caching, and using the query string. 2.5.2 Back End 2.5.2.1SQL Server Management studio YSPM’S YTC, Faculty of MCA, Satara. 11
S ugarcane Farming System SQL server includes SQL server management studio, a new integrated suite of management tools with the functionality to develop & troubleshoot SQL server database as well as enhancement of previous functionality. 2.5.2.2Dedicated Administrator Connection SQL server provides a dedicated administrator connection that administrator can use access a running server even if the server is locked otherwise unavailable. This capacity enables administrator to troubleshoot problems on a server by executing diagnostic functions or transaction SQL statement. 2.5.2.2.1Hosted Common Language Runtime With SQL server, developers can create database object using familiar languages such as Microsoft Visual C#.Net & Microsoft ASP.Net. Developers can also create two objects user defined types & aggregates. 2.5.2.2.2Native XML Supports Native XML data can be stored, queried & indexed in SQL server database allowing developers to build new classes of connected applications around web services and across any platform or device. 2.5.2.2.3Security Enhancement The security model in SQL Server 2008 separates users from objects, provides fine-grain access, and enables greater control of data access. Additionally, all system tables are implemented as views, providing more control over database system objects. 2.5.2.3Web Services With SQL server developers can develop Web Server a hypertext transfer protocol (HTTP) listener & providing a new type of data access capability for Web services center application.
3.1 Table Specifications (Design) YSPM’S YTC, Faculty of MCA, Satara. 12
