Universal Patterns: How They Can Help You Develop Your HR Data Model

3,506 views

Published on

Len Silverston and Paul Agnew have discovered in decades of data modeling that there are "universal patterns" that apply to well over 50 percent of data model constructs and that can be reused for many applications, including human resources. For example, a roles pattern may be used to consistently model employees, contractors, workers, and other roles. A hierarchy pattern may be used to consistently model employee, position and organizational structures. A classification pattern may be used to consistently model demographics of employees as well as other parties.

In this webinar, Silverston and Agnew will define what they mean by "universal patterns" and explain how these patterns can be applied to the development of human resource data models. They will focus on some of the most common re-usable patterns, including roles, hierarchies, and classifications that can aid in the development of consistent, flexible and powerful human resources data models.

Published in: Technology
1 Comment
5 Likes
Statistics
Notes
No Downloads
Views
Total views
3,506
On SlideShare
0
From Embeds
0
Number of Embeds
155
Actions
Shares
0
Downloads
143
Comments
1
Likes
5
Embeds 0
No embeds

No notes for slide
  • Paul- Good morning to you all. First, I would just like to say, on behalf of myself and my co-author and partner Len, thank you so much for donating some of your valuable time to attend this webinar, entitled “Using Universal Patterns to Build Your HR Data Model”. We hope and believe that you will find it a new and interesting approach for data modeling the information in you organizations. As we have limited time and a lot of material to go through we will jump straight in with a question…. [CLICK TO NEXT SLIDE]…….
  • Universal Patterns: How They Can Help You Develop Your HR Data Model

    1. 1. Using Universal Patterns to Build Your HR Data Model
    2. 2. Purpose and Agenda <ul><li>Purpose: </li></ul><ul><ul><li>Show value of using patterns in HR modeling </li></ul></ul><ul><li>Agenda </li></ul><ul><ul><li>Introduction </li></ul></ul><ul><ul><li>Patterns </li></ul></ul><ul><ul><ul><li>Declarative role </li></ul></ul></ul><ul><ul><ul><li>Contextual role </li></ul></ul></ul><ul><ul><ul><li>Classification </li></ul></ul></ul><ul><ul><li>Conclusion </li></ul></ul>
    3. 3. What is a Pattern?
    4. 4.
    5. 5.
    6. 6.
    7. 7.
    8. 8.
    9. 9.
    10. 10.
    11. 11.
    12. 12.
    13. 13.
    14. 14. Universal Data Modeling Patterns
    15. 15. Specific Modeling Vs. Generalized Modeling
    16. 16.
    17. 17. When Should I use a Specific or Generalized Pattern? Specific – Understand requirements Generalized - Flexibility
    18. 18. Why not Conceptual, Logical and Physical?
    19. 19. The Patterns
    20. 20. Declarative Roles
    21. 21.
    22. 22.
    23. 23.
    24. 24. Freddy Mercury Bono Ice T Virgin Records
    25. 25.
    26. 26. Freddy Mercury, Bono, Ice T, Virgin Records. Employee Advocate, Employee, Department
    27. 27. Contextual roles
    28. 28.
    29. 29. Freddy Mercury Bono Ice T Freddy’s Review. Ice T’s Review. Freddy’s Review.----Bono Freddy’s Review.----Ice T Virgin Records
    30. 30.
    31. 31. Freddy Mercury Bono Ice T Virgin Records Employee, Internal Organization, Employee Advocate, Department Freddy’s Review. Ice T’s Review. Freddy’s Review.----Bono Freddy’s Review.----Ice T
    32. 32.
    33. 33. Employee, Internal Organization, Reviewer, Mentor, Employee Advocate, Subject Freddy Mercury Bono Ice T Virgin Records Freddy’s Review. Ice T’s Review. Bono –Reviewer—Freddy’s Review, Freddy Mercury—Subject—Freddy’s Review Ice T – Mentor – Freddy’s Review
    34. 34. Freddy Mercury—Subject—Freddy’s Review Bono –Freddy’s Review, Ice T – Freddy’s Review Employee, Internal Organization, Reviewer, Mentor, Employee Advocate, Department, Subject Freddy Mercury Bono Ice T Virgin Records Freddy’s Review. Ice T’s Review.
    35. 35. Classifications
    36. 36.
    37. 37. Programmer, Admin Support. Typing, Negotiation. Management, Technical. Management Job 1 Sales support Job 2 Tech support Job 3 Management Job 1- Negotiation Tech Support Job 3- Technical
    38. 38.
    39. 39. Position Type, Skill Type Position Category Programmer (Position Type ), Admin Support (Position Type ), . Typing (Skill Type), Negotiation (Skill Type),. Management (Position Category) Technical. (Position Category) Management Job 1 Sales support Job 2 Tech support Job 3 Management Job 1- Negotiation Tech Support Job 3- Technical
    40. 40. Other Patterns <ul><li>Status </li></ul><ul><li>Business Rules </li></ul><ul><li>Hierarchies, recursive relationships </li></ul><ul><li>Contact mechanism </li></ul>
    41. 41. Value Proposition <ul><li>Time and $ </li></ul><ul><li>Quality systems </li></ul><ul><li>Enable integration </li></ul>
    42. 42. In Conclusion <ul><li>Not “Data Modeling for Dummies” </li></ul><ul><li>Systematic approach </li></ul>
    43. 43. Questions? <ul><li>[email_address] </li></ul><ul><li>[email_address] </li></ul>To license UDM models such as Universal Data Models for Human Resources, see: http://www.embarcadero.com/products/udm/index.html

    ×