Commitment-based software development

Mark, William R.; Tyler, Sherman W.; McGuire, James C.; Schlossberg, Jon L.

doi:10.1109/32.163604

Cited by 32 publications

(17 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…One major challenge for software engineers is judging how a change in one software module effects (and is affected by) the rest of the design. Mark [23] introduced the Comet system, which uses explicit representation and reasoning with commitments to aid the software engineering and development process. The design knowledge managed by Comet is in the form of module descriptions: structure and behaviour specifications of modules interrelated by commitment constraints.…”

Section: Other Representation Schemamentioning

confidence: 99%

“…that must be met in order to include an existing module, and can explore how commitments change when modules are modified. Comet has been applied to the domain of sensor-based tracker software [23].…”

Section: Other Representation Schemamentioning

confidence: 99%

“…The Comet system [23] uses explicit representation and reasoning with commitments to aid software design. In terms of rationale capture, it requires the user to introduce new module descriptions as specialisations of existing module descriptions, which limits the design flexibility.…”

Section: User-intervention-based Capturementioning

confidence: 99%

“…COMET [23], the software design support system for Computer-Aided Software Engineering, allows software developers to review and check any existing module descriptions in the Comet knowledgebase that are consistent with the descriptions created for a new module. There is a design memory window with a nodes-link diagram to help users with navigation.…”

Section: Navigating Archived Design Rationalementioning

confidence: 99%

See 3 more Smart Citations

A Survey of Design Rationale Systems: Approaches, Representation, Capture and Retrieval

Regli

Atwood

et al. 2000

EWC

181

110

View full text Add to dashboard Cite

This paper provides a survey on recent research in the area of design rationale. The study of design rationale spans a number of diverse disciplines, touching on concepts from research communities in mechanical design, software engineering, artificial intelligence, civil engineering, computer-supported cooperative work, and human-factors and human-computer interaction research. We focus this survey on prototype design rationale systems for these application domains, and put forward several major criteria with which to describe and classify design rationale systems, including argumentation-based, descriptive, process-based approaches. Further, we attempt to abstract the place of systems and tools for design rationale capture and retrieval in the context of contemporary knowledge-based engineering and Computer-Aided Design (CAD) tools. This survey is structured around classes of fundamentally different approaches, their representation schema, their capture methods and retrieval techniques. A number of recent design rationale systems, including JANUS, COMET, ADD. REMAP, HOS, PHIDIAS, DRIVE and IBIS are analysed. We conclude with an assessment of current state-of-the-art and a discussion of critical open research issues.

show abstract

Section: Other Representation Schemamentioning

confidence: 99%

Section: Other Representation Schemamentioning

confidence: 99%

Section: User-intervention-based Capturementioning

confidence: 99%

Section: Navigating Archived Design Rationalementioning

confidence: 99%

See 2 more Smart Citations

A Survey of Design Rationale Systems: Approaches, Representation, Capture and Retrieval

Regli

Atwood

et al. 2000

EWC

181

110

View full text Add to dashboard Cite

show abstract

“…COMET [Mark et al 1992] is concerned with assisting a developer with module design in the context of an existing design framework. Modules are viewed as having signature and behavior.…”

Section: The Comet Systemmentioning

confidence: 99%

The use of description logics in KBSE systems

Dévanbu

Jones²

1997

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

The increasing size and complexity of many software systems demand a greater emphasis on capturing and maintaining knowledge at many different levels within the software development process. This knowledge includes descriptions of the hardware and software components and their behavior, external and internal design specifications, and support for system testing. The knowledge-based software engineering (KBSE) research paradigm is concerned with systems that use formally represented knowledge, with associated inference procedures, to support the various subactivities of software development. As they grow in scale, KBSE systems must balance expressivity and inferential power with the real demands of knowledge base construction, maintenance, performance, and comprehensibility. Description logics (DLs) possess several features-a terminological orientation, a formal semantics, and efficient reasoning procedures-which offer an effective tradeoff of these factors. We discuss three KBSE systems in which DLs capture some of the requisite knowledge needed to support design, coding, and testing activities. We then survey some alternative approaches (to DLs) in KBSE systems. We close with a discussion of the benefits of DLs and ways to address some of their limitations.

show abstract

Mediation to Deal with Heterogeneous Data Sources

Wiederhold

1999

Interoperating Geographic Information Systems

View full text Add to dashboard Cite

Commitment-based software development

Cited by 32 publications

References 6 publications

A Survey of Design Rationale Systems: Approaches, Representation, Capture and Retrieval

A Survey of Design Rationale Systems: Approaches, Representation, Capture and Retrieval

The use of description logics in KBSE systems

Mediation to Deal with Heterogeneous Data Sources

Contact Info

Product

Resources

About