Question

*****

41.   Differentiate between Alpha testing and Beta testing.
42.   Compare waterfall, spiral and agile software development life cycles.
43.   List the five objectives of SWEBOK.
44.   What are the Key Knowledge Areas in SWEBOK.
45.   Differentiate between positive, negative and exhaustive testing.
46.   Differentiate between Verification and Validation
47.   Define the following:
a.       Fault
b.      Error
c.       Defect
d.      Failure
48.   Differentiate between testing and debugging
49.   Explain the 3C attributes of Software Quality.
50.   List various quality attributes associated with Software development and testing.

Answer 1

41.

ALPHA TESTING	BETA TESTING
Alpha testing involves both the white box and black box testing.	Beta testing commonly uses black box testing.
Alpha testing is performed by testers who are usually internal employees of the organization.	Beta testing is performed by clients who are not part of the organization.
Alpha testing is performed at developer’s site.	Beta testing is performed at end-user of the product.
Reliability and security testing are not checked in alpha testing.	Reliability, security and robustness are checked during beta testing.
Alpha testing ensures the quality of the product before forwarding to beta testing.	Beta testing also concentrates on the quality of the product but collects users input on the product and ensures that the product is ready for real time users.
Alpha testing requires a testing environment or a lab.	Beta testing doesn’t require a testing environment or lab.
Alpha testing may require long execution cycle.	Beta testing requires only a few weeks of execution.
Developers can immediately address the critical issues or fixes in alpha testing.	Most of the issues or feedback collected from beta testing will be implemented in future versions of the product.

42.

Waterfall SDLC Model

Waterfall — is a cascade SDLC model, in which development process looks like the flow, moving step by step through the phases of analysis, projecting, realization, testing, implementation, and support. This SDLC model includes gradual execution of every stage completely. This process is strictly documented and predefined with features expected to every phase of this software development life cycle model.

Use cases for the Waterfall SDLC model:

• The requirements are precisely documented
• Product definition is stable
• The technologies stack is predefined which makes it not dynamic
• No ambiguous requirements
• The project is short

Spiral SDLC Model

Spiral model — is SDLC model, which combines architecture and prototyping by stages. It is a combination of the Iterative and Waterfall SDLC models with the significant accent on the risk analysis. The main issue of the spiral model — is defining the right moment to make a step into the next stage. The preliminary set time frames are recommended as the solution to this issue. The shift to the next stage is done according to the plan, even if the work on the previous stage isn’t done yet. The plan is introduced basing on the statistic data, received during the previous projects even from the personal developer’s experience.

Use cases for the Spiral model

• Customer isn’t sure about the requirements
• Major edits are expected during the development cycle
• The projects with mid or high-level risk, where it is important to prevent these risks
• The new product that should be released in a few stages to have enough of clients feedback

Agile SDLC Model

In the agile methodology after every development iteration, the customer is able to see the result and understand if he is satisfied with it or he is not. This is one of the advantages of the agile software development life cycle model. One of its disadvantages is that with the absence of defined requirements it is difficult to estimate the resources and development cost. Extreme programming is one of the practical use of the agile model. The basis of such model consists of short weekly meetings — Sprints which are the part of the Scrum approach.

Use cases for the Agile model:

• The users’ needs change dynamically
• Less price for the changes implemented because of the many iterations
• Unlike the Waterfall model, it requires only initial planning to start the project

43.

• characterize the contents of the Software Engineering Body of Knowledge;
• provide a topical access to the Software Engineering Body of Knowledge;
• promote a consistent view of software engineering worldwide;
• clarify the place of, and set the boundary of, software engineering with respect to other disciplines such as computer science, project management, computer engineering and mathematics;
• provide a foundation for curriculum development and individual certification and licensing material.

NOTE: As per Chegg policy, I am allowed to answer only 3 questions (including sub-parts) on a single post. Kindly post the remaining questions separately and I will try to answer them. Sorry for the inconvenience caused.