Batory, D., et al.: Creating Reference Architectures: An Example from Avionics. In: Proceedings of Symposium on Software Reusability. (1995)  Home/Search   Document Not in Database   Summary   Related Articles   Check

....ADT, communication methods, device drivers, etc. so that their changes are not propagated into other parts of the software. Here, the feature based object oriented engineering method [10] is used for the development of reusable objects that are commonly used in the domain. Software architectures [2, 11, 12, 15] play a central role in the successful development of a product line. Most organizations with product line experience have their own software architectures, which serve as frameworks for composing and adapting domain components. In our method, multiple software architectures can be developed ....

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer, Creating Reference Architectures: An Example from Avionics, ACM-SIGSOFT Symposium on Software Reusability, Seattle, Washington, 1995.

....families traditional 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 ....

....Families 6 . Manageability. Items [18] 6] 4] 23] and [24] propose systematic approaches to designing and implementing program families. Others present technologies that are used in these processes. The approaches in [18] 7] 5] 6] 4] 23] 15] and [24] are general purposes. In [3], 16] and [14] specific application areas are discussed. In [7] and [16] a translator is needed to translate the high level language to a lower level. In [5] and [6] the term abstract interface was used and discussed in [12] in detail. The approaches used in [5] and [6] are based on the idea ....

[Article contains additional citation context not shown here]

Batory, D., Coglianese, L., Goodwin, M., Shafer, S., "Creating Reference Architectures: An Example from Avionics", private communication.

....reference architecture for control. Applications are built as hierarchically organized controllers, each with district domain and meta control components, with a unifying store for world models and shared information. DICAM is not inherently domain specific. 9.2. 2 GenVoca LE GenVoca LE language [BCGS93] is a domain independent model for defining scalable families of hierarchical systems as compositions of reusable components by meta models of large scale system construction. 9.2.3 Capture (aka KAPTUR Knowledge Acquisition for Preservation of Trade offs and Underlying Rationales) Capture ....

Don Batory, Lou Coglianses, Mark Goodwin, and Steve Shafer. Creating reference architectures: An example from avionics. anonymous ftp to cs.utexas.edu, 1993.

....examine a software product against requirements and specifications [7, 20] Many testers also derive tests primarily from user manuals. When software development is based on a domain model, the software could be tested using the domain model specification and the specifics of the user interface [3, 4]. To analyze, design, and implement a system, developers need detailed domain model specifications, well defined abstractions, and rules for extending the domain model into new problem domains. In contrast, system testers may not need all features of the domain model and therefore could rely on a ....

....Validating test results is still manual. We are working on adding test oracle information to the domain model. This requires new analysis steps to determine the nature of the oracle. 47 We also need to examine this method with existing domain analysis and domain models for software reuse [3, 4]. Currently, the application of the domain model is restricted to applications with a command or transaction language as a user interface. Extending the approach to testing systems with a graphical user interface would require mapping actions, objects, and object elements into GUI concepts like ....

D. Batory, L. Coglianese, M. Goodwin, S. Shafer, "Creating Reference Architectures: An Example from Avionics", Symp on Soft Reusability 1995, Seattle, Washington.

.... Stereotype DRAC Association for instances of meta class Association [1] Each association must be binary self.oclType.connection size = 2 [2] The association ends must refer to different instances self.oclType.connection forAll( c1, c2 c1.oclType.element c2.oclType.element) [3] Each connection must be a DRAC AssociationEnd self.oclType.connection forAll(c1 c1.oclType.type.oclType.oclIsTypeOf( DRAC AssociationEnd ) true) The interpretation of this constraint is shown in Figure 12. DRAC 1 has service s1 that depends on attribute a1 of DRAC 2. This introduces a ....

Batory, D., Coglianese, L., and Goodwin, M.: Creating Reference Architectures: An Example from Avionics. In Proceedings of ACM SIGSOFT Symposium on Software Reusability (SSR '95) ( Seattle, WA, 1995) 27-37.

....can be further developed into an even more productive application generator. Successful reference architectures and application generators has been built in a number of domains such as compilation, information systems (4GLs, code generators, CASE tools and visual environments) and avionics systems [2]. Domain Analysis Architecture Design Requirements Analysis System Development Domain Model Reference Requirements Reference Architecture System Requirements System Architecture System System Design DOMAIN ENGINEERING SYSTEM ENGINEERING Domain Knowledge User Needs Fig. 1. ....

Batory, D., Coglianese, L., Goodwin, M. and Shafer, S. Creating Reference Architectures: An Example from Avionics. In Collected Overview Reports from the DSSA Project. Will Tracz, Ed. October 1994.

....for re nements of event patterns. However, the reference and the instance architectures have to be known in advance to verify the re nement correctness, which implies an extended study and profound cognition of the re ned domain, as stressed by the experience report from the ADAGE project [6]. Fortunately, fault tolerance has been studied for years and the domain has reached a maturity level, which permits the deduction of re nement patterns for a set of well understood dependability abstractions. As a demonstrative example, the RCP architecture [74] provides four re nement levels for ....

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer. Creating Reference Architectures: An Example from Avionics. In Proceedings of the Symposium on Software Reusability, pages 2737, April 1995.

No context found.

D. Batory, L. Coglianese, et al., "Creating Reference Architectures: An Example from Av i on i cs " , Symposium on Software Reusability, Seattle Washington, April 1995.

No context found.

D. Batory, L. Coglianese, et al., "Creating Reference Architectures: An Example from Avionics", Symposium on Software Reusability, Seattle Washington, April 1995.

....basic ideas of GenVoca and one of its implementation techniques. It is beyond the scope of this paper to review design methodologies (i.e. how to apply GenVoca concepts) or to explain domains simpler than FSATS to elaborate the approach that we have taken. Interested readers should consult [37] [3], and [28] 2.2.1 Motivation Today s models of software are too low level, exposing classes, methods, and objects as the focal point of discourse in software design and implementation. This makes it difficult, if not impossible, to reason about software architectures (a.k.a. componentbased ....

D. Batory, L. Coglianese, M. Goodwill, and S. Shafer, "Creating Reference Architectures: An Example from Avionics", Symposium on Software Reusability, Seattle, Washington, April 1995.

....variations appropriate for designing software in the domain. That is, a domain model is a representation of the essential aspects of the domain [Pri95] A domain architecture (a.k.a. domain specific software architecture (DSSA) SEI90, Tra94] application framework [Joh88] reference architecture [Bat95], or software architecture) is a domain model that embodies an abstract design for software in a family of related systems. Thus, a domain architecture is analogous to an object oriented framework, but without the object oriented implementation detail. Domain engineering includes domain analysis ....

.... have been used in independently conceived generators in many disparate domains: Avoca in network protocols [Oma92] Rosetta in data manipulation languages [Vil94, Vil97] Ficus in distributed file systems [Hei94] Brale in host at sea buoy systems [Wei90] and ADAGE in realtime avionics software [Bat95]. Thus it seems worthwhile to factor out the common, domain independent ideas that underlie different software generators, and to build tools and develop design techniques that support these particular methods of software organization and construction. By doing so, we believe that other ....

Don Batory, Lou Coglianese, Mark Goodwin, and Steve Shafer. Creating Reference Architectures: An Example from Avionics, In [Sam95], pages 2737.

No context found.

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer. "Creating Reference Architectures: An Example from Avionics", Symposium on Software Reusability, Seattle Washington, April 1995.

No context found.

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer, "Creating Reference Architectures: An Example From Avionics", ACM SIGSOFT Symposium on Software Reusability, Seattle, 1995, 27-37.

....simplification to FSATS design and makes it possible to create variations of FSATS (e.g. for use by other armed forces) that would otherwise be infeasible. The techniques and results discussed in this paper are not isolated; GenVoca itself has a long history of successes, including avionics [Bat95], data structures [Bat93] and network protocols [Hay98] Among the technical issues previously addressed are the verification of layer composition, automatic optimization of compositions, and meta program implementation of refinements. Although mixin layers were conceived only recently, many ....

D. Batory, L. Coglianese, M. Goodwill, and S. Shafer. "Creating Reference Architectures: An Example from Avionics". Symposium on Software Reusability, Seattle Washington, April 1995.

....for a large family (or domain) of software. A primitive component, by definition, is reusable because it is used in the design of many family members. Domain modeling is the name given to software design methodologies that identify primitive components of software designs for a specific domain [Pri91, Gom94, Bat95a]. A second implication is that a primitive component of software design need not correspond to a primitive code module or package in a generated system. In general, the introduction of a component to a system s design might require incremental modifications to many parts (e.g. object oriented ....

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer, "Creating Reference Architectures: An Example From Avionics", ACM SIGSOFT Symposium on Software Reusability, Seattle, 1995, 27-37.

.... domain analyst for specific selections and compositions of components [Pou94] Software system generators are among the most visible and concrete products that can come from domain modeling; a generator is often the centerpiece for other analysis tools that are critical to applications development [Bat93]. 3 Recap We have an admittedly narrow focus on what should be the products of domain modeling; we concur that a broader vision should be adopted by the software engineering community. However, we feel our focus is justified as a consequence of years of work in the areas of reuse, software ....

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer. "Creating Reference Architectures: An Example from Avionics", ADAGE Tech. Rep. UT-93-06, 1993.

No context found.

Batory, D., et al.: Creating Reference Architectures: An Example from Avionics. In: Proceedings of Symposium on Software Reusability. (1995)

No context found.

Don Batory, Lou Coglianese, Mark Goodwin, and Steve Shafer. Creating reference architectures: An example from avionics. In Proceedings of the 1995 Symposium on Software Reusability (SSR'95), pages 27--37, 1995.

No context found.

D. Batory et al. Creating Reference Architectures: An Example from Avionics. In Proceedings of the Symposium on Software Reusability (SSR), 1995.

No context found.

D. Batory et al. Creating Reference Architectures: An Example from Avionics. In Symposium on Software Reusability, 1995.

No context found.

D. Batory et al. Creating Reference Architectures: An Example from Avionics. In Symposium on Software Reusability, 1995.

No context found.

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer. Creating reference architectures: An example from avionics. In Proceedings of the 1995.

No context found.

BATORY, D., COGLIANESE, L., GOODWIN, M., AND SHAFER, S. Creating Reference Architectures: An Example from Avionics, Symposium on Software Reusability. Seattle Washington, April 1995.

No context found.

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer, "Creating Reference Architectures: An Example from Avionics", In Proc. ACM SIGSOFT Symposium on Software Reusability, 1995, 27-37. 122

No context found.

D. Batory, L. Coglianese, M. Goodwin, and S. Shafer. Creating Reference Architectures: An Example from Avionics, Symposium on Software Reusability. Seattle Washington, April 1995.

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