Identifying the objects that constitute a software system is a critical task for any object-oriented system development and several techniques have already been introduced to tackle this problem. This paper introduces a new approach to partially solve that problem, based on the use cases that define the system's functionality. The application of the approach is exemplified with a real industrial case study, which highlights some of the approach's main characteristics for complex embedded systems development.
Software product lines and related approaches, like software factories, are starting to capture the attention of the industry practitioners. Nevertheless, their adoption outside the research community and big companies is still very restricted. We believe that model-driven approaches, like OMG's MDA, with proper tool support, can bring the advantages of product lines to a broader audience. For this to become a reality, model-driven methods should integrate requirements models into the software development process. In this paper, we discuss the semantics of use case relationships and their formalization using activity diagrams to support variability specification. Particularly, we propose an extension to the «extend» relationship that supports the adoption of UML 2.0 use case diagrams into modeldriven methods. Our proposal results from our work with 4SRS (4 Step Rule Set), a model-driven method in which use cases are the central model for requirements specification and model transformation.
The main aim of this paper is to present how to refine software logical architectures by application of a recursive model-based transformation approach called 4SRS (four step rule set). It is essentially based on the mapping of UML use case diagrams into UML object diagrams. The technique is based on a sequence of steps that are inscribed in a tabular representation that is used to derive the software architecture for a focused part of the global system.
The main purpose of this paper is to present h o w the Unied Modeling Language (UML) can be used for modeling industrial embedded systems. By using a car radios production line as a running example, the paper demonstrates the modeling process that can be follow edduring the analysis phase of complex control applications. In order to guarantee the con tinuity mapping of the models, the authors propose some guidelines to transform the use case diagrams into a single object diagram, which is one of the main diagrams for the next development phases.
Abstract-Developing quality software product is a challenging activity and yet necessary asset for most software companies especially small and medium size companies. For a Software process improvement (SPI) activity to be effective in such companies, the day to day product-focused activities needs to align with SPI activity.Different process maturity models have been developed, among them the Capability Maturity Model Integration (CMMI) is the most widely used process maturity framework. However, it is considered difficult to implement for small and medium companies due to various reasons related with its difficulty and financial requirement. On the other hand, the recent software development approach is being directed towards application of agile software development methodologies. But some difficulties have also been reported regarding agile methods limitations of long term and continues guide to process improvement.Researches findings and experience reports demonstrated that, combination of agile methods and CMMI has advantages where most of which can be considered as a solution to problems associated with implementing process maturity activities in immature companies.Index Terms-Integrated framework, CMMI and agile methods, institutionalization. I. INTRODUCTIONThe design and development of software is still the most challenging and complex process; where most products suffer from un-attained requirements and fail to maintain the expected quality. Many problems are attributed to failure of software products. Regardless of how it is explained, the set of problems that are encountered in the development of computer software is not limited to software that "doesn't function properly". The affliction encompasses problems associated with how we develop software, how we support a growing volume of existing software, and how we can expect to keep pace with a growing demand for more software [1].The quality of a software product is considered to be the output of the software process used in the production process. Different software organizations follow varieties of process Manuscript received June 29, 2014; revised November 4, 2014. Tatek Engdashet is with Addis Ababa University Addis Ababa, Ethiopia (e-mail: mail4te@gmail.com).Ricardo J. Machado is with the Department of Information Systems University of Minho Guimarã es, Portugal (e-mail: rmac@dsi.uminho.pt).Dida Midekso is with the Department of Computer Science Addis Ababa University Addis Ababa, Ethiopia (e-mail: dida.midekso@aau.edu.et). maturity models to improve the software process to maintain and upgrade the quality of software developed Continuous improvement of the software process is considered as a means to guide software developing companies towards standard practices to have a software process with better capability. A standard capability model is created, as a result significant improvement on the quality of the software products, through the introduction of new techniques and new tools, is achieved [2].A number of software process maturity models ...
Business process modeling and management approaches are increasingly used and disclosed between organizations as a means of optimizing and streamlining the business activities. A business process model identifies the activities, resources and data involved in the creation of a product or service, having lots of useful information that can be used to create a data model for the supporting software system. A data model is one of the most important models used in software development. Usually an organization deals with several business processes. As a consequence a software product does not usually support only one business process, but rather a set of business processes. This paper proposes an approach to generate a data model, based on a set of interrelated business processes, modeled in BPMN language. The approach allows aggregating in one data model all the information about persistent data that can be extracted from the set of business process models serving as a basis for the software development.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.