2009
DOI: 10.1007/s10270-009-0115-6
|View full text |Cite
|
Sign up to set email alerts
|

Formal specification of non-functional properties of component-based software systems

Abstract: Component-based software engineering (CBSE) is viewed as an opportunity to deal with the increasing complexity of modern-day software. Along with CBSE comes the notion of component markets, where more or less generic pieces of software are traded, to be combined into applications by third-party application developers. For such a component market to work successfully, all relevant properties of components must be precisely and formally described. This is especially true for non-functional properties, such as pe… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
20
0

Year Published

2012
2012
2021
2021

Publication Types

Select...
5
2
1

Relationship

3
5

Authors

Journals

citations
Cited by 31 publications
(21 citation statements)
references
References 39 publications
0
20
0
Order By: Relevance
“…Troya et al used the concept of observers in [57,58] to model non-functional properties of systems described by GTSs in a way that could be analysed by simulation. Zschaler had previously discussed modular specification of NFPs in temporal logic in [61]. In [14,58], we have combined these ideas to allow the modular encapsulation of observer definitions in a way that can be reused in different DSL specifications.…”
Section: Discussionmentioning
confidence: 99%
“…Troya et al used the concept of observers in [57,58] to model non-functional properties of systems described by GTSs in a way that could be analysed by simulation. Zschaler had previously discussed modular specification of NFPs in temporal logic in [61]. In [14,58], we have combined these ideas to allow the modular encapsulation of observer definitions in a way that can be reused in different DSL specifications.…”
Section: Discussionmentioning
confidence: 99%
“…In component specification, the non-functional requirements refer to security attributes. However, current CBSD lacks nonfunctional support (Zschaler, 2010). In component or application, the non-functional requirements are equally important as the functional ones (Zschaler, 2010).…”
Section: Motivationmentioning
confidence: 99%
“…In component or application, the non-functional requirements are equally important as the functional ones (Zschaler, 2010). Furthermore, non-functional requirements should be addressed at the early stage of the CBSD to avoid any costly failures in the future (Zschaler, 2010).…”
Section: Motivationmentioning
confidence: 99%
“…It is possible to specify Time Constraints which allow setting lower and upper bounds for delays in these scenarios. Zschaler [11] presents QML/CS, a specification language that is used to model non-functional properties of components and component-based software systems including response time. Alfonso et.al.…”
Section: Modeling Environment For the Dslmentioning
confidence: 99%