Hence, defects found must be properly logged in a system and their closure tracked. The use of informal mechanisms may lead to defects being found but later forgotten, resulting in defects not getting removed or in extra effort in finding the defect again. In such a scenario, defect reporting and closing cannot be done informally. Often the person who fixes a defect is different than the person who finds or reports the defect. Introduction:-A large software project may include thousands of defects that are found by different people at different stages of the project.
Restate the Problem as a Data Flow Diagram.The Architectural Tradeoff Analysis Method.Deployment View and Performance Analysis.Preserving the Integrity of an Architecture.Functional Specification with Use Cases.Components of an Software Requirements Specification.Characteristics of an Software Requirement Specification.Software Requirements Analysis and Specification.
Software Configuration Management Process.Support Testability and Maintainability.
