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
Accept vs Except Jonathan Poland

Accept vs Except

To accept is to consent, to receive or to believe something. Except means “not including.” Accept: to consent, to receive,…

The GSA Process 150 150 Jonathan Poland

The GSA Process

The General Services Administration (GSA) is an independent agency of the United States government responsible for managing and supporting the…

Keep It Super Simple Jonathan Poland

Keep It Super Simple

Keep it Super Simple or Keep it Simple Stupid. The KISS principle is a design guideline that suggests that unnecessary…

What is Design Risk? Jonathan Poland

What is Design Risk?

Design risk refers to the potential negative consequences that a business may face as a result of problems or issues…

Environmental Issues Jonathan Poland

Environmental Issues

Human activities have caused many environmental problems that are harmful to ecosystems, quality of life, and health. These issues have…

Bias for Action Jonathan Poland

Bias for Action

Bias for action is a mindset or approach that emphasizes the importance of taking action quickly, without extensive thought or…

Go-To-Market Strategy Jonathan Poland

Go-To-Market Strategy

A go-to-market strategy is a plan that outlines how a business will introduce its products or services to the market…

Long Tail Model Jonathan Poland

Long Tail Model

The long tail refers to a business model that allows a large number of niche products or services to be…

Prototyping Jonathan Poland

Prototyping

A prototype is a preliminary version of something that is used to test and refine an idea, design, process, technology,…

Content Database

Search over 1,000 posts on topics across
business, finance, and capital markets.

Brand Management Jonathan Poland

Brand Management

Brand management is the process of creating, developing, and managing a brand in order to build brand equity and drive…

Types of Efficiency Jonathan Poland

Types of Efficiency

Efficiency refers to the relationship between the amount of input used to produce something and the amount of output that…

Technology 101 Jonathan Poland

Technology 101

Technology is an important component of every business, constantly reshaping entire industries. Keeping pace with new and emerging technology can…

Service Level Objective Jonathan Poland

Service Level Objective

An service level objective (SLO) is a standard used to measure the performance of a business or technology service. These…

Capital Improvements Jonathan Poland

Capital Improvements

Capital improvements are investments in new assets or the improvement of existing assets that are intended to provide a long-term…

Mass Marketing Jonathan Poland

Mass Marketing

Mass marketing, also known as mass media marketing, refers to a marketing strategy that involves using a single marketing message…

Sticky Information Jonathan Poland

Sticky Information

Sticky information is information that is difficult to transfer. This is an analogy that information that knowledge “sticks” to people,…

Analysis Paralysis Jonathan Poland

Analysis Paralysis

Analysis paralysis, also known as “paralysis by analysis,” is a phenomenon that occurs when individuals or groups become so focused…

Strategic Advantage Jonathan Poland

Strategic Advantage

A strategic advantage refers to a position that gives a company an edge over its competitors and makes it likely…