Seeking the Source - Revision history

UE-InfoVis08-06 at 23:05, 8 May 2008

2008-05-08T23:05:41Z

← Older revision		Revision as of 23:05, 8 May 2008
Line 10:		Line 10:
	== Figures ==		== Figures ==

	The following images show specific ~~visualisations~~ by the "Augur" software.		The following images show specific visualizations by the "Augur" software.

	=== Augur Overview ===		=== Augur Overview ===

UE-InfoVis08-06 at 23:04, 8 May 2008

2008-05-08T23:04:45Z

← Older revision		Revision as of 23:04, 8 May 2008
Line 12:		Line 12:
	The following images show specific visualisations by the "Augur" software.		The following images show specific visualisations by the "Augur" software.

	=== ~~asdf~~ ===		=== Augur Overview ===
			<br/>[[Image:sts01_overview.png\|center\|780px]]<br/>
			This image shows the overview screen of the Augur software. You can see the different visualisations. As an example the big top part of the image, that shows a representation of source code (lines of code are represented by a line of pixels of certain length). The different colors show, when a part of the source code was last edited.

	<br/>[[Image:~~sts01_overview~~.png\|center\|~~400px\|test~~]]<br/>		=== Network structures ===
	~~text~~		<br>[[Image:sts02_participation.png\|center\|780px]]<br/>
			This image visualizes different types of networking:<br/>
			In a) you can see that the source code of the "surrounding" developers is only called by the code of the author in center. That shows a very centralized network. The author in the center represents the system's architect, who calls the code of other developers. In b) there's a little different situation. A tight network of few authors builds the core of the system, which calls methodes from a few other authors. Finally c) represents a mixture of a) and b). You can't find a defined system core, but a more or less tight network of seven developers. You can also see a periphery of four other developers. Their code just interact with the "core network" but not with each other's.

	[[Image:~~sts02_participation~~.png]]		=== Shifting ===
	~~text~~		<br>[[Image:sts03_shifting1.png\|center\|780px]]<br/>
			Here you can see developer's code in the software project shifting from a peripheral to a central role. In a) the developer only gabs code of the remaining software (i.e. his code is an interface), where in b) other parts of the software also use his code (i.e. they're implementing the interface). In this example you can see very good, how methodes get stronger integrated into the software.

	[[Image:~~sts03_shifting1~~.png]]		=== Authorship ===
			<br>[[Image:sts04_authorship.png\|center\|780px]]<br/>
			In a) (left) you can see a software project relied on a few authors. Open source projects allow developers to join the development team of the software and make changes of the source code. If a new author "overtakes" parts of another author's code by e.g. changing it more often than the original author. So in a) (right) you can see that after some time, a few more developers are involved in the development and they overtake other author's code. In b) you see an example that shows this process vice versa.

	[[Image:~~sts03_shifting2~~.png]]		=== Stability ===
			<br><center>[[Image:sts05_stability1.png\|300px]] [[Image:sts05_stability2.png\|300px]]</center><br/>
	[[Image:~~sts04_authorship~~.png]]		"These graphs show, how the structure of the source code (...) is being uset to structure the activities of the developers." [De Souza et al., 2005] In 6/a) you see a implemented module by a certain author. In 7/a) you see, that over some time, nothing has changed. The author is still the main developer of this module. Otherwise, the implemented module in 6/b) was distributet to a certain number of other developers after some time (7/b).

	[[~~Image:sts05_stability1~~.~~png~~]]

	~~[[Image:sts05_stability2~~.~~png]]~~

	== Suitable for which data types ==		== Suitable for which data types ==

UE-InfoVis08-06 at 22:13, 8 May 2008

2008-05-08T22:13:13Z

← Older revision		Revision as of 22:13, 8 May 2008
Line 10:		Line 10:
	== Figures ==		== Figures ==

	[[Image:sts01_overview.png]]		The following images show specific visualisations by the "Augur" software.

			=== asdf ===

			<br/>[[Image:sts01_overview.png\|center\|400px\|test]]<br/>
	text		text

UE-InfoVis08-06 at 22:02, 8 May 2008

2008-05-08T22:02:39Z

← Older revision		Revision as of 22:02, 8 May 2008
Line 9:		Line 9:

	== Figures ==		== Figures ==

			[[Image:sts01_overview.png]]
			text

			[[Image:sts02_participation.png]]
			text

			[[Image:sts03_shifting1.png]]

			[[Image:sts03_shifting2.png]]

			[[Image:sts04_authorship.png]]

			[[Image:sts05_stability1.png]]

			[[Image:sts05_stability2.png]]

	== Suitable for which data types ==		== Suitable for which data types ==

62.178.18.209: data types

2008-05-08T21:58:08Z

data types

← Older revision		Revision as of 21:58, 8 May 2008
Line 11:		Line 11:

	== Suitable for which data types ==		== Suitable for which data types ==
			This visualization method is most suitable for source code. Properties of the software system and the source code itself are mapped to color and other features of a graphical display. Dependencies between methods (e.g. method A calls method B) and other parts of the source code are visualized. Also relationships between programmers can be graphically displayed. With this method it is easy to understand how different programmers are involved in the code production process and how their methods towards or away from the system's core. Even code ownerships can be tracked.

	== Evaluation ==		== Evaluation ==

62.178.18.209: citation

2008-05-08T21:47:44Z

citation

← Older revision		Revision as of 21:47, 8 May 2008
Line 6:		Line 6:
	== Short Description ==		== Short Description ==
	In distributed software development, the structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. The paper uncovers the structures of software projects and the ways in which development processes are inscribed into software artifacts. With open source communities as an example, a range of organizational processes and arrangements are uncovered in software repositories.		In distributed software development, the structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. The paper uncovers the structures of software projects and the ways in which development processes are inscribed into software artifacts. With open source communities as an example, a range of organizational processes and arrangements are uncovered in software repositories.

	~~== Important Citation ==~~

	{{Quotation\|Software development, then, is a particularly fruitful domain in which to study the relationship between technological artifacts and the social structures that shape them.\| [De Souza et al., 2005]}}		{{Quotation\|Software development, then, is a particularly fruitful domain in which to study the relationship between technological artifacts and the social structures that shape them.\| [De Souza et al., 2005]}}

62.178.18.209: citation

2008-05-08T21:46:06Z

citation

← Older revision		Revision as of 21:46, 8 May 2008
Line 5:		Line 5:

	== Short Description ==		== Short Description ==
	In distributed software development, the structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers~~. Each of these both shapes and reflects the development process~~. The paper uncovers the structures of software projects and the ways in which development processes are inscribed into software artifacts. With open source communities as an example, a range of organizational processes and arrangements are uncovered in software repositories.		In distributed software development, the structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. The paper uncovers the structures of software projects and the ways in which development processes are inscribed into software artifacts. With open source communities as an example, a range of organizational processes and arrangements are uncovered in software repositories.

	== Important Citation ==		== Important Citation ==

	{{Quotation\|~~Dummy~~\| [~~John Doe~~ et al., ~~2008~~]}}		{{Quotation\|Software development, then, is a particularly fruitful domain in which to study the relationship between technological artifacts and the social structures that shape them.\| [De Souza et al., 2005]}}

	== Figures ==		== Figures ==

62.178.18.209: evaluation & description

2008-05-08T21:39:39Z

evaluation & description

← Older revision		Revision as of 21:39, 8 May 2008
Line 4:		Line 4:
	* [[Dourish, Paul \| Paul Dourish]]		* [[Dourish, Paul \| Paul Dourish]]

	== Short ~~Desctiption~~ ==		== Short Description ==
	In distributed software development, ~~two sorts of dependencies can arise. The~~ structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. ~~Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover~~ the structures of software projects, and the ways in which development processes are inscribed into software artifacts. ~~We show how~~ a range of organizational processes and arrangements ~~can be~~ uncovered in software repositories~~, with implications for collaborative work in large distributed groups such as open source communities~~.		In distributed software development, the structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. The paper uncovers the structures of software projects and the ways in which development processes are inscribed into software artifacts. With open source communities as an example, a range of organizational processes and arrangements are uncovered in software repositories.

	== Important Citation ==		== Important Citation ==
Line 16:		Line 16:

	== Evaluation ==		== Evaluation ==
			{{Quotation\|In our informal evaluations, developers involved in distributed software development projects relied upon both the activity information and the structure information in coordination to develop a holistic view of software development activity.\| [De Souza et al., 2005]}}

	== References ==		== References ==

UE-InfoVis08-06 at 20:02, 8 May 2008

2008-05-08T20:02:02Z

← Older revision		Revision as of 20:02, 8 May 2008
Line 8:		Line 8:

	== Important Citation ==		== Important Citation ==

			{{Quotation\|Dummy\| [John Doe et al., 2008]}}

	== Figures ==		== Figures ==

UE-InfoVis08-06 at 20:00, 8 May 2008

2008-05-08T20:00:26Z

← Older revision		Revision as of 20:00, 8 May 2008
Line 4:		Line 4:
	* [[Dourish, Paul \| Paul Dourish]]		* [[Dourish, Paul \| Paul Dourish]]

	== ~~Abstract~~ ==		== Short Desctiption ==
	In distributed software development, two sorts of dependencies can arise. The structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover the structures of software projects, and the ways in which development processes are inscribed into software artifacts. We show how a range of organizational processes and arrangements can be uncovered in software repositories, with implications for collaborative work in large distributed groups such as open source communities.		In distributed software development, two sorts of dependencies can arise. The structure of the software system itself can create dependencies between software elements, while the structure of the development process can create dependencies between software developers. Each of these both shapes and reflects the development process. Our research concerns the extent to which, by looking uniformly at artifacts and activities, we can uncover the structures of software projects, and the ways in which development processes are inscribed into software artifacts. We show how a range of organizational processes and arrangements can be uncovered in software repositories, with implications for collaborative work in large distributed groups such as open source communities.

	== ~~Data Types~~ ==		== Important Citation ==

			== Figures ==

			== Suitable for which data types ==

			== Evaluation ==

	== References ==		== References ==