Ana Moreira & R. Clark : "Adding Rigour to Object-Oriented Analysis", Software Engineering Journal, vol.11, n5, pp.270-280, July, 1996.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....a target language that has constructs and semantics suitable for representing the requirements and designs of embedded systems. Hartrum and Bailor [8] give a set of high level guidelines for linking together a subset of the OMT notation with Z [21] The Rigorous Object Oriented Analysis (ROOA) [15] formalizes object oriented analysis notations in terms of the LOTOS specification language, with an emphasis on requirements analysis capabilities. Hayes and Coleman [9] have used a VDM like [11] notation to perform a preliminary formalization of a designspecific subset of the object model of ....

A. M. D. Moreira and R. G. Clark. Adding rigour to object-oriented analysis. Software Engineering Journal, 11(5):270--280, 1996.

....except through the limited swimlines) Furthermore, UML is a modeling notation and is not too concerned with formal validation of prototypes and formal generation of test suites, while SPEC VALUE focuses on these two aspects. ROOA: In their Rigorous Object Oriented Analysis (ROOA) method [30], Moreira and Clark integrate formal techniques with object oriented analysis methods (i.e. OMT [36] in order to generate executable prototypes (in LOTOS) and validate them against the requirements. ROOA considers the system as a set of concurrent objects, modelled by LOTOS processes. The method ....

Moreira, A.M.D. and Clark, R.G. (1996) "Adding Rigour to Object-Oriented Analysis". In: Software Engineering Journal, 11(5), 270-280.

.... development methods [11] For example, 6] shows how message flow diagrams (equivalent to UML collaboration diagrams) can be given a semantics in terms of partial orders on events; 4] shows how the specification language Larch can be used to give a formal semantics to static object diagrams; and, [10] shows how LOTOS can be used to produce an executable object oriented design. In all of these cases, the specification language which is used either does not address the complete design notation or is executable and therefore in danger of leading to over specification. We claim that modal logic ....

A. Moreira, R. Clark. Adding Rigour to Object-Oriented Analysis. Software Engineering Journal, September 1996.

.... research area [Rui95] For example [Cit95] shows how message diagrams (equivalent to UML collaboration diagrams) can be given a semantics in terms of a partial order on events; Bou95] shows how the specification language Larch can be used to give a formal semantics to static object diagrams; and, [Mor96b] [Mor96a] can be used to produce executable objectoriented designs. The use of category theory to capture the essential characteristics of systems dates back to Goguen [Gog75] who updated the approach to address concurrent object oriented systems in [Gog90] Sheaf theory is a general mechanism ....

Moreira, A. & Clark, R.: Adding Rigour to Object-Oriented Analysis. Software Engineering Journal, September 1996.

.... research area [Rui95] For example [Cit95] shows how message diagrams (equivalent to UML collaboration diagrams) can be given a semantics in terms of a partial order on events; Bou95] shows how the specification language Larch can be used to give a formal semantics to static object diagrams; and, [Mor96b] [Mor96a] can be used to produce executable objectoriented designs. 36 The use of category theory to capture the essential characteristics of systems dates back to Goguen [Gog75] who updated the approach to address concurrent object oriented systems in [Gog90] Sheaf theory is a general ....

Moreira, A. & Clark, R.: Adding Rigour to Object-Oriented Analysis. Software Engineering Journal, September 1996.

.... an active research area [13] For example [5] shows how message diagrams (equivalent to UML collaboration diagrams) can be given a semantics in terms of a partial order on events; 4] shows how the specification language Larch can be used to give a formal semantics to static object diagrams; and, [12] can be used to produce executable object oriented designs. Our approach contributes to this area by identifying a potentially fruitful collaboration of ideas. The use of category theory to capture the essential characteristics of systems dates back to Goguen [10] who updated the approach to ....

Moreira, A. and Clark, R., Adding Rigour to Object-Oriented Analysis. Software Engineering Journal, September 1996.

....1.1 Background As we believe that there are many benefits in a formal approach to software development, we have been investigating how formality can be introduced into the object oriented analysis process. The first result of this study was the Rigorous Object Oriented Analysis (ROOA) method [13, 14, 15, 16, 17]. The ROOA method provides a process for the systematic construction of an executable, formal and object oriented specification from a set of informal requirements. The aim is to give a complete and accurate description of the static, dynamic and functional aspects of a problem in terms of ....

....to be detected sufficiently early in the development so that feedback can be given to the requirements capture process. When a problem is process oriented, only a very simple object model showing the most obvious objects and associations can be constructed without considering dynamic behaviour [17]. This simple object model corresponds to what Jacobson calls the domain object model [11] In such cases, scenarios and event trace diagrams already play an important part in the ROOA method and help to identify the objects and their interactions and to identify dynamic behaviour. However, the ....

Moreira, A.M.D., Clark, R.G.: Adding Rigour to Object-Oriented Analysis. Software Engineering Journal 11(5), 270-280, 1996.

....this report, we demonstrate the suitability of using SDL as the FDT [1] This differs from other work on SDL which has concentrated on the design phase of the software life cycle. Our previous work in this area used LOTOS [2, 3] and the result is the Rigorous Object Oriented Analysis (ROOA) method [4, 5]. Here we use ROOA as the vehicle to demonstrate the suitability of using SDL in the analysis phase. Our interest has been to produce a rigorous process that can be used by systems engineers as part of a development process. Our goal is to make FDTs more acceptable to those systems engineers who ....

....and so this approach cannot deal with the dynamic creation of aggregates. We therefore use SDL blocks purely as a static structuring mechanism and always represent objects by processes and classes by process types. 3. 6 Direct language support Although LOTOS can be used in an object oriented style [5], a major advantage of using SDL is that it has object oriented features such as inheritance built in. Another advantage of SDL is that it has specific language constructs, packages and blocks, to deal with the structuring of large systems into manageable and reusable units. There is a graphical ....

A. Moreira and R. Clark, Adding Rigour to Object-Oriented Analysis, Software Engineering Journal 11(5), 270-280, 1996.

No context found.

Ana Moreira & R. Clark : "Adding Rigour to Object-Oriented Analysis", Software Engineering Journal, vol.11, n5, pp.270-280, July, 1996.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC