Methodology Analysis Template
Shared by: krj18645
Methodology Analysis Template Methodology Analysis Template AGILE UP/RUP JAD TDD What are the Agile UP/RUP is Joint Testing first by significant methods for a full Application writing test scripts features of software structured Development and then writing this developme (many well (JAD) is a code to meet approach? nt are fast defined process where these tests. This in phases), groups or provides a rapid developme documentat workshops feedback of nt, slim in ion heavy, consisting of iterations and life cycle use case customers, produces the phases, driven users, and iterations correctly and able to method for developers and much faster accept software define and as a result. With change developme record the TDD you write the throughput nt. business tests, run the it’s SDLC. requirements of tests, refactor the Agile relies a system. It is code, run the on trust, also used in the tests again etc. communicat other SDLC The objective is to ion, and phases as well mold the code to collaboratio but the fit the test. n requirement gathering is superior in this approach. What The most Again this With Waterfall One deficiency deficiency or significant model of the addressed in the deficiencies in deficiency in software requirements waterfall method the waterfall the waterfall development are already well with regards to approach method that accepts known. With TDD is does this agile methods change. As the RAD, although documentation. approach correct is the SDLC used in all With TDD the respond to inability to progresses phases of the tests themselves (what is wrong accept change through the SDLC, the become the with during the stages change requirements documentation; waterfall)? SDLC. The is accounted for are derived i.e. acceptance waterfall steps through from working in tests become the are to linear. iterations and groups or requirements of increments. workshops with the project. the user and customer, thereby solidifying the 1 Methodology Analysis Template requirements perception. How does this Change in an The UP/RUP By jointly By continually approach do agile approach approach working in refactoring code things better works by consider groups with the to meet the needs than waterfall completing change through customer and of the test script (how does it tasks at a more iterations and user, you are always overcome the and more increments with requirements improving the deficiencies abstract level each phase; and the code, making it noted above)? through elaboration, changes in better by iterations and construction, them that occur correcting faults. increments. As and transition. are well defined change is and required in one understood. abstract phase the next less abstract phase can respond. In what type of An agile RUP is This approach TDD can be fast environment approach is customizable is best used because of the or situation most for projects to when time is an low number of will this appropriate customize as issue, where phases of the approach be when time and they need. It is quality matters, SDLC. TDD can most money are best used when where costs are be correct in appropriate? issues. the system is important, and stated purpose large and where buy in of because of the complex the system is at test first needing much stake. procedure. An iteration to environment complete. where just testers Developed for and coders are and used on present would OO systems define TDD’s environment. TDD is also used in OOP projects. What are the Large more This type of Some functional weaknesses of complex approach is not testing can not be this approach, systems require as fast as a tested only relative to a well traditional agile superficially. Full other structured life approach blown tests of approaches? cycle. Agile however things like query’s approaches are attempts have to databases or fast with less been made to user interfaces heavy popularize an must be tested structuring in Agile Unified fully; with code their phases. Process AUP. already written. 2 Methodology Analysis Template Bibliography on UP/RUP, JAD, and TDD Priestly M., Utt M. H. (2000) “A unified process for software and documentation development” http://delivery.acm.org.library.capella.edu/10.1145/510000/504836/p221- priestley.pdf?key1=504836&key2=6352945321&coll=portal&dl=ACM&CFID=824734&CFTOK EN=52522302 Retrieved Feb. 2009 from ACM database, Capella University Library. Krutchten P. (2000). “The Rational Unified Process: An Introduction, Second Edition, 2nd edition” http://my.safaribooksonline.com/0201707101/d1e824 Retrieved Feb. 2009 from ACM database, Capella University Library. Ambler S. W. (2002-2007). “Introduction to test driven design TDD” http://www.agiledata.org/essays/tdd.html Retrieved Feb. 2009. Palermo J. (2006). “Guidelines for test driven development” http://msdn.microsoft.com/en- us/library/aa730844(VS.80).aspx Retrieved Feb.2009. Yatco M. C. (1999). “Joint Application Design/Development” http://www.umsl.edu/~sauterv/analysis/JAD.html Retrieved Feb. 2009. Cline A. (no date). “Joint Application Development (JAD) for Requirements Collection and Management” http://www.carolla.com/wp-jad.htm Retrieved Feb.2009. 3 This document was created with Win2PDF available at http://www.win2pdf.com. The unregistered version of Win2PDF is for evaluation or non-commercial use only. This page will not be added after purchasing Win2PDF.