Generating an EXPLAIN plan
Recent Articles
-
Process of Counting Function Points
Function point analysis follows specific steps for counting: Identification of the subsystem boundaries Identification of the data functions (internal logical files and external interface files) Identification of transactional functions (external inputs, external outputs and external inquiries) Calculation of the Unadjusted Function Point (UAF) Count Determination of the Value Adjustment Factor (VAF) using General System Characteristics (GSC) Calculation of the final Function Read More...
-
Objectives of Function Point Analysis
Function Points measure systems from a functional perspective and are independent of technology. Hence, regardless of technology, language, development method, or hardware/software used, the number of function points for a system will remain constant. The variable in Function Point Analysis is the amount of effort required to deliver a given set of function points. Therefore, function point Read More...
-
What is Function point?
A function point is a unit of measurement to express the amount of business functionality an information system provides to a user. Function points are the units of measure used by the IFPUG Functional Size Measurement Method. The IFPUG FSM Method is an ISO recognised software metric to size an information system based on the functionality that is perceived by the user Read More...
-
What is a Test strategy?
A test strategy is a document outline that describes the testing portion of the software development cycle. It is created to inform project managers, testers, and developers about some key issues of the testing process. This includes the testing objective, methods of testing new functions, total time and resources required for the project, and the testing Read More...
-
Guidelines on writing Defect Description
Defect can be expressed as “Result followed by the action”. That means, the unexpected behavior occurring when a particular action takes place can be given as defect description. 1. Be specific. State the expected behavior which did not occur - such as after pop-up did not appear and the behavior which occurred instead. 2. Use present Read More...
-
Search
-
Categories
Archives
- August 2009 (7)
- July 2009 (62)
- June 2009 (752)
- May 2009 (776)
-