10-05-2013, 03:18 PM
WCPS Web Based Claims Processing System A PROJECT REPORT
WCPS Web Based.doc (Size: 2.21 MB / Downloads: 32)
Purpose
ABC is a company which is having employee strength of at least 1000. All the employees are provided medical reimbursement facility which means that the expenditure incurred by the employee for treatment is reimbursed by the company. For reimbursement, the employee needs to fill in a form detailing the treatment undertaken which includes the name & cost of medicines, laboratory tests, surgery. The form is duly signed by the employee and it will be sent to the concerned Claims Processing Department (CPD) by messenger for processing. CPD will process it and the order regarding the reimbursement is sent to the Cash counter (CC) where in the employee can come and receive the reimbursement amount.
Objective
Web Based Claims Processing System (WCPS) is complete end to end solution to cover all aspects of online claim and reimbursement system.
The basic objective of developing this project is:
• Provides complete web site solution, including employee registration, enter new claim, approve/ reject claim. Complete web based administration.
• The Web Based Claims Processing System can automatically display pending claim count in the main page of employee of Claims Processing Department (CPD).
• Employee can view their claim status online and all claims can be treated as Pending, Approved and Rejected.
• Employee of CPD can add, edit employee details, all employees are identified by the employee no. Employee no will be unique throughout the system.
• System must store audit trail of all DML transaction, like it stores employee no, time stamp in the database for add, edit, delete operation.
• System should capture lat login time for all the employees.
• Complete web based system no installation required to run the application in client system.
• Employee must able to view his/her previous claim details.
Project Scope
The Web Based Claims Processing System (WCPS) will permit to enter new claim, track the claim status and maintaining master information. The main users of the project are Employee of all departments and Employee of CPD – Claim Processing Department.
From an end-user perspective, the Web Based Claims Processing System Project consists of two functional elements: enhanced Employee modules for Login, Apply for new claim, view status of already applied claim. And CPD module for approve/reject claim, view pending status, Add/Edit employee details.
Development Environment
Visual Studio 2005 IDE
Most advanced integrated development environment for developing .NET application. Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It can be used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silverlight.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designer, and database schema designer. It allows plug-ins to be added that enhance the functionality at almost every level - including adding support for source control systems (like Subversion and Visual SourceSafe) to adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer).
Description:
Proposed to develop a software titled Web Based Claims Processing System (WCPS) which is web based so that the employee can fill the form online and submit it so that the form is sent to CPD through Internet. At CPD, the form needs to be checked automatically by a program which will compute the amount that needs to be reimbursed to the employee for the treatment undertaken. Any excess amount claimed by the employee is ignored by the software. The amount computed will be routed to the e-mail account of the employee as well as to the Bank which holds the accounts of all the employees of the company. The bank will credit the amount to the account of the employee based on the mail.
Requirement Analysis
The requirement analysis outlines the approach the development team will take to meet the goals of the project and provides the basis for proceeding to the planning phase. After identifying the business problem and defining the vision and scope, the team creates the solution concept that explains in general terms how the team intends to meet the requirements of the project.
Design goals
Design goals are similar to business goals in many ways. The difference is that design goals focus more on the attributes of the solution and less on what the solution will accomplish for the business. Design goals address not only what the team wants to accomplish but also what the team is not trying to accomplish with the solution. As with business goals, we need to prioritize design goals so that the team knows which goals must be accomplished, in case the project cannot achieve all of them.
System Constraints
Constraints indicate the parameters to which the final business solution must adhere. They are aspects of the business environment that cannot or will not be changed. Often, these constraints become design goals for the application. If constraints are not identified properly, the project team might design a product that cannot be deployed within the business.
Performance Requirements
An application’s performance is defined by metrics such as transaction throughput and resource utilization. A user might define an application’s performance in terms of its response time. No more than 5-percent degradation in average query response is allowed while all concurrent users are using the system. Processor utilization should not exceed 80 percent during all concurrent users are using the system.
We must define performance requirements before the team proceeds to the developing phase. To define a good performance requirement, we must identify project constraints, determine services that the application will perform, and specify the load on the application.
Availability Requirements
Availability is a measure of how often the application is available to handle service requests as compared to the planned run time. Availability also takes into account repair time because an application that is being repaired is not available for use.
Designing for availability includes anticipating, detecting, and resolving hardware or software failures before they result in service errors, faults, or data corruption, thereby minimizing downtime. To ensure availability, provide multiple routes to application services and data. Use only tested proven processes (both automated and people-based) that support the application throughout its life cycle.
In addition to unplanned downtime, planned downtime must be reduced. Planned downtime can include maintenance changes, operating system upgrades, backups, or any other activity that temporarily removes the application from service.
Reliability Requirement
The reliability of an application refers to the ability of the application to provide accurate results. Reliability and availability are closely related. While availability measures the capacity to handle all requests and to recover from a failure with the least loss of access to the application, reliability measures how long the application can execute and produce expected results without failing. Users bypass unreliable Web sites, resulting in lost revenue and reduced future sales. In addition, the expense of repairing corrupted data increases the cost of application failure. Unreliable systems are also difficult to maintain or improve because the failure points are typically hidden throughout the system. Because of the need no single point failure, automatic failover will be required. In addition, existing disaster recovery and backup plans and procedures must be revised to incorporate the Web Based Claims Processing System (WCPS).
Scalability Requirement
Scalability is defined as the capability to increase resources to produce an increase in the service capacity. In a scalable application, you can add resources to manage additional demands without modifying the application itself.
A scalable application requires a balance between the software and hardware used to implement the application. You might add resources to either software or hardware to increase the scalability of the application. Adding these resources might produce a benefit; however, it could also have a negative or null effect, with the application showing no significant increase in service capacity. For example, you might implement load balancing in an application. This will help only minimally if the application has been written to make synchronous method calls or to retrieve lengthy datasets in response to a user’s request.
Security Requirements
Malicious attackers use various methods to exploit system vulnerabilities to achieve their goals. Vulnerabilities are weak points or loopholes in security that an attacker exploits to gain access to an organization’s network or to resources on the network. Some vulnerabilities, such as weak passwords, are not the result of application or software development design decisions. However, it is important for an organization to be aware of such security weaknesses to better protect its systems.
Security Features of .NET Technologies
.NET Web applications implement one or more of the logical services by using technologies such as Microsoft ASP.NET, Enterprise Services, XML Web services, remoting, Microsoft ADO.NET, and Microsoft SQL Server. To create effective security strategies, we need to understand how to fine-tune the various security features within each product and technology area, and how to make them work together.
Authentication
Authentication is the process of discovering and verifying the identity of a user by examining the user’s credentials and then validating those credentials against some authority. A variety of authentication mechanisms are used, some of which can be used with .NET Framework role-based security.
Examples of commonly used authentication mechanisms include the operating system, Passport, and application-defined mechanisms, such as NTLM and Kerberos version 5 authentication.
Authorization
Authorization is the process of determining whether a user is allowed to perform a requested action. Authorization occurs after authentication and uses information about a user’s identity and roles to determine what resources that user can access. You can use .NET Framework role-based security to implement authorization.
ASP.NET security
ASP.NET provides a useful tool for application developers to use to create Web pages. When a Web site records a user’s credit card information, the file or database that stores such information must be secured from public access. ASP.NET, in conjunction with IIS, can authenticate user credentials such as names and passwords
ADO.NET and SQL Server
ADO.NET provides data access services. It is designed for distributed Web applications, and supports disconnected scenarios. When we build Web-based applications, it is essential that we must use a secure approach to accessing and storing data. ADO.NET and SQL Server provide several security features that can be used to ensure secure data access.
Waterfall model.
This model uses milestones as transition and assessment points. When using the waterfall model, you need to complete each set of tasks in one phase before moving on to the next phase. The waterfall model works best for projects in which the project requirements can be clearly defined and are not liable to modifications in the future. Because this model has fixed transition points between phases, you can easily monitor schedules and assign clear responsibilities and accountability.
Stabilization process:
During the stabilizing phase, the team performs integration, load, and beta testing on the solution. In addition, the team tests the deployment scenarios for the solution. The team focuses on identifying, prioritizing, and resolving issues so that the solution can be prepared for release. During this phase, the solution progresses from the state of all features being complete as defined in the functional specification for this version to the state of meeting the defined quality levels. In addition, the solution is ready for deployment to the business