The document presents an e-recipe management project aimed at providing users with a platform to search for recipes and manage their cooking needs efficiently. Key functionalities include user registration, product ordering, and recipe downloading, alongside an administrator interface for product management. The project outlines its objectives, technological requirements, testing modules, and future enhancements to improve user interaction and security.

1. E-RECIPE MANAGMENT
• Project Mentor
Prof. Sudakshina Dasgupta
• Presented by-
 Amit Kumar Saha
 Kanak Barman
 Keya Roy Dakua
 Subrata Mahata
 Sudip Mondal
 Sumanta Mete

2. CONTENTS
• Overview of the project
• Objectives
• Software interface and Hardware interface
• Functional Requirements
• Data-Flow-Diagram
• E-R Diagram
• Require Table – Structure
• Snapshots of project
• Testing
• Future Scope
• Conclusion and References

3. OVERVIEW OF THE PROJECT
• An E-commerce application, a web site where users can search their
desired recipes along with proper manual and ingredients.
Depending on the context, it’s been names as ‘G.C.E.T.T.S.
SHOP.com ’.
• The visitors will be able to sign up for an account to stay more up-
to-date about the site development and new recipes and get their
desire ingredient of recipes in quick time.
• A customer get his quick view on particular recipes to make a
easy decision on a product.
• Customers will be provided with very good quality cookers if they
need to have for festival arrangements.
• Users will be given an enabled option for downloading the recipes
for a step by step guidance.

4. OBJECTIVE
 Efficiency – one of the promises of e-recipe management system to increase
efficiency in custom recipe making, user manualing ,detail view of recipes .
 Enabling information exchange and communication in standardized way between
administrator and product or ingredient gainer give secure and safe use of
system.
 Extending the scope of recipe making in more innovative and convenient way
beyond its conventional boundaries. This is meant in conceptual sense e-recipe
management system enables consumers to easily obtain custom recipe making
along with festive mode budgeting online from global providers.
 In addition to these, it is easy to use along with the guidelines provided by
administrators.

5. SOFTWARE AND HARDWARE INTERFACE
SOFTWARE INTERFACE
• XMAPP
• Windows XP or above OS
• Web Browser like Microsoft
Internet Explorer, Mozilla
Firefox etc.
HARDWARE INTERFACE
• Intel Pentium IV or more
• At least 2 GB RAM
• 10 GB hard disk or more

6. FUNCTIONAL REQUIREMENTSFUNCTIONAL REQUIREMENTS
Here we have two majored section of use.
A) administrator B) customer
• Administrator activities
• Administrator can insert new
product.
• Administrator can update
product details.
• Administrator can delete old
product details.
• Administrator can view
transaction details.
Customer activities
•Customer can register to buy a product.
•Customer can login to buy a product.
•Customer can purchase a product.
•Customer can cancel order.
•Customer can track their order.
•Customer can get quick view of products.
•Customer can download recipes.

7. DFD - CONTEXT DIAGRAM

8. DFD – LEVEL 1 OF ADMIN

9. DFD – LEVEL 1 OF CUSTOMER

10. ENTITY RELATIONSHIP DIAGRAMENTITY RELATIONSHIP DIAGRAM

11. REQUIRED TABLE STRUCTURE

12. REQUIRED TABLE STRUCTURE

13. REQUIRED TABLE STRUCTURE

14. REQUIRED TABLE STRUCTURE

15. SOME SNAPSHOTS OF
G.C.E.T.T.S. SHOP.com

16. REGISTRATION PAGE

17. CUSTOMER ADDRESS

18. LOGIN PAGE

19. VIEW PRODUCTS

20. VIEW PRODUCTS

21. VIEW PRODUCTS

22. QUICK VIEW

23. ORDER PROCESS

24. ORDER PLACE

25. OREDR TRACKING

26. TESTING
MODULES TO BE TESTED INPUT TESTCONDITIONS OUTPUT
CUSTOMER_LOGIN FORM CUSTOMER EMAIL ID ,
password
Whether CUSTOMER EMAIL ID and
the corresponding password are
consistent with the database
Logging into
CUSTOMER
account
REGISTER CUSTOMER EMAIL_ID,
Name , password, PHONE
no., Address
Whether the Email id is valid
and if it is already exists or not
Whether two occurrences of
password having length
between 6-12 are identical
Whether the name consists of
single word(only alphabets)
with minimum length of three
Above all, no field should be
vacant
A confirmation
message is
delivered to
corresponding
page and a new
account is
created

27. TESTING
MODULES TO BE TESTED
MODULES TO BE TESTED
MODULES TO BE
TESTED
INPUT TESTCONDITIONS OUTPUT
BUY Quantity Fields should not be
blank and must be
number.
Order is placed
Track Order id It is checked if field is
left blank.
Order status
is generated

28. FUTURE SCOPE
•The interaction procedure of user and the online
application can be further more improved to make it
interactive and user friendly .
•One of the major problem, currently we can not provide
online transaction .
•we are trying to upgrade it into a advanced cryptography
secured system with convenient interface so that more
users can be attracted .We think more flexibility and
interactive features can make it more bigger.

29. CONCLUSION
After developing the application we have got a clear idea on how to
develop an online system for buying food item, especially with versatile
designed features, got a clear idea on use pros and cons of technology
and how a database generation takes place. The things required for a
sophisticated and user customization dependent e-commerce site
demands a huge list of features. We hope, in future, the experience will
help us in developing a very good web application in further future in
our career.

30. REFERENCES
LIST OF USEFUL WEBSITES
http://www.w3schools.com/html/default.asp
http://www.w3schools.com/php/default.asp
http://www.tizag.com/phpT/
http://www.tutorialspoint.com/php/index.htm