On Feature Orientation and on Requirements Encapsulation Using Families of Requirements

Bredereke, Jan

doi:10.1007/978-3-540-25930-5_3

Cited by 4 publications

(5 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In contrast to the proposal by [7], which is still close to the IN point of view, we distinguish the description of the feature's behaviour from that of the legal use of a feature. Restrictions to behaviours are in fact expressed at a different level, i.e.…”

Section: The Realization Of Each Slg Bases On a Library Of Reusable C...mentioning

confidence: 75%

Service-Oriented Design: The Roots

Margaria

Steffen

Reitenspieß³

2005

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

Service-Oriented Design has driven the development of telecommunication infrastructure and applications, in particular the so-called Intelligent Network (IN) Services, since the early 90s. A serviceoriented, feature-based architecture, a corresponding standardization of basic services and applications in real standards, and adequate programming environments enabled flexibilization of services, and dramatically reduced the time to market. Today the current trend toward triple-play services, which blend voice, video, and data on broadband wireline and wireless services builds on this successful experience when reaching for new technological and operational challenges. In this paper, we review our 10 years of experience in service engineering for telecommunication systems from the point of view of Service-Oriented Design then and now.

show abstract

Section: The Realization Of Each Slg Bases On a Library Of Reusable C...mentioning

confidence: 75%

Service-Oriented Design: The Roots

Margaria

Steffen

Reitenspieß³

2005

Service-Oriented Computing – ICSOC 2007

View full text Add to dashboard Cite

show abstract

“…We learned to appreciate the concept and the use of features in the context of Intelligent Networks [6,7,20], but our notion of features is more general than e.g. what defined in [3], in order to also capture a more general class of services like online, financial, monitoring, reporting, and intelligence services:…”

Section: Features As Modelling Entitiesmentioning

confidence: 99%

“…In the traditional telephony setting, features are understood as modifiers of the base service [3], which are basically executed sequentially,each of them departing and returning to the base service (the so called "daisy" or sequential model of execution [16]). In web-based applications, the proportion between base system and features is more extreme: web services have a minimal skeleton service, and are almost completely constituted by features.…”

Section: Features As Modelling Entitiesmentioning

confidence: 99%

See 1 more Smart Citation

Feature-based Modelling of a Complex, Online-Reconfigurable Decision Support Service

Karusseit

Margaria²

2006

Electronic Notes in Theoretical Computer Science

View full text Add to dashboard Cite

“…In order to make the complexity of modern software systems manageable their functionality is increasingly being decomposed into features. A feature is a set of logically-related requirements and their specifications, intended to deliver a particular behavioural effect [16], [17], [76], [88]. A feature often delivers tangible end user value [44].…”

Section: Introductionmentioning

confidence: 99%

Feature interaction: the security threat from within software systems

Nhlabatsi¹,

Laney²,

Nuseibeh³

2008

Prog. Inform.

View full text Add to dashboard Cite

Security engineering is about protecting assets from harm. The feature interaction problem occurs when the composition of features leads to undesirable system behaviours. Usually, this problem manifests itself as conflicting actions of features on a shared context. Security requirements may be violated by feature interactions creating security vulnerabilities which can potentially be exploited by attackers. In this paper, we discuss the feature interaction problem and some of its possible implications for security requirements. The paper concludes that (1) the detection of the violation of security requirements by feature interactions is not different from other types of requirements-what differs is the impact of such violation; and (2) feature interaction detection approaches can be used as a means for vulnerability analysis.

show abstract

On Feature Orientation and on Requirements Encapsulation Using Families of Requirements

Cited by 4 publications

References 19 publications

Service-Oriented Design: The Roots

Service-Oriented Design: The Roots

Feature-based Modelling of a Complex, Online-Reconfigurable Decision Support Service

Feature interaction: the security threat from within software systems

Contact Info

Product

Resources

About