<?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 7.
        
  </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/indtroducing-atam-with-technical-drama"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/toward-decision-centric-repository-of-architectural-knowledge"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/incremental-architecture-refinement"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/forum-english/software-architectures-english"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/knowledge-base/forum-english/architektura-oprogramowania"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/publikacje/bmichalik-09-adapt"/>
        
        
            <rdf:li rdf:resource="http://se.cs.put.poznan.pl/publikacje/michalik-ICSE08"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/indtroducing-atam-with-technical-drama">        <title>Indtroducing ATAM with Technical Drama</title>        <link>http://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://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://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://se.cs.put.poznan.pl/knowledge-base/software-engineering-blog/incremental-architecture-refinement">        <title>Incremental architecture refinement</title>        <link>http://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>
    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/forum-english/software-architectures-english">        <title>Software Architectures (English)</title>        <link>http://se.cs.put.poznan.pl/knowledge-base/forum-english/software-architectures-english</link>        <description>Here you can discuss topics concerning software architectures</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>software architecture</dc:subject>                <dc:date>2009-10-24T12:09:27Z</dc:date>        <dc:type>Forum</dc:type>    </item>
    <item rdf:about="http://se.cs.put.poznan.pl/knowledge-base/forum-english/architektura-oprogramowania">        <title>Architektura oprogramowania (Polish)</title>        <link>http://se.cs.put.poznan.pl/knowledge-base/forum-english/architektura-oprogramowania</link>        <description>Tutaj możesz podyskutować na tematy związane z architekturą oprogramowania</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>software architecture</dc:subject>                <dc:date>2009-10-24T12:09:05Z</dc:date>        <dc:type>Forum</dc:type>    </item>
    <item rdf:about="http://se.cs.put.poznan.pl/publikacje/bmichalik-09-adapt">        <title>Incremental Architecture Refinement</title>        <link>http://se.cs.put.poznan.pl/publikacje/bmichalik-09-adapt</link>        <description>In many contemporary projects, software architecture is a result of a knowledge discovery process and it is time consuming. To make the process more effective we propose a suite of short workshops that streamline the architecture refinement process. Each workshop is a central point of a corresponding architectural increment. The workshops can be easily adjusted to the process needs. The described approach is a result of our experience with using ATAM as an architecture evaluation method and it has been tried out in the industrial settings.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>architecture evaluation</dc:subject>                    <dc:subject>iso9126</dc:subject>                    <dc:subject>quality attributes</dc:subject>                    <dc:subject>software architecture</dc:subject>                    <dc:subject>adapt</dc:subject>                    <dc:subject>atam</dc:subject>                <dc:date>2009-11-05T19:36:03Z</dc:date>        <dc:type>Inproceedings Reference</dc:type>    </item>
    <item rdf:about="http://doi.acm.org/10.1145/1368088.1368193">        <title>3-Step Knowledge Transition: a Case Study on Architecture Evaluation</title>        <link>http://se.cs.put.poznan.pl/publikacje/michalik-ICSE08</link>        <description>Inżyniera oprogramowania to dynamicznie rozwijająca się dziedzina. Aby nadążyć za zmianami, firmy wytwarzające oprogramowanie potrzebują efektywnych metod transferu wiedzy. W tym artykule zostało przedstawione 3-stopniowe podejście do transferu, nazwane Technical Drama. W artykule uwagę poświęcono transferowi wiedzy w zakresie oceny architektury oprogramowania, aczkolwiek wykorzystane podejście może zostać wykorzystane do transferu wiedzy dotyczącej innych zagadnień jak na przykład inspekcje, testowanie itd. W artykule została postawiona teza, że Technical Drama może być z powodzeniem wykorzystana w kontekście przemysłowym (dwa studia przypadków zostały opisane), jak również w warunkach akademickich.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>mochodek</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>software architecture</dc:subject>                    <dc:subject>atam</dc:subject>                    <dc:subject>architecture evaluation</dc:subject>                    <dc:subject>knowledge transfer</dc:subject>                <dc:date>2009-08-17T13:18:54Z</dc:date>        <dc:type>Inproceedings Reference</dc:type>    </item>



</rdf:RDF>
