2004
DOI: 10.1007/978-3-540-30187-5_15
|View full text |Cite
|
Sign up to set email alerts
|

From Informal to Formal Specifications in UML

Abstract: Abstract. In this paper, we consider a way of bridging informal and formal specification. Most projects have a need for an informal description of the requirements of the system which all people involved can understand. At the same time, there is a need to make some of the requirements more formal. We present a way to relate informal requirements, in form of use cases, to more formal specifications, written in the Object Constraint Language (OCL). Our approach gives the customers of software systems a way of g… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
19
0
1

Year Published

2005
2005
2018
2018

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(20 citation statements)
references
References 7 publications
0
19
0
1
Order By: Relevance
“…As Cabot et al argue in [14], ''the modeling community is continuously pushing forward the OCL", and ''OCL is used in quite different application domains (domain-specific language and web semantics) as well as for various purposes (model verification and validation, code-generation, test-driven development, and transformations)". The availability of quality indicators of OCL expressions benefit those purposes and help to evaluate possible changes in maintainability [20,36]. There is great room for future work, in several directions.…”
Section: Discussionmentioning
confidence: 99%
“…As Cabot et al argue in [14], ''the modeling community is continuously pushing forward the OCL", and ''OCL is used in quite different application domains (domain-specific language and web semantics) as well as for various purposes (model verification and validation, code-generation, test-driven development, and transformations)". The availability of quality indicators of OCL expressions benefit those purposes and help to evaluate possible changes in maintainability [20,36]. There is great room for future work, in several directions.…”
Section: Discussionmentioning
confidence: 99%
“…Mohammad Reza Nami and Hassami [18] describe properties and types of formal specification languages (Z language, VDM, RSL and CSP) in software engineering. Giese and Heldal [19] build a semiformal model of ATM system with the help of UML and OCL. Daniel Jackson [20] proposes an example of an object model is given in full in three languages: Alloy, Z language, and UML.…”
Section: Related Workmentioning
confidence: 99%
“…A work with a similar goal is presented in (Giese and Heldal, 2004). Giese and Heldal propose an approach aiming at bridging the gap between informal and formal requirements.…”
Section: Related Workmentioning
confidence: 99%