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 the system.
    • External outputs: Functions related to data exiting the system.
    • External Inquiries: They lead to data retrieval from the system but don’t change the system.
    • Internal Files: Logical files maintained within the system. Log files are not included here.
    • External interface Files: These are logical files for other applications which are used by our system.
  • Compute the Unadjusted Function Points(UFP): Categorise each of the five function types like simple, average, or complex based on their complexity. Multiply the count of each function type with its weighting factor and find the weighted sum. The weighting factors for each type based on their complexity are as follows: 
     
Function typeSimpleAverageComplex
External Inputs236
External Output335
External Inquiries343
Internal Logical Files1310
External Interface Files


Result - Hence,We have find size of the project using functional point analysis method
5710





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