A model for understanding complexities of developing large-scale software systems

Bobbie, Patrick O.; Urban, Josef

doi:10.1109/tai.1989.65298

Cited by 4 publications

(2 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…(Examples of SA objects are: requirements specification document, test data file, audit and review report, target system configuration report, design document, user guide, performance criteria document.) A conceptual-level knowledge acquisition tool is assumed to be available, e.g., a query-answer expert system shell [2,3] that facilitates the elicitation and representation of descriptive data in two modes.…”

Section: A Framework For Requirements Elicitationmentioning

confidence: 99%

See 1 more Smart Citation

A knowledge-driven methodology for eliciting and restructuring software requirements for distributed design

Bobbie

Urban²

[1990] Proceedings of the 2nd International IEEE Conference on Tools for Artificial Intelligence

Self Cite

View full text Add to dashboard Cite

Some important issues in engineering the requirements of a distributed software system and methods that facilitate software system design for distributed or parallel implementations are discussed. The issues are presented from a knowledge engineering perspective and divided into four levels: acquisition; representation; structuring; and design. The acquisition level entails the methods for eliciting system requirements data (attributes and relationships of software entities) from the end-user group using a model of context classes. A context class is a domain of a software system in which software objectdentities have similar attributes or relationships. The representation level deals with the language paradigm for representing the attributes and relationships of the software entities. The structuring level addresses methods for rearranging and grouping the software objects of the context classes into related clusters. The design level deals with methods for mapping or transforming the clusters of software objects into specification modules to facilitate distributed design. To this end, the design level employs an object-based paradigm for specifying the attributes and abstract behavior of the objects within the modules.K e y w o r d s : clusters of specifications, data clustering, distributed object-oriented design (DOOD), distributed representation and implementation, frame-based systems, knowledge acquisition, PROLOG, requirements elicitation.

show abstract

Section: A Framework For Requirements Elicitationmentioning

confidence: 99%

“…The details of the partitioning algorithm [2] are omitted for the sake of brevity. However, for completeness of the discussion, we describe the algorithm to motivate its applicability to reorganizing the elicited data for distributed implementation.…”

Section: Partitioning and Clusteringmentioning

confidence: 99%