<rdf:RDF xmlns:community="http://www.bibsonomy.org/ontologies/2008/05/community#" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xml:base="http://www.bibsonomy.org/user/cschenk/design"><owl:Ontology rdf:about=""><rdfs:comment>BibSonomy publications for /user/cschenk/design</rdfs:comment><owl:imports rdf:resource="http://swrc.ontoware.org/ontology/portal"/></owl:Ontology><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2e503584bdf5c7bdb0e8b57478a18225a/cschenk"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2e503584bdf5c7bdb0e8b57478a18225a/cschenk"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://portal.acm.org/citation.cfm?id=9800"/><swrc:date>Tue Jul 01 15:32:11 CEST 2008</swrc:date><swrc:address>Piscataway, NJ, USA</swrc:address><swrc:journal>IEEE Transactions on Software Engineering</swrc:journal><swrc:number>2</swrc:number><swrc:pages>251-257</swrc:pages><swrc:publisher><swrc:Organization swrc:name="IEEE Press"/></swrc:publisher><swrc:title>A rational design process: How and why to fake it</swrc:title><swrc:volume>12</swrc:volume><swrc:year>1986</swrc:year><swrc:keywords>design fake how ieee paper process rational read:2008 why </swrc:keywords><swrc:abstract>A perfectly rational person is one who always has a good reason for what he does. Each step taken can be shown to be the best way to get to a well defined goal. Most of us like to think of ourselves as rational professionals. However, to many observers, the usual process of designing software appears quite irrational. Programmers start without a clear statement of desired behavior and implementation constraints.  They make a long sequence of design decisions with no clear statement of why they do things the way they do. Their 
rationale is rarely explained. </swrc:abstract><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="David Lorge Parnas"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Paul C. Clements"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/24d2c5f2df7333263bf75ccc82ef78bf6/cschenk"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/24d2c5f2df7333263bf75ccc82ef78bf6/cschenk"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><owl:sameAs rdf:resource="http://www.amazon.de/gp/redirect.html%3FASIN=1411609255%26tag=ws%26lcode=xm2%26cID=2025%26ccmID=165953%26location=/o/ASIN/1411609255%253FSubscriptionId=13CT5CVB80YFWJEPWS02"/><swrc:date>Mon Apr 07 07:34:36 CEST 2008</swrc:date><swrc:publisher><swrc:Organization swrc:name="Lulu.com"/></swrc:publisher><swrc:title>Domain-Driven Design Quickly</swrc:title><swrc:year>2007</swrc:year><swrc:keywords>book design domain quickly toread </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="9781411609259" swrc:key="ean"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="1411609255" swrc:key="asin"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="1411609255" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="004" swrc:key="dewey"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Floyd Marinescu"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Abel Avram"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/253b995ac24a4653ea11722662bc44642/cschenk"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/253b995ac24a4653ea11722662bc44642/cschenk"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><owl:sameAs rdf:resource="http://www.amazon.de/gp/redirect.html%3FASIN=3897214210%26tag=ws%26lcode=xm2%26cID=2025%26ccmID=165953%26location=/o/ASIN/3897214210%253FSubscriptionId=13CT5CVB80YFWJEPWS02"/><swrc:date>Fri Feb 08 10:03:51 CET 2008</swrc:date><swrc:edition>1</swrc:edition><swrc:publisher><swrc:Organization swrc:name="O&#039;Reilly"/></swrc:publisher><swrc:title>Entwurfsmuster von Kopf bis Fuß</swrc:title><swrc:year>2005</swrc:year><swrc:keywords>book design entwurfsmuster java pattern rating:1 read:2007 </swrc:keywords><swrc:hasExtraField><swrc:Field swrc:value="9783897214217" swrc:key="ean"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="3897214210" swrc:key="asin"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="3897214210" swrc:key="isbn"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Eric Freeman"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Elisabeth Freeman"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Kathy Sierra"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/209f05a12cae463b33e2372369621ff5b/cschenk"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/209f05a12cae463b33e2372369621ff5b/cschenk"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Book"/><swrc:date>Sat Jun 23 17:04:26 CEST 2007</swrc:date><swrc:month>March</swrc:month><swrc:note>ISBN-10: 0201633612
ISBN-13: 978-0201633610</swrc:note><swrc:publisher><swrc:Organization swrc:name="Addison-Wesley"/></swrc:publisher><swrc:title>Design Patterns. Elements of Reusable Object-Oriented Software.</swrc:title><swrc:year>1995</swrc:year><swrc:keywords>book design erich-gamma oop patterns rating:4 read:2006 reusable software </swrc:keywords><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Erich Gamma"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Richard Helm"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Ralph E. Johnson"/></rdf:_3><rdf:_4><swrc:Person swrc:name="John Vlissides"/></rdf:_4></rdf:Seq></swrc:author></rdf:Description></rdf:RDF>
