BCA final year project

SPONSORED LINKS

Bug Reporter Vb.net

Introduction

In large software organizations there are hundreds projects work is going on simultaneously, these projects will at different stages. The common problem in the software is the bugs, when testing people, implementation or quality people checking the software’s if any bugs will be there they will be identified, the bug information as to be sent to the corresponding project development team, these bugs are found at different places. So a tool is necessary to track all these bugs and proper management is required.

Purpose

The purpose of this document is to specify requirements and to give guidelines for the development of above said project. In particular it gives guidelines on how to prepare the above said project.

This document is intended to be a practical guide for people who developing this software.

Scope

This software serve the purpose of the bug reporter, as and when bugs are found they can report to this bug reporter in turn it will take action to send the information to the corresponding people.

Hardware Requirements

Processor : Pentium IV 2GHz and Above

RAM : 2GB RAM

Monitor : 15” Color Monitor

Keyboard

Mouse

Software Requirements

Operating System. : Windows XP

Developing Tool : VB6

Database : MS Access

All project list



The frontend of this project is VB.net and Backend is MSAccess.

CUSTOMER CARE MANAGEMENT SYSTEM PROJECT SYNOPSIS

CUSTOMER CARE MANAGEMENT SYSTEM PROJECT DOCUMENTATION

CUSTOMER CARE MANAGEMENT SYSTEM PROJECT SOURCE CODE

INTRODUCTION TO CUSTOMER CARE MANAGEMENT SYSTEM PROJECT

INTRODUCTION TO CUSTOMER CARE MANAGEMENT SYSTEM PROJECT

After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the customer care management system and other is to understand the requirements and domain of the new customer care management 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 system. Understanding the properties and requirements of a new customer care management 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.

) Posting a Query:

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

  • Customer care management 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 customer care management 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.

For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic.

Proposed Customer care management system projects are beneficial only if they can be turned out into information system. That will meet the organization’s operating requirements. Operational feasibility aspects of the Customer care management system project are to be taken as an important part of the Customer care management system project implementation. Some of the important issues raised are to test the operational feasibility of a Customer care management system project includes the following: -

Keeping in view the above description the Customer care management system project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat.