<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3ARole-oriented_Process_Modelling</id>
		<title>Trends:Role-oriented Process Modelling - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://www.enterprisearchitecture.management/index.php?action=history&amp;feed=atom&amp;title=Trends%3ARole-oriented_Process_Modelling"/>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Role-oriented_Process_Modelling&amp;action=history"/>
		<updated>2026-07-05T23:10:43Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.24.2</generator>

	<entry>
		<id>https://www.enterprisearchitecture.management/index.php?title=Trends:Role-oriented_Process_Modelling&amp;diff=5208&amp;oldid=prev</id>
		<title>Admin: Created page with &quot;{{DISPLAYTITLE: Role-oriented Process Modelling}} == The Role-oriented Process Modelling Trend == Traditional BPM and requirement concepts are insufficient for today’s EA, B...&quot;</title>
		<link rel="alternate" type="text/html" href="https://www.enterprisearchitecture.management/index.php?title=Trends:Role-oriented_Process_Modelling&amp;diff=5208&amp;oldid=prev"/>
				<updated>2017-01-10T14:02:58Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;{{DISPLAYTITLE: Role-oriented Process Modelling}} == The Role-oriented Process Modelling Trend == Traditional BPM and requirement concepts are insufficient for today’s EA, B...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{DISPLAYTITLE: Role-oriented Process Modelling}}&lt;br /&gt;
== The Role-oriented Process Modelling Trend ==&lt;br /&gt;
Traditional BPM and requirement concepts are insufficient for today’s EA, Business Model and Value-driven approach to organization operational execution and strategic management whereas requirements must support, link and be decomposed from top objectives down to technology requirements. Consequently, Business Processes are architected and designed as a system of activities reflecting and supporting achievement of organization’s goals, strategies and objectives. All of these can be classified as high level business requirements.&lt;br /&gt;
&lt;br /&gt;
A Role-oriented Process Modelling approach and discipline is requires to create process-centric organization these high level requirements must be decomposed, layered, and used to identify, model, architect, design, implement and operate cross-functional process scenarios each with a defined purpose, value-driven activities and measurable outcomes (performance indicators) related to needed business objectives (high level requirements). All of these are functional capabilities, which are also requirements.&lt;br /&gt;
&lt;br /&gt;
[[Category: Solution Trends]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>	</entry>

	</feed>