<?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://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/software-engineering-blog/RSS">
  <title>Software Engineering Blog</title>
  <link>http://www.se.cs.put.poznan.pl</link>
  
  <description>
    
       Here you can find information concerning our research and generally related to software engineering and software development.
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2009-10-20T08:51:25Z</syn:updateBase>
        
  
  <image rdf:resource="http://www.se.cs.put.poznan.pl/logo.png"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/uc-sketch-goes-online"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/indtroducing-atam-with-technical-drama"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/transactions-in-use-cases-nfr-and-architectural-decisions"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/garmus-function-point-analysis"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/eclipse-how-to-make-a-scrollable-view"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/specyfikacja-wymagan-dla-systemow-informatycznych"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucp"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/se-demystifying-the-black-art-book"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/introduction-to-use-cases"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/plone-cms-a-set-of-products-to-build-a-site"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/toward-decision-centric-repository-of-architectural-knowledge"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/incremental-architecture-refinement"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/uc-sketch-goes-online">        <title>UC-Sketch goes online</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/uc-sketch-goes-online</link>        <description>We have just published a new tool that supports analyst in writing use-case scenarios. Check it out!</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 transaction</dc:subject>                    <dc:subject>use cases</dc:subject>                <dc:date>2012-07-28T20:15:38Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/indtroducing-atam-with-technical-drama">        <title>Indtroducing ATAM with Technical Drama</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/indtroducing-atam-with-technical-drama</link>        <description>This blog entry presents Technical Drama knowledge transfer approach, its application for teaching ATAM (Architecture Tradeoff Evaluation Method) and summarizes the results we obtained in two case studies - at university and in software companies.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>skopczynska</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>architectural knowledge</dc:subject>                    <dc:subject>atam</dc:subject>                    <dc:subject>architecture evaluation</dc:subject>                    <dc:subject>design decision</dc:subject>                    <dc:subject>software architecture</dc:subject>                    <dc:subject>knowledge transfer</dc:subject>                <dc:date>2011-11-04T10:04:36Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/transactions-in-use-cases-nfr-and-architectural-decisions">        <title>Transactions in Use Cases, Non-functional Requirements, and Architectural Decisions</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/transactions-in-use-cases-nfr-and-architectural-decisions</link>        <description>Architectural decisions are usually considered to be influenced mainly by non-functional requirements (NFRs). It is difficult to disagree with such thesis. However, some of the decisions are not directly driven by NFRs, but by the functionality of the system. It can also happen that some of the NFRs are not explicitly defined. In this entry, you can find a checklist containing 20 questions regarding functional requirements that can help you investigate required capabilities of a system architecture.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>architectural knowledge</dc:subject>                    <dc:subject>architecture evaluation</dc:subject>                    <dc:subject>use cases</dc:subject>                <dc:date>2010-09-04T12:25:44Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/garmus-function-point-analysis">        <title>Review of book: Function Point Analysis: Measurement Practices for Successful Software Projects</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/garmus-function-point-analysis</link>        <description>This is a must-have book  for anyone who is seriously interested in counting IFPUG FPA and does not have access to official IFPUG counting practices manual.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>metrics</dc:subject>                    <dc:subject>effort estimation</dc:subject>                    <dc:subject>review</dc:subject>                    <dc:subject>function point analysis</dc:subject>                <dc:date>2010-09-04T11:48:56Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/eclipse-how-to-make-a-scrollable-view">        <title>Eclipse - How To Make a Scrollable View?</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/eclipse-how-to-make-a-scrollable-view</link>        <description>Sometimes you may like to have a scrollable view that contains another composite. The question is how to make it scrollable and adjustable to its content?</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>eclipse</dc:subject>                    <dc:subject>swt</dc:subject>                <dc:date>2010-04-27T08:24:18Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/specyfikacja-wymagan-dla-systemow-informatycznych">        <title>Guideliness for Developing SRS</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/specyfikacja-wymagan-dla-systemow-informatycznych</link>        <description>We have just received permission to publish results of the project Guideliness for Developing SRS, realized in co-operation with the Poznan City Hall, which goal was to provide guideliness for development of software requirements specifications (especially when bid of tender procedure is involved).</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>quality attributes</dc:subject>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>use case diagram</dc:subject>                    <dc:subject>SRS</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>ieee830:1998</dc:subject>                <dc:date>2010-03-25T11:23:00Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/crud-pattern-in-use-cases">        <title>CRUD Pattern in Use Cases</title>        <link>http://www.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://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucd-and-uc">        <title>Use-Case Relations - Diagram and Text</title>        <link>http://www.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://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucp">        <title>Use Case Points</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/ucp</link>        <description>The Use Case Points (UCP) method, proposed by Gustav Karner can be used to estimate effort early in the project life-cycle, with relatively low cost. It is based on two main inputs which are actors complexity, measured based on the interface actor uses to communicate with the system; and use-case complexity measured in the number of so-called transactions in use-case scenarios. Here, I would like to present you  basic information about the original method proposed by Karner.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>effort estimation</dc:subject>                    <dc:subject>use case points</dc:subject>                    <dc:subject>metrics</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>use-case transaction</dc:subject>                <dc:date>2010-09-01T10:12:30Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/use-case-diagram">        <title>Use Case Diagram</title>        <link>http://www.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>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/se-demystifying-the-black-art-book">        <title>Review of book: Software Estimation Demystifying the Black Art</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/se-demystifying-the-black-art-book</link>        <description>Steve McConell's book is one of the best book concerning software cost estimation available on the market. In my opinion it could be especially valuable for beginners in that field, however advanced users will also find plenty of valuable information there.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>effort estimation</dc:subject>                    <dc:subject>review</dc:subject>                <dc:date>2009-12-06T15:04:16Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/introduction-to-use-cases">        <title>Introduction to Use Cases</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/introduction-to-use-cases</link>        <description>Use cases, introduced by Ivar Jacobson more than 20 years ago, are used to capture user (actor) point of view while describing functional requirements of the system. In this brief article I would like to present you an overview of them (what are they, what are the most important parts of use-case model etc.)</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:date>2009-12-19T12:05:19Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/plone-cms-a-set-of-products-to-build-a-site">        <title>Plone CMS - a set of products to build a site</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/plone-cms-a-set-of-products-to-build-a-site</link>        <description>One of the main difficulties often met while setting up a site based on any open source CMS (with plugin-based architecture) is a choice of enhancement modules. The same problem relates to Plone-based sites. If you are planning to build such a site and you’ve just started to look for a good set of products for Plone 3.3, you may find this entry useful.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>programming</dc:subject>                    <dc:subject>plone</dc:subject>                <dc:date>2009-12-02T14:07:31Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/toward-decision-centric-repository-of-architectural-knowledge">        <title>Toward Decision Centric Repository of Architectural Knowledge</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/toward-decision-centric-repository-of-architectural-knowledge</link>        <description>One of the topic we are working on is software architecture evaluation. Recently we have  been focusing on incremental  architecture evaluation method. One of the key supporting techniques is a use of the architectural knowledge repository for storing the evaluation findings and refine the architecture continuously. Therefore, we  have proposed a model of repository which central concept is design decision. This work was presented at CEE-SET'09 conference. If you would like to know the details read this article. </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>bmichalik</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>iso42010</dc:subject>                    <dc:subject>architectural knowledge</dc:subject>                    <dc:subject>viewpoint</dc:subject>                    <dc:subject>repository</dc:subject>                    <dc:subject>design decision</dc:subject>                    <dc:subject>software architecture</dc:subject>                    <dc:subject>adapt</dc:subject>                    <dc:subject>knowledge transfer</dc:subject>                    <dc:subject>model</dc:subject>                    <dc:subject>iso1471</dc:subject>                    <dc:subject>view</dc:subject>                <dc:date>2009-11-09T12:13:33Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/incremental-architecture-refinement">        <title>Incremental architecture refinement</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/incremental-architecture-refinement</link>        <description>One of the topic we are working on is software architecture evaluation. The incremental architecture evaluation approach was presented at CEE-SET'09 conference. If you would like to know the details about the approach read this article.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>bmichalik</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>architectural knowledge</dc:subject>                    <dc:subject>architecture evaluation</dc:subject>                    <dc:subject>iso9126</dc:subject>                    <dc:subject>software architecture</dc:subject>                    <dc:subject>adapt</dc:subject>                    <dc:subject>atam</dc:subject>                <dc:date>2009-10-30T11:14:00Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>




</rdf:RDF>
