Title: Sizing software with testable requirementsArticle SummaryWithout measuring the cost, the project cannot be managed. In order to size the project, testable requirements can be used. Testable requirements involve a new software measurement paradigm. Certain attributes and applications must be identified. In industry, sizing measurements are generally used to standardize different sizing measurements, so they can be compared. Additionally, without sizing the project, productivity statistics cannot be obtained. There are other factors that would be attributes when sizing progress measurement, earned value, risk identification and change management. The most widely used sizing metrics are Lines of Code (LOC) and Function Points (FP). LOC is measured by the size of the system with respect to the number of programming states involved. This is a heavy reliance on the technology used to build the system. Unlike LOC, function points (FP) are a measure of system functionality. This is very 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 must have the same measurement standards. Once the high-level functional requirements are identified, they could be broken down into granular/precise requirements. The specific requirement can be considered a testable requirement. A testable requirement must be able to be tested by one or more test cases....... middle of paper ...... this requirement can be identified if the requirement can be tested by one or more test cases. This is a vague statement that requires further clarity. Overall, the author has well defined the testable requirements for sizing the project, but it needs to be improved with more clarity and detail. Citation -: 1. Quality Assurance Institute, Establishing a Software Defect Management Process, Quality Assurance Institute Research Report No. 8, 1995. Auerbach Publications, © 2000 RC Press LLC2. Wilson, P., Testable Requirements—An Alternative Measure of Software Sizing, Journal of the Quality Assurance Institute, October 1995, 3-11.3. Jones, C., Applied Software Measurement, McGraw-Hill, New York, 1991.4. Jones, C., Sizing up software, Scientific American, December 1998.5. Chicago Quality Assurance Association Presentation, November 22, 1996, Chicago, Illinois.