Search results

Security is a vital requirement for software systems. Misuse case models allow system designers to inject security considerations within their designs early in the development cycle rather than patching an end system with security mechanisms after it was developed. The notation and syntactical rules of misuse case models are relatively simple. However, misuse case modeling practitioners are highly vulnerable to modeling pitfalls, creating defective models that can have catastrophic effects downstream in the development cycle. This paper seeks to present a framework that unitizes antipatterns to help remedy defective misuse case models and poor modeling practices.

A repository of antipatterns was constructed and formatted to be machine‐readable whenever possible so that it can be utilized by the proposed framework. The feasibility of the proposed approach was then demonstrated using a real‐world misuse case model of an online bookstore system.

The results indicate that the overall quality and clarity of the bookstore misuse case model is improved by applying the proposed technique and framework.

This research work presents a series of domain‐independent antipatterns. Users of this framework may be interested to develop domain‐dependent antipatterns to better suit their modeling and development needs.

The proposed approach will help misuse case modelers, especially novice ones, to improve the quality of their current models as well as future models.

Game Theory has become an integral part of the business school curriculum, but the popular business press ignores it. Here's a crash course.

Public acts of self-criticism in Eastern Europe – a genre cultivated and extorted by the communist parties – did not disappear with the end of communism. In the young democracies of the region self-criticism has become an attempt to diagnose society’s ‘backward’ character and to develop ‘self-correction’ scenarios in order to participate in the Western modernising discourse. On the one hand, conservative and right-wing elites suppose that public acts of self-criticism (performed by politicians, artists or scholars) can endow the vetting procedures of the ancien régime with a sense of social catharsis and retroactive justice. On the other hand, liberal and left-wing intellectuals subject themselves to collective self-reckoning, not only with their choices made in the transition period, but also with the memory of WWII, in order to shape a civil society free of anti-Semitism and intolerance. An analysis based on the discourse-historical approach in critical discourse analysis, Reinhart Koselleck’s historical semantics and Michel Foucault’s notion of discourse, and carried out on the text corpus of selected acts of self-criticism in Poland, aims to diagnose the role these acts had in shaping public discourse on the troublesome past.

Purpose: Green computing is a way of using the computer resource in an eco-friendly while maintaining and decreasing the harmful environmental impact. Minimising toxic materials and reducing energy usage can also be used to recycle the product.

Need for the Study: The motivation of the study is to use green computing resources to decrease carbon emissions and their adverse effect on the environment.

Methodology: The study uses a qualitative method of collecting resources and data to address the opportunities, challenges, and future trends in green computing for Sustainable Future Technologies. The study focusses on multiple kinds of cloud computing services collected and executed into single remote servers. The service demand processor offers these services to the client per their needs. The simultaneous requests to access the cloud services, processing and expertly managing these requests by the processors are discussed and analysed.

Findings: The findings suggest that green computing is an upcoming and most promising area. The number of resources employed for green computing can be beneficial for lowering E-waste so that computing can be environmentally friendly and self-sustainable.

Practical Implications: Green computing applies across all industries and service sectors like healthcare, entertainment, tourism, and education. The convergence of technologies like Cloud Computing, AI, and Internet of Things (IoT) is greatly impacting Green Supply Chain Management (GSCM) market.

Many REpresentational State Transfer (RESTful) Web services suffered from anti-patterns problem, which may diminish the sustainability of the services. The anti-patterns problem could happen in the code of the programme or the uniform resource identifiers (URIs) of RESTful Web services. This study aims to address the problem by proposing a technique and an algorithm for detecting anti-patterns in RESTful Web services. Specifically, the technique is designed based on URIs parsing process.

The study was conducted following the design science research process, which has six activities, namely, identifying problems, identifying solutions, design the solutions, demonstrate the solution, evaluation and communicate the solution. The proposed technique was embedded in an algorithm and evaluated in four phases covering the process of extracting the URIs, implementing the anti-pattern detection algorithm, detecting the anti-patterns and validating the results.

The results of the study suggested an acceptable level of accuracy for the anti-patterns detection with 82.30% of precision, 87.86% of recall and 84.93% of F-measure.

The technique and the algorithm can be used by developers of RESTful Web services to detect possible anti-pattern occurrences in the service-based systems.

The technique is personalised to detect amorphous URI and ambiguous name anti-patterns in which it scans the Web service URIs using specified rules and compares them with pre-determined syntax and corpus.

The software development team reviews the testing phase to assess if the reliability growth of software is as per plan and requirement and gives suggestions for improvement. The objective of this study is to determine the optimal review time such that there is enough time to make judgments about changes required before the scheduled release.

Testing utilizes majority of time and resources, assures reliability and plays a critical role in release and warranty decision-making reviews necessary. A very early review during testing may not give useful information for analyzing or improving project performance, and a very late review may delay product delivery and lead to opportunity loss for developers. Therefore, it is assumed that the optimal time for review is in the later stage of testing when the fault removal rate starts to decline. The expression for this time point is determined using the S-curve 2-D software reliability growth model (SRGM).

The methodology has been illustrated using the real-life fault datasets of Tandem computers and radar systems resulting in optimal review time of 14 weeks and 26 months, respectively, which is neither very early in testing nor very near to the scheduled release. The developer can make changes (more resources or postpone release) to expedite the process.

Most of the literature studies focus on determination of optimal testing or release time to achieve considerable reliability within the budget, but in this study, the authors determine the optimal review time during testing using SRGM to ensure the considerable reliability at release.

Recent advancements in Artificial Intelligence (AI) and, at its core, Machine Learning (ML) offer opportunities for organizations to develop new or enhance existing capabilities. Despite the endless possibilities, organizations face operational challenges in harvesting the value of ML-based capabilities (MLbC), and current research has yet to explicate these challenges and theorize their remedies. To bridge the gap, this study explored the current practices to propose a systematic way of orchestrating MLbC development, which is an extension of ongoing digitalization of organizations.

Data were collected from Finland's Artificial Intelligence Accelerator (FAIA) and complemented by follow-up interviews with experts outside FAIA in Europe, China and the United States over four years. Data were analyzed through open coding, thematic analysis and cross-comparison to develop a comprehensive understanding of the MLbC development process.

The analysis identified the main components of MLbC development, its three phases (development, release and operation) and two major MLbC development challenges: Temporal Complexity and Context Sensitivity. The study then introduced Fostering Temporal Congruence and Cultivating Organizational Meta-learning as strategic practices addressing these challenges.

This study offers a better theoretical explanation for the MLbC development process beyond MLOps (Machine Learning Operations) and its hindrances. It also proposes a practical way to align ML-based applications with business needs while accounting for their structural limitations. Beyond the MLbC context, this study offers a strategic framework that can be adapted for different cases of digital transformation that include automation and augmentation of work.

The literature on software project management is extended into the broader domain of large‐scale IS management by studying enterprise‐wide system upgrade projects. In particular; examines the role that the intervention of project management practices (formal project methodologies and outsourcing) play in large and/or complex IS projects, which result in good project performance.

A survey instrument was completed by 449 information systems managers about a specific upgrade project. The primary analytical approach used was structural equation modeling (SEM).

It was found that neither project complexity nor project size are good indicators of meeting a project's target date. Large projects that adopted formal project management practices were more probable to meet the project target date. Projects with a high degree of complexity which involved outsourcing and adopted formal project management practices, were more likely to meet the project target date.

Clearly, the message to managers of IS projects is to establish a project methodology, especially in large, enterprise‐wide projects, and when some degree of outsourcing is required.

Future research should consider additional measures of performance such as cost, end‐user satisfaction and business value.

Much had been written in the literature about how large, complex IT projects have high failure rates. Our study provides conclusive evidence that, the greater the degree of methodology implementation, the greater the chance for meeting the project's target date. Prior to this research, this had not been explicitly shown in the research literature.

The purpose of this paper is that of linking security requirements for web services with security patterns, both at the architectural and the design level, obtaining in a systematic way a web services security software architecture that contains a set of security patterns, thus ensuring that the security requirements of the internet‐based application that have been elicited are fulfilled. Additionally, the security patterns are linked with the most appropriate standards for their implementation.

To develop secure WS‐based applications, one must know the main security requirements specified that applications have to fulfil and find appropriate security patterns that assure, through combination or relationships between them, the fulfilment of the implicated security requirements. That is why a possible link or connection between requirements and patterns will have to be found, attempting to select for a determined security requirement the best security patterns that solve this requirement, thus guaranteeing the security properties for internet‐based applications.

Using security patterns, that drive and guide one towards a secure development as well as towards security software architecture, one can be sure that this design based on these patterns fulfils and guarantees the most important security requirements of the internet‐based applications through the design and implementation of security solutions that provide reliable security services.

Security architecture for internet‐based applications and web services can be designed considering the security requirement types that it must fulfil and using the most appropriate security patterns.

This paper proposes a relationship between security requirements that can be specified for internet‐based applications and the possible security patterns that can be used in the design and implementation of the secure system based on the internet, guaranteeing that these security requirements are fulfilled.

Any XML schema definition can be organized according to one of the following design styles: “Russian Doll”, “Salami Slice”, “Venetian Blind” and “Garden of Eden” (with the additional “Bologna” style actually representing absence of style). Conversion from a design style to another can facilitate the reuse and exchange of schema specifications encoded using the XML schema language. Without any computer-aided engineering support, style conversions must be performed very carefully as they are difficult and error-prone operations. The purpose of this paper is to efficiently deal with such XML schema design style conversions.

A general approach, named StyleVolution, for automatic management of XML schema design style conversions, is proposed. StyleVolution is equipped with a suite of seven procedures: four for converting a valid XML schema from any other design style to the “Garden of Eden” style, which has been chosen as a normalized XML schema format, and three for converting from the “Garden of Eden” style to any of the other desired design styles.

Procedures, algorithms and methods for XML schema design style conversions are presented. The feasibility of the approach has been shown through the encoding (using the XQuery language) and the testing (with the Altova XMLSpy 2019 tool) of a suite of seven ready-to-use procedures. Moreover, four test procedures are provided for checking the conformance of a given input XML schema to a schema design style.

The proposed approach implements a new technique for efficiently managing XML schema design style conversions, which can be used to make any given XML schema file to conform to a desired design style.