Scribd
Upload
34 views5 pages

Code Freeze

Uploaded by

souravjdas23
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
34 views5 pages

Code Freeze

Uploaded by

souravjdas23
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/ 5

Code Freeze

Code freeze is an activity where the developers pause to make any further code changes. There are three types of
freezes in SDLC, namely requirement freeze, code freeze, and feature freeze.

What is a Code Freeze?

Code freeze is stopping any modification in the code for a certain period of time. It generally takes place at the later
stages of SDLC, while the software is being planned for a release. Thus, it is done to limit further changes to the
software just before being shipped to the customers.

A code freeze is implemented to avert a situation where the developers make changes to the code at the last moment,
and impact its stability. As a code freeze is announced, there are no possibilities to make any updates to the software.

However, in case of unavoidable circumstances, where critical bug fixes need to be made, code changes can be pushed
by the developers only after a thorough review and approvals from the project stakeholders. Post code fix stage, the
software is considered ready for production deployment.

This concept is generally followed in the waterfall model of development. However, it is not widely accepted in the
Agile framework since it is redundant there and does not follow the principles of agile. Moreover, it brings down the
software quality and slows down production release.

Why is Code Freeze Important?

 It avoids potential risks on the code stability.


 It does not allow the developers to make recurrent changes to the software.
 It provides flexibility to the developers to integrate multiple modules without worrying about unforeseen
errors.
 It helps to continue a good site performance by stopping service disturbances.

Advantages of Code Freeze

 Restricts unforeseen modifications and errors during code changes.


 It confirms a stable software.
 Code freeze period can be utilized by developers for other code optimization projects.

Disadvantages of Code Freeze

 It can result in poorly developed code due to strict project timelines.


 It requires approval from project stakeholders before starting a code freeze.
 It requires approval from project stakeholders to make critical bug fixes during a code freeze.
 The developers are not fully occupied with work during the code freeze period.

Best Practices to be Followed Before Code Freeze

 Incorporate all modifications before a code freeze.


 Verify and resolve all types of defects prior to a code freeze.
 Verify if no new errors are introduced after any code changes.
 Complete security testing before code freeze.
Code walkthrough

Code walkthrough is an informal process of code review.

A code walkthrough is primarily a review meeting initiated by the code author. He reads through the code in
this meeting and other team mates ask questions, point out the coding errors and wherever code standards
are not followed.

The author of the code leads a code walkthrough meeting and other team members attend it. There is no
requirement of a moderator in this meeting. It is an open-ended discussion and there is not much focus on
documentation. In short, a code walkthrough is a type of peer review and forms a part of the static testing.
No formal review process is followed here.

The advantages and purpose of code walkthrough are listed below −

 It is an informal approach of finding errors in the code.


 It enables all the team members to gather together and have a common understanding of the code,
thereby increasing the collaboration and cooperation among all.
 It allows gathering of multiple feedbacks and open interactions among the team members.

The disadvantages of code walkthrough are listed below −

 There may be defects in the sections of the code which are not discussed in the walkthrough meeting.
 It takes a lot of time to conduct it.
 As the author himself leads the meeting, there is no guarantee to the fact that what is being discussed
actually matches with code.
Code Inspection

The code inspection is done to review the code of the software and detect errors in it. It reduces the
probability of fault multiplication and defects being detected at the later stages of SDLC by streamlining the
bug identification procedures. Thus code inspection is a part of code review.

How Does the Code Inspection Work?

The moderator, author, reader, and recorder forms a part of the code inspection team. All relevant
documents are made available to this team to plan for the future course of actions in this regard. If the
inspection team is unaware of the project, the author gives an introduction of the project and the outline of
code to the inspection team.

The inspection team then checks every piece of code as per the inspection checklists. Once inspection has
been completed, the inspection team informs the findings of the reviewed code to the respective team
members.

Why is Code Inspection Done?

 It detects faults in the software code.


 It identifies if there are any needs for process improvements.
 It validates if the correct coding standards are followed in the project.
 It involves peer review of the code.
 It records and documents all the bugs in the code.

Advantages of Code Inspections

 It is done to enhance the software quality.


 It identifies bugs in the software code.
 It suggests various process improvements in the project.
 Educates the team how to leverage from past mistakes.
 It detects inefficiency in the code and project.

Disadvantages of Code Inspections

 It is a time-consuming process.
 It requires extensive planning and execution.

What are the Code Inspection Checklists?

 If the code is readable.


 If the code is maintainable.
 If there is efficient coding.
 If the code is incorporating all the software requirements.
 If the code has been created keeping in mind all the security features.
 If the code has the correct formatting, indentions, comments etc.
 If the code has been unit tested.
 If the code is as per the standards.
 If the code has all the relevant documentations and references.

The code inspection checklists followed in various projects, and organizations may differ from one another
based on the multiple factors. Also, the checklist items for code inspections are revisited frequently to
incorporate new changes. They assist the inspection procedure but not a replacement for human code review
and knowledge.
The errors that are generally detected during the code inspections are listed below −

Data Errors − Some of the data errors are −

 The variables are not initialized correctly before actually using them.
 The constants have no proper names.
 There is buffer overflow.

Control Errors − Some of the control errors are −

 The conditions in the conditional statements are not correct.


 The loop is not ending correctly.
 All the code snippets do not correct brackets.

Input/Output Errors − Some of the input/output errors are −

 All the input variables remain unutilized.


 All the output variables are not assigned values.
 Some of the input values get corrupted.

Interface Errors − Some of the interface errors are −

 The methods and functions do not have proper parameters.


 The formal and actual parameters are not matching.
 The parameters are not appearing in the correct sequence.
 The parameters are not sharing the same memory structure.

Exceptional Errors include all other error conditions which may appear in the software.

Difference between Code Walkthrough and Inspection

Sr.No Code Walkthrough Inspection


1 It is an informal process. It is a formal process.
2 It is led by the code author. It is conducted at the project level.
A group of specific team members from various
The team members of the same project take
3 projects in the department take part in the code
part in the code walkthrough meetings.
inspection meetings.
No checklist is available to find defects in A collection of checklists are followed to find defects in
4
the code. the code.
It includes an overview of the code, no It includes an overview of the code, a thorough
5
preparation, review, and follow up. preparation, review, and follow up.
6 No formalized technique is followed. Formalized techniques are followed.
It takes less time since there are no checklist
It takes more time since all the checklist items need to
7 items that need to be covered in the
be covered in the meeting.
meeting.
It is a planned meeting with each member assigned with
8 It is totally unplanned.
a defined set of roles and responsibilities.
The author reads through the code and the The reader reads through the code and everyone goes
9
team members find the defects in the code. through it and finds the defects there.
The author records all the defects and The recorder records all the defects encountered in the
10
feedback received in the code. code.
11 There is no moderator. The moderator ensures that the discussions are
conducted effectively in the meeting.

You might also like