Software technical review

Software technical review

A software technical review is a form of peer review in which "a team of qualified personnel ... examines the suitability of the software product for its intended use and identifies discrepancies from specifications and standards. Technical reviews may also provide recommendations of alternatives and examination of various alternatives" (IEEE Std. 1028-1997, "IEEE Standard for Software Reviews", clause 3.7).

"Software product" normally refers to some kind of technical document. This might be a software design document or program source code, but use cases, business process definitions, test case specifications, and a variety of other technical documentation, may also be subject to technical review.

Technical review differs from software walkthroughs in its specific focus on the technical quality of the product reviewed. It differs from software inspection in its ability to suggest direct alterations to the product reviewed, and its lack of a direct focus on training and process improvement.

The term formal technical review is sometimes used to mean a software inspection.

Objectives and participants

The purpose of a technical review is to arrive at a technically superior version of the work product reviewed, whether by correction of defects or by recommendation or introduction of alternative approaches. While the latter aspect may offer facilities that software inspection lacks, there may be a penalty in time lost to technical discussions or disputes which may be beyond the capacity of some participants.

IEEE 1028 recommends the inclusion of participants to fill the following roles:

The Decision Maker (the person for whom the technical review is conducted) determines if the review objectives have been met.

The Review Leader is responsible for performing administrative tasks relative to the review, ensuring orderly conduct, and ensuring that the review meets its objectives.

The Recorder documents anomalies, action items, decisions, and recommendations made by the review team.

Technical staff are active participants in the review and evaluation of the software product.

Management staff may participate for the purpose of identifying issues that require management resolution.

Customer or user representatives may fill roles determined by the Review Leader prior to the review.

A single participant may fill more than one role, as appropriate.

Process

A formal technical review will follow a series of activities similar to that specified in clause 5 of IEEE 1028, essentially summarised in the article on software review.


Wikimedia Foundation. 2010.

Игры ⚽ Нужно решить контрольную?

Look at other dictionaries:

  • Software peer review — In software development, peer review refers to a type of software review in which a work product (normally some form of document) is examined by its author and one or more colleagues, in order to evaluate its technical content and… …   Wikipedia

  • Software audit review — A software audit review, or software audit, is a type of software review in which one or more auditors who are not members of the software development organization conduct An independent examination of a software product, software process, or set …   Wikipedia

  • Software review — A software review is A process or meeting during which a software product is [examined by] project personnel, managers, users, customers, user representatives, or other interested parties for comment or approval .IEEE Std. 1028 1997, IEEE… …   Wikipedia

  • Software walkthrough — In software engineering, a walkthrough or walk through is a form of software peer review in which a designer or programmer leads members of the development team and other interested parties through a software product, and the participants ask… …   Wikipedia

  • Software prototyping — Software prototyping, a possible activity during software development, is the creation of prototypes, i.e., incomplete versions of the software program being developed.A prototype typically simulates only a few aspects of the features of the… …   Wikipedia

  • Technical analysis software — automates the charting, analysis and reporting functions that support technical analysts in their review and prediction of financial markets (eg. the stock market). Description of Technical Analysis Software FeaturesThe following are descriptions …   Wikipedia

  • Technical architecture — is one of several architecture domains that form the pillars of an enterprise architecture or solution architecture. It describes the structure and behaviour of the technology infrastructure of an enterprise, solution or system. It covers the… …   Wikipedia

  • Technical writing — Technical writing, a form of technical communication, is a style of formal writing, used in fields as diverse as computer hardware and software, chemistry, the aerospace industry, robotics, finance, consumer electronics, and biotechnology. Good… …   Wikipedia

  • Software studies — is an academic research field which studies software systems and their cultural effects.OverviewSoftware studies is interdisciplinary, approaching software both as a technical artifact and from perspectives of the humanities and social sciences… …   Wikipedia

  • Software testing — is an empirical investigation conducted to provide stakeholders with information about the quality of the product or service under test [ [http://www.kaner.com/pdfs/ETatQAI.pdf Exploratory Testing] , Cem Kaner, Florida Institute of Technology,… …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”