David A. Cuka and David M. Weiss. Engineering domains: Executable commands as an example. In Premkumar Devanbu and Jeffrey Poulin, editors, "5th Int'l Conf. on Software Reuse", pages 26--34, Los Alamitos, CA, USA (2--5 June 1998). IEEE Computer Society.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....that of domain modeling of families of systems (also referred to as software product lines) where an application domain is modeled by analyzing the common and variant aspects of the family. This concept has been investigated by several researchers and practitioners [Batory92, Bosch99, Coplien98, Cuka98, DeBaud99, Dionisi98, Kang90] At George Mason University, a reuse oriented software lifecycle, the Evolutionary Domain Lifecycle [Gomaa93] has been proposed, which is a highly iterative lifecycle that takes an application domain perspective allowing the development of families of systems ....

Cuka, D. and D. Weiss, "Engineering Domains: Executable Commands as an Example", Proceedings of IEEE ICSR5, Victoria, June 1998.

....then determining the special properties of the individual family members. The program family approach works well in situations where there are different versions of a system (different family members) all of which share common requirements, design, or code. Examples of such situations are (from[10]) Systems that have the same requirements but must execute on different platforms, e.g. database management systems or compilers for the same language) Systems that store and use the same data, but vary the processing of the data, e.g. systems that provide different types of reports ....

....programming methods, which are intended for the development of a single program, are not ideal. This paper discusses the process of designing and developing program families and surveys work on program families. The work surveyed is: 19] 20] 12] 18] 7] 5] 6] 4] 3] 16] 23] [10], 8] 9] 13] 14] 15] and [24] These papers have several things in common: 1. They all suggest that we should make the family the unit of software development. Here the set of programs that constitute the family are identified by defining a set of commonalities and variabilities that ....

[Article contains additional citation context not shown here]

Cuka, D., Weiss, D., "Engineering Domains: Executable Commands as an Example", Lucent Technologies, private communication.

.... form a program family [8] Because device drivers form a program family, their development could be systematized to improve productivity [3] Because device drivers are developed at a fast pace, their development should systematize both expertise and code re use to better time to market delivery [12, 9, 4]. Because device drivers are critical pieces of a system, their implementation should be veried to improve safety [3] Our approach Our approach to systematizing the development of device drivers is based on domain specic languages (DSL) 3] Because device drivers include several domains of ....

D. Cuka and D. Weiss. Engineering domains: Executable commands as an example. In Proc. Fifth Internationbal Conference on Software Reuse, June 1998.

....individual members. As with families of programs, it is crucial to identify early what are the common parts of the family, on which most other parts will depend. Accordingly, we have to do an SCV analysis (scope, commonality, and variability) of the family, as proposed by Weiss and others [CHW98, CuWe98, GJKW97] for families of programs. We do not already specify any conceivable telephone switching system, but we determine which requirements aspects will be common 17 to all conceivable systems, which aspects will be common to only some versions, and which aspects are highly special to the ....

Cuka, D. A. and Weiss, D. M. Engineering domains: Executable commands as an example. In Devanbu, P. and Poulin, J., editors, "5th Int'l Conf. on Software Reuse", pp. 26--34, Los Alamitos, CA, USA (2--5 June 1998). IEEE Computer Society.

.... form a program family [8] Because device drivers form a program family, their development could be systematized to improve productivity [3] Because device drivers are developed at a fast pace, their development should systematize both expertise and code re use to better time to market delivery [12, 9, 4]. Because device drivers are critical pieces of a system, their implementation should be verified to improve safety [3] Our approach Our approach to systematizing the development of device drivers is based on domain specific languages (DSL) 3] Because device drivers include several domains of ....

D. Cuka and D. Weiss. Engineering domains: Executable commands as an example. In Proc. Fifth Internationbal Conference on Software Reuse, June 1998.

....1. Introduction We report here our experience with jargons [Nakatani96] for software engineering. Jargons are DSLs that are unusually easy to make. We use jargons within the framework of the Family oriented Abstraction, Specification and Translation (FAST) domain engineering process [Parnas76] [Cuka98] to automate software production. Previous attempts with FAST had foundered when the DSLs needed for domain modeling took too long to make. Because jargons can be made quickly and easily, they seemed a good alternative to conventional DSLs. Preliminary experiments made us optimistic that jargons ....

Cuka, D.A. and Weiss, D.M. Engineering Domains: Executable Commands as an Example, Proceedings 5th International Conference on Software Reuse, Victoria, Canada, June 2-5, 1998, 26-34.

....behavior and assumptions that differ among family members) must be identified. The analysis takes into account domain knowledge such as technical literature, existing programs, and current and future requirements. It can be conducted using methodologies used for commonality analysis, such as FAST [40, 11], and domain analysis [24, 25, 28] The main results of this analysis phase are: language requirements, a description of the common objects and operations, and design elements of the DSL. We examine each of these items in turn and illustrate them with our working example. 2.1 Language ....

D. Cuka and D. Weiss. Engineering domains: Executable commands as an example. In Proc. Fifth Internationbal Conference on Software Reuse, June 1998.

No context found.

David A. Cuka and David M. Weiss. Engineering domains: Executable commands as an example. In Premkumar Devanbu and Jeffrey Poulin, editors, "5th Int'l Conf. on Software Reuse", pages 26--34, Los Alamitos, CA, USA (2--5 June 1998). IEEE Computer Society.

No context found.

D. A. Cuka and D. M. Weiss, "Engineering Domains: Executable Commands as an Example," Proc. 5 th Intl. Conf. on Software Reuse, Victoria, Canada, June 2--5, 1998, pp. 26--34.

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