<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Icerocket blog search: tag:&quot;software engineering&quot;</title>
<link>http://blogs.icerocket.com/search?q=tag%3A%22software+engineering%22</link>
<description>Blogs Search from IceRocket.com</description>
<language>en-us</language>
<copyright>Copyright 2009, IceRocket.com</copyright>
<item>
 <title><![CDATA[UML in Color]]></title>
 <description><![CDATA[In the book Java Modelling in Color with UML, the authors argue that it is better to color-code UML diagrams instead of just using plain black and white conventional diagrams. They do it on 214 pages. ]]></description>
 <link><![CDATA[http://mikhailian.livejournal.com/34912.html]]></link>
 <pubDate>Thu, 26 Nov 2009 08:20:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[5c561baf2a091eb77a5a90fec077d07c]]></guid>
 <dc:creator>mikhailian</dc:creator>
 <source url="http://mikhailian.livejournal.com/">mikhailian</source>
</item>
<item>
 <title><![CDATA[Metrics for Source Code]]></title>
 <description><![CDATA[Halstead assigned quantitative laws to the development of computer software, using a set of primitive measures that may be derived after code is generated or estimated once design is complete. The measures are :n1 = the number of distinct operatorsn2 = the number of distinct operandsN1 = the total n <b>...</b> ]]></description>
 <link><![CDATA[http://productdevelop.blogspot.com/2009/11/metrics-for-source-code.html]]></link>
 <pubDate>Thu, 26 Nov 2009 03:28:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[f9c0aeeeb3b61ca4fbccc2b74f257f09]]></guid>
 <dc:creator>Sunflower </dc:creator>
 <source url="http://productdevelop.blogspot.com/">Software Development</source>
</item>
<item>
 <title><![CDATA[Component Level Design Metrics]]></title>
 <description><![CDATA[Component level design metrics for software components focus on internal characteristics of a software component and include measures of the three Cs - module cohesion, coupling, and complexity.- Cohesion Metrics :It defines a collection of metrics that provide an indication of the cohesiveness of a <b>...</b> ]]></description>
 <link><![CDATA[http://productdevelop.blogspot.com/2009/11/component-level-design-metrics.html]]></link>
 <pubDate>Thu, 26 Nov 2009 03:02:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[2df96cada990e927a2dca497e9b4e5b1]]></guid>
 <dc:creator>Sunflower </dc:creator>
 <source url="http://productdevelop.blogspot.com/">Software Development</source>
</item>
<item>
 <title><![CDATA[Year 2 – Software Engineering – Domain Modelling]]></title>
 <description><![CDATA[What is Domain Modelling? Domain Modelling is a way of representing the context in which the software must operate – to understand the software better. However, one must remember that you’re not modelling the software to be built! A better description would be: A Domain Model in Software Engineering <b>...</b> ]]></description>
 <link><![CDATA[http://computersciencesource.wordpress.com/2009/11/26/year-2-software-engineering-domain-modelling-2/]]></link>
 <pubDate>Wed, 25 Nov 2009 18:46:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[e5d63713eb48db3915b3eb18cb5deb61]]></guid>
 <dc:creator>Badgerati</dc:creator>
 <source url="http://computersciencesource.wordpress.com">Computer Science: Source</source>
</item>
<item>
 <title><![CDATA[Different ways of thinking]]></title>
 <description><![CDATA[A program is a list of tasks to be performed by definition. But it can also be defined as a way of mapping a large task to shorter tasks. A computer always performs a program as a list of tasks. I take this question as a theoretical one. In my opinion the difference is the problem solver’s way of th <b>...</b> ]]></description>
 <link><![CDATA[http://softwareengineeringblog.com/http:/softwareengineeringblog.com/software_engineering/different-ways-of-thinking/48]]></link>
 <pubDate>Wed, 25 Nov 2009 17:56:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[7844276c0af67383e58dfd64b810a1b6]]></guid>
 <dc:creator>Laszlo</dc:creator>
 <source url="http://softwareengineeringblog.com">Software Engineering blog</source>
</item>
<item>
 <title><![CDATA[The Unplugged by Ruven Meulenberg]]></title>
 <description><![CDATA[While researching user experience design techniques, I stumbled upon some nifty whiteboard magnets for prototyping called GuiMags as well as a complementing book called The Unplugged. GuiMags look like the nicest way to prototype something before going to HTML and CSS. Labor intensive forms of proto <b>...</b> ]]></description>
 <link><![CDATA[http://ianlotinsky.wordpress.com/2009/11/25/the-unplugged-by-ruven-meulenberg/]]></link>
 <pubDate>Wed, 25 Nov 2009 16:23:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[f8b97168d7bfd87b909ce2fdf133a45e]]></guid>
 <dc:creator>Ian Lotinsky</dc:creator>
 <source url="http://ianlotinsky.wordpress.com">Ian Lotinsky</source>
</item>
<item>
 <title><![CDATA[VS Test Method Snippet]]></title>
 <description><![CDATA[Test driven geliştirme yapmak, eğlenceli olduğu kadar uzun sren bi işlemdir malumunuz. Bu konu ile ilgili bir yazım olacaktı. Önce test yazacaksınız, sonra testi geçirecek kodu yazacaksınız. Başka bir test yazıp asıl işi yapacak kodu yazmaya zorlarsınız kedinizi. Sonra duplicationları gidermek için  <b>...</b> ]]></description>
 <link><![CDATA[http://coderhapsody.wordpress.com/2009/11/25/vs-test-method-snippet/]]></link>
 <pubDate>Wed, 25 Nov 2009 13:50:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[40c33914040d90a7d7ccac70bac09495]]></guid>
 <dc:creator>syoguran</dc:creator>
 <source url="http://coderhapsody.wordpress.com">Code Rhapsody</source>
</item>
<item>
 <title><![CDATA[VS Test Method Snippet]]></title>
 <description><![CDATA[Test driven geliştirme yapmak, eğlenceli olduğu kadar uzun sren bi işlemdir malumunuz. Bu konu ile ilgili bir yazım olacaktı. Önce test yazacaksınız, sonra testi geçirecek kodu yazacaksınız. Başka bir test yazıp asıl işi yapacak kodu yazmaya zorlarsınız kedinizi. Sonra duplicationları gidermek için  <b>...</b> ]]></description>
 <link><![CDATA[http://serkanyoguran.com/2009/11/25/vs-test-method-snippet/]]></link>
 <pubDate>Wed, 25 Nov 2009 13:42:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[21593bf875f1c10732aaf57da8fa3d64]]></guid>
 <dc:creator>syoguran</dc:creator>
 <source url="http://serkanyoguran.com">Serkan Yoğuran</source>
</item>
<item>
 <title><![CDATA[Debugging SQL Server – Login failed for user ’sa’]]></title>
 <description><![CDATA[I was troubleshooting a pesky SQL Server 2005 problem this week. I kept seeing “Failure Audit” in the Windows Application Event Viewer. It looked like this: Event Type: Failure Audit Event Source: MSSQL$SQLEXPRESS Event Category: (4) Event ID: 18456 Date: 11/25/2009 Time: 10:15:40 AM User: N/A Compu <b>...</b> ]]></description>
 <link><![CDATA[http://blog.davidroossien.com/?p=331]]></link>
 <pubDate>Wed, 25 Nov 2009 13:17:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[2d21488a7aa80a5fc91d48aa767077d5]]></guid>
 <dc:creator>David</dc:creator>
 <source url="http://blog.davidroossien.com">David Roossien Photography</source>
</item>
<item>
 <title><![CDATA[Building ChromiumOS (The Google OS)]]></title>
 <description><![CDATA[I’ve been watching all of the hype about downloading and running the latest Google creation, ChromiumOS this week so yesterday I decided to take a stab at it myself. I did not however want to simply grab a VMWare image and run it. I’m a software engineer for Pete’s sake! I should build it myself. So <b>...</b> ]]></description>
 <link><![CDATA[http://www.franzone.com/2009/11/25/building-chromiumos-the-google-os/]]></link>
 <pubDate>Wed, 25 Nov 2009 11:28:00 CST</pubDate>
 <guid isPermaLink="false"><![CDATA[27298222c52ff41026077bdc520d4382]]></guid>
 <dc:creator>Jonathan Franzone</dc:creator>
 <source url="http://www.franzone.com">franzone.com</source>
</item>
</channel>
</rss>


