Website production It includes design, software program, etc. It is quite difficult to predict the scale of software application, and the estimation results are not very accurate. Only when the requirements come out can we use the function point indicators to measure the most applied scale, but it was too late for the initial software cost estimation and schedule planning. If similar applications do exist, the scale of source code can only be obtained through similar applications. However, between 2008 and 2009, new methods for analyzing the application scale of software have emerged. Today, the International Software Benchmarking Group (ISBSG) has reached a critical scale, with historical data of more than 5000 software applications. Therefore, we can obtain reliable data of similar software applications from ISBSG.
Since many applications are very similar to existing applications, obtaining scale data of similar applications from ISBSG has become a standard activity in the early stage of the project. The data to be obtained also includes progress and cost information, which is even more valuable than the size of the application. However, ISBSG data supports function point indicators rather than code line indicators. Since it is a best practice to use function point indicators, it is not appropriate to use code line indicators. This is certainly not a bad situation, but for companies that insist on using code line indicators, they will lose the opportunity to use ISBSG metrics.
For new software or applications that do not use ISBSG data representation, several current methods for quickly estimating the application scale may be appropriate. One is a new method specification based on pattern matching, which can obtain the approximate size of function points and source code, and even other information, such as the number of pages of specifications. In the development process, this method can also predict the growth rate of demand, but forecasting the growth rate of demand has always been a weak link in software projects. Other methods for estimating the scale include various new function point approximations or "lightweight" function point analysis. These methods can predict the scale of function points in just a few minutes, rather than at a normal speed (about 400 function points per day). Early and timely estimation of application scale is the premise of accurate estimation. It is also the premise of risk analysis. Many risks are proportional to the size of the application, so the earlier you know the size of the application, the better you can get the wind rank analysis.
Since the progress and cost of the project are proportional to the scale of the application, large systems usually divide the system into multiple versions, which are iterated almost every 12-19 months. Knowing the overall scale of the application and the scale of individual functions and features, we can specify an effective version strategy, which may involve three to four consecutive versions. After knowing the size of each version, it is easy to accurately estimate the progress and cost of the project. Before obtaining the requirements, we can obtain the application scale through pattern matching. This method is to obtain the external description of the software application first, and then match other similar applications according to the description. The fast function point method may differ in time. To accurately estimate the scale of the application, at least some requirements of the application need to be obtained.
