[서평]「The Unified Modeling Language User Guide」

Software engineering: theory and practice

We come up with the money for you this proper as competently as easy pretension to acquire those all. We find the money for applying uml and patterns an introduction to object oriented analysis and design an approach to object oriented analysis and design and numerous book collections from fictions to scientific research in any way. along with them is this applying uml and patterns an introduction to object oriented analysis and design an approach to object oriented analysis and design that can be your partner.

[서평]「Applying UML and Patterns - An Introduction to Object-Oriented Analysis and Design」

ContextUse cases have been widely accepted and acknowledged as a specification tool for specifying the functional requirements of a software system. Many variations of use cases exist which tries to address the issues such as their completeness, degree of formalism, automated information extraction, usability, and pertinence. ObjectiveThe aim of this systematic review is to examine the existing literature for the evolution of the use cases, their applications, quality assessments, open issues, and the future directions. MethodWe perform keyword-based extensive search to identify the relevant studies related to use case specifications research reported in journal articles, conference papers, workshop papers, bulletins and book chapters. ResultsThe specified search process resulted 119 papers, which were published between 1992 and February 2014. This included, 54 journal articles, 42 conference papers, 2 ACM/IEEE bulletins, 12 book chapters, 6 workshop papers and 3 white papers. We found that as many as twenty use case templates have been proposed and applied for various software specification problems ranging from informal descriptions with paragraph-style text to more formal keyword-oriented templates. ConclusionUse cases have been evolved from initial plain, semi-formal textual descriptions to a more formal template structure facilitating automated information extraction in various software development life cycle activities such as requirement documentation, requirement analysis, requirement validation, domain modeling, test case generation, planning and estimation, and maintenance. The issues that remain to be sorted out are (1) the right degree of formalism, (2) the efficient change management, (3) the industrial relevance, and (4) assessment of the quality of the specification. Additionally, its synergy with other software models that are used in the development processes is an issue that needs to be addressed.

A systematic literature review of use case specifications research

Satellite Events at the MoDELS 2005 Conference.

Use cases describe a set of interactions between actors/users and the system under study. These interactions should be described textually according to some style and template to be simultaneously readable, consistent and verifiable. The main reason for these qualities is that use cases specification should be used both by business analysts and requirements engineers, when specifying functional requirements, as well as by software developers, when designing and implementing the involved system functionality. In spite of the popularity of use cases, there are not many patterns and guidance to help produce use cases specifications in a systematic and high-quality way. Furthermore, in the context of Model Driven Development (MDD) approaches, use cases specifications can be also considered models with precise syntax and semantics to be automatically validated or used in model-to-model or model-to-text transformations.In this paper we propose a pattern language to improve the quality of use cases specifications. These patterns are concrete guidelines that have emerged from the research and industrial experience of the authors throughout the years, particularly in the designing of MDD languages and approaches and in applying them in concrete applications. These patterns are interconnected among themselves and are the following: (P1) Define Use Case Types, (P2) Keep Use Case Consistentwiththe Domain Model, (P3) Define Use Casewith Different Scenarioand Interaction Block Types, and (P4) Define Use Casewith Different Action Types.

A pattern language for use cases specification

The aim of this study is to identify the correlations between the use case model, data model and the desired user interface (UI). Since use cases describe the interaction between the users and the system, implemented through the user interface with the aim to change the state of the system, the correlation between these three components should be taken into account at the software requirements phase. In this study, the authors have introduced the meta-model of software requirements developed on the identified correlations. Based on this meta-model, it is possible to create a model of concrete software requirements, which enables not only the design and implementation of the user interface, but also the automation of this process. In order to prove the sustainability of this approach, they have developed a special software tool that performs the transformation of the model to an executable source code. They have considered different ways of user interaction with the system, and consequently, they have recommended the set of most common user interface templates. Thus the flexibility of the user interface is achieved, as the user interface of the same use case could be displayed in several different ways, while still maintaining the desired functionality.

Model and software tool for automatic generation of user interface based on use case and data model

Requirements specification includes technical concerns of an information system and is used throughout its life cycle. It allows for sharing the vision of the system among stakeholders and facilitates its development and operation processes. Natural languages are the most common form of requirements representation, however, they also exhibit characteristics that often introduce quality problems, such as inconsistency, incompleteness, and ambiguousness. This paper adopts the notions of linguistic pattern and linguistic style and discusses their relevance to produce better technical documentation. It focuses on the textual specification of data entities, which are elements commonly referred to throughout different types of requirements, like use cases, user stories, or functional requirements. This paper discusses how to textually represent the following elements: data entity, attribute, data type, data entity constraint, attribute constraint, and even cluster of data entities. This paper shows concrete examples and supports the discussion with three linguistic styles, represented by a rigorous requirements specification language and two informal controlled natural languages, one with a more compact and another with a more verbose, expressive, and complete representation. We analyzed how other languages cope with the representation of these data entity elements and complemented that analysis and comparison based on the PENS classification scheme. We conducted a pilot evaluation session with nineteen professional subjects who participated and provided encouraging feedback, with positive scores in all the analyzed dimensions. From this feedback, we preliminarily conclude that the adoption of these linguistic patterns would help to produce better requirements specifications written more systematically and consistently.

https://www.mdpi.com/2076-3417/11/9/4119/pdf

Linguistic Patterns and Linguistic Styles for Requirements Specification: Focus on Data Entities

The software requirements engineering (RE) process is one of the key processes in software development. The aim of requirements engineering process is capturing, understanding and analyzing customer requirements. Today, use cases are widely used as a technique for specification of the functional requirements of the system. Even through use cases are widely used for specification of the functional requirements, their semantics are unclear that it is difficult to apply them to complex problems. In this paper we have proposed SilabReq language for use cases specification for a standard information system. It is developed under XText framework. The benefits of using SilabReq for use cases specification are reflected in the fact that software requirements are considered as a model. Thereafter, the use cases can be used for automatic processing and analyzing.

Language for Use Case Specification

The software requirements engineering process is a part of a software development process and one of the key processes in software development. The elicitation, analysis, specification and validation of software requirements occur during the requirements engineering process. Use cases are used as a technique for functional system specification. Different notations can be used for a use case specification. In this paper, we present SilabReq Domain Specific Language (SilabReq DSL) for use case specification. On the one hand, we develop this language to describe the use cases in clear and precise way through the meta-model, and on the other hand to specify the use cases to be readable and understandable for all stakeholders in the software development project. This allows us to develop different transformations to get the structure and the behavior of the system from defined use cases. In this paper apart from the SilabReq DSL, we present some of these transformations.

/pdf/use-case-specification-using-the-silabreq-domain-specific-47rcr9uoxk.pdf

Dušan Savić

Papers

A pattern language for use cases specification

Model and software tool for automatic generation of user interface based on use case and data model

Linguistic Patterns and Linguistic Styles for Requirements Specification: Focus on Data Entities

Language for Use Case Specification

Use case specification using the silabreq domain specific language