1 / 16

Concise study of Progressive Documentation and its adaptation to Agile Software Testing

Concise study of Progressive Documentation and its adaptation to Agile Software Testing. 作者： Roshni Kanth 、 Madhu B K 、 Lokesha V 報告者： 975002510 鄭人榮. National Conference on Research Trends in Computer Science and Technology - 2012. Agile Software Testing.

jonny
Download Presentation

Concise study of Progressive Documentation and its adaptation to Agile Software Testing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Concise study of Progressive Documentation and its adaptation to Agile Software Testing 作者：RoshniKanth、Madhu B K、Lokesha V 報告者：975002510 鄭人榮 National Conference on Research Trends in Computer Science and Technology - 2012

  2. Agile Software Testing • Short life cycle time is the backbone and advantage of Agile Software Testing, given the relatively short turnaround time in this methodology it is important that the testingteam is clear onwhat needs to be tested. • The test activities provide objective data and conclusions about software and system quality.

  3. Agile Software Testing(Cont.) • Agile Software Testing requires innovative thinking and the right mix of people and skill should be chosen for doing the testing. • Early feedback allows the development organization to modify the products in a timely fashion and thereby reduce overall project and schedule impacts.

  4. Advantage ofdocumentation • Documentation also helps in Re-using and Re-engineering process. • A careful documentation can savean organization’s time, efforts and money. • Agile mechanism with careful implementation and co-processing results in remarkable optimized software product.

  5. Documentationchallenges • Increasing Complexity of Documentation Support • Globalization • Different Target Media • Increased Competition • High Quality Requirements • Integration • Shortening of Development Cycles • Availability • Increasing Demand for Documentation Variants

  6. Progressive Documentation Life Cycle • One of the prime reasons to state the same is the people involved in agile life development are highly motivated and technical experts. Hence a parallel process needs to be run with Agile Software Testing process. • This approach will give a special liberty to documentation as well as space to imprint facts need for the future reference. • The parallel process is termed as PDLC, which is started with SDLC and completes at the end of maintenance stage.

  7. Systems development lifecycle

  8. SDLC(Cont.) • Preliminary analysis ： Conduct a preliminary analysis, propose alternative solutions, describe costs and benefits and submit a preliminary plan with recommendations. • Systems analysis, requirements definition ： Defines project goals into defined functions and operation of the intended application. Analyzes end-user information needs.

  9. SDLC(Cont.) • Systems design ： Describes desired features and operations in detail, including screen layouts, business rules, process diagrams, pseudocode and other documentation. • Development ： The real code is written here. • Integration and testing ： Brings all the pieces together into a special testing environment, then checks for errors, bugs and interoperability.

  10. SDLC(Cont.) • Acceptance, installation, deployment ： The final stage of initial development, where the software is put into production and runs actual business. • Maintenance ：What happens during the rest of the software's life： changes, correction, additions, moves to a different computing platform and more. This is often the longest of the stages.

  11. Progressive Documentation Life Cycle

  12. PDLC(Cont.) • Content Management the stage of Feasibility study and Requirement Analysis stage of SDLC. • Workflow design, development and testing phases of SDLC.

  13. PDLC(Cont.) • Editing And Publishing the end of SDLC much of the developmental work would be finished and results analysis and test result validation would be documented. list the changes in requirements is done in this stage.

  14. PDLC(Cont.) • Help, Update & Feedback(FQA) Any important instruction, do’s and don’ts are listed. Future enhancement for the system, the timeline to make some necessary changes in the code is documented and discussed. This document is kept for re-use and re-engineering process in the new product development.

  15. Pair Programming with On-site Customer 1..N Bugs CYCLE TIME 5 seconds 簡約設計 交貨規劃 重構 測試碼保護中 1..N Methods CYCLE TIME 0.5day 持續整合 增量 1..NIterations CYCLE TIME 3 weeks 增量加 上次交貨 1..N Increments CYCLE TIME 2 months Communication Cycle 溝通週期 回合規劃 站著 開日會 CYCLE TIME 1day 喜好度調查 1..N Questions CYCLE TIME 5 seconds (Not in XP)

  16. Thanks!

More Related