Spelling suggestions: "subject:"feature diagrams"" "subject:"feature iagrams""
1 |
Programų sistemų variantiškumo modelių, aprašytų požymių diagramomis, tyrimas / Research of Software System Variability Models Described Using Feature DiagramsKreivys, Deividas 25 August 2010 (has links)
Požymis – tai savitas, charakteringas sistemos atributas. FODA (angl. Feature Orented Domain Analysis) požymius apibūdina kaip žinomas, savitas bei vartotojui matomas sistemos charakteristikas, tuo tarpu funkcijos, objektai ir aspektai yra naudojami apibūdinti vidines sistemos detales. Požymių modeliavimas susitelkia ties labai matomų išorinių produkto charakteristikų apibūdinimu, kalbant apie produkto bendrumą bei variantiškumą, o ne apie detalų sistemos apibūdinimą. Požymių modeliavimo rezultatas yra požymių diagramos. Tai yra grafinė kalba naudojama atvaizduoti bei modeliuoti sistemos arba komponento variantiškumus aukštesniame abstrakcijos lygyje, daţniausiai pradiniuose projektavimo lygiuose, tokiuose kaip reikalavimų specifikavime kuriant programinę įrangą. Šiame darbe atliekamas programų sistemų variantiškumo modelių aprašytų požymių diagramomis tyrimas specifikavimo, sintaksės validavimo, sudėtingumo įvertinimo ir konfigūravimo aspektais. Darbe aprašomas autoriaus (bendraautorius: P. Žaliaduonis) sukurtas požymių modeliavimo įrankis leidžia vartotojui specifikuoti, modeliuoti, validuoti, įvertinti ir dokumentuoti programų sistemos produktų linijos požymių variantiškumo modelius. / Feature Modeling is a domain modeling technique used in software product line development and generative software engineering that addresses the development of reusable software. A feature model defines common and variable elements of a family of software systems or products of a product line – the domain. It can be used to derive members of the system family built from a common set of reusable assets. The concept of product line, if applied systematically, allows for the dramatic increase of software design quality, productivity, provides a capability for mass customization and leads to the „industrial‟ software design. In this work, the author describes the way of product line variability specification using feature diagrams. The presented approach deals with specification of feature model elements, syntax validation, complexity evaluation and feature diagram configuration aspects. The developed software, described in this thesis, allows the user to specify features, design, validate, evaluate and document system product line variability models.
|
2 |
Quality of Feature Diagram Languages: Formal Evaluation and Comparison.Trigaux, Jean-Christophe 27 September 2008 (has links)
In software engineering, software reuse has been a popular topic since 1968. Nowadays, Software Product Line (SPL) engineering promotes systematic reuse throughout the whole software development process. Within SPL, reusability strongly depends on variability. In this context, variability modelling and management are crucial activities that crosscuts all development stages. Different techniques are used to model variability and one of them is Feature Diagrams (FDs). FD languages are a family of popular modelling languages used to model, and reason on, variability. Since the seminal proposal of a FD language, namely FODA, many extensions have been proposed to improve it. However, the pros and cons of these languages are difficult to evaluate for two main reasons: (1) most of them are informally defined and (2) no well defined criteria were used to justify the extensions made to FODA. As a consequence, variability modelling and management techniques proposed in the literature or used by practitioners may be suboptimal.
Globally, this work underlines that the current research on FDs is fragmented and provides principles to remedy this situation. A formal approach is proposed to introduce more rigour in the motivation, definition and comparison of FD languages. Thereby, examining their qualities should be more focused and productive. A formal approach guarantees unambiguity and is a prerequisite to define formal quality criteria and to produce efficient and safe tool automation. A quality analysis is necessary to avoid the proliferation of languages and constructs that are an additional source of misinterpretations and interoperability problems. The creation or selection of a FD language should be driven and motivated by rigourous criteria. Translations from one FD language to another should be defined and carefully studied to avoid interoperability problems.
The main contributions of this work are: (1) to use a quality framework to serve as a roadmap to improve the quality of FD languages, (2) to formally evaluate and compare FD language qualities according to well-defined criteria and following a clear method, (3) to formally define and motivate a new FD language that obtains the best scoring according to the quality criteria and (4) to develop tool support for this language.
|
Page generated in 0.0649 seconds