Tagged articles
non-functional requirements
27 articles · Page 1 of 1
This article presents a comprehensive software design methodology spanning strategic design (bounded contexts, domain partitioning, architectural style selection), tactical design (functional and non-functional modeling), structural modeling (class responsibilities, package structure), behavioral modeling (sequence diagrams, state machines), and DFX (design for performance, reliability, cost) — with concrete code examples and real-world failure patterns.
Bounded ContextCircuit BreakerSaga pattern
0 likes · 34 min read

The author shares a 15-step AI-assisted workflow for code quality control, starting with spec-driven development, automated skills for code review, regression checks, test data rehearsal, non-functional requirements validation, mandatory manual review, and optional security/extensibility checks, all orchestrated via AI-written skills and git integration.
AI-assisted developmentGit workflowautomated code review
0 likes · 6 min read

The article argues that excellent software design requires anticipating non‑functional issues—such as sudden database load, traffic spikes, or third‑party timeouts—by implementing retries, degradation, monitoring, and boundary checks early in the design phase, and by isolating core modules, exemplified by a micro‑service per payment channel architecture.
core module protectionmicroservicesnon-functional requirements
0 likes · 4 min read

The article outlines seven typical challenges that software developers face when moving into an architect role, such as over‑focusing on technical details, neglecting non‑functional requirements, poor communication with diverse stakeholders, and failing to design for failure, and suggests deliberate practice to address each issue.
career transitioncommunicationnon-functional requirements
0 likes · 8 min read

This article categorizes architectural characteristics (non-functional requirements) into four groups—operational, structural, cloud-native, and cross-cutting—detailing key attributes like availability, scalability, extensibility, security, and legal compliance to help architects build a systematic understanding of quality attributes that drive architectural decisions.
Cross-cutting Concernsarchitectural characteristicscloud native
0 likes · 8 min read

This article introduces software architecture through its etymology and the software crisis, then defines four interconnected dimensions—architecture characteristics, logical components, architecture style, and architecture decisions—that together form a complete architectural picture, using examples like database selection and e-commerce components to illustrate trade-offs.
architecture characteristicsarchitecture decisionsarchitecture style
0 likes · 9 min read

The article argues that in organizations, especially among developers, grounding daily work in solid theoretical frameworks—such as design patterns, SOLID principles, and non‑functional requirement models—enables faster, higher‑quality outcomes and guides long‑term strategic growth, whereas relying solely on ad‑hoc experience leads to inefficiency and technical debt.
R&D managementnon-functional requirementspractice
0 likes · 4 min read


21CTOApr 14, 2024 · Fundamentals
This reflective essay shares eight practical insights on software architecture—from the challenge of asking the right questions and deciding what not to build, to the pivotal role of non‑functional requirements, risk‑first design, and the paradox of simplicity—offering engineers actionable guidance for better architectural decisions.
continuous codingnon-functional requirementsrisk management
0 likes · 13 min read

This article outlines a comprehensive methodology for system architecture design, covering principles, three development stages—preparation, conceptual, and detailed design—along with techniques for requirement structuring, constraint analysis, key quality and functionality determination, and multi-view refinement to ensure robust, scalable solutions.
architectural patternsnon-functional requirementsrequirements analysis
0 likes · 14 min read

This article introduces software requirements engineering, covering its iterative process, the distinction between user and system requirements, functional versus non‑functional requirements, and the role of feasibility studies in guiding successful system development.
Requirements Engineeringfeasibility studyfunctional requirements
0 likes · 8 min read

The article explains ten key non‑functional quality attributes of software architecture—such as scalability, availability, consistency, resilience, usability, observability, security, persistence, agility, and maintainability—describing their meanings, typical implementation techniques, and why selecting the right attributes is crucial for any system.
availabilitynon-functional requirementsquality attributes
0 likes · 9 min read


DevOpsJan 31, 2023 · R&D Management
The article explains what cross‑functional (non‑functional) requirements are, illustrates common scenarios where they cause system failures, outlines the perspectives of different teams in identifying them, and advises Tech Leads on how to proactively address these requirements while noting an upcoming DevOps hackathon.
R&D managementTech Leadcross-functional requirements
0 likes · 6 min read


DevOpsNov 9, 2022 · Fundamentals
The article explains what cross‑functional (non‑functional) requirements are, illustrates common scenarios where they cause issues, and provides guidance for tech leads on identifying, discussing, and prioritizing these requirements from multiple stakeholder perspectives to avoid technical debt and risk.
Tech Leadcross-functional requirementsnon-functional requirements
0 likes · 5 min read


DevOpsJul 19, 2022 · R&D Management
The article outlines comprehensive quality‑assurance approaches for technical improvement projects—such as large‑scale refactoring, architecture upgrades, and migrations—by emphasizing risk‑driven planning, automated testing, business‑centric reviews, non‑functional requirement validation, and continuous knowledge sharing.
R&D managementautomated testingnon-functional requirements
0 likes · 11 min read


DevOpsApr 29, 2022 · R&D Management
The article outlines comprehensive quality assurance approaches for technical improvement projects, highlighting risk-driven processes, automated testing, business perspective integration, and the importance of addressing non‑functional requirements to ensure stable, reliable system upgrades.
R&D managementnon-functional requirementsrisk management
0 likes · 12 min read

This article explains the concepts, metrics, planning stages, and architectural components of high availability for business systems, covering reliability, performance, scalability, evaluation phases, performance modeling, and practical implementation guidelines to achieve four‑nine (99.99%) uptime.
Performance Modelingnon-functional requirementssystem architecture
0 likes · 17 min read

This article outlines the complete requirement engineering process, covering requirement acquisition, modeling, specification, verification, and management, along with the architect’s perspective, analysis methodologies, business process analysis, system boundary definition, functional and non‑functional requirements, and clear system acceptance criteria.
business analysisfunctional requirementsnon-functional requirements
0 likes · 6 min read


21CTOJan 26, 2021 · Fundamentals
This article explains the twenty‑one key non‑functional characteristics of software architecture—such as performance, reliability, scalability, security and maintainability—detailing their definitions, typical metrics, and practical techniques for improvement, while linking each trait to ISO‑25010 and real‑world engineering practices.
DevOpsnon-functional requirementsperformance
0 likes · 20 min read

This article explains the most important non‑functional characteristics of software architecture—such as performance, reliability, availability, resilience, scalability, security, and many others—and provides practical techniques and best‑practice recommendations for enhancing each of these qualities in modern systems.
non-functional requirementsscalabilitysecurity
0 likes · 18 min read


21CTODec 12, 2017 · Fundamentals
This article explains what software architecture is, its lifecycle, why a solid architecture is crucial, how to distinguish good from bad designs, the roles and responsibilities of architects, and the skills—both technical and soft—needed to become an effective software architect.
non-functional requirementssoftware architecturesystem design
0 likes · 12 min read

This article explains the concept of software architecture, its definition, lifecycle, importance, characteristics of good and bad designs, essential technical knowledge for Java architects, functional versus non‑functional requirements, types of architects, required hard and soft skills, and guidance on becoming and maintaining an effective software architect.
architect rolenon-functional requirementssoftware architecture
0 likes · 13 min read

This article explores the blurry line between development and software architecture, outlines the responsibilities and evolution of a software architect, and provides practical guidance on defining architecture, managing non‑functional requirements, selecting technologies, evaluating designs, and leading teams toward successful releases.
non-functional requirementssoftware architecturesoftware design
0 likes · 12 min read

The article outlines a software engineer’s evolution from focusing on business functionality and non‑functional requirements to mastering micro‑ and macro‑level concerns, embracing the "Shu‑Ha‑Ri" craftsmanship philosophy, and adopting the mindset, conditions, and practices needed for sustained professional growth.
craftsmanshipgrowth roadmapnon-functional requirements
0 likes · 18 min read


21CTOApr 13, 2017 · Operations
This article presents a comprehensive methodology for internet performance engineering, covering non‑functional quality goals, detailed metrics for application servers, databases, caches and message queues, a practical technical review outline, and a real‑world capacity‑planning case study with both maximal and minimal resource solutions.
Operationsbackend architecturecapacity planning
0 likes · 24 min read

This article presents a comprehensive methodology for reviewing internet‑scale system architectures, focusing on non‑functional quality attributes such as performance, availability, scalability, security, and maintainability, and provides detailed guidelines, metrics tables, and a classic case study for capacity and performance planning.
BackendOperationsarchitecture
0 likes · 27 min read

This article shares a senior technical director’s hard‑won lessons on balancing hands‑on development, non‑functional requirements, architecture design, training, and management to boost team productivity and product quality in software projects.
lead engineernon-functional requirementssoftware development
0 likes · 20 min read


21CTOMay 13, 2016 · Fundamentals
This article explores the definition, lifecycle, importance, and best practices of software architecture, compares good and bad designs, outlines the roles and responsibilities of architects, and offers guidance on the skills and mindset needed to become an effective software architect.
architect rolenon-functional requirementssoftware architecture
0 likes · 12 min read
