Technical Requirements

Technical Requirements

Technical Requirements Jonathan Poland

Technical requirements are specifications for a technology such as a system or application. It is common to define technical requirements with commanding verbs such as will, shall and must. Technical requirements are an opportunity to communicate business expectations for the end-to-end operational quality of a technology. As such, it can be a bad idea to fully delegate them to implementors, although they should certainly contribute. Technical requirements are typically designed to be smart. In many cases, technical requirements are specified at several levels of detail. For example, an initial requirement for a “flat structure” for a user interface may be later expanded with detailed specifications of screen flows and navigation.

Availability

The system will maintain availability of 99.99%.

Reliability

The system will maintain a mean time between failures of greater than 60 days.

Performance

The system will have an average page load time of less than 2 seconds.

Throughput

The system will handle 1,000 concurrent users while meeting performance objectives.

Standards

The system will comply with our architectural and security requirements with links to relevant standards.

Authentication & Authorization

The system will conform to our policy for authentication and authorization with links to relevant standards.

Serviceability

Changes and upgrades to the system will not require total outages.

Maintainability

Logging will be sufficient to quickly identify and resolve system problems with a mean time to repair of less than one hour for high severity incidents.

Accessibility

All videos will have accurate closed captioning.

Privacy

The user interface will not allow employees to view customer birth dates stored in the customer database.

Human Error

The system will detect when a price entered by a user is more than 10% from the realtime market price. This will result in a confirmation screen that warns the user of the discrepancy.

System Errors

System errors will result in an error code that will be communicated to the user. This code will be well documented in the help desk system to expedite support and incident resolution.

Information Security

User credentials and all personally identifiable information will be encrypted in storage and transit.

Audit Trail

Access to the database will result in logs including a high priority alert that is triggered for sensitive operations such as a database dump.

Internal Controls

The only persons that will have access to the decryption keys for customer data will be officially designated as data stewards. Data stewards will be prohibited from accessing databases and will not be given the authorizations required to do so.

Data

Customer data will be sourced from the customer database without permanently storing these fields in the billing system.

Data Migration

Historical customer invoices will be accurately migrated to the new system and will be viewable from the customer invoice screen.

Data Quality

The data migration will confirm that the billing rate is accurate for every customer.

Usability

Users will be able to permanently turn off each individual smart feature from the user preferences menu.

Productivity

Sales people will be able to generate a quotation using a single screen. It will be possible to regenerate the quotation without entering all fields again.

Structure

The sales system will have a flat hierarchy of screens whereby no screens are at a depth of greater than 3.

Interoperability

The website will work on all major operating systems, devices and browsers as specified in the current customer technology requirements [link to this document].

Vendor Lock-in

The system will be based on custom code and open source without any dependency on proprietary technologies.

Loose Coupling

The system will continue to fully function when the billing API is down with the exception of any functions that depend on uncached data from this API.

Transitional Requirements

The old billing system will remain fully operational for a period of 3 months after the launch as a reference that can be used to confirm the correctness of calculations, user interfaces and migrated data.

Learn More…

Customer Dissatisfaction Jonathan Poland

Customer Dissatisfaction

Customer dissatisfaction refers to a customer’s negative evaluation of a product or…

Supplier Risk Jonathan Poland

Supplier Risk

Supplier risk refers to the risk that a supplier will not fulfill…

Digital Maturity Jonathan Poland

Digital Maturity

Digital maturity refers to an organization’s ability to effectively utilize information technology…

Operations 101 Jonathan Poland

Operations 101

Business operations refer to the processes and activities that are involved in…

Performance Improvement Plan Jonathan Poland

Performance Improvement Plan

A performance improvement plan (PIP) is a formal document that outlines specific…

Ease of Use Jonathan Poland

Ease of Use

Ease of use refers to the usability of a product, service, tool,…

Managing Expectations Jonathan Poland

Managing Expectations

Managing expectations is the practice of communicating information to prevent gaps between…

Customer Acquisition 101 Jonathan Poland

Customer Acquisition 101

Customer acquisition is the process of acquiring new customers for a business…

Operational Efficiency Jonathan Poland

Operational Efficiency

Operational efficiency can be defined as the ratio between the inputs to run a business and the output gained from the business. It is primarily a metric that measures the efficiency of profit earned as a function of operating costs.

Jonathan Poland © 2023

Search the Database

Over 1,000 posts on topics ranging from strategy to operations, innovation to finance, technology to risk and much more…

Marketing Technologies Jonathan Poland

Marketing Technologies

Marketing technology, or “martech,” refers to the tools and software used to…

Product Extension Jonathan Poland

Product Extension

Product extension is the practice of introducing new products or product lines…

Data Infrastructure Jonathan Poland

Data Infrastructure

Data infrastructure refers to the hardware, software, and network resources that support…

What are Finished Goods? Jonathan Poland

What are Finished Goods?

Finished goods are products that have completed the manufacturing process and are…

Collective Intelligence Jonathan Poland

Collective Intelligence

Collective intelligence refers to the ability of a group to solve problems,…

What is a Business Model? Jonathan Poland

What is a Business Model?

A business model is a plan or framework that outlines how a…

Bliss Point Jonathan Poland

Bliss Point

The concept of a “bliss point” refers to the amount of consumption…

Algorithms Jonathan Poland

Algorithms

An algorithm is a set of instructions or rules that are followed…

Lifetime Customer Value Jonathan Poland

Lifetime Customer Value

Lifetime customer value (LCV) is a measure of the total value that…