Using annotations in the naked objects framework to explore data requirements

Authors:
Marcos E. B. Broinizi;João Eduardo Ferreira;Alfredo Goldman
Affiliations:
University of São Paulo, São Paulo - SP - Brazil;University of São Paulo, São Paulo - SP - Brazil;University of São Paulo, São Paulo - SP - Brazil
Venue:
Proceedings of the 2008 ACM symposium on Applied computing
Year:
2008

Citing 9
Cited 0

Database system concepts

Database system concepts
An analysis of SQL integrity constraints from an entity-relationship model perspective

Information Systems
Database modeling and design (3rd ed.)

Database modeling and design (3rd ed.)
Extending the database relational model to capture more meaning

ACM Transactions on Database Systems (TODS)
The entity-relationship model—toward a unified view of data

ACM Transactions on Database Systems (TODS) - Special issue: papers from the international conference on very large data bases: September 22–24, 1975, Framingham, MA
On the relational representation of complex specialization structures

Information Systems
Naked Objects

Naked Objects
Fundamentals of Database Systems (5th Edition)

Fundamentals of Database Systems (5th Edition)
Agile development using naked objects

XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

The creation of conceptual data design that appropriately represents specific application domain is one of the main challenges in requirements engineering. An initiative to help designers is the Naked Objects framework, where it is possible to interact with conceptual model in a limited way. The interactions are restricted to entity creations and single object-relations. We created an extension of the Naked Objects framework using annotations to allow manipulation of higher level abstractions as specialization and object-relationship. These abstractions allow better interactions between the domain specialist and designers. The use of our approach to explore and validate data requirements has several benefits: 1) It reduces conceptual specification problems (like poorly data requirements identification); 2) It narrows the distance among domain and design specialists; 3) It allows the simultaneous exploration of the conceptual data design and the system requirements.