Software Development Life cycle N5天033983 MRD Review Fns Reviev QA Test Planning KP Test Resource Planning Test Strategy QR Functional MRD Engg Plan Test Plan SDLC PRODUCT REQUIREMENT PRODUCT DESIGN
6 Software Development Life Cycle QA KP PRODUCT REQUIREMENT QR MRD SDLC Functional Spec PRODUCT DESIGN - MRD Review - Test Resource Planning - FnS Review - Test Planning - Test Strategy Engg Plan Test Plan Zhu.Kerry@gmail.com
SPECIFICATION DOCUMENT 3.As we have seen, specifications are not easy to write o They are meticulously detailed(and often ponderous in g their wording Given even a simple program, rarely would two people program it the same way. We need to know what the user really wants One use for the specification document is that testers can find bugs even before a line of code is written
7 SPECIFICATION DOCUMENT • As we have seen, specifications are not easy to write. • They are meticulously detailed (and often ponderous in their wording) • Given even a simple program, rarely would two people program it the same way. We need to know what the user really wants. • One use for the specification document is that testers can find bugs even before a line of code is written. Zhu.Kerry@gmail.com
spec example 3 Let's see a example 3
8 Spec Example Let’s see a example Zhu.Kerry@gmail.com
What Happens If No spec 当· First, try to avoid such projects! 3 If you are stuck, you need to wait until you have the o software 3 Treat the software as the specification and explore it feature by feature Of course, you cannot tell if a feature is missing Start educating your company about the need to find bugs early in the development process
9 What Happens If No Spec • First, try to avoid such projects! • If you are stuck, you need to wait until you have the software. • Treat the software as the specification and explore it feature by feature. • Of course, you cannot tell if a feature is missing. • Start educating your company about the need to find bugs early in the development process! Zhu.Kerry@gmail.com
Why examining the spec N5天033983 In the past, most Software organizations are faced with a compelling need to Reduce cycle time Improve quality ° Reduce costs Improve productivity By Examining The Specification, we can We can find many bugs that we can't find through testing especially the logic design problems Find defects BEFORE production began ° Reduction of cost Shortening the software development life cycle
10 Why Examining the Spec ? ◼ In the past, most Software organizations are faced with a compelling need to: • Reduce cycle time • Improve quality • Reduce costs • Improve productivity ◼ By Examining The Specification, we can: • We can find many bugs that we can’t find through testing, especially the logic design problems. • Find defects BEFORE production began. • Reduction of cost. • Shortening the software development life cycle. Zhu.Kerry@gmail.com