Capacity planning and performance modeling: from mainframes to client-server systems
Capacity planning and performance modeling: from mainframes to client-server systems
Database processing (5th ed.): fundamentals, design, and implementation
Database processing (5th ed.): fundamentals, design, and implementation
ACM SIGMOD Record
The Unified Modeling Language user guide
The Unified Modeling Language user guide
The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
Deriving a queueing network based performance model from UML diagrams
Proceedings of the 2nd international workshop on Software and performance
Performance Engineering of Software Systems
Performance Engineering of Software Systems
Fundamentals of Database Systems
Fundamentals of Database Systems
Selected Issues in Object-oriented Database Design
BT Technology Journal
Expressing UML Class Diagrams Properties with OCL
Object Modeling with the OCL, The Rationale behind the Object Constraint Language
EDOC '05 Proceedings of the Ninth IEEE International EDOC Enterprise Computing Conference
A Framework for Design Tradeoffs
Software Quality Control
From annotated software designs (UML SPT/MARTE) to model formalisms
SFM'07 Proceedings of the 7th international conference on Formal methods for performance evaluation
Applying the UML class diagram in the performance analysis
EPEW'06 Proceedings of the Third European conference on Formal Methods and Stochastic Models for Performance Evaluation
Hi-index | 0.00 |
A data model, or UML class diagram of a software system, is of central importance to the computing time and the disk usage a software system exhibits. It can be normalized or denormalized to better utilize the components of a computer system or to offer acceptable performance values.This paper describes an approach to software performance analysis that is based on the UML class diagram. It predicts the performance values for use cases operating on persistent data collections as well as whether and how much normalization or denormalization a UML class diagram may need, in order to ensure that these use cases meet their performance objectives.