Hello Logout


Development of a Campaign Information System


Title of the Project


Development of a Campaign Information System


Abstract of the project


An insurance company wants to start campaigns for its new products to be sold to the prospective customers. Campaign means advertising of the products through channels like Tele marketing, letters, signboards, TV Commercials, etc. There are different campaigns for different products and there is a specific period for each campaign.


Before the campaign starts, estimates are made on sales to be achieved, budget allocation for each campaign and variance allowed (%) both for sales and budget. When the actual data is captured, the actual variance(%) is calculated. The difference between the actual and the estimated variance gives the insurance company an insight into their estimation and it helps in making strategic decisions about budgets and campaign periods.


You have to develop the system, which captures the above functionality. It is an intranet application




Generic Keywords


Databases, Middleware, Programming


Specific Technology Keywords


Oracle Stored Procedures, ASP, HTML, JavaScript/VBScript


Project Type keywords


Analysis, Design, Implementation, Testing, Graphical User Interface


Functional components of the project


Following is a list of functionality of the system. More functionality that you find appropriate can be added to this list. And, in places where the description of functionality is not adequate, you can make appropriate assumptions and proceed.


Users of the system : Employees of the Campaign department. Here again any number of groups can be assumed. For example, groups which have rights to view only the reports in HTML Format, groups having rights to enter/update/delete data, etc..


User will start with the login page in which username and password are entered. This screen should also provide a functionality to change the password. To change the password, it should ask for the old password, new password and confirm new password.


Based on the group, to which the user belongs, relevant modules are shown.

Modules are


·         Campaign Master – which captures the master data for the campaigns for the product category and for the given period

·         Product Master – All the new products for which campaigns are to be done.

·         Estimated Budget Campaign - The information about the estimated campaign budget , sales target, period, type of campaign will be captured. Various formulae can be put to cross check the budget allocation with the period/type of campaign and type of product. For example, say for a campaign of 3 months by tele-marketing for xyz product type, the budget should be abc amount. These validations can be put on the client side. Assumption on various details(like gifts to be given to customers in campaign period, discounts, etc ) to be captured for a campaign apart from the ones mentioned can be helpful. Please Brainstorm on this.

·         Actual Budget Campaign – This will be similar to the above module except that it will capture the actual data

·         Statistics – Here different reports can be shown as follows

Ø  Different campaigns for different products in a given time frame

Ø  Variance reports (estimated vs actuals)

Ø  Sales target reports vis a vis campaigns

·         Help – Describing operation of the whole application

·         Administration – Here users can be assigned to groups and the groups in turn can be assigned rights to different modules.

In addition to this , we can have a help link on each of the modules.


Steps to start-off the project:


Microsoft platform: The system is developed using Active Server Pages as the  front end and Oracle/SQL Server/DB2 as the back end.


Java Platform: The system is developed using Java Server Pages/ Servlets as the  front end and Oracle/SQL Server/DB2 as the back end.


The following steps will be helpful to start off the project


1.      Get a firm grasp on the above technology.

2.      Decide on the number of groups, number of products, period of campaigns, number of campaigns, business rules.

3.      Decide on the various details of the user and their groups that would be stored in the database (like employee/registeration-number, name, grade, location, system-login, password in cryptic form, etc)

4.      Make a super user who will be able to assign users to groups and will be able to assign rights to a group.

5.      Help should be very user friendly.

6.      UI should include good images and have a constant look and feel throughout the application.





Hardware requirements




Alternatives (If available)


PC with 5 GB hard-disk and 512 MB RAM







Software requirements





Alternatives (If available)


Windows 95/98/XP with MS-office

Not Applicable


MS-SQL server/Oracle




Not Applicable


IIS for MS

Tomcat for java



Manpower requirements


2 to 3 students can complete this in 4 – 6 months if they work fulltime on it.


Milestones and Timelines




Milestone Name

Milestone Description





Week no. 

from the start

of the project





Requirements Specification

Complete specification of the system (with appropriate assumptions)  that constitutes this milestone. A document detailing the same should be written and a presentation on that be made.


Attempt should be made to add some more relevant functionalities other than those that are listed in this document.


Technology familiarization

Understanding of the technology needed to implement the project.


The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.


Database creation

A database of atleast 100 entries of users, 50-60products,

10-15 campaigns in a year should be created.


It is important to finalize on the database at this stage itself so that development and testing  can proceed with the actual database itself.


High-level and Detailed  Design

Listing down all possible scenarios (like estimated budget, actual budget, etc) and then coming up with flow-charts or pseudocode to handle the scenario.


The scenarios should map to the requirement specification (ie, for each requirement that is specified, a corresponding scenario should be there).


Implementation of the front-end of the system

Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each of the options (various master modules).


During this milestone period, it would be a good idea for the team (or one person from the team) to start working on a test-plan for the entire system. This test-plan can be updated as and when new scenarios come to mind.


Integrating the front-end with the database

The front-end developed in the earlier milestone will now be able to update the database. Other features like. In short, the system should be ready for integration testing.




Integration Testing

The system should be thoroughly tested by running all the testcases written for the system (from milestone 5).


Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.


Final Review

Issues found during the previous milestone are fixed and the system is ready for the final review.


During the final review of the project, it should be checked that all the requirements specified during milestone number 1 are fulfilled (or appropriate reasons given for not fulfilling the same)


Guidelines and References


http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnasp/html/asptutorial.asp (ASP tutorial)


http://www.functionx.com/sqlserver/ (SQL-server tutorial)

Tags :
Your rating: None