Title: Software Sizing with Verifiable RequirementsArticle SummaryWithout measuring costs, the project cannot be managed. Verifiable requirements can be used to size the project. Testable requirements imply a new software measurement paradigm. There are some attributes and applications that need to be identified. In the industry sizing measurements are generally used to normalize different sizing measurements, so they can be compared. Furthermore, without project sizing it is not possible to obtain productivity statistics. There are other factors that could be attributed when sizing progress measurement, value gained, risk identification and change management. The most commonly used sizing measures are lines of code (LOC) and function points (FP). LOC is measured by the size of the system in relation to the number of programming states involved. This is a high dependency on the technology used to build the system. In contrast to LOC, function points (FP) are a measure of system functionality. It is completely independent of the technology used to develop the system. The use of testable requirements is as follows. According to the IEEE definition, there are six different types of requirements: functional, design, implementation, interface, performance and physical. For sizing purposes, each type of these requirements must be considered, and each should have the same measurement standards. Once high-level functional requirements are identified, these could be broken down into granular/fine-grained requirements. The precise requirement can be considered a verifiable requirement. A testable requirement should be able to be tested by one or more test cases....... half of the document ......this requirement can be identified if the requirement can be tested by one or more test cases. This is a vague statement and needs more clarity. Overall the author has defined the verifiable requirements for project sizing well, however it needs to be improved with more clarity and detail. Quote -:1. Quality Assurance Institute, Defining a Software Defect Management Process, Research Report No. 8 of the Institute for Quality Assurance, 1995. Auerbach Publications, © 2000 RC Press LLC2. Wilson, P., Testable Requirements: An Alternative Software Sizing Measure, Journal of the Quality Assurance Institute, October 1995, 3–11.3. Jones, C., Applied Software Measurement, McGraw-Hill, New York, 1991.4. Jones, C., Software Sizing, Scientific American, December 1998.5. Chicago Quality Assurance Association Presentation, November 22, 1996, Chicago, IL.