Modular Design
A design approach that divides a system into smaller parts or modules that can be independently created, modified, replaced, or exchanged. Crucial for creating flexible, scalable, and maintainable systems.
166 topics found for:
“maintainable systems”
DDD
Domain-Driven Design (DDD) is an approach to software development that focuses on modeling the business domain and its logic. Essential for aligning software development with business needs and creating maintainable systems.
m12n
Numeronym for the word "Modularization" (M + 12 letters + N), dividing a system into separate, interchangeable modules that can be developed, tested, and maintained independently. Important for improving maintainability and scalability of systems.
Cruft
Redundant, outdated, or unnecessary code or design elements that accumulate over time in a system. Important for identifying and removing to maintain clean, efficient, and maintainable systems and interfaces.
Graceful Degradation
A design principle that ensures a system continues to function at a reduced level rather than completely failing when some part of it goes wrong. Crucial for enhancing system reliability and user experience in adverse conditions.
o11y
Numeronym for the word "Observability" (O + 11 letters + N), the ability to observe the internal states of a system based on its external outputs, facilitating troubleshooting and performance optimization. Crucial for monitoring and understanding system performance and behavior.
Postel’s Law
A principle stating that a system should be liberal in what it accepts and conservative in what it sends, meaning it should handle user input flexibly while providing clear, consistent output, similar to the principle of fault tolerance. Essential for designing robust and user-friendly interfaces that accommodate a wide range of user inputs and behaviors while maintaining reliability and clarity in responses.
SRE
Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems to create scalable and highly reliable software systems. Crucial for maintaining the reliability and efficiency of complex software systems.
Use Case
A detailed description of a system's behavior as it responds to a request from one of its stakeholders, often used to capture functional requirements. Essential for understanding and documenting how users will interact with a system to achieve their goals.
Scalability
The ability of a system, product, or process to handle increased loads or expand without compromising performance or efficiency. Essential for ensuring that products and systems can grow and adapt to increasing demands.
Fault Tolerance
The capability of a system to continue operating properly in the event of the failure of some of its components, ensuring that user experience is not significantly affected by errors or issues, similar to Postel's Law. Essential for designing reliable and resilient systems, such as a form that normalizes user input for compatibility rather than returning an error (e.g., unconstrained phone number format).
Middleware
Software that acts as an intermediary between different systems or applications, enabling them to communicate and function together. Crucial for integrating various components and ensuring seamless interaction within digital products.
d11n
Numeronym for the word "Documentation" (D + 11 letters + N), creating detailed records and instructions to support the development, use, and maintenance of systems or products. Crucial for ensuring users and developers understand and properly use the system or product.
Product Architecture
The structural design of a product, defining its components, their relationships, and how they interact to fulfill the product's purpose. Important for ensuring that a product is well-organized, scalable, and maintainable.
State Persistence
The ability of a system to maintain its state and data across sessions, ensuring continuity and consistency in user experience. Crucial for designing reliable and user-friendly systems that retain data and settings across interactions.
Application Architecture
The high-level structure of a software application, defining its components and their interactions. Essential for designing robust, scalable, and maintainable digital products.
Design System
A collection of reusable components, guided by clear standards, that can be assembled to build any number of applications, ensuring consistency and efficiency. Crucial for maintaining design consistency and efficiency across products.
Modularity
The degree to which a system's components may be separated and recombined, often used in the context of software or hardware design. Important for enhancing flexibility, reusability, and ease of maintenance in design.
Design Tokens
A system of design variables used to maintain consistency in a design system, such as colors, fonts, and spacing. Crucial for ensuring uniformity and scalability in design across different platforms and products.
Atomic Design
A methodology for creating design systems by breaking down interfaces into their basic components (atoms, molecules, organisms, templates, and pages). Essential for creating scalable and maintainable design systems.
HITL
Human in the Loop (HITL) integrates human judgment into the decision-making process of AI systems. Crucial for ensuring AI reliability and alignment with human values.
Flexibility-Usability Tradeoff
A principle stating that as the flexibility of a system increases, its usability often decreases, and vice versa. Crucial for balancing versatility and ease of use in design.
Error Handling
The process of anticipating, detecting, and resolving errors in software or systems to ensure smooth operation. Important for creating reliable and user-friendly software applications.
Platform Team
A team responsible for developing and maintaining the foundational systems and services that support other teams and products. Crucial for ensuring scalability and efficiency across the organization.
Soak Testing
A performance testing method that evaluates the system's behavior and stability over an extended period under a high load. Essential for identifying memory leaks and ensuring the reliability and performance of digital products under prolonged use.
Configuration Management
The process of handling changes to software, hardware, or documentation in a systematic way. Critical for maintaining consistency and ensuring system integrity.
3-Tiered Architecture
3-Tiered Architecture is a software design pattern that separates an application into three layers: presentation, logic, and data. Crucial for improving scalability, maintainability, and flexibility in software development.
DRY Principle
Don't Repeat Yourself (DRY) is a software development principle for reducing repetition and redundancy. Essential for creating efficient, maintainable, and scalable code in digital product design.
Sustainability
The practice of designing and implementing processes, systems, or business solutions in a way that ensures their long-term viability, efficiency, and maintainability. Crucial for creating durable and efficient designs that remain practical and effective over time, ensuring the ongoing success and feasibility of digital products and operations.
Big Data Engineer
A professional who designs, builds, and maintains systems for processing large-scale data sets. Essential for enabling data-driven decision-making and supporting advanced analytics in organizations.
Ethical AI Design
The practice of developing artificial intelligence systems that are fair, transparent, and respect user privacy and rights. Crucial for ensuring that AI technologies are developed responsibly and ethically.
Servicing
The process of maintaining, updating, and improving a product or system after its initial deployment to ensure its continued functionality, performance, and relevance to users. Crucial for ensuring long-term user satisfaction, product reliability, and adaptation to changing user needs and technological advancements.
Control Framework
A set of standards and guidelines used to ensure the integrity, security, and compliance of business processes and IT systems. Important for establishing robust governance and control mechanisms in digital product design and development.
Content Inventory
A comprehensive list of all content within a system, used to manage and optimize content. Essential for organizing, auditing, and improving content strategy.
Tesler’s Law
The principle stating that there is a limit to the amount of complexity that users can handle, and if designers don't manage complexity, users will. Crucial for designing user-friendly systems that manage complexity effectively.
Principle of Growth
The Principle of Growth is an information architecture guideline that plans for the future expansion and evolution of a system. Crucial for ensuring that information structures can scale and adapt over time.
Principle of Choices
The Principle of Choices is an information architecture guideline that emphasizes providing users with meaningful options to navigate and interact with a system. Crucial for enhancing user experience by ensuring users can easily find what they need without being overwhelmed.
Deployment Infrastructure
The hardware and software environment used to deploy and manage applications and services. Essential for ensuring reliable and scalable application deployment.
Structured Programming
A programming paradigm aimed at improving the clarity, quality, and development time of software by using structured control flow constructs. Essential for writing clear, maintainable, and efficient code in digital product development.
Component Library
A collection of reusable UI components that can be used to build applications. Helps in maintaining consistency and efficiency in the design and development process.
Production Environment
The setting where software and systems are actually put into operation for their intended use. Essential for ensuring that products are fully functional and meet user requirements in a real-world setting.
DSDM
Dynamic Systems Development Method (DSDM) is an agile project delivery framework focused on delivering business value early and continuously. Essential for ensuring that projects align with business goals and user needs through iterative processes.
Burn-In
The process of running a system for an extended period to detect early failures and ensure reliability. Important for ensuring the stability and performance of digital products before full-scale deployment.
Operational Risk
The risk of loss resulting from inadequate or failed internal processes, people, and systems. Important for identifying and mitigating potential operational threats.
Principle of Objects
The Principle of Objects is an information architecture guideline that treats content as living, distinct entities with behaviors and attributes. Crucial for creating modular, reusable, and flexible content structures.
Principle of Front Doors
The Principle of Front Doors is an information architecture guideline that acknowledges multiple entry points into a website or system. Crucial for ensuring that all entry points provide a coherent and navigable experience.
Interaction Modeling
The process of creating representations of how users will interact with a system, including the flow of interactions and the overall experience. Crucial for planning and optimizing user interactions and experience.
REST
Representational State Transfer (REST) is an architectural style for designing networked applications based on stateless, client-server communication. Essential for building scalable and efficient web services.
External Consistency
The degree to which a product's elements are consistent with external standards or other products. Important for ensuring compatibility and user familiarity across different systems.
c12s
Numeronym for the word "Communications" (C + 12 letters + S). Essential for effective collaboration and information exchange.
Interactive Design
The design of interactive digital products, environments, systems, and services. Crucial for creating engaging and user-friendly digital experiences.
Pattern Library
A collection of design patterns that provides solutions to common design problems. Useful for standardizing design solutions and promoting best practices across projects.
Native
Content or functionality that is built into a platform or device rather than being provided by an external application. Important for ensuring seamless integration and optimal performance.
Business Logic
The part of an application that encodes the real-world business rules that determine how data is created, stored, and modified. Crucial for ensuring that digital products align with business processes and deliver value to users.
Data Architect
A professional responsible for designing and managing data structures, storage solutions, and data flows within an organization. Important for ensuring efficient data management and supporting data-driven decision-making in digital product design.
Secondary Reinforcer
A stimulus that gains reinforcing properties through association with a primary reinforcer, such as money or tokens, which are associated with basic needs. Essential for understanding complex behavior reinforcement strategies and designing effective reward systems.
Server-Side
Operations and processes that occur on a server rather than on the user's computer. Important for handling data processing, storage, and complex computations efficiently.
360-Degree Customer View
A comprehensive view of a customer that includes data from all interactions and touchpoints across the customer journey. Crucial for delivering personalized experiences and improving customer satisfaction.
Breakpoint System
A structured set of breakpoints used to create responsive designs that work seamlessly across multiple devices. Important for maintaining consistency and usability in responsive design.
Grid System
A framework used in graphic and web design to organize content in a structured and consistent manner. Essential for creating balanced and readable layouts.