scholarly journals Conceptual Integrity of Software Systems: Architecture, Abstraction and Algebra

2017 ◽  
Author(s):  
Iaakov Exman
Keyword(s):  
Software Systems ◽  
Systems Architecture ◽  
And Algebra ◽  
Conceptual Integrity

scholarly journals Software System Package Dependencies and Visualization of Internal Structure

2018 ◽  
Vol 7 (1) ◽  
pp. 13
Author(s):  
Ahmad Abdul Qadir Alrababah
Keyword(s):  
Reverse Engineering ◽  
Error Correction ◽  
Internal Structure ◽  
Software Systems ◽  
Software System ◽  
Systems Architecture ◽  
Software Packages

<span>This manuscript discusses the visualization methods of software systems architecture with composition of reverse engineering tools and restoration of software systems architecture. The visualization methods and analysis of dependencies in software packages are written in Java</span><em><span lang="AR-SA" dir="RTL">.</span></em><span> To use this performance graph</span><em></em><span>it needs to describe the relationships between classes inside the analyzed packages and between classes of different packages. In the manuscript also described the possibility of tools to provide the infrastructure for subsequent detection and error correction design in software systems and its refactoring.</span>

scholarly journals Quality-Aware Model-Driven Service Engineering

2009 ◽  
pp. 400-430
Author(s):  
Claus Pahl ◽  
Boškovic Marko ◽  
Ronan Barrett ◽  
Wilhelm Hasselbring
Keyword(s):  
Service Oriented Architecture ◽  
Software Systems ◽  
Systems Architecture ◽  
Service Engineering ◽  
Model Driven ◽  
Recent Approach ◽  
Architectural Patterns ◽  
Quality Aspects ◽  
Empirical Performance ◽  
Service Oriented

Service engineering and service-oriented architecture as an integration and platform technology is a recent approach to software systems integration. Quality aspects ranging from interoperability to maintainability to performance are of central importance for the integration of heterogeneous, distributed service-based systems. Architecture models can substantially influence quality attributes of the implemented software systems. Besides the benefits of explicit architectures on maintainability and reuse, architectural constraints such as styles, reference architectures and architectural patterns can influence observable software properties such as performance. Empirical performance evaluation is a process of measuring and evaluating the performance of implemented software. We present an approach for addressing the quality of services and service-based systems at the model-level in the context of modeldriven service engineering. The focus on architecture-level models is a consequence of the black-box character of services.

Motives for Feral Systems in Denmark

2016 ◽  
pp. 193-222
Author(s):  
Torben Tambo ◽  
Martin Olsen ◽  
Lars Bækgaard
Keyword(s):  
Case Studies ◽  
Business Models ◽  
Business Processes ◽  
Low Cost ◽  
Software Systems ◽  
Work Processes ◽  
Systems Architecture ◽  
General Acceptance ◽  
Process Support ◽  
Information Systems Architecture

Feral systems have largely been regarded as the users' response to discrepancies between official IT software systems and actual business processes. Inadequacies, discrepancies, and absence of systems support to work processes might lead to users initiating systems development themselves: systems involving any combination of software and manual processes. Feral systems are unofficial and exhibit a conflict between formal and actual operational implementation. In this chapter, the use and implementation of feral systems in Denmark are analysed and discussed. It is found interesting to aim for an understanding of feral systems in a small, relatively agile economy with traditionally positive to rapid adoption of information technology in enterprises. The method being used is qualitative case studies in selected companies representing various complexities of their respective business models and industries. The case studies address both issues of organisational and technological nature of the feral systems typically with an offset in the companies' overall information systems architecture. Among findings are (1) feral systems as a known choice when reflecting business processes with open and non-routinised character, (2) a general acceptance not related to the size or industry, (3) feral systems have received attention as implementations of innovation, (4) feral systems start as opposed to formal and official systems, but during their lifetime they can drift towards a more official status, and (5) feral systems are accepted as low-cost solutions to fill gaps in business process support where ERP systems come short.

Motives for Feral Systems in Denmark

2014 ◽  
pp. 129-160
Author(s):  
Torben Tambo ◽  
Martin Olsen ◽  
Lars Bækgaard
Keyword(s):  
Case Studies ◽  
Business Models ◽  
Business Processes ◽  
Low Cost ◽  
Software Systems ◽  
Work Processes ◽  
Systems Architecture ◽  
General Acceptance ◽  
Process Support ◽  
Information Systems Architecture

Feral systems have largely been regarded as the users’ response to discrepancies between official IT software systems and actual business processes. Inadequacies, discrepancies, and absence of systems support to work processes might lead to users initiating systems development themselves: systems involving any combination of software and manual processes. Feral systems are unofficial and exhibit a conflict between formal and actual operational implementation. In this chapter, the use and implementation of feral systems in Denmark are analysed and discussed. It is found interesting to aim for an understanding of feral systems in a small, relatively agile economy with traditionally positive to rapid adoption of information technology in enterprises. The method being used is qualitative case studies in selected companies representing various complexities of their respective business models and industries. The case studies address both issues of organisational and technological nature of the feral systems typically with an offset in the companies’ overall information systems architecture. Among findings are (1) feral systems as a known choice when reflecting business processes with open and non-routinised character, (2) a general acceptance not related to the size or industry, (3) feral systems have received attention as implementations of innovation, (4) feral systems start as opposed to formal and official systems, but during their lifetime they can drift towards a more official status, and (5) feral systems are accepted as low-cost solutions to fill gaps in business process support where ERP systems come short.

Sign in / Sign up

Export Citation Format

Share Document