PRIETO-DIAZ, R.: `Domain analysis for reusability', Proceedings of COMPSAC'87, 1987  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... a domain of interest [42] In domain analysis, common characteristics from similar systems are generalized, objects and operations that are common to all systems within the same domain and that vary from system to system are identified, and a domain model is defined to describe their relationships [43]. For our purpose, we used the analysis method based on faceted classification suggested in [43] and later improved by Birk [44] Before proceeding, we would like to state that our aim here is far less ambitious than conducting a full fledged domain analysis of expert finding systems (for which ....

.... objects and operations that are common to all systems within the same domain and that vary from system to system are identified, and a domain model is defined to describe their relationships [43] For our purpose, we used the analysis method based on faceted classification suggested in [43] and later improved by Birk [44] Before proceeding, we would like to state that our aim here is far less ambitious than conducting a full fledged domain analysis of expert finding systems (for which we concur the expert finding domain is not mature enough) as is done in software reuse efforts, ....

R. Prieto-Diaz, Domain Analysis for Reusability, inProceedings of COMPSAC87: The Eleventh Annual International Computer Software & Applications Conference, Tokyo, Japan, 1987, pp. 23 --- 29.

....using both kinds of characteristics. Characteristics of an artifact s application context can be expected to be most effective for finding relevant reuse candidates. However, finding an appropriate set of characteristics is not trivial. It requires special techniques known as domain analysis [10, 37, 43]. Most domain analysis work has focused on the reuse of software components only. Domain analysis for other kinds of software engineering artifacts has been addressed by quite a few authors yet (such as [18, 30] If more than one kind of experience is to be reused, either several retrieval ....

....associated with knowledge based systems [24] The different attribute types allow to deal with various degrees of formality. In the beginning of the reuse program, it is often not clear how artifacts should be characterized. Unless a comprehensive pre study and domain analysis work are preferred [10, 37, 43], an initial reuse infrastructure can be built gradually. Text attributes can be used to allow the storage of arbitrary information. However, in general, no meaningful queries are possible (though information retrieval techniques are conceivable) Thus, mainly browsing is possible. However, this ....

R. Prieto-Diaz. Domain analysis for reusability. In Proceedings of the Eleventh Annual International Computer Software and Application Conference (COMPSAC), pages 23--29, 1987.

.... (Lung and Urban 1993) In domain analysis, common characteristics from similar systems are generalized, objects and operations that are common to all systems within the same domain and that vary from system to system are identified, and a domain model is defined to describe their relationships (Prieto Diaz 1987). For our purpose, we used the analysis method based on faceted classification suggested in (Prieto Diaz 1987) and later improved by Birk (1997) Before proceeding, we would like to state that our aim here is far less ambitious than conducting a full fledged domain analysis of expert finding ....

.... and operations that are common to all systems within the same domain and that vary from system to system are identified, and a domain model is defined to describe their relationships (Prieto Diaz 1987) For our purpose, we used the analysis method based on faceted classification suggested in (Prieto Diaz 1987) and later improved by Birk (1997) Before proceeding, we would like to state that our aim here is far less ambitious than conducting a full fledged domain analysis of expert finding systems (for which we concur the expert finding domain is not mature enough) as is done in software reuse efforts, ....

Prieto-Diaz, R. (1987). Domain Analysis for Reusability. In: Proceedings of COMPSAC87: The Eleventh Annual International Computer Software & Applications Conference, Tokyo, Japan: 23 --- 29.

....32 . CURT89] 8 Although the reuse of software components trails what might be achieved, reuse of components alone does not reveal the entire picture about reuse in software development. Prieto Diaz defines two levels of software reuse: 1) ideas and knowledge and 2) artifacts and components. [PRIE87a] Whenever a programmer creates software he is reusing knowledge that he already possesses, whether through training, education, experience, or a combination of these. CURT89] On a larger scale, programming projects reuse a massive amount of knowledge, including software development process ....

....practice for real time software design. Section IV presents a strategy for achieving this objective in concert with domain analysis and modeling. Domain analysis attempts to generalize all systems in an application domain, that is, to produce a domain model that transcends specific applications. [PRIE87a] Although no accepted definition for representing a domain model exists, remarkable similarity can be seen among researchers regarding the content of such a model. Jacobsen and Lindstrom describe a domain model as the set of domain objects (including their attributes and functions) and the ....

[Article contains additional citation context not shown here]

R. Prieto-Diaz, "Domain Analysis For Reusability," IEEE, 1987, pp. 23-29.

....cobbling together a program from a set of software pieces or linking an application with a set of library subroutines, the reality of reuse defies simple description. As a working model of software reuse, Prieto Diaz defines two levels: 1) ideas and knowledge and 2) artifacts and components. [PRIE87a] This is a convenient dichotomy because whenever a programmer creates software he is reusing knowledge he already possesses. CURT89] On a larger scale, programming projects reuse a massive amount of knowledge, including software development process knowledge. Thus, initiatives such as that of the ....

....Two approaches to identifying reusable components are being explored: domain analysis and software re manufacturing. Domain analysis is a front end activity analogous to elicitation, organization, and analysis in the requirements engineering process. See, for example, the work of Prieto Diaz. [PRIE87a]) Since domain analysis forms an integral part of the proposals advanced later in this paper, a discussion of the topic will be deferred until then. Software 21 re manufacturing, however, falls beyond the scope of the proposals made in the present paper, and is, therefore, considered here in the ....

[Article contains additional citation context not shown here]

R. Prieto-Diaz, "Domain Analysis For Reusability", IEEE, 1987, pp. 23-29.

....of applications. Since DA deals with knowledge identification, elicitation, and representation of software products, techniques that systematize these tasks are necessary. One can assume that this is a well resolved situation, since there are several DA approaches found in the technical literature (Prieto, 1987,1993,1994) Cohen, 1991) Neighbors, 1992) Leite, 1994) Gomaa, 1994,1995) Arango et al., 1994) Simos, 1994) Stars, 1996) Jacobson et al., 1997) Griss et al., 1998) However, when considering the issue of knowledge acquisition, these approaches do recognize the importance of this activity, but ....

....in terms of relevance to the domain, explored and registered in a suitable and coherent representation. Under this perspective, two issues are important in order to evaluate the DA approaches: knowledge elicitation and its representation. The analyzed approaches were: Facets and Sandwich Method (Prieto, 1987, 1994) Feature Oriented Domain Analysis (Cohen, 1991, 1994) DRACO (Neighbors, 1992) Leite, 1994) Evolution Domain Life Cycle (Gomaa, 1994, 1995) Arango s DA Generic Process (Arango et al., 1994) ODM (Simos, 1994) Stars, 1996) and RSEB (Jacobson et al., 1997) Griss et al., 1998) Fig. 1. ....

Prieto, R., 1987, "Domain Analysis for Reusability", in: Proceedings of the Eleventh Annual International Computer Software and Applications Conference, pp. 23-29, Tokyo, Japan, Oct.

....a generic component or generator, first we need to extract commonalties, differences and similarities from a domain. The activity that serves for achieving this aim is called domain analysis (DA) The primary goal of DA is to build a domain model. The most general domain model is a domain language (Prieto Diaz, 1990; Iscoe et al. 1991) Many different approaches exist how to perform DA (Batory, 1998b; Neighbors, 1998) The best known example is FODA, the Feature Oriented DA method (Sametinger, 1997) A domain can be treated as well understood one, if a maturity level of domain knowledge is high. That level ....

....in (sub)domains, etc. Among others, the applications related to hardware design with the standard high level domain language VHDL (VHDL Interactive Tutorial, 1996) must be mentioned. For well understood domains, such as mentioned above, a domain language already exists. According to Pietro Diaz (Prieto Diaz, 1990) this is the reuse of analysis of information and it is the most powerful sort of reuse . The standard high level language yields a very broad knowledge for understanding of the domain. As a result, the domain can be subdivided into subdomains and applications. For example, the standard VHDL ....

Prieto-Diaz, R. (1990). Domain analysis for reusability. In W. Tracz (Ed.), Software Reuse: Emerging Technology. IEEE press, pp. 347--353.

....simply classify them under the heading of requirements . Similarly, this process differentiates between the System Architecture and the Software Architecture that is part of it. Another difference between this approach to domain engineering and other domain analysis approaches (e.g. Prieto Diaz[2]) is that case based reasoning and reverse engineering are not central mechanisms for identifying reusable resources, but rather existing applications are used as vehicles to validate the architectures that are derived, top down, from generalized user requirements 2 . At the top most level there ....

R. Prieto-Diaz. Domain Analysis for Reusability. In Proceedings of COMPSAC 87, 1987.

....libraries of components for an application domain. These libraries of components are then accessible by the application engineers working in the specific domain. Prieto Diaz has worked on a method for analyzing a domain with the intent of creating a library of domain specific components [66]. The problems associated with general purpose libraries of components are typically classification and search problems, as the libraries are typically very large. Once the components are created, how do developers know that they exist and where to find them. The developers can t reuse a component ....

....Many of the domain specific software architecture (DSSA) and software technology for adaptable, reliable systems (STARS) projects have been based on the work of Ruben Prieto Diaz and one of the other pioneers in the domain analysis field, who Prieto Diaz has worked with, Guillermo Arango. [28,65,66,67,68,69] The goal of the sandwich method is to specify components that can be implemented and put in a library for future reuse. A classification scheme is produced that aids developers in selecting components to use for their projects. According to Prieto Diaz, the purpose of doing a domain analysis is ....

Prieto-Diaz, R., Domain Analysis For Reusability, in Proceedings of the Eleventh Annual International Computer Software and Application Conference (COMPSAC), pp. 23-29, 1987

....are constructed. The construction of reference components is a domain intensive task. By this, we mean that a domain analysis has to be done, given the domain to which the components to be inserted into the repository belong. Todate, there is no automated means of performing a domain analysis, as [24] states, Domain Analysis is a knowledge intensive activity for which no methodology or any kind of formalization is yet available. An important process in domain analysis is the capture of the essential functionality required in that domain [24] In domain analysis, common characteristics from ....

....means of performing a domain analysis, as [24] states, Domain Analysis is a knowledge intensive activity for which no methodology or any kind of formalization is yet available. An important process in domain analysis is the capture of the essential functionality required in that domain [24]. In domain analysis, common characteristics from systems are captured and generalized. This implies that domain analysis is quite similar to knowledge acquisition, where knowledge has to be elicited from the domain, and encapsulated into the requirements of the system. We have had to elicit the ....

Ruben Prieto-Diaz. Domain analysis for reusability. In R. Prieto-Diaz and G. Arango, editors, Domain analysis and software systems modeling. IEEE Computer Society Press, 1991.

....construction of reusable technologies, and finally, Table 13 sets out the results obtained when comparing different DA methods for the construction of and reusable experiences. DA TECHNIQUES ANALYSIS CLASSIFICATION REPRESENTATION [McCain85] adaptation costs optimum domain decomposition [Prieto Daz87] elements analysis decomposition Simos Populate libraries elements Specify the domain model of a Functionality Functional Features Parameterisation Combinations DA TECHNIQUES TECHNIQUE TECHNIQUE OF VARIABILITY HP Construct Characterise a software domain Functionality ....

R. Prieto-Daz. Domain analysis for reusability. In Proceddings COMPSAC'87, pages 23-29, Tokio, Japan, October 1987.

.... and development histories within a domain of interest (Lung and Urban, 1993) In domain analysis common characteristics from similar systems are generalized, objects and operations common to all systems within the same domain are identified, and a model is defined to describe their relationships (Prieto Siaz, 1987). We used the analysis method based on faceted classification suggested by Prieto Siaz (1987) and later improved by Birk (1997) Before proceeding, we would like to state that our aim is far less ambitious than conducting a full fledged domain analysis of expert finding systems (for which we ....

.... common characteristics from similar systems are generalized, objects and operations common to all systems within the same domain are identified, and a model is defined to describe their relationships (Prieto Siaz, 1987) We used the analysis method based on faceted classification suggested by Prieto Siaz (1987) and later improved by Birk (1997) Before proceeding, we would like to state that our aim is far less ambitious than conducting a full fledged domain analysis of expert finding systems (for which we concur the expert finding domain is not mature enough) as is done in software reuse efforts, ....

Prieto-Diaz, R. (1987): "Domain Analysis for Reusability". In: Proceedings of COMPSAC'87: The Eleventh Annual International Computer Software & Applications Conference, pp: 23 -- 29.

....an analysis of a problem domain. However, there are a number of drawbacks associated with pattern reuse : 1) Pattern reuse can only be applied to individual domains of a wellunderstood and standardised nature. 2) The acquisition of domain information is not a simple task. It has been reported [Prieto Diaz87b] that such a process lacks standardisation and a process model. Prieto Diaz has attempted to address this problem by devising a model domain analysis process, which is currently under investigation. 3) The software generation process produces code several orders of magnitude larger than the input ....

Prieto-Diaz, R. "Domain Analysis for Reusability", Proc. of COMPSAC 1987 - The 11th Annual International Computer Software and Applications Conf., pp.23-29 (1987).

....is an alternate approach better suited to the needs of program understanding. This paper argues that application domain modeling provides such an approach. 1.2. Domains A domain is a problem area. Typically, many application programs exist to solve the problems in a single domain. Arango and Prieto Daz [1991] give the following prerequisites for the presence of a domain: the existence of comprehensive relationships among objects in the domain, a community interested in solutions to problems in the domain, a recognition that software solutions are appropriate to problems in the domain, and a store ....

....that software solutions are appropriate to the problems in the domain, and a store of knowledge or collected wisdom to address the problems in the domain. Once recognized, a domain can be characterized by its vocabulary, common assumptions, architectural approach, and literature. Arango and Prieto Diaz 1991] 10. Domain analysis: is an attempt to identify the objects, operators, and relationships between what domain experts perceive to be important about the domain. Neighbors 1980] 11. Domain model: The domain model should serve as a unified, definitive source of reference when ambiguities ....

[Article contains additional citation context not shown here]

Prieto-Daz, R. (1991), "Domain Analysis for Reusability," In Domain Analysis and Software Systems Modeling, R. Prieto-Daz and G. Arango, Eds., IEEE Computer Society Press, pp. 63-69.

.... Puncello, et al. 37] analogical reasoning Maiden Sutcliffe [30] knowledge based systems Lowry [26] Tamai [41] Borgida [6] Lubars Harandi [28, 29] Zeroual [44] analysis patterns Fowler [13] domain mapping Simos, et al. 39] Cybulski Reed [10] domain analysis Prieto Diaz [35] Frakes, et al. 15] Kang, et al. 23] Simos [40] reuse based process Kang, et al. 24] meta and working models Castano, Bubenko [7, 8] wide spectrum reusability Lubars [27] family of requirements Lam [25] reuse based maintenance Basili [4] CASE support of early reuse Poulin [34] 3 in ....

Prieto-Diaz, R. (1988): "Domain analysis for reusability", in Software Reuse: Emerging Technology, W. Tracz (Editor). IEEE Computer Society Press. p. 347-353.

....are another method by which information on a problem domain can be captured: the class structure of the domain model can be used to reflect the relationships between the entities in the domain. Such a framework would usually be the product of a process of domain analysis as descriibed below [PD87, Ara89] These frameworks would not normally be seen as falling within the realm of AI but are often used in conjunction with other representations such as those discussed above. Further discussion of this issue can be found in [Jac86, LS89] This concludes the section on knowledge ....

....particular domain of interest. The output of literary warrant is a set of terms which allow classification of each document along various axes (facets) The process assumes some prior knowledge of the domain and of the intended use of the collection in order to propose sensible axes. Prieto Diaz [PD87] describes the process in some detail. Perhaps the classification of documents for information retrieval purposes is a rather simpler problem than the general one of developing sufficient knowledge of a domain to be able to maintain intelligent dialogue; nevertheless, it indicates some of the ....

[Article contains additional citation context not shown here]

R. Prieto-Diaz. Domain analysis for reusability. In IEEE COMPSAC 87, 1987.

....engineering process For a detailed exposition of uncertainties in reverse engineering and re architecting, see [ZKR96] 2.1. 4 Uncertainty in software reuse Uncertainty in software reuse has not only been recognized but also addressed by many researchers, for example Prieto Diaz and Arango [PD91a, PD91b] Special sessions on uncertainty in software reusability were held at the 1994 and 1996 IPMU conferences, including papers on, among others, uncertainties in the composition of reusable components [MW96] and in object recovery [GK94] Effective reuse of software components introduces ....

Rub'en Prieto-D ' iaz. Domain analysis for reusability. In Rub'en Prieto-D ' iaz and Guillermo Arango, editors, Domain Analysis and Software Systems Modeling, pages 63--69. IEEE Computer Society Press, 1991.

....related to the study of features in software systems. For the most part, these efforts employ concepts that overlap with the feature engineering framework in a specific domain, such as software architecture or configuration management. 2.2. 1 Domain Analysis and Modeling In domain analysis [71] and modeling, the activity of feature analysis has been defined to capture a customer s or an end user s understanding of the general capabilities of systems in an application domain [45, 50] Domain analysis frequently uses the notion of features to distinguish basic, core functionality from ....

....of features to distinguish basic, core functionality from variant, optional functionality [33] Although features are generally explicit elements of domain models, in this work, their connection to other life cycle artifacts is effectively non existent. The classification scheme described in [71] is a taxonomy of primitive functions and relationships between them in the problem domain. We find significant agreement between 15 domain analysis and the feature engineering framework within the problem domain, but domain analysis does not address solution domain concerns. One narrow view of ....

R. Prieto-D'iaz. Domain Analysis for Reusability. In Eleventh Annual Computer Software and Applications Conference, pages 23--29. IEEE Computer Society, 1987.

....domains (Lemke Fischer, 1990; Fischer, Henniger, Redmiles, 1991; Fischer, 1994) Each of these environments relies on a domain model. A domain model is generally recognized in software engineering as the end product of a domain analysis process that is either synthetic or evidentiary (Prieto Diaz, 1987). In synthetic domain analysis, a software developer starts with an informal description of one or more systems within an application domain, identifies aspects common across the systems, and models these with object classes and frameworks. In evidentiary domain analysis, a software developer ....

Prieto-Diaz, R. (1987). Domain Analysis for Reusability. Proceedings of the International Computer Software and Applications (COMPSAC-87) Conference (Tokyo, Japan), IEEE Computer Society Press, Los Alamitos, CA, pp. 23-29.

....proposals describing: their application domain, the expected deliverables as a result of the funding, and . an estimate of required funding. If accepted, the Parts Stimulation Program funded the front end expenses of conducting the reuse study, which included: performing a domain analysis [30], developing specifications for the reusable parts, and, completing a reuse business case detailing who else will benefit and the expected return on the investment. Funding the front end expenses proved an effective way to leverage a limited amount of funding. Because the organizations would ....

Prieto-Diaz, Ruben, "Domain Analysis for Reusability, " Proceedings of COMPSAC '87, 1987, pp. 23-29.

.... for systems analysis (e.g. by specializing the domain model) and 3) providing an application dependent c categorization classification of existing reusable components (of later development stages) so that opportunities for reuse an be identified as early in the development process as possible [5, 130, 132]. Domain models should identify: 1) the s b entities and operations on those entities that are common to the application domain, 2) relationships and constraint etween the entities, and 3) retrieval cues , i.e. properties of objects that are likely to be used by developers in the prom cess of ....

....activity, p and there is some disagreement as to what it involves, both in terms of process activities and in terms of outputs work roducts. However, most researchers agree that a critical (and notoriously difficult) step in domain analysis is the s s identification of the boundaries of the domain [5, 101, 130]. Lest we oversimplify, domain analysis follows a proces imilar to that in developing specific software systems. Namely, it involves requirements, analysis, and the production of January 2, Software Reuse Page 32 n t domain wide reusable components [5, 101, 130] The outputs, however, differ ....

[Article contains additional citation context not shown here]

Ruben Prieto-Diaz, "Domain Analysis for Reusability," in Proceedings of COMPSAC'87, pp. 23-29, IEEE Press, 1 1987.

.... Ascent Logic Corporation 4 Although their authors would probably find this to be a good point of discussion application specific requirements (which define a problem domain) Another difference between this approach to domain engineering and other domain analysis approaches (e.g. Prieto Diaz [9]) is that case based reasoning and reverse engineering are not central mechanisms for identifying reusable resources, but rather existing applications are used as vehicles to validate the architectures that are derived, top down, from generalized user requirements. The reuse of existing artifacts ....

R. Prieto-D ' iaz. Domain Analysis for Reusability. In Proceedings of COMPSAC'87, pages 23--29, 1987.

....8 . Despite the differences, the result of both kinds of analyses includes a description of a set of components. Thus the terminology used by domain analysts to describe the results of their efforts is pertinent to a reverse knowledge engineering effort. Both Neighbours [ 29 ] and Prieto Diaz [ 36 ] suggest a model based on objects and actions. Our KB is concerned with storing knowledge about a large software system, and using this knowledge as an index into a library of reusable components. As Curtis [ 13 ] suggests, the way programmers think about the system is an important determinant ....

.... Display a number on the Attendant s console. These key primitive building blocks are combined and sequenced in various ways to implement the customer features; the descriptions of these operations, with their operands and precise effects constitute the domain model (in the spirit of PrietoDiaz [ 36 ] ) of the PBX switching features supported by the Definity 75 85. Though there was no explicit discussion of the domain model anywhere in the documentation, a detailed study of the architecture indicates that the designers carefully considered the feature set and isolated a set of primitives that ....

Prieto-Diaz, R. Domain Analysis for Reusability, Proceedings IEEE COMPSAC-87, Tokyo, Japan, October, 1987.

....behind classification are that there are potentially many, different pieces of components available in a library (see the discussion of REBOOT below) and that the retrieval of software should be supported by the computer. Informally said, classification is the act of grouping like things [PD91a; p. 64] A classification scheme should meet the following requirements [BM91] PD91b] Accommodate library expansion . Support finding similar assets 14 . Support finding functionally equivalent assets . Enable partial searches . Be expressive and descriptive . Allow easy maintenance ....

....science, to the domain. Briefly sketched, a literary warrant consists in selecting a random example of titles from the collection to be classified, listing individual terms from the titles, grouping related terms in common classes, and organizing the common classes into a classification scheme [PD91a; p. 64] Faceted classification presupposes several facets with a number of terms for each facet. To classify an asset one has to select from each facet the term that best describes the asset. For a somewhat simplified example, a facet scheme for a model library may have the facets (in ....

R. Prieto-Diaz. Domain Analysis for Reusability, pages 63--69. 1991. Originally published in Proc. COMPSAC 87.

No context found.

PRIETO-DIAZ, R.: `Domain analysis for reusability', Proceedings of COMPSAC'87, 1987

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC