Software Engineering - Topic 6

Software Engineering - Topic 6

by Mark Lister V. Nalupa

​Intended Learning Outcomes

​1.   Identify the characteristics of a good programming language

2.   Apply coding standards and guidelines

3.   Apply code review techniques

4.   Identify different types of software documents

Fill in the Blanks

The process of using a programming language to convert specified requirements into software source code and later into compiled code for execution.

​Implementation

Fill in the Blanks

A programming language characteristic that allows programs to be written in some ways that resemble a quite-English description of the underlying algorithms.

Fill in the Blanks

A programming language characteristic that allows the writing of a wide variety of programs.

Fill in the Blanks

A programming language characteristic that implements the algorithm with less amount of code.

​Characteristics of a Programming Language

• ​Readability

• ​Portability

• ​Generality

• ​Brevity

• ​Error checking

• ​Cost

• ​Familiar notation

• ​Quick translation

• ​Efficiency

• ​Modularity

• ​Widely available

Coding Standards and Guidelines

Multiple Choice

Good coding practice must limit the use of global data.

• True

• False

Multiple Choice

Format of code's header should be standardized for all software development companies.

• True

• False

Multiple Choice

Good coding practice must follow a naming convention for global variables, local variables, and constant identifiers.

• True

• False

Multiple Choice

The way error conditions are reported by different functions in a program are handled should be standardized within an organization

• True

• False

​Coding Guidelines Recommended by Many Software Development Organizations

1. ​Do not use a coding style that is too clever or too difficult to understand

2. ​Avoid obscure side effects

3. ​Do not use an identifier for multiple purposes

4. ​Code should be well documented

5. ​Length of any function should not exceed 10 source lines

6. ​Do not use goto statements

Fill in the Blanks

This is carried out after the module is successfully compiled and the all the syntax errors have been eliminated.

Code Review

Fill in the Blanks

The main objective of this type of code review is to discover the algorithmic and logical errors in the code.

Fill in the Blanks

The main objective of this type of code review is to discover some common types of errors caused due to oversight and improper programming.

Fill in the Blanks

This type of testing was pioneered by IBM.

Software Documentation

Fill in the Blanks

This type of software document is provided as part of the source code itself

Fill in the Blanks

This type of software document is provided through various types of supporting documents such as users’ manual, software requirements specification document, design document, test documents, etc.

​1.   Identified the characteristics of a good programming language

2.   Identified coding standards and guidelines

3.   Identified different types of code review techniques

4.   Identified different types of software documents

​

​

-end-