Scribd
Upload
4 views

unit_4.1

The document outlines the importance of coding standards and guidelines in software development, emphasizing uniformity, code understanding, and good programming practices. It discusses various coding standards, such as naming conventions and error handling, as well as the significance of code reviews and testing methodologies like code walkthroughs and inspections. Additionally, it differentiates between functional testing and structural testing, highlighting their respective approaches to test case design.

Uploaded by

Rohit 14
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
4 views

unit_4.1

The document outlines the importance of coding standards and guidelines in software development, emphasizing uniformity, code understanding, and good programming practices. It discusses various coding standards, such as naming conventions and error handling, as well as the significance of code reviews and testing methodologies like code walkthroughs and inspections. Additionally, it differentiates between functional testing and structural testing, highlighting their respective approaches to test case design.

Uploaded by

Rohit 14
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

CODING & TESTING Unit-4

A N IN T ROD U CTION - Abhilash Chakraborty


CODING STANDARDS
Good software development organizations normally require their programmers to adhere to some well-
defined and standard style of coding called coding standards.

Why do engineers of an organization need to adhere to a standard style of coding?

❑ A coding standard gives a uniform appearance to the codes written by different


engineers.
❑ It enhances code understanding. Unit-4

❑ It encourages good programming practices.


- Abhilash Chakraborty
CODING STANDARDS
Good software development organizations usually develop their own coding standards and
guidelines depending on what best suits their organization and the type of products they
develop.

Unit-4

- Abhilash Chakraborty
CODING STANDARDS.
1. Rules for limiting the use of global:
These rules list what types of data can be declared global and what cannot.
2. Contents of the headers preceding codes for different modules:
Information contained in the headers of different modules should be standard for an organization.
3. Naming conventions for global variables, local variables, and constant identifiers:
A possible naming convention can be that global variable names always start with a capital letter,
local variable names are made of small letters, and constant names are always capital letters.
4. Error return conventions and exception handling mechanisms:
The way error conditions are reported by different functions in a program
Unit-4 are handled should be
standard within an organization. For example, different functions while encountering an error
condition should either return a 0 or 1 consistently.
- Abhilash Chakraborty
CODING GUIDELINES.
1. Do not use a coding style that is too clever or too difficult to understand:
Code should be easy to understand. Clever coding can obscure meaning of the code and hamper
understanding. It also makes maintenance difficult.
2. Avoid obscure side effects:
The side effects of a function call include modification of parameters passed by reference, modification
of global variables, and I/O operations.
3. Do not use an identifier for multiple purposes:
Programmers often use the same identifier to denote several temporary entities. For example, some
programmers use a temporary loop variable for computing and a storing the final result.
4. The code should be well-documented:
As a rule of thumb, there must be at least one comment line on the average for every three-source line.
5. The length of any function should not exceed 10 source lines: Unit-4
A function that is very lengthy is usually very difficult to understand as it probably carries out many
different functions and are likely to have disproportionately larger number of bugs.
6. Do not use goto statements: - Abhilash Chakraborty
Use of goto statements makes a program unstructured and makes it very difficult to understand.
CODE REVIEW
Code review for a model is carried out after the module is successfully compiled and the all the syntax
errors have been eliminated.
Code reviews are extremely cost-effective strategies for reduction in coding errors and to produce
high quality code.
There are basically types of code review techniques:
➢ Code Walk Throughs
➢ Code Inspection
Unit-4

- Abhilash Chakraborty
CODE WALK THROUGHS
Code walk through is an informal code analysis technique. In this technique, after a module
has been coded, successfully compiled and all syntax errors eliminated.

Some of example guidelines are the following.


• The team performing code walk through should not be either too big or too small. Ideally, it
should consist of between three to seven members.
• Discussion should focus on discovery of errors and not on how to fix the discovered errors.
• In order to foster cooperation and to avoid the feeling among engineers
Unit-4 that they are
being evaluated in the code walk through meeting, managers should not attend the walk
through meetings
- Abhilash Chakraborty

NOTE: These are not standard guidelines, they are just given as an example.
CODE INSPECTION
The main objective of code inspection is to check for the presence of common types of error that
usually arise in code due to programmer oversight or improper programming.

Following is a list of some classical programming errors which can be checked during code inspection:
•• Use of uninitialized variables.
•• Jumps into loops.
•• Nonterminating loops.
•• Incompatible assignments. Unit-4

•• Array indices out of bounds.


- Abhilash Chakraborty
•• Improper storage allocation and deallocation.
PROGRAM TESTING
Testing a program consists of providing the program with a set of test inputs (or test cases) and
observing if the program behaves as expected.
If the program fails to behave as expected, then the conditions under which failure occurs are noted
for later debugging and correction.

Some commonly used terms associated with testing are:


•Error: It is a mistake committed by the developer team during any of the development phases.
•• Failure: This is a manifestation of an error (or defect or bug). But, the mere presence of an
Unit-4
error may not necessarily lead to a failure.
•• Test case: This is the triplet [I,S,O], where I is the data input to the system, S is the state of the
system at which the data is input, and O is the expected output -ofAbhilash
the system.
Chakraborty
•• Test suite: This is the set of all test cases with which a given software product is to be tested.
FUNCTIONAL TESTING VS. STRUCTURAL TESTING

In the black-box testing approach, test cases are designed using only the functional specification of the
software, i.e. without any knowledge of the internal structure of the software. For this reason, black-
box testing is known as functional testing.

On the other hand, in the white-box testing approach, designing test cases requires thorough
knowledge about the internal structure of software, and therefore the white-box testing is called
structural testing.
Unit-4

- Abhilash Chakraborty

You might also like