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.
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.
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.
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.
Model-View-Controller (MVC) is an architectural pattern that separates an application into three main logical components: the Model (data), the View (user interface), and the Controller (processes that handle input). Essential for creating modular, maintainable, and scalable software applications by promoting separation of concerns.
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.
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.
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.
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.
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.
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.
A programming paradigm that uses objects and classes to structure software design, promoting reusability and scalability. Crucial for developing maintainable and scalable software systems.
The process of anticipating future developments to ensure that a product or system remains relevant and functional over time. Essential for designing durable and adaptable products.
New Product Development (NPD) is the complete process of bringing a new product to market, from idea generation to commercialization. Essential for companies to innovate, stay competitive, and meet evolving customer needs through a structured approach to creating and launching new offerings.
Minimum Marketable Feature (MMF) is the smallest set of functionality that delivers significant value to users and can be marketed effectively. Crucial for prioritizing development efforts and releasing valuable product increments quickly, balancing user needs with business objectives.
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.