The Tetrad Influences

2014 ◽  
Vol 5 (2) ◽  
pp. 30-42
Author(s):  
Usman Khan Durrani ◽  
Zijad Pita ◽  
Joan Richardson

The Software Configuration Management (SCM) process with its origin in hardware development was first applied to the software development environment in the 1950's. Since then many IT dynamics associated with this process have evolved, such as, software development methodologies, software process improvement standards, computing environments, and organizational needs. Through the observation of these IT dynamics, which the researchers called “the tetrad influences”, it is now apparent that there is a need to look into new adaptable approaches to apply the SCM process for traceability and governance. In this paper, we will present a conceptual framework highlighting the tetrad influences on the SCM process and will propose a Software configuration Adaptable Lean Agile Management “SALAM” model as a solution. We contribute a case study of a large Australian IT project where hybrid project teams delivered a consolidated software product in a hybrid cloud computing environment.

1999 ◽  
Vol 28 (540) ◽  
Author(s):  
Henrik Bærbak Christensen

The Ragnarok project is an experimental computer science project within the field of software development environments. Taking current problems in software engineering as starting point, a small set of hypotheses are proposed, outlining plausible solutions for problems concerning the management of the development process and its associated data, and outlining how these solutions can be supported directly in a development environment. These hypotheses are all deeply rooted in the viewpoint that the logical software architecture forms a natural and powerful framework for handling essential aspects of the development process. <br /> <br /> The main contributions presented in the thesis have evolved from work with two of the hypotheses: These address the problems of management of evolution, and overview, comprehension and navigation respectively. <br /> <br /> The first main contribution is the Architectural Software Configuration Management Model: A software configuration management model where the abstractions and hierarchy of the logical aspect of software architecture forms the basis for version control and configuration management. The second main contribution is the Geographic Space Architecture Visualisation Model: A visualisation model where entities in a software architecture are organised geographically in a two-dimensional plane, their visual appearance determined by processing a subset of the data in the entities, and interaction with the project's underlying data performed by direct manipulation of the landscape entities. <br /> <br /> A major effort has been invested in the design, development and deployment of a prototype software development environment, Ragnarok, that implements the core of these models. The Ragnarok prototype has been used in three, small- to medium-sized, real development projects for nearly three years. <br /> <br /> The main results from the three case studies are the following: The architectural software configuration management model is a natural and viable model for configuration management, at least for small- to medium-sized systems. The model's main assets are that it minimises the gap between the concepts used in the development domain and configuration domain; and its emphasis on bound configurations ensures traceability and reproducibility of configurations and architectural changes. The geographic space architecture visualisation model is a viable model for visualising the logical aspect of an architecture. The model's main assets are enhanced navigational abilities as the focus is shifted from name-based to location-based search which allows humans' fine spatial memory to be exploited; and strengthened overview as the architecture is visible and readily accessible in a compact form.


2016 ◽  
Vol 24 (3) ◽  
pp. 45-70 ◽  
Author(s):  
Delroy Chevers ◽  
Annette M. Mills ◽  
Evan Duggan ◽  
Stanford Moore

For software development firms to be competitive they must assure the quality of the software product. This has led many firms to adopt software process improvement (SPI) programs such as the capability maturity model integration (CMMI). However, for small software firms, especially those in developing countries with limited resources, these programs are often too cumbersome and costly to implement. To address this issue, this paper proposes a simplified SPI model for small firms (SPM-S) comprised of 10 key software development practices; with fewer practices, the proposed model should be more accessible and less costly to implement. Using data collected in four developing countries in the English-speaking Caribbean from 112 developer/user dyads, the model is evaluated with respect to its impact on software quality. The findings show that the software development process coupled with supporting technology (e.g. project management tools) significantly impact software product quality. Implications for software process improvement in small firms and future research are discussed.


2008 ◽  
Vol 16 (3) ◽  
pp. 157 ◽  
Author(s):  
Sergio De Cesare ◽  
Chaitali Patel ◽  
Nicola Iacovelli ◽  
Antonio Merico ◽  
Mark Lycett

Author(s):  
Muhammad Aminu Umar ◽  
Sheidu Salami Tenuche ◽  
Sahabi Ali Yusuf ◽  
Aminu Onimisi Abdulsalami ◽  
Aliyu Muhammad Kufena

As the popularity and acceptance of agile software development methodologies increases, the need to integrate usability engineering in the design and development processes is imperative. While, agile the focus is on technical and functional requirements not on end-user interaction, usability is usually only dealt with on the side. Combining this two in practice will go a long way in development of better product. Since the success and acceptance of software product depends not only on the technologies used but how well it integrates user-oriented methods. Therefore, this chapter puts together works on how usability engineering has been integrated with agile processes.


2020 ◽  
Vol 28 (4) ◽  
pp. 265-279 ◽  
Author(s):  
Daniel Hinterreiter ◽  
Lukas Linsbauer ◽  
Kevin Feichtinger ◽  
Herbert Prähofer ◽  
Paul Grünbacher

In the domain of industrial automation companies nowadays need to serve a mass market while at the same time customers demand highly customized solutions. To tackle this problem, companies frequently define software product lines (SPLs), which allow to automatically derive and further customize individual solutions based on a common platform. SPLs rely on defining common and variable platform features together with mappings, which define how the features are realized in implementation artifacts. In concurrent engineering such a feature-oriented process is challenged by the evolution of features, the complexity of feature-to-artifact mappings, and the diversity of the implementation artifacts. To address these challenges this paper introduces an approach supporting feature-oriented development and evolution in industrial SPLs. We outline the key elements and operations of our approach, including an implementation in a development environment. We report results of evaluating our approach regarding functional correctness, usefulness, and scalability based on a case study of a Pick-and-Place Unit (PPU) and an industrial case system.


2017 ◽  
Vol 19 (1) ◽  
Author(s):  
Mzwandile M. Shongwe

Background: Software organisations have been experiencing software development failures since the beginning of software development. Globally, latest Standish Group CHAOS reports indicate that only 29% of projects are successful. In South Africa (SA), the ITWeb report (2013) indicates that only 11% of all projects are successful. Intervention strategies such as software process improvement (SPI) frameworks and new software development methodologies such as agile methods have been introduced to address this issue. These intervention strategies do not seem to be effective because software development projects continue to fail. To address this issue, software organisations are turning to knowledge management (KM). This is because software development is a knowledge-intensive task.Objectives: The study aimed to investigate KM practices in small, medium and micro (SMMEs) software development organisations in SA and to determine if KM has benefited the organisations.Method: Fifteen software development project managers from 15 software development SMMEs were interviewed. Content analysis was used to analyse the data.Results: The study found six KM practices in the organisations: knowledge acquisition, creation, storage, sharing, organisation and application. The study found that KM has benefited organisations by making them effective, efficient and productive.Conclusions: The study concluded that software development organisation have adopted KM, although informally, and that KM practices have improved organisational routines and processes.


Sign in / Sign up

Export Citation Format

Share Document