TAILIEUCHUNG - Lecture Software engineering: Lecture 6 - Ivan Marsic

Lecture 6: Domain modeling. The main contents of this chapter include all of the following: Identifying concepts, concept attributes, concept associations, contracts: preconditions and postconditions. | Ivan Marsic Rutgers University LECTURE 6: Domain Modeling Topics Identifying Concepts Concept Attributes Concept Associations Contracts: Preconditions and Postconditions Domain Modeling Why? —The goal of domain modeling is to understand how system-to-be will work Requirements analysis determined how users will interact with system-to-be (external behavior) Domain modeling determines how elements of system-to-be interact (internal behavior) to produce the external behavior How? —We do domain modeling based on sources: Knowledge of how system-to-be is supposed to behave (from requirements analysis, ., use cases) Studying the work domain (or, problem domain) Knowledge base of software designs Developer’s past experience with software design Use Cases vs. Domain Model (b) (a) In use case analysis, we consider the system as a “black box” In domain analysis, we consider the system as a “transparent box” Example: ATM Machine (b) (a) Building Domain Model from Use Cases .

Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.