ASSESSMENT OF HEALTHCARE WITH USE CASE POINT

: Project plan plays a vital role in development of the software projects. The software projects can be successfully managed and controlled by managers with the help of effective effort, schedule and estimated size plan. Due to uncertainties in requirements, complexity and size of software systems increases. There are many methods for effective project management in context with measuring and commuting size and productivity. One of the method in this category is use case point .Use case point approach enables to produce a reliable estimate in the software development cycle at a very early stage. In this paper necessity of planning phase in SPM is shown. Requirement elicitation is done by discussion with stakeholders. Accordingly use cases are prepared. We have estimated the size of health care model using use case point.


I. INTRODUCTION
The important technique for increasing the new product design effectiveness is Project management. Basically project management means laying out tasks to make sure tasks are in sequence and dependency between tasks is clearly defined, making sure resources assigned to tasks are not overloaded, making sure enough contingency is put in place to cover various different risks. People, Product ,Process and Project are four p's of Project management [1] [8] . The relationship is defined between them. Every project follows a process to develop a product by the people. To fulfill the requirements of stakeholder project manager should develop an effective project plan. There is dynamism in software projects [4]. Additional measures have to be added to the management and development of software projects due to change in technology and market scenario. An intelligent framework and appropriate solutions are required for development and management of software projects as complexity and uncertainties have increased a lot in software development of projects [9]. So planning phase of SPM is emphasized to resolve uncertainties and complexity of software projects. The four phases of Software project management process are initiation phase, planning phase, executing phase, monitoring and controlling phase. In initiation phase approval of the project is done. In the planning phase scope document is developed on the basis of collected requirements [6]. Scope document includes budget, time line, size, security initial review etc. In the executing phase communications and information distribution is done. In the monitoring and controlling phase performances are reported, final training, security final approvals are done. Also final budget and timeline approved changes are verified [14].
In this paper, at the initial stage of software project development we have shown the importance of planning phase For requirement elicitation we have used use cases. This paper is organized as follows: II section contains an introduction of planning phase; III section describes Use case point method. It also includes the formulas for calculation of software size. IV Section applies use case point method for estimating size of cardiac medical system, V Section gives the conclusion.

II. PLANNING PHASE OF SPM
In planning and execution phase of SPM, various tasks are allotted to resources in order to achieve the timelines and budget related goals of the projects [11]. In planning phase various plans like project, resource, financial, quality, risk, communication and acceptance are prepared.
Basic theory concepts and approaches should be included in an intelligent and complete framework. So first of all planning of project is important [2]. After the initiation phase, the planning of project is done till an apt level of detail. The SPM planning phase involves creation of a scope document which helps and guides the team in other phases of SPM. The primary aim of planning phase is to plan time, cost and resources as shown in figure 1, to find the estimation of work needed and to effectively manage risk during execution of project.
An inadequate plan greatly reduces the development and completion of project successfully and thereby it stops initiation phase to accomplish its goals. The artifacts are gathered through the software development process. They are the evidence that the process is followed. The artifacts of planning phase are project team identified, business process mapping, current and planned Work Breakdown Structure, project plan, mitigation strategy, budget, resource, communication and change plan [7].
Project plan shows timeframes required to deliver the project, along with resources and milestones. A resource plan outlines the resource levels required for successful completion of project . A properly documented resource plan will specify the exact quantities of people, equipment and materials needed to complete your project. It helps in calculating efforts and creating schedule. The financial plan summarises the total expenses to be incurred across the project and this is treated as project budget. A quality plan assists to schedule tasks related to customer's needs. It makes sure that customer's needs are done. It consists of quality assurance plan and quality control plan. A risk plan helps to identify risks and identify actions to prevent them from plan is occurring .An acceptance plan contains deliverables produced by the project. It is an agreement with the customer. Customer gives its concern for schedule tasks. A communication plan recounts how it is intended to send right messages at the right time to the right people [3].

III. USE CASE POINT APPROACH
In initial phase of software development life cycle, software effort estimation requires large amount of time [5]. Large amount of efforts should be calculated accurately to avoid underestimation and overestimation. Use Case Point (UCP) approach is developed by Gustav Karner [12]. Requirements are represented by using use case diagrams .The purpose of use case approach is measure projects at their initial stage.
The use cases are to be treated as building blocks for any software effort estimation method based on use case point model. A use case diagram is composed of use cases and actors. Each use case is represented by a use case scenario. In use case point method the software size is calculated according to the number of use cases and actors in a use case diagram multiplied by their complexity factors. The classification of different levels of use cases is done on the basis of number of transactions in a use case. Use Case point method calculates size through two stages [10].
Health care job is a complex, highly supported, timepressured process. The health system checking should be very appropriate and it should have well planned, welldefined and Factors and weights are considered of both technical environmental factors. There are total 13 technical factors and 8 environment factors as suggested by Karner [12].Values taken by factors vary from 0 to 5. Their significance is shown in Table 2    Intermediate effect 4 Significant influence 5 Very strong influence The weights and factors are assigned below in a health care model.

IV. HEALTH CARE MODEL
On the basis of requirements elicited from cardiology department in reference to health care system ,for different scenarios different use cases are prepared [13]. Classification for 17 use cases shown in Table 3 is done as 4 simple, 6 medium and 7 complex. In reference to user tasks for system development scenario preparation is a basic element.
Scenario preparation as a top down approach starts with the requirement elicitation process. It identifies the properties and limitations of domain to be worked upon [14]. We have shown use cases in figure 3 and figure 4 for different scenarios.

2.
Check if patient has symptoms of heart problem.

4.
Check if patient has come for follow up .

5.
Check history of patient.

6.
Check the tests if recommended in previous visit , identify the problem and treat. Use case point approach is applied on health care model. The weights assigned for technical and environmental factors are shown in Table 4 and Table 5.  The size is reliable and closer to the efforts applied iteratively. Thus in the very early stage in the development cycle the size is assessed of model of health care.

V. CONCLUSION
The importance of planning phase of software project management is shown in this paper.. Requirements are elicited by using use cases for different Scenarios. On the basis of Project plan tasks, resources, schedule is planned. Project Plan helps to review actual against planned .Weights between 0 and 5 are assigned to existing factors for health care model. Then efforts are estimated using use case point approach. It is mandatory to evaluate the weights properly as the weighted values influence each factor. The weights will vary according to the type of Project. Many factors including technical and political have impact on the software development process. The estimation at initial stage can decrease error.

VI. REFERENCES
[1]. A Guide to the Project Management Body of Knowledge,5th edition,PMI,USA,2013.
[2]. Project Management Instiute ,"PMBOK -A guide to the project management body of knowledge " Newtown square, PA: Project management institute ,4th edition,2008.