Using software metrics in the evaluation of a conceptual component model

Céret, Éric; Dupuy-Chessa, Sophie; Godet-Bar, Guillaume

doi:10.1109/rcis.2010.5507320

Cited by 4 publications

(7 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Details concerning HCI design were also addressed in [7]. The quality of the analysis model that the method enables developers to produce was evaluated in [5]. Fig.…”

Section: History Of the Symphony Methodsmentioning

confidence: 99%

“…Although the software development practices presented in this section emanate from a specific development method, evaluations made in previous work [5] lead us to believe that the software architecture these practices enable developers to build may be used outside of the method's scope.…”

Section: Figure 3: Organization Of the Symphony Objects Of The Teamavmentioning

confidence: 99%

“…We have proposed in past papers [11,10,5,12] our own contribution to this problem: the Extended Symphony Method, whose relevance for efficiently bridging the gap between Software Engineering, Information Systems and Human-Computer Interaction development practices was demonstrated. At the analysis and design levels, our method suggests using a specific combination of architectural patterns for building the application's business and interaction abstract logics, and for designing clearly distinct technical layers (e.g., for implementing the actual graphics), called the Symphony Architecture.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Sonata: Flexible connections between interaction and business spaces

Godet-Bar

Dupuy-Chessa

Rieu

2012

Journal of Systems and Software

View full text Add to dashboard Cite

Every interactive system features a functional core and a user interface. Over the years, several types of software architectures for connecting these conceptual elements have been proposed, all of which fail to conciliate two essential qualities: enabling both business and interaction objects reuse, and limiting the amount of communication-specific code in reusable objects. We have described in previous work the Symphony Architecture, which bridges the gap between the interaction and business spaces, while requiring no code overhead in either business or interaction objects. Resulting development features minimal coupling between technology-agnostic business and interaction constructs, called Symphony Objects, and improves their reusability by clearly isolating them from the applicative logic and from technical objects. In this paper, we present an original software framework, called Sonata, which capitalizes on the conventions used for building and organizing Symphony Architecture instances, for minimizing the amount of configuration required for setting up connections between the business and interaction spaces.

show abstract

“…Details concerning HCI design were also addressed in [7]. The quality of the analysis model that the method enables developers to produce was evaluated in [5]. Fig.…”

Section: History Of the Symphony Methodsmentioning

confidence: 99%

Section: Figure 3: Organization Of the Symphony Objects Of The Teamavmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Sonata: Flexible connections between interaction and business spaces

Godet-Bar

Dupuy-Chessa

Rieu

2012

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…We use this approach to evaluate a new component model, called Symphony Objects model, because we hypothesised the existence of a causal relationship between the characteristics of our conceptual model (the Symphony Objects model) and the characteristics of the code. Then we try to evaluate the Symphony Objects model through the quality of several of its implementations (Ceret, 2010).…”

Section: Methods Validation Practicesmentioning

confidence: 99%

Towards a Community for Information System Design Validation

2010

Proceedings of the 12th International Conference on Enterprise Information Systems

View full text Add to dashboard Cite

Information systems become ubiquitous. This opens a large spectrum of possibilities for end-users, but the design complexity is increasing. So domain specific languages are proposed sometimes supported by appropriate processes. These proposals are interesting but they are under-validated. Even if validation is a difficult task, which requires specific knowledge, we argue that validation should be systematic. But many problems remain to be considered to achieve this goal: 1) computer scientists are often not trained to evaluation; 2) the domain of information systems design validation and evaluation is still under construction. To cope with the first problem, we propose to capitalize evaluation practices into patterns so that they can be reusable for non-specialists of validation practices. For the second issue, we propose an environment where evaluation specialists and engineering methods specialists can work together to define their common and reusable patterns.

show abstract

“…But it was still a theoretical proposal that needed to be confronted to practical issues. Then we realized empirical studies focused on specific parts of the method [2]. One of them is presented in this article.…”

Section: Introductionmentioning

confidence: 99%