<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
	<id>https://wiki.kram.nz/index.php?action=history&amp;feed=atom&amp;title=SE450%3AG9</id>
	<title>SE450:G9 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.kram.nz/index.php?action=history&amp;feed=atom&amp;title=SE450%3AG9"/>
	<link rel="alternate" type="text/html" href="https://wiki.kram.nz/index.php?title=SE450:G9&amp;action=history"/>
	<updated>2026-06-08T20:02:40Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://wiki.kram.nz/index.php?title=SE450:G9&amp;diff=50&amp;oldid=prev</id>
		<title>Mark: New page: = PRESENTATION SLIDES = Download here: http://studwww.cs.auckland.ac.nz/~ezur001/SOFTENG_450.ppt -Danushka and Eddie  == Objectives == * To review and evaluate an article on Domain Specifi...</title>
		<link rel="alternate" type="text/html" href="https://wiki.kram.nz/index.php?title=SE450:G9&amp;diff=50&amp;oldid=prev"/>
		<updated>2008-02-15T19:52:43Z</updated>

		<summary type="html">&lt;p&gt;New page: = PRESENTATION SLIDES = Download here: http://studwww.cs.auckland.ac.nz/~ezur001/SOFTENG_450.ppt -Danushka and Eddie  == Objectives == * To review and evaluate an article on Domain Specifi...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;= PRESENTATION SLIDES =&lt;br /&gt;
Download here: http://studwww.cs.auckland.ac.nz/~ezur001/SOFTENG_450.ppt&lt;br /&gt;
-Danushka and Eddie&lt;br /&gt;
&lt;br /&gt;
== Objectives ==&lt;br /&gt;
* To review and evaluate an article on Domain Specific Visual Language (DSVL)&lt;br /&gt;
** Our article can be found at https://www.se.auckland.ac.nz/courses/SOFTENG450/resources/vlpapers/OCONVL99.pdf  (password protected)&lt;br /&gt;
&lt;br /&gt;
== Members == &lt;br /&gt;
&lt;br /&gt;
*Milenovic, Ivan (imil018)&lt;br /&gt;
*Abeysuriya, Danushka (dabe012)&lt;br /&gt;
*Halytskyy, Yuriy (yhal003)&lt;br /&gt;
*Clark, Kevin Alan (kcla048)&lt;br /&gt;
*Long, Ratha (rlon008)&lt;br /&gt;
*Zurita, Edmund (ezur001)&lt;br /&gt;
*Meads, Andrew (amea020)&lt;br /&gt;
&lt;br /&gt;
== Evaluation == &lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
=== Closeness of mapping ===&lt;br /&gt;
Metaphors are familiar to OOP designers (contract-based, polymorphic type systems).&lt;br /&gt;
Petri nets formalism is used for concurency modeling and may be familiar to those working &lt;br /&gt;
on distributed systems. At least has wikipedia page :). PN seem to have strong math. foundations&lt;br /&gt;
but whether it is necessary to know is unclear.&lt;br /&gt;
Conclusion - good.&lt;br /&gt;
&lt;br /&gt;
=== Abstraction gradient ===&lt;br /&gt;
&lt;br /&gt;
=== Consistency ===&lt;br /&gt;
&lt;br /&gt;
=== Difusiness ===&lt;br /&gt;
Allowes modeling at different abstraction levels (from contracts to resource sceduling).&lt;br /&gt;
So different level of verbosity possible. Separation of functional requirements from &lt;br /&gt;
distributed behaviour - diagrams are relatively small with only necessary details.&lt;br /&gt;
Entities can be expanded/hidden.&lt;br /&gt;
Conclusion - terse but users may give more details if needed making diagrams larger (more verbose).&lt;br /&gt;
So I gues - good.&lt;br /&gt;
&lt;br /&gt;
=== Error proneness ===&lt;br /&gt;
&lt;br /&gt;
=== Hard mental operations ===&lt;br /&gt;
&lt;br /&gt;
=== Hidden dependencies ===&lt;br /&gt;
&lt;br /&gt;
That is what VDSL is all about - figuring dependancies and resolving them automaticlly.&lt;br /&gt;
So shouldn&amp;#039;t be big problem ifOCoN is of any use.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;Contracts&amp;#039; define the behaviour between components (or entities) of the DSVL.  The dependency among different components are made visible through such contracts - hence good :).&lt;br /&gt;
&lt;br /&gt;
=== Premature commitment ===&lt;br /&gt;
&lt;br /&gt;
=== Progressive Evaluation ===&lt;br /&gt;
Possible to run simulations of scenarios. Type checking on the fly (?).&lt;br /&gt;
Not clear if there is progressive validation.&lt;br /&gt;
Conclusion - average&lt;br /&gt;
&lt;br /&gt;
=== Role expressiveness ===&lt;br /&gt;
&lt;br /&gt;
=== Secondary notation ===&lt;br /&gt;
&lt;br /&gt;
=== Viscosity ===&lt;br /&gt;
&lt;br /&gt;
Modular - may be easy to replace contracts. Polymorphic type system seems to help.&lt;br /&gt;
Diagrams similar to state machines so can become large. Rearanging elements may be time-consuming.&lt;br /&gt;
&lt;br /&gt;
=== Visibility ===&lt;br /&gt;
&lt;br /&gt;
=== Cognitive Dimension===&lt;br /&gt;
more blah&lt;br /&gt;
&lt;br /&gt;
=== Pros ===&lt;br /&gt;
* Concurrency did not have a visual model before this&lt;br /&gt;
* Concept is easy for Object Oriented Programmers to understand because of the use a polymorphic-type system&lt;br /&gt;
* A good separation of concerns (the protocol net &lt;br /&gt;
* Well known formalism for modelling concurrency&lt;br /&gt;
* Good metaphor for the procedural calls&lt;br /&gt;
* Consistency among views &lt;br /&gt;
=== Cons ===&lt;br /&gt;
* Limited to Object oriented architectures&lt;br /&gt;
* Not much of an improvement over something that already exists (statechart) - although that may be why there is not much wrong with it&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Conclusion ==&lt;br /&gt;
* Simple improvement to include an important concept of distributed system design&lt;br /&gt;
* Visual notation is something we are somewhat familiar with.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Presentation ==&lt;br /&gt;
* Presenter: Danushka&lt;br /&gt;
* Downloadable here: &amp;lt;not here yet&amp;gt;&lt;/div&gt;</summary>
		<author><name>Mark</name></author>
	</entry>
</feed>