46 docs tagged with "Conceptual Guide"

After reading Secure Design Best Practices, architects who are part of a software development team may find this page useful as the weaknesses are

This document provides a guideline for tracking dependencies between architecture activities. A dependency exists when a specific activity needs to be executed before another activity can be executed or even started.

This document provides a guideline for structuring architecture documentation in the PAPCP R&D environment.

This guide describes how bugs – when they are created in Azure DevOps (ADO) – also are classified to ensure that they are handled with regards to their severity and potential impact.

This guide describes the procedure for monitoring, inspection and calibration of used test and measurement equipment. It is valid for the PAPCP REH instruments.

This guide describes the most fundamental parts of component capabilities. It also includes a flowchart of component capabilities updates and a list of attributes sometimes mistaken for component capabilities.

This guide provides a quick overview of component tests and when and how they should be used.

This conceptual guide explains the purpose of configuration audits and presents the main parts of a configuration audit and the high-level approach adopted in PCP.

This is the overall description of how to handle configuration release management within ABB PCP.

The quality dashboard can help teams measure and compare product quality by setting appropriate widgets and queries. A common template based on standardized queries will help save effort and improve efficiency.

Division testing (DT) is an optional testing stage carried out with ABB divisions (e.g., PAEN, PAPI, PADI) during the project if it is relevant to the respective product or system release.

Below is a short introduction to testing on different DMS link types. Use this page to take a look at how to get and how DMS links work. Before going to the DMS links URL, here are some tips for URL anatomy. For more details, please see the DMS documentation.

The term Document Management includes both Office files and wiki pages. While the general processes are the same – such as version control, review, and approval – the specific procedures for each type of document differ and are described in the relevant guides.

This guideline outlines how to organize and manage product and project documents during development and maintenance. It applies only to internal R&D documents at the product and project level, not for publication through the ABB Library or other channels.

<!---

This document provides guidance on how to handle interference-free product development for new products and for maintenance of existing products.

This guide provides an overview of Kanban and its application to software development teams.

R&D quality dashboards can be automatically created, based on Azure DevOps (ADO) data, to support the organization in visualizing project progress based on quality key performance indicators (KPIs).

The PCP System Epic Dashboard is used to visualize the implementation progress of system epics, by planning and tracking child epics and features whose completion is required to fulfill a given requirement.

This guides includes general information about performance testing and a brief description of different types of performance testing.

Product capabilities describe what the product “can do” for anyone who wants to understand its capabilities. They represent the product's property and are updated throughout its lifecycle through multiple releases.

This guide explains what a product issue number (PIN) is and how it is used within the PCP organization.

The product test verifies that the product to be released has acceptable quality. It applies to new products and maintenance/updates of existing products.

Key performance indicators (KPIs) are used within PCP R&D to better understand, control, and manage the organization.

References between artifacts (e.g., documents and web pages) support the user to find more information easily. It also ensures the same content isn't repeated in several places and can therefore simplify maintenance. But wrongly used, with too many references, the contents can be hard to read for the user and become costly to maintain.

Software architecture is not a static document, instead, it's a continuous iterative process throughout each increment. This guide serves as a reference for the roles providing and describing different levels of architecture.

A regression bug is a bug that causes a completed feature that worked correctly to stop working after updates (e.g., system upgrade, system patching, or bug fixes). This definition applies both before and after releasing the feature to customers.

This guide provides insights and definitions for the various release stages of a component, function, product, or system.

This guide describes how system requirements in Decision Focus are broken down into system epics, epics and features in Azure DevOps (ADO).

This guide describes how Scrum can be used by teams to manage their work. Scrum is a framework that implements the principles of Agile as a concrete set of artifacts, practices, and roles.

This chapter gives some basic best practices for a secure software design. Assessing how security is addressed in the design of a product is one important step to ensure that the product meets the best security level and can be done at various points in a product lifecycle.

This guide gives an overview of the software artifact model which describes the relationship between artifacts used in software development.

This guide describes different types of software vulnerabilities and associated threats. It also describes various defense mechanisms that are typically needed to be prepared for software attacks.

Static source code analysis is a method for analyzing the source code without executing it. This guide provides relevant information about static code analysis within PCP R&D.

The PCP R&D Processes style guide offers recommendations on writing and formatting text for web pages, PPTs and documents.

After reading Secure Design Best Practices, this page describes some weaknesses around concepts that are frequently used or encountered in software development environments. This includes all aspects of the software development lifecycle including implementation.

This guide describes what system interfaces are, how they are documented, and how they are managed.

The system test is a crucial step in the development process as it integrates and tests deliverables from the various development streams.

This guide gives an overall view of the test performed before a component, container, product, or system is released.

This guideline briefly describes test techniques used at the different test levels. Each project defines the test levels and when to use the various test techniques.

This guide gives an overview of what a unit test is, and when and how it should be used.

This guide provides valuable tips to anyone involved in creating unit tests. A good unit test should be easy to understand, reliable, quick to run, and without dependencies.

This guide describes the what, why, and how related to the versioning of architecture documents.

This guide describes the different states of Azure DevOps (ADO) work items. Consistent work item state transitions are essential to enable consistent follow up on status.

The traceability of the work items shows the relationship between them in Azure DevOps (ADO).

This guide describes traceability between work products that are not in Azure DevOps (ADO).