<?xml version="1.0" encoding="utf-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://se.cs.put.poznan.pl/search_rss">
  <title>PUT Software Engineering Team</title>
  <link>http://se.cs.put.poznan.pl</link>
  
  <description>
    
            These are the search results for the query, showing results 1 to 3.
        
  </description>
  
  
  
  
  <image rdf:resource="http://se.cs.put.poznan.pl/logo.png"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases">        <title>CRUD Pattern in Use Cases</title>        <link>http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases</link>        <description>If you have ever been writing use cases for a data-oriented system (i.e.  CMS), you have probably noticed that there is a problem with the large number of use cases like "Add an article", "Remove an article" etc. If you have all CRUD operations available for all objects in the system, you can finish with up to 4 x number-of-objects of use cases. You can reduce this number by introducing the CRUD pattern, which I would like to present you in this blog entry.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>pattern</dc:subject>                    <dc:subject>use case diagram</dc:subject>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>uml</dc:subject>                <dc:date>2010-04-07T19:35:00Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc">        <title>Use-Case Relations - Diagram and Text</title>        <link>http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc</link>        <description>In this blog entry, I would like to show you how the relations (include, and extend) between use cases are presented on use case diagrams and how to use them in textual representations of use cases.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>use case diagram</dc:subject>                    <dc:subject>uml</dc:subject>                <dc:date>2010-01-24T09:11:47Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram">        <title>Use Case Diagram</title>        <link>http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram</link>        <description>Use cases were Ivar Jacobson's contribution to the UML notation. Although they are in most cases presented in a textual form, there is a special diagram in UML called Use Case Diagram (UCD), which is used to present their structure and associations with actors.
In this article I will try to present you all necessary information to use UCD effectively.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>use case diagram</dc:subject>                    <dc:subject>uml</dc:subject>                <dc:date>2009-12-22T09:54:15Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>



</rdf:RDF>
