Software Risk Issues

-

1.Test Deliverables that need to be mentioned in the test plan :

Test Deliverables means The documents which are created during the testing process.
The documents created during the testing process are :
  • Test Plan 
  • Test Cases
  • Test Scripts
  • Defect/Enhancement Logs
  • Test Reports

2.Input documents that are needed and referred to write a Test Plan :

Test plan documents mean a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. In test planning phase test leader or test manager will create test plan documents.
Following documents are needed and referred to write this test plan are Requirement documents:
  • BRS(Business requirement specification)  
  • SRS (System requirement specification)
  • Development plan Document (DPD)
  • The Documents related to the previous version

3.Software Risk Issues :

It is also called a Product risk issue. The risk which is going to affect the product will mention here. Risk is an expectation of loss, a potential problem that may or may not occur in the future. It is generally caused due to lack of information, control or time. A possibility of suffering from loss in the software development process is called a software risk. Loss can be anything, an increase in production cost, development of poor quality software, not being able to complete the project on time. Software risk exists because the future is uncertain and there are many known and unknown things that cannot be incorporated in the project plan.
A software risk can be of two types:
  • Internal risks that are within the control of the project manager 
  • External risks that are beyond the control of the project manager.
Identify what software is to be tested and what the critical areas:
  • Delivery of a third party product.
  • The new version of interfacing software.
  • Ability to use and understand a new package/tool, etc.
  • Extremely complex functions.
  • Modifications to components with a past history of failure.
  • Poorly documented modules or change requests.
There are some inherent software risks such as complexity these need to be identified.
  • Safety.
  • Multiple interfaces.
  • Impacts on the Client.
  • Government regulations and rules.

4. Testing Be Suspended :

If any defects are found which seriously impact the test progress the test lead may choose to suspend testing.
The criteria which are considered for suspension or resumption are :
  • Hardware/software not available at the time indicated in the Project Schedule.
  • The build contains many serious defects which seriously prevent or limit testing progress.
  • Assigned test resources are not available when needed by the test team.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more