Back to feed
Planning Notes·그냥 기획

(Code Scrap) Design Part 1 - IA, Functional Specification, Flowchart

NS
normalstory
cover image

Source: http://blog.naver.com/prologue/PrologueList.nhn?blogId=weedboy

Now that the analysis phase is complete, the planner begins concrete design based on the execution plan. Design here generally refers to screen design — creating storyboards.

Information Architecture (IA)

IA defines the structure and organization of content. It's the skeleton of any digital product — get it right, and everything else flows naturally. Get it wrong, and no amount of visual polish can save the user experience.

Functional Specification

Every feature needs clear documentation: what it does, how it behaves, what triggers it, and what the edge cases are. Ambiguity in specs leads to ambiguity in implementation.

Flowchart

Flowcharts map the user's journey through the system. They reveal bottlenecks, dead ends, and unnecessarily complex paths before a single line of code is written.

These three documents — IA, functional spec, and flowchart — form the bridge between analysis and implementation. They transform abstract requirements into actionable blueprints.

This English version was translated by Claude.

친절한 찰쓰씨
Written by
친절한 찰쓰씨

Pleasant Charles — UI/UX researcher at AIT. Keeping notes on design, planning, and slow days here since 2010.

More on the author's page

Keep reading

Planning Notes

May 26, 2026·1 min
Planning Notes

Turning AI’s Decisions into Real-World Action

May 24, 2026·2 min
Planning Notes

The two unchanging principles of vibe coding

Apr 12, 2026·3 min