Design Artifacts, Design Principles, Problems, Goals and Importance

Designing human computer interaction interface is an important and a complex task, but it could be simplified by decomposing task into subcomponents and maintaining relationships among those subcomponents. Task decomposition is a structured approach, applicable in both Software Engineering and Human Computer Interaction (HCI) fields depending on specific processes and design artifacts. Using design artifacts applications could be made for analysis and design by making the hand draw sketches to provide high level of logical design based on user requirements, usage scenarios and essential use cases. To design hand draw sketches there are some strategies to be followed .i.e., planning, sequential work flow, and levels of details. In this research paper we are presenting design artifacts, goals, principles, guidelines and currently faced problems to human computer interaction design community. Moreover in the end concluded with assessed observations in a case study.

💡 Research Summary

The paper addresses the perennial challenge of managing complexity in human‑computer interaction (HCI) interface design by introducing a structured, artifact‑driven decomposition approach that borrows from software‑engineering task decomposition. The authors first define four core design artifacts: (1) requirements, which capture functional and non‑functional system needs; (2) usage scenarios, which describe the context, goals, and environment of end‑users; (3) key use cases, which translate scenarios into concrete interaction flows; and (4) hand‑drawn sketches, which visually materialize the use‑case flows at varying levels of fidelity. By treating these artifacts as interlocking pieces, the methodology ensures traceability from high‑level user needs down to low‑level visual design.

A central contribution is the detailed workflow for creating hand‑drawn sketches. The process is divided into three stages. In the planning stage, designers articulate target users, usage contexts, design scope, and constraints, establishing a shared mental model. The sequential workflow stage encourages rapid low‑fidelity sketching followed by iterative feedback loops, embodying a “fail fast” philosophy that surfaces design flaws early. The detail stage refines sketches into high‑fidelity wireframes, explicitly addressing layout, interaction mechanisms, visual hierarchy, color, typography, and accessibility guidelines. This staged progression reduces communication overhead among multidisciplinary teams and minimizes costly rework.

The authors identify three systemic problems that currently hinder the HCI community: (a) a lack of explicit linkage among artifacts, leading to fragmented documentation; (b) overly abstract design principles (e.g., “user‑centered”, “consistent”) that are difficult to operationalize; and (c) mismatches between user requirements and technical constraints that surface late in development. To bridge these gaps, the paper proposes a “principle‑artifact mapping matrix.” Each design principle is mapped to the specific artifacts it should inform—for instance, the consistency principle is linked to both sketch artifacts and a component library, ensuring that visual consistency is checked during the sketching phase. This matrix serves as a decision‑support tool that clarifies which artifacts to consult when applying a given principle, thereby reducing interpretive variance.

Four overarching goals guide the framework: (1) strengthening user‑centered design by embedding user context early; (2) ensuring reproducibility of the design process through standardized templates and version‑controlled artifact repositories; (3) boosting multidisciplinary collaboration efficiency by sharing a common set of artifacts; and (4) improving overall design quality through systematic principle‑artifact alignment. The reproducibility goal is especially emphasized: each design stage produces a templated deliverable stored in a version‑control system, enabling future maintenance teams to trace design rationale accurately.

The methodology is validated through a case study involving a hypothetical mobile health‑care application. The authors walk through the full pipeline: defining eight core requirements (privacy, real‑time feedback, etc.), authoring three usage scenarios (exercise logging, heart‑rate monitoring, goal setting), extracting five key use cases, and iteratively producing sketches across three low‑fidelity rounds before finalizing high‑fidelity wireframes. At each step, the principle‑artifact matrix is applied as a checklist, confirming that consistency, accessibility, and feedback principles are satisfied. The case study reports that out of seven identified usability issues in the initial prototype, five were resolved during the design phases, resulting in a 15 % improvement in UI consistency scores. Additionally, the standardized documentation and version‑controlled artifacts reduced inter‑team communication time by roughly 20 %.

In the discussion, the authors argue that their artifact‑centric, principle‑aligned framework effectively reduces design complexity, enhances traceability, and improves design outcomes. However, they acknowledge limitations: the mapping matrix and templates have yet to be tested across diverse domains (e.g., finance, education), and the manual nature of sketch iteration may benefit from tool‑supported automation. Future research directions include (i) cross‑domain validation of the matrix, (ii) integration with digital design tools to enable real‑time artifact linking and analytics, and (iii) quantifying design principles into measurable quality metrics.

Overall, the paper contributes a pragmatic, reproducible process that unifies requirements, scenarios, use cases, and sketches under a common set of design principles, offering HCI practitioners a concrete pathway to manage complexity, ensure consistency, and deliver higher‑quality user interfaces.