A Structured Approach to Systems TestingQED Information Sciences, 1983 - 543 sayfa |
Kitabın içinden
74 sonuçtan 1-3 arası sonuçlar
Sayfa 276
... complete ( maintainability ) Maintainable programs are well documented . One of the developmental steps that is easy to delay is documentation , yet the cost of incomplete documentation may be high after the system goes operational ...
... complete ( maintainability ) Maintainable programs are well documented . One of the developmental steps that is easy to delay is documentation , yet the cost of incomplete documentation may be high after the system goes operational ...
Sayfa 293
... complete ? 2 . Is user documentation current and complete ? 3 . Is data documentation current and complete ? 4 . Is security documentation current and complete ? 5 . Is program documentation current and complete ? 6 . Is system ...
... complete ? 2 . Is user documentation current and complete ? 3 . Is data documentation current and complete ? 4 . Is security documentation current and complete ? 5 . Is program documentation current and complete ? 6 . Is system ...
Sayfa 395
... complete ( i.e. , that which is required to perform all system functions ) and correct ( i.e. , the data types and relationships are consistent with the functions which need to be performed ) . V , V & T technique : о о Example : 3 ) A ...
... complete ( i.e. , that which is required to perform all system functions ) and correct ( i.e. , the data types and relationships are consistent with the functions which need to be performed ) . V , V & T technique : о о Example : 3 ) A ...
Diğer baskılar - Tümünü görüntüle
Sık kullanılan terimler ve kelime öbekleri
ADEQUATE ADEQUATE ADEQUATE V/N RECOMMENDED amination analysis ance Compli application system audit trail automated Boundary Value Analysis Checklist complete compliance Confirm Control Flow Analysis correct cyclomatic complexity Data flow analysis defined design review determine documentation effectiveness of testing employee ensure evaluate example execution Fact finding FIGURE file integrity Functional Testing graph identified input Inspec installation phase interface ments method methodology modules needed normally objectives output paths peer review performed personnel PHASE TEST PROCESS problems procedures PROCESS TEST FACTOR production program phase project team RECOMMENDED TEST TEST records recovery regression testing requirements phase responsibility risk matrix SDLC software testing subphase systems development TECHNIQUE TEST TOOL techniques and tools test conditions test cost test data test phase test plan TEST PROCESS TEST test team TEST TECHNIQUE TEST TEST TEST TECHNIQUE test transactions TESTING TOOLS APPENDIX tion/ex updated V/N RECOMMENDED TEST Verify Volume testing walk-through