E farming - Tgmc Project Started

The Great Mind Challenge - Project Scenario Template

Team Members

         Mohammed Tabraiz Ali

         Mohammed Yaser

         Ibadur Rahman

1.	Name of the Project	e- Farming
2.	Objective/ Vision	The main objective of this project is build a website which will help farmers from Indian villages too sell their products to different cities. Here if suppose some village farmers want to use this facility and want to learn how is it possible and how they can use e-farming to sell their products,  If they have knowledge of computer then they can directly register in the site and sell their product otherwise they can contact company's computer professional who will schedule classes to teach them basics of computers and internet like how they can open this site and register with  it and sell their products online etc. On the other side, wholesaler from town can also register and buy products as per their needs.
1.	Users of the System	i.   Director – Admin ii. Users – Farmers, wholesaler who wants to buy product directly from Farmers iii.      Computer professionals iv.        any other users
3.	Functional Requirements (Atleast Eight)	i.People can register in the site for some basic e learning like if some user wants to learn how to operate computer, they can go and learn it from the site. (It will be just HTML page with all basic courses on how to operate computer).            ii.Site should also be available in Hindi and local languages as per States.          iii.While registering there should be option of selecting whether one who is registering is farmer or wholesaler •     If user select as farmer then there should be option to   select whether he wants to take lesson or if he is already familiar with online buying and selling then he can directly go to sell his products. •     If user select as wholesaler then he needs to fill all details as per  requirement – place, shop address, which product he wants to buy, quantity etc. v.   Admin should be able to see all record from any users. vi.      The records shown for selling should be available in a format of Quantity name , Quantity available, price. vii.     The database should be robust enough to handle all the online transactions which will be happening parallely. viii.  The data should be stored inside database such that when queried with different parameters the query should retrieve the results quickly , for example – there should be in build query for farmers to view what all products they are selling and how many have been sold + the quantity left. Another query must be there for wholesaler to query for products and also drill down the results in the result page to view how much quantity of that product is available with single farmer in case they are interested in single lot. ix.       There should be facility of scheduling classes for farmers who enrolled for basic courses. x.   Automatic transfer of mails to company's computer professional(teachers) if some user(farmer) enrolled for basic course.
1.	Non-functional requirements (Atleast Four)	i. Secure access of confidential data (user’s details). SSL can be used.            ii. 24 X 7 availability          iii.Better component design to get better performance at peak time          iv.Flexible service based architecture will be highly desirable for future extension
4.	Optional features	11   1. Available in English and Hindi language        3. Contextual error-correction. 4. Browser testing and support for IE, Mozila, and Firefox.
5.	User interface priorities	A. Professional look and feel B. Use of AJAX atleast with all registration forms C. Browser testing and support for IE, NN, Mozila, and Firefox. D. Use of Graphical tool like JASPER to show strategic data to admin E. Reports exportable in .XLS, .PDF or any other desirable format
6.	Reports	i.   Daily report of enrollment to Admin. ii. Monthly report of enrollment as per states to Admin iii.      Work hours uses of Computer professionals on a monthly basis to Admin
7.	Other important issues	None
8.	Team Size		2 – 4 members
9.	Technologies to be used		UML, J2EE, XML, e-Forms, AJAX, Web 2.0, Web-services, SOA
10.	Tools to be Used		·         ROSE/RSA / WebSphere Modeler ·         Eclipse/ RAD / Lotus Forms Designer / Portlet Factory ·         WebSphere Portal/ WAS/ WAS CE / WPS ·         DB2 Express – ‘C’ or DB2 UDB ·         Tivoli CDP/TSM / Tivoli Directory Server ·         Linux will be the preferred OS.
11.	Final Deliverable must include		A. Online or offline help to above said users, Application deployment executive and developer B. Application archive ( .war/.ear ) with source code C. Database backup and DDL Script D. Complete Source code
12.	Advantages of using XML		I.              Because of the use of XForms which generate XML data as input, its easy to consume (gather) all user information in a single XML document and store it as a single entity without breaking it up into pieces as done is case of relational database. II.             Since the data will be stored in a single XML document, its easy to fetch it using a simple XQuery without any complex joins III.            Since the data is stored as XML, it is very easy to construct SOAP messages from this XML content as no relational to XML transformation is required. IV.            Use of XSLT to report data in multiple format is now possible because of the XML data model. V.             XML Indexes can be used to further increase the XQUERY performance.