Citation Context

...ith components and realms. Components. The fundamental unit of large scale software construction is the component. Every component has an interface and an implementation. Following the lead of Parnas =-=[20, 51]-=-, the interface of a component is arzything that is visible externally to the component. Everything else belongs to its implementation. Every component is a member of a realm T, where all members of T...

Citation Context

...e interface between two programs consists of the set of assumptions that each programmer needs to make about the other program in order to demonstrate the correctness of his program (paraphrased from =-=[5]-=-). Defining interfaces is the most important part of system design. Usually it is also the most difficult, since the interface design must satisfy three conflicting requirements: an interface should b...

Citation Context

...were facing. Instead, proposing a standard virtual machine interface for all adc sensors, another interface for all gps sensors, etc. was much easier and more readily acceptable by avionics engineers =-=[Bri81]-=-. This decision led to a realm of components for each distinct DSO type. The realm of inertial navigation sensors (ins) is a typical example: ins = { // equipment list } controls and display flight di...

Citation Context

...ilding families center on constructing a design for the family that consists of a set of information hiding modules, each independently adaptable to independently occurring changes, as exemplified in =-=[2]-=-, [15], [14], and [16]. A change may be made to one module without needing to know how changes are made to other modules. Each module is said to have a secret, i.e., a decision that is hidden within t...

Citation Context

...ace speci cation should be reviewed by programmers who will use the module as well as others interested in the design, e.g., reviewers. For more information about the design of module interfaces, see =-=[5, 8]-=-. Designing the Uses Hierarchy Once the modules and their interfaces are known, the uses hierarchy [35] can be de ned. This hierarchy is a relation de ned on the access programs in the module interfac...

Citation Context

...Analysis: A Systematic Process for Defining Families 1.1 Developing Families Techniques for building families were documented in the software engineering literature starting in the 1970s (see, e.g., (=-=[1]-=-, [4], [5], [6], [7], [8]). These techniques often centered on constructing an architecture that would accommodate expected changes in the software, but most said little about how to decide what the m...

Citation Context

...nd its environment. 1 1. In SPC’s CoRE method, these objects are known as “boundary classes” [11]. In the Software Cost Reduction project architecture, they were known as “Hardware-Hiding modules” [2]=-=[1]-=-, but later refinement suggested the more general “Environment-Hiding modules”. 4Of course, a correct domain model for this application will have anticipated and captured the differences between thes...

Citation Context

...ongly encapsulated modules, that is, syntactic structures that support information hiding approaches [14] to design and constrain interactions among the components to well-defined abstract interfaces =-=[2]-=- as shown in Figure 1. iii. The language should be compositional. It should be possible to combine separately developed components to form a larger assembly such that the overall behavior can be accur...