Figure 8 - uploaded by Zhiming Liu - 刘志明
Content may be subject to copyright.
Source publication
Abstract These notes present the basic engineering principles, methods and practice of how a large system can be specified, desigined and implemented using object - oriented techniques The overall purpose of the notes is to give a understanding of problems of large - scale software development and how this can be solved using object - oriented tech...
Similar publications
Resumen— En el proceso de desarrollo de software, el re-conocimiento automático de operaciones de clases a partir de los requerimientos del sistema, es un tema de investigación complejo que se ha venido desarrollando por varios autores [1-4] en diferentes proyectos de investigación y á un permanece abierto. En este artículo se presenta una propuest...
Regarding modularised software development, Aspect-oriented programming (AOP) identifies and represents individually crosscutting concerns during the software development cycle's programming stage. This article proposes and applies OOAspectZ to formal Aspect-oriented requirement specifications for prior stages of the software development cycle. It...
In Software engineering, elicitation phase consists of identifying functional and non-functional requirements. Functional properties describe all user functionalities realized by the future software. Non-functional properties define the overall qualities or attributes of the resulting system. Both kinds of properties are relevant to software develo...
In this chapter, a software modeling language—Unified Modeling Language (UML)—is reviewed as a part of software intensive system development process. The review includes the evolution of UML by paying most attention on the diagrams included in versions 1.x and 2.x as well as on the formalism development used to specify the language. The review of U...
Citations
... All these models together describe the system being designed. Moreover, the modeling languages in UML can be used for different stages of development, including requirement capture and analysis, design and implementation [22,23]. ...
... And these models together describe the system being designed. Moreover, the modeling languages in UML can be used for different stages of development, including requirement capture and analysis, design and implementation [39,40]. But this also causes the main drawback of the current UML standard: the lack of a unifying formal semantics. ...
Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.3.2 Multiple Inheritance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.4 Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.5 Semantics of Class Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.6 Examples in Checking Consistency of Class Diagrams . . . . . . . . . . . . . . . . . . 355 Use Cases 375.1...
With one of the most interesting developments in the Information Age is the emergence of the Internet technology in education where the teaching and learning process play a major role. The education world is experiencing a change not just in terms of curriculum but also in terms of approaches to teaching and learning strategies. These changes in learning strategies from traditional to dynamic strategies based on the use of information technology create a learner centered learning environment. The most important role of an instructor in an online environment is a high degree of interactivity and participation. This means designing and conducting learning activities that result in engagement with the subject matter and with fellow learners using proper pedagogical approaches are very important.The development of e-Learning in the sciences in general and in mathematics in particular has not met the general expectations. The instructional design of the teaching of mathematics incorporates the elements on Mathematical Approaches, Hierarchy of Teaching, Interactive Multimedia, Systematically Designed and Developed Teaching and Learning Modules and Sub Modules, and Holistic Development of Students OO (Object-Oriented) analysis and design techniques were developed to help in the modeling of business, the analysis of requirements and the design software. With the rapid growth of OO technology, a number of techniques in OO have been developed and integrated. UML was designed to bring together the best feature of a number of analysis and design techniques and notations to produce an industry standard.The Unified Modeling Language (UML) is an effective and popular notation which is used to capture high-level designs for software systems. However, one aspect of soft are system design which is not typically captured in a UML document is a record of the likely (or desired) rate of performance of the major activities of the system. When this information is not included in the initial UML description of a system it increases the likelihood that the performance of the software system being developed will not b e considered until very late in the software development process.
Being a successful technique in software practice, Object Orientation (OO) is a hot topic in academic research fields. Among many formalisms, rCOS, a refinement calculus of object-oriented systems based on Unifying Theories of Programming (UTP), has been proven a promising one in the sense of its applications to incremental software constructions, the formal use of UML, etc. However, equipped with a semantics reasoning on both static and dynamic properties, rCOS is not designed for static checking. We believe introducing static checking will extend the power of rCOS. In this paper, we develop a type system for rCOS and prove some type safety theorems. To make the theoretical results of this paper convincible and easy to be understood, we follow the traditional approaches of type systems construction. That is, we use an operational semantics as the basic explanation of rCOS language in spite of the fact that rCOS is originally developed in a denotational framework.
This paper develops a mathematical characterisation of object-oriented concepts by defining an observation-oriented semantics for an object-oriented language (OOL) with a rich variety of features including subtypes, visibility, in- heritance, dynamic binding and polymorphism. The language is expressive enough for the specification of object-oriented designs and programs. We also propose a calculus based on this model to support both structural and behavioural refine- ment of object-oriented designs. We take the approach of the development of the design calculus based on the standard predicate logic in Hoare and He's Unifying Theories of Programming (UTP). We also consider object reference in terms of object identity as values and mutually dependent methods.
We present a model of object-oriented and component-based refinement. For object-orientation, the model is class-based and refinement is about correct changes in the structure, methods of classes and the main program, rather than changes in the behaviour of individual objects.
This allows us to prove refinement laws for both high level design patterns and low level refactoring. For component-based
development, we focus on the separation of concerns of interface and functional contracts, leaving refinement of interaction protocols in future work. The model supports the specification of these aspects at different levels of abstractions and their consistency.
Based on the semantics, we also provide a general definitional approach to defining different relational semantic models with
different features and constraints.
We discuss the promises and problems of UML-based development. We then suggest a framework in which UML can be used precisely and more disciplined so as to solve the problems and meet the promises better.
E-commerce systems have been changing traditional business activities through the Internet. This paper presents a formal use of the Unified Modeling Language (UML) to analyze and design e-commerce systems using an online ticketing system as a case study. An e-commerce system can be seen as a client-server system in which a server maintains some information and provides a searching function to a client. However, for an e-commerce system we also need to consider two specific functions for booking products and carrying out payment transactions. We demonstrate how to use the formalization of UML given by Xiaoshan et al. (2001) in formal specification of the system functional requirements, safety and liveness constraints, and in verification of the correctness of the design.
