A Structured Approach to Systems Testing |
Kitabın içinden
42 sonuçtan 1-3 arası sonuçlar
Sayfa 54
STEP 3 - ASSIGN TEST RESPONSIBILITY Someone must assume responsibility
for the testing . In traditional testing where the life cycle follows a predetermined
sequence , acceptance of the system is normally a user responsibility . In other ...
STEP 3 - ASSIGN TEST RESPONSIBILITY Someone must assume responsibility
for the testing . In traditional testing where the life cycle follows a predetermined
sequence , acceptance of the system is normally a user responsibility . In other ...
Sayfa 118
REQUIREMENTS PHASE TEST RESPONSIBILITIES The requirements phase
should be a user - dominated phase . In other ... This means that the user , being
the dominant party , should take responsibility for requirements phase testing .
REQUIREMENTS PHASE TEST RESPONSIBILITIES The requirements phase
should be a user - dominated phase . In other ... This means that the user , being
the dominant party , should take responsibility for requirements phase testing .
Sayfa 152
DESIGN PHASE TEST RESPONSIBILITIES The design phase involves a close
working relationship between the user and the ... If the team is comprised of both
users and data processors , then the project team can accept test responsibility .
DESIGN PHASE TEST RESPONSIBILITIES The design phase involves a close
working relationship between the user and the ... If the team is comprised of both
users and data processors , then the project team can accept test responsibility .
Kullanıcılar ne diyor? - Eleştiri yazın
Her zamanki yerlerde hiçbir eleştiri bulamadık.
İçindekiler
1985 SURVEY ON SOFTWARE TESTING | 37 |
TESTING AN APPLICATION SYSTEM TEST PLAN | 43 |
PROGRAM PHASE TESTING | 209 |
Telif Hakkı | |
3 diğer bölüm gösterilmiyor
Diğer baskılar - Tümünü görüntüle
Sık kullanılan terimler ve kelime öbekleri
acceptance achieve action activities ADEQUATE ADEQUATE amination analysis ance application system appropriate ASSESSMENT authorization automated checking Checklist complete Compli conducted Confirm continued correct cost cycle data processing defects defined described DESCRIPTION detailed determine documentation effective ensure error established evaluate Examine example execution expected Fact finding FIGURE function graph identified implemented INDICATIVE individual input Inspec installation integrity involved limit maintenance manual measure ments method methodology METRIC modules needed normally objectives occur operations output paths performed personnel PHASE TEST prepared problems procedures production properly reasonableness RECOMMENDED TEST records recovery requirements responsibility risk selected shows skills specifications Step structure techniques TEST CRITERIA test data TEST FACTOR test process TEST TECHNIQUE TEST TEST TEST TOOL tion/ex tions trail transactions validation Verify