An object-oriented model of measurement systems

This paper presents a general object-oriented model for measurement systems. The limitations of the conventional function-oriented models are examined in the light of the generalized concept of measurement and its theoretical framework proposed previously by the authors. The proposed model identifies five classes of objects, i.e., measured object, measuring instrument, reference standard, human observer, and operating environment. Each is characterized by its own attributes and operations or functions at three levels, i.e., internal, operational, and environmental. The interactions between them are also modeled, including the coupling between the measured object and the measuring instrument, the human-instrument interface, the calibration, and the interference. It serves as both a modeling framework and a practical tool for description, analysis and design, and, in particular, for computer-aided analysis and design of a measuring system. It will find applications in instrumentation engineering and measurement research and education

Integrity Estimation Model: Fault Perspective

An integrity estimation model for object oriented design fault perspective has been proposed in this paper. Integrity has been recognized as a major factor to software security, an importance is being drawn to measure integrity early in development life cycle. No such model has been available in the literature that estimates security of object oriented design by taking fault parameters into consideration. A suit of design metrics useful in measuring integrity of software has been recognized. It becomes more significant in the case of object oriented design fault perspective. In this study a metrics based Integrity Estimation Model (IEMOODF) for object oriented design has been developed and justifying the correlation with the help of experimental tryouts. Finally the developed model ?Integrity Estimation Model? is empirically validated and contextual importance of the study shows the high correlation for proposed model acceptance

Object-oriented productivity metrics

Software productivity metrics are useful for sizing and costing proposed software and for measuring development productivity. Estimating and measuring source lines of code (SLOC) has proven to be a bad idea because it encourages writing more lines of code and using lower level languages. Function Point Analysis is an improved software metric system, but it is not compatible with newer rapid prototyping and object-oriented approaches to software development. A process is presented here for counting object-oriented effort points, based on a preliminary object-oriented analysis. It is proposed that this approach is compatible with object-oriented analysis, design, programming, and rapid prototyping. Statistics gathered on actual projects are presented to validate the approach

Comparison Study and Review on Object-Oriented Metrics

The best elucidations to software development problems are regularly touted as object-oriented processes. The popularity of object-oriented design metrics is essential in software engineering for measuring the software complexity, estimating size, quality and project efforts. There are various approaches through which we can find the software cost estimation and predicates on various kinds of deliverable items. Object-oriented metrics assures to reduce cost and the maintenance effort by serving as early predictors to estimate software faults. Such an early quantification augments the quality of the final software. This paper reviews object-oriented metrics. A comparison table is maintained via which we can analyze the difference between all the object-oriented metrics effectively

Comparative Analysis of Data Redundancy and Execution Time between Relational and Object-Oriented Schema Table

Database design is one of the important phases in designing software because database is where the data is stored inside the system. One of the most popular techniques used in database design is the relational technique, which focuses on entity relationship diagram and normalization. The relational technique is useful for eliminating data redundancy because normalization produces normal forms on the schema tables. The second technique is the object-oriented technique, which focuses on class diagram and generating schema tables. An advantage of object-oriented technique is its close implementation to programming languages like C++ or Java. This paper is set to compare the performance of both relational and object-oriented techniques in terms of solving data redundancy during the database design phase as well as measuring query execution time. The experimental results based on a course database case study traced 186 redundant records using the relational technique and 204 redundant records when using the object-oriented technique. The query execution time measured was 46.75ms and 31.75ms for relational and object-oriented techniques, respectively

Pemeringkatan Software Aplikasi Berdasarkan Properti Kualitas Disain Dan Metrics for Object Oriented Software Menggunakan Analytic Hierarchy Process

Sebuah metode untuk mengukur kualitas desain berdasarkan hasil implementasinya dalam Java source codes diusulkan dalam penelitian ini. Metode yang diusulkan menggabungkan Metrics for Object-Oriented Software Engineering (MOOSE), properti kualitas desain software dan konsep Analytic Hierarchy Process (AHP). Sebagai studi kasus, metode ini diterapkan pada sejumlah aplikasi ERP yang bersifat open source yaitu Adempiere, OpenBravo, Plazma, FreedomERP, dan JAllInOne. Pengukuran MOOSE dilakukan dengan bantuan tool CKJM 1.8. Hasil ukur MOOSE dikelompokkan dalam properti kualitas yaitu efficiency, understandability, reusability, testability dan maintainability. Kombinasi MOOSE dan AHP yang dihasilkan dapat menjadi alat bantu dalam menentukan peringkat kualitas software dari aspek orientasi objek. A method for measuring the quality of the design is based on the results of its implementation in the Java source codes proposed in this study. The proposed method combines Metrics for Object-Oriented Software Engineering (MOOSE), property and the concept of software design quality Analytic Hierarchy Process (AHP). As a case study, this method is applied to a number of applications that are open source ERP is Adempiere, Openbravo, Plazma, FreedomERP, and JAllInOne. MOOSE measurements done with the aid tool CKJM 1.8. MOOSE measuring results are grouped in quality properties that are efficiency, understandability, reusability, testability and maintainability. MOOSE and AHP combination that have been produced can be a useful tool in determining the quality ratings of aspects of object oriented software

PEMERINGKATAN SOFTWARE APLIKASI BERDASARKAN PROPERTI KUALITAS DISAIN DAN METRICS FOR OBJECT ORIENTED SOFTWARE MENGGUNAKAN ANALYTIC HIERARCHY PROCESS

Sebuah metode untuk mengukur kualitas desain berdasarkan hasil implementasinya dalam Java source codes diusulkan dalam penelitian ini. Metode yang diusulkan menggabungkan Metrics for Object-Oriented Software Engineering (MOOSE), properti kualitas desain software dan konsep Analytic Hierarchy Process (AHP). Sebagai studi kasus, metode ini diterapkan pada sejumlah aplikasi ERP yang bersifat open source yaitu Adempiere, OpenBravo, Plazma, FreedomERP, dan JAllInOne. Pengukuran MOOSE dilakukan dengan bantuan tool CKJM 1.8. Hasil ukur MOOSE dikelompokkan dalam properti kualitas yaitu efficiency, understandability, reusability, testability dan maintainability. Kombinasi MOOSE dan AHP yang dihasilkan dapat menjadi alat bantu dalam menentukan peringkat kualitas software dari aspek orientasi objek. A method for measuring the quality of the design is based on the results of its implementation in the Java source codes proposed in this study. The proposed method combines Metrics for Object-Oriented Software Engineering (MOOSE), property and the concept of software design quality Analytic Hierarchy Process (AHP). As a case study, this method is applied to a number of applications that are open source ERP is Adempiere, Openbravo, Plazma, FreedomERP, and JAllInOne. MOOSE measurements done with the aid tool CKJM 1.8. MOOSE measuring results are grouped in quality properties that are efficiency, understandability, reusability, testability and maintainability. MOOSE and AHP combination that have been produced can be a useful tool in determining the quality ratings of aspects of object oriented software