tailieunhanh - Chapter 05: Testing Process - Nguyen Thi Thanh Thuy

Content Chapter 05 Testing Process: Process lab, Project Management, Software Development Management; Testing Process; Tools, Bug zilla.   | Testing Process nttthuy@ Content Process lab Project Management Software Development Management Testing Process Tools Bug zilla Purpose To verify that all requirements have been correctly implemented To verify the proper integration of all components of the software To validate that the product, as provided, will fulfill its intended use when placed in its intended environment To determine how well a system meets its original objectives Defect Any type of undesired result is a defect. The failure meets one of the acceptance criteria of your customers. A defective unit may have one or more defects. A defect is a failure to conform to requirements' (Crosby, 'Quality Is Free'), whether or not those requirements have been articulated or specified. The non-conformance intend usage requirement Bug It is a problem in software. The part of code that makes the program behaves in an unwanted manner. The sooner a bug is detected in the Software Lifecycle, lesser would be the cost . | Testing Process nttthuy@ Content Process lab Project Management Software Development Management Testing Process Tools Bug zilla Purpose To verify that all requirements have been correctly implemented To verify the proper integration of all components of the software To validate that the product, as provided, will fulfill its intended use when placed in its intended environment To determine how well a system meets its original objectives Defect Any type of undesired result is a defect. The failure meets one of the acceptance criteria of your customers. A defective unit may have one or more defects. A defect is a failure to conform to requirements' (Crosby, 'Quality Is Free'), whether or not those requirements have been articulated or specified. The non-conformance intend usage requirement Bug It is a problem in software. The part of code that makes the program behaves in an unwanted manner. The sooner a bug is detected in the Software Lifecycle, lesser would be the cost involved in fixing it. The term bug came from the fact that a moth flew into an early computer that ran on vacuum tubes. Error It is a mistake, a wrong action attributable to bad judgment or ignorance or inattention Severity After the bug is opened, it has to be classified as the severity and make the priority for those bugs Critical: Any bug/defect/error that stops the standard functionality of program from working as designed, no work around is available. It may get to rework with big cost or can not acceptable by customer or it is inconsistent with the requirement. Major: Any bug/defect/error that affects standard program functionality from working as designed, a work around is available Severity Normal: Any bug/defect/error that affects enhanced program features from working as designed, a work around is available Minor: The product is not working as it was designed, but this is a cosmetic or trivial problem that has little or no business impact on the customer. Trivial: Fix if .

• Cơ sở dữ liệu
• Software Process Models
• Software Process Models
• Dependent on software
• Software engineering
• Testing Process
• Công nghệ phần mềm
• Công nghệ thông tin
• Deployment Process
• Process lab
• Analysis Process
• Design Process
• Requirement Process
• Development Process
• Rational Unified Process Made Easy
• Practitioner’s Guide to RUP
• Lecture Software engineering
• Software process
• Process models
• Process patterns
• Software Processes
• Process activities
• Process iteration
• Bài giảng Kỹ thuật phần mềm
• Process improvement
• Lecture Software process improvement
• Bài giảng Cải tiến quy trình phần mềm
• Software process improvement
• Process standardization
• Kỹ thuật phần mềm
• Extreme programming
• Programming practices
• Problem statement
• Basic requirements
• Software process descriptions
• The waterfall model
• Waterfall model phases
• Lecture Software design
• Software design
• Bài giảng Thiết kế phần mềm
• Agile process models
• Nhập môn Công nghệ phần mềm
• Copingwith change
• Objected oriented
• Classical software engineering
• The scope of software engineering
• Software life cycle models
• The software process
• The tools of the trade
• Planning and estimating
• System models
• Context models
• Logical system models
• Business process models
• State transition diagrams
• Company’s centralized database
• Reliable component base system
• Component software
• Component based development process
• Component models
• Component composition