[attachment=3247]

WEB BASED REWARD POINTS SYSTEM
Objective:
This project aims at building a Reward Points Management System for the customer
support team of the company. Objectives are to build
1.A data store for user information
2.Web site supporting functionalities like - Search/sort/add/delete/view/modify etc on user information
3.Modules for bonus point allocation
4.Facility to add information on different gifts available and bonus points against them
5.Generate report on number of users using the Infobar in a month, their responses to various schemes etc
6.Communicate user via email to notify him about various incentives and bonus point schemes, get his feedback etc

Existing System:
Existing system has no facility to providing the usages information. This system is not having the facility to providing points for their users.This System has no facilitiy to providing schemes ,gifts to users. This system has no facilty as fast as to retrieve the data of users and its not providing to usage information to the users.
Proposed System:
The development of this new system contains the following activities, which try to recover the problems from the previous system:
Secure registration and profile management facilities for system users. Tracking userâ„¢s activities and progress. Facilitating communication - Discussion through email. In this system providing schemes and rewards to users according to using of the system.User has winning points from system, he can select rewards according to his/her wish. The system providing bonus points to the users. Basic and advance admin facilities like add/updatemembers,backup/recovery of data, generating various reports etc.
Number Of Modules:
Study of the System:
In the flexibility of uses the interface has been developed a graphics concepts in mind, associated through a browser Interface. The GUIâ„¢s at the top level has been categorized as follows
A. Admin
B. Users
The system after careful analysis has been identified to be presented with the following modules:
The Modules involved are
1.Registration
2. Security and Authentication
3. Communication
5. Points Calculation Module
5. Admin
6. user
7. Reports
Security and Authentication :
1. User Registration.
2. Login as User or Administrator
3. Change password
4. Forgot Password
Admin Module:
1. Admin collects the details of all usage toolbars, links and activities and Enters that details into the site.
2. Admin adds different rewards/gifts to the system.
3. he can look up about user requests and he can give the status of user registration.
After acceptance of admin, user has the facility to access the system.
4. View the reward/gift Lists .
5. View the points of user, which user getting how many points.
6. View the reward reward request details from the user and can give the status about that reward.
7. Post the news about new articles usage information.
8. View the feedback details.
User Module:
1. View Usage details.
2. View The news details.
3. make the request for registration to this system.
4. view getting points, based on points what gifts information avilable for him/her.
5. view rewards/gifts details.
6. select available gifts on that view the status of the gift.
7. can give the feedback about the system.
Communication:
In the module, system user can comminicate with each other through the emails according queries or suggestions.
Points Calculation Module:
In thsi module, it maintains the time, from user registration onwards. the user how much time he spending with system after login, depending on the spending time points will be calculated. Per every one hour he getting 10 points. When he reaching 100 points then he can saw some gifts displayed to him. From among that gifts he can select one the gift for every 100 points.
Reports:
In this Module the administrator, User can generate different types of reports.
Software Requirements :
Operating System : Windows XP/2003 or Linux
User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlets, JSP
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 5.x
Hardware Requirements:
Processor : Pentium IV
Hard Disk : 40GB
RAM : 512MB or more

---

[attachment=8537]

Author Name
Fatma Al Waheibi


1 Introduction
Chapters are entered using the Heading 1 paragraph style; they start on a new page. The paragraph after a heading automatically uses the Body First paragraph style.
However most text uses the Body Text paragraph style like this paragraph. Ordinary text appears as 11 point Times New Roman, single-spaced, single-sided pages.
In general, use the default spacing that headings and paragraphs give you. Avoid using newlines or spaces to format text. If you need to use quotes, preferably use single curly quotes ‘…’.

1.1 Background and Context
Describe the problem that you are tackling. Sections are entered using the Heading 2 paragraph style.

1.2 Scope and Objectives
Define the scope and objectives of your project. Define the expected results and how others will gain from the work.


2 State-of-The-Art
Discuss the work of others in the same area as your project. Show critical awareness of what others have done, and how you hope to extend or complement existing capabilities. Give references to other work by using cross-references like.

3 Approach
Explain how you are tackling the project. Describe any special software or hardware that you are using. Discuss the techniques you have chosen, and the developments you are undertaking. Demonstrate how you are performing the project as a computing professional (i.e. application of systematic techniques, awareness of relevant professional issues).

3.1 First Section
Subdivide lengthy text into sections.

3.1.1 First Subsection
If necessary, also use subsections. Subsections are entered using the Heading 3 paragraph style.

3.1.1.1 First Subsubsection
If you really need subsubsections, enter these using the Heading 4 paragraph style.
As an example of a figure, consider ‎Figure 1. Captions are entered using the Figure paragraph style. Use automatic figure numbering and cross-references. Let large figures float to the top of the next page rather than having a big gap in the text. If you need something centred as for a figure, use the Body Centre paragraph style.

4 Prototype
Describe the prototype you have implemented.

5 Interim Plan

5.1 Updated Project Plan
Give an updated plan for the remainder of the project. This should identify the remaining pieces of work and when you plan to complete them.

5.2 Updated Project Deliverables
Update the remaining deliverables of the project. In particular, describe what you will demonstrate when the final report is due


References
Use the Reference paragraph style to enter and cross-reference document references. Books ‎[1], standards ‎[2], reports ‎[3], journal articles ‎[4], conference papers ‎[5], and web pages ‎[6] are conventionally presented in slightly different ways.

[1] Greene, D. and Williams, P. C. Linear Accelerators for Radiation Therapy, Second Edition. IOP Publishing Ltd., Bristol and Philadelphia, 1997.
[2] ISO. Language Of Temporal Ordering Specification, ISO 8807, International Organization for Standardization, Geneva, 1989.
[3] Jacobson, J. and Andersen, O., editors. Software Controlled Medical Devices. SP Report 1997:11, Swedish National Testing and Research Institute, Sweden, 1997.
[4] Turner, K. J. The Rules for Sailing Races on PDAs, J. Navigation, 23(5):114-240, May 2002.
[5] Ji, H. and Turner, K. J. Specification and Verification of Synchronous Hardware using LOTOS. In Wu, J. Chanson, S. T. Gao, Q. editors, Proc. Formal Methods for Protocol Engineering and Distributed Systems (FORTE XII/PSTV XIX), pages 295-312, Kluwer Academic Publishers, London, UK, October 1999.
[6] University of Stirling. Computing Science and Mathematics Research Home Page, http://cs.stir.ac.uk/research, October 2008.

---

Problem Definition & Domain:
Nowadays so many software’s are introduced to world. Based on that system owners or software owners want to bring full traffic to their software’s or system. For that they are providing gifts or rewards to the customers. According to using of system or software they are providing points to customers (users). They offering rewards to customers based on points. This application bring a full traffic to their system or software’s

System Analysis:

Purpose of the System:
This project aims at building a Reward Points System for the customer. Objectives are to build
 A data store for user information
 Web site supporting functionalities like -Search/sort/add/delete/view/modify etc on user information
 Modules for bonus point allocation
 Facility to add information on different gifts available and bonus points against them
 Generate report on number of users using the Infobar in a month, their responses to various schemes etc
 Communicate user via email to notify him about various incentives and bonus point schemes, get his feedback etc.




[attachment=8917]
Existing System:
Existing system has no facility to providing the usages information. This system is not having the facility to providing points for their users. This System has no facility to providing schemes ,gifts to users. This system has no facility as fast as to retrieve the data of users and it’s not providing to usage information to the users.
Proposed System:
The development of this new system contains the following activities, which try to recover the problems from the previous system. Secure registration and profile management facilities for system users. Tracking user’s activities and progress. Facilitating communication - Discussion through email. In this system providing schemes and rewards to users according to using of the system. User has winning points from system, he can select rewards according to his/her wish. The system providing bonus points to the users. Basic and advance admin facilities like add/update members, backup/recovery of data, generating various reports etc.
Feasibility Study:
Technical Feasibility:
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical analysis.
 Understand the different technologies involved in the proposed system:
o Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.
 Find out whether the organization currently possesses the required technologies:
o Is the required technology available with the organization?
o If so is the capacity sufficient?
o “Will the current printer be able to handle the new reports and forms required for the new system?”
Operational Feasibility:
Proposed project is beneficial only if it can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:
Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance. Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.Have the user been involved in the planning and development of the project? Early involvement reduces the chances of resistance to the system and in general and increases the likelihood of successful project.Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.
Economical Feasibility:
Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.
A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.
Software Requirements :
Operating System : Windows XP/2003 or Linux
User Interface : HTML, CSS
Client-side Scripting : JavaScript
Programming Language : Java
Web Applications : JDBC, Servlets , JSP
IDE/Workbench : My Eclipse 6.0
Database : Oracle 10g
Server Deployment : Tomcat 5.x
Hardware Requirements:
Processor : Pentium IV
Hard Disk : 40GB
RAM : 512MB or more

to get information about the topic web based reward points management system full report ,ppt and related topic refer the page link bellow

http://studentbank.in/report-web-based-r...stem--9466

http://studentbank.in/report-web-based-r...nts-system