A Review on Software Performance Analysis for Early Detection of Latent Faults in Design Models

Organizations and society could face major breakdown if IT strategies do not comply with performance requirements. This is more so in the era of globalization and emergence of technologies caused more issues. Software design models might have latent and potential issues that affect performance of software. Often performance is the neglected area in the industry. Identifying performance issues in the design phase can save time, money and effort. Software engineers need to know the performance requirements so as to ensure quality software to be developed. Software performance engineering a quantitative approach for building software systems that can meet performance requirements. There are many design models based on UML, Petri Nets and Product-Forms. These models can be used to derive performance models that make use of LQN, MSC, QNM and so on. The design models are to be mapped to performance models in order to predict performance of system early and render valuable feedback for improving quality of the system. Due to emerging distributed technologies such as EJB, CORBA, DCOM and SOA applications became very complex with collaboration with other software. The component based software systems, software systems that are embedded, distributed likely need more systematic performance models that can leverage the quality of such systems. Towards this end many techniques came into existence. This paper throws light into software performance analysis and its present state-of-the-art. It reviews different design models and performance models that provide valuable insights to make well informed decisions

Blockchain and sustainability disclosure: A scenario-based application for supply chains

This paper presents the implications of blockchain technologies on sustainability reporting and disclosure, and specifically proposes blockchain use-cases as a possible solution for problems experienced in the field of supply chain carbon information. This study addresses how the reliability of supply chains’ carbon-related information can become more transparent and reliable through a decentralized approach based on blockchain thinking (BT), issues that have been identified as a gap in the literature and in the practice. Scenario analysis and design science research (DSR) are used as a methodological driver to conceptualize over the nature of practical solutions using unified modeling language (UML) diagrams. The resulting use-case focuses on data retrieval in the supply chain. The paper also presents implications for the audit industry and their role in the assurance of such technological architecture implementations. The study is visionary as it offers a conceptualization based on scenario analysis. Developing a scenario enables researchers to depict a prospective situation, develop ability to solve future problems, and to back cast them in current policies, technologies, and actions

Performance by Unified Model Analysis (PUMA)

Evaluation of non-functional properties of a design (such as performance, dependability, security, etc.) can be enabled by design annotations specific to the property to be evaluated. Performance properties, for instance, can be annotated on UML designs by using the UML Profile for Schedulability, Performance and Time (SPT) . However the communication between the design description in UML and the tools used for non-functional properties evaluation requires support, particularly for performance where there are many alternative performance analysis tools that might be applied. This paper describes a tool architecture called PUMA, which provides a unified interface between different kinds of design information and different kinds of performance models, for example Markov models, stochastic Petri nets and process algebras, queues and layered queues. The paper concentrates on the creation of performance models. The unified interface of PUMA is centered on an intermediate model called Core Scenario Model (CSM), which is extracted from the annotated design model. Experience shows that CSM is also necessary for cleaning and auditing the design information, and providing default interpretations in case it is incomplete, before creating a performance model

Towards an Automated Evaluation Process for Software Architectures

Optimizing and editing enterprise software systems, after the implementation process has started, is widely recognized to be an expensive process. This has led to increasing emphasis on locating mistakes within software systems at the design stage, to help minimize development costs. There is increasing interest in the field of architecture evaluation techniques that can identify problems at the design stage, either within complete, or partially complete architectures. Most current techniques rely on manual review-based evaluation methods that require advanced skills from architects and evaluators. We are currently considering what a formal Architecture Description Language (ADL) can contribute to the process of architecture eval uation and validation. Our investigation is considering the inter-relationships between the activities performed during the architecture evaluation process, the characteristics an ADL should possess to support these activities, and the tools needed to provide convenient access to, and presentation of architectural information

Utilización de DEVS para evaluar arquitecturas de software

En el presente trabajo se propone un modelo para la simulación de productos de software en etapa temprana del desarrollo, empleando la arquitectura. El mismo se centra en la captura de la información necesaria relacionada al modelado arquitectónico y la transformación de los conceptos capturados a elementos de un modelo de simulación. Se propone el formalismo DEVS para incorporar las ventajas de la simulación en el contexto de diseño arquitectónico, ya que, a diferencia de otras herramientas de simulación, permite mantener el modelo desacoplado del simulador, y trabajar en forma modular y jerárquica. El modelo propuesto soporta la transformación de elementos arquitectónicos a elementos de un modelo de simulación, con el objetivo de obtener información cuantitativa para evaluar la calidad de un sistema en la etapa de diseño, permitiendo tomar decisiones tempranamente.Presentado en el VII Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

Utilización de DEVS para evaluar arquitecturas de software

En el presente trabajo se propone un modelo para la simulación de productos de software en etapa temprana del desarrollo, empleando la arquitectura. El mismo se centra en la captura de la información necesaria relacionada al modelado arquitectónico y la transformación de los conceptos capturados a elementos de un modelo de simulación. Se propone el formalismo DEVS para incorporar las ventajas de la simulación en el contexto de diseño arquitectónico, ya que, a diferencia de otras herramientas de simulación, permite mantener el modelo desacoplado del simulador, y trabajar en forma modular y jerárquica. El modelo propuesto soporta la transformación de elementos arquitectónicos a elementos de un modelo de simulación, con el objetivo de obtener información cuantitativa para evaluar la calidad de un sistema en la etapa de diseño, permitiendo tomar decisiones tempranamente.Presentado en el VII Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

Requirements Modelling and Design Notations for Software Product Lines

Although feature modelling is a frequently used approach to the task of modelling commonality and variability within product lines, there is currently no standard modelling notation or methodology. On the assumption that the commonality/variability model will be used as a basis for architecture design, our modelling notation allows features to be augmented with behavioural detail, captured using the UCM path notation. This gives rise to models that capture commonality and variability in behaviour as well as in product features, and are thus more valuable for downstream design activities. This paper outlines the modelling notation and describes ongoing work on the characterisation of variability points within models based on this notation, and on the relationships between model fragments and solution domain techniques such as design patterns or variability realisation techniques. It also describes preliminary work, aimed at evolving an intelligent tool that can characterise feature and behavioural model fragments and suggest design and realisation methods

Taguchi approach for performance evaluation of service-oriented software systems.

Service-oriented software systems are becoming increasingly common in the world today as big companies such as Microsoft and IBM advocate approaches focusing on assembly of system from distributed services. Although performance of such systems is a big problem, there is surprisingly an obvious lack of attention for evaluating the performance of enterprise-scale, service-oriented software systems. This thesis investigates the application of statistical tools in performance engineering domain for total quality management. In particular, the Taguchi approach is used as an efficient and systematic way to optimize designs for performance, quality, and cost. The aim is to improve the performance of software systems and to reduce application development cost by assembling services from known vendors or intranet services. The focus of this thesis is on the response time of service-oriented systems. Nevertheless, the developed methodology also applies to other performance issues, such as memory management and caching. The interaction problems of those issues are preserved for future work.Dept. of Computer Science. Paper copy at Leddy Library: Theses & Major Papers - Basement, West Bldg. / Call Number: Thesis2004 .L585. Source: Masters Abstracts International, Volume: 43-01, page: 0240. Adviser: Xiaobu Yuan. Thesis (M.Sc.)--University of Windsor (Canada), 2004