Äriprotsesside modelleerimine ja automatiseerimine Loeng 6 Protsesside juhtimine, jälgimine Eesmärgid ja mõõdikud Enn Õunapuu Enn.ounapuu@ttu.ee
Sisu MDA Eesmärgid Nõuded Mõõtmised Tasakaalustatud tulemuskaart Teie töös kuidas kasutada?
Model driven approach The model-driven approach is how the current IT solutions can be realized because the current IT solutions no longer satisfy the modern-time requirements. The creation and modification of IT solutions today are costly, time-consuming and mainly manual work. We need new approaches. A promising possibility is to use a Model-Driven engineering approach. One of the central models in this approach is the business process model. Goal model, data model, Integration model, Interface models are also used.
Federal Enterprise Architecture Framework v2 The Federal Enterprise Architecture Framework v2 describes a suite of tools to help government planners implement the Common Approach. At its core is the Consolidated Reference Model (CRM), which equips OMB and Federal agencies with a common language and framework to describe and analyze investments. It consists of a set of interrelated reference models that describe the six sub-architecture domains in the framework: Strategy Business Data Applications Infrastructure Security
Federal Enterprise Architecture (FEA) Business-Driven Approach Performance Reference Model (PRM) Government-wide Performance Measures & Outcomes Line of Business-Specific Performance Measures & Outcomes Business Reference Model (BRM) Lines of Business Agencies, Customers, Partners Service Component Reference Model (SRM) Service Layers, Service Types Components, Access and Delivery Channels Data Reference Model (DRM) Business-focused data standardization Cross-Agency Information exchanges Technical Reference Model (TRM) Service Component Interfaces, Interoperability Technologies, Standards Recommendations Component-Based Architecture
The FEA Business Reference Model (BRM) is a framework for describing the Lines of Business performed by the Federal Government independent of the Agencies that perform them Citizen to Government Access Channels Government Employee to Employee Access Channels Inter-Agency Telephone -Voice -Interactive Web Services Program Admin Public Asset Management Marketable Asset Management Defense & Nat l Security Ops Diplomacy & Foreign Relations Disaster Management Domestic Economy Education Energy Management Insurance Public Health Recreation & National Resources Social Services R&D & Science Telephone -Voice -Interactive E-system to System/ Web Services E-system to System Legislative Management Business Management of Information IT Management, Regulator Management Planning and Resource Allocation Human Resources, Financial Management Admin Supply Chain Management Public/ Private Partnerships Internet/ Portal Services for Citizens Services to Citizens Public/Private Partnerships Fax Kiosk Support Delivery of Services Controls and Oversight Public Affairs Internal Risk Management and Mitigation Federal Financial Assistance Internal Operations / Infrastructure Human Resources, Financial Management Admin Supply Chain Management 10/6/2014 8 Fax Face to Face Compliance Regulated Regulated Activity Activity Approval Approval Consumer Safety Safety Environmental Management Law Law Enforcement Legal Revenue Revenue Collection Collection Trade Trade (Import/Export) (Import/Export) Transportation Workforce Workforce Management Management Intranet/ Portal Face to Face Mail Mail
MDA perspectives 16
Metamudel 17
Context perspective 18
Goal orientation What are goals? The granularity of goals and their relationship to requirements and assumptions Goal types and categories Types of goals: behavioral goals vs. soft goals Goal categories: functional goals vs. non-functional goals The central role of goals in the RE process
What are goals? Goal = prescriptive statement of intent the system should satisfy through cooperation of its agents "prescriptive statement": in optative mood shall, should, must,... e.g. Train doors shall be closed while the train is moving Loan periods shall be limited to 2 weeks formulated in terms of problem world phenomena "system": system-as-is, system-to-be software + environment "agent": active system component responsible for goal satisfaction
Goal satisfaction requires agent cooperation Maintain [SafeTransportation] on-board train controller + tracking system + station computer + passenger + train driver +... Achieve [BookCopyReturnedToShelves] patron + staff + library software Agent = role, rather than individual must restrict its behavior to meet its assigned goals must be able to monitor/control phenomena involved in assigned goals Agent types software (software-to-be, legacy software, foreign software) device (sensor, actuator,...) human
Goals vs. domain properties Domain property = descriptive statement about environment indicative mood: is", are", etc --not prescriptive e.g. If train doors are open, they are not closed A borrowed book is not available for other patrons The distinction between goals & domain properties is essential for RE... goals can be negotiated, weakened, prioritized domain properties cannot both required in requirements documentation
The granularity of goals Goals can be stated at different levels of abstraction Higher-level goals: strategic, coarse-grained - "50% increase of transportation capacity - Effective access to state of the art Lower-level goals: technical, fine-grained - Acceleration command sent every 3 secs - Reminder issued by end of loan period if no return The finer-grained a goal, the fewer agents required for its satisfaction
Goals, requirements & expectations Requirement = goal assigned to single agent in software-to-be "doorstate = closed while measuredspeed 0" TrainController Acceleration command sent every 3 secs StationComputer Expectation = goal assigned to single agent in environment prescriptive assumption on environment cannot be enforced by software-to-be (unlike requirements) Train left when doors open at destination Passenger
Statement typology revisited in the presence of goals Cf. general terminology introduced in Chap. 1... software requirement requirement system requirement goal involving multiple agents incl. software-to-be (prescriptive) assumption expectation (descriptive) assumption hypothesis Statement Prescriptive Descriptive Multi-agent goal Single-agent goal Domain property Domain hypothesis Requirement Expectation Subtype
Goal types Behavioral goals: prescribe behaviors vs. Soft goals: state preferences among alternative behaviors Goal Behavioral goal Soft goal Subtype Achieve Maintain/Avoid
Goal types: behavioral goals Prescribe intended system behaviors declaratively implicitly define maximal sets of admissible agent behaviors Can be satisfied in a clear-cut sense: YES or NO goal satisfaction, formal analysis Used for building operation models to meet them Worst-case stopping distance maintained Reminder sent if book not returned on time
Behavior goals prescribe sets of desired behaviors DoorsClosed WhileMoving moving closed stopped closed stopped open stopped closed moving closed
Behavioral goals: subtypes and specification patterns (1) Achieve [TargetCondition]: [if CurrentCondition then] sooner-or-later TargetCondition Achieve [BookRequestSatisfied]: if a book is requested then sooner-or-later a copy of the book is borrowed by the requesting patron Achieve [FastJourney]: if train is at some platform then within 5 minutes it is at next platform Achieve Current Condition Target Condition time
Behavioral goals: subtypes and specification patterns (2) Maintain [GoodCondition]: - [if CurrentCondition then] always GoodCondition - always (if CurrentCondition then GoodCondition) Maintain [DoorsClosedWhileMoving]: - always (if a train is moving then its doors are closed) Maintain [WorstCaseStoppingDistance]: - always (if a train follows another then - its distance is sufficient to allow the other to stop suddenly) Maintain Current Condition Good Condition Good Condition Good Condition time
Behavioral goals: subtypes and specification patterns (3) Accuracy goals are usually of type Maintain Maintain [AccurateBookClassification]: - if a book is registered in the library directory then - always its keyword-based classification reflects its covered topics Avoid [BadCondition]: dual of Maintain... - [if CurrentCondition then] never BadCondition Avoid [BorrowerLoansDisclosed]: never patron loans disclosed to other patrons Many security goals are Avoid goals
Goal types: soft goals Capture preferences among alternative behaviors Cannot be satisfied in clear-cut sense: more satisfied in one option, less satisfied in another goal satisficing, qualitative analysis Used for comparing options to select preferred Often take the form Maximize / Minimize, Incresase / Reduce, Improve,... Stress conditions of air traffic controllers shall be educed The workload of library staff shall be reduced The bibliographical search engine shall be usable by non-cs students
Goal categories Classification into functional, quality, development goals Categories may overlap; boundary not always clear unlike goal types Functional goals prescribe intended services to be provided by the system used for building operational models of such services - use cases, state machines (see later) e.g. - Passengers transported to their destination - Train acceleration computed - Book request satisfied"
Goal categories: non-functional goals (1) Quality goals (not to be confused with soft goals, cf. book p. 271) about quality of service... security "info about other patrons kept confidential safety "worst-case stopping distance maintained accuracy measured speed = physical speed book displayed as available iff there is a copy in shelves performance acceleration command sent every 3 seconds usability interoperability,... Development goals about quality of development cost, deadline, variability, maintainability, reusability, etc.
Goal categories (2) goal functional satisfaction information quality development usability... safety security accuracy performance......... confidentiality availability integrity time space...... See book, Fig. 7.5 p. 269 Helpful for eliciting overlooked application-specific instances through taxonomy browsing
Using goal types & categories Lightweight specification patterns Heuristic rules for elicitation, validation, reuse, conflict management,... "Is there any conflict between Information goals and Confidentiality goals? "Confidentiality goals are Avoid goals on sensitive info "Safety goals have highest priority in conflict resolution More specific types & categories more specific heuristics
37
Dell inspired example Strategic goal online ordering 24 hours to get product Process subgoals 18 hours for produstion, 6 hours for logistics Up to individual goals
Measurement scales Nominal Ordinal Interval Ratio
Nominal scale At the nominal scale, i.e., for a nominal category, one uses labels; for example, rocks can be generally categorized as igneous, sedimentary and metamorphic. For this scale, some valid operations are equivalence and set membership. Nominal measures offer names or labels for certain characteristics. Variables assessed on a nominal scale are called categorical variables; see also categorical data.
Ordinal scale Rank-ordering data simply puts the data on an ordinal scale. Ordinal measurements describe order, but not relative size or degree of difference between the items measured. In this scale type, the numbers assigned to objects or events represent the rank order (1st, 2nd, 3rd, etc.) of the entities assessed. A scale may also use names with an order such as: "bad", "medium", and "good"; or "very satisfied", "satisfied", "neutral", "unsatisfied", "very unsatisfied." An example of an ordinal scale is the result of a horse race, which says only which horses arrived first, second, or third but include no information about race times. Another is the Mohs scale of mineral hardness, which characterizes the hardness of various minerals through the ability of a harder material to scratch a softer one, saying nothing about the actual hardness of any of them.
Interval scale Quantitative attributes are all measurable on interval scales, as any difference between the levels of an attribute can be multiplied by any real number to exceed or equal another difference. A highly familiar example of interval scale measurement is temperature with the Celsius scale. In this particular scale, the unit of measurement is 1/100 of the difference between the melting temperature and the boiling temperature of water at atmospheric pressure. The "zero point" on an interval scale is arbitrary; and negative values can be used. The formal mathematical term is an affine space (in this case an affine line). Variables measured at the interval level are called "interval variables" or sometimes "scaled variables" as they have units of measurement.
Ratio measurement Most measurement in the physical sciences and engineering is done on ratio scales. Mass, length, time, plane angle, energy and electric charge are examples of physical measures that are ratio scales. The scale type takes its name from the fact that measurement is the estimation of the ratio between a magnitude of a continuous quantity and a unit magnitude of the same kind (Michell, 1997, 1999). Informally, the distinguishing feature of a ratio scale is the possession of a non-arbitrary zero value. For example, the Kelvin temperature scale has a non-arbitrary zero point of absolute zero, which is denoted 0K and is equal to -273.15 degrees Celsius. This zero point is non arbitrary as the particles that compose matter at this temperature have zero kinetic energy.
Context perspective 44
Motivation extension metamodel 45
Motivational Concepts -stakeholder 46
Motivational concepts - driver 47
Motivational concepts- assessment 48
Motivational concepts - Goal 49
Motivational concepts - requirement 50
Motivational concepts - principle 51
53
Enterprise objectives balanced scorecard
Questions? 57