Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Code review

Related Topics

In the News (Sat 25 May 19)

  Source Code Review Guidelines
At reviews beyond the first, copies of the diffs and the minutes of all previous meetings should be available, along with a full copy of the current code.
Code on the firewall should attempt not to dump core if it might have sensitive data in memory that could be retrieved.
The GNU Coding standards are a set of coding standards that produce some of the consistently best code that is freely available.
www.homeport.org /~adam/review.html   (3842 words)

 Code Inspection / Review - QA Forums
A good code review checklist should be present in the meeting and should be followed so that a variety of problems are kept in mind and looked for.
Granted, part of the review is looking for the adherence to coding standards but one has to realize these are, by nature, critical meetings ("critical" in the sense of criticism) and thus some people skills come into play here in terms of focusing on the issue and not the person.
Reviewers cannot just review a piece of code, they need to know at least what the design is and how it fits into the rest of the system.
www.qaforums.com /Forum15/HTML/003455.html   (993 words)

 Code Review FAQ
Code review is our basic mechanism for validating the design and implementation of patches.
A review is focused on a patch's design, implementation, usefulness in fixing a stated problem, and fit within its module.
Checking code in seems to cause a psychological effect that the patch is done, it's time to go on to the next thing, and requested changes are new and extra work.
www.mozilla.org /hacking/code-review-faq.html   (2713 words)

 Code Review Protocol
Reviewers are assigned roles in peer code reviews.
If the code is complex the leader may choose to have a half hour informational session some time before the actual peer review session where the author of the code provides a high level detail or the code and is available for questions.
Optional reviewers are selected to participate in the review session because of their knowledge of the subject matter or expertise in the type of code to be reviewed.
usfweb2.usf.edu /ora_ban/pdprocess/codereview/codereviewpolicy.html   (1345 words)

 A Case for Code Review
The primary reviewer would then be tasked with keeping the review focused, making sure that all issues were sufficiently covered, that each reviewer and the implementor had opportunity to state opinions, facts, observations, what-have-you.
The code review is meant to guarentee successful completion of the coding task, not to define or write the code, that’s the responsibility (and authority) of the implementor.
Review the review process constantly, the introduction of a new team member is the ideal opportunity.
www.gamasutra.com /features/20000314/stenersen_pfv.htm   (5956 words)

 Honor Code Review Committee Report
The Honor Code Review Committee recommends that the jurisdictions of the Student Judicial Council and the Judicial Review Board be combined into a single Academic Judicial Board that would hear all cases of alleged academic dishonesty.
The Honor Code Review Committee proposes that the manner in which first-year students are introduced to the honor code be changed to emphasize its importance.
To further stress the honor code as well as to educate students on the difficult topic of plagiarism, the Committee recommends that issues of academic honesty be addressed in all first-year seminars, preferably in a standardized format developed for the seminar program.
www.middlebury.edu /academics/honorcode/report.htm   (2445 words)

 Security Code Review   (Site not responding. Last check: 2007-10-08)
You must ensure that code reviews are an integral part of your development cycle, and be aware that they will only be as effective as the amount of resources and budget allocated.
The review goal is to identify as many potential security vulnerabilities as possible before the code is deployed, since the cost and effort required to fix security flaws at development time is far less than fixing them later in the product deployment cycle.
Security code reviews are similar to regular code reviews or inspections except that the focus is on the identification of coding flaws that can lead to security vulnerabilities.
msdn.microsoft.com /library/en-us/secmod/html/secmod94.asp?frame=true   (9682 words)

 Macadamian code review checklist for software developers, software test, software QA, software managers
If you don't, the review may not be complete, or the code may not be well commented.
Code accessing the variable should be enclosed with the same mechanism.
Code that is replicated in more than one function should be put in a helper function for easier maintenance.
www.macadamian.com /codereview.htm   (1611 words)

 AEP Practices
A code review is the process where the developers and the architect meet and discuss code.
The purpose of code reviews is to exchange ideas about how the code is written and to establish a standard group interpretation of the code.
When this occurs, groups usually decide that code reviews are not valuable, drop code reviews from their development process, and lose the potential benefits that can stem from a correctly implemented code review.
www.parasoft.com /jsp/aep/aep_practices.jsp?practice=CodeReview   (214 words)

 Code Review   (Site not responding. Last check: 2007-10-08)
Measure the quality of code produced during the Code Development stage and provide these measures (number of defects, type of defect, cause of defect, etc.) back to the project manager so that the progress of the project can be tracked and appropriate planning changes made.
The review process is used to uncover defects in code which would be difficult or time consuming to detect merely by execution of the component.
Reviews are ideal vehicles for inspecting code for conformance with coding standards and design documents, which would be difficult to detect through unit testing.
www.cc.gatech.edu /classes/cs8113h_96_spring/process/Code_Review.html   (310 words)

 Mozilla Code Review and the super-reviewer list
This review is done by one or more of a designated group of strong hackers, known as reviewers@mozilla.org.
This is necessary because mozilla.org does not require a separate design review prior to code review; instead, we expect hackers to talk about their designs, post specs or less formal blurbs about their intentions, and take feedback throughout the (usually non-linear) design/implementation process.
This mail/news setup exists so extra reviewers and interested observers can watch requests for review and responses from reviewers (although typically, positive responses from reviewers will be given via bugzilla comments rather than using a message to the newsgroup).
www.mozilla.org /hacking/reviewers.html   (2032 words)

To prepare the Code for formal adoption, staff will utilize the Five Step Process adopted by the City Council to be used for all code adoptions.
The City of Phoenix is currently accepting proposed code change submittals to be considered during staff review of the codes.
The second component of the staff review will be to review each code change submittal and incorporate the proposed change into the code according to current ordinances, interpretations and practice.
www.ci.phoenix.az.us /fire/fp_adopt.html   (626 words)

 Code Review Procedure   (Site not responding. Last check: 2007-10-08)
During the code review cycle, the Technical Advisory Groups (TAGs) are responsible for preparing a technical analysis and comparison of codes to assist the Council in adoption of codes.
Report all model code requirements that differ from the current state code and identify any requirement that is not contained in the current state code, following the procedure outlined below.
Examine the model codes chapter-by-chapter and compare the model code requirements to current state code requirements, using the current state code as the base document.
www.sbcc.wa.gov /docs/tagrevew.html   (305 words)

 PST Code Review Checklist
The success of the review is highly dependent on the code reviewers thoroughness and diligence in reviewing the packet.
The code reviewer must produce a list of all major areas that need to be addressed by the developer.
The reviewers should OPR comment the problem areas to be addressed by the developer and also document the fact that a re-review is desired.
www.pst.stsci.edu /guidelines/code_review_guidelines.html   (700 words)

 Code Reviewer   (Site not responding. Last check: 2007-10-08)
Everyone agrees that peer code review uncovers bugs, makes code more standard and maintainable, and promotes learning and sharing.
CodeReviewer is the only peer code review tool with support for multiple remote reviewers, automated audit trails, SCM integration, and custom reviewer checklists.
Reviewers usually don't verify that problems were fixed.
www.codehistorian.com /codereviewer-overview.php   (196 words)

 CSDL Code Review Process
In general, it is preferable to limit the amount of code to be reviewed to less than half a dozen classes, although you should use your best judgment.
In addition to listing the files to be reviewed and their location, please provide a list of your "burning questions" regarding this code.
In the 24 hours between the time of the announcement and the actual review meeting, all of the participants in the review (including the author(s)) should read the code and prepare for the meeting.
csdl.ics.hawaii.edu /FAQ/software-review.html   (1215 words)

 Michael Swanson's Blog : Code Review and Complexity
Of course, the primary reason we formally review code is to subjectively comment on other possible ways to accomplish the same functionality, simplify its logic, or identify candidates for
After a very productive code review meeting that produced many good suggestions, the original author of this method was able to re-approach the problem, simplify the design, and refactor a good portion of the logic.
It is difficult to tell a person after he or she wrote 10000 lines of code that it is not good and has to be reimplemented.
blogs.msdn.com /mswanson/articles/154460.aspx   (2148 words)

 Application Security, Code Review   (Site not responding. Last check: 2007-10-08)
We consider the number of lines of code, language, site complexity, types of interaction with external systems, numbers of roles, type of business, and several other factors in determining an estimate.
Once the project is approved and under an NDA, we arrange to securely transfer the code to our labs, either via physical carrier (e.g., U.S. Mail, Fedex), posting an encrypted archive to our secure server, or by e-mailing us an encrypted archive (using PGP or some other file encryption mechanism).
We may contact you during the review if we identify a serious problem in an operational application, or if we have questions about how something in the code is supposed to work.
www.aspectsecurity.com /code.html   (504 words)

 Smart Bear Software   (Site not responding. Last check: 2007-10-08)
Jul 29, 2005 — Smart Bear has released Code Reviewer v3.1.
CodeCollaborator enables peer review of source code changes before or after files are checked into version control.
Whether you're interested in efficient, effective peer code reviews, software metrics reporting, or change analysis, our software will save you time and make your processes more accurate, repeatable, and reportable.
www.codehistorian.com   (212 words)

 Building Code Review
The Building Code review is taking place in consultation with industry, government and consumer representatives.
Workshops were held in 2004 and 2005 for people to share their views about the buildings they use.
The review will ensure that performance criteria in the Building Code are in line with the Act, and take into account people’s expectations.
www.building.govt.nz /publish/codreview.php   (131 words)

 C# code review checklist
With two successful.NET applications already live, he is working as the lead developer on a commercial Windows Forms application that deployed on schedule to a worldwide audience in June.
Discussion of "how" should be in blocks or in-line with the code in question.
During a code review, all these items are checked, supposedly capturing the vast majority of mistakes.
weblogs.asp.net /tgraham/archive/2003/12/19/44763.aspx   (981 words)

 use Perl | Code Review Ladder Mailing List
Simon Cozens writes "I've been threatening to do it for a while, but now I've caved in, and set up the code review ladder mailing list." This list is for reviewing Perl code, and posting Perl code to be reviewed.
The idea behind the mailing list is that you can post your code to be reviewed, and if you get good feedback, you ought to feel some kind of moral obligation to help the next guy along.
People were posting there code for review for long time.
use.perl.org /article.pl?sid=03/09/01/2138209   (828 words)

 Java Code Review: JStyle (Man Machine Systems)
Although dynamic testing is a necessary step during the testing phase, code review (also called code audit) conducted prior to dynamic testing can reveal code/design deficiencies and has been reported to save upto 70% test effort in some cases.
is an automated Java code review tool which knows about important Java coding guidelines practiced widely by expert Java developers, and can quickly apply these to any Java code.
A major advantage of JStyle is that a team can customize the Java coding guidelines to be enforced during code inspection, and can plug-in newer guidelines if necessary.
www.mmsindia.com /jstyle.html   (244 words)

 Compuware DevPartner for Visual C++
Users can automatically locate coding errors, measure detailed execution performance and track what lines of code have been executed during the testing of their application.
Code coverage aids developers in building reliable code by automatically tracking and measuring application execution.
With the optional DevPartner Studio Server license, code coverage is collected across distributed machines.
www.compuware.com /products/devpartner/1592_ENG_HTML.htm   (350 words)

 Gamasutra - Features - "A Case for Code Review" [03.14.00]
Actually, let me broaden the answer somewhat.  Any of the discussion about code review can easily be applied to the design review process, they really work hand in hand.  In fact, its difficult for me to conceive one without the other.
What do you mean show people my code?  What do you mean no more code ownership?  How am I going to know to who blame for all these bugs?
The code review forum also provides an ideal learning environment.  Where do programmers today go to learn new tricks, refine their methods, test their prowess, and grow their skill?  Primarily its through individual effort, i.e.
www.gamasutra.com /features/20000314/stenersen_01.htm   (338 words)

 Code Review
A review of all code related to CompleteSource, focusing on performance, architecture, supportability and maintainability with future versions of CompleteSource.
List of feature use - the purpose is to identify the key features providing a framework for continuing to phase two of the review.
Where to limit columns returned by queries to those required for dependent logic or presentation within the given template.
www.moai.com /services/code_review.asp   (132 words)

 Code Review Terminology
In the shower this morning, it occurred to me it would be useful to write a guide listing certain words and phrases that arise during code reviews and their actual, candid meanings.
Hopefully this will help the communication process at technical reviews.
Review term or phrase Real Meaning --------------------- ------------ I'm not sure this fits in If I have anything to do with our architecture.
www.elsop.com /wrc/humor/coderev.htm   (244 words)

 DaVinci Code Review (logicalrealism.org)   (Site not responding. Last check: 2007-10-08)
Dan Brown's most recent novel, The DaVinci Code, has gotten a lot of attention of late.
Having just finished it, I'd have to say "not really." It's a good read, reasonably well researched, but not worth all of the fuss it has caused.
You had better pay it back quick to promote the good news of Yahshua HaMashiach, or God will hold you accountable at your judgement for leading His children into the hands of the enemy.
www.logicalrealism.org /archives/267   (2004 words)

 code-review-ladder Info Page   (Site not responding. Last check: 2007-10-08)
This is a list for posting and reviewing Perl code for style, efficiency, and so on.
If someone reviews your code, please review someone else's.
To see the collection of prior postings to the list, visit the code-review-ladder Archives.
lists.netthink.co.uk /listinfo/code-review-ladder   (265 words)

Try your search on: Qwika (all wikis)

  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.