1 views collected around this technical thread.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.