The aim of this document is to propose an initial set of rules to be applied in the evaluation of the Object Oriented (OO) Function Points (OOFP) computed on an object oriented analysis or design model (OOFPD) (in the following OMT notation will be assumed for the models). To derive from the function points (FP) methodology a measurement bethod working for OO software, sme analogies have to be drawn to better understand how the well established FP technology can be modified to cope with non-transactional code. The advantage of appliying the well known and consolidata FP aproach is clear: the enormous experience derived from traditional software development processes can be reused in thenew OO aproach. In sustems developed with traditional non-OO approaches the central conceptual entities to define and evaluate system sizing are files or better, as stated by FP counting rules, the logical files and transactions operating on those files. However in OO systems the core concept is no longer related to data base issues, mass storage, etc. rather the new central paradigm of the approach is the 'object'. The central analogy used to map FP to OO sofrware relates comcepts and attributes traditionally referred to files to objects. Therefore: * Internal Logical Files (ILF) <--> Objects belonging to the application considered; * External Interface Files (EIF) <--> Objects not belonging to the application considered but 'used' (by method invocation or data member reference) by the application objects; * Transactions <--> methods belonging to the classes internal to the application
Development Effort Measurement for Object-Oriented Software [DEMOS]: Deliverable D1.1.1 Survey of the state of the art in size/complexity, effort, duration and quality estimation and assessment (D1.1.1, D1.2.1, D2.2.1)
1997-01-01
Abstract
The aim of this document is to propose an initial set of rules to be applied in the evaluation of the Object Oriented (OO) Function Points (OOFP) computed on an object oriented analysis or design model (OOFPD) (in the following OMT notation will be assumed for the models). To derive from the function points (FP) methodology a measurement bethod working for OO software, sme analogies have to be drawn to better understand how the well established FP technology can be modified to cope with non-transactional code. The advantage of appliying the well known and consolidata FP aproach is clear: the enormous experience derived from traditional software development processes can be reused in thenew OO aproach. In sustems developed with traditional non-OO approaches the central conceptual entities to define and evaluate system sizing are files or better, as stated by FP counting rules, the logical files and transactions operating on those files. However in OO systems the core concept is no longer related to data base issues, mass storage, etc. rather the new central paradigm of the approach is the 'object'. The central analogy used to map FP to OO sofrware relates comcepts and attributes traditionally referred to files to objects. Therefore: * Internal Logical Files (ILF) <--> Objects belonging to the application considered; * External Interface Files (EIF) <--> Objects not belonging to the application considered but 'used' (by method invocation or data member reference) by the application objects; * Transactions <--> methods belonging to the classes internal to the applicationI documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.
