https://medium.

com/swlh/comparing-3-popular-pricing-models-fixed-price-time-materials-and-
milestone-6b986021f2ed

RAD software development : https://www.tutorialspoint.com/sdlc/sdlc_rad_model.htm

https://www.guru99.com/compare-waterfall-vs-incremental-vs-spiral-vs-rad.html

https://www.geeksforgeeks.org/software-engineering-cocomo-model/

Sprint planning is an event in the Scrum framework where the team determines the product backlog
items they will work on during that sprint and discusses their initial plan for completing those
product backlog items.

During the daily scrum, each team member answers the following three questions:

1. What did you do yesterday?

2. What will you do today?
3. Are there any impediments in your way?

https://www.agilealliance.org/glossary/sprint-
planning/#q=~(infinite~false~filters~(postType~(~'page~'post~'aa_book~'aa_event_session~'aa_exp
erience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'sprint*20planning))~searchTer
m~'~sort~false~sortDirection~'asc~page~1)

Illustrate any three competencies that are required in order to become a successful

software Project Manager.

https://www.guru99.com/traceability-matrix.html

https://www.guru99.com/software-configuration-management-tutorial.html#10

What is Black Box testing?

In Black-box testing, a tester doesn't have any information about the internal working of the
software system. Black box testing is a high level of testing that focuses on the behavior of the
software. It involves testing from an external or end-user perspective. Black box testing can be
applied to virtually every level of software testing: unit, integration, system, and acceptance.

This type of testing is ideal for higher levels of testing like System Testing, Acceptance testing
What is White Box testing?

White-box testing is a testing technique which checks the internal functioning of the system. In this
method, testing is based on coverage of code statements, branches, paths or conditions. White-Box
testing is considered as low-level testing. It is also called glass box, transparent box, clear box or
code base testing. The white-box Testing method assumes that the path of the logic in a unit or
program is known. Programming knowledge required.

Testing is best suited for a lower level of testing like Unit Testing, Integration testing.

TESTING TYPES

Analyze the need for it and elaborate on the key aspects of any six types of testing
Unit Testing, : Testing of an individual software component or module is termed as Unit Testing. It is
typically done by the programmer and not by testers, as it requires detailed knowledge of the
internal program design and code. It may also require developing test driver modules or test
harnesses. Unit Testing is used to design robust software components that help maintain code and
eliminate the issues in code units.

Integration testing, Testing of all integrated modules to verify the combined functionality after
integration is termed as Integration Testing.

Modules are typically code modules, individual applications, client and server applications on a
network, etc. The main function or goal of this testing is to test the interfaces between the
units/modules.

 In the real world, when applications are developed, it is broken down into smaller modules
and individual developers are assigned 1 module. The logic implemented by one developer is
quite different than another developer, so it becomes important to check whether the logic
implemented by a developer is as per the expectations and rendering the correct value in
accordance with the prescribed standards.
 A very common problem in testing – Frequent requirement change! :) Many a time
developer deploys the changes without unit testing it. Integration testing becomes
important at that time

System testing: Under System Testing technique, the entire system is tested as per the
requirements. It is a Black-box type Testing that is based on overall requirement specifications and
covers all the combined parts of a system.

 Load testing
 Stress testing
 Security testing
 Performance testing
 ST is performed in an environment which is similar to the production environment and
hence stakeholders can get a good idea of the user's reaction.
 It helps to minimize after-deployment troubleshooting and support calls.
 In this STLC stage Application Architecture and Business requirements, both are tested.
Performance Testing: This term is often used interchangeably with ‘stress' and ‘load' testing.
Performance Testing is done to check whether the system meets the performance requirements.
Different performance and load tools are used to do this testing.

Acceptance Testing: An Acceptance Test is performed by the client and verifies whether the end to
end the flow of the system is as per the business requirements or not and if it is as per the needs of
the end-user. Client accepts the software only when all the features and functionalities work as
expected.

It is the last phase of the testing, after which the software goes into production. This is also called
User Acceptance Testing (UAT).

Regression testing

AGILE ESTIMATION TECHNIQUES

https://www.softwaretestinghelp.com/agile-estimation-techniques/