Journal of the Brazilian Computer Society · 2004 · 17 citations · 18 references
ComputingComputer ScienceSystems EngineeringSoftware EngineeringSystems ArchitectureSystems DesignApplication ArchitectureComponent-based Software EngineeringFunctional RequirementsSoftware ArchitectureSoftware DesignComponent ArchitectureComponent-based ArchitecturesComponent-based Software DesignMiddlewareMiddleware DesignNon-functional Requirements ModelingSoftware Component ReuseSoftware Components
Abstract This paper presents a comprehensive approach to describe, deploy and adapt component-based applications having dynamic non-functional requirements. The approach is centered on high-level contracts associated to architectural descriptions, which allow the non-functional requirements to be handled separately during the system, design process. This helps to achieve separation of concerns facilitating the reuse of modules that implement the application in other systems. Besides specifying non-functional requirements, contracts are used at runtime to guide configuration adaptations required to enforce these requirements. The infrastructure required to manage the contracts follows an architectural pattern, which can be directly mapped to specific components included in a supporting reflective middleware. This allows designers to write a contract and to follow standard recipes to insert the extra code required to its enforcement in the supporting middleware.
18
Making components contract aware
Antoine Beugnard, Jean‐Marc Jezéquél, Noël Plouzeau et al. · Computer · 1999 · 516 citations
The case for reflective middleware
Fábio Kon, Fábio M. Costa, Gordon S. Blair et al. · Communications of the ACM · 2002 · 342 citations