Integration of Extra-Functional Properties in Component Models

Sentilles, Séverine; Štěpán, Petr; Carlson, Jan; Crnković, Ivica

doi:10.1007/978-3-642-02414-6_11

Cited by 33 publications

(12 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• The non-functional requirements should be assignable to different system parts, i.e. not only the application itself but also subcomponents or services [27]. This means that NFRs and NFPs differ in scope and applicability and it should be possible to attach them to the most suitable system part.…”

Section: Challengesmentioning

confidence: 98%

See 1 more Smart Citation

A Middleware for Managing Non-Functional Requirements in Cloud PaaS

Braubach¹,

Jander²,

Pokahr³

2014

2014 International Conference on Cloud and Autonomic Computing

View full text Add to dashboard Cite

A key aspect of distributed applications in platformas-a-service clouds revolves around the definition of requirements for quality of service and the most efficient use of the available resources to achieve them. Matching both the requirements and resources represents a unique challenge: While requirements are generally defined in relatively abstract form and defined as system-wide parameters, the resources are concrete, low-level entities that, by themselves, are only of marginal influence on the requirements. In order to establish a relationship between these two requires both the agglomeration of properties into more abstract ones as well as refining requirements in more detailed, concrete ones, both of which can often only be done to a certain degree. This paper presents a vision how both aspects can be brought to the same level and introduces an approach enhancing component-based cloud applications with non-functional properties in the context of an integrated programming model. This allows developers of such applications to formally declare properties that may influence the application during runtime and document the expectations regarding non-functional aspects of the overall system. This can be used to ensure the health of the application and, in case requirements are violated, actions like the deployment of additional resources can be performed in order to alleviate any degradation of its non-functional state, either by evaluating, choosing and performing pre-defined actions automatically or by manual administrative intervention.

show abstract

Section: Challengesmentioning

confidence: 98%

“…E.g. in an approach presented in [27], non-functional component properties are first estimated by the developer and later on measured at runtime. During component assembly of new applications, the previously recorded values can be used for component selection and for checking that properties hold by aggregating values using verifiers.…”

Section: Related Workmentioning

confidence: 99%

A Middleware for Managing Non-Functional Requirements in Cloud PaaS

Braubach¹,

Jander²,

Pokahr³

2014

2014 International Conference on Cloud and Autonomic Computing

View full text Add to dashboard Cite

show abstract

“…What particularly distinguishes Pride from other modelling tools is the support for managing extra-functional properties through the attribute framework [12]. Every component can include a collection of structured attributes defining simple or complex types of properties such as behavioural and resource models, certain dependability measures, different timing attributes and documentation.…”

Section: Software Architecturementioning

confidence: 99%

PRIDE - An Environment for Component-Based Development of Distributed Real-Time Embedded Systems

Borde

Carlson

Feljan

et al. 2011

2011 Ninth Working IEEE/IFIP Conference on Software Architecture

Self Cite

View full text Add to dashboard Cite

Settling down the software architecture for embedded system is a complex and time consuming task. Specific concerns that are generally issued from implementation details must be captured in the software architecture and assessed to ensure system correctness. The matter is further complicated by the inherent complexity and heterogeneity of the targeted systems, platforms and concerns. In addition, tools capable of conjointly catering for the complete design-verificationdeployment cycle, extra-functional properties and reuse are currently lacking. To address this, we have developed Pride, an integrated development environment for component-based development of embedded systems. Pride is based on an architecture relying on components with well-defined semantics that serve as the central development entity, and as means to support and aggregate various analysis and verification techniques throughout the development -from early specification to synthesis and deployment. Pride also provides generic support for integrating extra-functional properties into architectural definitions.

show abstract

“…Model-driven development is also gaining interest for early design and analysis of embedded systems, due to automated environments, such as MathLab SimulinkStateflow [9], and the development of the UML profile for Modeling and Analysis of Real-time and Embedded systems, (MARTE) [11]. In contrast to a component-based approach, this methodology is not centered around the notion of components, and does not focus on reusability.…”

Section: Packaging As Componentsmentioning

confidence: 99%