Software Code Change Peer Review Task

From GM-RKB
(Redirected from Code Review)
Jump to navigation Jump to search

A Software Code Change Peer Review Task is a software review task for a software code change.

References

2022

  • (Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/software_review Retrieved:2022-1-24.
    • A software review is "a process or meeting during which a software product is examined by a project personnel, managers, users, customers, user representatives, or other interested parties for comment or approval".[1]

      In this context, the term "software product" means "any technical document or partial document, produced as a deliverable of a software development activity", and may include documents such as contracts, project plans and budgets, requirements documents, specifications, designs, source code, user documentation, support and maintenance documentation, test plans, test specifications, standards, and any other type of specialist work product.

  1. ↑ IEEE Std . 1028-1997, "IEEE Standard for Software Reviews", clause 3.5

2021

  • (Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/Code_review Retrieved:2021-11-4.
    • Code review (sometimes referred to as peer review) is a software quality assurance activity in which one or several people check a program mainly by viewing and reading parts of its source code, and they do so after implementation or as an interruption of implementation. At least one of the persons must not be the code's author. The persons performing the checking, excluding the author, are called "reviewers".

      Although direct discovery of quality problems is often the main goal, code reviews are usually performed to reach a combination of goals:

      • Better code quality improve internal code quality and maintainability (readability, uniformity, understandability, etc.)
      • Finding defects improve quality regarding external aspects, especially correctness, but also find performance problems, security vulnerabilities, injected malware, ...
      • Learning/Knowledge transfer help in transferring knowledge about the codebase, solution approaches, expectations regarding quality, etc.; both to the reviewers as well as to the author
      • “Increase sense of mutual responsibility increase a sense of collective code ownership and solidarity
      • Finding better solutions generate ideas for new and better solutions and ideas that transcend the specific code at hand.
      • Complying to QA guidelines, ISO/IEC standards Code reviews are mandatory in some contexts, e.g., air traffic software, safety-critical software
    • The above-mentioned definition of code review delimits it against neighboring but separate software quality assurance techniques: In static code analysis the main checking is performed by an automated program, in self checks only the author checks the code, in testing the execution of the code is an integral part, and pair programming is performed continuously during implementation and not as a separate step.


2020

  • https://smartbear.com/learn/code-review/what-is-code-review/
    • QUOTE: ... Code Review, also known as Peer Code Review, is the act of consciously and systematically convening with one’s fellow programmers to check each other’s code for mistakes and has been repeatedly shown to accelerate and streamline the process of software development like few other practices can. There are peer code review tools and software, but the concept itself is important to understand. Software is written by human beings. Software is therefore often riddled with mistakes. To err is, of course, human, so this is an obvious correlation. But what isn’t so obvious is why software developers often rely on manual or automated testing to vet their code to the neglect of that other great gift of human nature: the ability to see and correct mistakes ourselves. ...

2018
Retrieved from "http://www.gabormelli.com/RKB/index.php?title=Software_Code_Change_Peer_Review_Task&oldid=894417"