Capturing	
  and	
  Sharing	
  Domain	
  
Knowledge	
  with	
  Business	
  Rules	
  
Lessons	
  Learned	
  from	
  a	
  Global	
  So<ware	
  Vendor	
  	
  
All	
  Started	
  with	
  an	
  ObservaAon	
  
2	
  
One	
  minor	
  change	
  in	
  a	
  UK	
  
regula2on	
  (rule	
  for	
  growth	
  
rate	
  of	
  insurance	
  funds)	
  	
  
A	
  significant	
  ripple	
  effect	
  
and	
  maintenance	
  effort	
  
which	
  lasted	
  for	
  6	
  months!	
  
Our	
  Working	
  Hypothesis	
  
3	
  
Would	
  a	
  systema2c	
  management	
  of	
  
these	
  rules	
  decrease	
  maintenance	
  
costs	
  and	
  increase	
  reuse?	
  
Many	
  of	
  the	
  “rules”	
  are	
  the	
  
same	
  for	
  the	
  same	
  region,	
  
domain,	
  or	
  company	
  (customer)	
  
What	
  are	
  Business	
  Rules?	
  
4	
  
Business	
  rules	
  are:	
  
•  Statements	
  that	
  define	
  or	
  constrain	
  	
  
par2cular	
  aspects	
  of	
  the	
  business	
  
Used	
  to:	
  
•  Specify	
  the	
  behavior	
  of	
  a	
  system	
  under	
  development	
  
•  Specify	
  how	
  a	
  system	
  should	
  be	
  used	
  
[The	
  Business	
  Rule	
  Group,	
  2000	
  ]	
  
Outline	
  of	
  the	
  Talk	
  
Summary	
  
Study	
  Design	
  
Findings	
  
MoAvaAon	
  
2	
  
1	
  
3	
  
4	
  
5	
  
Research	
  QuesAons	
  
6	
  
1.	
  How	
  do	
  prac22oners	
  perceive	
  
business	
  rules	
  and	
  which	
  types	
  exist?	
  
2.	
  How	
  do	
  prac22oners	
  capture	
  
and	
  maintain	
  business	
  rules?	
  
3.	
  How	
  are	
  business	
  rules	
  
used	
  in	
  soYware	
  projects?	
  
4.	
  How	
  does	
  RE	
  pracAces	
  impact	
  the	
  
usage	
  and	
  management	
  of	
  rules?	
  
Research	
  Method	
  
•  Exploratory,	
  qualita2ve	
  research	
  
•  Semi-­‐structured	
  interviews	
  
–  open	
  ques2ons	
  
•  Sec2ons:	
  
–  About	
  you	
  	
  
–  Requirements	
  engineering	
  	
  
–  Business	
  rules	
  
•  90	
  minutes	
  
•  2-­‐3	
  interviewers	
  per	
  session	
  
7	
  
8	
  
#	
   Roles	
   Exp(Y)	
   Domain	
  
P1	
  
Domain	
  consultant,	
  business	
  process	
  manager,	
  
requirements	
  reviewer	
  
13	
  	
   Insurance	
  	
  
P2	
  
Business	
  process	
  manager,	
  domain	
  consultant,	
  
program	
  manager	
  
20	
   Insurance	
  
P3	
   Developer,	
  project	
  manager,	
  analyst	
   4	
   SoYware,	
  Banking	
  
P4	
   Developer,	
  maintenance	
  lead,	
  project	
  manager	
   20	
  
Telecom,	
  Insurance,	
  
Power	
  
P5	
   Developer,	
  soYware	
  architect,	
  project	
  manager	
   12	
  	
   Telecom,	
  Finance	
  
P6	
   SoYware	
  architect,	
  program/delivery	
  manager	
   10	
   Automo2ve	
  and	
  Telecom	
  
P7	
   Program	
  manager,	
  product	
  manager	
   16	
   Finance	
  
P8	
   Project	
  manager,	
  program	
  manager	
   21	
   Finance	
  
P9	
   Product	
  manager,	
  presales	
  lead	
   17	
   Banking,	
  Finance	
  
P10	
   Tester,	
  lead	
  underwriter,	
  program	
  manager	
   14	
   Banking,	
  Finance	
  
P11	
   Delivery	
  center	
  head	
   18	
   Finance	
  
Overview	
  of	
  ParAcipants	
  
9	
  
Result	
  SummarizaAon	
  
10	
  
Interviews	
  
17	
  Findings	
  
Take	
  minutes	
  
Group	
  quotes	
  by	
  
quesAon	
  	
  
Group	
  similar	
  
quotes	
  
Describe	
  
findings	
  
Statement	
  must	
  be	
  observed	
  twice	
  at	
  least	
  
Sent	
  to	
  par2cipant	
  within	
  48	
  h	
  
Independent	
  tagging	
  of	
  quotes	
  
Result	
  SummarizaAon	
  
11	
  
Interviews	
  
17	
  Findings	
  
Take	
  minutes	
  
Group	
  quotes	
  by	
  
quesAon	
  	
  
Group	
  similar	
  
quotes	
  
Describe	
  
findings	
  
Outline	
  of	
  the	
  Talk	
  
Summary	
  
Study	
  Design	
  
Findings	
  
MoAvaAon	
  
2	
  
1	
  
3	
  
4	
  
12	
  
PercepAons	
  of	
  Business	
  Rules	
  
13	
  
Stakeholders	
  have	
  
different	
  percepAons	
  of	
  
business	
  rules	
  depending	
  
on	
  their	
  roles	
  and	
  
experience	
  
27	
  Types	
  of	
  Business	
  Rules	
  were	
  MenAoned	
  
14	
  
#	
   Rule	
  Type	
  
Times	
  
MenAoned	
  
1	
   Valida2ons	
  rules	
  &	
  value	
  ranges	
   7	
  
2	
   System	
  /	
  applica2on	
  specific	
  rules	
   4	
  
3	
   Calcula2on	
  rules	
   4	
  
4	
   Access	
  control	
  rules	
   4	
  
5	
   External	
  system	
  interfaces	
   3	
  
6	
   Laws	
  &	
  regula2ons	
   3	
  
7	
   Sequencing	
  /	
  control	
  flow	
   3	
  
8	
   Geography	
  specific	
  rules	
   3	
  
27	
  Types	
  of	
  Business	
  Rules	
  were	
  MenAoned	
  
15	
  
#	
   Rule	
  Type	
  
Times	
  
MenAoned	
  	
  
9	
   Business	
  process	
  rules	
   3	
  
10	
   Procedural	
  /	
  Opera2onal	
  rules	
   3	
  
11	
   User	
  interface	
  rules	
   2	
  
12	
   Company	
  policies	
   2	
  
13	
   Time	
  restric2ons	
  	
   2	
  
14	
   Dynamic	
  rules	
   2	
  
15	
   Defini2ons	
   2	
  
Capturing	
  and	
  Maintaining	
  Business	
  Rules	
  
Business	
  rules	
  are	
  
embedded	
  as	
  free	
  text	
  
anywhere	
  in	
  the	
  project	
  	
  
and	
  domain	
  
documenta2on	
  
16	
  
17	
  
no	
  separate	
  sec2on	
  for	
  business	
  rules	
  
You	
  can	
  find	
  business	
  rules	
  in	
  requirements	
  
specifica2ons,	
  source	
  documents,	
  process	
  
descrip2on,	
  marke2ng	
  brochures,	
  (telecom)	
  
regula,ons,	
  or	
  laws	
  
[P5]	
  
[P3]	
  
18	
  
The	
  use	
  of	
  formal	
  rule	
  
languages	
  and	
  rule	
  
engines	
  is	
  rather	
  
excep2onal	
  in	
  prac2ce	
  
Use	
  of	
  Business	
  Rules	
  
19	
  
Business	
  rules	
  are	
  
captured	
  and	
  used	
  not	
  
only	
  in	
  RE	
  but	
  also	
  in	
  	
  
other	
  project	
  ac2vi2es	
  
20	
  
Many	
  rules	
  were	
  discovered	
  
during	
  the	
  implementa2on	
  and	
  
tes2ng	
  when	
  we	
  needed	
  them.	
  
[P6]	
  
Externalized	
  business	
  
rules	
  facilitate	
  sharing	
  
knowledge	
  with	
  new	
  
team	
  members	
  and	
  a	
  
cross	
  projects	
  
21	
  
RE	
  PracAces	
  and	
  Business	
  Rules	
  
22	
  
Customers	
  expect	
  
soYware	
  vendors	
  to	
  
have	
  domain	
  knowledge	
  
and	
  to	
  “develop”	
  
business	
  rules	
  
RE	
  and	
  Business	
  Rules	
  
23	
  
Prac22oners	
  allocate	
  low	
  effort	
  for	
  
understanding	
  special	
  flows	
  (rules)	
  
The	
  lack	
  of	
  domain	
  knowledge	
  in	
  
development	
  teams	
  hinders	
  the	
  
capturing	
  of	
  business	
  rules	
  
RE	
  and	
  Business	
  Rules	
  
24	
  
To	
  iden2fy	
  the	
  right	
  level	
  of	
  detail	
  in	
  
documenta2on	
  is	
  difficult	
  (too	
  much	
  
informa2on	
  or	
  only	
  main	
  flows	
  
without	
  rules	
  and	
  excep2ons)	
  
Business	
  rules	
  (excep2ons)	
  represent	
  a	
  specific	
  
type	
  of	
  requirements	
  or	
  domain	
  knowledge,	
  
which	
  oYen	
  remains	
  tacit	
  
Outline	
  of	
  the	
  Talk	
  
Summary	
  
Study	
  Design	
  
Findings	
  
MoAvaAon	
  
2	
  
1	
  
3	
  
4	
  
25	
  
Business	
  Rules	
  =	
  Crucial	
  Domain	
  Knowledge	
  
•  SoYware	
  vendors	
  increasingly	
  rely	
  on	
  the	
  domain	
  knowledge	
  
•  Customers	
  expect	
  vendors	
  to	
  know	
  the	
  domain	
  very	
  well	
  
•  “Knowing”	
  the	
  domain,	
  the	
  restric2ons,	
  the	
  constraints,	
  and	
  
the	
  excep2ons	
  is	
  very	
  cost	
  intensive	
  
26	
  
ImplicaAon	
  for	
  Researchers	
  
27	
  
1.  Focus	
  on	
  the	
  knowledge	
  and	
  documenta2on	
  
poten2als	
  of	
  business	
  rules	
  
2.  Extract	
  and	
  trace	
  rules	
  to	
  various	
  ar2facts	
  
3.  Develop	
  ques2on-­‐answering	
  systems	
  to	
  retrieve	
  the	
  
required	
  informa2on	
  depending	
  on	
  task	
  and	
  context	
  
28	
  
It	
  would	
  be	
  perfect	
  if	
  I	
  could	
  just	
  
select	
  a	
  component	
  or	
  a	
  feature	
  	
  
and	
  my	
  tool	
  show	
  me	
  the	
  most	
  
important	
  business	
  rules	
  	
  
which	
  I	
  should	
  take	
  care	
  of.	
  
[P9]	
  
29	
  
Business	
  rules:	
  The	
  
bomb	
  or	
  the	
  treasure?	
  
Exploratory	
  study	
  of	
  business	
  
rules	
  in	
  RE	
  pracAce	
  
Business	
  rules	
  =	
  an	
  asset	
  worth	
  
“externalizing”	
  (automaAcally?)	
  
17	
  findings	
  on	
  
types	
  of	
  rules,	
  
management	
  
and	
  use	
  
Uni	
  Hamburg,	
  Germany	
  
Prof.	
  Dr.	
  Walid	
  Maalej	
  	
  
maalej@informa2k.uni-­‐…	
  
mobis.informa2k.uni-­‐…	
  
maalejw	
  

More Related Content

PPTX
11 Towards a Research Agenda for Recommendation Systems in Requirements Engin...
PDF
Us and Them — A Study of Privacy Requirements Across North America, Asia, and...
PPTX
Why is Test Driven Development for Analytics or Data Projects so Hard?
PPTX
Operational Risk Management Data Validation Architecture
PDF
IT PROJECT SHOWSTOPPER FRAMEWORK: THE VIEW OF PRACTITIONERS
DOC
Prince 2: project managment Document Lessons learned report
PDF
PPTX
Cpe orientation
11 Towards a Research Agenda for Recommendation Systems in Requirements Engin...
Us and Them — A Study of Privacy Requirements Across North America, Asia, and...
Why is Test Driven Development for Analytics or Data Projects so Hard?
Operational Risk Management Data Validation Architecture
IT PROJECT SHOWSTOPPER FRAMEWORK: THE VIEW OF PRACTITIONERS
Prince 2: project managment Document Lessons learned report
Cpe orientation

What's hot (11)

PPTX
Rethinking Lessons Learned in the PMBoK Process Groups: A Model based on Peop...
DOC
Chap011
PPT
Enterprise Architecture Roles And Competencies V9
PPTX
Time to Money- Software Development for a Regulated Medical World
PPTX
Technology supported requirement handling an estimation
PDF
Distributed Software Development Process, Initiatives and Key Factors: A Syst...
PDF
D0704014018
PDF
Chapter 6
DOC
SPGregory_Resume
PDF
Project management
PDF
Exploring the frontiers of Agile Development in the Digital Era
Rethinking Lessons Learned in the PMBoK Process Groups: A Model based on Peop...
Chap011
Enterprise Architecture Roles And Competencies V9
Time to Money- Software Development for a Regulated Medical World
Technology supported requirement handling an estimation
Distributed Software Development Process, Initiatives and Key Factors: A Syst...
D0704014018
Chapter 6
SPGregory_Resume
Project management
Exploring the frontiers of Agile Development in the Digital Era
Ad

Viewers also liked (9)

PDF
Assisting Engineers in Switching Artifacts by using Task Semantic and Interac...
PDF
Invited Talk at TU Graz
PDF
Msr14 tutorial 4upload
PDF
Intention-Based Integration of Software Engineering Tools
PDF
2012 icse program comprehension
PDF
How Do Users Like This Feature? A Fine Grained Sentiment Analysis of App Revi...
PDF
On the Socialness of Software
PDF
Context aware software engineering and maintenance: the FastFix approach
PDF
Help! I need an empirical study for my PhD!
Assisting Engineers in Switching Artifacts by using Task Semantic and Interac...
Invited Talk at TU Graz
Msr14 tutorial 4upload
Intention-Based Integration of Software Engineering Tools
2012 icse program comprehension
How Do Users Like This Feature? A Fine Grained Sentiment Analysis of App Revi...
On the Socialness of Software
Context aware software engineering and maintenance: the FastFix approach
Help! I need an empirical study for my PhD!
Ad

Similar to Business Rules In Practice - An Empirical Study (IEEE RE'14 Paper) (20)

PDF
Sabrion_Consulting_Overview CPG Retail Apparel.pdf
PPT
software and vendor selection is imp nw a days with advent of tech
PDF
Equipment finance systems project guide "101"
PDF
Equipment finance projects guide "101"
PDF
Equipment finance systems project guide 101
PDF
Equipment finance systems project guide "101"
PDF
SHARE in Boston: z/OS Applications Adapting at the Speed of Business
PDF
Asset Finance Systems: Project Initiation "101"
PPT
Roadmap planning approach
PPTX
Contracts – the Missing Link: Utilizing Contract Management to Close the Gap ...
PPTX
Preparing for ASC 606
PDF
Asset Finance Systems: Project Initiation "101"
PDF
Robinatech_eTOM-Training
PDF
Charlotte FENG - What you need to know in 2014!
DOC
Togaf 9 template Preliminary Phase architecture principles
PDF
Agile and Cost Effective Compliance: Going Beyond Business Rules with Decisio...
PPTX
Software Requirements development
PPTX
Sucessful BPO Through Technology Enablement
PPTX
Capturing and documenting business processes and rules for agility
PDF
Rule-based Design. Managing complexity!
Sabrion_Consulting_Overview CPG Retail Apparel.pdf
software and vendor selection is imp nw a days with advent of tech
Equipment finance systems project guide "101"
Equipment finance projects guide "101"
Equipment finance systems project guide 101
Equipment finance systems project guide "101"
SHARE in Boston: z/OS Applications Adapting at the Speed of Business
Asset Finance Systems: Project Initiation "101"
Roadmap planning approach
Contracts – the Missing Link: Utilizing Contract Management to Close the Gap ...
Preparing for ASC 606
Asset Finance Systems: Project Initiation "101"
Robinatech_eTOM-Training
Charlotte FENG - What you need to know in 2014!
Togaf 9 template Preliminary Phase architecture principles
Agile and Cost Effective Compliance: Going Beyond Business Rules with Decisio...
Software Requirements development
Sucessful BPO Through Technology Enablement
Capturing and documenting business processes and rules for agility
Rule-based Design. Managing complexity!

More from Walid Maalej (17)

PDF
How Can Software Engineering Support AI
PDF
Can Development Work Describe Itself?
PPT
05 Making Tacit Requirements Explicit
PPTX
10 A Machine Learning Approach for Identifying Expert Stakeholders
PPTX
12 Leveraging Rule Deviations in IT Ecosystems for Implicit Requirements Elic...
PPT
08 Domain KnowledgeWiki for Requirements Elicitation
PPT
13 Continuous and Collaborative Validation: A Field Study of Requirements Kno...
PPTX
01 Using Defect Reports to Build Requirements Knowledge in Product Lines
PPT
07 Modeling and Managing Tacit Product Line Requirements Knowledge
PPTX
14 Reasoning on Requirements Knowledge to Support Creativity
PPT
03 How to Keep Domain Requirements Models Reasonably Sized
PPT
00 Opening: Why MaRK
PPT
04 The Papyrus tool as an Eclipse UML2-modeling environment for requirements
PPT
09 On Presuppositions in Requirements
PDF
From Work To Word
PDF
Team Weaver Demo Camp June 08
PDF
Potential And Challenges of Recommendation Systems for Software Development
How Can Software Engineering Support AI
Can Development Work Describe Itself?
05 Making Tacit Requirements Explicit
10 A Machine Learning Approach for Identifying Expert Stakeholders
12 Leveraging Rule Deviations in IT Ecosystems for Implicit Requirements Elic...
08 Domain KnowledgeWiki for Requirements Elicitation
13 Continuous and Collaborative Validation: A Field Study of Requirements Kno...
01 Using Defect Reports to Build Requirements Knowledge in Product Lines
07 Modeling and Managing Tacit Product Line Requirements Knowledge
14 Reasoning on Requirements Knowledge to Support Creativity
03 How to Keep Domain Requirements Models Reasonably Sized
00 Opening: Why MaRK
04 The Papyrus tool as an Eclipse UML2-modeling environment for requirements
09 On Presuppositions in Requirements
From Work To Word
Team Weaver Demo Camp June 08
Potential And Challenges of Recommendation Systems for Software Development

Recently uploaded (20)

PPTX
Trending Python Topics for Data Visualization in 2025
PPTX
Cybersecurity: Protecting the Digital World
PPTX
AMADEUS TRAVEL AGENT SOFTWARE | AMADEUS TICKETING SYSTEM
PDF
Ableton Live Suite for MacOS Crack Full Download (Latest 2025)
PDF
Top 10 Software Development Trends to Watch in 2025 🚀.pdf
DOCX
Modern SharePoint Intranet Templates That Boost Employee Engagement in 2025.docx
PPTX
Introduction to Windows Operating System
PDF
How to Make Money in the Metaverse_ Top Strategies for Beginners.pdf
PPTX
Tech Workshop Escape Room Tech Workshop
PDF
Microsoft Office 365 Crack Download Free
PDF
DuckDuckGo Private Browser Premium APK for Android Crack Latest 2025
PDF
Cost to Outsource Software Development in 2025
PDF
How Tridens DevSecOps Ensures Compliance, Security, and Agility
PPTX
GSA Content Generator Crack (2025 Latest)
PDF
Salesforce Agentforce AI Implementation.pdf
DOCX
How to Use SharePoint as an ISO-Compliant Document Management System
PDF
DNT Brochure 2025 – ISV Solutions @ D365
PDF
AI Guide for Business Growth - Arna Softech
PDF
How AI/LLM recommend to you ? GDG meetup 16 Aug by Fariman Guliev
PDF
EaseUS PDF Editor Pro 6.2.0.2 Crack with License Key 2025
Trending Python Topics for Data Visualization in 2025
Cybersecurity: Protecting the Digital World
AMADEUS TRAVEL AGENT SOFTWARE | AMADEUS TICKETING SYSTEM
Ableton Live Suite for MacOS Crack Full Download (Latest 2025)
Top 10 Software Development Trends to Watch in 2025 🚀.pdf
Modern SharePoint Intranet Templates That Boost Employee Engagement in 2025.docx
Introduction to Windows Operating System
How to Make Money in the Metaverse_ Top Strategies for Beginners.pdf
Tech Workshop Escape Room Tech Workshop
Microsoft Office 365 Crack Download Free
DuckDuckGo Private Browser Premium APK for Android Crack Latest 2025
Cost to Outsource Software Development in 2025
How Tridens DevSecOps Ensures Compliance, Security, and Agility
GSA Content Generator Crack (2025 Latest)
Salesforce Agentforce AI Implementation.pdf
How to Use SharePoint as an ISO-Compliant Document Management System
DNT Brochure 2025 – ISV Solutions @ D365
AI Guide for Business Growth - Arna Softech
How AI/LLM recommend to you ? GDG meetup 16 Aug by Fariman Guliev
EaseUS PDF Editor Pro 6.2.0.2 Crack with License Key 2025

Business Rules In Practice - An Empirical Study (IEEE RE'14 Paper)

  • 1. Capturing  and  Sharing  Domain   Knowledge  with  Business  Rules   Lessons  Learned  from  a  Global  So<ware  Vendor    
  • 2. All  Started  with  an  ObservaAon   2   One  minor  change  in  a  UK   regula2on  (rule  for  growth   rate  of  insurance  funds)     A  significant  ripple  effect   and  maintenance  effort   which  lasted  for  6  months!  
  • 3. Our  Working  Hypothesis   3   Would  a  systema2c  management  of   these  rules  decrease  maintenance   costs  and  increase  reuse?   Many  of  the  “rules”  are  the   same  for  the  same  region,   domain,  or  company  (customer)  
  • 4. What  are  Business  Rules?   4   Business  rules  are:   •  Statements  that  define  or  constrain     par2cular  aspects  of  the  business   Used  to:   •  Specify  the  behavior  of  a  system  under  development   •  Specify  how  a  system  should  be  used   [The  Business  Rule  Group,  2000  ]  
  • 5. Outline  of  the  Talk   Summary   Study  Design   Findings   MoAvaAon   2   1   3   4   5  
  • 6. Research  QuesAons   6   1.  How  do  prac22oners  perceive   business  rules  and  which  types  exist?   2.  How  do  prac22oners  capture   and  maintain  business  rules?   3.  How  are  business  rules   used  in  soYware  projects?   4.  How  does  RE  pracAces  impact  the   usage  and  management  of  rules?  
  • 7. Research  Method   •  Exploratory,  qualita2ve  research   •  Semi-­‐structured  interviews   –  open  ques2ons   •  Sec2ons:   –  About  you     –  Requirements  engineering     –  Business  rules   •  90  minutes   •  2-­‐3  interviewers  per  session   7  
  • 9. #   Roles   Exp(Y)   Domain   P1   Domain  consultant,  business  process  manager,   requirements  reviewer   13     Insurance     P2   Business  process  manager,  domain  consultant,   program  manager   20   Insurance   P3   Developer,  project  manager,  analyst   4   SoYware,  Banking   P4   Developer,  maintenance  lead,  project  manager   20   Telecom,  Insurance,   Power   P5   Developer,  soYware  architect,  project  manager   12     Telecom,  Finance   P6   SoYware  architect,  program/delivery  manager   10   Automo2ve  and  Telecom   P7   Program  manager,  product  manager   16   Finance   P8   Project  manager,  program  manager   21   Finance   P9   Product  manager,  presales  lead   17   Banking,  Finance   P10   Tester,  lead  underwriter,  program  manager   14   Banking,  Finance   P11   Delivery  center  head   18   Finance   Overview  of  ParAcipants   9  
  • 10. Result  SummarizaAon   10   Interviews   17  Findings   Take  minutes   Group  quotes  by   quesAon     Group  similar   quotes   Describe   findings   Statement  must  be  observed  twice  at  least   Sent  to  par2cipant  within  48  h   Independent  tagging  of  quotes  
  • 11. Result  SummarizaAon   11   Interviews   17  Findings   Take  minutes   Group  quotes  by   quesAon     Group  similar   quotes   Describe   findings  
  • 12. Outline  of  the  Talk   Summary   Study  Design   Findings   MoAvaAon   2   1   3   4   12  
  • 13. PercepAons  of  Business  Rules   13   Stakeholders  have   different  percepAons  of   business  rules  depending   on  their  roles  and   experience  
  • 14. 27  Types  of  Business  Rules  were  MenAoned   14   #   Rule  Type   Times   MenAoned   1   Valida2ons  rules  &  value  ranges   7   2   System  /  applica2on  specific  rules   4   3   Calcula2on  rules   4   4   Access  control  rules   4   5   External  system  interfaces   3   6   Laws  &  regula2ons   3   7   Sequencing  /  control  flow   3   8   Geography  specific  rules   3  
  • 15. 27  Types  of  Business  Rules  were  MenAoned   15   #   Rule  Type   Times   MenAoned     9   Business  process  rules   3   10   Procedural  /  Opera2onal  rules   3   11   User  interface  rules   2   12   Company  policies   2   13   Time  restric2ons     2   14   Dynamic  rules   2   15   Defini2ons   2  
  • 16. Capturing  and  Maintaining  Business  Rules   Business  rules  are   embedded  as  free  text   anywhere  in  the  project     and  domain   documenta2on   16  
  • 17. 17   no  separate  sec2on  for  business  rules   You  can  find  business  rules  in  requirements   specifica2ons,  source  documents,  process   descrip2on,  marke2ng  brochures,  (telecom)   regula,ons,  or  laws   [P5]   [P3]  
  • 18. 18   The  use  of  formal  rule   languages  and  rule   engines  is  rather   excep2onal  in  prac2ce  
  • 19. Use  of  Business  Rules   19   Business  rules  are   captured  and  used  not   only  in  RE  but  also  in     other  project  ac2vi2es  
  • 20. 20   Many  rules  were  discovered   during  the  implementa2on  and   tes2ng  when  we  needed  them.   [P6]  
  • 21. Externalized  business   rules  facilitate  sharing   knowledge  with  new   team  members  and  a   cross  projects   21  
  • 22. RE  PracAces  and  Business  Rules   22   Customers  expect   soYware  vendors  to   have  domain  knowledge   and  to  “develop”   business  rules  
  • 23. RE  and  Business  Rules   23   Prac22oners  allocate  low  effort  for   understanding  special  flows  (rules)   The  lack  of  domain  knowledge  in   development  teams  hinders  the   capturing  of  business  rules  
  • 24. RE  and  Business  Rules   24   To  iden2fy  the  right  level  of  detail  in   documenta2on  is  difficult  (too  much   informa2on  or  only  main  flows   without  rules  and  excep2ons)   Business  rules  (excep2ons)  represent  a  specific   type  of  requirements  or  domain  knowledge,   which  oYen  remains  tacit  
  • 25. Outline  of  the  Talk   Summary   Study  Design   Findings   MoAvaAon   2   1   3   4   25  
  • 26. Business  Rules  =  Crucial  Domain  Knowledge   •  SoYware  vendors  increasingly  rely  on  the  domain  knowledge   •  Customers  expect  vendors  to  know  the  domain  very  well   •  “Knowing”  the  domain,  the  restric2ons,  the  constraints,  and   the  excep2ons  is  very  cost  intensive   26  
  • 27. ImplicaAon  for  Researchers   27   1.  Focus  on  the  knowledge  and  documenta2on   poten2als  of  business  rules   2.  Extract  and  trace  rules  to  various  ar2facts   3.  Develop  ques2on-­‐answering  systems  to  retrieve  the   required  informa2on  depending  on  task  and  context  
  • 28. 28   It  would  be  perfect  if  I  could  just   select  a  component  or  a  feature     and  my  tool  show  me  the  most   important  business  rules     which  I  should  take  care  of.   [P9]  
  • 29. 29   Business  rules:  The   bomb  or  the  treasure?   Exploratory  study  of  business   rules  in  RE  pracAce   Business  rules  =  an  asset  worth   “externalizing”  (automaAcally?)   17  findings  on   types  of  rules,   management   and  use  
  • 30. Uni  Hamburg,  Germany   Prof.  Dr.  Walid  Maalej     maalej@informa2k.uni-­‐…   mobis.informa2k.uni-­‐…   maalejw