The software infrastructure for a Distributed System Factory

Scacchi, Walt

doi:10.1049/sej.1991.0036

Cited by 16 publications

(14 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the remainder of this section, the information structures highlighted in the preceding paragraph are elaborated, based on experiences with software hypertext environments in the System Factory Project at USC (Garg and Scacchi, 1988,1989Scacchi, 1991, Scacchi 1991) and elsewhere (Anderson 1999;Cybulski and Reed, 1992;Fielding and co-workers, 1998;OinasKukkonen 1999;Whitehead 1997;Wiil, Nurnberg, and Leggett 1999).…”

Section: The Structure Of Information In Software Productionmentioning

confidence: 99%

“…Partitions provide a semantic structuring mechanism (Sacerdoti 1977) whereby collections of hierarchical indices of nodes can be composed, standardized, and shared by classes of users. For example, in the System Factory Project, partitions were organized by work group, project, or project site (Scacchi, 1991;Noll and Scacchi, 1991). Partitions represent contexts (Delisle andSchwartz, 1987, Sacerdoti 1979) for structuring access to a hypertext of software object descriptions.…”

Section: Software Hypertext Information Structuresmentioning

confidence: 99%

“…As such, these software process descriptions at varying levels of detail can not be guaranteed a priori to be consistent, complete, or correct under all possible performance circumstances. Hence the need arises for viewing the creation and manipulation of software process tasks as (semi-structured descriptions that should be managed as domain-specific hypertext (Garg and Scacchi, 1989;Noll and Scacchi 2001;Scacchi, 1989Scacchi, ,1991.…”

Section: Software Hypertext Information Structuresmentioning

confidence: 99%

“…Next, the domain of software production is examined in order to identify how hypertext tools and document production/consumption techniques can play a role to facilitate software engineering objectives. The focus then shifts to describe the structure of information to evolve within a DSHE in terms of product, task, and setting information for the domain of software production (Anderson 1999;Cybulski and Reed, 1992;Garg andScacchi, 1989,1990;Oinas-Kukkonen 1999;Scacchi 1991,1999;Roth, Aiken, and Hobbs 1994;Scacchi, 1989Scacchi, ,1991Wiil, Nurnberg, and Leggett 1999). Together, these sections then set the final stage for a discussion of the power of DSHE.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Hypertext for Software Engineering

Scacchi¹

2002

Encyclopedia of Software Engineering

Self Cite

View full text Add to dashboard Cite

What is the power of hypertext in supporting software engineering? (The term “hypertext” is treated throughout as synonymous with “hypermedia,” which denotes the nonlinear representation of interrelated textual, graphic, filmic, or auditory information.) Power in other contexts usually refers to the ability of some entity or agent to affect the behavior of another or to achieve advantage over another in ways that the other cannot avoid. Following this, one might expect that as a technology , hypertext systems offer relative advantage over alternatives to automated text/document information systems, including conventional word processing systems, file systems, and database management systems. Hypertext systems offer a degree of information processing power that enables new kinds of applications, much like the advent of expert system shells enabled the creation of expert applications for domains such as computer configuration and diagnostic pathology. Similarly, as a medium for writing and reading electronic documents hypertext systems allow the redefinition of the structure and content of documents that alter the constraints and opportunities for conveying information in contrast to the linear print medium. Thus the power of hypertext in whatever form it exists is subtle and incremental; it is potential rather than kinetic. However, such power can accumulate in different application domains in the long run if effectively mobilized and integrated with domain‐specific tasks, processing mechanisms, and workflows. The power of hypertext technology in different application domains can be realized in a number of ways. In particular, technology that supports a unified view of the hypertext documents, production processes, processing mechanisms, and settings of use appears to offer the greatest power at this time. To see this, the concept of a domain‐specific hypertext environment (DSHE) is defined in the following section. Next, the domain of software production is examined in order to identify how hypertext tools and document production/consumption techniques can play a role to facilitate software engineering objectives. The focus then shifts to describe the structure of information to evolve within a DSHE in terms of product, task, and setting information for the domain of software production. Together, these sections then set the final stage for a discussion of the power of DSHE. Subsequently, seven ways the power of DSHE can be realized are identified, followed by an examination of the costs that are borne in order to realize this power.

show abstract

Section: The Structure Of Information In Software Productionmentioning

confidence: 99%

Section: Software Hypertext Information Structuresmentioning

confidence: 99%

Section: Software Hypertext Information Structuresmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Hypertext for Software Engineering

Scacchi¹

2002

Encyclopedia of Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…The currently popular "Re-engineering the Organization" is classical systems analysis applied to existing organizations to remove glue. Some organizational domains have been analyzed, such as the software system factory [27]. Organizational processes and technical development processes are co-dependent.…”

Section: Conclusion and The Next 10 Yearsmentioning

confidence: 99%