Business Design - OBASHI Think2018-05-24T17:18:45Zhttp://think.obashi.co.uk/forum/categories/business-design/listForCategory?feed=yes&xn_auth=noOBASHI examplestag:think.obashi.co.uk,2015-12-16:6264419:Topic:299132015-12-16T22:30:54.265ZPaweł Drążykhttp://think.obashi.co.uk/profile/PawelDrazyk
<p>Hello,</p>
<p>I'm a newbee to the OBASHI methodology since I've took the course and certification last week however in our organization (softwarehouse) we would like to implement this methodology in context of running projects to our customers. Aim is to enhance our analytical approach towards modelling business processes and their impact on IT world. </p>
<p></p>
<p>For some time I've been trying to gather some examples of the how to start with OBASHI especially in terms of IT projects…</p>
<p>Hello,</p>
<p>I'm a newbee to the OBASHI methodology since I've took the course and certification last week however in our organization (softwarehouse) we would like to implement this methodology in context of running projects to our customers. Aim is to enhance our analytical approach towards modelling business processes and their impact on IT world. </p>
<p></p>
<p>For some time I've been trying to gather some examples of the how to start with OBASHI especially in terms of IT projects (most suitably in AS-IS -&gt; TO-BE analysis). I'm also wondering how to establish a whole B&amp;IT and DAV diagram model for a big organisation.</p>
<p></p>
<p>Maybe you have some experience or examples of how to address this problems and you would be eager to share it?</p>
<p></p>
<p>Best regards,</p>
<p>Paweł Drążyk</p> Operating Systems and the OBASHI Layerstag:think.obashi.co.uk,2011-10-25:6264419:Topic:153022011-10-25T20:11:57.098ZPaul Wallishttp://think.obashi.co.uk/profile/PaulWallis
<p><span style="font-family: arial,helvetica,sans-serif;">A question was posed the other day on the OBASHI LinkedIn group:</span></p>
<blockquote><p><span style="font-family: arial,helvetica,sans-serif;">"At what point does a piece of software fall into the Application Layer instead of [Operating] System?</span><br></br> <span style="font-family: arial,helvetica,sans-serif;">I'm busy documenting a bunch of Windows IIS and SQL servers: IIS (which is included with Windows Server) should logically be…</span></p>
</blockquote>
<p><span style="font-family: arial,helvetica,sans-serif;">A question was posed the other day on the OBASHI LinkedIn group:</span></p>
<blockquote><p><span style="font-family: arial,helvetica,sans-serif;">"At what point does a piece of software fall into the Application Layer instead of [Operating] System?</span><br/> <span style="font-family: arial,helvetica,sans-serif;">I'm busy documenting a bunch of Windows IIS and SQL servers: IIS (which is included with Windows Server) should logically be on the same layer as MS SQL (which is a separate install but thus in the Application Layer).</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">Also wondering about Server Support Software (i.e. backup, scheduling, monitoring, asset management) - I feel this should be in the System Layer as it cannot be linked to a customer. Any thoughts, suggestions?"</span></p>
</blockquote>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">Due to space restrictions on LinkedIn I had to give a truncated reply, but here is a more complete response:</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">The question of what constitutes an Operating System (or part of an Operating System) is one which we debated long and hard over the years when we were designing OBASHI.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">I think you are correct in placing IIS at the same layer as SQL Server because, despite it shipping with the Operating System, it is not actually part of it, but runs as a separate application on top of the Operating System.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">The same can be said of the server support software you mentioned. We would class those as applications which are run in the Application Layer, even the software which ships with the Operating System.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">Taking it to an extreme, you could say that just because Notepad (or NT Backup) ships with, and is installed by, Windows, we wouldn’t call it part of the Windows OS, rather it is an application which is run on top of the OS.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">On the ‘linking to a customer point’, we generally find that such support software is maintained and operated by the IT department (or those tasked with IT Support). The staff which perform this role, together with the software they are using, all contribute to the cost of operating the server.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">Consequently, we would tend to map the IT Support with its own Ownership and Business Layers, to show the service which is being offered to customers, with the support applications which are supporting those processes in the Application Layer.</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">So, our rule of thumb would be to turn your question around. </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">Rather than considering “At what point does a piece of software fall into the Application Layer instead of [Operating] System?” it’s easier to consider “At what point does a piece of software fall into the System Layer instead of the Application Layer?”</span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">We place all software in the Application Layer unless it is the actual Operating System itself, or (as you’ll see in section 8.8.1 of the OBASHI Manual) it is a virtualisation application such as a hypervisor which runs an Operating System. </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;"> </span></p>
<p><span style="font-family: arial,helvetica,sans-serif;">To place a hypervisor in the Application Layer would mean that any Operating Systems running on the hypervisor would also need to be in the Application Layer, which would not be logical… so virtualisation software is considered an Operating System too, as it act as an abstraction layer to the hardware on which another Operating System can run.</span></p>
<p> </p>