Domain analysis for business software systems

1999 ◽  
Vol 24 (7) ◽  
pp. 555-568 ◽  
Author(s):  
A.T. Berztiss
2021 ◽  
Vol 2083 (3) ◽  
pp. 032095
Author(s):  
Zhimin Ni ◽  
Fan Zhao

Abstract For the existing service-oriented software single, favors business processing, cannot guarantee the software business processing into the development of software. When the operator encounters operational problems, software failure problems and other problems related to software operation and operation, software development technicians to provide technical support to ensure the software’s business processing functions. This study will move away from dependence on other software and provide technical support to business software operators accurately and in a timely manner to effectively solve the problems that operators may encounter.


Author(s):  
Zoran Dragičević ◽  
Saša Bošnjak

The consequence of the increasing development and use of digital technologies, in every segment of society, is the emergence of digital disruption - a powerful external pressure that is changing the way business is done in all industries. Businesses are responding to digital disruption by digital transformation, which involves organizational change, redefining and aligning digital and business strategies, new business models, increased agility of software development and delivery processes, migration and/or integration of legacy systems using cloud-based platforms and ecosystems. In such a context, one of the key responsibilities of a software architect is to maintain the agility of the organization by defending the flexibility of digital strategy and IT resources so that the enterprise is able to transform and respond adequately and rapidly to the effects of digital disruption. In this regard, the question arises as to how digital disruption and business transformation affect the change in the role, importance, competence and agility of a software architect, especially in the context of the development of complex business software systems. This paper aims to present the role of an agile software architect in the era of digital disruption and transformation, by integrating the results of theoretical and empirical research. A systematic literature review identifies the role, importance, and competencies of a software architect in implementing agile architecture. In other hand, empirical research, based on a case study in a large enterprise, provides a better understanding of the importance of software architect for aligning business and digital strategy, as well as its contribution to increasing the agility of the process of developing, delivering and integrating complex business software systems.


2009 ◽  
pp. 603-619
Author(s):  
Walt Scacchi

This study examines the development of open source software supporting e-commerce (EC) or e-business (EB) capabilities. This entails a case study within a virtual organization engaged in an organizational initiative to develop, deploy, and support free/open source software systems for EC or EB services, like those supporting enterprise resource planning. The objective of this study is to identify and characterize the resource-based software product development capabilities that lie at the center of the initiative, rather than the software itself, or the effectiveness of its operation in a business enterprise. By learning what these resources are, and how they are arrayed into product development capabilities, we can provide the knowledge needed to understand what resources are required to realize the potential of free EC and EB software applications. In addition, the resource-based view draws attention to those resources and capabilities that provide potential competitive advantages and disadvantages to the organization in focus.


2019 ◽  
Vol 8 (6) ◽  
pp. 270
Author(s):  
Agustina Buccella ◽  
Alejandra Cechich ◽  
Juan Porfiri ◽  
Domenica Diniz Dos Santos

Documenting the paleontological process includes data produced by different techniques and protocols, which are used by paleontologists to prospect and eventually find a new fossil. Nowadays, together with the aforementioned data, a great amount of information is also available in terms of georeferenced systems, including contextual as well as descriptive information. However, the use of this information into a model capable of recognizing similarities and differences is still an open issue within the Natural Heritage community. From the software engineering field, software product lines are models that focus on reusing common assets, in such a way that new software developments are only concern on differentiation relying on already modeled (and implemented) systems. This synergy leads us to apply our taxonomy-oriented domain analysis for Software Product Line (SPL) development, when building systems for documenting the paleontological process. In this paper, we introduce the approach for building such software systems, and illustrate its use through a case study in North Patagonia. Findings show promissory results in terms of reuse.


Author(s):  
ARNON STURM ◽  
DOV DORI ◽  
ONN SHEHORY

Domain engineering can simplify the development of software systems in specific domains. During domain analysis, the first step of domain engineering, the domain is modeled at an abstract level, providing guidelines for modeling applications within that domain. Drawbacks of existing domain analysis approaches include poor guidelines for domain-specific application modeling, insufficient validations capability, and limited usability. In this paper we apply the Application-based Domain Modeling (ADOM) to the Object-Process Methodology (OPM). This application requires the extension of OPM with a classification mechanism. Showing that the ADOM-OPM approach overcomes limitations of existing approaches, we further verify experimentally that the level of correctness of an ADOM extended OPM model is higher than that achieved without the extension. Finally, we ensure that the proposed extension does not degrade the generic vanilla form of OPM.


Author(s):  
ZHENG-YANG LIU

This paper presents a pragmatic knowledge-based approach to evolving and reengineering legacy business software systems. We describe a CASE tool for assisting legacy system evolution by automating the tedious and knowledge-intensive conversion process and show how we developed and maintained the tool and how it is used with payoff. This work demonstrates that timely technology upgrades of legacy systems are only possible with carefully engineered knowledge-based tools. Viewing software as an artifact with structure, behavior, and function, we can represent most program conversion knowledge explicitly for function-preserving transformation in an automated conversion system. The payoff for using the knowledge-based approach to software evolution is not only in terms of valuable resources saved, but also in terms of improved quality of the upgraded software systems.


Sign in / Sign up

Export Citation Format

Share Document