<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version="2.0">
    <channel>
        <title>MERLOT Search - userId=22331</title>
        <link>http://www.merlot.org:80/merlot/</link>
        <description>A search of MERLOT materials</description>
        <copyright>Copyright 1997-2013 MERLOT. All rights reserved.</copyright>
        <pubDate>Thu, 23 May 2013 10:59:47 PDT</pubDate>
        <lastBuildDate>Thu, 23 May 2013 10:59:47 PDT</lastBuildDate>
        <image>
            <title>MERLOT Search - userId=22331</title>
            <url>http://www.merlot.org:80/merlot/images/merlot.gif</url>
            <link>http://www.merlot.org:80/merlot/</link>
            <width>44</width>
            <height>34</height>
        </image>
        <item>
            <title>Object Oriented Analysis and Design Using UML</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=77711</link>
            <description>The article describes the core concepts of Object-Oriented analysis and Design using UML.</description>
        </item>
        <item>
            <title>OO Design</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78904</link>
            <description>Explain OO design in detail.</description>
        </item>
        <item>
            <title>Software Maintenance Cycles with the RUP</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78956</link>
            <description>The Rational Unified Process?(RUP?) has no concept of a &quot;maintenance phase.&quot; Some people claim that this is a major deficiency, and are proposing to add a production phase to cover issues like maintenance, operations, and support.1 In my view, this would not be a useful addition. First, maintenance, operations, and support are three very distinct processes; although they may overlap in time, they involve different people and different activities, and have different objectives. Operations and support are clearly outside the scope of the RUP. Maintenance, however, is not; yet there is no need to add another phase to the RUP&apos;s sequence of four lifecycle phases: Inception, Elaboration, Construction, and Transition. The RUP already contains everything that is needed in terms of roles, activities, artifacts, and guidelines to cover the maintenance of a software application. And because of the RUP&apos;s essentially iterative nature, the ability to evolve, correct, or refine existing artifacts is inherent to most of its activities.</description>
        </item>
        <item>
            <title>User Interface Design</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78067</link>
            <description>This web page is maintained by a group of users who are doing research on User Interface design. This page contains a number of useful articles on designing user interface in different situation based on user types, or available resources e.g. bandwidth</description>
        </item>
        <item>
            <title>Ways to measure computer performance</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78553</link>
            <description>This link gives hints on how to compare computer performance.It present a practical and fair approach that provides mathematically sound comparison of computational performance even when the algorithm, computer, and precision are changed</description>
        </item>
        <item>
            <title>Extreme Programming</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78068</link>
            <description>This web site is dedicated to Extreme Programming (XP), another methodology for system construction. XP is particularly useful when the requirements are frequently changed and the development team has to re-schedule the deliverables frequently.  XP starts with user stories, similar to use cases in UML, but not the same.</description>
        </item>
        <item>
            <title>Intel MultiProcessor Specification</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=79195</link>
            <description>This document is intel multiprocessor specification which describes the OS, hardware and BIOS guidlines for multiprocessors.</description>
        </item>
        <item>
            <title>Interfacing Processors and Peripherals</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=79194</link>
            <description>Describes all design issues and characteristics in interfacing processors and peripherals.</description>
        </item>
        <item>
            <title>JUnit</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78954</link>
            <description>This site has a free downloadable test framework called JUnit, which can be used for regression tesing of Java code.</description>
        </item>
        <item>
            <title>Pipelining, pushing the Clockspeed Envelope</title>
            <link>http://www.merlot.org/merlot/viewMaterial.htm?id=78903</link>
            <description>This tutorial explains about pipelining and its basics. It also gives good examples and compares different types of processors.</description>
        </item>
    </channel>
</rss>
