SW Engineering & Management Topics
107 topics
- SW Engineering & Management
Git Branching Strategy — GitFlow, GitHub Flow, Trunk-Based Development
A team ruleset for creating, integrating, and releasing branches that standardizes collaboration and deployment; GitFlow (release-centric, long-lived branches), GitHub Flow (single main, short branches), and trunk-based development (ultra-short branches, feature flags) trade stability against deployment speed at different points, chosen per the organization deployment frequency, automation maturity, and regulatory needs.
- SW Engineering & Management
Sidecar Pattern
A structural cloud-native design pattern that co-locates an auxiliary container sharing the application's lifecycle to separate and reuse cross-cutting concerns such as logging, observability, security, and communication from the code — covering the shared-Pod structure and lifecycle, automatic injection, network/observability/secret/platform types, comparison with Ambassador and Adapter, the ambient and eBPF sidecar-less trends, and professional-engineer adoption strategy.
- SW Engineering & Management
Component-Based Development (CBD)
A software-reuse methodology that identifies, acquires, and assembles black-box components with specified interfaces that can be deployed and composed independently — constituent elements, the development process (for reuse / with reuse) and design principles, comparison with OOP/SOA/MSA/SPL, and the link to package ecosystems and supply-chain security (Log4Shell, SBOM).
- SW Engineering & Management
Kano Model
A quality-classification and prioritization technique by Noriaki Kano that analyzes quality attributes as a nonlinear fulfillment-satisfaction relationship and sorts them into five categories — must-be, one-dimensional, attractive, indifferent, and reverse quality. Using functional/dysfunctional question pairs, the Kano evaluation table, and Timko's Better/Worse coefficients, it distinguishes "defense elements that prevent dissatisfaction from differentiation elements that lift satisfaction" to support requirements prioritization. Covers the satisfaction-dissatisfaction asymmetry (resemblance to Herzberg's motivation-hygiene theory), the survey/analysis process and sampling cautions, combination with IPA/QFD/AHP, dynamic Kano degeneration from attractive to one-dimensional to must-be, text-mining and AI-based continuous analysis, agile backlog prioritization, and professional-engineer considerations such as segment dependence and the limits of innovation creation.
- SW Engineering & Management
Monorepo Strategy and Comparison with Polyrepo
A source control strategy that consolidates multiple projects into a single repository via source dependency to gain atomic change, global visibility, and code sharing. It covers the role of dedicated infrastructure such as impact-based selective builds, remote cache, and virtual filesystems, a comparison of Nx/Turborepo/Bazel, the coupling-point difference versus polyrepo, and the scaling cases and trade-offs of Google, Meta, and Microsoft, written as a professional-engineer essay.
- SW Engineering & Management
ISO/IEC 12207 (Software Life Cycle Processes)
An international standard defining the entire software life cycle — acquisition, supply, development, operation, maintenance, disposal — as standard processes; reorganized into four process groups harmonized with ISO/IEC 15288 in the 2017 revision, applied via tailoring.
- SW Engineering & Management
ArchiMate (Enterprise Architecture Modeling Language)
The Open Group's open standard — an EA modeling language that renders all layers (strategy, business, application, technology) consistently with 'layer × aspect' and formally defined elements and relationships, enabling cross-layer tracing and impact analysis. Covers the layer/aspect framework, elements/relationships and service orientation, the viewpoint mechanism, the division of roles with TOGAF·UML·BPMN·Zachman, and ArchiMate 3.2 trends with Architecture-as-Code, in a professional-engineer essay style.
- SW Engineering & Management
TCC (Try-Confirm-Cancel) Distributed Transaction Pattern
A compensation-based distributed transaction pattern that decomposes a transaction into per-service Try (reserve), Confirm (commit), and Cancel (release) operations to obtain, without 2PC's long lock holding, a quasi-isolation stronger than Saga — an application-level two-phase commit, organized as an essay covering resource-freezing principles, comparison with 2PC and Saga, integrity challenges such as idempotence/empty-rollback/hanging, and Seata application and practical cases.
- SW Engineering & Management
Evolutionary Architecture and Fitness Functions
An architecture that nails down the quality attributes to be preserved as executable fitness functions and evaluates them automatically on every change to absorb change across multiple dimensions safely and incrementally — covers the guided/incremental/multi-dimensional properties, fitness function classification (atomic/holistic, triggered/continual) and automated governance, comparison with traditional governance, and extension into the data/AI era.
- SW Engineering & Management
Software Product Line (SPL)
A strategic reuse paradigm that produces a family of software systems sharing a market or mission from a common set of core assets in a prescribed way — covering the separation of domain and application engineering, commonality/variability analysis with feature models and binding time, proactive/reactive/extractive adoption strategies and scoping, the Cummins and Nokia cases, and convergence with DevOps and multi-tenancy.
- SW Engineering & Management
Modular Monolith Architecture
An architecture that keeps single-deployment simplicity while connecting domain modules only through public APIs and events and enforcing boundaries with tools — comparison with traditional monolith and microservices, data ownership and transition strategy, and Shopify/Prime Video cases.
- SW Engineering & Management
Software Asset Management (SAM)
A management system that, across the full lifecycle of software assets (acquisition, deployment, use, reclaim, retirement), continuously reconciles entitlements held against actual installation and usage to produce the Effective License Position (ELP), controlling compliance, cost, and security at once — covering ISO/IEC 19770 (SWID/ENT/RUM), license metrics (core, user, subscription) and virtualization/cloud traps, vendor-audit response, and the SAM/ITAM/FinOps convergence from a Professional Engineer viewpoint.
- SW Engineering & Management
Function Point (FP) Analysis
A functional size measurement method that identifies and weight-sums the functionality software delivers into data functions (ILF·EIF) and transaction functions (EI·EO·EQ) to measure size independently of implementation technology — the standard for Korea's SW project cost estimation.
- SW Engineering & Management
Webhooks: Event Integration with Reliability and Security Design
A reverse-callback integration method where the provider sends HTTP directly to the receiver URL when an event occurs, eliminating polling inefficiency for near-real-time linkage. It secures reliability via delivery queues, retries, and idempotency; security via HMAC signatures, timestamps, HTTPS, and SSRF defense; and performance via immediate response plus asynchronous processing, with comparisons to polling, WebSocket, SSE, and brokers.
- SW Engineering & Management
Dead Letter Queue (DLQ) and Message Failure-Handling Strategies
An auxiliary queue that isolates poison messages which cannot be processed, preventing both infinite retries and loss in at-least-once delivery environments. It covers the two-stage retry/backoff strategy, broker-specific topologies (SQS redrive, RabbitMQ DLX, Kafka DLT), idempotent reprocessing, and the observation system that together secure the reliability of asynchronous architectures.
- SW Engineering & Management
Digital Immune System (DIS)
An essay-form treatment of the Digital Immune System (DIS), a design and operations paradigm that combines observability, AI-augmented testing, chaos engineering, autoremediation, SRE, and software supply chain security into a single feedback loop so software resists, detects, recovers from, and learns about failures, defects, and threats on its own. Covers the backdrop of rising failure cost, exploding system complexity, and siloed practices; the biological-immunity-inspired closed loop of detect-resist-recover-learn and the role of the six practices; the principles of observability/anomaly detection, AI-augmented testing/chaos engineering, autoremediation/SRE, and software supply chain security; comparison with DevSecOps, observability, and cyber resilience; streaming/finance/manufacturing cases; a four-stage maturity roadmap and pitfalls such as alert fatigue and skipping the order; and professional-engineer considerations on risk-tiered application, the automation-control trade-off, organizational-culture change, metrics (MTTD/MTTR), related technologies, and extending to the AI-era threat surface.
- SW Engineering & Management
EAI and ESB (Enterprise Application Integration)
EAI integrates heterogeneous applications, data, and processes on a central connectivity foundation, and ESB is its SOA-style implementation (bus-type mediation, routing, transformation, orchestration) — point-to-point to hub-and-spoke to bus topologies, differences from API Gateway and MOM, modernization to iPaaS/API-led/event-based, and a right-weight selection strategy.
- SW Engineering & Management
Cell-Based Architecture and Blast-Radius Isolation
An availability-centric pattern that partitions the system into independent, share-nothing self-complete cells and pins each request to a cell by partition key through a simple, highly-available router, so any failure, faulty deployment, or overload is contained to one cell (1/N, or combinatorially smaller with shuffle sharding). Covers cells, the router, control/data-plane separation and static stability, shuffle sharding, wave deployment, comparison with bulkhead/microservices/sharding/multi-tenancy, cases (Slack, DoorDash, Roblox), and design trade-offs.
- SW Engineering & Management
SPICE (ISO/IEC 15504·330xx, Software Process Assessment)
An international-standard process assessment scheme that evaluates software and system processes along two dimensions — a process dimension and a capability dimension (levels 0–5, Process Attributes, N/P/L/F scale). This essay covers the two-dimensional structure and PRM·PAM·measurement framework, capability levels and Process Attributes, the assessment procedure, Automotive SPICE (ASPICE) and a comparison with CMMI, and the 15504→330xx transition.
- SW Engineering & Management
Formal Methods and Formal Verification
A high-assurance quality means that deals with the absence of defects through mathematical specification and proof; model checking (automatic, finite), theorem proving (general, infinite), and abstract interpretation are selected and concentrated by risk and combined with SMT, AI, and CI.
- SW Engineering & Management
Consumer-Driven Contract Testing
A testing technique in which the consumer defines its actual request/response usage as a contract and the provider independently verifies it, guaranteeing interface compatibility before deploy without running services together.
- SW Engineering & Management
Progressive Web App (PWA)
A web app that combines a Service Worker, Web App Manifest, and HTTPS on top of standard web technologies (HTML·CSS·JS) to deliver reliability, speed, and engagement — covering the Service Worker's request interception and lifecycle, App Shell·Cache Storage·IndexedDB offline design, the Cache First·Network First·SWR caching strategies and Workbox, comparison with native·hybrid·responsive web, the Twitter·Starbucks·Pinterest outcome cases, and trends in Project Fugu·iOS Web Push·store listing, in essay form.
- SW Engineering & Management
The Zachman Framework
A normalized two-dimensional classification schema (ontology) that classifies enterprise artifacts as the 36 cells of six questions (What·How·Where·Who·When·Why, columns) intersecting six stakeholder perspectives (Planner~User, rows) — covering primitive/composite models and the basic rules, comparison with TOGAF and government EA, and Zachman 3.0 with digital-transformation application.
- SW Engineering & Management
Micro-Frontend Architecture
An essay-style study note on decomposing a frontend monolith by business domain for per-team independent development and deployment: build/server/runtime/edge composition and Module Federation, routing/state sharing/style isolation, comparison with a single SPA, real cases such as Zalando, and the trade-offs of performance, consistency, and operational complexity.
- SW Engineering & Management
Open API
A deep-dive on open APIs: definition/background/components and OAuth authentication, SOAP vs REST comparison, response to OWASP API vulnerabilities (BOLA), gateway/contract-first/lifecycle management, and latest trends (GraphQL/zero trust).
- SW Engineering & Management
Software Maintenance 3R (Reverse Engineering, Restructuring, Reengineering)
A technique that improves the maintainability of legacy SW and cuts costs through reverse engineering (design extraction), restructuring (structural improvement), and reengineering (rebuilding).
- SW Engineering & Management
Mutation Testing
A technique that injects artificial faults (mutants) into code and evaluates the fault-detection power of test cases by whether the tests catch them.
- SW Engineering & Management
Cost Estimation for the Software Operation Phase
Operation-phase cost estimation under the SW Project Cost Estimation Guide (2023): rate-based maintenance (development cost × rate) for scale-driven work, effort-based operation (M/M × unit labor cost) for staffing-driven work, and fixed/variable-cost methods for demand variation, plus recent integrated-operation trends.
- SW Engineering & Management
Software Requirements Engineering
Activities that systematize stakeholder requirements through elicitation → analysis → specification → validation → management, preventing requirement defects and project failure with a complete, consistent, traceable SRS plus baseline, RTM, and CCB.
- SW Engineering & Management
Classification of Software Engineers (Grade System → IT Job System)
The concept and characteristics of shifting from a career-based grade system to a job- and competency-based IT job system, and the problems and improvement directions of the current IT job system.
- SW Engineering & Management
Architectural Styles and Design Patterns (GoF)
The difference between macro-level architectural styles (layered, MSA, event-driven) and micro-level GoF design patterns (creational, structural, behavioral).
- SW Engineering & Management
DataOps and DevOps
A comparison of DevOps, which automates code deployment, and DataOps, which automates data pipelines and analytics, along with DataOps architecture and technologies.
- SW Engineering & Management
Reactive Streams and Backpressure Control
Reactive Streams is an asynchronous, non-blocking stream-processing standard that controls the production rate by sending request(n)-based demand signals back upstream to match the consumer's processing capacity. This note covers the Publisher/Subscriber/Subscription/Processor specification, the demand-based flow-control procedure, overflow strategies such as buffer/drop/latest, WebFlux and Kafka-consumer cases, and its complementary relationship with virtual threads, in essay form.
- SW Engineering & Management
Configuration Management and Baselines
Configuration management, which handles changes to work products through identification, control, status accounting, and auditing, and the concepts of functional, allocated, and product baselines.
- SW Engineering & Management
Integration Test
Integration testing that verifies interfaces and interactions when modules are combined — non-incremental (big bang) vs. incremental (top-down, bottom-up), drivers and stubs, and MSA contract testing.
- SW Engineering & Management
Comparison of Waterfall and Agile Development Methodologies
A comparison of the characteristics, strengths and weaknesses of sequential, plan-driven Waterfall and iterative, change-responsive Agile, with selection criteria.
- SW Engineering & Management
Idempotency Design and Distributed System Reliability
An overview of the definition of idempotency — whereby performing the same operation multiple times does not change the final state — its distinction from safety and atomicity, HTTP method conventions and delivery semantics, the implementation of idempotency keys, natural keys, and idempotent consumers with atomic reservation, payment and messaging examples, and integration with resilience patterns.
- SW Engineering & Management
Software Safety Analysis (FTA, FMEA, HAZOP)
Analysis techniques that prevent hazards in safety-critical systems from the early design stage — FTA (top-down), FMEA (bottom-up, RPN), HAZOP (guidewords), and STPA (systems theory) — and their links to ISO 26262 and IEC 61508.
- SW Engineering & Management
Test-Driven Development (TDD)
An evolutionary development technique that repeats short cycles of writing a failing test first (Red), passing it with a minimal implementation (Green), and improving the structure (Refactor) to simultaneously secure an executable specification, loosely coupled design, and a regression safety net. Extends to the FIRST principles, test doubles, the classicist/London schools, and BDD/ATDD integration.
- SW Engineering & Management
Web Accessibility and WCAG/KWCAG
A professional-engineer essay-style overview of the quality attribute that ensures everyone, including people with disabilities and older adults, can use web information equally — the four POUR principles, WCAG 2.2 (international, AA) and KWCAG 2.2 (4 principles, 14 guidelines, 33 items), the accessibility-by-design process, automated, manual, and user evaluation, and WCAG 3.0 trends.
- SW Engineering & Management
Software Architecture Analysis and ATAM
Evaluating whether a structure satisfies quality-attribute requirements. ATAM uses quality scenarios to elicit sensitivity points, trade-offs, and risks.
- SW Engineering & Management
Legacy Modernization Based on the Strangler Fig Pattern
A strategy that lets legacy and new functionality coexist through a facade/routing layer and modernizes a large-scale system without downtime via business slices, data ownership, CDC, gradual traffic shifting, rollback, and observability, then removes the temporary structure and the legacy.
- SW Engineering & Management
Green Software and Sustainable Software Engineering
Sustainable software engineering that reduces carbon emissions across the software lifecycle through the three principles of energy efficiency, carbon awareness, and hardware efficiency, measures emissions per functional unit with ISO/IEC 21031 (SCI), and links to ESG, FinOps, and Observability.
- SW Engineering & Management
Structured Methodology and Agile (Scrum and Kanban)
A comparison of structured methodology and Agile, the Agile implementations Scrum (time-boxing) and Kanban (flow optimization), and approaches to executing them effectively.
- SW Engineering & Management
Feature Flags and Progressive Delivery
The types, lifecycle, and evaluation architecture of feature flags, which separate deployment from release and control feature exposure at runtime, along with strategies for progressive delivery, kill switches, and flag-debt management.
- SW Engineering & Management
Software Modules — Cohesion, Coupling, and Fan-in/out
Cohesion and coupling as measures of module design (high cohesion, low coupling), and the Fan-in (reuse) and Fan-out (dependency) metrics.
- SW Engineering & Management
Property-Based Testing and Generative Quality Verification
A generative quality-verification strategy that explores a broad input space using executable properties and domain generators, and links the shrunk minimal counterexample to regression tests.
- SW Engineering & Management
BFF (Backend for Frontend) Pattern and Browser OAuth Security
Organizes the BFF pattern, which places a dedicated backend per client experience to compose, transform, and protect APIs, along with its architecture, organizational ownership, comparison with API gateways and GraphQL, and failure/performance/operational trade-offs, and connects it to the browser OAuth security recommendations of RFC 10017.
- SW Engineering & Management
Technical Items of the Software Requirements Specification (SRS)
The items to be described in a requirements specification (overview, functional, non-functional, interface, constraints, data) and the quality attributes of good requirements.
- SW Engineering & Management
Domain Exploration and Design Based on EventStorming
A workshop in which domain experts and developers jointly explore the terminology, rules, exceptions, responsibilities, and boundaries of complex business by laying domain events along a timeline — covering the Big Picture, Process, and Software Design stages, DDD/EDA/CQRS integration, hotspot management, and legacy modernization and facilitation strategy.
- SW Engineering & Management
STPA (System-Theoretic Process Analysis)
The limits of component-failure-centric FMEA and HAZOP, and the concept and method of STPA, a systems-theory-based approach that analyzes control and interaction errors.
- SW Engineering & Management
Software Architecture Documentation Based on the C4 Model and ADRs
An integrated documentation strategy that represents structure for each audience through C4's Context, Container, Component, and Code layers, and records the context, alternatives, and trade-offs of architectural decisions with ADRs.
- SW Engineering & Management
Event-Driven Architecture (EDA) Topologies
A comparison of the mediator and broker topologies of EDA, which loosely couples components through event publishing and subscription, its components, and extensions to Saga, eventual consistency, event sourcing, and CQRS.
- SW Engineering & Management
Microservices Architecture (MSA)
An architecture that decomposes an application into small, independently deployable and scalable services. Covers a comparison with monoliths, saga and circuit breaker, service mesh (Istio), DDD-based decomposition, and Kubernetes and incremental migration.
- SW Engineering & Management
DORA Software Delivery Performance Metrics (DORA Metrics)
Organizes how to measure and improve both software delivery throughput and instability together through change lead time, deployment frequency, time to restore from a failed deployment, change failure rate, and rework rate.
- SW Engineering & Management
Procedural and Object-Oriented Programming
Comparing procedural programming centered on function flow with object-oriented programming that encapsulates data and behavior into objects. Inheritance and polymorphism make it well suited to large-scale systems.
- SW Engineering & Management
UML Class Diagrams and Object Modeling
A static model expressing classes with their attributes, operations, and relationships (association, aggregation, composition, generalization). The design convergence point running from conceptual objects to sequences (message to method) to classes, with two-way linkage to code.
- SW Engineering & Management
Hexagonal Architecture (Ports and Adapters)
A Ports and Adapters structure that abstracts the business core into ports and isolates REST, DB, messaging, and external APIs as adapters — covering driving/driven ports, dependency inversion, testing and operational strategy, and comparison with layered and Clean Architecture.
- SW Engineering & Management
Java AWT and Swing
Comparing heavyweight OS-native-dependent GUI (AWT) with lightweight, Java-rendered GUI (Swing). Platform independence, look-and-feel, and the evolution to JavaFX.
- SW Engineering & Management
Transactional Outbox Pattern
A pattern that binds the dual-write problem of business data changes and event publishing into a single local transaction and delivers to the broker via an outbox and message relay — organizing polling publisher and CDC approaches, duplication/ordering/reprocessing/retention policies, comparison with 2PC/saga/event sourcing, and adoption strategy.
- SW Engineering & Management
AOP (Aspect-Oriented Programming)
A paradigm that separates cross-cutting concerns such as logging, security, and transactions into aspects and stitches them in through weaving. Covers its components, types of advice and weaving, application in Spring, and extension to service mesh.
- SW Engineering & Management
SOLID Object-Oriented Design Principles
Object-oriented design principles that separate responsibilities via the five principles SRP, OCP, LSP, ISP, and DIP and control dependency direction and size through abstraction to achieve change-resilient design — a common language for maintainability that extends to Clean Architecture and MSA.
- SW Engineering & Management
Software Cost Estimation Methods
A risk-management activity that predicts effort, schedule, and cost before project kickoff. The trade-offs among top-down (expert, Delphi), bottom-up (WBS), and mathematical models (COCOMO, Function Point), Korea's Function Point standard (2024 FP unit price KRW 605,784), and Agile and AI-based estimation.
- SW Engineering & Management
ITIL 4 (IT Infrastructure Library) and Service Management
An in-depth note on ITIL 4, designing the operation and improvement framework for digital services through the Service Value System (SVS), the four dimensions, the seven guiding principles, the value chain, and management practices.
- SW Engineering & Management
No-Code
An approach that develops apps through visual editing without coding, enabling participation by business-side citizen developers, along with its pros and cons.
- SW Engineering & Management
Refactoring and Design Patterns
Refactoring, which improves structure while preserving behavior, and design patterns, which are proven design solutions — their definitions, techniques, code smells, and commonalities and differences.
- SW Engineering & Management
CI/CD Pipeline (Continuous Integration / Continuous Deployment)
This essay covers the structure and principles of a CI/CD pipeline that implements the software-delivery process from commit to deployment as an automation chain of build, test, quality gate, and deployment — the difference between CI (small, frequent integration with immediate verification) and continuous delivery/deployment, zero-downtime deployment strategies, quality gates, DevSecOps, and supply chain security, environment-promotion principles, and DORA-metrics-based management along with a professional-engineer application strategy.
- SW Engineering & Management
CMMI (Capability Maturity Model Integration)
A performance-oriented framework that diagnoses and improves an organization's process capability across five maturity levels (Initial, Managed, Defined, Quantitatively Managed, Optimizing) and four capability levels. This essay covers the representations (continuous and staged), practice areas and domains, the appraisal (Benchmark, Sustainment, Evaluation) procedures, a comparison with SPICE and ISO 9001, integration with Agile and DevOps, and the V3.0 (2023, ISACA) extension.
- SW Engineering & Management
Fuzz Testing and Vulnerability Detection Strategy
This essay covers the principles and application strategy of fuzz testing, which automatically generates and mutates abnormal and boundary inputs to find crashes, memory errors, state-transition violations, and business-rule defects.
- SW Engineering & Management
SW Safety Diagnosis: Functional-Behavior Correctness Diagnosis
Traceability-based verification of correctness at each stage: requirements, design, implementation, and test. Includes normal, abnormal, and boundary conditions, linked to functional-safety standards such as ISO 26262 and IEC 61508.
- SW Engineering & Management
Types of Software Coupling
The types of coupling that weaken in the order content > common > external > control > stamp > data, and the design principles of low coupling and high cohesion.
- SW Engineering & Management
Microservices Architecture (MSA)
This essay covers, in an essay format, service decomposition along domain boundaries, API and event-based communication, distributed data consistency, fault isolation, and incremental migration strategy.
- SW Engineering & Management
RPA (Robotic Process Automation) and Intelligent Process Automation (IPA)
This essay addresses how to extend RPA — which automates repetitive tasks with rule-based software robots — into intelligent process automation by combining it with process mining, IDP, and AI. It covers target selection, architecture, operational governance, security, and performance measurement in an essay format.
- SW Engineering & Management
Software Quality Certification (GS Certification)
A scheme in which a third party tests and certifies the quality of SW products based on ISO/IEC 25000. Covers resolving information asymmetry and preferential treatment in public procurement.
- SW Engineering & Management
UML Sequence Diagram
A UML dynamic diagram that represents messages between objects in chronological order. Covers lifelines, activation boxes, messages, frames, and guards.
- SW Engineering & Management
API Management and API Lifecycle Governance
A governance framework that manages APIs as a single lifecycle spanning contract, portal, gateway, security, observability, change, and retirement, improving reusability, stability, and consumer experience.
- SW Engineering & Management
Message Queues and Apache Kafka
This essay provides an in-depth treatment of the communication model of message queues, which decouple producers and consumers via a buffer to achieve asynchronous, loose coupling, and of the architecture, delivery semantics, and trade-offs of Apache Kafka, which supports durable storage, reprocessing, and horizontal scaling of high-volume events based on a distributed commit log.
- SW Engineering & Management
Technical Debt Management and Repayment Strategy
The causes, types, measurement, and management lifecycle of technical debt — incurred by accepting future change and operational costs for the sake of fast delivery — and a sustainable repayment strategy.
- SW Engineering & Management
Web Performance Management and Front-End Optimization
Factors that degrade web performance and front-end optimization measures such as resource compression, image optimization, request reduction, caching, and rendering optimization.
- SW Engineering & Management
Distributed Tracing and Unified Observability with OpenTelemetry
How to collect and correlate traces, metrics, and logs with OpenTelemetry, the vendor-neutral instrumentation standard, and design observability for distributed systems using the Collector, OTLP, and semantic conventions.
- SW Engineering & Management
Software Cost of Quality
The four cost-of-quality categories of conformance cost (prevention, appraisal) and non-conformance cost (internal, external failure) and their trade-off relationship. Covers the law of escalating defect-fix cost, the optimal investment point, and Shift-Left/Right in depth.
- SW Engineering & Management
E-Government Website Quality (Accessibility, Compatibility, Openness, Optimization)
UI/UX design criteria plus web accessibility, compatibility, openness, and optimization to guarantee all citizens equal, non-discriminatory use. KWCAG-based accessibility is a legal obligation.
- SW Engineering & Management
Software Architecture Evaluation Based on ATAM (Architecture Tradeoff Analysis Method)
This essay covers the ATAM evaluation method, which identifies architectural risks, sensitivity points, and trade-offs based on business drivers and quality-attribute scenarios and links them to stakeholder consensus and decision records, in a professional-engineer essay format.
- SW Engineering & Management
The Bulkhead Pattern and Fault Isolation
The principle, implementation levels, and operational strategy of the bulkhead pattern, which partitions shared resources into independent pools so that the latency or exhaustion of one dependency does not propagate to other functions.
- SW Engineering & Management
SRE (Site Reliability Engineering) and Service Reliability Management
An engineering discipline that designs software from an operations perspective and, through SLIs, SLOs, error budgets, and incident response, manages the balance between service reliability and development velocity.
- SW Engineering & Management
Test Coverage and Code Coverage
The relationship and comparison between test coverage, which validates requirements, functions, and risks, and code coverage, which instruments code execution (statement, branch, condition, MC/DC). Covers the limits of 100% coverage and mutation testing, CI quality gates, and risk-based target setting.
- SW Engineering & Management
CBAM (Cost Benefit Analysis Method)
An architecture evaluation method (an extension of ATAM) that analyzes the costs and benefits of architectural strategies to set ROI-based investment priorities.
- SW Engineering & Management
Spring Boot
The characteristics of Spring Boot, which rapidly develops standalone applications with minimal configuration through auto-configuration, starters, and an embedded server.
- SW Engineering & Management
gRPC (Google RPC Framework)
An RPC framework that combines Protocol Buffers' strongly typed contracts and code generation, binary serialization, and HTTP/2 multiplexing and streaming to deliver low-latency, high-throughput communication between microservices—a pillar of a tiered API strategy that uses gRPC internally and REST/GraphQL externally.
- SW Engineering & Management
GraphQL (API Query Language)
An API specification in which clients select only the fields they need within a strongly typed schema and query a single endpoint—resolving over-/under-fetching and covering resolvers, the N+1 problem, DataLoader, comparison with REST, and caching, security, and federation.
- SW Engineering & Management
Saga Pattern and Distributed Transactions
A distributed-transaction technique that splits a transaction spanning multiple services into a chain of local transactions and, on failure, undoes them in reverse order via compensating transactions to achieve atomicity at the application level—an eventual-consistency strategy that trades 2PC's strong consistency for availability and scalability, where the choice between choreography and orchestration and the design of idempotency, outbox, and compensation determine success or failure.
- SW Engineering & Management
Domain-Driven Design (DDD)
A method of reflecting the core concepts and rules of a complex business domain in the software model and designing systems resilient to change through bounded contexts and tactical patterns.
- SW Engineering & Management
API Gateway Architecture and Operations
An essay-style overview of the architecture, design, and operational strategy of the API gateway, which unifies routing, authentication and authorization, traffic control, and observability between clients and backend services.
- SW Engineering & Management
Circuit Breaker Pattern and Fault Isolation
Explains the circuit breaker's state model, which detects failures and delays in remote dependencies to block calls and confirms recovery with limited trial calls, along with its combination of retries and timeouts, fallback, and operational design.
- SW Engineering & Management
CQRS and Event Sourcing (Command Query Responsibility Segregation, Event Sourcing)
Organizes the principles of CQRS, which separates read and write responsibilities, and event sourcing, which preserves change history as events, along with their combined structure, consistency, reprocessing, schema evolution, and adoption strategy.
- SW Engineering & Management
Four Characteristics of Good Software
The four characteristics of good software (maintainability, dependability, efficiency, usability), ways to achieve them, and their link to the ISO/IEC 25010 quality model.
- SW Engineering & Management
Digital Government Service UI/UX Guideline (Feb. 2024)
A Ministry of the Interior and Safety guideline that consistently ensures the UI/UX quality and accessibility of public digital services through a structure of principles, elements, patterns, and styles.
- SW Engineering & Management
IT Service Management (ITSM) and ISO/IEC 20000
A framework for managing IT from a service perspective — Design (SLA, capacity) → Transition (change, release, configuration) → Operation (incident, problem) → Improvement processes.
- SW Engineering & Management
Performance Indicators for Information System Performance Requirements
Performance indicators such as response time, throughput (TPS), concurrent users, resource utilization, and availability, along with considerations for defining them (peak, quantitative, SLA) and verification methods.
- SW Engineering & Management
Types of Software Testing and Reliability & Portability Testing
Types of testing (by level, technique, and purpose) and the detailed activities of reliability testing (maturity, fault tolerance, recoverability) and portability testing (adaptability, installability, replaceability).
- SW Engineering & Management
REST API (Representational State Transfer)
An architectural-style API based on a stateless, uniform interface that identifies resources by URI and expresses actions via HTTP methods — the six principles and the maturity model.
- SW Engineering & Management
Software Sizing Methods and Improvements for Public SW
Comparison of the LoC, function point (FP), use case, and story point methods, and practical improvement measures for sizing public-sector SW.
- SW Engineering & Management
Deployment and Testing Strategies for Running Applications
Zero-downtime deployment (blue-green, canary, rolling, A/B) and testing strategies before, during, and after deployment (regression, canary analysis, shadow, feature toggle).
- SW Engineering & Management
Information Hiding
A design principle that hides a module's internal implementation and exposes only its interface to reduce coupling, and its relationship with and effects on encapsulation.
- SW Engineering & Management
IT Governance
The components of governance that align and control IT with business strategy, effectiveness metrics (BSC, KPI), and measurement methodologies (COBIT, ISO 38500).
- SW Engineering & Management
Software Testing (Principles, Black-box/White-box, Techniques)
The seven testing principles, a black-box vs. white-box comparison, and a summary of specification-, structure-, and experience-based testing techniques.
- SW Engineering & Management
Design System
A product-level asset and operating framework that binds design tokens, components, patterns, and governance into a single source of truth to synchronize design and code. Covers the three token layers and SSOT, atomic design, centralized·federated·hybrid governance, cases like Material 3·Carbon·Polaris, W3C token standardization, built-in accessibility, and an incremental-ROI strategy.