Title : Sizing Software with Testable Requirements
Article summary
Without measuring the cost the project cannot be managed. In order to size the project the testable requirements can be used . The Testable requirements implies a new software measurement paradigm. There are some attributes and applications which needs to be identified.
In the industry the sizing measures are generally used to normalize the different sizing measures ,hence it can be compared . Further without a sizing the project the productivity statistics cannot be obtained. There are other factors which would be attributes when sizing progress measurement, earned value, risk identification, and change management.
Mostly widely used sizing measures are lines of code (LOC) and function points (FP). LOC is a measured by the size of the system which regard to numbers of programming states involved. This is a high dependency with the technology which has been used to build the system. Contrary to LOC, function points (FP) is a measure of by the functionality of the system. It is very much independent of the technology which has been used to develop the system. The use of testable requirements is as follows. As per the definition of IEEE there are six different types of requirements: functional, design, implementation, interface, performance, and physical. For the purposes of sizing,
each type of these requirements must be considered and each should have the same measurement standards.
Once high level functional requirements are identified, it could be decomposed into granular / precise requirements. The precise requirement can be considered as testable requirement. A testable requirement should be able to tested by one or more test cases.
...
... middle of paper ...
...se requirement can be identified if the requirement can be tested by one or more test cases. This is a vague statement and need more clarity.
Overall the author has defined the testable requirements for sizing project well however it needs to be improved with more clarity and details.
Citation -:
1. Quality Assurance Institute,Establishing a Software Defect Management Process , Quality Assurance Institute Research Report #8, 1995. Auerbach Publications , © 2000 RC Press LLC
2. 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., Sizing up software, Scientific American , December 1998.
5. Chicago Quality Assurance Association presentation, November 22, 1996, Chicago, IL.
Phadnis, S. (2006). Selection of project metrics. iSixSigma. Retrieved on 16 August, 2006 from Website: http://www.isixsigma.com/library/content/c011008a.asp
The project has to assemble a set of requirements drafted out before hand, which will be used to decide if the overall result meets the satisfactory conclusion. The requirements are split into two categories, the so-called functional that will state what the system will do and the non-functional that will enunciate how the system will do it.
Sommerville, I. and Sawyer, P. (2000) Requirements Engineering: A good practice guide. Chichester: Lancaster University.
Business requirements are gathered in this stage. This stage is the main focus of the project managers and stake holders. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the main project approach and to conduct product feasibility study in the economical, operational and technical areas. You identify needs of the software. This is the vital stage, because bad investigation may lead to the project
The team implementing the new system were required to do both functional and systematic requirements thus affecting the implementation of the new system
Gautham, R. N. (2009). Testing processes in business-critical chain software lifecycle. Software Engineering, 2009. WCSE '09. WRI World Congress on (Volume:4 ) , 5.
Once customer requirements have been captured and analyzed, information of customer requirements needs to be translated into functional specifications and design. This activity involves marketing function, product designers and engineers.
Abstract— Software testing is very important element in various product accuracy. Software testing is set of activities conducted with the intent of finding errors in software. It also verifies and validate whether the program is working correctly with no bugs no not. There are basically three levels of testing- Unit, Integration and System. Unit testing referred to as testing in small whereas Integration and System testing are referred to as testing in large. Various testing techniques available for designing of test cases. This paper basically deals with various techniques available to design software testing test cases.
Because the risk is determined by the degree of difficulty in the quantitative measures established for cost and schedule. The director or planner, and more powerful, the customer should understand and realized the reality of variability in software requirements means of instability in cost and schedule (Sommervill, 2009).
Requirement analysis is a very important and one of the fundamental stages in SDLC. It is carried out by the senior members of a team with the given inputs from customers, the sales department, domain experts and market surveys in the industry. This information is utilized to plan an approach to initiate the basic project and to conduct a product feasibility study in the various areas such as economical, operational, and technical.
Here we test the system function manner that can be reasonably expected by the customer, the system was tested against system requirement specification.
A documentation framework is essential for any large project; hence, RUP describes how to document functionality, constraints, design decisions and business requirements. Use Cases and Scenarios, are examples of artifacts prescribed by the process and have been found to be very effective at both capturing functional requirements and providing coherent threads throughout the development and deployment of the system.
Our aim is to monitor the risks areas for early detection of errors and also to ensure the management awareness of risks. The main objectives is to generate accurate estimates for modifying and integrating existing software and thereby developing the software at the expected productivity rate. The project will also look into the ability to estimate the proper size of the software development and integration effort where the known state of the software level requirements are collected at the time of estimate. The objective also includes the ability to effectively manage the requirements and changes which will result in software size growth. This will adversely affect the scheduled
Project cost management is a strategy which depends on technological tools to measure the productivity and the cost of a project via the complete life cycle of the level projects of the enterprise (PMBOK Guide)
What Information is Relevant when Selecting Software Testing Techniques? By: Vegas, Sira; Juristo, Natalia; Basili, Victor. International Journal of Software Engineering & Knowledge Engineering, Dec2002, Vol. 12 Issue 6, p657, 18p; (AN 9199276)