Login | Register
My pages Projects Community openCollabNet

Discussions > Commits > svn commit: r116 - trunk/www/index.html

argouml-spl
Discussion topic

Back to topic list

svn commit: r116 - trunk/www/index.html

Author marcusvnac
Full name Marcus Vinícius de Ávila Couto
Date 2010-09-11 14:00:44 PDT
Message Author: marcusvnac
Date: 2010-09-11 14:00:43-0700
New Revision: 116

Modified:
   trunk/www/index.html

Log:


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​16&r1=115&r2​=116
====================​====================​====================​==================
--- trunk/www/index.html (original)
+++ trunk/www/index.html 2010-09-11 14:00:43-0700
@@ -33,12 +33,13 @@
 
 <p>At the moment, we have already modularized the following features:</p>
 <ul>
- <li>Design Critics: "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>State Diagrams: "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>Activity Diagrams: "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>Sequence Diagrams: "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>Use Case Diagrams: "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>Logging: "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>
+ <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>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>

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

Messages

Show all messages in topic

svn commit: r116 - trunk/www/index.html marcusvnac Marcus Vinícius de Ávila Couto 2010-09-11 14:00:44 PDT
Messages per page: