1. 1

2. 2 Object Modeling XBRL-based Applications using UML: Developing Balanced-Scorecard Appraisal Systems Presented by Rob Nehmer Oakland University Rochester, Michigan USA

3. 3 Overview  Methodology  Adding methods to classes to form objects  Hierarchical reporting example  Balanced scorecard example  Conclusions

4. 4 Methodology  Reverse engineer  Augment UML model  Application generation

5. 5

6. 6 Extracting Class Diagrams  Map XBRL tags to class templates  Classes are XBRL structures  Attributes are instance variables of the class

7. 7 Adding Methods  Processing knowledge is defined as methods  Activity diagrams determine the processing knowledge  Communication and sequence diagrams supplement processing knowledge, especially in the dimension of time

8. 8 Adding Methods - Examples  [FR ID:tag, FR:tag]  [FR ID:, FR ID: ] [FR ID:, FR ID: ]

9. 9 Adding Methods - Examples  [FR ID:tag, GL ID:tagset]  [FR ID:, GL ID:entryDetail>]

10. 10 Hierarchical Example  Drill down from XBRL FR to GL details  Sales to particular customers

11. 11 Hierarchical Example 10207 East Shore, Maine Revenues C 64000

12. 12 Balanced Scorecard Example  Customer  Financial  Internal Business Processes  Learning and Growth

13. 13 Customer  Scenario:  Customer satisfaction score  measurableID is a reference to an external survey document  That document is an XML schema  The satisfaction score is 4.2  The measure is in “utils”

14. 14 Customer 554 Customer Satisfaction 123778 “reference to survey schema” 4.2 utils

15. 15 Financial  The example shows a sales account  That account is comprised of subaccounts

16. 16 Financial 41000 Sales 41005 Hampton Company, Sales C 15000 41062 Campania Company, Sales C 8000

17. 17 Internal Business Processes  We have the sales data already  Link this data back to inventory  This can be done through a finished goods inventory listing

18. 18 Internal Business Processes 10340 Coats 10347 D 29000 10347 Winter Coats D 7000 10347 Winter Coats D 16000

19. 19 Learning and Growth  Time is the relevant dimension here  Use numbers from documents created over time  We use revenues by product line in the following example

20. 20 Learning and Growth 2072 Sales Report#: 3905 2006-3-31 23500

21. 21 Conclusions  GL can be used in OO and UML design environments  GL can be used as an alternative to full ERP commitments  Further research