<?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/search_rss">
  <title>PUT Software Engineering Team</title>
  <link>http://www.se.cs.put.poznan.pl</link>
  
  <description>
    
            These are the search results for the query, showing results 6 to 8.
        
  </description>
  
  
  
  
  <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/ucp"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/enhancing-use-case-based-effort-estimation-with-transaction-types"/>
        
        
            <rdf:li rdf:resource="http://www.se.cs.put.poznan.pl/publications/ochodek-2008"/>
        
    </rdf:Seq>
  </items>

</channel>

    <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/enhancing-use-case-based-effort-estimation-with-transaction-types">        <title>Enhancing Use-Case-Based Effort Estimation with Transaction Types (presentation)</title>        <link>http://www.se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/enhancing-use-case-based-effort-estimation-with-transaction-types</link>        <description>Recently we have conducted some research regarding use-case-based effort estimation. Results were presented at CEE-SET'09 conference. If you would like to read how knowledge about use-case transactions semantics can help in estimating effort, go ahead and see the presentation. If you like the idea you can find more information in the paper.</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>ttpoints</dc:subject>                    <dc:subject>requirements engineering</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>use-case transaction</dc:subject>                <dc:date>2010-09-04T11:21:15Z</dc:date>        <dc:type>Blog Entry</dc:type>    </item>
    <item rdf:about="http://dx.doi.org/10.1007/978-3-540-85279-7_5">        <title>Automatic Transactions Identification in Use Cases</title>        <link>http://www.se.cs.put.poznan.pl/publications/ochodek-2008</link>        <description>Since the early 90's of the previous century, use cases have became informal industry standard for presenting functional requirements. The rapid popularity growth stimulated many different approaches for their presentation and writing styles. Unfortunately, this variability makes automatic processing of use cases very difficult. This problem might be mitigated by the use of transaction concept, which is defined as an atomic part of the use case scenario.   In this paper we present approach to the automatic transaction discovery in the textual use cases, through the NLP analysis. The proposed solution was implemented as a prototype tool  UCTD  and preliminarily verified in a case study. </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>requirements engineering</dc:subject>                    <dc:subject>natural language processing</dc:subject>                    <dc:subject>use cases</dc:subject>                    <dc:subject>use-case transaction</dc:subject>                <dc:date>2009-09-08T06:25:23Z</dc:date>        <dc:type>Inproceedings Reference</dc:type>    </item>



</rdf:RDF>
