Project manager를 위한 View

  • A top-level context diagram [ module ]
  • A decomposition, uses, and/or layered view [ module ]
  • A work assignment view [ allocation ]
  • A deployment view [ allocation ]
  • Overall purpose and constraints

 개발 팀을 위한 View

  • A context diagram containing the module(s) he or she has been assigned[ module ]
  • A decomposition, uses, and/or layered view [ module ]
  • A view showing the component(s) the developer is working on and how they interact with other components at runtime [ C&C ]
  • A mapping between views, showing the module(s) as components [ module, C&C ]
  • The interface specification(s) of the developer’s element(s) and the interface specifications of those elements with which they interact [ module, C&C]
  • The variability guide to implement required variability [ module ]
  • An implementation view to find out where the assets he or she produces must go [ allocation ]
  • A generalization view showing other modules that the developer can use to accomplish his or her work assignment [ module ]
  • A deployment view [ allocation ]
  • The documentation that applies beyond views, including a system overview
  • Rationale and constraints

 Tester 혹은 integrater를 위한 View

  • A context diagram showing the module(s) to be tested or integrated [ module ]
  • The interface specification(s) and behavior specification(s) of the module(s) and the interface specifications of those elements with which they interact [ module, C&C ]
  • An implementation view to find out where the assets that build the module are [ allocation ]
  • A deployment view [ allocation ]

 다른 시스템의 디자이너를 위한 View

  • A top-level context diagram [ module and/or C&C]
  • Interface specifications for those elements with which their system will interact [ module, C&C ]

 Maintainer를 위한 View

  • The views as mentioned for the developers of a system
  • A decomposition view [ module ]
  • A layered view [ module ]
  • Rationale and constraints

 Customer를 위한 View

  • A work assignment view, no doubt filtered to preserve the development organization’s confidential information [ allocation ]
  • A deployment view [allocation ]
  • Analysis results [ module, C&C ]
  • A top-level context diagram in one or more C&C views [ C&C]

End User를 위한 View

  • A view emphasizing flow of control and transformation of data, to see how inputs are transformed into output [ C&C ]
  • A deployment view to understand how functionality is allocated to the platforms with which the users interact [allocation ]
  • Analysis results that deal with properties of interest to them, such as performance or reliability [ module and/or C&C ]

 Analyst를 위한 View

  • Views of the module viewtype family [ allocation ]
  • A deployment view [allocation ]
  • A communicating-processes view [ C&C ]
  • Applicable component-and-connector views [ C&C]

 Infrastructure support 담당자를 위한 View

  • A decomposition view [module ]
  • A uses view [ module ]
  • A implementation view [ C&C ]
  • A variability guide [ module, C&C]
  • A deployment view [ allocation ]

미래의 아키텍트(후임자)를 위한 View

  • 아키텍쳐 모든 것에 관심이 있으며, 전임 아키텍트의 작업을 모두 이해하고자 함


Posted by sjokim
,