Agile Software Development

“…Experienced project teams adopt waterfall model while their clients know accurately what they desire and nothing changes other than fixing problems. On the other hand, when project scope is not fixed and the feedback requires from the client to proceed on, the next steps are the selection of an agile model that can provide the best results (Stober & Hansmann, 2010). Therefore, the project manager needs to have a clear idea about the differences between project lifecycle and system development lifecycle.…”

Section: Introductionmentioning

confidence: 99%

IT Project Development using Capability Maturity Model

Rusu

Kabir

2016

Information Resources Management Journal

View full text Add to dashboard Cite

In many research studies on IT project development process, the authors have noticed that different frameworks are used for this purpose. In fact, many companies choose specific frameworks to run their IT projects based on project type and face dissimilar problems during the execution. In this research the authors are presenting a framework for IT project development using Capability Maturity Model. The framework has been developed to improve the IT project development in a large company because of the lower rate of successfully IT projects in that company. To develop the framework, they have used design science research and evaluated this framework with the project managers from that large company. The result of this research is a framework for IT projects development that is based on generic Capability Maturity Model and is adapted to the specific needs of an IT project development environment. Moreover, the framework identifies for each key process area of IT project development, the goals and activities to be performed.

show abstract

“…Modern practices of software development encourage extensive code testing during development stages (Bagge et al, 2010). Additionally, Beck (2003) stated that automatized testing for Test-Driven Development (TDD) is a key factor as it influences the success and improvement of productivity during software design and development (Stober and Hansmann, 2010;Hunt et al, 2014). However, automatized testing often depends on the testability of Systems Under Test (SUT) (Blackburn et al, 2004).…”

Section: Introductionmentioning

confidence: 99%

Fixture Setup through Object Notation for Implicit Test Fixtures

Longo¹,

Wilges²,

Vilain³

et al. 2015

Journal of Computer Science

View full text Add to dashboard Cite

This paper presents an approach to the development of fixture setup code through an objects notation that is applied on implicit test fixtures. This approach is integrated with a management mechanism to call the fixture setup code from the JUnit test framework. The objective of this work is to enable the reuse of fixtures across multiple test classes avoiding the management and the creation of fixtures within the test itself. The evaluation of this proposal was performed during test-driven development of a Web-based system. Results present approximately 190 fixture setups with a reutilization average of about 13 times, observed in an analysis with 2200 h of development. Initial results show the growing reutilization of fixture setups during test development, with significant test code volume reduction.

show abstract

Agile Software Development

Cited by 26 publications

References 0 publications

Lean Software Management: BBC Worldwide Case Study

Lean Software Management: BBC Worldwide Case Study

IT Project Development using Capability Maturity Model

Fixture Setup through Object Notation for Implicit Test Fixtures

Contact Info

Product

Resources

About