Case Study: Applying an Agile Development Methodology to XML Schema Construction

2016 ◽  
Author(s):  
Dianne Kennedy
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Xml Schema ◽  
Third Party ◽  
Agile Development ◽  
Print Quality ◽  
Brand Quality ◽  
Measurement Tools ◽  
Agile Software

To assure brand integrity, brands such as Coca-Cola and Proctor & Gamble, assisted by third party brand quality experts, receive, score and track the quality of their print suppliers over time. Currently this is difficult and expensive because printers use many different measurement tools and report print quality using a wide variety of proprietary formats that cannot be directly utilized by brand scoring and tracking systems. In 2015 Idealliance members launched an effort to develop a standard XML-based print quality exchange message. This specification, known as Print Quality eXchange (PQX), was developed by applying agile software development techniques to the construction of the PQX XSD. This case study highlights how agile software development principles can be applied to the construction of an XML schema.

Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

scholarly journals Agile Software Development

2010 ◽  
Vol 1 (3) ◽  
pp. 71-85 ◽  
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Development Effort ◽  
Implementation Team ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

scholarly journals New Approach on the Agile Cycles Containment Effectiveness Metrics in Automotive SW Development

ACTA IMEKO ◽  
2019 ◽  
Vol 7 (4) ◽  
pp. 3
Author(s):  
Ionut Andrei Sandu ◽  
Alexandru Salceanu
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Extended Version ◽  
New Approach ◽  
Development Team ◽  
Real Application ◽  
Original Contribution ◽  
Agile Software

<p class="Abstract"><span lang="EN-US">In an ideal Agile Development Team, defects should not exist. But in reality and especially in Automotive Agile Software Development, we need to have a mechanism for defects handling and tracking to closure. In this paper we describe the benefits and principles for measuring the defects handling metrics in automotive programs and organizations which adopted Agile SW Development. We are presenting the Iteration Containment Effectiveness, Program Increment Containment Effectiveness and Defect Debt Trend metrics. The acquired advantages are demonstrated by a detailed example of real application on how to measure the classical Phase Containment Effectiveness metric on Iteration (Sprint) and Program Increment (Scum of Scrums / Scaled Agile) Level. This paper is an extended version of the original contribution to the IMEKO TC 4 2017 symposium in Iasi, Romania.</span></p>

Agile Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Fixed Priced Projects in Agile

2016 ◽  
pp. 222-236
Author(s):  
Anuradha Chaminda Gajanayaka
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Model ◽  
Software Development Model ◽  
Responding To Change ◽  
The One ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Agile software development has established as a reliable alternative to waterfall software development model. Unfortunately the use of agile software development has been limited to time based contracts and not for time limited contracts. The main reason for this limitation is the “Agile manifesto” itself. The forth value of the manifesto states that agile believers find more value in “Responding to change over following a plan”. This is the one of the main reasons why agile software development methods are not preferred for a fixed priced contract or time limited contract. The following case study provides an example on how the agile software development can be used for fixed priced software development contracts even when operating in offshore context. The agile software development concepts were used throughout to plan, execute, monitor, report, etc. for the project documented in this case study.

Agile Software Development Quality Assurance

2009 ◽  
pp. 2680-2699
Author(s):  
James F. Kile ◽  
Maheshwar R. Inampudi
Keyword(s):  
Software Development ◽  
High Performance ◽  
General Rule ◽  
Adaptive Methods ◽  
Agile Software Development ◽  
Agile Development ◽  
Performance Requirements ◽  
Small Project ◽  
Software Development Methodologies ◽  
Agile Software

Of great interest to software development professionals is whether the adaptive methods found in agile methodologies can be successfully implemented in a highly disciplined environment and still provide the benefits accorded to fully agile projects. As a general rule, agile software development methodologies have typically been applied to non-critical projects using relatively small project teams where there are vague requirements, a high degree of anticipated change, and no significant availability or performance requirements (Boehm & Turner, 2004). Using agile methods in their pure form for projects requiring either high availability, high performance, or both is considered too risky by many practitioners (Boehm et al., 2004; Paulk, 2001). When one investigates the various agile practices, however, one gets the impression that each may still have value when separated from the whole. This chapter discusses how one team was able to successfully drive software development quality improvements and reduce overall cycle time through the introduction of several individual agile development techniques. Through the use of a common-sense approach to software development, it is shown that the incorporation of individual agile techniques does not have to entail additional risk for projects having higher availability, performance, and quality requirements.

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.  

Sign in / Sign up

Export Citation Format

Share Document