Agile Software Development

exam in lively softw be using approach is quite different from the conventionalistic interrogatory methodologies as it requires scrutiny at every phase of the exploitation and not only by the Quality Assurance team entirely by developers and business enterprise analysts as well.This is because 1) wide awake bundle system training requires sampleing throughout the lifecycle of the project and 2) Developers and Business Analysts are under the system and the business better, respectively.According to Ambler, the basic strategy of testing in energetic software tuition is testing throughout the lifecycle and therefore can be divided into spare-time activity four phases1) Initiation This is often short and includes indentifying initial acceptance tests, backing up the testing environment and identifying a testing team for the project. The derive of this test phase is to set-up testing groundwork, possibly install the tools that will be needed for testing as well.2) Construction This may comprise of both number of iterations depending on how the scope and management of the project. A significant aggregate of testing occurs during this phase. Concepts such as validating and investigative testing is apply here by the agile developers who test often, test early and usually test first. Confirmatory and fact-finding testing, as described by Ambler, are briefly defined on a lower floora. Confirmatory Testing This focuses on verifying that the system fulfills the intent of the stakeholders as described to the team to date. Two aspects of confirmatory testing, as presented by Ambler, arei. busy Acceptance Testing is a mix of conventional operating(a) testing and traditional acceptance testing because the victimization team and their stakeholders are doing it collaboratively. Developer testing is a mix of traditional unit testing and traditional class/component/service desegregation testing.ii. Developer Testing strives to verify the a pplication code and the database schema and to look for code errors, perform at least coverage if not full avenue testing, and to ensure that the system meets the current intent of its stakeholders.It is often done in a test-first manner, where a single test is written and then satisfactory production code is written to fulfill that test. (Ambler, Agile Testing Strategies)b. Investigative Testing This strives to discover problems that the development team didnt consider.Agile teams produce working software at the end of each construction iteration and hence a new version of the system should ideally be given to a separate test team that which can be assigned the refinement to explore potential scenarios that neither the development team nor business stakeholders may have considered. (Ambler, Agile Testing Strategies)3) Release At this stage, the project is straightaway to be delivered to the user and is tested from user acceptance point of have at this stage.4) Production O nce the system has been delivered, defects may arise and Agile testing ensures that these defects are fixed in a timely and prehend manner.Testing Tools It is not necessary to use a tool, solely designed for testing in an Agile development methodology. Automated testing holds a describe place in agile development because of the sheer amount of testing that is required throughout the lifecycle.Some tools that have been used by agile development and testing teams include JUnit for Unit testing, Fit and Fitnesse for acceptance testing, Autoit and Selenium for functional testing etc.Microsoft Visual Studio is the first IDE that introduced integrated unit testing tool (Ingles)Test Documents Agile software development encourage going as light as possible, hence the need for singular reference points and scheme of multiple documents and redundant information as is the norm in traditional approaches. (Ambler, Single Source Information An Agile Practice for powerful Documentation)The m ain documentation work required in Agile software development is1) Test plan to ensure comprehensive coverage of the software and take on quality (Black)2) Traceability Matrices these matrices are used in testing phases to link functionality and test cases to specific requirements.Risks involvedThere are however certain ventures involved in Agile development as suggested by some researchers. Some of these have been quoted below (Agile Software Development) Lack of structure and necessary documentation Incorporates insufficient software designRequires too much cultural change to adopt Can extend to more difficult contractual negotiations Can be very ineffective if the requirements for one discipline of code change through various iterations, the selfsame(prenominal) programming may need to be done several measure over.Whereas if a plan were there to be followed, a single area of code is expected to be written once. Impossible to develop naturalistic estimates of work effort n eeded to provide a quote, because at the initiation of the project no one knows the entire scope/requirements Drastically increases the risk of scope creep due to the lack of detailed requirements documentation Agile is feature driven, non-functional quality attributes are hard to be placed as user stories Test Standards The standards that have been introduced for agile software development include ISO/IEC 122071995 and its replacement ISO/IEC 152882002. Other standards that are also of interest to software development are ISO/IEC 159392002 (Software measurement process) and ISO/IEC 14143 (Software measurement Functional size measurement). (W.H. MORKEL THEUNISSEN) Bibliography 28 July 2008 .28 July 2008 .28 July 2008 .28 July 2008 .28 July 2008 .Agile Software Development. Wikipedia. 28 July 2008 .Agile Software Development Definition. 28 July 2008 .Ambler, Scott. Agile Testing Strategies. 28 July 2008 .. Single Source Information An Agile Practice for Effective Documentation. 28 July 2008 .Black, Rex. 28 July 2008 .Ingles, Paul. 28 July 2008 .W.H. MORKEL THEUNISSEN, DERRICK G. KOURIE AND BRUCE W. WATSON. Standards and Agile Software Development. 28 July 2008 .