One doc tagged with "Complexity Risk"

Creating documentation to describe the software and its use.

Conducting systematic reviews of work done.

Using machines to perform repetitive tasks.

Managing and maintaining configuration settings of the software.

The practice of forecasting, planning, and managing the demand for resources to ensure that the best use is made of them.

Continuous observation and tracking of a system, team or person, perhaps with respect to performance, security or availability.

Ensuring backup systems are in place to prevent failure.

Writing software to meet a required feature.

Revising code to improve its structure without changing its behavior.

Implementing and adhering to specific standards and libraries.

Implementing and utilising specific tools in the development process.

Logging support issues and tracking their resolution.

Writing and running tests for individual units or components of the software.

Writing and running tests for individual units or components of the software.

Quantitatively evaluating the software against benchmarks along some defined dimension.

Testing to ensure the software performs well under expected workloads.

Testing to ensure new changes do not adversely affect existing functionality.

Ensuring the application is secure by identifying vulnerabilities.