Software Development Life Cycle

Software Development Life Cycle

Software development approach and has a value proposition that includes faster turnaround times, trained pool of engineers with decent exposure to processes and best practices followed for the entire SDLC.

We have exposure on the following SDLC models :

• Waterfall
• V-Shaped
• Structured Evolutionary Prototyping Model
• Incremental
• Spiral
• Agile

A brief description of the various models mentioned above is given below. Along with the description, we have mentioned the strengths and discussed when a particular model is suited to you:

Advertisements

 

Identifying sqa issues

Software Quality Assurance is a good practice that every large scale business should employ. IT related businesses have never hesitated to use SQA to ensure that the application they will release for their users or sell to their customers will live up to their expectations.

Sponsored Links

On the other hand, there are companies that has opted to forgo with the usage of SQA and relied on application testers just to make sure the application will never have internal errors. The SDLC on the other hand, will ensure the development of the application will work as planned.

Like other development plans, there are issues why developers and companies do not use SQA.

 

IEEE SOFTWARE TEST DOCUMENTATION Std 829-1998 – TEST PLAN

Purpose
To describe the scope, approach, resources, and schedule of the testing activities. To identify the items being tested, the features to be tested, the testing tasks to be performed, the personnel responsible for each task, and the risks associated with this plan.

 

Software Testing Levels, Types, Terms and Definitions

Testing Levels and Types
There are basically three levels of testing i.e. Unit Testing, Integration Testing and System Testing. Various types of testing come under these levels.

Unit Testing:
To verify a single program or a section of a single program

Integration Testing:
To verify interaction between system components
Prerequisite: unit testing completed on all components that compose a system

System Testing:
To verify and validate behaviors of the entire system against the original system objectives
Software testing is a process that identifies the correctness, completeness, and quality of
software.

 

Most common software errors

Following are the most common software errors that aid you in software testing. This helps you
to identify errors systematically and increases the efficiency and productivity of software testing.
Types of errors with examples
• User Interface Errors: Missing/Wrong Functions, Doesn’t do what the user expects, Missing
information, Misleading, Confusing information, Wrong content in Help text, Inappropriate error
messages. Performance issues – Poor responsiveness, Can’t redirect output, Inappropriate use of
key board
• Error Handling: Inadequate – protection against corrupted data, tests of user input, version
control; Ignores – overflow, data comparison, Error recovery – aborting errors, recovery from
hardware problems.
• Boundary related errors: Boundaries in loop, space, time, memory, mishandling of cases
outside boundary.
• Calculation errors: Bad Logic, Bad Arithmetic, Outdated constants, Calculation errors,
Incorrect conversion from one data representation to another, Wrong formula, Incorrect
approximation.

 

Verification and Validation

 Verification and Validation.

• Testing is part of verification and validation.
• Verification: Are we building the product right?
• Validation Are we building the right product?
• V&V activities include a wide range of the SQA activities.

 

Some Important terminologies

Some Important terminologies

• Project :  If something is developed based on a particular user/users requirements, and is used exclusively by them, then it is known as project. The finance is arranged by the client to complete the project successfully.
• Product :  If something is developed based on company’s specification (after a general survey of the market requirements) and can be used by multiple set of masses, then it is known as a product. The company has to fund the entire development and usually expect to break even after a successful market launch.
• Defect v/s Defective: If the product is justifying partial requirements of a particular customer but is usable functionally, then we say that The product has a defect, But If the product is functionally non usable , then even if some requirements are satisfied, the product still will be tagged as Defective.
• Quality Assurance : Quality assurance is a process of monitoring and guiding each and every role in the organization in order to make them perform their tasks according to the company’s process guidelines.