Experiences modelling and using object-oriented telecommunication service frameworks in SDL

This paper describes experiences in using SDL and its associated tools to create telecommunication services by producing and specialising object-oriented frameworks. The chosen approach recognises the need for the rapid creation of validated telecommunication services. It introduces two stages to service creation. Firstly a software expert produces a service framework, and secondly a telecommunications ‘business consultant' specialises the framework by means of graphical tools to rapidly produce services. Here the focus is given to the underlying technology required. In particular, the advantages and disadvantages of SDL and tools for this purpose are highlighted

Literate modelling: capturing business knowledge with the UML

At British Airways, we have found during several large OO projects documented using the UML that non-technical end-users, managers and business domain experts find it difficult to understand UML visual models. This leads to problems in requirement capture and review. To solve this problem, we have developed the technique of Literate Modelling. Literate Models are UML diagrams that are embedded in texts explaining the models. In that way end-users, managers and domain experts gain useful understanding of the models, whilst object-oriented analysts see exactly and precisely how the models define business requirements and imperatives. We discuss some early experiences with Literate Modelling at British Airways where it was used extensively in their Enterprise Object Modelling initiative.We explain why Literate Modelling is viewed as one of the critical success factors for this significant project. Finally, we propose that Literate Modelling may be a valuable extension to many other object-oriented and non object-oriented visual modelling languages

Designing Software Architectures As a Composition of Specializations of Knowledge Domains

This paper summarizes our experimental research and software development activities in designing robust, adaptable and reusable software architectures. Several years ago, based on our previous experiences in object-oriented software development, we made the following assumption: ‘A software architecture should be a composition of specializations of knowledge domains’. To verify this assumption we carried out three pilot projects. In addition to the application of some popular domain analysis techniques such as use cases, we identified the invariant compositional structures of the software architectures and the related knowledge domains. Knowledge domains define the boundaries of the adaptability and reusability capabilities of software systems. Next, knowledge domains were mapped to object-oriented concepts. We experienced that some aspects of knowledge could not be directly modeled in terms of object-oriented concepts. In this paper we describe our approach, the pilot projects, the experienced problems and the adopted solutions for realizing the software architectures. We conclude the paper with the lessons that we learned from this experience

On Teaching an Object-Oriented Database Module in Undergraduate CS/IS Curricula

As object-oriented technology becomes more and more prevalently used in the computing industry, it is important that the computing science curricula keep up with the technological trend. The literature shows numerous efforts in this direction but few have dealt with object-oriented databases. Much of the efforts are in the areas of incorporating object-orientation into introductory computing courses or integrating special topics courses on object-oriented programming into the curricula. This paper describes the experiences that the author had while integrating object-orientation into a CS/IS curriculum. In particular, it illustrates where and how object-oriented databases can be introduced in an introductory DBMS course by using some object-oriented DBMS prototypes. A sample module for introducing object-oriented databases is also presented

Large project experiences with object-oriented methods and reuse

The SSVTF (Space Station Verification and Training Facility) project is completing the Preliminary Design Review of a large software development using object-oriented methods and systematic reuse. An incremental developmental lifecycle was tailored to provide early feedback and guidance on methods and products, with repeated attention to reuse. Object oriented methods were formally taught and supported by realistic examples. Reuse was readily accepted and planned by the developers. Schedule and budget issues were handled by agreements and work sharing arranged by the developers

Object-Oriented Development "The New Design Problem"

New techniques often involve innovative approaches and looking at the problem they address from a different perspective: OO will be of heavy impact of the software construction. The technological shift from classical development and structured methods to evolutionary development and object-oriented methods is certainly not easy. We must given it the time and the means in terms of structures, training, staff, and support for all to come effective. C,S has joined several R&D projects to test if and how Object Orientation can be applied to its software. We share here our considerations on OO development and the understanding obtained through practical experiences within the CMS object oriented activities and the RD41 (Moose) project

Object-Oriented Business Solutions

This report summarises the presentations, discussions, and main results of the ECOOP’01 Workshop on Object-Oriented Business Solutions (WOOBS). It was not a pure scientific meeting, but a mixed gathering where people from the industry and the academia met to exchange ideas, experiences and build a network of relationships with others committed to the emergence of object-oriented business solutions. WOOBS had an invited talk on quality of service, twelve presentations and lively discussions during and after them. The main conclusions were on the importance of Multi-Organisational Web-Based Systems in today’s e-commerce world, which justifies the study of a new multidisciplinary paradigm called Web-Oriented Programming

The AutoProof Verifier: Usability by Non-Experts and on Standard Code

Formal verification tools are often developed by experts for experts; as a result, their usability by programmers with little formal methods experience may be severely limited. In this paper, we discuss this general phenomenon with reference to AutoProof: a tool that can verify the full functional correctness of object-oriented software. In particular, we present our experiences of using AutoProof in two contrasting contexts representative of non-expert usage. First, we discuss its usability by students in a graduate course on software verification, who were tasked with verifying implementations of various sorting algorithms. Second, we evaluate its usability in verifying code developed for programming assignments of an undergraduate course. The first scenario represents usability by serious non-experts; the second represents usability on "standard code", developed without full functional verification in mind. We report our experiences and lessons learnt, from which we derive some general suggestions for furthering the development of verification tools with respect to improving their usability.Comment: In Proceedings F-IDE 2015, arXiv:1508.0338