<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
	<channel>
		<title><![CDATA[Latest posts for the topic "1 big project versus collection of projects?"]]></title>
		<link>http://www.synthis.com/forum/posts/2.page</link>
		<description><![CDATA[Latest messages posted in the topic "1 big project versus collection of projects?"]]></description>
		<generator>JForum - http://www.jforum.net</generator>
			<item>
				<title>1 big project versus collection of projects?</title>
				<description><![CDATA[ <u><b>1 big project versus collection of projects?</b></u><br> <br> If I want to describe de workflow of a company and I want to avoid duplicating the same data or elements (e.g. People):<br> - Do I have to create 1 big project in which I detail sub-processess in different diagrams<br> - Can I create several projects that describe part of a workflow and in which I can re-use elements or diagrams developed in other projects without having tot duplicate them so that when I update that element or diagram in one project, the update is valid for the different projects in which that element is used? <br> <br> Has this something to do with the creation of a new project in file format Single File ? Multiple Files? If I try to create a multiple Files New Project, nothing happens.<br> ]]></description>
				<guid isPermaLink="true">http://www.synthis.com/forum/posts/89#207.page</guid>
				<link>http://www.synthis.com/forum/posts/89#207.page</link>
				<pubDate><![CDATA[Mon, 12 Feb 2007 05:57:19]]></pubDate>
				<author><![CDATA[ Kris Demuelenaere]]></author>
			</item>
			<item>
				<title>Re:1 big project versus collection of projects?</title>
				<description><![CDATA[ Hi,<br> <br> I'm currently mapping the company I work for and have found its very easy to do so just using 1 big project as long as you keep organised.  For example all diagrams are named 'department - process', eg 'Customer Services - Technical Support'.  This allows for quick and easy location of particular processes.<br> <br> Also you can then go on to generate various reports listing ownership of processes within the busines and produce a website allowing you to navigate from process to process.<br> <br> I found I had to create a couple of overview diagrams for the website to be truly effective, but its a very good method of letting others see the maps, eg for reference.<br> <br> Good luck!]]></description>
				<guid isPermaLink="true">http://www.synthis.com/forum/posts/89#215.page</guid>
				<link>http://www.synthis.com/forum/posts/89#215.page</link>
				<pubDate><![CDATA[Mon, 26 Mar 2007 03:58:54]]></pubDate>
				<author><![CDATA[ M Draper]]></author>
			</item>
			<item>
				<title>Re:1 big project versus collection of projects?</title>
				<description><![CDATA[ I hit a similar issue: I have a project with 40 processes. Most readers won't refer to the maps very often.<br> <br> I made an 'index process map' that has the 40 processes logically grouped. For example: the heading 'Customer Set Up' has 5 process maps (from different departments). The heading 'Customer Support' has 10 process maps, etc...<br> <br> Is that what you mean? Or, is there a better way to make it easier for a casual reader to figure out what's available?]]></description>
				<guid isPermaLink="true">http://www.synthis.com/forum/posts/89#272.page</guid>
				<link>http://www.synthis.com/forum/posts/89#272.page</link>
				<pubDate><![CDATA[Fri, 21 Mar 2008 09:37:36]]></pubDate>
				<author><![CDATA[ Robert Hazan]]></author>
			</item>
	</channel>
</rss>