Confessions of a used-program salesman

Tracz, Will

doi:10.1145/211782.211785

Cited by 30 publications

(9 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Other authors have emphasized the significance of a thorough domain analysis for software reuse (e.g. [17], [12]). In other related work we look at formal descriptions of RSAs, RSCs and the Plugging operator.…”

Section: Resultsmentioning

confidence: 99%

A reuse triplet for systematic software reuse

Mugisa

1997

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

We present the view that for systematic software reuse (SSR) to happen we need a reuse software architecture (RSA) as the invariant base and a collection of reuse software components (RSCs) as the pluggable variant part of a family of architecturally similar software systems. We shall identify a reuse situation with a RSA, RSCs and a plugging operator. SSR is then presented as a case of plugging a collection of RSCs into the appropriate RSA. We apply this view of reuse to a number of reuse cases and find evidence that for reuse to be successful we need simple, clear and easily pluggable RSAs and RSCs.

show abstract

Section: Resultsmentioning

confidence: 99%

A reuse triplet for systematic software reuse

Mugisa

1997

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

show abstract

“…It is also advocated when creating flexible and reusable software designs [26]. This type of flexibility is similar to keeping the possible decisions in as great as possible.…”

Section: Design Flexibilitymentioning

confidence: 99%

Flexible Specification of Operation Behavior Using Multiple Projections

Bengtsson¹,

Lennartson

2014

IEEE Trans. Automat. Sci. Eng.

View full text Add to dashboard Cite

The execution behavior of a system or a product can often be specified by a set of operations (sometimes called tasks, actions or activities). The process to specify these operations seems to be a real challenge in various situations, for example when designing automation systems or keeping track of the work at an emergency department. To be flexible during design and development, is about coping with uncertainty. However, in practice, specifying operation behavior is often quite inflexible because every possible execution route is explicitly defined. This approach is sometimes refereed to as point-based engineering, which is characterized by the early selection and approval of a single "best" specific solution. This approach can result in neither a robust nor a flexible design process with many rework iterations.This paper instead suggests a set-based operation specification approach that does not explicitly defines operation routes, where instead the operation behavior is specified using the execution restrictions in transition conditions for each operation. This enables the possibility to create multiple projections of the operation relations to enable better understanding. This is accomplished by creating various Sequences of Operations, sequences of operations (SOP), including a multiplicity of sequences and operation relations. Two example case studies are presented, where the first show the development of an automation system and the second study uses sequence projections in an emergency department at a hospital to handle the complex and flexible operation (task) behavior.Note to Practitioners-This paper proposes methods and algorithms in which sequences are automatically created based on the relations among operations instead of having to be manually constructed. These are to be used during designing of the logical behavior of operation. The use of various views increases the understanding of operation behavior during design.Index Terms-Automation design, control logic design, formal methods, sequence planning, sequences of operations.

show abstract

“…This work, like ours, emphasized the importance of repositories of reusable modules, and the use of architectural frameworks within which to insert them. These approaches are presented in work such as [9,21,18]. Our work takes these approaches further in using explicit, rigorous process representations to effect the module reuse.…”

Section: Related Workmentioning

confidence: 99%

Containment units

Cobleigh

Osterweil

Wise

et al. 2002

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

Software is increasingly expected to run in a variety of environments. The environments themselves are often dynamically changing when using mobile computers or embedded systems, for example. Network bandwidth, available power, or other physical conditions may change, necessitating the use of alternative algorithms within the software, and changing resource mixes to support the software. We present Containment Units as a software architecture useful for recognizing environmental changes and dynamically reconfiguring software and resource allocations to adapt to those changes. We present examples of Containment Units used within robotics along with the results of actual executions, and the application of static analysis to obtain assurances that those Containment Units can be expected to demonstrate the robustness for which they were designed.

show abstract

Confessions of a used-program salesman

Cited by 30 publications

References 7 publications

A reuse triplet for systematic software reuse

A reuse triplet for systematic software reuse

Flexible Specification of Operation Behavior Using Multiple Projections

Containment units

Contact Info

Product

Resources

About