PROJECT REPORT & SOURCE CODE

BCA MCA COMPUTER SCIENCE PROJECT SOURCE CODE

BCA MCA COMPUTER SCIENCE PROJECT PROJECT REPORT

SPONSORED LINKS

CLICK HERE AND SUBSCRIBE TO DOWNLOAD ALL PROJECTS - FREE

2.1. INTRODUCTION

After analyzing the requirements the customer query management system, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing Query system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed customer query management system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.

2.2. ANALYSIS MODEL OF CUSTOMER QUERY SYSTEM

SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.

As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.

The steps for Spiral Model can be generalized as follows:

· The new customer query system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing query system.

· A preliminary design is created for the new Query management system.

· A first prototype of the new query management system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.

· A second prototype is evolved by a fourfold procedure:

1. Evaluating the first prototype in terms of its strengths, weakness, and risks.

2. Defining the requirements of the second prototype.

3. Planning an designing the second prototype.

4. Constructing and testing the second prototype.

· At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.

· The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.

· The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.

· The final system is constructed, based on the refined prototype.

· The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.

The following diagram shows how a spiral model acts like:

Fig 1.0- SPIRAL MODAL OF CUSTOMER QUERY MANAGEMENT SYSTEM

ADVANTAGES:

· Estimates(i.e. budget, schedule etc .) become more realistic as work progresses, because important issues discover earlier.

· It is more able to cope with the changes that are software development generally entails.

· Software engineers can get their hands in and start woring on the core of a project earlier.

2.3. STUDY OF THE QUERY MANAGEMENT SYSTEM

GUI’S

In the flexibility of the uses the interface has been developed a graphics concept in mind, associated through a browses interface. The GUI’S at the top level have been categorized as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transaction states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibility.

NUMBER OF MODULES IN CONSUMER QUERY MANAGEMENT SYSTEM

The Query management system after careful analysis has been identified to be presented with the following modules:

The Modules Involved in the project are:

1. Customer’s Module

2. Employee’s Module

3. Search

4. Authentication

1. Customer’s Module:

The Customer’s Module is designed to provide the following services.

i) Posting a Query:

• Customers should be free to post their queries to the concern department.

• The system must identify each query with an automatically generated Query Id, for future references.

ii) Survey Details:

• Customers should be able to post the survey details on a department by simply selecting the department and post the survey details to the organization.

• In survey details service the system provides the rate of satisfaction of the customer on a particular employee.

• The rate of satisfaction can be known by giving ratings to the employee.

iii) Status

• Customers should be allowed to check the status of their query, by using the unique Query Id provided by the system.

• The system must display the answers along with the Query to the customer, after posting the query.

2. Employee’s Module:

In this Employee’s Module we have two services, which are

i). Posted Queries:

• The employees should be able to see the posted queries, which are posted by the customers.

• An employee can visit the queries posted to that department only.

• The employee should post back the solution to the queries he has received.

• An employee cannot only see his rating but also rating of other employees who are working in other departments.

ii). Survey:

• The employees should be able to see the survey details posted by the customers.

• He can able to see the survey details of all the departments.

• This system should also provide registration of new customers for the organization.

• The customers should be able to see the frequently asked question asked by the customers.

A password protection with secure mode option is provided to guard from un-authorized access to database.

PROJECT INSTRUCTIONS:

· Based on the given requirements, conceptualize the Solution Architecture. Choose the domain of your interest otherwise develop the application for ultimatedotnet.com. Depict the various architectural components, show interactions and connectedness and show internal and external elements. Design the web services, web methods and database infrastructure needed both and client and server.

· Provide an environment for upgradation of application for newer versions that are available in the same domain as web service target.

2.4. HARDWARE SPECIFICATIONS

HARDWARE REQUIREMENTS:

• PIV 2.8 GHz Processor and Above

• RAM 512MB and Above

• HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

• WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

• Visual Studio .Net 2005 Enterprise Edition

• Internet Information Server 5.0 (IIS)

• Visual Studio .Net Framework (Minimal for Deployment)

• SQL Server 2000 Enterprise Edition

2.5. PROPOSED CONSUMER QUERY MANAGEMENT SYSTEM

To debug the existing system, remove procedures those cause data redundancy, make navigational sequence proper. To provide information about audits on different level and also to reflect the current work status depending on organization/auditor or date. To build strong password mechanism.

NEED FOR COMPUTERIZATION

We all know the importance of computerization. The world is moving ahead at lightening speed and every one is running short of time. One always wants to get the information and perform a task he/she/they desire(s) within a short period of time and too with amount of efficiency and accuracy. The application areas for the computerization have been selected on the basis of following factors:

· Minimizing the manual records kept at different locations.

· There will be more data integrity.

· Facilitating desired information display, very quickly, by retrieving information from users.

· Facilitating various statistical information which helps in decision-making?

· To reduce manual efforts in activities that involved repetitive work.

· Updating and deletion of such a huge amount of data will become easier.

FUNCTIONAL FEATURES OF THE MODEL

As far as the project is developed the functionality is simple, the objective of the proposal is to strengthen the functioning of Audit Status Monitoring and make them effective and better. The entire scope has been classified into five streams knows as Coordinator Level, management Level, Auditor Level, User Level and State Web Coordinator Level. The proposed software will cover the information needs with respect to each request of the user group viz. accepting the request, providing vulnerability document report and the current status of the audit.

WORKING OF THE SYSTEM

The entire scope has been classified into five streams known as: -

Coordinator Level

(Addressing the information management needs of coordinator)

Management Level

(Addressing the information management needs of management)

Auditor Level

(Addressing the information management needs of auditors)

User Level

(Addressing the information management needs of the user group)

State Web Coordinator level

(Addressing the needs of coordinator of the state)

2.6. INPUT AND OUTPUT in Query system

The main inputs, outputs and major functions of the system are as follows

INPUTS:

· Head operator enters his or her user id and password.

· Operators enter his or her user id and password.

· Technicians enter his or her user id and password.

· Sub technicians enter his or her user id and password.

· User requests the reports.

· User requests the search.

· Head operator can edits the personal details and so on.

OUTPUTS:

· Head operator receives personal details.

· Operator receives the personal details.

· Technicians receive personal and technical details.

· Users receive requested reports.

· Displays search result.

2.7. PROCESS MODELS USED WITH JUSTIFICATION

ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION

The following commands specify access control identifiers and they are typically used to authorize and authenticate the user (command codes are shown in parentheses)

USER NAME (USER)

The user identification is that which is required by the server for access to its file system. This command will normally be the first command transmitted by the user after the control connections are made (some servers may require this).

PASSWORD (PASS)

This command must be immediately preceded by the user name command, and, for some sites, completes the user's identification for access control. Since password information is quite sensitive, it is desirable in general to "mask" it or suppress type out.