Professional Documents
Culture Documents
Summer Training Project Report Final
Summer Training Project Report Final
Summer Training Project Report Final
Declaration
I hereby declare that work entitled Summer training project report, submitted towards completion of summer training after 3rd year of B.Tech(IT) at Malaviya National Institute Of Technology Jaipur, comprises of my original work pursued under the guidance of Mr. Vikas Sonwal. The results embodied in this report have not been submitted to any other Institute or University for any award.
Signature
Date
Table of Contents
Chapter 1....................................................................................................................................................... 5 GIRNARSOFT COMPANY PROFILE ................................................................................................................. 5 1.1 Overview Of Company ........................................................................................................................ 5 1.2 GirnarSoft Mission .............................................................................................................................. 5 1.3 Products and Services ......................................................................................................................... 5 1.3.1 Business Value Services ............................................................................................................... 6 1.3.2 Product Services ........................................................................................................................... 6 1.4 GirnarSoft BI Services.......................................................................................................................... 6 Chapter 2....................................................................................................................................................... 7 JAVA .............................................................................................................................................................. 7 2.1 Principles ............................................................................................................................................. 7 2.2 Java Platform....................................................................................................................................... 7 2.3 Implementations ................................................................................................................................. 7 2.4 Performance ....................................................................................................................................... 8 2.5 Automatic Memory Management ...................................................................................................... 8 Chapter 3....................................................................................................................................................... 9 MVC Architecture.......................................................................................................................................... 9 3.1 Component interactions ..................................................................................................................... 9 3.1.1 Model .......................................................................................................................................... 9 3.1.2 View ........................................................................................................................................... 10 3.1.3 Controller ................................................................................................................................... 10 3.2 How it Works..................................................................................................................................... 10 3.3 Use In Web Applications ................................................................................................................... 11 Chapter 4..................................................................................................................................................... 11 Spring Framework ....................................................................................................................................... 11 4.1 Introduction ...................................................................................................................................... 11 4.2 Spring includes: ................................................................................................................................. 12 4.3 Spring Modules ................................................................................................................................. 12 4.4 Importance of Spring Framework ..................................................................................................... 13 Chapter 5..................................................................................................................................................... 13 Hibernate Framework ................................................................................................................................. 13
4 5.1 Introduction ...................................................................................................................................... 13 5.2 Hibernate Architecture ..................................................................................................................... 14 ................................................................................................................................................................ 14 5.3 Hibernate Configuration .................................................................................................................. 14 5.4 Building a SessionFactory.................................................................................................................. 15 5.5 Getting Session instance ................................................................................................................... 15 Chapter 6..................................................................................................................................................... 15 Project Overview......................................................................................................................................... 15 6.1 Introduction ...................................................................................................................................... 15 6.2 Problem Statement ........................................................................................................................... 16 6.3 Propose Solution ............................................................................................................................... 16 6.4 Event Dekho Website........................................................................................................................ 16 6.4.1 Registration App......................................................................................................................... 16 6.4.2 EventDekho Main Website ........................................................................................................ 17 6.4.3 EventDekho CRM ...................................................................................................................... 18 Chapter 7..................................................................................................................................................... 18 EventDekho Component Repository Management .................................................................................... 18 7.1 Introduction ...................................................................................................................................... 18 7.2 Procedure of working of CRM ........................................................................................................... 19 7.3 Requirements ................................................................................................................................... 21 7.3.1 User interface requirement ....................................................................................................... 21 7.3.2 Database Requirements ............................................................................................................. 21 7.3.3 Functional Requirements ........................................................................................................... 21 7.4 Data Flow Diagram ............................................................................................................................ 23 7.5 Database Schema .............................................................................................................................. 24 8 Conclusion ................................................................................................................................................ 30 9 References ............................................................................................................................................... 30
Chapter 2
JAVA
Java is a programming language originally developed by James Gosling at Sun Microsystems (which is now a subsidiary of Oracle Corporation) and released in 1995 as a core component of Sun Microsystems' Java platform. The language derives much of its syntax from C and C++ but has a simpler object model and fewer low level facilities. Java applications are typically compiled to byte code (class file) that can run on any Java Virtual Machine (JVM) regardless of computer architecture. Java is a general-purpose, concurrent, class-based, object-oriented language that is specifically designed to have as few implementation dependencies as possible. It is intended to let application developers "write once, run anywhere." Java is currently one of the most popular programming languages in use, particularly for client-server web applications.
2.1 Principles
There were five primary goals in the creation of the Java language: 1. It should be "simple, object-oriented and familiar" 2. It should be "robust and secure" 3. It should be "architecture-neutral and portable" 4. It should execute with "high performance" 5. It should be "interpreted, threaded, and dynamic"
2.3 Implementations
Sun Microsystem officially licensed the Java Standard Edition platform for Linux, Mac OS X, and Solaris. In the past Sun licensed Java to Microsoft but the license expired without renewal. Because Windows does not ship with a Java software platform, a
network of third party vendors and licensees develop them for Windows and other operating system/hardware platforms. Sun also distributes a superset of the JRE called the Java Development Kit (commonly known as the JDK), which includes development tools such as the Java compiler, Javadoc, Jar, and Debugger.
2.4 Performance
Programs written in Java have a reputation for being slower and requiring more memory than those written in C. However, Java programs' execution speed improved significantly with the introduction of Just-in-time compilation in 1997/1998 for Java 1.1, the addition of language features supporting better code analysis (such as inner classes, StringBuffer class, optional assertions, etc.), and optimizations in the Java Virtual Machine itself, such as Hot Spot becoming the default for Sun's JVM in 2000.
Chapter 3
MVC Architecture
The MVC (Model-View-Controller) architecture is a way of decomposing an application into three parts: the model, the view and the controller. It was originally applied in the graphical user interaction model of input, processing and output.
10
wrap and abstract the functionality of the business process being modeled. A models interface exposes methods for accessing and updating the state of the model and for executing complex processes encapsulated inside the model. Model services are accessed by the controller for either querying or effecting a change in the model state. The model notifies the view when a state change occurs in the model.
3.1.2 View
The view is responsible for rendering the state of the model. The presentation semantics are encapsulated within the view, therefore model data can be adapted for several different kinds of clients. The view modifies itself when a change in the model is communicated to the view. A view forwards user input to the controller.
3.1.3 Controller
The controller is responsible for intercepting and translating user input into actions to be performed by the model. The controller is responsible for selecting the next view based on user input and the outcome of model operations.
11
Chapter 4
Spring Framework
4.1 Introduction
The Spring Framework is an open source application framework and Inversion of Control container for the Java platform. The core features of the Spring Framework can be used by any Java application, but there are extensions for building web applications on top of the Java EE platform. Although the Spring Framework does not impose any specific programming model, it has become popular in the Java community as an alternative to, replacement for, or even addition to the Enterprise JavaBean (EJB) model. The Spring Framework provides a comprehensive programming and configuration model for modern Java-based enterprise applications - on any kind of deployment
12
platform. A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.
Flexible dependency injection with XML and annotation-based configuration styles Advanced support for aspect-oriented programming with proxy-based and AspectJ-based variants Support for declarative transactions, declarative caching, declarative validation, and declarative formatting Powerful abstractions for working with common Java EE specifications such as JDBC, JPA, JTA and JMS First-class support for common open source frameworks such as Hibernate and Quartz A flexible web framework for building RESTful MVC applications and service endpoints Rich testing facilities for unit tests as well as for integration tests
13
Chapter 5
Hibernate Framework
5.1 Introduction
Hibernate is an Object-relational mapping (ORM) tool. Object-relational mapping or ORM is a programming method for mapping the objects to the relational model where entities/classes are mapped to tables, instances are mapped to rows and attributes of instances are mapped to columns of table. A virtual object database is created that can be used from within the programming language. Hibernate is a persistence framework which is used to persist data from Java environment to database. Persistence is a process of storing the data to some permanent medium and retrieving it back at any point of time even after the application that had created the data ended.
14
The above diagram shows minimal architecture of Hibernate. It creates a layer between Database and the Application. It loads the configuration details like Database connection string, entity classes, mappings etc.
15
Hibernate creates persistent objects which synchronize data between application and database.
Chapter 6
Project Overview
6.1 Introduction
In this era of science and technology computer is most important component in our life. Work can be done in better way with the help of computer. Our project is an online portal where any one can see recently happed and famous events of his city. Any one can arrange events line parties, marriages, meetings on this portal. Name of this portal is Event dekho Website. On this website users can arrange their events according to their budget. They can choose all resources which will be used in the event like garden, band-baja, dj, cakes Catering etc from a lot of of different options of these resources on this single online portal. They can even talk to the partners who own these resources.
16
17
So there are 3 different tables in the database, each contains information about the respective kind of user. This is how refistration App. Of EvntDekho Portal works When a user gets registered himself with EventDekho, there will be scheduler which will bring the registration request to the admin. This scheduler regularly runs after certain amount of time. if it finds any recent registration request, it will bring the registration request to the admin and drops an email to the admin for reminding him about the registration request. Admin will see the registration request and he can verify the data provided by the user. if he finds the request suitable for the registration he will approve the registration otherwise will cancel the registration. means admin either can approve the registration request or can cancel the registration request. If admin approves the registration request, all the information provided by the user will be added into database and a notification email will be sent to the user that he has been successfully registered with the EventDekho. also this email will explain the user that what services he can get from the portal and how he can make this portal beneficial for him. After approval of the registration request user can sign in in the portal and can do the related work he is supposed to do depends on the kind of the user he has signed in as.
18
User can sign in being different kind of the user. User can see different event resources available on the portal User can choose an option of budget-automation for searching the event resources. This automation automatically searches the resources which are in the budget of the user. User can see the list of the partners and their contacts. User can plan his event by giving his requirements.
Chapter 7
EventDekho Component Repository Management
7.1 Introduction
EventDekho Component Repository Management is the most important module of this online portal. CRM is basically for the partners. Partners are those users who owns the event resources. CRM aims at providing an automated system for proper management of all the event resources, their imges and themes and contribution of admin to recognize if there are all genuine and quality event resources. Admin does this act with the help of scheduler which automatically runs in certain amount of time gap and convey all the regarding information to the admin.
19
20
of the admin. 16. Now all users can see these resources on the main website and they can select them for their event.
21
7.3 Requirements
22
Component Repository Management consists of three type of users. Each user has their own requirement to be satisfied by the project. These requirement are are explained below PartnerThe person who owns the event resources and share the resources with EventDekho on rent or profit persentage basis.
Priveleges
Can login view his current rsources available on the portal Can add more different kinds of reources. Can edit information about his previous resources. Can add more facilities in the previous resources. Can delete his previos resources. Can edit his profile information and contact details.
Can login and view all the event resources available on the portal. Can search the resources via name or location. Can use budget automation for automatic searching of resources according to his budget. Can see his priviously used event resources. Can view and edit his profile.
AdminPerson who is administrator of the portal. This is the user with maximum priviledges and minimum restrictions.
Priveleges-
Can login and view the histroy of all partners and customers visited the portal recently. Can remove any customer, partne and resources from the portal. Can add more subadmins who can help him in working. Can approve or cancel any registration request.
23
24
25
16. Partner_bakery (partner_id, bakery_id) 17. Partner_band_baja (partner_id, band_id) 18. Partner_garden (partner_id, garden_id) 19. Partner_decoration (partner_id, decoration_id) 20. Partner_dj (partner_id, dj_id) 21. Partner_hotel (partner_id, hotel_id) 22. Partner_review (partner_id, review_id) 23. Resources (resource_id, resource_name, resource_desc, min_price, max_price, resource_bean_name) 24. Partner_resources (partner_id, resource_id) 25. Tent_house (tent_id, tent_name, tent_address, status) 26. Tent_items (tent_id, tent_item_id, unit_price, status) 27. Theme (theme_id, theme_name, theme_desc) 28. Theme_image (theme_id, image_id) 29. User (username, password, status, type)
resource_type,
26
27
Database Tables
7.6 GUI
28
29
30
8 Conclusion
Implementation of this project has reduced the headache of event organizers, now they dont need to waste their precious time to go here and there for the event resources. They dont even need to bargain with resources owners for prices. On this website users can arrange their events according to their budget. They can choose all resources which will be used in the event like garden, band-baja, dj, cakes Catering etc from a lot of of different options of these resources on this single online portal. They can even talk to the partners who own these resources. CRM aims at providing an automated system for proper management of all the event resources, their images and themes and contribution of admin to recognize if there are all genuine and quality event resources.
9 References
http://www.theserverside.com/news/1364527/Introduction-to-the-Spring-Framework http://www.roseindia.net/tutorial/spring/index.html http://en.wikipedia.org/wiki/Hibernate_%28Java%29 http://viralpatel.net/blogs/introduction-to-hibernate-framework-architecture/ http://javabuzzu.blogspot.in/2010/02/mvc-architecture-in-java.html http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller http://www.girnarsoft.com/aboutus.htm