Project Contexts and the Possibilities for Mixing Software Development and Systems Approaches

2012 ◽  
pp. 360-375 ◽  
Author(s):  
D. Petkov ◽  
S. Alter ◽  
J. Wing ◽  
A. Singh ◽  
O. Petkova ◽  
...  
Keyword(s):  
Software Development ◽  
System Development ◽  
Systems Development ◽  
System Of Systems ◽  
Agile Development ◽  
Systems Approaches ◽  
Stakeholder Interests ◽  
System Method ◽  
System Methodology ◽  
Single Approach

It is widely agreed that no single approach for software or systems development addresses all problems and contexts. This chapter summarizes three software development and systems approaches that are often viewed as somewhat unrelated: soft system methodology (SSM), work system method (WSM), and agile development. Next it presents a framework linking stakeholder interests and problem contexts known as the System of Systems Methodologies (SOSM) from Jackson and Keys (1984) and frameworks from Bustard and Kennan (2005) and Alter and Browne (2005) for visualizing various Information Systems (IS) contexts. It uses SOSM to position and explore alternative sets of IS project contexts described by Bustard and Kennan (2005) and Alter and Browne (2005) using their own frameworks. Comparison of these contexts in relation to SOSM leads to observations about the suitability of SSM, WSM, and agile development in different project contexts. Contributions of this research include identifying and comparing alternative contexts for software and system development and identifying possibilities for including within one project combinations of methodologies that are often viewed as unrelated.

Project Contexts and the Possibilities for Mixing Software Development and Systems Approaches

2014 ◽  
pp. 335-350
Author(s):  
D. Petkov ◽  
S. Alter ◽  
J. Wing ◽  
A. Singh ◽  
O. Petkova ◽  
...  
Keyword(s):  
Software Development ◽  
System Development ◽  
Systems Development ◽  
System Of Systems ◽  
Agile Development ◽  
Systems Approaches ◽  
Stakeholder Interests ◽  
System Method ◽  
System Methodology ◽  
Single Approach

It is widely agreed that no single approach for software or systems development addresses all problems and contexts. This chapter summarizes three software development and systems approaches that are often viewed as somewhat unrelated: soft system methodology (SSM), work system method (WSM), and agile development. Next it presents a framework linking stakeholder interests and problem contexts known as the System of Systems Methodologies (SOSM) from Jackson and Keys (1984) and frameworks from Bustard and Kennan (2005) and Alter and Browne (2005) for visualizing various Information Systems (IS) contexts. It uses SOSM to position and explore alternative sets of IS project contexts described by Bustard and Kennan (2005) and Alter and Browne (2005) using their own frameworks. Comparison of these contexts in relation to SOSM leads to observations about the suitability of SSM, WSM, and agile development in different project contexts. Contributions of this research include identifying and comparing alternative contexts for software and system development and identifying possibilities for including within one project combinations of methodologies that are often viewed as unrelated.

Agile Embedded System Development versus European Space Standards

2017 ◽  
Vol 8 (1) ◽  
pp. 1-23
Author(s):  
Ville Rantala ◽  
Kaisa Könnölä ◽  
Samuli Suomi ◽  
Minna Isomäki ◽  
Teijo Lehtonen
Keyword(s):  
Software Development ◽  
Embedded System ◽  
System Development ◽  
Agile Methods ◽  
Agile Development ◽  
Space Systems ◽  
European Cooperation ◽  
Space Projects ◽  
Mission Critical ◽  
Development Methods

Agile development methods are widely utilized in software development. There is a growing interest and effort to introduce them to other areas of technology, such as development of space systems. Space systems are typically safety- and mission-critical and therefore their development is strongly regulated and standardized. European Cooperation for Space Standardization (ECSS) has created a collection of standards which are extensively followed mainly in European space projects. In this paper, a review and discussion are presented to find out the conflicts between the agile development and the ECSS standards. The presented analysis and discussion show that the ECSS standards do not fully prevent the utilization of agile methods. However, there are aspects to be taken into account in the development methods, contracts and tailoring of standards.

A Framework for Risk Management in AI System Development Projects

2019 ◽  
pp. 1-20
Author(s):  
Kitti Photikitti ◽  
Kitikorn Dowpiset ◽  
Jirapun Daengdej
Keyword(s):  
Artificial Intelligence ◽  
Risk Management ◽  
Project Management ◽  
Software Development ◽  
System Development ◽  
Systems Development ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Very High

It has been well-known that the chance of successfully delivering a software project within an allocated time and budget is very low. Most of the researches in this area have concluded that “user's requirements” of the systems is one of the most difficult risks to deal with in this case. Interestingly, until today, regardless of amount of effort put into this area, the possibility of project failure is still very high. The issue with requirement can be significantly increased when developing an artificial intelligence (AI) system, where one would like the systems to autonomously behave. This is because we are not only dealing with user's requirements, but we must also be able to deal with “system's behavior” that, in many cases, do not even exist during software development. This chapter discusses a preliminary work on a framework for risk management for AI systems development projects. The goal of this framework is to help project management in minimizing risk that can lead AI software projects to fail due to the inability to finish the projects on time and within budget.

Back to Basics

2014 ◽  
pp. 279-292 ◽  
Author(s):  
Roy Morien
Keyword(s):  
Software Development ◽  
System Development ◽  
Agile Development ◽  
Development Projects ◽  
Structured Design ◽  
Development Methodology ◽  
Successful Approach ◽  
Development Approach ◽  
Inherent Nature ◽  
System Development Methodologies

Massive failures of software development projects have been recorded in the literature, and particularly in the popular press, over the years. Yet, rarely if ever have we seen any objective, detailed analysis of the causes of these failures. Indeed, we usually can only surmise how the projects were managed or what the development methodology or approach was. This chapter analyses some aspects of software development projects and development methodologies in terms of the success or failure potential of these methodologies. The conclusion arrived at is that the system development methodologies handed down since the late 1970s as the preferred development approach, generally known as Structured Methodologies, based on the Structured Design Life Cycle methodology (SDLC), bear the seeds of their own failure. It is asserted that they cannot succeed because of the inherent nature and assumptions embedded in those methodologies. After some analysis of these assumptions, considered to be highly flawed and unworkable, the now not so recently published Agile Development methodologies are discussed and proffered as a workable and inherently successful approach to software system development.

Integrating Human-Centered Design and the Agile Development Process for Safety and Mission Critical System Development

2017 ◽  
Vol 61 (1) ◽  
pp. 1086-1090 ◽  
Author(s):  
Angelia Sebok ◽  
Brett Walters ◽  
Christopher Plott
Keyword(s):  
Software Development ◽  
Development Process ◽  
System Development ◽  
Rapid Development ◽  
Systems Design ◽  
Agile Development ◽  
Critical Systems ◽  
Critical System ◽  
Human Centered Design ◽  
Mission Critical

The Agile software development process offers many potential benefits, including a design approach that allows frequent customer input, rapid development of functionality, and the ability to identify and resolve potential misunderstandings in design requirements. This process has generally been highly successful and offered many benefits to the software development industry. It is being adopted by an ever-increasing number of industries and used for applications beyond software development, including hard ware development, training materials, and marketing materials, to name a few examples. This paper describes a project to examine the integration of Human-Centered Design principles with the Agile process, and evaluate the appropriateness of this integrated process for safety and mission critical systems design.

scholarly journals FACTORS THAT INFLUENCE STUDENT TEAMS IN INFORMATION SYSTEM DEVELOPMENT PROJECT: STUDENT’S PERSPECTIVES

2015 ◽  
Vol 10 (2) ◽  
pp. 90
Author(s):  
Sofiyanti Indriasari ◽  
Dana Indra Sensuse
Keyword(s):  
Information System ◽  
Information Systems ◽  
Software Development ◽  
System Development ◽  
Systems Development ◽  
Development Project ◽  
Information Systems Development ◽  
Research Model ◽  
Information System Development ◽  
Student Teams

The success of information systems development activities are influenced by technology and human resources. Experience and knowledge of team members is the key to performance improvements in the software development process. So the experience and knowledge are considered to be one of the main capitals in the success of a software development team. However, what if the information system development team are students who may not have experience at all ? Is the information system developed by an un-experienced team always fail ? Therefore, it is necessary to conduct a study to identify the factors that influence the student teams in information systems development project. The study was conducted with the literature study to establish research model. Furthermore, a survey conducted by distributing questionnaires to students of information systems whom are doing an internship in developing information systems. The results of the survey were analyzed quantitatively using Partial Least Square technique to test the proposed research model. The results of this study indicate that the development of information systems conducted by a team of students is significantly influenced by the Customer Relationship and Horizontal Relationship. Capability factor have a significant effect although the effect is small on the student teams.

On the Suitability of Soft Systems Methodology and the Work System Method in Some Software Project Contexts

2013 ◽  
Vol 6 (2) ◽  
pp. 22-34 ◽  
Author(s):  
Doncho Petkov ◽  
Steven Alter ◽  
Olga Petkova ◽  
Theo Andrew
Keyword(s):  
Software Development ◽  
Soft Systems Methodology ◽  
System Of Systems ◽  
Software Project ◽  
Systems Methodology ◽  
Soft Systems ◽  
Work System ◽  
System Method ◽  
Development Processes ◽  
Development Literature

This paper proposes the use of the System of Systems Methodologies (SOSM) framework by Jackson and Keys for mapping of diverse software project contexts analyzed previously in the software development literature. In addition it presents an evaluation of the suitability of Soft Systems Methodology by Checkland and the Work System Method by Alter for those specific situations within SOSM. Thus we extend the work by Bustard and Keenan and by Alter and Browne on software project contexts that may lead to better tailoring of software development processes by mixing methods within a particular project.

Batch-based agile program management approach for coordinating IT multi-project concurrent development

2021 ◽  
pp. 1063293X2110152
Author(s):  
Qing Yang ◽  
Yingxin Bi ◽  
Qinru Wang ◽  
Tao Yao
Keyword(s):  
Software Development ◽  
New Technologies ◽  
Program Management ◽  
Agile Development ◽  
Management Approach ◽  
Development Projects ◽  
Project Development ◽  
Concurrent Development ◽  
Communication And Coordination ◽  
Development Practice

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Many firms are facing a need to use these approaches to manage entities consisting of multiple projects (i.e. programs) simultaneously and efficiently. New technologies such as big data provide a huge power and rich demand for the IT application system of the commercial bank which has the characteristics of multiple sub-projects, strong inter-project correlation, and numerous project participating teams. Hence, taking the IT program management of a bank in China as a case, we explore the methods to solve the problems in multi-project concurrent development practice through integrating the ideas of program and batch management. First, to coordinate the multi-project development process, this paper presents the batch-based agile program management approach that synthesizes concurrent engineering with agile methods. And we compare the application of batch management between software development projects and manufacturing process. Further, we analyze the concurrent multi-project development practice in the batch-based agile program management, including the overlapping between stages, individual project’s activities, and multiple projects based on common resources and environment to stimulate the knowledge transfer. Third, to facilitate the communication and coordination of batch-based program management, we present the double-level responsibility organizational structure of batch management.

The Design and Implementation of Code Generation Based on J2EE in the Development of JBPM Workflow System

2012 ◽  
Vol 263-266 ◽  
pp. 1961-1968
Author(s):  
Yong Chao Song ◽  
Bu Dan Wu ◽  
Jun Liang Chen
Keyword(s):  
Software Development ◽  
Code Generation ◽  
System Development ◽  
Source Code ◽  
Design And Implementation ◽  
Workflow System ◽  
Development Cycle ◽  
The Cost ◽  
Static Form

According to the feature of the JBPM workflow system development, the target code generated is determined by analyzing the process of JBPM workflow development and the architecture of J2EE. The code generation tool generates code by parsing the static form source code and loading the code generation template. The code generation tool greatly shortens the JBPM workflow system development cycle and reduces the cost of software development which has the good practicality and scalability.

scholarly journals Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

2015 ◽  
Vol 3 (1) ◽  
Author(s):  
Adriana Iglesias ◽  
Acellys Messino ◽  
Patty Pedroza ◽  
Ricardo Llanos
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Process Management ◽  
Model Development ◽  
Agile Development ◽  
Total Quality ◽  
Model Quality ◽  
Development And Management ◽  
Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

Sign in / Sign up

Export Citation Format

Share Document