Sad assignment

Q1. What is system testing ?
Explain the different types of
system testing ?
Ans  :-
System testing is the process of
evaluation a software item to detect differences between given input and expected output. Also to assess the feature of A software item. Testing assesses the quality of the product. System testing is a process that should be done during the development process. In other words system testing is a verification and validation process.

Verification:-
Verification is the process to make
sure the product satisfies the
conditions imposed at the start of
the development phase. In other
words, to make sure the product
behaves the way we want it to.

Validation:-
Validation is the process to make sure the product satisfies the specified requirements at the end of the development phase. In other words, to make sure the product is built as per customer requirements.

Basics of software testing
There are two basics of software
testing:-
1.Blackbox testing
2.Whitebox testing.

Blackbox Testing
Black box testing is a testing
technique that ignores the internal
mechanism of the system and
focuses on the output generated
against any input and execution of
the system. It is also called functional testing.

Whitebox Testing
White box testing is a testing
technique that takes into account
the internal mechanism of a system. It is also called structural testing and glass box testing.
Black box testing is often used for
validation and white box testing is
often used for verification.

Types of testing

There are many types of testing like

1.Unit Testing
2.Integration Testing
3.Functional Testing
4.System Testing
5.Stress Testing
6.Performance Testing
7.Usability Testing
8.Acceptance Testing
9.Regression Testing
10.Beta Testing

Unit Testing
Unit testing is the testing of an
individual unit or group of related
units. It falls under the class of
white box testing. It is often done
by the programmer to test that the unit he/she has implemented is producing expected output against given input.

Integration Testing
Integration testing is testing in
which a group of components are
combined to produce output. Also,
the interaction between software
and hardware is tested in
integration testing if software and
hardware components have any
relation. It may fall under both
white box testing and black box
testing.

Functional Testing
Functional testing is the testing to
ensure that the specified
functionality required in the system requirements works. It falls under the class of black box testing.

System Testing

System testing is the testing to
ensure that by putting the software in different environments (e.g., Operating Systems) it still works.
System testing is done with full
system implementation and
environment. It falls under the class of black box testing.
Stress Testing Stress testing is the testing to evaluate how system behaves under unfavorable conditions. Testing is conducted at beyond limits of the specifications. It falls under the class of black box testing.

Performance Testing
Performance testing is the testing to assess the speed and effectiveness of the system and to make sure it is generating results within a specified time as in performance requirements. It falls under th class of black box testing.

Usability Testing
Usability testing is performed to the perspective of the client, to evaluate how the GUI is user-friendly? How easily can the client learn? After learning how to use, how proficiently can the client perform? How pleasing is it to use its design? This falls under the class of black box testing.

Acceptance Testing:-
Acceptance testing is often done by the customer to ensure that the delivered product meets the
requirements and works as the
customer expected. It falls under
the class of black box testing.
Regression Testing Regression testing is the testing after modification of a system,
component, or a group of related
units to ensure that the modification is working correctly and is not damaging or imposing other modules to produce unexpected results. It falls under the class of black box testing.

Beta Testing
Beta testing is the testing which is
done by end users, a team outside
development, or publicly releasing
full pre-version of the product which is known as beta version. The aim of beta testing is to cover unexpected errors. It falls under the class of black box testing.

Q2. Explain the goal of quality assurance in SDLC? Explain level of SQA?
Ans:-
Following are the SQA Goals:-

• Requirements quality

o Ambiguity

o Completeness

o Volatility

o Traceability

o Model clarity

• Design quality

o Architectural integrity

o Component completeness

o Interface complexity

o Patterns

• Code quality

o Complexity

o Maintainability

o Understandability

o Reusability

o Documentation

• Quality control effectiveness

o Resource allocation

o Completion rate

o Review effectiveness

o Testing effectiveness

Following are the various levels of SQA:-

Level 1 - Initial or chaotic

Level 1 means that the software development methodology, followed by an organization is in its novice stage, and is filled with chaos, and periodic panics. Due to lack of any methodology, heroic effort is required by individuals, to successfully complete projects. No software process is in place, and even if the organization meets with success in a project, successes may not be repeatable in other projects.

Level 2 – Repeatable

Level 2 in the CMM model means that, some software development process is in place, and is being followed. Software project tracking, requirements management, realistic planning, and configuration management are part of the process in place. The success achieved by the organization in a project is repeatable in other projects.

Level 3 – Defined

Level 3 in the model signifies that standard software development, and maintenance processes are integrated throughout an organization. It also means that, a Software Engineering Process Group is in place, to oversee software processes, and training programs are used to ensure understanding, and compliance. Any organization that does contracts for the US Department of defense, must reach this level.

Level 4 – Managed

If an organization reaches level 4 in the CMM model, then it means that metrics are used, to track productivity, processes, and products. Project performance is predictable, and quality is consistently high. [1]

Level 5 – Optimized

At level 5 of the CMM model, the focus is on continuous process improvement. The impact of new processes, and technologies, can be predicted, and effectively implemented when required. Moreover, as and when required, the software development methodology that’s practiced is optimized to suit the changing needs.
Q3. Explain the
implementation and maintenance
of software system? ?

Deadline 18/10/14