「メモ/アーキテクチャ」の編集履歴（バックアップ）一覧はこちら

「メモ/アーキテクチャ」(2010/03/18 (木) 20:17:55) の最新版変更点

追加された行は緑色になります。

削除された行は赤色になります。

#contents

 In [Perry & Wolf 1992], a distinction is made between
 architecture erosion and architectural drift.Architectural
 erosion, according to Perry and Wolf, is the result of
 'violations of the architecture'. Architectural drift, on
 the other hand is the result of 'insensitivity to the
 architecture' (the architecturally implied rules are not
 clear to the software engineers who work with it). Parnas,
 in his paper on software aging [Parnas 1994], observes
 similar phenomena's. Although he does not explicitly talk
 about erosion, he does talk about aging of software as the
 result of bad design decisions which in turn are the result 
 of poorly understood systems. In other words: erosion is
 caused by architectural drift.

-[[Design Erosion: Problems & Causes>http://www.jillesvangurp.com/publications/]]

-[[Software Architecture Document Guidelines>http://www.codingthearchitecture.com/2008/03/18/software_architecture_document_guidelines.html]]

*カンファレンス
-[[Software Architect 2008>http://www.software-architect.co.uk/slides/]]

**ワークショップ
-[[Fourth Workshop on SHAring and Reusing architectural Knowledge (SHARK 2009)>http://www.cs.rug.nl/~paris/SHARK2009/]]

*本
-[[Software Architecture Knowledge Management: Theory and Practice >http://www.amazon.co.jp/dp/3642023738]]



*文献

-[[Software Architecture Reconstruction: A Process-Oriented Taxonomy>http://stephane.ducasse.free.fr/Publications.html]], TSE 2009

-[[Applying empirical software engineering to software architecture: Challenges and lessons learned>http://www.falessi.com/]], TR 2009


-[[Criteria for the Evaluation of Implemented Architectures >http://swerl.tudelft.nl/bin/view/Main/TechnicalReports]], TR 2009/ICSM 2009

-[[Modeling Architectural Patterns’ Behavior Using Architectural Primitives>http://www.rug.nl/informatica/onderzoek/programmas/softwareengineering/publications]], ECSA 2008


-[[Continuous and Automated Evolution of Architecture-to-Implementation Traceability Links>http://www.ics.uci.edu/~andre/publications.html]], 2008


-[[Sharing architecture knowledge through models: quality and cost>http://www.rug.nl/informatica/onderzoek/programmas/softwareengineering/publications]]

-[[Grokking Software Architecture>http://plg.uwaterloo.ca/~holt/cv/papers.html]], WCRE2008

**ADL
-[[Haskell as an Architecture Description Language>http://www.cs.uu.nl/wiki/Center/TechnicalReports]], TR 2008


**進化
-[[The Loss of Architectural Knowledge during System Evolution: An Industrial Case Study>http://www4.informatik.tu-muenchen.de/~juergens/publications/index.html]], ICPC 2009


-[[Evolution Styles: Formal foundations and tool support for software architecture evolution>http://www.cs.cmu.edu/~garlan/publisting.html]], Technical report, 2008


-[[Using graph transformation to evolve software architectures>http://w3.umh.ac.be/~infofs/preprints/index.php?page=paper_info&ID=218]], BENEVOL 2008

**可視化
-[[Ontology-Driven Visualization of Architectural Design Decisions >http://www.win.tue.nl/~alext/ALEX/PAPERS/papers.html]], WICSA 2009


**プラットフォーム
-[[The Architecture of Platforms: A Unified View>http://www.hbs.edu/research/facpubs/workingpapers/papers0809.html#wp09-034]], HBS Working Papers 2008

**パターン
-[[メモ/アーキテクチャパターン]]

**その他
-[[Measuring and Understanding Hierarchy as an Architectural Element in Industry Sectors>http://www.hbs.edu/research/facpubs/workingpapers/papers0809.html#wp09-144]], HBS Working Paper 2009

#contents

 In [Perry & Wolf 1992], a distinction is made between
 architecture erosion and architectural drift.Architectural
 erosion, according to Perry and Wolf, is the result of
 'violations of the architecture'. Architectural drift, on
 the other hand is the result of 'insensitivity to the
 architecture' (the architecturally implied rules are not
 clear to the software engineers who work with it). Parnas,
 in his paper on software aging [Parnas 1994], observes
 similar phenomena's. Although he does not explicitly talk
 about erosion, he does talk about aging of software as the
 result of bad design decisions which in turn are the result 
 of poorly understood systems. In other words: erosion is
 caused by architectural drift.

-[[Design Erosion: Problems & Causes>http://www.jillesvangurp.com/publications/]]

-[[Software Architecture Document Guidelines>http://www.codingthearchitecture.com/2008/03/18/software_architecture_document_guidelines.html]]

*カンファレンス
-[[Software Architect 2008>http://www.software-architect.co.uk/slides/]]

**ワークショップ
-[[Fourth Workshop on SHAring and Reusing architectural Knowledge (SHARK 2009)>http://www.cs.rug.nl/~paris/SHARK2009/]]

*本
-[[Software Architecture Knowledge Management: Theory and Practice >http://www.amazon.co.jp/dp/3642023738]]



*文献

-[[The Architecture of Complex Systems: Do Core-periphery Structures Dominate?>http://www.hbs.edu/research/facpubs/workingpapers/papers0910.html#wp10-059]]. HBS WP 2010

-[[Software Architecture Reconstruction: A Process-Oriented Taxonomy>http://stephane.ducasse.free.fr/Publications.html]], TSE 2009

-[[Applying empirical software engineering to software architecture: Challenges and lessons learned>http://www.falessi.com/]], TR 2009


-[[Criteria for the Evaluation of Implemented Architectures >http://swerl.tudelft.nl/bin/view/Main/TechnicalReports]], TR 2009/ICSM 2009

-[[Modeling Architectural Patterns’ Behavior Using Architectural Primitives>http://www.rug.nl/informatica/onderzoek/programmas/softwareengineering/publications]], ECSA 2008


-[[Continuous and Automated Evolution of Architecture-to-Implementation Traceability Links>http://www.ics.uci.edu/~andre/publications.html]], 2008


-[[Sharing architecture knowledge through models: quality and cost>http://www.rug.nl/informatica/onderzoek/programmas/softwareengineering/publications]]

-[[Grokking Software Architecture>http://plg.uwaterloo.ca/~holt/cv/papers.html]], WCRE2008

**ADL
-[[Haskell as an Architecture Description Language>http://www.cs.uu.nl/wiki/Center/TechnicalReports]], TR 2008


**進化
-[[The Loss of Architectural Knowledge during System Evolution: An Industrial Case Study>http://www4.informatik.tu-muenchen.de/~juergens/publications/index.html]], ICPC 2009


-[[Evolution Styles: Formal foundations and tool support for software architecture evolution>http://www.cs.cmu.edu/~garlan/publisting.html]], Technical report, 2008


-[[Using graph transformation to evolve software architectures>http://w3.umh.ac.be/~infofs/preprints/index.php?page=paper_info&ID=218]], BENEVOL 2008

**可視化
-[[Ontology-Driven Visualization of Architectural Design Decisions >http://www.win.tue.nl/~alext/ALEX/PAPERS/papers.html]], WICSA 2009


**プラットフォーム
-[[The Architecture of Platforms: A Unified View>http://www.hbs.edu/research/facpubs/workingpapers/papers0809.html#wp09-034]], HBS Working Papers 2008

**パターン
-[[メモ/アーキテクチャパターン]]

**その他
-[[Measuring and Understanding Hierarchy as an Architectural Element in Industry Sectors>http://www.hbs.edu/research/facpubs/workingpapers/papers0809.html#wp09-144]], HBS Working Paper 2009