<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM2Lopes2</id>
	<title>WG211/M2Lopes2 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://mw.hh.se/wg211/index.php?action=history&amp;feed=atom&amp;title=WG211%2FM2Lopes2"/>
	<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M2Lopes2&amp;action=history"/>
	<updated>2026-04-05T22:41:16Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.5</generator>
	<entry>
		<id>http://mw.hh.se/wg211/index.php?title=WG211/M2Lopes2&amp;diff=99&amp;oldid=prev</id>
		<title>Admin: 1 revision</title>
		<link rel="alternate" type="text/html" href="http://mw.hh.se/wg211/index.php?title=WG211/M2Lopes2&amp;diff=99&amp;oldid=prev"/>
		<updated>2011-12-12T10:06:24Z</updated>

		<summary type="html">&lt;p&gt;1 revision&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[Category:WG211]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Title:&lt;br /&gt;
&lt;br /&gt;
An Economics-Based Model for Assessing Program Modularity&lt;br /&gt;
&lt;br /&gt;
Cristina Videira Lopes&lt;br /&gt;
&lt;br /&gt;
Abstract:&lt;br /&gt;
In the second part of the talk, I will present a radically new approach for assessing modular software design. The underlying question is &amp;quot;how can we assess the value of dividing a software system into modules, and why are certain modularizations better than others?&amp;quot; This question is, of course, related to the continuous flow of new solutions and technologies for improving software development, including OOP, AOP, and all generative approaches. While empirical studies can show the benefits of these technologies, they don&amp;#039;t provide any insights as for &amp;#039;&amp;#039;&amp;#039;why&amp;#039;&amp;#039;&amp;#039; these technologies are beneficial. Recently, I stumbled across an economics-based model of modularity that gave me hope of understanding the hidden issues behind the word &amp;#039;better.&amp;#039;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>