Documents Flashcards
Black and white agreement of duties of the client and developer
Software development agreement/contract
Describes the requirements of the software
User Requirement Specification
Defines system requirements depending on the URS
System Requirement Specification
Used in Testing and recording after the software has been developed
System Test Cases
After all system test cases are successful, this is conducted to check if the software covers all points mentioned in the URS
User Acceptance Testing
All bugs/defects recorded during UAT/STC are mentioned here so they can be fixed
Defect track log
Identifies user’s expectation of the product
Well written, w/out ambiguity
IEEE Standard 830-1993
Business analysts involved
System requirements specification
Describes Calculations, technicalities
Functional requirement specification
> list requirements to validate product against ereqs and verify if according to specs
trace origin of requirement, identify how they will be satisfied and what impact will result if they are changed
Requirements traceability matrix
Communicated decisions and concepts on how to create a product
Diagrams to show the fxns
Pegs
Design document
Identify objectives, scope, approach and focus of product testing
Test plan
Written by testers
Identifies findings and recommendations to fix bugs
Test report
Records of date, time , meetings, topics discussed, decisions, open issues snd action items
Record absent and what had transpired in the meeting
Meeting minutes
Communicates info of the product’s new features and functions. System and instrallation requirements
Release noted
Instructs user how to use the product
User guides and training manuals
