Guillermo Arango, "Domain Analysis Methods," in Software Reusability, Ellis Horwood, 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....line modeling. In most product line modeling approaches, the integration of legacy systems into the domain analysis phase is not described in depth. An overview on domain analysis methods like FODA [19] ODM [28] or Commonality Analysis within FAST [30] can be found in several surveys like [8] or [2]. An approach that is often used is feature modeling [19] where features are seen as common and variable characteristics of a system that have some value to the user. Our elicitation approach supports feature modeling as with the approach, features can be identified in user documentation. The ....

G. Arango. Domain analysis methods. In W. Shaefer, R. Prieto-Diaz, and M. Matsumoto, editors, Software Reusability. Ellis Horwood, 1993.

....doubt of the importance of explicitly considering domain knowledge in software production. The issue permeates all the four chosen topics, and are present in several of the problems pointed at the Report. Although research on domain aspects has been mainly addressed by the software reuse community [3] the requirements community is also concerned with the issue [59] Our main objective with the survey was to bridge recent findings in Requirements Engineering research to a real world problem. A fundamental piece in the process is the Report on the London Ambulance Service itself, an accessible ....

G. Arango. Domain Analysis Method, Software Reuse, Ellis Horwood, pages 17-49, 1994.

....focus on supporting formal or semi formal reasoning about domains. Others focus on compositional software construction. This section discusses the latter category. A reviews and comparisons of several of these reuse oriented domain analysis methods is presented in [Wartik and Prieto Dfaz, 1992] [Arango, 1994], and [Nilson et al. 1994] These methods provide guidelines on what kind of information we should look for and how to represent it in order to support systematic software reuse. Although these methods differ on how they breakdown and represent the domain knowledge, the general domain analysis ....

....differ on how they breakdown and represent the domain knowledge, the general domain analysis process is basically the same for all methods. Identifying the fact that the differences between these method are accidental rather than essential, Arango proposes a Common Process for domain analysis [Arango, 1994]. Before describing the analysis process and methods, it is useful to define more precisely the meaning of some of the keywords used by all methods: Problem Domain: A problem domain or simply a domain can be defined as an area of activiti or knowledge containing applications which share a set ....

[Article contains additional citation context not shown here]

G. Arango. Domain analysis methods. In W. Schifer, R. Prieto-Dfaz, and M. Mat- sumoto, editors, Software Reusability, chapter 2. Ellis Hotwood, New York, 1994.

....as domain analysis. Domain Analysis strives for the identification of commonalties across applications in a domain, and results in the definition of product line features documented by domain models. Domain analysis is a top down activity considering only applications in a domain of discourse. See [18] for a survey of DA methods. A method specifically designed for DA is the Feature Oriented Domain Analysis (FODA) method developed at the SEI [19] This method defines a process for domain analysis that supports the discovery, analysis, and documentation of commonality and differences within a ....

Arango, G. Domain Analysis Methods. In Software Reusability. (Chichester, England: Ellis Horwood, 1994) pp 17-49. SEKE-JDH.doc submitted to World Scientific: 9/30/00 : 9:35 AM 20/22

....and produces some supporting rationale, models and architectures that enable better decisions to be made, recorded and revisited for further revision, and for process improvement based on learning. Domain engineering is a key part of preparing a reliable architecture and components for reuse[5, 6]. Domain engineering starts with Domain Analysis (DA) primarily a systematic analysis of commonality and variability in a family of systems across a domain: example systems, user needs, domain expertise and technology trends are analyzed to identify and characterize elements that are common to ....

....architecture, component development and packaging steps, summarized in Table 1. FODA and RSEB will be described in the following sections. Steps 1 3 are referred to as domain analysis, and steps 4 7 as asset or component engineering. Several different domain engineering methods have been developed [5]. They vary in how they identify the domain effectively, and make maximum use of available domain, architecture and systems expertise. Some methods focus on how to select existing exemplars for detailed analysis, while others focus on how to collect, represent and cluster sets of so called ....

[Article contains additional citation context not shown here]

G Arango, Domain Analysis Methods, in W. Schfer et al., Software Reusability, Ellis Horwood, Hemel Hempstead, UK, 1994.

....companies have developed process enactment tools, such as Process Weaver [ProcessWeaver 92] Synervision [Synervision 93] and PEAKS [Ett 93] The creation of reusable processes is dependent on domain analysis. Many domain analysis techniques for creating reusable software have been developed. Arango 94] has surveyed these techniques and created a composite domain analysis technique . This composite technique is used as a basis for the methods described later in this paper. This paper investigates how to pragmatically and systematically standardize and replicate project specific processes in an ....

....standards, and improve productivity and quality. The methodological steps to create a reusable process are described below. The method derives from a generalization of standard software development and domain analysis techniques, particularly Arango s domain analysis of domain analysis methods [Arango 94] 1. Process Requirements Analysis: This step defines the operating conditions under which the process will be enacted and the goals and requirements that the process will satisfy. A process definition and evaluation action plan is developed that contains this information plus basic project ....

Arango, G. "Domain Analysis Methods," from Software Reusability, edited by Schafer, W., Prieto-Diaz, R., and Matsumoto, M., Ellis Horwood, 1994

....possible to come up with a skeletal process by analyzing the domain specific language and the variabilities allowed as parameters. 10 23 97 76 5. Related Work There are many different domain analysis methods available. Some of them have been compared in survey papers by Arango and Prieto Diaz [64,65]. However there are only a few that are well defined and used repeatedly in practice. These include: Feature oriented domain analysis (FODA) Organizational domain modeling (ODM) the sandwich method (by Ruben Prieto Diaz) and Knowledge Acquisition for Preservation of Tradeoffs and Underlying ....

Arango, G., Domain Analysis Methods. in Software Reusability (W. Shaefer, R. Prieto-Diaz, and M. Matsumoto, eds.), Ellis Horwood, 1993

....along with the (reusable) solution, there has to be a description in each case of what the domain (class of problems) is. Reusable elements are identified in DA during the modelling phases: data analysis (also called subsidiary modelling) and classification (also called primary modelling) [Arango94]. Methods differ with regard to the parameters used in the classification: features [Kang90,Simos91,Simos95] facets [PrietoD az87,Birk97] capabilities [Cornwell96] etc, and the type of data analysed: entities and relationships [McCain85, Jaworski90,Prieto Daz91] context ....

.... from two opposing points of view: as an advantage (there can always be assumed to be a method that meets the particular needs of the reuser) or as a disadvantage (the question arises of whether the variety is a response to shortcomings or an overspecialisation of existing methods) Authors like [Arango94] have evaluated different DA methods, focusing on the differences in the DA process (how the domain model is obtained) rather than on other method features. For example, the comparative study performed by Arango [Arango94] on several DA methods concluded that all DA methods follow a common ....

[Article contains additional citation context not shown here]

G. Arango. Software Reusability, chapter 2. Domain analysis methods, pages 17-49. Workshops M.E. Horwood, London 1994.

....consistently to make agents work together as a flexible yet robust whole. Experience with this almost orthogonal feature decomposition of agents motivates a feature driven, aspect oriented implementation. 1. 4 Domain analysis helps find features Domain analysis or domain engineering techniques (Arango, 1994) are used to systematically extract features from existing or planned members of a product line. Feature trees are used to relate features to each other in various ways, showing sub features, alternative features, optional features, dependent features or conflicting features. These methods, such ....

Arango, G. (1994), Domain Analysis Methods, in W. Schfer, et al., Software Reusability, Ellis Horwood, Hemel Hempstead, UK.

....would be used as is, some would be parameterized Lecture Notes in Computer Science 3 and others would come in sets of plug compatible alternatives with different characteristics to satisfy the features. 1. 1 Domain Analysis Helps Find Features Domain analysis and domain engineering techniques [5] are used to systematically extract features from existing or planned members of a product line. Features trees are used to relate features to each other in various ways, showing sub features, alternative features, optional features, dependent features or conflicting features. These methods, such ....

G Arango, "Domain Analysis Methods," in W. Schfer et al., Software Reusability, Ellis Horwood, Hemel Hempstead, UK, 1994.

....five to eight people was first videotaped and then analyzed. The team designed an educational software system. Working alone or in groups, designers create, develop, refine, analyze and document their conceptualization of a product. In addition to the number of participants, its empirical nature [Ara94] and the scope of problems that could arise contribute to the complexity of the design process. There are many methods for observing the design activity which vary from simple documentation analysis to video tape analysis. Although video tape technology was previously used to record the design ....

G. Arango. Domain analysis methods. In.W. Schfer, R. Prieto-daz and M. Matsumoto (Eds.) Software Reusability (Ellis Horwood, New York, 1994) 17-49.

....with the end use of the knowledge of less a concern than the other disciplines previously discussed. Knowledge engineering is an attempt at combining all other perspectives. Task analysis is used to understand a domain through constraining its description into formalized model representations (Arango, 1993). Modeling limits the description and limits the complexity, so that various analysts can draw their own conclusions by studying the models rather than be overwhelmed by unconstrained data. Perhaps the simplest model is the task template. Table 1 lists task decomposition fields of a task template ....

Arango, G. (1993). Domain Analysis Methods. Austin, TX: Schlumberger Laboratory for Computer Science.

....the organization forms a team to study an area before it starts the main development effort. Organizations must use the topdown approach when they do not have the benefit of experience in the domain and normally employ a structured domain analysis method to help guide them through the process [2]. The resulting domain library continues to evolve during development but the initial work takes place early in the project. IBM Rockville took a top down approach when it engineered and wrote their AAS shared libraries before the main AAS development effort began. 5.3 Organizing for ....

Arango, Guillermo, "Domain Analysis Methods," in Software Reusability. Wilhem Shaefer, Ruben Prieto-Diaz, and Masao Matsumoto, eds. Ellis Horwood, Chichester, U.K.,1993.

.... a class of problems to develop problemoriented specification languages [Nei81] There are several approaches to domain analysis, which can be divided into two main groups depending on whether one interprets a domain as a collection of problems or a collection of (existing or future) applications [Ara94] If one takes the first view, domain analysis creates a theory of the problems in a domain. If one takes the second position, i.e. defines a domain by applications, domain analysis yields a taxonomy of reusable system components. Such a system oriented view underlies some of the reuse ....

.... we concentrate on the commonalities between both approaches, which can be described from a narrower, life cycle oriented perspective (see Table 1: above, phase Analysis II) For an integrative view on the different approaches to domain analysis see the Common Process model defined by Arango [Ara94; section 3] We will characterize the major steps (roughly common between the different approaches to domain analysis) and their sub activities as defined in the Common Process model. The first phase is domain characterization and project planning. This phase consists of the activities business ....

[Article contains additional citation context not shown here]

G. Arango. Domain analysis methods, pages 17--49. In SPDM94, 1994.

....may include project domain knowledge of similar or related projects. Either type of knowledge may be vertical or horizontal depending on the applicability of the knowledge. How can we capture and represent these types of domain knowledge 2. 2 How is the domain knowledge represented Arango in [1] provides a comparative survey of published domain analysis methods. The survey also provides a common domain analysis process, but it does not explicitly define what is the representation of the domain knowledge (i.e. the output from the process) Is the classification and the data analysis ....

G. Arango, "Domain Analysis Methods," in Software Reusability, pp. 17--49, London, UK: Ellis Horwood, 1994.

....having the following characteristics: 1. deep or comprehensive relationships among the items of information are suspected or postulated with respect to some class of problems, and 2. the problems are perceived as significant by the members of the community. Domain analysis is defined in Arango [1] as the process of creating models that make it possible to reason about the domain, and to predict, explain, or derive facts about the domain that are difficult to observe directly. Prediction might involve establishing the feasibility of an application, or estimating the cost of evolving an ....

G. Arango. Domain analysis methods. In W. Schafer, R. Prieto-D ' iaz, and M. Matsumoto, editors, Software Reusability, pages 17--49. Ellis Horwood, 1994.

No context found.

Guillermo Arango, "Domain Analysis Methods," in Software Reusability, Ellis Horwood, 1994.

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