R. Macala, L. Stuckey, D. Gross, "Managing Domain-Specific, Product line Development," IEEE Software, Vol.14, No. 13, May 1996.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....theory at this point [15] To establish a basis for understanding variability, it is necessary to investigate the current state of practice and the questions that arise in industry. Several authors have reported on experiences with evolutionary software systems in an industrial context, e.g. 12][22][9] but they do not explicitly address variability. In addition, most of this work primarily reports on large, American software companies that are often related to defense industry and is therefore not necessarily representative for small and medium sized enterprises. This paper focuses on ....

R. R. Macala, L. D. Stucky, D.C. Gross. Managing Domain-Specific Product-Line Development. IEEE Software, 1996, 57-67.

....recognized. The combination of these two insights lead to the definition of software product lines. A software product line consists of a product line architecture, a set of reusable components and a set of products derived from the shared assets. Existing literature on software product lines [1,5,6,7] tends to focus on the technology and the processes that surround product line based software development. These processes include the design of the software architecture for the product line, the development of the shared software components, the derivation of software products and the evolution ....

....to understand what alternatives are available and to evaluate these, rather than blindly adopting a standard model. 8 RELATED WORK As we discussed in the introduction, most publications in the domain of software product lines address issues different from the organizational ones. Macala et al. [7] and Dikel et al. 5] were among the first publications that describe experiences from using software product lines in an industrial context. Although the authors do address organizational, management and staffing issues, both assume the domain engineering unit model and present it as the de facto ....

R.R. Macala, L.D. Stuckey, D.C. Gross, `Managing DomainSpecific Product-Line Development,' IEEE Software, pp. 5767, 1996.

....addressed. Weiss Lai 99] discuss the FAST method, which is a systematic approach creating a software product line with a primary focus on the use of domain specific languages and code generators for these languages. Other work in the area of software product lines includes [Dikel et al. 97] Macala et al. 96] and [Bass et al. 98] However, none of these publications discusses product instantiation in software product lines in detail. In [Bosch 00] we discuss the development, deployment and evolution phases of software product lines, but do not discuss the problems and issues presented in this ....

. R.R. Macala, L.D. Stuckey, D.C. Gross, `Managing Domain-Specific Product-Line Development,' IEEE Software, pp. 57-67, 1996.

....discipline which involves the quantitative study, comprehension, propagation, and exploitation of proven and functionally valid software designs (and their variations) within vertical domains, product classes, and market sectors. Literature is slowly emerging which examines this SPI approach [33, 34, 35, 36, 37, 38, 39]. Defect Removal Model Life Cycle: The Defect Removal Model Life Cycle is the process of using a Rayleigh life cycle reliability model in conjunction with the Software Inspection Process to predict and manage software development and software quality management [7, 12, 25, 26, 27] Personal ....

Macala, R., "Managing Domain-Specific Product -Line Development," IEEE Software, May 1996.

....reuse of existing software to minimize product specific development and to increase the quality of software. A number of authors have reported on industrial experiences with product line architectures. In [SEI 97] results from a workshop on product line architectures are presented. Also, Macala et al. 96] and [Dikel et al. 97] describe experiences from using product line architectures in an industrial context. The aforementioned work reports primarily from large, american software companies, often defense related, which we do not consider to be representative for software industry as a whole, ....

. R.R. Macala, L.D. Stuckey, D.C. Gross, `Managing Domain-Specific Product-Line Development,' IEEE Software, pp. 57-67, 1996.

....building software systems out of relatively small, problem oriented application components. CBSD offers mechanisms for runtime customization and integration of such components. To identify and, eventually, build such components, we need a proper decomposition technique for domain analysis [11,12,13]. This technique should facilitate creation of partial problem oriented domain models and generic architectures for problem oriented software components. In such a scenario, software applications would be created by customizing and combining generic architectures. Software evolution would be done ....

Macala R. et al. "Managing Domain-Specific, Product-Line Development," IEEE Software, May 1996, pp. 57-67

No context found.

R. Macala, L. Stuckey, D. Gross, "Managing Domain-Specific, Product line Development," IEEE Software, Vol.14, No. 13, May 1996.

No context found.

Randall R. Macala, Lynn D. Stuckey, Jr. David C. Gross, "Managing Domain-Specific, Product -Line Development", IEEE Software, Vol.14, No. 13, May 1996

No context found.

R.R. Macala, L.D. Stuckey, D.C. Gross, 'Managing Domain-Specific Product-Line Development,' IEEE Software, pp. 57-67, 1996.

No context found.

MACALA R., STUCKEY, L. JR. and GROSS, D. `Managing Domain-Specific, Product-Line Development,' IEEE Software, May 1996, pp. 57-67Lewis Ted et al Component-Oriented Application Frameworks

No context found.

R. R. Macala, L. D. Stuckey, and D. C. Gross, "Managing Domain-Specific Product-Line Development," IEEE Software, Vol. 12, No. 12, May 1996, pp. 57--67.

No context found.

Macala R., Stuckey, L. Jr. and Gross, D. "Managing Domain-Specific, Product-Line Development," IEEE Software, May 1996, pp. 57-67Lewis Ted et al Component-Oriented Application Frameworks

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