14-09-2012, 02:51 PM
WEB BASED REWARD POINTS MANAGEMENT SYSTEM
1WEB BASED REWARD POINTS.docx (Size: 4.82 MB / Downloads: 74)
ABSTRACT
This project aims at building a Reward Points Management System for the customer support team of the company which allows users to view useful links from different sites on topics of his/her interest
To encourage the usage of the Infobar, the company has a reward point scheme. 10 points are rewarded on usage of Inforbar for 1 hr. When a user accumulates over 100 points, he can redeem them for a gift of his choice.
Existing system:
In existing system, the rewards points are not given to the customers. With this, the revenue will be very less.
As the current System is not offering any type of offers their benefits are also low. In this current System the customers might not be happy because they don’t get all things at one location.
Proposed system:
Web Based Reward Points Management System allows the users use different links which are useful to them. This new system encourages the usage of info bar by giving rewords points to customers depends upon their usage.
This new system provide several links to user those are
Education: To get the education details to know the process of online tests.
Weather Report: To get the weather details of required place.
Currency Convertor: This currency convertor is useful to know the money amount if it is converted form one type to other type for example us dollars to Indian rupees.
Medical represents: This will give the medical represents details in the given area.
Sms: By using this Users can send free sms.
This site provide commutation also by making mails available.
INTRODUCTION & OBJECTIVE
This project aims at building a Reward Points Management System for the customer support team of the company which allows users to view useful links from different sites on topics of his/her interest.
To encourage the usage of the Infobar, the company has a reward point scheme. 10 points are rewarded on usage of Inforbar for 1 hr. When a user accumulates over 100 points, he can redeem them for a gift of his choice
METHODOLOGY IN DEVELOPING S/W PROJECT
The general methodology in developing a system is involved in different phases, which describes the system’s life cycle model for developing software project. The concept includes not only forward motion but also have the possibility to return that is cycle back to an activity previously completed. This cycle back or feedback may occur as a result of the failure with the system to meet a performance objective or as a result of change in redefinition of system activities. Like most system, the life cycle of the computer based system also exhibits distinct phase.
REQUIREMENT ANALYSIS PHASE:
This phase includes the identification of the problem, in order to identify the problem; we have to know information about the problem, the purpose of the evaluation for problem to be known. We have to clearly know about the client’s requirements and the objectives of the project.
SYSTEM ANALYSIS PHASE:
Feasibility analysis involves the benefits of various approaches and the determination of the alternative approaches a\through methods like questionnaires and interviews etc., different data about the project is collected and the data throughout the project is represented in the form of UML Diagrams.
DESIGN PHASE:
S/W design is a process through which the requirements are translated into a representation of a s/w. One of the software requirements have been analyzed and specified, the s/w design involves three technical activities: design, coding generation and testing. The design of the system is in modular form i.e., the s/w is logically partitioned into components that perform specific functions and sub functions. The design phase leads to modules that exhibit independent functional characteristics. It even leads to interfaces that reduce the complexity of the connections between modules and with the external environment. The design phase is of main importance because in this activity, decisions ultimately affect the success of s/w implementation and maintenance.
What is SRS?
Software Requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended. Hence the need for the requirement phase arose. The software project is initiated by the client needs. The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.)
SYSTEM ANALYSIS
Analysis is the detailed study of the various operations performed by a system and their relationships within and outside of the system. A key question is: What must be done to solve the problem? One aspect of analysis is defining the boundaries of the system and determining whether or not candidate system should consider other related systems. During analysis, data are collected on the available files, decision points, and transactions handled by the present system.
In this phase system analyst involving to convert all business requirements into technical requirements.This technical document is called as Software Requirement specification.
Feasibility analysis involves the benefits of various approaches and the determination of the alternative approaches a\through methods like questionnaires and interviews etc., different data about the project is collected and the data throughout the project is represented in the form of UML Diagrams.
Prototyping Model
The goal of prototyping based development is to counter the first two limitations of the waterfall model discussed earlier. The basic idea here is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an "actual feel" of the system, since the interactions with prototype can enable the client to better understand the requirements of the desired system.
Administrator or Customer Relation Ship manager:
He is the owner of the web site. He should have rights to accept the registration of the Customers based on their profile (unless the Customers should not able to login to the site). He should also have rights to add or delete customers from the site. He can view all the customers and Infobar Usage History on clicking on customer name/Email-id. He can search for Customers Based on customer name, city and Country etc.
Administrator can send a mail to the customers regarding the Reward point schemes, usage tips for Infobar, points gained etc. He can manage the Gift Articles details like add new articles, update the available stock etc.
Administrator is responsible to provide the bonus points to the customers based on usage time of Infobar and the schemes available. He is only responsible for managing customer orders for redemption of their bonus points. He has rights to accept or reject the order.
Administrator can change the status of customer profile into active or Inactive. If customers Last login date is more than one month then automatically set status into Inactive and once the customer is login then change the status into active.
DATAFLOW DIAGRAMS
Data flow diagram is a structure analysis tool that is used for graphical representation of Data processes through any organization. The data flow approach emphasis on the logic underlying the system, by using combination of only 4 symbols. It follows a top down approach. A full description of a system actually consists of set of DFD s, which comprises of various levels. And initial over view model is exploded lower level diagrams that show additional feature of the system. Further each process can be broken down into a more detailed DFD. This occurs repeatedly until sufficient details are described.