Agile Development Methods and Component-Orientation

2011 ◽  
pp. 1-22
Author(s):  
Zoran Stojanovic ◽  
Ajantha Dahanayake ◽  
Henk Sol
Keyword(s):  
Software Development ◽  
Architectural Design ◽  
Development Process ◽  
System Modeling ◽  
Theory And Practice ◽  
Agile Methods ◽  
Agile Development ◽  
Model Driven ◽  
Agile Software ◽  
Development Methods

Agile software development methods have been proposed as the way to address the problem of delivering high-quality software on time under constantly and rapidly changing requirements in business and IT environments. An agile development process is characterized by extensive coding practice, intensive communication between stakeholders, fast iterative cycles, small and flexible teams, and minimal efforts in system modeling and architectural design. This paper presents the state-of-the-art of agile methods and analyzes them along the selected criteria that highlight different aspects of their theory and practice. Certain limitations of agile methods are identified. The chapter presents the component paradigm as a way of balancing traditional (model-driven or plan-driven) and agile development, depending on the project settings. Service-based component concepts applied at the level of modeling, architectural design and development can ensure and strengthen agile development principles and practices, and at the same time introduce necessary agility to more traditional development. By using components, the software development process can easily scale in size, robustness, and the level of details. This provides an effective balance between the requirements for agility in software development and needs for a disciplined, design-driven way of building complex software.

Reuse in Agile Development Process

2022 ◽  
pp. 1511-1534
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Development ◽  
Reusable Software ◽  
Model Driven ◽  
Development Processes ◽  
Agile Approach ◽  
Similar Solutions ◽  
Agile Software ◽  
Model Driven Approach

Reusability is a clear principle in software development. However, systematic reuse of software elements is not common in most organizations. Application programmers rarely design and create software elements for possible future reuse. In many agile software development processes, the project teams believe that the development of reusable software elements can slow down the project. This can be a misconception. This chapter examines various ways to reuse software. Three approaches to developing reusable software artifacts from 15 years of experience in the agile development process are presented. The first approach is to create generic programs or configurable frameworks that support similar solutions for a variety of use cases and environments. The reuse of patterns is the second approach presented. Another effective way is to use a model-driven approach with model patterns. These approaches help to speed deployment software. The final product is flexible and can easily be adapted to changes. This is one of the main goals of an agile approach.

An Agile Architecture for a Legacy Enterprise IT System

2016 ◽  
Vol 6 (4) ◽  
pp. 65-97 ◽  
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Architectural Design ◽  
Development Process ◽  
Agile Development ◽  
Centralized Control ◽  
Model Driven ◽  
Architectural Patterns ◽  
New Business ◽  
Service Oriented ◽  
Agile Software ◽  
New Applications

Back in the 1970s, applications mainly comprised programs written in COBOL. Many of these applications are still in operation. To meet new business demands, new applications that have to collaborate with existing programs need to be developed. It is possible to have an agile software architecture that enables easy development, extension and maintenance in COBOL. Such an architecture, and the agile development process, are presented in this article. The architectural design is a combination of the layered, component-based and service-oriented architectural patterns. It also includes features such as the centralized control of the business process, plug-and-play autonomous COBOL modules and context container for storing state data. A model-driven approach is used in the agile development process. Application models include UML class diagrams, state charts and activity diagrams from which various software artefacts and COBOL codes are generated. The architecture and development approaches were first introduced in 2004 and have been successfully applied to 13 applications since then.

Reuse in Agile Development Process

2020 ◽  
pp. 164-187
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Development ◽  
Reusable Software ◽  
Model Driven ◽  
Development Processes ◽  
Agile Approach ◽  
Similar Solutions ◽  
Agile Software ◽  
Model Driven Approach

Reusability is a clear principle in software development. However, systematic reuse of software elements is not common in most organizations. Application programmers rarely design and create software elements for possible future reuse. In many agile software development processes, the project teams believe that the development of reusable software elements can slow down the project. This can be a misconception. This chapter examines various ways to reuse software. Three approaches to developing reusable software artifacts from 15 years of experience in the agile development process are presented. The first approach is to create generic programs or configurable frameworks that support similar solutions for a variety of use cases and environments. The reuse of patterns is the second approach presented. Another effective way is to use a model-driven approach with model patterns. These approaches help to speed deployment software. The final product is flexible and can easily be adapted to changes. This is one of the main goals of an agile approach.

An Agile Architecture for a Legacy Enterprise IT System

2018 ◽  
pp. 155-190
Author(s):  
Chung-Yeung Pang
Keyword(s):  
Architectural Design ◽  
Development Process ◽  
Agile Development ◽  
Centralized Control ◽  
Model Driven ◽  
New Business ◽  
Service Oriented ◽  
Agile Software ◽  
New Applications ◽  
Model Driven Approach

Back in the 1970s, applications mainly comprised programs written in COBOL. Many of these applications are still in operation. To meet new business demands, new applications that have to collaborate with existing programs need to be developed. It is possible to have an agile software architecture that enables easy development, extension and maintenance in COBOL. Such an architecture, and the agile development process, are presented in this article. The architectural design is a combination of the layered, component-based and service-oriented architectural patterns. It also includes features such as the centralized control of the business process, plug-and-play autonomous COBOL modules and context container for storing state data. A model-driven approach is used in the agile development process. Application models include UML class diagrams, state charts and activity diagrams from which various software artefacts and COBOL codes are generated. The architecture and development approaches were first introduced in 2004 and have been successfully applied to 13 applications since then.

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
Agile Methods ◽  
Two Dimensional ◽  
Dimensional Classification ◽  
Agile Software ◽  
Structural Mechanisms ◽  
Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

An Effective Approach for Context Driven Testing in Practice — A Case Study

2020 ◽  
Vol 30 (09) ◽  
pp. 1245-1262
Author(s):  
Quyet-Thang Huynh ◽  
Le-Trinh Pham ◽  
Nhu-Hang Ha ◽  
Duc-Man Nguyen
Keyword(s):  
Software Development ◽  
Development Process ◽  
Continuous Process ◽  
Minimum Cost ◽  
Agile Development ◽  
Software Products ◽  
Engineering Company ◽  
Quality Product ◽  
Software Engineers ◽  
Agile Software

Software testing is a continuous process during the software development stages to ensure quality software products. Researchers, experts and software engineers keep going on studying new techniques, methods and approaches of testing to accommodate changes in software development because of the flexible requirement along with the changing of technology. So, developers and testers need to have effective methods, tools and approaches to create a high-quality product at an efficient cost. This paper provides an effective approach for context-driven testing (CDT) in an agile software development process. CDT is a testing approach that supports the tester to choose their testing techniques and test objectives based on specific contexts. The aim of this paper is to propose an effective approach for implementing the CDT in practice, called CDTiP. Through an analysis of two case studies using an agile development process with different contexts, we validate the effectiveness of the approach in terms of test coverage, detect errors, test effort. The empirical results show that CDTiP is suitable for the agile development process that can help the tester to detect defects faster at minimum cost. The results of this method have been applied at Enclave, an ODC Software Engineering company, on real projects.

scholarly journals IMPLEMENTATION OF REUSE IN THE AGILE SOFTWARE DEVELOPMENT PROCESS SCRUM

2017 ◽  
Vol 10 (13) ◽  
pp. 143 ◽  
Author(s):  
Jayasudha R ◽  
Viswanathan V ◽  
Shanthi P
Keyword(s):  
Software Development ◽  
Development Process ◽  
Dynamic Change ◽  
Agile Software Development ◽  
Agile Development ◽  
Software Development Process ◽  
Customer Requirements ◽  
Waterfall Model ◽  
Agile Software ◽  
First Time

The concept of reuse is applied in one of the agile development methodologies called the scrum. Sprint is a single functionality and the result at the end of the sprint functionality is derived as the shippable or bugs. This paper makes an attempt to use the concept of reuse in the agile software development to meet the dynamic change of customer requirements in banks. A banking project is created using both waterfall model and scrum model, and the knowledge gained is stored in the ontology-based repository for the first time. Again, the same project is created for different vendors using the ontology-based repository. The result shows that maximum sprint is reused and all the knowledge gained is stored in the form of ontology. This ontology helps identify the shippable component of each sprint which is a small executable functionality. This leads to less cost and time to deliver the product. The main aim is to increase the availability of the reusable artifacts, which lead to increase the reusability of the developer. The experimental results show improvements in the performance of retrieving the components for the software development.  

scholarly journals Applications supporting utilization of agile methods in software development process

2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Methods ◽  
Tabular Form ◽  
Software Development Process ◽  
Internet Applications ◽  
Technical Requirements ◽  
Development Processes ◽  
Agile Software

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

Sign in / Sign up

Export Citation Format

Share Document