1 views collected around this technical thread.
This article explores how software engineers can demonstrate and grow technical depth through a mindset shift, meticulous handling of requirements, continuous problem‑solving, and aligning personal growth with business goals, while also offering practical steps and resources for deeper skill development.
This article shares the author’s real‑world experience with equivalence class partitioning, explaining the concept, illustrating how to apply it to both numeric and non‑numeric game scenarios, and offering practical tips for writing robust test cases and avoiding common pitfalls in QA work.
This article explains how to move from business modeling to business and system use case diagrams, covering vision definition, business sequence diagrams, system use case creation, use case specifications, and concludes with a brief promotion for a DevOps certification course, offering practical guidance for software engineers.
The guide walks readers through clarifying vision, modeling business use case diagrams that capture external value, then translating those insights into detailed system use case diagrams and specifications—including actors, pre/postconditions, and paths—emphasizing that solid requirements, not code alone, drive enterprise profit.
The article distills the book “Software Method,” outlining a disciplined approach that starts with industry‑specific business modeling—defining vision, use‑case and sequence diagrams, and improvement patterns—then moves to precise requirements gathering, detailed analysis class diagrams, and finally design, emphasizing that true software value comes from meeting real demand.
The article explains how product managers convert boss and user demands into concrete product features by analyzing requirements, creating prototypes, writing clear PRD documents, organizing modules and functions, and visualizing feature structures, while also highlighting the importance of systematic processes for both existing and new products.
The article explains how business and domain modeling—using UML diagrams, RUP‑based workflows, and DDD principles—help engineers bridge the gap between business problems and technical solutions, enabling clearer requirements, stakeholder alignment, and improved system design across complex industries such as finance, logistics, and e‑commerce.
This article shares practical experiences and reflections on product thinking, user research, requirement analysis, cognitive biases, and user‑experience layers, offering concrete guidance for building usable, stable, and efficient QA tools within a development team.
This article outlines four practical QA scenarios—building a simple API automation framework, creating a Locust performance‑testing demo, writing functional test cases, and analyzing product requirements for hidden risks—while emphasizing how mastering ChatGPT can boost a tester's competitiveness.
This article explains how to design comprehensive test cases for offline store applications by reviewing requirement documents, applying testing theories, using software quality models, and addressing new features, existing feature iterations, technical refactoring, and statistical reporting requirements to ensure robust quality assurance.
This article outlines how QA can proactively join technical design reviews, detailing the required documentation, preparation steps, thinking methods, impact assessment, and testability improvements to ensure higher delivery quality and better collaboration among product, development, and testing teams.
This guide explains how to plan an application by identifying the problem it solves, its users, and goals, then maps the entire business process with visual flowcharts to ensure the solution fits within and improves the overall workflow.
This article explains how to select and use appropriate UML diagrams throughout a software project's lifecycle—covering project initiation, requirements analysis, system design, and detailed modeling—illustrated with electronic procurement and hospital admission case studies.
The article, presented by a senior architect, outlines the standardized six-stage process of database design—system requirements analysis, conceptual design, logical design, physical design, implementation, and operation & maintenance—accompanied by illustrative diagrams for each phase.
The article explains how thorough requirement analysis, disciplined daily planning, proactive risk communication, and a strong team project culture enable testers to actively contribute to project success, improve delivery quality, and align product outcomes with business value in fast‑changing mobile‑internet environments.
The article explains why software architects need to create clear diagrams, describes the problems they solve, lists nine typical diagram types—including use case, robustness, mind map, DFD, flowchart, class, state, E‑R, and sequence diagrams—with their appropriate scenarios, advantages, and drawbacks, and outlines a step‑by‑step workflow for applying them in real projects.
The article presents a structured framework for problem solving and architectural thinking, defining problems as goal‑state gaps, warning against common pitfalls, introducing a “what‑how‑why” learning loop, detailing root‑cause analysis for anomalous issues and goal‑driven stakeholder mapping for improvement tasks, and emphasizing emotional intelligence in human‑centric solutions.
The article explains how componentization, illustrated through computer hardware analogies, helps product managers analyze requirements from point, line, and surface perspectives, defines three core component attributes—individuality, shared reuse, and business enablement—and shows practical e‑commerce projects that embody these principles.
After a rushed fix for a division‑by‑zero bug caused incorrect results, the team learns to validate data at its source, adopt proper validation frameworks, and step back to understand underlying requirements, emphasizing that thoughtful design outweighs quick code patches.