1998
DOI: 10.1145/299917.299919
|View full text |Cite
|
Sign up to set email alerts
|

A survey of structured and object-oriented software specification methods and techniques

Abstract: This article surveys techniques used in structured and object-oriented software specification methods. The techniques are classified as techniques for the specification of external interaction and internal decomposition. The external interaction specification techniques are further subdivided into techniques for the specification of functions, behavior, and communication. After surveying the techniques, we summarize the way they are used in structured and object-oriented methods and indicate ways in which they… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
84
0
5

Year Published

2001
2001
2009
2009

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 136 publications
(89 citation statements)
references
References 49 publications
(49 reference statements)
0
84
0
5
Order By: Relevance
“…It is important to remark that, in general, designers define underspecified postconditions [20]. This means that, given an operation contract, there are usually several final states that satisfy its postcondition.…”
Section: List Of Correctness Propertiesmentioning
confidence: 99%
See 1 more Smart Citation
“…It is important to remark that, in general, designers define underspecified postconditions [20]. This means that, given an operation contract, there are usually several final states that satisfy its postcondition.…”
Section: List Of Correctness Propertiesmentioning
confidence: 99%
“…In particular, this paper presents a new method for the verification of the behavioural aspects of software models defined using the design by contract approach [20], where each operation is defined by means of a contract consisting of a precondition (set of conditions on the operation input) and a postcondition (conditions to be satisfied at the end of the operation). In conceptual modeling, this is also known as the declarative specification of an operation, in contrast to imperative specifications where the set of updates produced by the operation on the system state is explicitly defined.…”
Section: Introductionmentioning
confidence: 99%
“…An operation contract includes a set of preconditions, which are conditions that the state of the information base must guarantee so that the operation can be executed, and a set of postconditions. The postconditions of an operation can be defined either imperatively or declaratively [32]. We will define declarative postconditions, which specify conditions that must hold after the execution of the operation.…”
Section: The System Behavior Modelmentioning
confidence: 99%
“…The contention of [11] and [27] supported by the empirical data in the CHAOS report [3] is that object-oriented methods are underdeveloped in the specification of external functions of systems and weak in guidelines for partitioning a system into components. The work of Jacobson [12] has proven to be one of the most significant advances in software engineering.…”
Section: Introductionmentioning
confidence: 99%