Scribd
Upload
3 views6 pages

Software Testing Notes 2

The document outlines the Software Development Life Cycle (SDLC) phases, which include Requirement Analysis, Feasibility Study, Design, Development, Testing, Deployment, and Maintenance. Each phase involves specific roles and deliverables, such as Business Requirement Documents (BRS), System Requirement Specifications (SRS), and various maintenance types like corrective, adaptive, perfective, and preventive changes. It emphasizes the importance of addressing defects and improving software based on user feedback and technological changes.

Uploaded by

rayachur sreenath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
3 views6 pages

Software Testing Notes 2

The document outlines the Software Development Life Cycle (SDLC) phases, which include Requirement Analysis, Feasibility Study, Design, Development, Testing, Deployment, and Maintenance. Each phase involves specific roles and deliverables, such as Business Requirement Documents (BRS), System Requirement Specifications (SRS), and various maintenance types like corrective, adaptive, perfective, and preventive changes. It emphasizes the importance of addressing defects and improving software based on user feedback and technological changes.

Uploaded by

rayachur sreenath
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Day2

SDLC

66
55 ad
96
85 ey
99 S

OR
1.Requiremnt Analysis

2.Feasibility Study

3.Design

4.Development/Coding

5.Testing

6.Deployment

7.Maintenance
66
55 ad
96
85 ey

1.Requment Analysis:
99 S

Business Analyst:

1. Business Analyst ---→ BRS/BRD/CRD(Contains Functional req in Non Technical


Language )

2. Sr.Team(System Analyst)--→ SRS (Contains Functional req In Technical Language)

2.Feasibility Study:

• Product Manager

• BA

• Architect

• Finance Team

• Hr Team

1.Project Manager-→Project Plan (Contains scope of the


project,Budget,Resources,Team schedule ,Etc..,)
3.Design

Architect/UI/UX Designer

Design Documents

1. HLD→High Level Document -→ Describes flow between Modules

2. LLD→Low Level Document -→Describes Flow within the modules

4. Development/Coding

Developers

66
55 a
1. Build-→Code is ready for testing
d
5. Testing
96
85 e
• QA(Quality Analyst)
y

1.Test Document→It is done by tester STLC starts here.


99 S

6. Deployment

• Field engineer ,Site Engineer

1.User Manual→Tested Software is deployed at client side


7. Maintenance

If any defect is found by the end user r customer while using the product in live environment
it will be handleled by the maintance team

• Developers &QA(Quality Analyst)

• Corrective Change

• Adaptive Change

• Perfective Change

66
• Preventive Change
55 ad
96
85 e
Maintance Phase:
y

1. Corrective Change
99 S

2. Adaptive Change

3. Perfective Change

4. Preventive Change

1.Corrective Software Maintenance

Defect in the software arises due to errors and faults in design, logic, and code of the
software. Corrective maintenance action (commonly referred to as “bug fixing”) addresses
these errors and faults in your software system.

Corrective changes in the software are required when:

• Software is not working the way it is expected due to some acute issues, such as
faulty logic flow, incorrect implementation, invalid or incomplete tests, etc.

• The issues in the software are affecting users after you have released the software.

2. Adaptive Software Maintenance

Adaptive maintenance aims at updating and modifying the software when:


1. The platform in which your software operates is changing (due to technology, laws,
policies, rules, operating system,etc.)

2. Your customers need the product to interface with new hardware or software.

3. You have predicted defects in the software that will affect your customers in the
future.

3. Perfective Software Maintenance

Perfective software maintenance is performed when you update the software system to
improve its value, according to user demands. This includes:

1. Speed optimization

66
55 a
2. Improvement in user interfaces
d
3. Improvements in software usability

96
4. Enhancement of software functionality
85 e
5. Improvement in software performance.
y
99 S

4. Preventive Software Maintenance

Preventive maintenance is a software change you make to prevent the occurrence of


errors in the future. It increases the software maintainability by reducing its complexity.
Preventive maintenance task include:

1. Updating the documentation: Updating the document according to the current


state of the system.

2. Optimizing the code: Modifying the code for faster execution of programs or making
efficient use of storage space.

3. Reconstructing the code: Transforming the structure of the program by reducing the
source code, making it easily understandable.
99 S
85 ey
55 ad
96
66

You might also like