Elaboration4 [OOAD] 3-3. Elaboration - OOI Elaboration - OOI (Object Oriented Implentation) - Systemetic 하게 기계적으로 구현하는 단계 - OOA / OOD를 잘해놓으면 Implementation 단계가 쉬워진다. Designing for Visibility - Visibility is the ability of an object to “see” or “have a reference to” another object. When an object A sends a message to an object B, B must be visible to A. - 4 common ways that visibility can be achieved from object A to object B: Attribute v.. 2022. 8. 29. [OOAD] 3-2. Elaboration - OOD Iteratively Analysis and Design - In iterative development, a transition from requirements/OOA to design/implementation occur in each iteration. - iteration (매 3주)마다 mini-waterfall(Requirement Analysis -Design-구현- 테스트)을 진행해서 계속 반복! Logical Architecture and UML Package Diagrams - A software architecture is the set of significant decisions about the organization of a software system, : the selecti.. 2022. 8. 29. [OOAD] 3-1. Elaboration - OOA Elaboration (정교화) - Elaboration is the initial series of iterations during which: → The core, risky software architecture is programmed and tested. / 핵심 SW Architecutre 프로그램 및 테스팅 → Most requirements are discovered and stabilized. / 요구사항 발견 및 안정화 → The major risks are mitigated or retired. / 주요 위험은 완화되거나 폐기 UP Artifacts in Elaboration - OOA (Analysis) - Domain Models - Use-Case Model Domain Mode.. 2022. 8. 29. [OOAD] 1. Introduction of Object-Oriented Analysis and Design Object-Oriented Analysis and Design - Object-Oriented Analysis (OOA, 객체 지향 분석) : Discover the domain concepts/objects (the objects of the problem domain) : domain concepts/objects 찾는 단계이다. → Define use cases / Define Domail Model - Object-Oriented Design (OOD, 객체 지향 설계) : Define software objects (static) → Define interaction diagram : Object을 구성하는 Attributes와 Operation을 정의한다. : Define how they c.. 2022. 8. 29. 이전 1 다음
