Choose a System Metaphor
Choose a system metaphor to keep the team on the same page by naming classes and methods consistently. What you name your objects is very important for understanding the overall design of the system and code reuse as well. Being able to guess at what something might be named if it already existed and being right is a real time saver. Choose a system of names for your objects that everyone can relate to without specific, hard to earn knowledge about the system. For example the Chrysler payroll system was built as a production line. At Ford car sales were structured as a bill of materials. There is also a metaphor known as the naive metaphor which is based on your domain itself. But don't choose the naive metaphor unless it is simple enough.
μμ€ν
λ©νν¬λ₯Ό μ μ νλ©΄ κ°μ νλ΄μμ ν΄λμ€μ λ©μλμ μ΄λ¦μ μΌκ΄μ μΌλ‘ μ ν μ μμ΄ κ³΅κ°λλ₯Ό νμ±ν μ μλ€. (μ¦ νλμ λ©νν¬λ₯Ό μ μ νμ¬ κ³΅μ νλ©΄ λ³μ μ΄λ¦κ°μ κ²μ μ§μλ κ°μ κ΄μ μΌλ‘ μ§κ² λλ€λ μλ―Έ). μ΄λ€ κ°μ²΄μ λν μ΄λ¦μ μ νλ κ²μ μμ€ν
μ 체λ₯Ό μ΄ν΄νκ±°λ μ½λλ₯Ό μ¬μ¬μ©νλλ° λ§€μ° μ€μνλ€. λ§μ½ λ©νν¬λ₯Ό μ¬λ°λ₯΄κ² μ νλ€λ©΄, μ΄λ¦μ΄ μ΄λ»κ² μ ν΄μ§λκ°λ₯Ό μΆμΈ‘ν μ μκ²λκ³ μ€μ λ‘ κ°λ° μκ°μ ν¬κ² μ κ°μμΌμ€λ€. ꡬμΆν κ°μ²΄μ λν μ΄λ¦μ μν μμ€ν
(μ¦ λ©νν¬)λ₯Ό κ²°μ ν λλ λͺ¨λ μ¬λμ΄ ν΄λΉ μμ€ν
μ λνμ¬ νΉλ³ν μ§μμ΄ μμ΄λ μ½κ² μ°κ΄λμ΄ μ§μ μλ κ²μΌλ‘ μ νν΄μΌ νλ€. μλ₯Ό λ€μ΄ ν¬λΌμ΄μ¬λ¬μ μ§λΆμμ€ν
μ μμ°λΌμΈμΌλ‘ ꡬμΆλμλ€. ν¬λμ μλμ°¨ μμ
μ¬μλ€μ BOM(λΆνν)μΌλ‘ ꡬ쑰ν λμλ€. ꡬμΆνλ €κ³ νλ λΆμΌμ λ©νν¬λ₯Ό μ¬μ©ν μλ μλ€. κ·Έλ¬λ μΆ©λΆν λ¨μνμ§ μλ€λ©΄ μμμ ν΄λΉνλ λ©νν¬λ₯Ό μ¬μ©νμ§λ λ§μλΌ.
--> κ·Έλ°λ° μ€ μ¬λ‘λ‘ μ΄ν΄νκΈ°κ° νλλ€μ. λ©νν¬κ° νμ¬ μμ€ν μ μΆ©λΆν ν¬κ΄νμ§ λͺ»νλ κ²½μ°κ° μλΉν λ§μν΄λ°...
--> κ·Έλ°λ° μ€ μ¬λ‘λ‘ μ΄ν΄νκΈ°κ° νλλ€μ. λ©νν¬κ° νμ¬ μμ€ν μ μΆ©λΆν ν¬κ΄νμ§ λͺ»νλ κ²½μ°κ° μλΉν λ§μν΄λ°...
λ΅μ£Όμ€λΆ..
see XperDotOrg