CAMPAIGN INFORMATION SYSTEM

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.

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

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

Campaign Information System, which will cover the following modules:

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

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

·         Estimated Budget Campaign - The information about the estimated campaign budget, type of campaign will be captured.

·         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. actual)

The Front-End   :   Asp.net/C#.net

The Back End    :  Sql Server 2000.

Steps to start-off the project:

Microsoft platform: The system is developed using Active Server Pages Dot net as the front end and SQL Server as the back end.

Requirements

                       

Hardware requirements

Number	Description
1	PC with 5 GB hard-disk and 512 MB RAM

Software requirements

Number	Description
1	Windows 95/98/XP
2	MS-SQL server
3	Visual Studio .net 2.0
4	IIS 5.0, IE 6.0

Manpower requirements:

            Project Duration:  60 days (Business days)

           Project team-size: 1

Project Milestones and Schedules

Number	Milestone Name	Milestone Description	Timeline No of Days from start of the course	Remarks
1	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.	45 days	Attempt should be made to add some more relevant functionality other than those that are listed in this document.
2	Technology familiarization	Understanding of the technology needed to implement the project.	3 days	The presentation should be from the point of view of being able to apply it to the project, rather than from a theoretical perspective.
3	Database creation	A database of at least 100 entries of users, 50-60products, 10-15 campaigns in a year should be created.	2 days	It is important to finalize on the database at this stage itself so that development and testing can proceed with the actual database itself.
4	High-level and Detailed  Design	Listing down all possible scenarios (like estimated budget, actual budget, etc) and then coming up with flow-charts or pseudo code to handle the scenario.	5 days	The scenarios should map to the requirement specification (i.e., for each requirement that is specified, a corresponding scenario should be there).
5	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).	5 days	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.
6	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.	10 days
7	Integration Testing	The system should be thoroughly tested by running all the test cases written for the system (from milestone 5).	15 days	Another 2 weeks should be there to handle any issues found during testing of the system. After that, the final demo can be arranged.
8	Final Review	Issues found during the previous milestone are fixed and the system is ready for the final review.	10 days	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)