SW 공부/OOP_OOAD_UML15 [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] 2.Inception Inception - Short initinal step (Feasibility Study) - Not the requirement phase - Go or Stop을 결정할 사람에게 보고할 자료를 만드는 정도의 단계 - Artifacts : Use-Case Model, Supplementary specification, Glossary Vision, Business Rules,... , erc. Requirements - Capabilities and conditions to which the system must conform → Requirements(요구사항)은 시스템이 준수해야 하는 기능 및 조건을 말하는 것 - In the UP, requirements are analyzed iterative.. 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. [UML] Component Diagram UML Components - component는 코드로 개발하는 단위 → class를 만듦 - Components interact with each other through interfaces. • Provided interface : Interface that the component realizes (provided services) → Ball symbols / output • Required interface : Interface that the component needs to function (expected services) → socket symbols / input - 3 standard ways to show provided and required interfaces in UML • .. 2022. 8. 29. [UML] Activity Diagram Activity Diagram - shows the flow of actions in system - shows the flow of operations in methods/functions * no flow of messages from one activity to another Activity Diagram Notations Activity : 일 (상태 X) / the core symbol / rectangle with rounded ends Transition : trigger가 없음, 앞에 activity가 끝나면 넘어감 / shows the flow (sequence) between activities Objects Activity Diagram vs Statechart Diagram - 둘다.. 2022. 8. 29. [UML] Statechart Diagram Statechart - FSM (Finite State Machine) - Formal Specification Model, 정형 명세 모델 - State machine (=Statechart) diagram is used as follows: – to model the possible states of a system or object (시스템 또는 객체의 가능한 상태를 모델링) – to show how state transitions occur as a consequence of events (이벤트 결과로 상태 전환이 어떻게 일어나는지) – to show what behavior the system or object exhibits in each state (각 state에서 어떤 행동을 하는지) .. 2022. 8. 29. [UML] Sequence Diagram Interation Diagrams - Interaction diagrams illustrate how objects interact via messages. (Dynamic object modeling) Sequence Diagram - Lifeline boxes : Represent the participants (roles) : 아래로 lifelines 표시됨 - Messages 3 Types of Messages Synchronous message : 무조건 Response message를 기다림 - Sender waits until it has received a response message before continuing. - An execution specification is insert.. 2022. 8. 29. 이전 1 2 다음
