<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Business Analysis vs. Systems Engineering</title>
	<atom:link href="http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/</link>
	<description>Connecting Business Requirements to Technology</description>
	<lastBuildDate>Mon, 30 Jan 2012 21:31:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: FEDE</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-3872</link>
		<dc:creator>FEDE</dc:creator>
		<pubDate>Fri, 12 Feb 2010 15:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-3872</guid>
		<description>So the Business Analyst is a generalist/all-rounder and the system engineer is a specialist?</description>
		<content:encoded><![CDATA[<p>So the Business Analyst is a generalist/all-rounder and the system engineer is a specialist?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerber</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2501</link>
		<dc:creator>Kerber</dc:creator>
		<pubDate>Thu, 21 Feb 2008 15:13:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2501</guid>
		<description>UML? I agree, it really help to avoid misunderstandings among different people, I&#039;m testing it with my wife, since she&#039;s from Venus and I&#039;m from Mars or something like that. You should see the &#034;Go to the grocery store&#034; activities diagram, it&#039;s beautiful.</description>
		<content:encoded><![CDATA[<p>UML? I agree, it really help to avoid misunderstandings among different people, I&#38;#39;m testing it with my wife, since she&#38;#39;s from Venus and I&#38;#39;m from Mars or something like that. You should see the &#38;#34;Go to the grocery store&#38;#34; activities diagram, it&#38;#39;s beautiful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sandra</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2500</link>
		<dc:creator>sandra</dc:creator>
		<pubDate>Thu, 21 Feb 2008 08:22:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2500</guid>
		<description>i am not saying it to be wrong to do. what is important when the Analysis role is played by more than one, is that a &#039;common&#039; language ie.UML is in place and clearly defined processes and procedures are pre-defined for the project.</description>
		<content:encoded><![CDATA[<p>i am not saying it to be wrong to do. what is important when the Analysis role is played by more than one, is that a &#8216;common&#8217; language ie.UML is in place and clearly defined processes and procedures are pre-defined for the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerber</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2499</link>
		<dc:creator>Kerber</dc:creator>
		<pubDate>Thu, 14 Feb 2008 13:00:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2499</guid>
		<description>Isandra, what you say makes sense, but depending on the size of the project, defining the requirements at a higher level and defining the low level infrastructure to support the high level goals is too much for one person to think about and to be responsible for, that&#039;s why we separated the roles, they work close, the vision is the same, but one focus on higher level goals, requirements gathering and modeling, and the other is concerned about how to make them work. The analogy we use is the Architect and the Engineer, both can design a house alone, but not a huge building. It&#039;s not only a matter of scale (more people sharing the work), it&#039;s a matter of focus (different roles).</description>
		<content:encoded><![CDATA[<p>Isandra, what you say makes sense, but depending on the size of the project, defining the requirements at a higher level and defining the low level infrastructure to support the high level goals is too much for one person to think about and to be responsible for, that&#8217;s why we separated the roles, they work close, the vision is the same, but one focus on higher level goals, requirements gathering and modeling, and the other is concerned about how to make them work. The analogy we use is the Architect and the Engineer, both can design a house alone, but not a huge building. It&#8217;s not only a matter of scale (more people sharing the work), it&#8217;s a matter of focus (different roles).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Isandra</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2498</link>
		<dc:creator>Isandra</dc:creator>
		<pubDate>Wed, 13 Feb 2008 12:44:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2498</guid>
		<description>I guess its different strokes for different&nbsp;folks but .... companies do make the mistake by having the role of BA split into those two roles. So much information gets cross communicated and/or lost between a BA and a Systems Analyst. it is mostly done when, within an enterprise, those BAs do not possess the correct skills and tools to communicate to the technical team what the requirements are! The role is then split to have a Systems Analyst as well. They then speak different languages and the solution or result of development is not what it should be/meant to be. The blame of the errors then also gets passed between the two roles. My feeling is that the role of an analyst should not be split. The risk is just too high. Rather get the BA&#039;s tools and techniques improved! The function required of the role of a systems analyst and BA resides within one.</description>
		<content:encoded><![CDATA[<p>I guess its different strokes for different&#38;nbsp;folks but &#8230;. companies do make the mistake by having the role of BA split into those two roles. So much information gets cross communicated and/or lost between a BA and a Systems Analyst. it is mostly done when, within an enterprise, those BAs do not possess the correct skills and tools to communicate to the technical team what the requirements are! The role is then split to have a Systems Analyst as well. They then speak different languages and the solution or result of development is not what it should be/meant to be. The blame of the errors then also gets passed between the two roles. My feeling is that the role of an analyst should not be split. The risk is just too high. Rather get the BA&#8217;s tools and techniques improved! The function required of the role of a systems analyst and BA resides within one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerber</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2494</link>
		<dc:creator>Kerber</dc:creator>
		<pubDate>Thu, 07 Feb 2008 02:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2494</guid>
		<description>Pine, we have a simple sentence to define the difference over here: BA - &#034;what&#034; SA - &#034;how&#034; Each role has a lot to have fun with. It&#039;s working so far.</description>
		<content:encoded><![CDATA[<p>Pine, we have a simple sentence to define the difference over here: BA &#8211; &#38;#34;what&#38;#34; SA &#8211; &#38;#34;how&#38;#34; Each role has a lot to have fun with. It&#38;#39;s working so far.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pine</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2497</link>
		<dc:creator>Pine</dc:creator>
		<pubDate>Tue, 05 Feb 2008 09:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2497</guid>
		<description>I would like to ask a follow-up question:
&quot;What is the difference between a BA and a Systems Analyst?&quot;</description>
		<content:encoded><![CDATA[<p>I would like to ask a follow-up question:<br />
&#8220;What is the difference between a BA and a Systems Analyst?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kerber</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2496</link>
		<dc:creator>Kerber</dc:creator>
		<pubDate>Wed, 30 Jan 2008 21:58:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2496</guid>
		<description>Well, does the SE perform Enterprise Analysis? The KAs define the scope of the BA so maybe we should get the INCOSEBOK&#039;s KAs and compare it, find overlapings and key differences. What about &lt;a href=&quot;http://betterprojects.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt;Craig&lt;/a&gt;? He&#039;s got INCOSEBOK two weeks ago, I bet he already took a good look on it.</description>
		<content:encoded><![CDATA[<p>Well, does the SE perform Enterprise Analysis? The KAs define the scope of the BA so maybe we should get the INCOSEBOK&#38;#39;s KAs and compare it, find overlapings and key differences. What about <a href="http://betterprojects.blogspot.com/" rel="nofollow">Craig</a>? He&#38;#39;s got INCOSEBOK two weeks ago, I bet he already took a good look on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2495</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 30 Jan 2008 15:27:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2495</guid>
		<description>The way I see it, a BA&#039;s focus is on the business requirements, and the system in general meeting those needs.  Sort of like a black box approach.  The systems engineer, however, takes the business needs as defined in technical terms by the BA, and translates that into a technical system, the details of which are of more concern than to the BA.
While the two may have considerable overlap in their understanding of business, the BA must be able to translate user terminology and focus into technical terminology, and the SE must be able to translate technical requirements into actual system architecture.
At least, this is what I have observed over the past 16 years.</description>
		<content:encoded><![CDATA[<p>The way I see it, a BA&#8217;s focus is on the business requirements, and the system in general meeting those needs.  Sort of like a black box approach.  The systems engineer, however, takes the business needs as defined in technical terms by the BA, and translates that into a technical system, the details of which are of more concern than to the BA.<br />
While the two may have considerable overlap in their understanding of business, the BA must be able to translate user terminology and focus into technical terminology, and the SE must be able to translate technical requirements into actual system architecture.<br />
At least, this is what I have observed over the past 16 years.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roeland</title>
		<link>http://www.b2ttraining.com/2008/01/14/business-analysis-vs-systems-engineering/comment-page-1/#comment-2493</link>
		<dc:creator>Roeland</dc:creator>
		<pubDate>Sun, 20 Jan 2008 16:35:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/page/business-analyst-blog/archives/122/business-analysis-vs-systems-engineering#comment-2493</guid>
		<description>Good question - the difference between a BA and a Systems engineer.
I am actually not quite sure what INCOSE&#039;s standpoint is, but my preference would be:
Where a BA focuses on the area of process, data and required IT support, a systems engineer would approach the situation in a more holistic way, as a complete transformation, covering strategy, process, people, technology, legal, etc etc.</description>
		<content:encoded><![CDATA[<p>Good question &#8211; the difference between a BA and a Systems engineer.<br />
I am actually not quite sure what INCOSE&#8217;s standpoint is, but my preference would be:<br />
Where a BA focuses on the area of process, data and required IT support, a systems engineer would approach the situation in a more holistic way, as a complete transformation, covering strategy, process, people, technology, legal, etc etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

