A METRIC FOR THE SIZE ESTIMATION OF OBJECT-ORIENTED GRAPHICAL USER INTERFACES

2000 ◽  
Vol 10 (05) ◽  
pp. 581-603 ◽  
Author(s):  
G. COSTAGLIOLA ◽  
F. FERRUCCI ◽  
G. TORTORA ◽  
G. VITIELLO
Keyword(s):  
User Interfaces ◽  
Object Oriented ◽  
Software Project ◽  
Size Estimation ◽  
Interactive Applications ◽  
Planning Software ◽  
Function Point ◽  
Size Measure ◽  
Critical Components ◽  
Class Point

In order to achieve quality products with reliable cost and effort estimations, one of the main tasks for planning software project development is size estimation. This is especially true when dealing with interactive applications which represent critical components in a software project. In the paper, we address the problem of the size estimation of interactive graphical applications developed using the object-oriented methodology. In particular, we define and validate a metric, the Class Point metric, for estimating the size of object-oriented GUIs. The method is based on the idea of quantifying classes in a program analogous to function counting performed by the function point metric. Theoretical validation has proven the consistency of the Class Point metric as size measure. Empirical validation provides evidence that the Class Point metric is a useful measure for OO software size.

DEVELOPMENTAL SIZE ESTIMATION FOR OBJECT-ORIENTED SOFTWARE BASED ON ANALYSIS MODEL

2013 ◽  
Vol 23 (03) ◽  
pp. 289-308 ◽  
Author(s):  
CHAMUNDESWARI ARUMUGAM ◽  
CHITRA BABU
Keyword(s):  
Software Development ◽  
Object Oriented ◽  
Use Case ◽  
Size Estimation ◽  
Model Function ◽  
Analysis Phase ◽  
Point Analysis ◽  
Function Point ◽  
Model Components ◽  
Use Case Model

Software size estimation at the early analysis phase of software development lifecycle is crucial for predicting the associated effort and cost. Analysis phase captures the functionality addressed in the software to be developed in object-oriented software development life-cycle. Unified modeling language captures the functionality of the software at the analysis phase based on use case model. This paper proposes a new method named as use case model function point to estimate the size of the object-oriented software at the analysis phase itself. While this approach is based on use case model, it also adapts the function point analysis technique to use case model. The various features such as actors, use cases, relationship, external reference, flows, and messages are extracted from use case model. Eleven rules have been derived as guidelines to identify the use case model components. The function point analysis components are appropriately mapped to use case model components and the complexity based on the weightage is specified to calculate use case model function point. This proposed size estimation approach has been evaluated with the object-oriented software developed in our software engineering laboratory to assess its ability to predict the developmental size. The results are empirically analysed based on statistical correlation for substantiating the proposed estimation method.

Class point: an approach for the size estimation of object-oriented systems

2005 ◽  
Vol 31 (1) ◽  
pp. 52-74 ◽  
Author(s):  
G. Costagliola ◽  
F. Ferrucci ◽  
G. Tortora ◽  
G. Vitiello
Keyword(s):  
Object Oriented ◽  
Size Estimation ◽  
Object Oriented Systems ◽  
Class Point

scholarly journals Using Actors and Use Cases for Software Size Estimation

Electronics ◽  
2021 ◽  
Vol 10 (5) ◽  
pp. 592
Author(s):  
Radek Silhavy ◽  
Petr Silhavy ◽  
Zdenka Prokopova
Keyword(s):  
Project Planning ◽  
Use Cases ◽  
New Method ◽  
Software Systems ◽  
Software Project ◽  
Use Case ◽  
Size Estimation ◽  
Software Size Estimation ◽  
Use Case Points

Software size estimation represents a complex task, which is based on data analysis or on an algorithmic estimation approach. Software size estimation is a nontrivial task, which is important for software project planning and management. In this paper, a new method called Actors and Use Cases Size Estimation is proposed. The new method is based on the number of actors and use cases only. The method is based on stepwise regression and led to a very significant reduction in errors when estimating the size of software systems compared to Use Case Points-based methods. The proposed method is independent of Use Case Points, which allows the elimination of the effect of the inaccurate determination of Use Case Points components, because such components are not used in the proposed method.

Research on 3D Reconstruction System for Medical Images

2011 ◽  
Vol 464 ◽  
pp. 57-60
Author(s):  
Yong Zhang ◽  
Jun Fang Ni ◽  
Peng Liu
Keyword(s):  
User Interfaces ◽  
Medical Images ◽  
Object Oriented ◽  
Graphical User Interfaces ◽  
Object Oriented Programming ◽  
3D Data ◽  
Efficient Data ◽  
User Friendly ◽  
Process Reconstruction ◽  
Display Technique

In accordance with the object-oriented programming, a system for 3D medical images of reconstruction and display has been designed and implemented. The overall software structure is established based on VC++6.0 and display technique of Open Graphics Library. The functional modules, such as acquisition of encoded 3D data, pre-process, reconstruction and display, are achieved by the design and implementation of customized classes. At last the software system provides user-friendly graphical user interfaces, highly efficient data processing and reconstruction, and rapid capability of graphic display.

scholarly journals Design and Development of Ceramic Information System Based on Object Oriented Programming

2020 ◽  
Vol 4 (1) ◽  
pp. 105-111
Author(s):  
Mari Rahmawati ◽  
Amin Kusniawati ◽  
Rangga Kori Lesmana
Keyword(s):  
Information System ◽  
User Interfaces ◽  
Human Error ◽  
Positive Impact ◽  
Object Oriented ◽  
Object Oriented Programming ◽  
Sequence Diagrams ◽  
Report Generation ◽  
Customer Data ◽  
Entity Relationship

The author designed an object oriented programming based sales application using use case diagrams, activity diagrams, sequence diagrams, deployment diagrams, entity relationship diagrams, logical record structures, and user interfaces. The design of this information system is expected to produce sales application programs ranging from customer data input, input data of goods, input of sales orders, print out of travel documents, print invoices, cash receipts input, print payment receipts to print reports so that sales applications can have a positive impact on the course of business which is built, reducing duplicated functions, and errors caused by human errors. With the design of a sales application, the problems that exist in the manual system can be resolved such as the system will not receive incomplete data, the system can make automatic numbering, and minimize errors that occur due to humans (human error), reduce the amount of paper usage, report generation can done easily and quickly because the data is processed by the system.Keywords: Design, Sales, Object Oriented Programming.

scholarly journals Towards a methodology to estimate cost of object-oriented software development projects

2004 ◽  
Vol 1 (2) ◽  
pp. 173-194 ◽  
Author(s):  
Radoslav Rakovic
Keyword(s):  
Software Development ◽  
Development Process ◽  
A Priori ◽  
Unified Modeling Language ◽  
Object Oriented ◽  
Subsequent Development ◽  
Development Project ◽  
Software Project ◽  
Software Development Project ◽  
Early Estimate

Successful management of a software project, besides a well-defined project development process, requires an early estimate of project complexity. In a prevailing practice, software development costs usually have been determined a posteriori i.e. after software project implementation. It is essential however, to know this estimate a priori, i.e., before commencement of works. This paper presents an attempt to construct a methodology that would enable an early estimate of software development cost and its refinements during subsequent development phases. The methodology assumes an object-oriented approach based on the Unified Modeling Language (UML) and Unified Software Development Process (USDP). It outlines an Use Case Driven Architecture-Centric, Iterative and Incremental estimate process that could significantly improve and simplify early cost estimates. The presented methodology is illustrated on example of the POST software development project.

Sign in / Sign up

Export Citation Format

Share Document