Technology and Engineering Atlas

How Things Are Built
Sign In
Text size
100%
Theme
Group

Software Requirements and Architecture Practices

Practices for specifying, modeling and structuring software systems so that they meet their requirements. A member belongs here when the cited article describes it as a software requirements, architecture or modeling practice. The group is one of the groupings under this field in the Technology Atlas, and each member keeps its own entry with its own cited sources and its own place in the field. Its members appear in the Browse By view for the field, so a reader can move from this group to each member entry and to the sources cited there.

Browse By
Software Requirements and Architecture Practices
Filter Results11 entries
Sources
Non-functional requirement (Wikipedia)
Has Member: Non-functional requirement, Introduction
Quote, Has Member: Non-functional requirement, Introduction
In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours.
View the Source
Functional requirement (Wikipedia)
Has Member: Functional requirement, Introduction
Quote, Has Member: Functional requirement, Introduction
In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a summary (or specification or statement) of behavior between inputs and outputs.
View the Source
Functional specification (Wikipedia)
Has Member: Functional specification, Introduction
Quote, Has Member: Functional specification, Introduction
A functional specification (also, functional spec, specs, functional specifications document (FSD), functional requirements specification) in systems engineering and software development is a document that specifies the functions that a system or component must perform (often part of a requirements specification) (ISO/IEC/IEEE 24765-2010).
View the Source
Enterprise architecture (Wikipedia)
Has Member: Enterprise architecture, Introduction
Quote, Has Member: Enterprise architecture, Introduction
Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data.
View the Source
Model-based systems engineering (Wikipedia)
Has Member: Model-based systems engineering, Introduction
Quote, Has Member: Model-based systems engineering, Introduction
Model-based systems engineering (MBSE) represents a paradigm shift in systems engineering, replacing traditional document-centric approaches with a methodology that uses structured domain models as the primary means of information exchange and system representation throughout the engineering lifecycle.
View the Source
Model-driven engineering (Wikipedia)
Has Member: Model-driven engineering, Introduction
Quote, Has Member: Model-driven engineering, Introduction
Model-driven engineering (MDE) is a software development methodology that focuses on creating and exploiting domain models, which are conceptual models of all the topics related to a specific problem.
View the Source
Configuration management (Wikipedia)
Has Member: Configuration management, Introduction
Quote, Has Member: Configuration management, Introduction
Configuration management (CM) is a management process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life.
View the Source
Fault tolerance (Wikipedia)
Has Member: Fault tolerance, Introduction
Quote, Has Member: Fault tolerance, Introduction
Fault tolerance is the ability of a system to contain the propagation of faults (e.g. failed transistor, shorted connector, intermittent data bus).
View the Source
Privacy by design (Wikipedia)
Wikipedia contributors, Wikimedia FoundationHas Member: Privacy by design, Introduction
Quote, Has Member: Privacy by design, Introduction
Privacy by design (PbD) is an approach to systems engineering initially developed by Ann Cavoukian and formalized in a joint report on privacy-enhancing technologies by a joint team of the Information and Privacy Commissioner of Ontario (Canada), the Dutch Data Protection Authority, and the Netherlands Organisation for Applied Scientific Research in 1995.
View the Source
Message-oriented middleware (Wikipedia)
Has Member: Message-oriented middleware, Introduction
Quote, Has Member: Message-oriented middleware, Introduction
Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems.
View the Source
Infrastructure as code (Wikipedia)
Has Member: Infrastructure as code, Introduction
Quote, Has Member: Infrastructure as code, Introduction
Infrastructure as code (IaC) is the process of managing and provisioning computer data center resources through machine-readable definition files, rather than via physical hardware configuration or interactive configuration tools.
View the Source
Comments (0)
No comments yet. Be the first to share a thought.
Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.