Head First OOAD Ch6 tips

Information , features , and requirements
本章節當中 開宗明義的提到 一開始不要把features 與use classes 劃上等號
因為在處理大型系統時很可能一開始無法一窺全貌
但這並部代表說 就不能用use case來作為一簡單的描述
反倒是說 希望藉由簡單的(模糊點的大範圍功能)use case
來盡可能對應到所有的user request features(切記不要漏掉了囉).

# Use a feature or requirement list to capture the BIG THINGS that your
   system needs to do.
# Draw a use case diagram to show what your system IS , without getting into unnecessary detail.
# Domain analysis lets you check your designs, and still speak the customer's language.

Domain Analysis
The process of identifying , collecting, organizing, and representing the relevant information of
a domain, based upon the study of existing systems and their development histories, knowledge
captured from domain experts, underlying  theory, and emerging technology within a domain.

當已經逐漸的把大型系統範疇都拉進來之後, 開始逐步divide and conquer ..
# Don't forget who your customer really is A_A


# Domain analysis helps you avoid building parts of a system that aren't your job to build.