Login | Register
My pages Projects Community openCollabNet

Discussions > Commits > svn commit: r157 - trunk/www: . cn-project-pages cn-project-pages/snippets

argouml-spl
Discussion topic

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

Back to topic list

svn commit: r157 - trunk/www: . cn-project-pages cn-project-pages/snippets

Author marcusvnac
Full name Marcus Vinícius de Ávila Couto
Date 2020-02-10 12:06:13 PST
Message Author: marcusvnac
Date: 2020-02-10 12:06:11-0800
New Revision: 157

Added:
   trunk/www/cn-project-pages/
   trunk/www/cn-project​-pages/snippets/
   trunk/www/cn-project​-pages/snippets/page​.xml
Modified:
   trunk/www/index.html

Log:
Updated html component "Adding GitHub info" through the web interface.

Added: trunk/www/cn-project​-pages/snippets/page​.xml
Url: http://argouml-spl.t​igris.org/source/bro​wse/argouml-spl/trun​k/www/cn-project-pag​es/snippets/page.xml​?view=markup&pat​hrev=157
====================​====================​====================​==================
--- (empty file)
+++ trunk/www/cn-project​-pages/snippets/page​.xml 2020-02-10 12:06:11-0800
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<page visibility="1">
+ <component_list>
+ <component visibility="1" type="ProjectMetadata" order="1">
+ <title localize="false" />
+ </component>
+ <component visibility="1" type="Html" order="2">
+ <title localize="false">Adding GitHub info</title>
+ <filename>inde​x.html</filename​>
+ </component>
+ <component visibility="1" type="Subproject" order="3">
+ <title localize="true">S​ubprojects</title​>
+ </component>
+ </component_list>
+</page>
+

Modified: trunk/www/index.html
Url: http://argouml-spl.t​igris.org/source/bro​wse/argouml-spl/trun​k/www/index.html?vie​w=diff&pathrev=1​57&r1=156&r2​=157
====================​====================​====================​==================
--- trunk/www/index.html (original)
+++ trunk/www/index.html 2020-02-10 12:06:11-0800
@@ -1,143 +1,147 @@
-<html>
-<head>
-<meta name="keywords"
- content="ArgoUML, Argo, Software Product Line, SPL, Feature, UML, Unified Modeling Language, modeling, modelling, MDA, model-driven, software architecture, software methods, software engineering, CASE, Java, XML, OCL, object, technology">
-
- <style type="text/css">
-/* <![CDATA[ */
-@import "http://www.tigris.or​g/branding/css/tigri​s.css";
-@import "http://www.tigris.or​g/branding/css/inst.​css";
-/* ]]> */
- </style>
- <link rel="stylesheet" type="text/css" href="http://www.tigris.or​g/branding/css/print​.css" media="print" />
-<script src="http://www.tigris.or​g/branding/scripts/t​igris.js" type="text/javascript">
-</script>
- <title>Software Product Line for ArgoUML :: ArgoUML-SPL</title>
-</head>
-<body>
-
-<div class="h2">
-<h2>Descripti​on</h2>
-
-<p>ArgoUML-SPL is a project that aims to extract a SPL from the current ArgoUML codebase.</p>
-
-<p>Software product lines (SPL) are basically a software development methodology that advocates that software should be designed and implemented by composing together particular features (or variabilities) with a pre-defined set of core components. The ultimate goal is to promote the generation of systems that meet the requirements of particular users, domains or environments.</p>
-
-<p>Despite several research in this field, we have not many concrete and public examples of systems implemented according to SPL principles. For example, it is common to have systems that use preprocessor directives (e.g. #ifdef and #ifndef) to support low-level variabilities (such as different APIs or application specific configuration options), but not high-level features. On the other hand, there are attempts to implement end-users features using technologies such as AOP. However, such attempts are based on small and fairly simple systems.</p>
-</div>
-
-<div class="h3">
-<h3>Mission</h3>
-
-<p>Our ultimate goal is to deliver a version of ArgoUML where end-users can remove (or add) features from the system codebase.</p>
-
-<p>At the moment, we have already modularized the following features:</p>
-<ul>
- <li><b>Design Critics</b>: "Simple agents that continuously execute in a background thread of control. They analyze the design as the designer is working and suggest possible improvements. These suggestions range from indications of syntax errors, to reminders to return to parts of the design that need finishing, to style guidelines, to the advice of expert designers."</li>
- <li><b>State Diagrams</b>: "State diagrams are used to describe the behavior of a system. State diagrams describe all of the possible states of an object as events occur. Each diagram usually represents objects of a single class and track the different states of its objects through the system."</li>
- <li><b>Activity Diagrams</b>: "Activity diagrams describe the workflow behavior of a system. Activity diagrams are similar to state diagrams because activities are the state of doing something. The diagrams describe the state of activities by showing the sequence of activities performed."</li>
- <li><b>Sequence Diagrams</b>: "Interaction diagrams model the behavior of use cases by describing the way groups of objects interact to complete the task. Sequence Diagram displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects)."</li>
- <li><b>Use Case Diagrams</b>: "A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. The two main components of a use case diagram are use cases and actors."</li>
- <li><b>C​ollaboration Diagrams</b>: "Collaboration diagrams are used to show how objects interact to perform the behavior of a particular use case, or a part of a use case. Along with sequence diagrams, collaborations are used by designers to define and clarify the roles of the objects that perform a particular flow of events of a use case. They are the primary source of information used to determining class responsibilities and interfaces."</li>
- <li><b>Deployment Diagrams</b>: "A deployment diagram models the run-time architecture of a system. It shows the configuration of the hardware elements (nodes) and shows how software elements and artifacts are mapped onto those nodes."</li>
- <li><b>L​ogging</b>: "The purpose of debug log and trace messages is to provide a mechanism that allows the developer to enable output of minor events focused on a specific problem area and to follow what is going on inside ArgoUML."</li>
-</ul>
-</div>
-
-<div class="h3">
-<h3>Feature Model</h3>
-<br>
-<center><img align="middle" alt="ArgoUML-SPL Feature Model" src="images/ArgoUML-​SPL_FeatureModel.png​"></center>​
-
-<div class="h3">
-<h3>Feature Extraction Mechanism</h3>
-
-<p>At the moment, we are using pre-processor directives in order to modularize and delimit our feature's code. Currently, our implementation is based on the <a href="http://www.slashdev.ca/javapp/">javapp</a> pre-processor.</p>
-
-<p>Examples of Products:</p>
-<ul>
- <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_full.zip​">Product 1: Full ArgoUML application</a> (including the four mentioned features)
- <p>Size: 120,348 TLOC - ZIP File (6,458,926 bytes)</p>
- </li>
- <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_no-featu​res.zip">Product 2: ArgoUML without the eight mentioned features</a>
- <p>Size: 82,924 TLOC - ZIP File (6,028,146 bytes)</p>
- </li>
- <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_no-cogni​tive.zip">Product 3: ArgoUML without Design Critics feature</a>
- <p>Size: 104,029 TLOC - ZIP File (6,105,454 bytes)</p>
- </li>
-</ul>
-</div>
-
-<div class="h3">
-<h3>Academic paper</h3>
-<ul>
- <li><p>Marcus Vin&iacute;cius Couto; Marco T&uacute;lio Valente; Eduardo Figueiredo. <a href="http://argouml-spl.t​igris.org/publicatio​ns/argouml-spl_csmr_​2011.pdf">Extracting Software Product Lines: A Case Study Using Conditional Compilation.</a> 15th European Conference on Software Maintenance and Reengineering (CSMR), p. 191-200, 2011.</p></li>
-</ul>
-</div>
-
-<div class="h3">
-<h3>How can I collaborate?</h3>
-
-<p>Everybody is welcome to help with developing and testing ArgoUML-SPL.</p>
-
-<p>Suggestions can be send through the <a href="http://argouml-spl.t​igris.org/ds/viewFor​umSummary.do?dsForum​Id=9411">Developers Mailing List</a> or to Marcus Vin&iacute;cius de &Aacute;vila Couto (ArgoUML-SPL project leader) through the form below.</p>
-
-<br>
-
-<table align="center">
- <tr>
- <td>
- <!-- Begin Freedback Form -->
- <form enctype="multipart/form-data" method="post" action="http://www.freedback​.com/mail.php" accept-charset="UTF-8" >
- <div>
- <input type="hidden" name="acctid" id="acctid" value="njhc996q8fb7r5lr" />
- <input type="hidden" name="formid" id="formid" value="749776" />
- <input type="hidden" name="required_vars" id="required_vars" value="name,email,fi​eld-4bc532f257266af"​ />
- </div>
- <table cellspacing="5" cellpadding="5" border="0">
- <tr>
- <td valign="top">Name​:</td>
- <td valign="top">
- <input type="text" name="name" id="name" size="40" value="" />
-
- </td>
- </tr>
- <tr>
- <td valign="top">Email Address:</td>
- <td valign="top">
- <input type="text" name="email" id="email" size="40" value="" />
-
- </td>
- </tr>
- <tr>
- <td valign="top">Suggestions to ArgoUML-SPL:</td>
- <td valign="top">
- <textarea name="field-4bc532f257266af" id="field-4bc532f257266af" rows="6" cols="40"></textarea>
-
- </td>
- </tr>
- <tr>
- <td colspan="2" align="center">
- <input type="submit" value=" Submit Suggestion " />
- </td>
- </tr>
- </table>
- </form>
- </td>
- </tr>
-</table>
-<!-- End Freedback Form -->
-
-</div>
-
-<div class="h3">
-<h3>Related Resources</h3>
-
-<ul>
- <li><a href="http://argouml.tigris.org/" target="_blank">A​rgoUML</a><​/li>
- <li><a href="http://argouml-spl.t​igris.org/psf/argoum​l-spl_core-projectSe​t.psf" target="_blank">Team Project Set file for ArgoUML-SPL</a​></li>
-</ul>
-</div>
-
-</body>
-</html>
\ No newline at end of file
+<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <html>
+<head>
+<meta name="keywords"
+ content="ArgoUML, Argo, Software Product Line, SPL, Feature, UML, Unified Modeling Language, modeling, modelling, MDA, model-driven, software architecture, software methods, software engineering, CASE, Java, XML, OCL, object, technology">
+
+ <style type="text/css">
+/* <![CDATA[ */
+@import "http://www.tigris.or​g/branding/css/tigri​s.css";
+@import "http://www.tigris.or​g/branding/css/inst.​css";
+/* ]]> */
+ </style>
+ <link rel="stylesheet" type="text/css" href="http://www.tigris.or​g/branding/css/print​.css" media="print" />
+<script src="http://www.tigris.or​g/branding/scripts/t​igris.js" type="text/javascript">
+</script>
+ <title>Software Product Line for ArgoUML :: ArgoUML-SPL</title>
+</head>
+<body>
+
+<div class="h2">
+<h2>Descripti​on</h2>
+
+<p>ArgoUML-SPL is a project that aims to extract a SPL from the current ArgoUML codebase.</p>
+
+<p>Software product lines (SPL) are basically a software development methodology that advocates that software should be designed and implemented by composing together particular features (or variabilities) with a pre-defined set of core components. The ultimate goal is to promote the generation of systems that meet the requirements of particular users, domains or environments.</p>
+
+<p>Despite several research in this field, we have not many concrete and public examples of systems implemented according to SPL principles. For example, it is common to have systems that use preprocessor directives (e.g. #ifdef and #ifndef) to support low-level variabilities (such as different APIs or application specific configuration options), but not high-level features. On the other hand, there are attempts to implement end-users features using technologies such as AOP. However, such attempts are based on small and fairly simple systems.</p>
+</div>
+
+<div class="h3">
+<h3>Mission</h3>
+
+<p>Our ultimate goal is to deliver a version of ArgoUML where end-users can remove (or add) features from the system codebase.</p>
+
+<p>At the moment, we have already modularized the following features:</p>
+<ul>
+ <li><b>Design Critics</b>: "Simple agents that continuously execute in a background thread of control. They analyze the design as the designer is working and suggest possible improvements. These suggestions range from indications of syntax errors, to reminders to return to parts of the design that need finishing, to style guidelines, to the advice of expert designers."</li>
+ <li><b>State Diagrams</b>: "State diagrams are used to describe the behavior of a system. State diagrams describe all of the possible states of an object as events occur. Each diagram usually represents objects of a single class and track the different states of its objects through the system."</li>
+ <li><b>Activity Diagrams</b>: "Activity diagrams describe the workflow behavior of a system. Activity diagrams are similar to state diagrams because activities are the state of doing something. The diagrams describe the state of activities by showing the sequence of activities performed."</li>
+ <li><b>Sequence Diagrams</b>: "Interaction diagrams model the behavior of use cases by describing the way groups of objects interact to complete the task. Sequence Diagram displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects)."</li>
+ <li><b>Use Case Diagrams</b>: "A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. The two main components of a use case diagram are use cases and actors."</li>
+ <li><b>C​ollaboration Diagrams</b>: "Collaboration diagrams are used to show how objects interact to perform the behavior of a particular use case, or a part of a use case. Along with sequence diagrams, collaborations are used by designers to define and clarify the roles of the objects that perform a particular flow of events of a use case. They are the primary source of information used to determining class responsibilities and interfaces."</li>
+ <li><b>Deployment Diagrams</b>: "A deployment diagram models the run-time architecture of a system. It shows the configuration of the hardware elements (nodes) and shows how software elements and artifacts are mapped onto those nodes."</li>
+ <li><b>L​ogging</b>: "The purpose of debug log and trace messages is to provide a mechanism that allows the developer to enable output of minor events focused on a specific problem area and to follow what is going on inside ArgoUML."</li>
+</ul>
+</div>
+
+<div class="h3">
+<h3>Feature Model</h3>
+<br>
+<center><img align="middle" alt="ArgoUML-SPL Feature Model" src="images/ArgoUML-​SPL_FeatureModel.png​"></center>​
+
+<div class="h3">
+<h3>Feature Extraction Mechanism</h3>
+
+<p>At the moment, we are using pre-processor directives in order to modularize and delimit our feature's code. Currently, our implementation is based on the <a href="http://www.slashdev.ca/javapp/">javapp</a> pre-processor.</p>
+
+<p>Examples of Products:</p>
+<ul>
+ <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_full.zip​">Product 1: Full ArgoUML application</a> (including the four mentioned features)
+ <p>Size: 120,348 TLOC - ZIP File (6,458,926 bytes)</p>
+ </li>
+ <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_no-featu​res.zip">Product 2: ArgoUML without the eight mentioned features</a>
+ <p>Size: 82,924 TLOC - ZIP File (6,028,146 bytes)</p>
+ </li>
+ <li><a href="http://argouml-spl.t​igris.org/downloads/​argouml-spl_no-cogni​tive.zip">Product 3: ArgoUML without Design Critics feature</a>
+ <p>Size: 104,029 TLOC - ZIP File (6,105,454 bytes)</p>
+ </li>
+</ul>
+</div>
+
+<div class="h3">
+<h3>Academic paper</h3>
+<ul>
+ <li><p>Marcus Vin&iacute;cius Couto; Marco T&uacute;lio Valente; Eduardo Figueiredo. <a href="http://argouml-spl.t​igris.org/publicatio​ns/argouml-spl_csmr_​2011.pdf">Extracting Software Product Lines: A Case Study Using Conditional Compilation.</a> 15th European Conference on Software Maintenance and Reengineering (CSMR), p. 191-200, 2011.</p></li>
+</ul>
+</div>
+
+<div class="h3">
+<h3>How can I collaborate?</h3>
+
+<p>Everybody is welcome to help with developing and testing ArgoUML-SPL.</p>
+
+<p>The most up to date code it is now hosted on <a href="https://github.com/m​arcusvnac/argouml-sp​l" target="_blank">G​itHub</a></​p>
+
+<p>Suggestions can be send through the <a href="http://argouml-spl.t​igris.org/ds/viewFor​umSummary.do?dsForum​Id=9411">Developers Mailing List</a> or to Marcus Vin&iacute;cius de &Aacute;vila Couto (ArgoUML-SPL project leader) through the form below.</p>
+
+<br>
+
+<table align="center">
+ <tr>
+ <td>
+ <!-- Begin Freedback Form -->
+ <form enctype="multipart/form-data" method="post" action="http://www.freedback​.com/mail.php" accept-charset="UTF-8" >
+ <div>
+ <input type="hidden" name="acctid" id="acctid" value="njhc996q8fb7r5lr" />
+ <input type="hidden" name="formid" id="formid" value="749776" />
+ <input type="hidden" name="required_vars" id="required_vars" value="name,email,fi​eld-4bc532f257266af"​ />
+ </div>
+ <table cellspacing="5" cellpadding="5" border="0">
+ <tr>
+ <td valign="top">Name​:</td>
+ <td valign="top">
+ <input type="text" name="name" id="name" size="40" value="" />
+
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">Email Address:</td>
+ <td valign="top">
+ <input type="text" name="email" id="email" size="40" value="" />
+
+ </td>
+ </tr>
+ <tr>
+ <td valign="top">Suggestions to ArgoUML-SPL:</td>
+ <td valign="top">
+ <textarea name="field-4bc532f257266af" id="field-4bc532f257266af" rows="6" cols="40"></textarea>
+
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2" align="center">
+ <input type="submit" value=" Submit Suggestion " />
+ </td>
+ </tr>
+ </table>
+ </form>
+ </td>
+ </tr>
+</table>
+<!-- End Freedback Form -->
+
+</div>
+
+<div class="h3">
+<h3>Related Resources</h3>
+
+<ul>
+ <li><a href="https://github.com/m​arcusvnac/argouml-sp​l" target="_blank">ArgoUML-SPL on GitHub</a></li>
+ <li><a href="http://argouml.tigris.org/" target="_blank">A​rgoUML</a><​/li>
+ <li><a href="http://argouml-spl.t​igris.org/psf/argoum​l-spl_core-projectSe​t.psf" target="_blank">Team Project Set file for ArgoUML-SPL</a​></li>
+</ul>
+</div>
+
+</body>
+</html>
+
\ No newline at end of file

« Previous message in topic | 1 of 1 | Next message in topic »

Messages

Show all messages in topic

svn commit: r157 - trunk/www: . cn-project-pages cn-project-pages/snippets marcusvnac Marcus Vinícius de Ávila Couto 2020-02-10 12:06:13 PST
Messages per page: