Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

IEEE-Std-1016-2009 Systems Design — Software Design Descriptions

1,358 views

Published on

IEEE-Std-1016-2009 Systems Design — Software Design Descriptions

Published in: Software
  • Be the first to comment

IEEE-Std-1016-2009 Systems Design — Software Design Descriptions

  1. 1. 1 © Copyright reserved Software Design Description
  2. 2. 2 © Copyright reserved Definition, abbreviation • design attribute: An element of a design view that names a characteristic or property of a design entity, design relationship, or design constraint. See also: design constraint, design entity, design relationship. • design concern: An area of interest with respect to a software design. • design constraint: An element of a design view that names and specifies a rule or restriction on a design entity, design attribute, or design relationship. See also: design attribute, design entity, design relationship.
  3. 3. 3 © Copyright reserved Definition, abbreviation • design element: An item occurring in a design view that may be any of the following: design entity, design relationship, design attribute, or design constraint. • design entity: An element of a design view that is structurally, functionally, or otherwise distinct from other elements, or plays a different role relative to other design entities. See also: design view. • design overlay: A representation of additional, detailed, or derived design information organized with reference to an existing design view. • design rationale: Information capturing the reasoning of the designer that led to the system as designed, including design options, trade-offs considered, decisions made, and the justifications of those decisions.
  4. 4. 4 © Copyright reserved Definition, abbreviation • design relationship: Element of a design view that names a connection or correspondence between design entities. See also: design entity. • design stakeholder: An individual, organization, or group (or classes thereof playing the same role) having an interest in, or design concerns relative to, the design of some software item. See also: design concern. • design subject: A software item or system for which an SDD will be prepared. Syn: software under design, system under design. • designer: The stakeholder responsible for devising and documenting the software design.
  5. 5. 5 © Copyright reserved Definition, abbreviation • design view: A representation comprised of one or more design elements to address a set of design concerns from a specified design viewpoint. See also: design concern, design element, design viewpoint. • design viewpoint: The specification of the elements and conventions available for constructing and using a design view. See also: design view. • diagram (type): A logically coherent fragment of a design view, using selected graphical icons and conventions for visual representation from an associated design language, to be used for representing selected design elements of interest for a system under design from a single viewpoint See also: design subject.
  6. 6. 6 © Copyright reserved SDD의 conceptual model SDD는 다음의 정보들을 커버한다. 1) Database design description 2) Database detailed design description 3) High-level software design description 4) Interface description 5) Low-level software design description 6) System description 7) System element description
  7. 7. 7 © Copyright reserved SDD의 conceptual model SDD는 디자인과 이해관계가 있는 자들(design stakeholders)에 의해 표현된다. 디자인과 이해관계가 있는 자들은 아래와 같다. 1) Users 2) Developers 3) Software designers 4) System integrators 5) Maintainers 6) Acquirers 7) Project managers
  8. 8. 8 © Copyright reserved SDD의 conceptual model SDD는 design view를 이용하여 구성된다. Design view는 하나 이상의 design concern을 표현한다. Design element의 구성 요소 1. Design entities 2. Design relationships 3. Design attributes 4. Design constraints
  9. 9. 9 © Copyright reserved Conceptual model: Top view Design entity Design relationship
  10. 10. 10 © Copyright reserved Conceptual model: Top view one or more Design Views are part of a Software Design Description Design Rationale is part of a Design View Design Viewpoint conforms to Design View Design View governs Design Viewpoint • design view: A representation comprised of one or more design elements to address a set of design concerns from a specified design viewpoint. • design viewpoint: The specification of the elements and conventions available for constructing and using a design view. • design rationale: Information capturing the reasoning of the designer that led to the system as designed, including design options, trade-offs considered, decisions made, and the justifications of those decisions.
  11. 11. 11 © Copyright reserved Conceptual model: Top view One or more Design Concerns have Design stakeholder One or more Design Stakeholders are important to Design Concern • design stakeholder: An individual, organization, or group (or classes thereof playing the same role) having an interest in, or design concerns relative to, the design of some software item. • design concern: An area of interest with respect to a software design.
  12. 12. 12 © Copyright reserved Conceptual model: Top view One or more Design Elements which are parts of Design Language define Design Viewpoint Design Overlay or Design Language is an realization of Diagram Type • design overlay: A representation of additional, detailed, or derived design information organized with reference to an existing design view. • diagram (type): A logically coherent fragment of a design view, using selected graphical icons and conventions for visual representation from an associated design language, to be used for representing selected design elements of interest for a system under design from a single viewpoint
  13. 13. 13 © Copyright reserved Conceptual model: Design elements
  14. 14. 14 © Copyright reserved SDD의 contents SDD에 포함되어야 하는 내용들은 다음과 같다. – SDD의 identification – Identified design stakeholder – Identified design concerns – Selected design viewpoints – Design views – Design overlays – Design rationale
  15. 15. 15 © Copyright reserved SDD의 identification SDD는 다음의 정보를 포함해야 한다. – Date of issue, Status – Scope – Issuing organization – Authorship(responsibility or copyright information) – References – Context – One or more design languages for each design viewpoint used – Body – Summery – Glossary – Change history
  16. 16. 16 © Copyright reserved Design stakeholder와 그들의 concerns SDD는 design subject에 대한 design stakeholder를 식별 해야 한다. SDD는 각각의 식별된 design stakeholder의 design concern을 식별해야 한다. SDD는 각각의 식별된 design concern을 설명해야 한다.
  17. 17. 17 © Copyright reserved Design view SDD는 1개 혹은 그 이상의 Design views로 구성된다. 각각의 Design View는 그것을 통제하는 design viewpoint에 부합하여야 한다. Design View의 목적은 1) Design subject에 존재하는 design concern을 설명하기 위해 2) Design stakeholder가 특정 관점으로 기술된 design detail에 집중하고 관련 요구사항을 효과적으로 설명하 도록 하기 위해 각각의 design view는 design viewpoint에 의해 제어되는 기술되어 있는 design concern을 설명해야 한다.
  18. 18. 18 © Copyright reserved Design view SDD는 다음의 조건을 만족하면 complete하다 1) 각각의 식별된 design concern이 최소한의 design view 의 topic일 때 2) 모든 design 속성이 각각의 design concern으로부터 개 선되어져 나온 것일 때, 여기서의 design concern은 모 든 design entity와 그와 관련된 view의 relationship에 대해 기술되어 있다. 3) 모든 design constraint가 적용되었을 때
  19. 19. 19 © Copyright reserved Design view Design view의 design element간에 conflict가 없으면 SDD는 consistent하다고 볼 수 있다.
  20. 20. 20 © Copyright reserved Design viewpoint SDD에서 각각의 design view에 대해 그것을 제어하는 design viewpoint가 정확하게 하나가 있어야 한다. 각각의 design viewpoint는 다음을 기술해야 한다. - Viewpoint name - Viewpoint의 주제인 design concerns - Viewpoint에 의해 정의된 design element, 특별히 viewpoint에 의해 소개되거나 사용된 design entity, attribute, relationship, constraint 의 type. 이런 element는 1개 혹은 그 이상의 디자인 언어에 의해 realize된다. - Viewpoint기반의 분석적 방법이나 design view를 구성할 때 사용되 는 다른 operations - Design을 이해하고 평가하기 위한 범주 - (가능한 경우) viewpoint의 source
  21. 21. 21 © Copyright reserved Design viewpoint 추가적으로 design viewpoint specification은 viewpoint를 이용하여 다음의 정보를 제공할 수도 있다. - View에 적용될 공식 또는 비공식적인 consistency 및 completeness test - View에 적용될 평가 및 분석 기술 - View의 합성이나 구성을 지원하는 휴리스틱, 패턴 또는 다른 가이드라인 SDD는 각각의 선택된 viewpoint의 선정이유를 포함해야 한다. SDD에서 식별된 각각의 design concern은 적어도 하나의 사용을 위한 design viewpoint에 의해 고안되어야 한다.
  22. 22. 22 © Copyright reserved Design viewpoint Design element는 design view에서 발생하는 어떤 item이 다. Design element는 다음의 것들 중 하나가 될 수 있다: • design entity • design relationships • design attribute • design constraint SDD에서의 각각의 design element는 name, type, contents를 포함해야 한다.
  23. 23. 23 © Copyright reserved Design viewpoint 각각의 design elements의 타입은 정확하게 하나의 design viewpoint정의 내에서 소개되어야 한다. Design element는 하나 혹은 그 이상의 design view에서 사용될 수 있다.
  24. 24. 24 © Copyright reserved Design relationships Design relationship은 두 개 혹은 그 이상의 design entity 들 사이의 연합 혹은 관계에 대한 명명을 한다. Design relationship은 design entity들에 대한 fact를 설명 한다. SDD에서 각각의 design relationship은 name, type을 가져 야 한다. Design relationship은 relationship에 참여하는 design entity를 식별해야 한다.
  25. 25. 25 © Copyright reserved Design constraints Design constraint는 design view의 element이다. • 하나의 design element로부터 다른 design element에 부과된 rule혹은 restriction • 그 design element는 design entity, design attribute, design relationship이 될 수 있음 각각의 design constraint는 name과 type을 가져야 한다. Design constraint는 source와 target design entity를 식별 해야 한다.

×