Practical No 13

-

 Practical No 13 -  Estimate the cost of the project using COCMOII approach for assign project.


Cocomo (Constructive Cost Model) is a regression model based on LOC, i.e number of Lines of Code. It is a procedural cost estimate model for software projects and is often used as a process of reliably predicting the various parameters associated with making a project such as size, effort, cost, time, and quality. It was proposed by Barry Boehm in 1981 and is based on the study of 63 projects, which makes it one of the best-documented models.

The key parameters which define the quality of any software products, which are also an outcome of the Cocomo are primarily Effort & Schedule:

  • Effort: Amount of labor that will be required to complete a task. It is measured in person-months units.
  • Schedule: Simply means the amount of time required for the completion of the job, which is, of course, proportional to the effort put in. It is measured in the units of time such as weeks, months.
There are three types of COCOMOII model 

COCOMO consists of a hierarchy of three increasingly detailed and accurate forms. Any of the three forms can be adopted according to our requirements. These are types of COCOMO model:

  1. Basic COCOMO Model
  2. Intermediate COCOMO Model
  3. Detailed COCOMO Model

The first level, Basic COCOMO can be used for quick and slightly rough calculations of Software Costs. Its accuracy is somewhat restricted due to the absence of sufficient factor considerations.

Intermediate COCOMO takes these Cost Drivers into account and Detailed COCOMO additionally accounts for the influence of individual project phases, i.e in case of Detailed it accounts for both these cost drivers and also calculations are performed phase-wise henceforth producing a more accurate result. 


Result: Hence,We have calculated cost of bank management system using COCOMOII.

Popular posts from this blog

Practical No 11

-
 Practical 11 - Identify the risk involve in the project and prepare RMMM plan. A risk management technique is usually seen in the software Project plan. This can be divided into Risk Mitigation, Monitoring, and Management Plan (RMMM). In this plan, all works are done as part of risk analysis. As part of the overall project plan project manager generally uses this RMMM plan.  Risk : Due to the large size of some banks, overexposure to risk can cause bank failure and impact millions of people. By understanding the risks posed to banks, we can set better regulations to encourage prudent management and decision-making. The ability of a bank to manage risk also affects investors’ decisions. Even if a bank can generate large revenues, lack of risk management can lower profits due to losses on loans. Value investors are more likely to invest in a bank that is able to provide profits and is not at an excessive risk of losing money. Risk Mitigation :   It is an activity used to avoid problems
Read more

Practical No 7

-
Image
 Develop a activity diagram to represent a flow from one activity to anotyher for software develpment Activity diagram for Bank management system Activity diagram is basically a flowchart to represent the flow from one activity to another activity. The activity can be described as an operation of the system. The control flow is drawn from one operation to another. This flow can be sequential, branched, or concurrent. Activity diagrams deal with all type of flow control by using different elements such as fork, join, etc.i t captures the dynamic behavior of the system. The purpose of an activity diagram can be described as − Draw the activity flow of a system. Describe the sequence from one activity to another. Describe the parallel, branched and concurrent flow of the system. Result - Hence,We have developed activity diagram to represent the flow of one activity to another for bank management system.
Read more

Practical No 12

-
 Practical No 12 -  Evaluate the size of a project using functional point metric for the assign project. Estimation of the size of the software is an essential part of Software Project Management. It helps the project manager to further predict the effort and time which will be needed to build the project. Various measures are used in project size estimation.  Function Point Analysis:  Is the method in which, the number and type of functions supported by the software are utilized to find FPC(function point count). The steps in function point analysis are:    Count the number of functions of each proposed type. Compute the Unadjusted Function Points(UFP). Find Total Degree of Influence(TDI). Compute Value Adjustment Factor(VAF). Find the Function Point Count(FPC). The explanation of the above points is given below:    Count the number of functions of each proposed type:  Find the number of functions belonging to the following types:  External Inputs: Functions related to data entering t
Read more