0% found this document useful (0 votes)
21 views2 pages

Co3 Pmse

The document discusses software implementation and testing which includes coding, characteristics of programming languages, structured programming, coding standards and guidelines, code review techniques like code inspection and code walk through, and types of software documentation.

Uploaded by

fayizkozhikode
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
21 views2 pages

Co3 Pmse

The document discusses software implementation and testing which includes coding, characteristics of programming languages, structured programming, coding standards and guidelines, code review techniques like code inspection and code walk through, and types of software documentation.

Uploaded by

fayizkozhikode
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

MODULE III: SOFTWARE IMPLEMENTATION & TESTING

Coding: the coding phase is to transform the design of a system into code in a high-level
language
Characteristics of a Programming Language

• Readability
• Portability
• Generality
• Brevity
• Error checking
• Cost
• Familiar notation
• Quick translation
• Efficiency
• Modularity
• Widely available

Structured Programming: the program be easy to understand Coding

standards and guidelines


1. Rules for limiting the use of global
2. Contents of the headers preceding codes for different modules
3. Naming conventions for global variables, local variables, and constant identifiers
4. Error return conventions and exception handling mechanisms
5. Do not use a coding style that is too clever or too difficult to understand
6. Avoid obscure side effects
7. Do not use an identifier for multiple purposes
8. The code should be well-documented
9. The length of any function should not exceed 10 source lines 10. Do not use goto
statements
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
• two types code review techniques
• code inspection
• code walk through.
Code Inspection
• The basic goal of inspections is to improve the quality of code by finding defects.
• characteristics of inspections
• Code inspection is conducted by programmers and for programmers.
• It is a structured process with defined roles for the participants.
• The focus is on identifying defects, not fixing them.
• Inspection data is recorded and used for monitoring the effectiveness of the
inspection process
Stages in inspections
• Planning
• self-review
• group review meeting
• rework and follow-up
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.
• The main objectives of the walk through are to discover the algorithmic and
logical errors in the code.
Software documentation
• Software documentation provides information about a software program for
everyone involved in its creation, deployment and use.
• Types of software documentation
• internal
• external
Internal software documentation
• Developers and software engineers create internal documentation that is used
inside a company
• Internal documentation may include:
• Administrative documentation
• Developer documentation
External software documentation
• Software developers create this documentation to provide IT managers and end
users with information on how to deploy and use the software.
• External documentation includes:
• End-user documentation
• Enterprise user documentation
• Just-in-time documentation

You might also like