International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056 Volume: 02 Issue: 09 | Dec-2015 www.irjet.net p-ISSN: 2395-0072 © 2015, IRJET ISO 9001:2008 Certified Journal Page 886 Evaluation of Software Hazard and Cost by Commercial Point-of-View Ankur Srivastava 1 Mahesh Kumar Singh 2 , Abhimanyu Mishra 3 1 3 Assistant Professor, Department of CSE, Jahangirabad Group of Institutions, Faculty of Engineering, Uttar Pradesh, India 2 Assistant Professor, Department of CSE, Bansal Institute of Engineering & Technology, Uttar Pradesh, India ---------------------------------------------------------------------***--------------------------------------------------------------------- Abstract - Function Point is a well known established method for commercializing cost of any software projects. There are several areas of the software engineering in which I can use the function point analysis (FPA) like project development, project construction, software execution etc.[1] This function point method is used for two different purposes, firstly, to estimation the risk in the software and secondly to estimate the cost of the software. In the literature of software engineering there are so many models to estimate the risk in the software like Soft Risk Model, SRAM, and SRAEM and so on. But in the proposed method we have used SRAEM i.e. Software Risk Assessment and Estimation Model, because in this model FP is used as an input variable, and on the other hand side, in sort to determine the cost of the software the International Software Benchmarking Standards Group Release Report (ISBSG) used. Proposed effort is helpful in cost estimation and risk analysis of any software. Broadly software can be divide into three category data processing software , examine software and system software On the basis of type of software cost and risk can be predicted. By by device guess of cost and risk can be done in well in advance, so that rejection and acceptance of projects are decided on the basis of results of cost and risk estimation models to estimate the risk in the software like Soft Risk Model, SRAM, SRAEM, SAEP and so on. As a background work SRAM and SRAEM are selected. Key Words: Soft Risk Model, International Software Benchmarking Standards Group Release Report, Function Point, etc… 1. INTRODUCTION PROBABILITY STUDY As a feasibility study in this project background and related work is chosen. As a part of cost estimation and risk assessment there is lot of work has been done till now. This section discussed about related work which has already been completed in past and there advantages and disadvantages. To check feasibility it is best policy to analysis from previous work and find out opportunity of new form previous one. To estimate the risk in the software like Soft Risk Prototype tool ,SRAM, Software Risk Assessment and Estimation Model SAEP, and so on. As a background work SRAM and SRAEM considered. COCMO model and LINE OF CODE method are used as previous work taken for calculating cost of the software. 1.1 Assessment of the overall menace level of a task. Let the nine risk element probabilities be denoted by Rl, Rz, ..,Ri, ..,R9. [2] As the nine risk elements have different degree of impact on different types of software project, different weights may be assigned to these elements when combining the risk element probabilities to derive at the overall risk value for the project. Let the weights assigned to the elements be denoted by Wl, W2, .., Wi, .., W9. The risk level R of the project is then computed as W1 Rl+ WZ R2+ ...+ Wi Rl+ ...+ WG R9. If the maximum rating for all questions is 3 and the minimum rating is 1, then the maximum value of R, R,,,, is given by R,,, = W1 3+ WZ 3+ ...+ Wi 3+ ...+ WG 3 = 3 (Wl+ WZ+ ...+ Wi+ ...+ WG). Similarly, the minimum R, Rmin,, is given by Rmin = l*(Wl+ WZ+ ..+ Wi+ ...+W9). The overall risk level R may then be normalized as follows: Normalized R The normalized R, provides the risk level of the assessed project as a fraction between 0 and 1. R, for project with the lowest risk (no risk) is 0 and R, for project with the highest risk is 1. 1.2 Calibration of SRAM Ten projects of a multinational company are used to calibrate the SRAM. For simplicity, these projects are named P1 to P10. The projects are all related to mobile software and point of impact of the risk basics on Quality, Schedule and Cost of the projects are similar. A common