Full metadata record
| DC pole | Hodnota | Jazyk |
|---|---|---|
| dc.contributor.author | Brada, Přemysl | |
| dc.date.accessioned | 2016-06-27T07:50:29Z | |
| dc.date.available | 2016-06-27T07:50:29Z | |
| dc.date.issued | 2002 | |
| dc.identifier.uri | http://www.kiv.zcu.cz/publications/ | |
| dc.identifier.uri | http://hdl.handle.net/11025/21622 | |
| dc.format | 40 s. | cs |
| dc.format.mimetype | application/pdf | |
| dc.language.iso | en | en |
| dc.publisher | University of West Bohemia in Pilsen | en |
| dc.rights | © University of West Bohemia in Pilsen | en |
| dc.subject | softwarové inženýrství | cs |
| dc.subject | model | cs |
| dc.title | The ENT model: a general model for software interface structuring: technical report no. DCSE/TR-2002-10 | en |
| dc.type | zpráva | cs |
| dc.type | report | en |
| dc.rights.access | openAccess | en |
| dc.type.version | publishedVersion | en |
| dc.description.abstract-translated | Software modules and components have always played a key role in software engineering, primarily as key abstractions that embody the principle of information hiding, using separation of interface and implementation. In most module- and component-based systems, the specification of the interface therefore plays an important role. This paper presents a model for structuring module interfaces (called the ENT model) which allows their multi-faceted views and analyses. The design of the model is motivated by two factors. First, we feel a need to unify the variety of approaches to module- and component-based software descriptions. Secondly, we want to provide a vehicle for modeling the different roles which the features on module/component interface play for the players in software composition (users, developers, tools). The model uses a classification of module’s features according to their purpose as perceived by human users. The feature declarations are consequently grouped by their classification properties in a hierarchy of named sets called traits and categories. This structuring allows us to analyse module interface in the same way as the users do. Perhaps more interestingly, it provides a way to formally define the split of the interface into sets of provided and required features. Besides the model definition itself, we provide examples of its use for two component frameworks – SOFA components and CORBA Component Model. The applicability of the model in other situations is also discussed, and its possible usages are presented. | en |
| dc.subject.translated | software engineering | en |
| dc.subject.translated | model | en |
| Vyskytuje se v kolekcích: | Zprávy / Reports (KIV) | |
Soubory připojené k záznamu:
| Soubor | Popis | Velikost | Formát | |
|---|---|---|---|---|
| Brada.pdf | Plný text | 423,78 kB | Adobe PDF | Zobrazit/otevřít |
Použijte tento identifikátor k citaci nebo jako odkaz na tento záznam:
http://hdl.handle.net/11025/21622Všechny záznamy v DSpace jsou chráněny autorskými právy, všechna práva vyhrazena.