Abstraction and Refinement techniques applied to Object - Oriented Conceptual Models, allows Software Engineers debugging stakeholders' requirements, getting optimal and valid products that guarantee the information consistency at the development stage. In this paper, we propose a method that provides refinement rules, expressed in a formal language to be used in the transition between analysis and design stages of the Information Systems Life Cycle. Specifically, these rules are taken from use a case whose functionality is expressed by methods and derived attributes belonging to related classes to the use case.
Data provided are for informational purposes only. Although carefully collected, accuracy cannot be guaranteed. The impact factor represents a rough estimation of the journal's impact factor and does not reflect the actual current impact factor. Publisher conditions are provided by RoMEO. Differing provisions from the publisher's actual policy or licence agreement may be applicable.
[Show abstract][Hide abstract]ABSTRACT: It is well-known that uncontrolled change to software can lead to increasing evolution costs caused by deteriorating structure and compromised system qualities. For complex systems, the need to carefully manage system evolution is critical. In this paper we outline an approach to managing evolution of object-oriented (OO) software. The approach is based on a goal-directed, cyclic process, in which OO models are transformed and quantitatively evaluated in each cycle. Evaluation criteria guide developers in choosing between alternative transformations in each cycle. The process, transformations, and evaluation techniques can be used to develop systems from a set of baseline models.
[Show abstract][Hide abstract]ABSTRACT: We propose refinement laws for the top level design elements of Real Time UML (UML-RT): classes and capsules. These laws can be used to develop concrete design models from abstract analysis models. Laws for introducing and decomposing classes and capsules are presented. Standard data refinement techniques are adapted for classes, and process refinement techniques for capsules. We also propose techniques for behavioural inheritance of classes and capsules. Soundness is briefly addressed by relating UML-RT elements to OhCircus, a formal unified language of classes and processes. To illustrate the overall strategy, we develop a detailed design of an operating system resource scheduler from a high-level analysis model.
Full-text · Article · May 2004 · Electronic Notes in Theoretical Computer Science
[Show abstract][Hide abstract]ABSTRACT: C or ; Abstract-Cut = L n dl(C) L 6= L C or L Match match C with S end Class-Context E[C] ] Evaluation contexts for classes E ::=  j match E with S end j E or C j C or E Rules for lters Filter-Apply K 1 & K . P with K 1 ) K 2 . Q j S 7! K 2 & K . P & Q or dl(K 1 ) n dl(K 2 ) Filter-Next dl(K 1 ) 6 dl(M) Filter-End C with ; 7! C Filter-Or C 1 with S 7! C 1 C 2 with S 7! C (C 1 or C 2 ) with S 7! C Filter-Abstract L with S 7! L 10 plify abstract classes, rule Class-Abstract discards empty abstract classes; rule Abstract-Cut discards abstract labels that are declared elsewhere. Rule Match reduces selective re nements match C with S end by means of an auxiliary relations, described below. Rule Class-Context applies rewriting under disjunctions and selective re nements.
Inheritance in the join calculus, in ‘Foundations of Software Technology and Theoretical Computer Science (FSTTCS2000)’, New Delhi Multi-view software evo-lution:a uml-based framework for evolving object-oriented software. C Fournet, C Laneve, L Maranget, D Remy. 397-408.
Class and cap-sule refinement in uml for real timeWorkshop de Métodos Formais Extending the uml meta-model to support software refinementUnified modeling language uml. resource page. C Larman, Prentice Patrones, Segunda Hall, Edición, Madrid, A Sampaio, A Mota, R Ramos. 35-42.