Unified Modeling Language: Systems Analysis, Design and Development Issues最新文献

{"title":"Systematic Design of Web Applications with UML","authors":"R. Hennicker, N. Koch","doi":"10.4018/978-1-930708-05-1.CH001","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH001","url":null,"abstract":"We propose a systematic design method for Web applications which takes into account the navigation space and the presentational aspects of the application. The method is based on a UML profile for the Web domain. Starting with a use case analysis and a conceptual model of the application, we first provide guidelines for modeling the navigation space. From the navigation space model we can derive, in a subsequent step, a navigational structure model which shows how to navigate through the navigation space using access elements like indexes, guided tours, queries and menus. Finally, a static and dynamic presentation model is constructed. The different models of the design process are represented by using a Web extension of UML. The strength of the presented methodology is that most steps can be performed in a semiautomatic way, thus providing the basis for a systematic mechanism for Web design. INTRODUCTION Web engineering is a new and still evolving discipline. The process of learning how to develop large Web applications has just begun. Web applications are mostly the result of an ad hoc implementation, growing usually from small to large applications that very quickly become difficult to maintain. Some guidelines and tools are beginning to appear that assist developers of Web applications, but these current practices often fail due to inappropriate techniques, processes and methodologies. The objective is to develop a suitable method that allows high-quality Web applications to be produced through the systematic construction of high-quality models. 2 Hennicker and Koch People with different skills are involved in the process of Web systems development, such as authors, layout designers, programmers, multimedia experts and marketing specialists. The role of the user is augmented and makes it more difficult to capture the requirements of the application. The non-linearity of the hyperdocuments as well as the possibility to connect easily to other Web applications increases the complexity and risk of lost in the hyperspace.“ Web engineering has also to take into account aesthetic and cognitive aspects that general software engineering environments do not support (Lowe & Hall, 1999). Moreover, the development process tends to be more fine grained, more incremental and iterative. Maintenance is an even more significant part of the lifecycle of Web applications than in traditional systems since Web technologies and user requirements change continuously. In addition, nonfunctional requirements such as security have to be addressed by a Web development process. If we restrict ourselves to the design steps, the main differences we can observe between design of Web solutions and other software applications are the heterogeneity of the designer group, the hypertext structure of nodes and links, the need for navigational assistance, the inclusion of searching and indexing mechanisms, and the presentation of the multimedia contents and the contents, e.g., fo","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"8 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123276652","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Rendering Distributed Systems in UML","authors":"P. Lago","doi":"10.4018/978-1-930708-05-1.CH009","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH009","url":null,"abstract":"This chapter is about the use of UML in the design of distributed systems. We have been using UML in the context of both international and local projects, and we continuously face the need for additional constructs that are especially conceived for distributed software components in general, and specifically for software running on middleware such as CORBA. In particular, it is our opinion that various UML diagrams would need some extensions (or customizations). Also we defined a development methodology supporting UML and a set of conventions that help us in overcoming such needs. Nevertheless, they contribute just to software documentation and communication, and do not provide any help in the low-level design phase as well as in the generation of code for the subsequent implementation phase. The chapter is intended to discuss our requirements and possible solutions.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"18 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124339902","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"UML Modeling Support for Early Reuse Decisions in Component-Based Development","authors":"J. Sykes, Pankaj Gupta","doi":"10.4018/978-1-930708-05-1.CH005","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH005","url":null,"abstract":"Component-based development is the software industry’s latest answer to some long-standing problems in software development. Its aim is to make actual reuse of existing software units (components) a widespread reality. We argue that significant reuse decisions can occur in the early stages of system development. Using a theory of the modeling process, we show that choice of abstractions and notations is critical. We investigate the kinds of models that would support early reuse decisions. We show that easily composable, business-oriented abstractions about software behaviour and a functional mental model are necessary. Evaluation of the UML in these terms emphasizes its bias towards structural mental models and abstractions derived from the software domain. INTRODUCTION Component-based development (CBD) is the software industry’s latest answer to some long-standing problems in software development (Allen & Frost, 1998; Szyperski, 1998). Building on lessons learned from earlier software-engineering innovations, CBD focuses on the goal of actual reuse of software (rather than reusability, which is simply the potential for reuse). This is seen as the key to a number of desirable economic outcomes, such as rapid development, clarification of developer roles and amortization of software development costs. If components are thought of simply as units of software, it might be concluded that reuse is mainly a matter for the design and construction phases of development, but we argue","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"63 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130887243","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"RUP - A process model for working with UML","authors":"W. Hesse","doi":"10.4018/978-1-930708-05-1.CH004","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH004","url":null,"abstract":"Recently, the Rational Unified Process (RUP) has been published as the second part of Rational’s Unified Method project. The RUP is advertised as an “iterative and incremental, use case-driven, architecture-centric” process model and aims to support system designers, builders and managers working with the Unified Modeling Language (UML) by a procedural guideline. In this chapter, a brief review and a critical analysis of the RUP is attempted. Its general aim and its contribution towards more harmonisation in the software process field are acknowledged. However, its ability to reduce the complexity of software development and to clarify its interlaced structure and terminology is doubted. Major problems may result from concepts not clearly specified like workflow or architecture. In particular, RUP core concepts like phase, iteration, workflow and milestone are debated. It is argued that RUP phases and milestones do not support the requirements of modern object-oriented (and, in particular, component-based) software projects. Iteration cycles should be based on software building blocks rather than on phases and activities. As one possible alternative to the RUP, a component-based (and truly architecturecentric) process model is sketched, and a multi-variant approach to software process modelling is recommended. INTRODUCTION: THE “UNIFIED PROCESS,” ITS HISTORY AND AIMS In the mid-'90s Rational company has started a project trying to merge some existing methodologies for object-oriented analysis and design into a common “Unified Method.” For this purpose their chief methodologist G. Booch, joined by J. Rumbaugh and (later) by I. Jacobson, tried to combine their methods which became popular at that time. Realizing that this goal was not to be achieved, within one single step the authors reduced their ambitions and started with a common metamodel and notation, an approach which resulted","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"87 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124850045","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"The Whole-Part Relationship in the Unified Modeling Language: A New Approach","authors":"F. Barbier, B. Henderson-Sellers, A. Opdahl, Martin Gogolla","doi":"10.4018/978-1-930708-05-1.CH012","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH012","url":null,"abstract":"This study of the semantics of the Whole-Part relationship in OO modeling is based upon, extends and, specifically, formalizes earlier analyses of the semantics of UML’s Aggregation and Composition (white and black diamonds, also called shared aggregation and composite aggregation). Although UML is nowadays regarded as a standard and is widely used as an OO modeling language, the way the Whole-Part relationship is formalized is unsatisfactory. Here, we provide a rigorous specification of various forms of the Whole-Part relationship using OCL (Object Constraint Language). The first part of the specification is based on the differentiation between primary characteristics (applicable to all Whole-Part relationships) assigned to a new Whole-Part metatype in the UML, and secondary features, which are possessed by subtypes of this metatype and permit the representation of several \"flavors\" of the Whole-Part relationship. This UML-compliant style of specification, based on the use of OCL as well as metamodeling, allows us to directly incorporate our results into the UML metamodel, in particular revising UML's definition of Composition.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"92 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115153034","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Linking UML with Integrated Formal Techniques","authors":"Jing Liu, J. Dong, Brendan P. Mahony, Kun Shi","doi":"10.4018/978-1-930708-05-1.CH013","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH013","url":null,"abstract":"The challenge for complex systems specification is how to visually and precisely capture static, dynamic and real-time system properties in a highly structured way. In particular, requirement specifications for composite systems often involve capturing concurrent interactions between software control parts and physical system components/devices. The requirement specifications of such systems need to capture the structure and behavior of each individual physical/ software components and their communications. In this chapter, we investigate the links between the graphical notation UML and an integrated formal notation. We present an effective combination of UML and an integrated formal method for the requirement specification of a light control system. This work is supported in part by the research grant (Integrated Formal Methods) from National University of Singapore (No. RP3991615).","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"13 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117183578","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"An Interactive Viewpoint on the Role of UML","authors":"Dina Q. Goldin, D. Keil, P. Wegner","doi":"10.4018/978-1-930708-05-1.CH015","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH015","url":null,"abstract":"The role of the Unified Modeling Language (UML) is to model interactive systems, whose behaviors emerge from the interaction of their components with each other and with the environment. Unlike traditional (algorithmic) computation, interactive computation involves infinite and dynamic (late binding) input/output streams. Algorithmic tools and models do not suffice to express the behavior of today’s interactive systems, which are capable of self-reconfiguring and adapting to their environment. Whereas procedural languages may express precise designs of closed processes, UML provides support for the inherently open-ended preliminary steps of system analysis and specification, which are becoming increasingly complex. Interactive systems require dynamic models where interaction has first-class status, and where the environment is modeled explicitly, as actors whose roles constrain the input patterns. UML’s interaction-based approach to system modeling fits well with the encapsulation-based OO approach to implementation. By coupling these approaches, the software engineering process can provide a complete solution to system design and implementation. A theoretical framework for modeling interactive computing can strengthen the foundations of UML and guide its evolution.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"71 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117002216","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Extension of the Unified Modeling Language for Mobile Agents","authors":"Cornel Klein, A. Rausch, M. Sihling, Zhaojun Wen","doi":"10.4018/978-1-930708-05-1.CH008","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH008","url":null,"abstract":"Mobile agents gained immense attraction as a new programming concept for implementing distributed applications. However, up to now mobile agent programming has been mainly technology driven, with a focus on the implementation of mobile agent platforms and only small programming applications. In this chapter, we present an extension of the standard UML that provides language concepts for modeling mobility both in analysis and design phases. This extended version of UML is applied to the modeling of an advanced telecommunication system.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"96 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124747488","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Using a Semiotic Framework to Evaluate UML for the Development of Models of High Quality","authors":"J. Krogstie","doi":"10.4018/978-1-930708-05-1.CH006","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH006","url":null,"abstract":"Many researchers have evaluated different parts of UML and have come up with suggestions for improvements to different parts of the language. This chapter looks at UML (version 1.3) as a whole, and contains an overview evaluation of UML and how it is supported in the modeling tool Rational Rose as a basis for creating models of high quality. The evaluation is done using a general framework for understanding quality of models and modeling languages in the information systems field. The evaluation is based on both practical experiences and evaluations of UML and Rational Rose made by others. Based on the evaluation, we conclude that, although being an improvement over its predecessors, UML still has many limitations and deficiencies. Also Rational Rose only partly supports the development of information system models of high quality, and provides too limited support for using different modeling techniques in concert within a larger methodological framework. INTRODUCTION According to Booch, Rumbaugh & Jacobson (1999), developing a model for an industrial strength software system before its construction is regarded increasingly as a necessary activity in information systems development. Good models are essential for communication among the members of project teams and to assure that it is possible to implement the system.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"10 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127735973","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}

{"title":"Supplementing UML with concepts from ORM","authors":"T. Halpin","doi":"10.4018/978-1-930708-05-1.CH011","DOIUrl":"https://doi.org/10.4018/978-1-930708-05-1.CH011","url":null,"abstract":"The Unified Modeling Language (UML) is useful for designing object-oriented code, but is less suitable for conceptual data analysis. Its process-centric usecases provide an inadequate basis for specifying data-centric class diagrams, and the UML graphical language suffers from incompleteness, inconsistency and unnecessary complexity. For example, multiplicity constraints can lead to unexpected problems when extended to n-ary associations, the constraint primitives are not optimized for orthogonality or expressibility, and the graphical language does not lend itself readily to verbalization and multiple instantiation for validating models with domain experts. This chapter examines some of these defects, and shows how to compensate for them by augmenting UML with concepts and techniques from the Object Role Modeling (ORM) approach. It highlights the potential of “data use cases” for seeding the data model, using verbalization of facts and rules with positive and negative examples to facilitate validation of business rules. The following approaches are suggested as possible ways to exploit the benefits of fact-orientation: use ORM for the conceptual analysis then map the ORM model to UML; use UML supplemented by informal population diagrams and user-defined constraints; enhance the UML metamodel to better support business rules.","PeriodicalId":255100,"journal":{"name":"Unified Modeling Language: Systems Analysis, Design and Development Issues","volume":"1989 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2001-04-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125491394","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}