Decision Modeling with DMN OMG（决策建模与静息,OMG）.pdfVIP

An Introduction to Decision Modeling with DMN Building a Decision Requirements Model using the new Decision Model and Notation (DMN) makes for better business analysis and improved system requirements. The Object Management Group has recently adopted the Decision Model and Notation standard. Here’s why you should use it to define your decision requirements. Why Model Decisions Experience shows that there are three main reasons for defining decision requirements as part of an overall requirements process: 1. Current requirements approaches don’t tackle the decision-making that is increasingly important in information systems. 2. While important for all software development projects, decision requirements are especially important for projects adopting business rules and advanced analytic technologies. 3. Decisions are a common language across business, IT and analytic organizations improving collaboration, increasing reuse, and easing implementation. Gaps in Current Requirements Approaches Today organizations use a variety of techniques to accurately describe the requirements for an information system. Most systems involve some workflow and this is increasingly described by business analysts in terms of business process models