Improving Quality of Use-Case Models by Correlating Defects, Difficulties, and Modeling Strategies

Author(s):  
Cristiana Pereira Bispo ◽  
Ana Patrícia Magalhães ◽  
Sergio Fernandes ◽  
Ivan Machado
Keyword(s):  
Use Case ◽  
Author(s):  
Pankaj Kamthan

As software systems become ever more interactive, there is a need to model the services they provide to users, and use cases are one abstract way of doing that. As use cases models become pervasive, the question of their communicability to stakeholders arises. In this chapter, we propose a semiotic framework for understanding and systematically addressing the quality of use case models. The quality concerns at each semiotic level are discussed and process- and product-oriented means to address them in a feasible manner are presented. The scope and limitations of the framework, including that of the means, are given. The need for more emphasis on prevention over cure in improving the quality of use case models is emphasized. The ideas explored are illustrated by examples.


Author(s):  
Pankaj Kamthan

The majority of the present software systems, such as those that run on automatic banking machines (ABMs), on mobile devices, and on the Web, are interactive in nature. Therefore, it is critical to precisely understand, identify, and document the services that an interactive software system will provide from the viewpoint of its potential users. A large and important class of models that these services encapsulate is use cases (Jacobson, Christerson, Jonsson, & Övergaard, 1992). In the last few years, use cases have become indispensable as means for behavioral modeling of interactive software systems. They play a crucial role in various software development activities, including estimating development cost (Anda, 2003), eliciting behavioral requirements, and defining test cases. It is well known that addressing quality early is crucial to avoid the propagation of problems to later artifacts (Moody, 2005). With the increasing deployment of use cases as early artifacts in software process environments, the question of how these models should be developed so as to attain high quality arises. In response, this article focuses on the use case modeling process (the act of constructing use case models) and, based on the notion of patterns (Appleton, 1997), proposes a systematic approach towards the development of use case models. The rest of the article is organized as follows. The background and related work necessary for the discussion that follows is outlined. This is followed by the presentation of a pattern-oriented use case modeling process for systematically addressing the semiotic quality of use case models in a feasible manner. Next, challenges and directions for future research are outlined, and finally, concluding remarks are given.


2009 ◽  
Vol 9 (2) ◽  
pp. 141-160 ◽  
Author(s):  
Mohamed El-Attar ◽  
James Miller
Keyword(s):  
Use Case ◽  

Author(s):  
Seunghwa Park ◽  
Inhan Kim

Today’s buildings are getting larger and more complex. As a result, the traditional method of manually checking the design of a building is no longer efficient since such a process is time-consuming and laborious. It is becoming increasingly important to establish and automate processes for checking the quality of buildings. By automatically checking whether buildings satisfy requirements, Building Information Modeling (BIM) allows for rapid decision-making and evaluation. In this context, the work presented here focuses on resolving building safety issues via a proposed BIM-based quality checking process. Through the use case studies, the efficiency and usability of the devised strategy is evaluated. This research can be beneficial in promoting the efficient use of BIM-based communication and collaboration among the project party concerned for improving safety management. In addition, the work presented here has the potential to expand research efforts in BIM-based quality checking processes.


Author(s):  
Jing Liu ◽  
Zhiming Lui ◽  
Xiaoshan Li ◽  
He Jifend ◽  
Yifeng Chen

In this chapter, we study the use of a formal object-oriented method within Relational Unified Process (RUP). Our purposes are (a) to unify different views of UML models; (b) to enhance RUP and UML with a formal method to improve the quality of software; (c) to scale up the use of the formal method with the use-case driven, iterative and incremental aspects of RUP. Our overall aim is to establish a sound foundation of RUP and UML and scale up the use of formal methods in software-intensive system development.


Author(s):  
Mark T. Dishaw ◽  
Diane M. Strong

Computer-Aided Software Engineering (CASE) tools have been advocated for improving maintainer productivity and the quality of maintained software. While there is evidence that such benefits can accrue to organizations adopting maintenance-oriented CASE tools, a key problem in achieving the desired benefits from CASE tools is low usage of these tools by programmers. The previously tested Maintenance Tool Utilization Model was a first step in investigating the factors that affect whether maintainers choose to use CASE tools during maintenance projects. We test the addition of experience with software maintenance tools and with the software maintenance task to the Maintenance Tool Utilization Model. The role of experience is important because managers can provide training to increase experience and they can ensure that project teams have some members experienced with the tools or with the task. Data for the test are collected from software maintainers working on their organization’s normal maintenance project backlog. Tool experience is significant as both a main and interaction effect, but task experience adds little to the explanatory power of the Maintenance Tool Utilization Model. These results support the value of improved CASE tool training programs.


Sign in / Sign up

Export Citation Format

Share Document