Feature modelling of component-based embedded software

Kalaoja, Jarmo; Niemelä, Eila; Perunka, Harri

doi:10.1109/step.1997.615534

Cited by 6 publications

(2 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Features should be well-known by both customers and designers and can be functional (services or operations) and nonfunctional (capacity, usage, cost, and other quality attributes) [67]. [43], aspect-oriented programming [73], generative programming [22], product line software engineering [20,67,68], reengineering [85,86], object oriented software engineering [66,72,90], component based systems [63,65,88,110,115,117], feature oriented programming [6].…”

Section: Design Structure Matrixmentioning

confidence: 99%

See 1 more Smart Citation

Systematic Component-Oriented development with Axiomatic Design

Togay

Doğru

Tanik

2008

Journal of Systems and Software

View full text Add to dashboard Cite

In this research, component oriented development is supported with design guidance by extending the Axiomatic Design Theory for component orientation, and utilizing domain engineering and ontology mechanisms. Guidance is offered in the form of suggesting missing components and discovering incompatibilities among the candidate elements of software development, corresponding to different phases such as requirement analysis, design, and implementation. A mature domain concept is developed suggesting the availability of reference models for customer needs, software system requirements, software design, and also a rich set of implemented components. As the system is being defined starting with the customer needs and progressing towards components, at every step the developer is presented what is available in the domain and what becomes unavailable. This guidance is based on the selections made so far, utilizing ontology based constraint checking. Feature Models are incorporated for modeling customer needs. Case studies are presented for demonstration purposes.

show abstract

Section: Design Structure Matrixmentioning

confidence: 99%

“…Similar approach proposed for Service Oriented Architectures with utilizing OWL. Therefore there is a direct connection between features and components such as defined in [63,65]. In [63], many-to-many relationship is identified between features and components thus a feature-based component selection is targeted.…”

Section: Design Structure Matrixmentioning

confidence: 99%