Home

ArgoUML: Manual de Usuario - Departamento de Informática da

1. 0eeee ee 137 15 4 5 Role name conflicts with Member oocooccoccnccncnnconcnnconcnnroncnnnonos 137 15 4 6 Choose a Name Classes and Interfaces oooocoocococcconononnnncnnoos 137 15 4 7 Choose a Unique Name for an Artifact Classes and Interfaces 137 15 4 8 Choose a Name Attributes oooococccnccnocncnconcnccnoncncnncnncncncnnos 138 15 4 9 Choose a Name Operations ocooccoccocnoconcnnconcnnconcnnconcnnroncnaronos 138 15 4 10 Choose a Name States ocoocoococococnnconcncncnncnnnnnncnnnncnncnancnnos 138 15 4 11 Choose a Unique Name for a State related Artifact 138 15 4 12 Revise Name to Avoid Confusion ocooccocnoconcnoconcnoconcnnroncnnnonos 138 15 4 13 Choose a Legal Name ooocccccnnccnnconnconnconnccnnconnconncnnncnnncnnnonoss 138 15 4 14 Change an Artifact to a Non Reserved Word eeeeeeeee ee 138 15 4 15 Choose a Better Operation Name cece eee eee ceeeeeeeee teen es 138 15 4 16 Choose a Better Attribute Name oooccoccncnnconcnnconcnnconcnnconcnnnonos 139 15 4 17 Capitalize Class Name viennoiserie se r E E TE SEE 139 15 4 18 Revise Package Name ooocccoccnnccnnconnconnconnconconoconnconncnnncnoronose 139 SA heia rr tends O EEEE ta pushes inde goa EE EEE E REE eE 139 15 5 1 Revise Attribute Names to Avoid Conflict oocooccoccncnoccncnnconos 139 15 5 2 Add Instance Variables to a Class ocooccocnoccncnnconcnnconcnnronanano
2. ccccec cece cece ec eeeceee eens sence ee eeneaeeneneenens 55 6 5 2 Class Attributes and Operations To be written coocooccnccoccncnoconcnns 56 6 5 3 Advanced Class Features oocooccoconcnoconcnnconcnononcnoroncnoroncnnroncnarononns 56 6 6 Sequence and Collaboration Diagrams To be written ooooccocccnccnnccnnccnniono 37 6 6 1 More on the Sequence Diagram To be written eee 37 6 6 2 The Collaboration Diagram To be written oocooccocnoccncnoconcnonononns 57 6 6 3 Advanced Collaboration Diagrams To be written ce eee seen ee 57 6 7 Creating Collaboration Diagrams in ArgoUML To be written 57 6 7 1 Collaboration Diagrams To be written cooccoccoconcnoconcnononcnnronanns 57 6 7 2 Messages To be Written occoococcnocccononocononocononononanononanorinanoninns 57 6 7 3 Advanced Collaboration Diagrams To be written oocooccoccnccoccnc 57 6 8 Statechart Diagrams To be Written oocooccoccocnncnoconcnnconcnnroncnnconcnnronannnos 57 6 8 1 The Statechart Diagram To be written ocoocooccoconcnoconcnnnoncnnnononns 57 6 8 2 Advanced Statechart Diagrams To be written o coccoccocnoccncnononcnns 57 6 9 Creating Statechart Diagrams in ArgoUML To be written ee 58 6 9 1 Statechart Diagrams To be written ocoocooccoccncnoconcnoconcnnroncnanonanns 58 69 20 tates To De written ses a ad dia aa 58 6 9 3 Transitions
3. Note The ArgoUML critics will complain about attribute names that do not have an initial lower case letter Stereotype 197 Class Diagram Artifact Reference Drop down selector There are no UML standard stereotypes for Attribute Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Owner Text box Records the class which contains this attribute Button 1 double click on the entry will navigate to the class Multiplicity Editable drop down selector The default value 1 is that there is one instance of this attribute for each instance of the class i e it is a scalar The drop down provides a number of commonly used specifications for non scalar attributes Note ArgoUML presents a number of predefined ranges for multiplicity for easy access The user may also enter any user defined range that follows the UML syntax such as 1 3 7 10 The value 1 1 is equivalent to the default exactly one scalar instance The selec tion O 1 indicates an optional scalar attribute Type Drop down selector The type of this attribute This can be any UML Classifier although in practice only Class DataType or Interface make any sense Note A type must be declared it can be void By default ArgoUML supplies int as the type Navigate Type icon This will navigate to the property panel for the currently sel
4. e derived from the superclass ModelElement Values true meaning the dependency rela tionship is redundant it can be formally derived from other elements or false meaning it cannot Note Derived dependencies still have their value in analysis to introduce useful names or concepts 18 13 2 Dependency Property Toolbar Go up Navigate up through the package structure of the model For a dependency this will be the package containing the dependency New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected dependency navig ating immediately to the properties tab for that stereotype Delete This deletes the selected dependency from the model Warning This is a deletion from the model not just the diagram To delete a dependency from the diagram but keep it within the model use the main menu Remove From Dia gram or press the Delete key 18 13 3 Property Fields For Dependency Name Text box The name of the dependency 217 Class Diagram Artifact Reference Tip It is quite common to leave dependencies unnamed Note ArgoUML does not enforce any naming convention for associations Note There is no representation of the name of a dependency on the diagram Stereotype Drop down selector Dependency has no standard stereotypes of its own under UML 1 3 and so ArgoUML does not provide any The stereotype is shown between and above or across
5. It is sometimes useful to give simple names to stimuli so they can be referred to in at tached notes giving timing constraints Action Text box This is used to identify the action that generated the stimulus Caution The current release of ArgoUML only implements actions as textual descriptions As a practical convention it is suggested that call actions are shown as the name of the operation generating the action with any arguments in parentheses and that send ac 230 Sequence Diagram Artifact Reference tions are shown as the name of the signal generating the action with any arguments in parentheses Return actions should be shown as the expression for the value they re turn or empty otherwise Create and destroy actions should be left empty since they are implied by their representation Stereotype Drop down selector Stimulus has no stereotypes by default in the UML standard but ArgoUML provides the stereotypes machine organization and person Caution ArgoUML also provides the stereotype realize for stimuli This appears to be an error since this stereotype properly belongs to the Abstraction metaclass Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 18 4 Stereotype Sender Text box Identifies the instance which sent this stimulus Button 1 click navigates to the sender instance button 2 gives a pop up menu with on
6. Note This field shows the name of the transition while on the diagram the name of the trig ger is shown separated with a from the effect script Button 1 double click navigates to the selected transition button 2 gives a pop up menu with one entry e New Add a new internal transition 20 3 Action An action specifies an executable statement and is an abstraction of a computational procedure that can change the state of the model In the UML metamodel it is a child of ModelElement Since in the metamodel an ActionSequence is itself an Action that is an aggregation of other actions i e the com posite pattern an ActionSequence may be used anywhere an action may be There are a number of different types of action that are children of Action within the UML metamodel e CreateAction Associated with a classifier this action creates an instance of that classifier e CallAction Associated with an operation this action calls the given operation e ReturnAction An action used to return a result to an earlier caller e SendAction Associated with a signal this action causes the signal to be raised e TerminateAction Causes the invoking object to self destruct e UninterpretedAction An action used to specify language specific actions that do not classify under the other types of actions e DestroyAction Destroys the specified target object An action is represented on the diagram by the text of its expression Cau
7. e New Operation Only appears where the selected artifact is a class or interface Creates a new op eration on the artifact e New Comment Attaches a new comment to the selected artifact e Add All Relations Only appears where the selected artifact is a class or interface Makes all relations visible that exist in the model and that are connected to the selected artifact Remove all Relations Only appears where the selected artifact is a class or interface Re moves all connected relations from the diagram without removing them from the model 12 9 4 Show This sub menu only appears with certain artifacts It is completely context dependent There are many possible entries depending on the selected artifact and its state e Hide Extension Point Compartment Only appears when the extension point compartment of a use case is displayed Hides the compartment e Show Extension Point Compartment Only appears when the extension point compartment of a use case is hidden Displays the compartment e Hide All Compartments Only appears when both attribute and operation compartments are displayed on a class or object Hides both compartments e Show All Compartments Only appears when both attribute and operation compartments are hidden on a class or object Displays both compartments e Hide Attribute Compartment Only appears when the attribute compartment of a class or object is displayed Hides the compartment e Show
8. for stereotypes clear by default By default ArgoUML uses pairs of less than and greater than lt lt gt gt characters for stereotypes If this box is checked stereotypes on dia grams are shown between true guillemots This feature is presumably added to ArgoUML because guillemots are poorly supported by various fonts and if they are present then they are quite small and poorly visible Show visibility clear by default If this is selected then ArgoUML will show the visibility in dicators in front of e g attributes in the diagram In UML the notation is for public for private for protected and for package E g for an attribute it may show newAttr int Show multiplicity clear by default If this is selected then ArgoUML will show the multipli city of e g attributes in the diagram In UML notation the multiplicity is shown between such as newAttr 0 int This setting has no impact on showing multiplicity near association ends Show initial value clear by default If this is selected then ArgoUML will show the initial value of e g attributes in the diagram In UML notation the initial value is shown e g like this newAttr int 1 Show properties clear by default If this is selected then ArgoUML will show various proper ties between braces E g for an attribute it may show newAttr int frozen Show types and parameters set by default When this chec
9. A 2 3 Supplementary Requirements Specification To be written To be written 298 Appendix B UML resources B 1 The UML specs To be written To be written B 2 UML related papers To be written To be written B 2 1 UML action specifications To be written To be written B 3 UML related websites To be written To be written 299 Appendix C UML Conforming CASE Tools C 1 Other Open Source Projects To be writ ten To be written C 2 Commercial Tools To be written To be written 300 Appendix D The C Module The ArgoUML C Module C Mod provides C code generation functionalities and C nota tion within ArgoUML It works the same way as the other languages modules D 1 Modeling for C D 1 1 The C programming language has constructs that aren t contained by default in UML Examples are pointers global functions and variables references and operator overloading To enable us to apply these constructs in our models and be capable of taking advantage of it for code generation and C notation in UML diagrams the C module uses conventions in the use of the extension features of UML tagged values and stereotypes Since UML and C are object oriented there is an obvious correspondence between the UML model elements and C structural constructs e g the UML Class is related to the C class These obvi ous relations will not be descr
10. Operation Property Toolbar or the button 2 pop up menu for the class on the diagram 18 7 3 Property Fields For Operation Name Text box The name of the operation The name of an operation has a leading lower case letter with words separated by bumpy caps Note The ArgoUML critics will complain about operation names that do not have an initial lower case letter 201 Class Diagram Artifact Reference Tip If you wish to follow the Java convention of constructors having the same name as the class you will violate this rule Silence the critic by setting the stereotype create for the constructor operation Stereotype Drop down selector There are two UML standard stereotypes for Operation from the parent metaclass BehavioralFeature create and destroy Tip You should use create as the stereotype for constructors and destroy for de structors which are called finalize methods under Java Navigate Stereotype icon If a stereotype has been selected clicking button 1 will navigate to the stereotype property panel see Section 18 4 Stereotype Owner Text box Records the class which contains this operation Button 1 double click on the entry will navigate to the class Visibility Radio box with entries public private protected and package e public The operation is available to any artifact that can see the owning class e private The operation is available only to the ow
11. Stereotype Namespace Drop down selector Records and allows changing the namespace for the abstraction This is the package hierarchy Suppliers Text area Lists the artifact that is the supplier end of this abstraction for a realization this is the end providing the implementation Note Although this is a text area there is no mechanism for adding more than one supplier Button 1 double click navigates to the selected entry Clients Text area Lists the artifact that is the client end of this abstraction for a realization this is the end providing the specification Note Although this is a text area there is no mechanism for adding more than one client Button 1 double click navigates to the selected entry 224 Chapter 19 Sequence Diagram Artifact Reference 19 1 Introduction This chapter describes each artifact that can be created within a sequence diagram Note that some sub artifacts of artifacts on the diagram may not actually themselves appear on the diagram There is a close relationship between this material and the Properties tab of the details pane see Section 13 3 Properties Tab That section covers properties in general in this chapter they are linked to specific artifacts Caution Sequence diagrams are not fully developed yet in ArgoUML Many aspects are not fully implemented or may not behave as expected Figure 19 1 Possible artifacts on a sequence diagram show
12. The V0 20 version of ArgoUML implementation is incomplete The reason given is not stored when the project is saved And there is no way to retrieve todo items that were re solved So it is not usefull to give a reason at all When a todo item generated by a critic is resolved then there is no way to undo this unless by re creating the object that triggered the critic e Send Email To Expert Activating this tool allows the user to send an Email to an expert asking for advice This works like clicking a mailto users O argouml tigris org subject critic head er link in your webbrowser e Snooze Critic This suspends the activity of the critic that generated the current to do item The to do item and all others generated by the critic will disappear from the to do pane The critic will wake up after a period of time Initially this period is 10 minutes but it doubles on each successive application of the Snooze button The critic can be awakened explicitly through the Cri tique gt Browse Critics menu see Section 10 9 4 Browse Critics Tip Some common critics can fire the whole time as you build a big diagram Some users find it useful to snooze these critics until the diagram has been completed 13 2 1 Wizards Some of the more common critics have a wizard available to help in fixing the problem The wizard comprises a series of pages one or more in the ToDo Item tab that step you through the
13. 34 Captura de Requerimientos caso de que una visita de mantenimiento de rutina se halla dejado pasar Caution Evita pre condiciones todo lo posible Necesitas tener la absoluta certeza de que las pre condiciones caben bajo todas las posibles circunstancias Si no tu sistema estar debil mente especificado y por lo tanto fallara cuando la pre condici n no es cierta Altern ativamente cuando no tienes la certeza de que la pre condici n es siempre cierta ne cesitaras especificar un segundo caso de uso para manejar la pre condici n siendo falsa En el primer caso las pre condiciones son una fuente de problemas en el segundo una fuente de mas trabajo Flujo B sico La secuencia lineal de pasos que descruben el comportamiento de el caso de uso en el escenar o normal Donde un caso de uso tiene un n mero de escenarios que podr an ser nor males uno es seleccionado arbitrariamente Especificar el flujo b sico est descrito con m s de talle mas Section 4 3 3 1 Especificando el Flujo Basico abajo Flujos Alternativos Unas series de secuencias lineales describiendo cada uno de los comportamientos alternativos al flujo b sico Especificar flujos alternativos est descrito con mas detalle en Sec tion 4 3 3 2 Especificando los Flujos Alternativos Post condiciones Ser a mejor llamarlas post asumciones Esta es una especificaci n de cualesquiera asumciones que podemos hacer al final del caso de uso
14. Actions To be written To be written 6 8 2 2 Transitions To be written To be written 6 8 2 2 1 Triggers To be written To be written 6 8 2 2 2 Guards To be written To be written 6 8 2 2 3 Effectss To be written To be written 6 8 2 3 Pseudo States To be written To be written 6 8 2 3 1 Junction and Choice To be written To be written 6 8 2 3 2 Fork and Join To be written To be written 6 8 2 4 Hierarchical State Machines To be written To be written 6 8 2 5 Models for State History To be written Shallow v Deep To be written 6 9 Creating Statechart Diagrams in ArgoUML To be written 6 9 1 Statechart Diagrams To be written To be written 6 9 2 States To be written To be written 6 9 3 Transitions To be written To be written 6 9 4 Actions To be written To be written 6 9 5 Advanced Statechart Diagrams To be written To be written 58 Design 6 9 5 1 Transitions To be written To be written 6 9 5 1 1 Triggers To be written To be written 6 9 5 1 2 Guards To be written To be written 6 9 5 1 3 Effectss To be written To be written 6 9 5 2 Pseudo States To be written To be written 6 9 5 2 1 Junction and Choice To be written To be written 6 9 5 2 2 Fork and Join To be written To be written 6 9 5 3 Hierarchical State Machin
15. Caution A stimulus should not generate any code so having this tab active is probably a mis take Constraints Standard tab ArgoUML only supports constraints on Classes and Features Attributes Operations Receptions and Methods so this tab is grayed out Tagged Values Standard tab In the UML metamodel Stimulus has the following standard tagged values defined 229 Sequence Diagram Artifact Reference e derived from the superclass ModelElement Values true meaning the stimulus is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived stimuli still have their value in analysis and design to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 19 3 2 Stimulus Property Toolbar Go up Navigate up through the package structure Delete This deletes the stimulus from the model Warning This is a deletion from the model not just the diagram To delete an stimulus from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 19 3 3 Property Fields For Stimulus Name Text box There is no convention for naming stimuli and it is quite normal to leave them unnamed The action is sufficient identification Tip
16. Experiencial and Tool The former cat egory Designer s contains the manually entered todo items 14 4 Item Count To the right of the flat hierarchical button is a count of the number of to do items currently found It will be highlighted in yellow when the number of to do items grows above 50 todo items and red when above 100 134 Chapter 15 The Critics 15 1 Introduction The key feature that distinguishes ArgoUML from other UML CASE tools is its use of concepts from cognitive psychology The theory behind this is well described in Jason Robbins PhD dissertation ht tp argouml tigris org docs robbins_dissertation http argouml tigris org docs robbins_dissertation Critics are one of the main ways in which these ideas are implemented Running in the background they offer advice to the designer which may be accepted or ignored A key point is that they do not impose a decision on the designer Note The critics are asynchronous processes that run in parallel with the main ArgoUML tool Changes typically take a second or two to propagate as the critics wake up 15 1 1 Terminology The critics are background processes which evaluate the current model according to various good design criteria There is one critic for every design criterion The output of a critic is a critique a statement about some aspect of the model that does not appear to follow good design practice Finally a critique will g
17. Figure Figure 6 4 Generalization between two Interfaces shows how your diagram should look now Figure 6 4 Generalization between two Interfaces By clicking on the subinterface and the source tab properties pane and then selecting Java Notation for the source tab you can see that the interface actually extends it s superinterface 6 5 3 2 Stereotypes To be written To be written 56 Design 6 6 Sequence and Collaboration Diagrams To be written Note Sequence diagrams does not work in ArgoUML version 0 14 To be written 6 6 1 More on the Sequence Diagram To be written To be written 6 6 2 The Collaboration Diagram To be written To be written 6 6 2 1 Messages To be written To be written 6 6 2 2 Actions To be written To be written 6 6 3 Advanced Collaboration Diagrams To be written To be written 6 7 Creating Collaboration Diagrams in ArgoUML To be written 6 7 1 Collaboration Diagrams To be written To be written 6 7 2 Messages To be written To be written 6 7 2 1 Actions To be written To be written 6 7 3 Advanced Collaboration Diagrams To be written To be written 6 8 Statechart Diagrams To be written To be written 6 8 1 The Statechart Diagram To be written More on this To be written 6 8 2 Advanced Statechart Diagrams To be written 57 Design To be written 6 8 2 1
18. Hierarchical Statechart Diagrams To be written To be written 5 7 Creating Statechart Diagrams in ArgoUML 5 7 1 Statechart Diagrams To be written To be written 5 7 1 1 Creating a Statechart Diagram Select a class then you can create a statechart diagram 5 7 2 States To be written To be written 50 5 7 2 1 5 7 3 5 7 4 5 7 5 5 7 5 1 Analysis Editing a Composite State When editing a composite state how do you provide do and event for a composite state The answer is to select a class then you can create a statechart diagram Transitions To be written To be written Actions To be written To be written Advanced Statechart Diagrams To be written To be written Hierarchical Statechart Diagrams To be written To be written 5 8 Realization Use Cases To be written To be written 5 9 Creating Realization Use Cases in Argo 5 10 5 10 1 UML To be written To be written Case Study To be written Regardless of which methodology you use at this time you are undoubtedly going to take the problem statement from Section 4 5 Case Study and extract the nouns from it This list should be compacted to contain only those nouns that are expected to result in a class This effort results in the following e Account e Audit trail e Bank e Cash Customer CRC Cards The project manager convenes a CRC session at which t
19. It is also possible to add associations using small handles that appear to the left and right of a use case or actor when it is selected and the mouse is over it Dragging the handle from a use case to an actor will create an association to that actor and similarly by dragging a handle from an actor to a use case Dragging a handle from a use case into empty space will create a new actor to go on the other end Sim ilarly dragging a handle from an actor into empty space will create a new use case It is possible to give an association a name describing the relationship of the actor to the use case al though this is not usually necessary This is done through the property tab of the association Such a name appears alongside the association near its center 4 4 3 1 Setting Navigation There are two ways of setting the navigation of an association 1 Use button 2 click on the association to bring up a context sensitive pop up menu The Navigab ility sub menu has options for bi directional navigation the default with no arrows and for nav igability Actor Use Case and Use Case Actor 2 Use button 1 to select the association and select its property tab in the details pane This shows a field named Association Ends with entries for each end labeled by the actor or use case name and its multiplicity Select the end that should be at the tail of the arrow with button 1 click This brings up the property tab for the association en
20. Note In this text area you may see the text lt oc1 gt self lt oc1 gt which will be replaced by the name of the artifact in question when the critic is triggered The last field is a drop down selector labeled Use Clarifier with three options Always If Only One and Never Clarifiers are the icons and wavy red underlines drawn on the actual diagrams to indicate the artefact to which the critic refers The original intention was to make the mapping from critics to clarifiers some what customizable For example one user might make a Missing Name critic show a red underline another user might turn off the clarifier or have it draw a wavy green underline or a blue questionmark Critics with their clarifier s disabled would still produce feedback that is listed in the to do pane Caution In the V0 20 release of ArgoUML this selector has no function whatsoever It is for future development Underneath the fields are three buttons in a horizontal row e Wake It is possible to snooze a critic from the to do pane see Chapter 14 The To Do Pane which makes the critic inactive for a period If the critic has been snoozed this button is enabled and will wake the critic back up again Otherwise it is grayed out Tip You can tell a snoozed critic because in the list on the left it will be indicated in the third column e Configure This button is for configuring the critic Caution In the VO 20 version of ArgoUML this functio
21. Stereotype for the selected include relationship navigating immediately to the properties tab for that stereotype Delete This deletes the selected include relationship from the model 185 Use Case Diagram Artifact Reference Warning This is a deletion from the model not just the diagram To delete a include from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 17 10 3 Property Fields For Include Name Text box The name of the include relationship Tip It is quite common to leave include relationships unnamed in use case analysis Note ArgoUML does not enforce any naming convention for include relationships Stereotype Drop down selector ArgoUML does not provide any stereotypes for include relationships Tip Stereotyping does not have great value on an include relationship Note There is no representation of the stereotype of an include relationship on the diagram Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the include This is the package hierarchy Button 1 click on the entry will navigate to the package defining this namespace or the model for the top level namespace Base Use Case Drop down selector Records the use case that is doing the including in this include relationship
22. The Editing Pane 12 1 Introduction Figure 12 1 Overview of the editing pane shows the ArgoUML window with the editing pane high lighted Figure 12 1 Overview of the editing pane This is where all the diagrams are drawn In earlier versions of ArgoUML this pane went under a variety of names You may encounter drawing pane diagram pane or multi editor pane in other docu mentation that is still being updated The pane has a tool bar at the top and a single tab labeled As Diagram at the bottom which has no function in the 0 20 version of ArgoUML The main area shows the currently selected diagram of which the name is shown in the window title bar 12 2 Mouse Behavior in the Editing Pane Behavior of the mouse in general and the naming of the buttons is covered in the chapter on the overall user interface see Chapter 8 Introduction 12 2 1 Button 1 Click In the tool bar of the editing pane button 1 click is used to select a tool for creating a new artifact and adding it to the diagram see double clicking for creating multiple artifacts For most tools adding a new artifact to the diagram is achieved by moving the mouse into the editing area and clicking again In the main editing area button 1 click is used to select an individual artifact Many artifacts e g actor class show special handles when selected and the mouse hovers over them These are called Selection Action Buttons see Sec
23. The dialog box is almost identical to that for Open Project see Figure 10 2 The file selection dia log for Open Project The extension of the filename is automatically set 10 3 5 Revert to Saved This menu item allows you to throw away all your recent changes and reload the last saved version of the current project It works a bit like an Undo feature but only restores changes done since the last time the file was saved This menu item is downlighted unless the currentproject has been saved or loaded before i e it has a name and it has been altered When this menu item is activated a small confirmation dialog box opens as shown in the figure below This warning that all recent changes will be discarded is needed because the action can not be undone Selecting No cancels the whole action as if you did not select the menu item in the first place Selecting Yes reloads the last saved file Figure 10 3 The warning dialog for Revert to Saved 74 The Menu bar 10 3 6 Import XMI This menu item allows to load an UML 1 3 or 1 4 model which was exported by e g another tool as a XMI file according the XMI V1 0 V1 1 or V1 2 standard The extension of such file should be xmi If the model has been altered as indicated by the in the titlebar of ArgoUML s window then activ ating the Import XMI function is potentionally not the user s intention since it will erase the changes Hence a confirmati
24. any hardcopy and CD ROM expression of an Open Publication licensed work to its author s F 6 License Options The author s and or publisher of an Open Publication licensed document may elect certain options by appending language to the reference to or copy of the license These options are considered part of the license instance and must be included with the license or its incorporation by reference in derived works A To prohibit distribution of substantively modified versions without the explicit permission of the au thor s Substantive modification is defined as a change to the semantic content of the document and excludes mere changes in format or typographical corrections To accomplish this add the phrase Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder to the license reference or copy B To prohibit any publication of this work or derivative works in whole or in part in standard paper book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder To accomplish this add the phrase Distribution of the work or derivative of the work in any standard paper book form is prohibited unless prior permission is obtained from the copyright holder to the li cense reference or copy 307 Open Publication License F 7 Open Publication Policy Appendix This is not consi
25. boolean and user defined enumeration types Note Also void is implemented as a datatype within ArgoUML Within ArgoUML new datatypes may be created using the New datatype button on the property tabs of the model and packages in which case the new datatype is restricted in scope to the package as well as the properties tab for datatype Note UML 1 3 allows user defined datatypes to be placed on class diagrams This is not permit ted in ArgoUML Datatype Details Tabs The details tabs that are active for datatypes are as follows ToDoltem Standard tab Properties See Section 16 3 2 Datatype Property Toolbar and Section 16 3 3 Property Fields For Data type below Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab Unused One would expect a class declaration for the new datatype to support code generation Tagged Values 156 Top Level Artifact Reference Standard tab In the UML metamodel Datatype has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed Tip Since user defined datatypes are enumerations they have no state to preserve and the value of this tagged value is irrelevant semantics from the superclass Classifier The value is a spec
26. n problemas ocasionalmente ArgoUML no leer archivos XMI files que contengan modelos UML 1 5 o UML 2 0 pero deber a ser capaz de abrir la mayor a de los archivos UML 1 4 y UML 1 3 Si encuentras uno que no puede abrir por favor informa del bug para que un desarrollador pueda investigar 3 4 3 3 6 Generando Formato XMI Selecciona el comando Exportar Archivo como XMI y escoge un nombre de archivo 3 4 3 4 Generaci n de C digo 3 4 3 4 1 C digo Generado por ArgoUML Es posible compilar tu c digo generado con ArgoUML si bien a n necesitas implementar los cuerpos de metodos para obtener resultados utiles 3 4 3 4 2 Generando C digo para M todos Hasta el momento no puedes escribir c digo para m todos operaciones dentro de ArgoUML El pan el de fuentes es editable pero los cambios son ignorados ArgoUML es una herramienta de dise 0 puro por ahora no hay funcionalidad IDE pero el deseo est ah Puedes considerar usar Forte y ArgoUML Puedes ayudarnos aqu si quisieras 3 4 4 Trabajando Con Criticas de Dise o0 3 4 4 1 Los Mensajes del Panel de Tar as Pendientes de las Critic as de dise 0 Donde estamos ahora Un nuevo proyecto ha sido creado y est conectado al archivo Primer Proyecto argo Figure 3 9 Ventana de ArgoUML Habiendo Guardado PrimerProyecto zargo muestra como tu ventana de ArgoUML deber a aparecer en est etapa Figure 3 9 Ventana de ArgoUML Habiendo Guardado PrimerProy
27. of Extend Relationship 184 Extension Point 39 175 of Extend Relationship 184 of Use Case 175 Extension Point Base Use Case 177 Extension Point Details Tabs 176 Extension Point Extending Use Cases 177 Extension Point Location 177 Extension Point Name 177 Extension Point Stereotype 177 External entity 169 F FAQ 2 File Menu 19 File Toolbar 20 Flujo Basico de Casos de Uso 36 del Caso de Uso 35 Flujos Alternativos de Casos de Uso 35 36 G Generalizaci n de Casos de Uso 34 Generalizar un Caso de Uso 34 Generalization 178 Generalization Child 181 Generalization Details Tabs 178 Generalization Discriminator 180 Generalization Name 180 Generalization Namespace 180 Generalization Parent 181 Generalization Powertype 181 Generalization Relationship 292 in a Use Case Diagram 41 Generalization Stereotype 180 Generalizations of Actor 172 of Package 191 of Use Case 175 Generate All Classes 93 Generating Code from Collaboration Diagrams 63 from Interactions 63 from Sequence Diagrams 63 from Statechart Diagrams 63 from the Static Structure 62 Generation Menu 20 GIF 13 GUI 293 H Help Menu 20 Hierarchical Statechart Diagram 293 Hierarchical Use Cases 41 Include Relationship 184 293 in a Use Case Diagram 41 of Use Case 175 Include Relationship Base 186 Include Relationship Details Tabs 185 Include Relationship Included Use Case 186 Include Relationship Nam
28. the name of a parameter has a leading lower case letter with words separated by bumpy caps Note The ArgoUML critics do not complain about parameter names that do not have an ini tial lower case letter Stereotype Drop down selector There are no UML standard stereotypes for Parameter Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype 205 Class Diagram Artifact Reference Owner Text box Records the operation which contains this parameter Button 1 double click on the entry will navigate to the operation Type Drop down selector The type of this parameter This can be any UML Classifier although in practice only Class DataType or Interface make any sense Note A type must be declared it can be void but this only makes sense for a return para meter By default ArgoUML supplies int as the type the first time a parameter is created and thereafter the type of the most recently created parameter Default Value Text box with drop down This allows you to set an initial value for the parameter if desired this is optional The drop down menu provides access to the common values 0 1 2 and null Caution This only makes sense for out or return parameters Kind Radio box with entries out in out return and in e out The parameter is used only to pass values back from the operation e in out
29. ture will be designed in house Close liaison must be maintained between the software development and the design development and production of the hardware Neither the hardware nor the software shall be considered the independent variable but rather they shall be considered equal 44 Captura de Requerimientos 4 5 1 7 Appendix 4 5 2 4 5 3 4 5 4 The following are the actors that directly support this vision Additional actors may be identified later that are needed to support this or that technology They should not be added to this list unless they are deemed to directly support the vision as described in this document e Central Computer Customer e Local Branch Official e Maintenance Engineer The following are the use cases that directly support this vision Additional use cases may be identified later that are needed to support this or that technology or to support the use cases listed here They should not be added to this list unless they are deemed to directly support the vision as described in this document e Audit e Customer Uses Machine e Maintain Machine Identifying Actors and Use Cases For the ATM case study we will elaborate on the examples in Section 4 3 Salida del Proceso de Cap tura de Requerimientos Figure 4 4 Diagrama de caso de uso para un sistema de Cajero Autom tico mostrando relaciones de inclusi n and Figure 4 5 Diagrama de casos de uso para un sistema de Ca jero
30. 0 0 0 cece eee enee ee eee een eees 54 6 1 3 Realization Class Diagrams To be written oocooccocnoconcnoconcnonononns 54 6 1 4 Sequence Diagrams and Collaboration Diagrams To be written 54 6 1 5 Statechart Diagrams and Activity Diagrams To be written 54 6 1 6 Deployment Diagram To be written coooccnccnnccnnccnncnnccnnccnnccnncnnno 54 6 1 7 Documents To be Written 00 0 0 ccc ccc ccc ec eee eee ee eeneceeeeeeeneaeeneneenens 54 6 2 Package Diagrams To be written coooccnoconoconccnnccnnccnnccnocnnccnnccnnccnnccnnions 54 6 2 1 The Package Diagram To be written ocooocccccccccnnccnccnnccnnccnnccnninns 54 6 2 2 Advanced Package Diagrams To be written ooocooccncccnccnnconnccnncono 54 6 3 Creating Package Diagrams in ArgoUML ooooccnccnnccnnccnccnnccnncnnncnnconnconncinns 54 6 3 1 Packages tensores 54 6 3 2 Relationships between packages To be written ooooocoocccnccnnccnncono 55 6 3 3 Advanced Package Features To be written ocooccoccoconcnoroncnorononns 55 6 4 More on Class Diagrams To be written oocooconcnoconcnnconcnnconcnnroncnoronannnos 55 6 4 1 The Class Diagram To be written oocooccoccoconcnoroncnnconcnoroncnarononns 55 ArgoUML Manual de Usuario 6 4 2 Advanced Class Diagrams To be written oo ooccoccncnoconcnoconcnononcnns 55 6 5 More on Class Diagrams in ArgoUML To be written 2 00 0 eee 55 6 5 1 Classes To be Written
31. 0 0 0 0 cece eee cece eeceeeceeeeeeeeeeeeneeenes 142 15 7 11 Add Choice Junction Transitions oocooccocnoconcnoconcnnconcnnconcnnnonos 142 15 7 12 Add Guard to Transition ocooccocnoconcnoconcnnroncnoroncnnroncnoroncnnnonos 142 15 7 13 Clean Up Diagram ci O Re 142 15 7 14 Make Edge More Visible ooocccoccnnconcconoconiconocnnccnnncnaronicnno 142 15 7 15 Composite Association End with Multiplicity gt 1 0 143 15 8 Design PattemMs sacs ss tsssesssposeduss neta oh setae E E E E EES 143 15 8 1 Consider using Singleton Pattern for lt class gt ooooccccccccccncccnncnnoo 143 15 8 2 Singleton Stereotype Violated in lt class gt 0 0 0 0 eee eeee eee ee ee 143 15 8 3 Nodes normally have no enclosers ooocoooconcconccnnccnnncnncnnnccnicnnns 144 15 8 4 NodeInstances normally have no enclosers ceeeeeeeeeeeee ee 144 15 8 5 Components normally are inside nodes cee ceee cece eee eeee ee ee 144 15 8 6 ComponentInstances normally are inside nodes ceeeeeee 144 15 8 7 Classes normally are inside components cee ceeeeee eee ee ee 144 15 8 8 Interfaces normally are inside components ceeeeeee eee eee 144 15 8 9 Objects normally are inside component cee ceee eee eee ee ee 144 15 8 10 LinkEnds have not the same locations oococcooccccnocccononocononocos 144 15 8 11 Set classifier Deployment Diagram cec
32. 2 Enumeration Property Toolbar cece cece cece eee ceeeeeeeee teen es 161 16 4 3 Property Fields For Enumeration oocoooccnnconncnnccnnccnnncnnnnnoroninnnos 162 16 5 Stereotype wis vcs sione sss te sedes dons danene Ea E PS E DETERE PRERE PESEE E PeR 163 16 5 1 Stereotype Details Tabs ooooconoccnnconnconoconcconconoconncnnacnnncnanonoso 164 16 5 2 Stereotype Property Toolbar oooconoccnnconcconccnnconoconcnnncnnncnnnonoso 164 xi ArgoUML Manual de Usuario 16 5 3 Property Fields For Stereotype ocoooccnoconoconoconoconocnnncnnccnaronicnnos 165 16 6 Diagta Mm 5 5 55 05 feo eeei thes ods couch r tae os bsaeehe aaa e wal ea beaten eeweheasnaee 166 16 6 1 Diagram Details Tabs oooooooccnnccnnconoconoconccnnconoconacnnncnnncnnnonoss 167 16 6 2 Diagram Property Toolbar ooooccnoccncconccnnccnncnnnconccnnncnnncnnnonoso 167 16 6 3 Property Fields For Diagram oooconoccncconiconccnnconnconncnnncnnncnanonoso 168 17 Use Case Diagram Artifact Reference oooccooccnnconoconoconncnnccnncnnncnnarnnocnnccnaronose 169 V7 Introd cti n os sic ccs TS 169 17 1 1 ArgoUML Limitations Concerning Use Case Diagrams 169 V2 2 A COR e shoe Rioes oS 52 ees EEEE E RERE ETE o sein naee cess save 169 17 2 1 Actor Details Tabs sirier sinri eie na eap bandas 169 17 2 2 Actor Property Toolbar voryen iia EEE E e ES 170 17 2 3 Property Fields For Actor ooocococcnoconoconoconccnnconnconcnnac
33. 2 5 1 Within Lists This behavior applies where there is a list of things that may be selected This includes various dialog boxes and the to do pane where there is a list of to do items to be selected Where selections are to be made the SHIFT key is used to with button to extend from the original but ton 1 selection to the current position Similarly the CTRL key with button 1 is used to add individual items to the current selection Where Ctrl button 1 is used on an item already selected that item is removed from the selection Caution Users of Microsoft Windows might be familiar with the use of SHIFT CTRL Click i e holding both the Shift and Ctrl key down when clicking to add sub lists to an existing se lection ArgoUML does not support this SHIFT CTRL Click will behave as CTRL Click 8 2 5 2 General Behavior When Editing Text 8 2 6 8 2 7 In a number of places in ArgoUML text may be directly edited for example when naming a mod el element in the properties pane or when typing a UML note comment Here SHIFT button 1 is used to select a range of text from the previously selected point Subsequent operations text entry and deletion will replace the selected text Alt with Button 1 Panning When holding down the Alt key during button 1 down on a diagram movement of the mouse pans the drawing area The function is indicated by the mousepointer which turns into a crosshair with arrows Ctrl with Button 1 Co
34. 291 Collaboration 292 Sequence 295 State 295 System Sequence 296 System State 296 Use Case 296 Diagram Details Tabs 167 Diagram Name 168 Diagram Property Fields 168 Diagrama Casos de Uso 31 Diagrama de Casos de Uso 31 Discriminator of Generalization 180 Dise o xvii 1 Documentation in Use Case Diagrams 42 Documento de Visi n 30 31 312 Index Documeto de Visi n 29 E Edit Menu 19 Edit Toolbar 20 Enumeration 160 Enumeration Details Tabs 161 Enumeration Literals 163 Enumeration Modifiers 162 Enumeration Name 162 Enumeration Properties 161 Enumeration Property Fields 162 Enumeration Property Toolbar 161 Enumeration Tagged Values 161 Enumeration Visibility 162 EPS 13 Escenario 35 Escenario de Casos de Uso 34 Escenarios Alternativos 36 Especializaci n de Casos de Uso 34 Especializaciones de Casos de Uso 34 Especificaci n de Casos de Uso 30 34 Especificaci n de Casos de Uso 30 34 Especificaci n de Requerimientos Suplementarios 30 30 Exit 80 Explorer 99 Mouse Behavior 99 Extend Relationship 181 292 in a Use Case Diagram 41 of Use Case 175 Extend Relationship Base Use Case 184 Extend Relationship Details Tabs 181 Extend Relationship Extension 184 Extend Relationship Extension Point 184 Extend Relationship Name 183 Extend Relationship Namespace 184 Extend Relationship Stereotype 183 Extending Use Cases of Extension Point 177 Extension
35. 3 Delete From Model encoccronions scious nieron arraie 81 10 4 4 Configure Perspectives cece cece ence eeceeeceeeea teen sean eeu eegs 81 10 45 Stun GS x mees eas igsyethiasas cote as pve roads tras pios 81 10 5 The View IA pocccssuets iso eeo E E E ESS 85 10 51 Goto Diagram tue aes heel AR ea asi Babess 85 10 5 2 Find aye taer e n E E E AEEA E E AE fte 86 105 3 ZOOM ein ir a E E E a id 87 10 5 4 Adjust Grd essa eneee sheeted e e e Ee E dar a 88 10 5 5 Adjust Grid Snap i nre r n scales leed E ate 88 10 5 6 Page Breaks siei eoroe reno nn E A SE E Epe eens 88 10 6 The Create Ment sso crno irna Seed oes Soest EEE EE S EE E 88 10 6 1 New Use Case Diagram copo canon corroe de orto oops na Es pias 89 10 6 2 New Class Diagram ooocccoccnnccnnconnconoconnconaconononcnnncnnconnconnccnncons 89 10 6 3 New Sequence Diagram oooccoccnnccnnconnconnccnnconccnnccnnccnnccnnconacinncos 89 10 6 4 New Collaboration Diagram oooconoconoconocnnccnncnnncnnncnnconnronncinncons 89 10 6 5 New Statechart Diagram oooooccnnccnnconnconccnnocnnocnncnnncnnconnconnccnncons 90 vii ArgoUML Manual de Usuario 10 6 6 New Activity Diagram eee cece ce ee ce eeeeeeea teen sone eene eens 90 10 6 7 New Deployment Diagram cece cece eee ceee ce eeee teen tenn eeneens 90 10 7 The Arrange Med avis oti yo Bilao aaa ee nN 90 LO Fed AMI BMS dit ata daa 90 10202 Distribute a ie 91 1013 Reorder aida torr
36. 4 5 Role name conflicts with member A suggestions that good design avoids role names for associations that clash with attributes or opera tions of the source class Roles may be realized in the code as attributes or operations causing code gen eration problems 15 4 6 Choose a Name Classes and Interfaces The class or interface concerned has been given no name it will appear in the model as anon Sugges tion that good design requires that all interfaces and classes are named 15 4 7 Choose a Unique Name for an Artifact Classes and Interfaces Suggestion that the class or interface specified has the same name as another in the namespace which is bad design and will prevent valid code generation 137 The Critics 15 4 8 Choose a Name Attributes The attribute concerned has been given no name it will appear in the model as anon Attribute Suggestion that good design requires that all attributes are named 15 4 9 Choose a Name Operations The operation concerned has been given no name it will appear in the model as anon Operation Suggestion that good design requires that all operations are named 15 4 10 Choose a Name States The state concerned has been given no name it will appear in the model as anon State Sugges tion that good design requires that all states are named 15 4 11 Choose a Unique Name for a State related Arti fact Suggestion that the state specified has the same
37. 46 Chapter 5 Analysis Analysis is the process of taking the customer requirements and re casting them in the language of and from the perspective of a putative solution We are not actually trying the flesh out the detailed solution at this stage That occurs in the Design Phase see Chapter 6 Design Unlike the boundary between Requirements and Analysis Phases the boundary between Analysis and Design Phases is inherently blurred The key is that analysis should define the solution no further than is necessary to specify the requirements in the language of the solution The artifacts in Analysis generally represent a high level of abstraction Once again the recursive and iterative nature of our process means we will come back to the Analysis phase many times in the future 5 1 The Analysis Process There are three schools of thought on how Analysis should be approached The ontologist defines the data actually the metadata first and worries about processes later The true ontologist would prefer not to have to think about processes at all The phenomenonologist reverses this and favors process over data The panparadigmist considers both process and data to be equally important and addresses both from the start When it comes to being a purist the ontologist has the upper hand It is possible to define and build a database into which data can be entered and retrieved without concern for what happens to it or is done wi
38. 6 Reduce Associations on lt artifact gt Suggestion that the given artifact actor use case class or interface has so many associations it may be a maintenance bottleneck The Wizard of this critic allows setting of the treshold i e the maximum number of associations al lowed before this critic fires Caution This number is not stored persistently and there is no way to reduce it after it has been set higher except by creating more associations until the critic fires again Restarting ArgoUML resets this number to its default 7 15 9 7 Make Edge More Visible This critic is discussed under an earlier design issues category see Section 15 7 14 Make Edge More Visible 146 The Critics 15 10 Instantiation Critics concerning instantiation of classifiers in ArgoUML The current version of ArgoUML has no critics in this category 15 11 Modularity Critics concerning modular development in ArgoUML The current version of ArgoUML has the following critics in this category 15 11 1 Classifier not in Namespace of its Association One of the well formedness rules in UML 1 4 for associations is that all the classifiers attached to the ends of the association should belong to the same namespace as the association If this were not the case there would be no naming by which each end could refer to all the others This critic is triggered when an association does not meet this criterion The solution
39. 7 Invocando Guardar Proyecto como Por favor date cuenta que el menu Archivo contiene las opciones usuales para crear un nuevo proyecto para abrir un proyecto existente para guardar un proyector bajo un nuevo nombre para imprimir del diagrama actualmente mostrado para guardar el diagrama mostrado actualmente como archivo y para salir del programa 22 OOA amp D basada en UML Algunos de estos commandos de men pueden ser invocados presionando combinaciones como se in dica en el men desplegable Por ejemplo manteniendo presionana la tecla Ctrl y presionando N crearas un nuevo proyecto En la versi n actual ArgoUML solo puede contener un proyecto activo al mismo tiempo Ademas un poryecto solo puede contener un modelo UML Puesto que un modelo UML puede contener un n mero ilimitado de elementos y diagramas esto no deber a presentar ninguna limitaci n seria incluso mod elando sistemas bastante grandes y complejos 3 4 2 8 3 El Di logo de Elecci n de Archivo Pero volvamos a guardar nuestro proyecto Despues de hacer click en el comando de men Guardar Proyecto como obtenemos el dialogo de elecci n de archivo para introducir el nomvre del archivo que deseamos usar como se muestra en Figure 3 8 Di logo de Elecci n de Archivo Figure 3 8 Di logo de Elecci n de Archivo Este es un FileChooser Java estandar Vayamos sobre ello con alg n detalle La caracteristica principal y dest
40. ArgoUML is that actions should be able to be invoked in whatever way the user finds convenient As a result many but not all actions that can be carried out on the menu can be carried out in other ways as well under ArgoUML A number of the common menu entries are also available through keyboard shortcuts It is also be possible to navigate the menu from the keyboard Each level of each menu is identified by a letter shown underlined in the menu or entry name from the moment the ALT key is pressed This se quence of letters while holding down the ALT key selects the entry The following is an explanation of why the menuitems are grouped as they are e The File menu contains operations that affect on the whole project file All the items in this menu can be explained as such e The Edit menu is generally intended for editing the model or changing the content of a diagram It also contains functions to enable editing like e g selecting This menu is not intended for diagram layout functions Most functions here do something with the selected modelelement and diagram The items Configure Perspectives and Settings are a bit different since they adjust the way ArgoUML works but they do not belong in the File menu since their settings are not stored in the project e The View menu is for functions that do never alter the model nor the diagram layout only the way you view the diagram A good example is zoom Also navigational fu
41. Attribute Compartment Only appears when the attribute compartment of a class or object is hidden Displays the compartment e Hide Operation Compartment Only appears when the operation compartment of a class or object is displayed Hides the compartment e Show Operation Compartment Only appears when the operation compartment of a class or object is hidden Displays the compartment e Hide Enumeration Literal Compartment Only appears when the enumeration literal compartment of an enumeration is displayed Hides the compartment e Show Enumeration Literal Compartment Only appears when the enumeration literal compartment of an enumeration is hidden Displays the compartment e Show All Edges Only appears on a class Displays all associations to shown artifacts that are not shown yet This is the same function as the add to Diagram on the asociation in the explorer context menu currently 117 The Editing Pane e Hide All Edges Only appears on a class Hides all associations This is the same function as Remove from Diagram on all the associations of this class e Hide Stereotype Only appears when the Stereotype of a package is displayed Hides the stereo type e Show Stereotype Only appears when the Stereotype of a package is hidden Displays the stereo type e Hide Visibility Only appears when the visibility of a package is displayed Hides the visibil ity e Show Visibilit
42. Autom tico mostrando una relaci n de extensi n and progress to identify additional actors and use cases that comprise our model of the ATM system Figure 4 4 Diagrama de caso de uso para un sistema de Cajero Autom tico mostrando relaciones de inclusi n and Figure 4 5 Diagrama de casos de uso para un sistema de Cajero Autom tico mostrando una relaci n de extensi n exempli fied the essential concepts and components of a use case diagram such as use cases actors multiplicity and include extend relationships They showed the relationships between the actors and use cases and demonstrated how these actors and use cases interact In Figure 4 4 Diagrama de caso de uso para un sistema de Cajero Autom tico mostrando relaciones de inclusi n we see a use case diagram for an ATM system consisting of include relationships for the use cases Maintain ATM and Use ATM Maintain ATM was further defined by two use cases Maintain Equipment and Reload ATM Use ATM was further defined in terms of the behavior of three simpler use cases Deposit Cash Withdraw Cash and Query Account More to be written Associations To be written To be written Advanced Diagram Features To be written To be written 4 5 5 Use Case Specifications To be written 45 Captura de Requerimientos To be written 4 5 6 Supplementary Requirements Specification To be written To be written
43. Built In Classes From java net These are the classes within the java net package e URL 24 3 4 Built In Classes From java util These are the classes within the java util package e Vector e Date e Time 24 4 Built In Interfaces These are some useful interfaces corresponding to classes defined within the standard Java environ ment Interfaces have many of the properties of classes like all types and you can change them if you wish All these can be found in the java util subpackage of the main model These are the interfaces defined within the java util package For their definition consult the Java language and library references e Collection e Iterator e List e Set e Sorted Set 24 5 Built In Stereotypes UML 1 4 defines a large number of stereotypes of which most are supported by ArgoUML Caution Not all stereotypes defined by UML 1 4 appear in ArgoUML V0 20 due to the fact that they were not yet updated from previous versions of ArgoUML that only supported UML 287 Built In DataTypes Classes Interfaces and Stereotypes 1 3 Also there are limitations in the current implementation of some base elements The table below lists all stereotypes defined in UML 1 4 and if they are supported in ArgoUML or not Caution The UML 1 4 standard also specifies many stereotypes in the chapters Example Profiles one for Software Development and one for Business Modeling Due to the sp
44. Button 1 click on this entry will give a drop down menu of all available use cases which may be se lected by button 1 click Included Use Case 186 Use Case Diagram Artifact Reference Drop down selector Records the use case that is being included by this include relationship But ton 1 click on this entry will give a drop down menu of all available use cases and an empty entry which may be selected by button 1 click 187 Chapter 18 Class Diagram Artifact Reference 18 1 Introduction This chapter describes each artifact that can be created within a class diagram Note that some sub artifacts of artifacts on the diagram may not actually themselves appear on the diagram Class diagrams are used for only one of the UML static structure diagrams the class diagram itself Ob ject diagrams are represented on the ArgoUML deployment diagram In addition ArgoUML uses the class diagram to show model structure through the use of packages There is a close relationship between this material and the Properties Tab of the Details Pane see Sec tion 13 3 Properties Tab That section covers Properties in general in this chapter they are linked to specific artifacts Figure 18 1 Possible artifacts on a class diagram shows a class diagram with all possible artifacts dis played Figure 18 1 Possible artifacts on a class diagram Figure 18 2 Possible artifacts on a package diagram shows a packag
45. Cuande se construlle un producto por contrato para un cliente el punto final esta bien definido Sin em bargo cuando se desarrolla un nuevo producto para el mercado una estrategia que puede se usada es de cidir la fecha de lanzamiento del producto y por tanto la fecha final para completar las labore de ingen ieria alg n tiempo antes El tiempo est entonces dividido en iteraciones y la cantidad del producto que puede ser construido en el tiempo desarrollado El processo iterativo es muy efectivo donde el timepo para la comercializaci n es mas importante que la funcionalidad exacta 3 2 1 3 Procesos de Desarrollo Recursivo 3 2 2 Muy pocos sistemas software est n concevidos como artefactos monoliticos Est n divididos en sub sistemas modulos etc Los procesos de Software son iguales con partes tempranas del proceso definiendo una estructura de alto nivel y reaplicando el proceso para partes de la estructura en turnos para definir cada vez mayores detalles Por ejemplo el dise o inicial de un sistema telefonico puede identificar objetos para i manejar las lin eas de telefono 11 procesar las llamadas 111 manejar el sistema y 1v facturar al cliente Los procesos de software pueden entonces ser reaplicados a cada uno de esos cuatro componentes para identificar su dise o OOA amp D con sus limites claros a los objetos soporta naturalmente este enfoque Esta clase de OOA amp D con desarrollo recursivo se abrevia a veces c
46. Datatype 189 197 201 205 Add Enumeration 154 Add Extend Relationship 182 Add Extension Point 174 176 Add Package 154 Add Qualifier 214 264 Add Stereotype 154 158 161 177 179 183 185 189 193 197 201 205 208 211 214 217 220 227 234 237 240 244 246 248 250 251 255 259 265 267 270 275 277 279 282 Add Use Case 173 Aggregation of Association End 216 Analisis 1 Analysis 7 11 291 Object Oriented 294 Arrange Menu 20 Association 209 291 in a Use Case Diagram 40 Association Class 291 Association Details Tabs 210 Association End 212 Association End Aggregation 216 Association End Changeability 216 Association End Details Tabs 213 Association End Modifiers 215 Association End Multiplicity 215 Association End Name 214 Association End Property Fields 214 Association End Property Toolbar 213 Association End Stereotype 214 Association End Tagged Values 213 Association End Type 214 Association End Visibility 216 Association Ends of Actor 172 of Association 212 Association Name 211 Association Property Fields 211 Association Property Toolbar 211 Association Stereotype 211 Association Tagged Values 210 Attribute 195 of a Class 291 of an Object 291 Attribute Changeability 199 Attribute Details Tabs 196 Attribute Initial Value 198 Attribute Multiplicity 198 Attribute Name 197 Attribute Property Fields 197 Attribute Property Toolbar 197 Attribute Tag
47. EPS GIF PGML PNG PS SVG e Encapsulated PostScript EPS http en wikipedia org wiki Encapsulated_PostScript es un archivo PostScript que satisface restricciones adicionales Estas restricciones estan previstas para hacer mas facil para el software incrustar un archivo EPS dentro de otro documento PostScript e Graphics Interchange Format GIF http en wikipedia org wiki GIF es un formato cubierto por patente aunque las patentes se agotaran en Agosto del 2006 Precision Graphics Markup Language PGML http en wikipedia org wiki PGML es un lenguaje basado en XML para representar graficos vectoriales Fu un borrador de la W3C pero no fu ad optado como recomendaci n PGML y VML otro lenguaje basado en XML para graficos vec toriales fueron luego fusionados y mejorados para crear juntos el formato SVG e Portable Network Graphics PNG http en wikipedia org wiki PNG es un estandar de ISO IEC 15948 2004 y es tambien una recomendaci n de la W3C PNG es un formato de imagen de mapa de bits que emplea compresi n de baja perdida PNG fu creado para mejorar y sustituir el formato GIF con un formato de archivos de imagen que no requiriera de una licencia de patense para ser usado PNG es oficialmente pronunciado ping pero a menudo es simplemente deletreado prob ablemente para evitar confusi n con la utilidad de red ping PNG est soportado por la librer a de referencia libpng una librer a independiente de la platafo
48. Environment Tab Tip 79 The Menu bar This is a text file which you can edit to configure ArgoUML 10 3 16 Most Recent Used Files ArgoUML remembers a few of the most recently saved files and lists them here to enable loading then in the most simple way The maximum number of files that is listed here can be adjusted in the Edit gt Settings menu The list of files is stored in the argo user properties file in the user s home directory 10 3 17 Exit Shortcut Alt F4 This closes down ArgoUML A warning message will pop up if you have a project open with unsaved changes asking if you wish to save it See Figure 10 11 The save changes dialog The options are Yes save the project and exit ArgoUML No do not save the project but still exit ArgoUML and Cancel do not save the project and do not exit ArgoUML The dialog box can also be closed by clicking in the close button in the window border The effect is the same as selecting Cancel Figure 10 11 The save changes dialog 10 4 The Edit Menu This menu provides support for selecting artifacts on the editing pane removal of artifacts from dia grams and the model and control of user settings 10 4 1 Select This sub menu provides for selection of items on the editing menu It has the following entries Select All shortcut Ctrl A Selects all artifacts on the current pane or in the current field The exact behaviour depend
49. For convenience when the mouse is over a selected class it dis plays two handles to left and right which may be clicked or dragged to form association relationships or composition in case SHIFT has been pressed and two handles top and bottom which may be dragged or clicked to form generalization and specialization relationships respectively e Association Add an association between two artifacts selected using button 1 motion from the first artifact to the second There are 2 types of association offered here bidirectional or uni directional Composition Add an composition between two artifacts selected using button 1 motion from the first artifact to the second There are 2 types of composition offered here bidirectional or unidirectional e Aggregation Add an aggregation between two artifacts selected using button 1 motion from the first artifact to the second There are 2 types of aggregation offered here bidirectional or unidirectional e Generalization Add a generalization between two artifacts selected using button 1 from the child to the parent e Interface Add an interface to the diagram For convenience when the mouse is over a selected interface it displays a handle at the bottom which may be dragged to form a realization relationship the target being the realizing class e Realization Add a realization between a class and an interface selected using button 1 motion from the realizing class to the realiz
50. Note Derived abstractions still have their value in analysis to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 18 16 2 Abstraction Property Toolbar Go up Navigate up through the package structure Delete This deletes the abstraction from the model Warning This is a deletion from the model not just the diagram To delete an abstraction from the diagram but keep it within the model use the main menu Remove From Dia gram or press the Delete key 18 16 3 Property Fields For Abstraction Name Text box The name of the abstraction There are no constraints on the name of an abstraction which is not shown on any diagram Stereotype Drop down selector Abstraction is provided by default with the UML standard stereotypes de rive realize refine and trace Caution ArgoUML automatically selects the stereotype realize when an abstraction is created The user is free to change the stereotype to use the abstraction to indicate for example a trace relationship However ArgoUML will not alter the representation on the dia gram accordingly Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec 223 Class Diagram Artifact Reference tion 16 5
51. Programming Systems Lan guages amp Applications conference in 1989 A tutorial on the subject can be found at ht tp www csc calpoly edu dbutler tutorials winter96 crc_b The CRC card methodology was originally designed as a teaching tool but has proved useful as a modeling tool as well The three parts of the CRC acronym were felt by the authors of the paper to represent the essential di mensions of object oriented modeling The term Responsibilities refers to the contract that the class un der discussion offers to the rest of the world Interface and Contract are similar concepts Responsibilit ies model the things that a class can do Services Methods or Operations will result from these The term Collaborators refers to the classes whose services the class under discussion will use Kent Beck tried unsuccessfully to use ther term Helpers instead of Collaborators to indicate classes that were sup porting the class under discussion It is widely believed that the terminology was chosen because CRC are the initials of Ward Cunningham s son Why use CRC cards They are portable No computers are required so they can be used anywhere Even away from the of fice They allow the participants to experience first hand how the system will work No computer tool can replace the interaction that happens by physically picking up the cards and playing the role of that ob ject They are a useful tool for teaching people the object oriented
52. The parameter is used both to pass values in and to pass results back out of the opera tion Note This is the default for any new parameter e return The parameter is a return result from the call Note There is nothing to stop you declaring more than one return parameter some pro gramming languages support this concept Tip The name of the return parameter does not appear on the diagram but it is conveni ent to give it an appropriate name such as the default return to identify it in the list of parameters on the operation property tab e in The parameter is used only to pass values in to the operation 206 Class Diagram Artifact Reference 18 9 Signal A signal is a specification of an asynchronous stimulus communicated between instances In the UML metamodel it is a sub class of Classifier Within ArgoUML signals are not fully handled Their value is when they are received as signal events driving the asynchronous behavior of state machines and when associated with send actions in state ma chines and messages for collaboration diagrams Tip In general there is limited value at present in defining signals within ArgoUML It may prove more useful to define signals as classes with a user defined stereotype of signal as suggested in the UML 1 4 standard This allows any dependency rela tionships between signals to be shown 18 9 1 Signal Details Tabs The details tabs that are active for sign
53. This creates a new Stereotype see Section 16 5 Stereotype within the same package as the data type navigating immediately to the properties tab for that stereotype Delete This deletes the datatype from the model 16 3 3 Property Fields For Datatype Name Text box The name of the datatype The primitive datatypes all have lower case names but there is no formal convention Note The default name supplied for a newly created datatype is the empty string Data types with empty string names will appear with the name anon Datatype in the explorer Stereotype Drop down selector Stereotype is provided by default with the UML standard stereotypes for clas sifier metaclass powertype process threadand utility Tip The stereotype enumeration should always be used for any created enumeration datatypes Caution In ArgoUML version 0 18 the stereotype enumeration must be created before it can be used However by creating an Enumeration Literal the stereotype enumera tion is created automatically Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Allows changeing the namespace for the datatype This is the package hier archy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that this datatype cannot be instantiated but must al
54. To be Written oooocoococccnccnoncnnoncnncnncnoncncnnconcnnncnnns 58 6 9 4 Actions To be Written 20 0 0 cece ce ceccec ee eec ee eeeceeeeeeeeeeneaeeeensaeenees 58 6 9 5 Advanced Statechart Diagrams To be written cooccoccnccoccncnononcnns 58 6 10 Activity Diagrams To be written ooocoooconocnnccnnccnnncnnconoconccnnccnnccnnccnnioos 59 6 10 1 The Activity Diagram To be written ooococcccnccnncnnccnnconnconnccnninns 59 6 11 Creating Activity Diagrams in ArgoUML To be written ee 59 6 11 1 Activity Diagrams To be written 2 0 0 cee cece eee eeeeeene eens 59 6 11 2 Action States To be Written ooocococoocnononncncnncnncnnncncnnconcnnncnnoos 59 6 12 Deployment Diagrams To be written 2 0 0 0 cece cece eee ee eeee eee een eens 60 6 12 1 The Deployment Diagram To be written 2 0 0 0 eee reece 60 6 13 Creating Deployment Diagrams in ArgoUML To be written 60 6 13 1 Nodes To be Written Wii iz 60 6 13 2 Components To be written ocooccoccnccoconcnoconcnoroncnoroncnnconcnarononns 60 6 13 3 Relationships between nodes and components To be written 60 6 14 System Architecture To be Written cooccoccocnncnoconcnoconcnnroncnnroncnoronononos 60 6 13 Case Study To Dewiitten eee E hen eoneteve tee den eri aves 60 6 15 1 CRC Cards To be written oooococcocncncnncncnncncnncnncnnncnnnncnncnoncnnns 60 6 15 2 Packages To be written oc
55. Values Standard tab In the UML metamodel Extend has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the extend relation ship is redundant it can be formally derived from other elements or false meaning it cannot Note Derived extend relationships could have their value in analysis to introduce useful names or concepts 17 9 2 Extend Property Toolbar Go up Navigate up through the package structure of the model For a extend this will be the package con taining the extend New extension point This creates a new use case extension point within the namespace of the current extend relationship with the current extend relationship as its first extending relationship Tip 182 Use Case Diagram Artifact Reference While it is perfectly valid to create extension points from an extend relationship the created extension point will have no associated use case it can subsequently be set up It would be more usual to instead create the extension point within a use case and sub sequently link to it from an extend relationship see Section 17 9 3 Property Fields For Extend below New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected extent relationship navigating immediately to the properties tab for that stereotype Delete This deletes the selected extend relationship from the model Warni
56. a e E a e a E dae NERE 42 4 4 6 Documentation sesana a n a r a E a 42 4 4 7 System Boundary BOX esecesece seen eccneeceecsneseeecneeenssens RS 43 4 3 Case Study cc ds 43 4031 Vision DOCU Meter roer rio prisa paladio 43 4 5 2 Identifying Actors and Use Cases ooocoocccnccnnccnnccnoconoconccnnconncinnccnno 45 4 5 3 Associations To be Written oooocoococccnccnoconncnncncnnoncncnnconcnnncnnnns 45 4 5 4 Advanced Diagram Features To be written oocooconcnoconcnoconcnnnonos 45 4 5 5 Use Case Specifications To be written ocooccoccncnoconcnoconcnnroncnanonos 45 4 5 6 Supplementary Requirements Specification To be written 46 A ee re cd eaee mabey 47 iv ArgoUML Manual de Usuario oul The Analysis Procesal tad Aenea deere ee 47 5 1 1 Class Responsibilities and Collaborators CRC Cards 0 06 47 5 1 2 Concept Diagram To be written oocoooccnccnncnnnccnnconccnnccnnccnnccnnions 48 5 1 3 System Sequence Diagram To be written 2 0 0 0 eee ee eeee ee 48 5 1 4 System Statechart Diagram To be written 2 2 0 0 eect ee eee 48 5 1 5 Realization Use Case Diagram To be written oocooccoccncnoconcnonononns 48 5 1 6 Documents To be Written 2 0 0 0 ccc ceccec ec ee cece cence sence ee eeneaesneaeeeens 48 3 2 Class Diagrams To be Written oo e simii spore conan nel Ra E PTE SEPARA 48 5 2 1 The Class Diagram To be written oocooccoccoconcnoco
57. action itself th e result of an operation of a class Shown as a solid line with a solid arrowhead to the time line of the object instance receiving the stimulus e Stimulus Create Generated by a create action fo r the class for which an instance is to be cre ated Shown as a solid line with a solid arrowhead to the object head of the object instance being cre ated e Stimulus Destroy Generated by a destroy action of the originating object Shown as a solid line with an open arrowhead terminating in a diagonal cross at the end of the time line of the receiving destroyed object instance e Stimulus Send Generated by a send action the result of a signal raised by an operation of the sending object instance and handled by the receiving object instance Shown as a solid line with half an open arrowhead e Stimulus Return Generated by an object instance that has received an earlier call stimulus and 1s returning a result to the calling object instance Shown as a dotted line with an open arrowhead Note ArgoUML does not allow you to create stimuli directly but instead provides tools to create stimuli of each of the five types above Caution In the current release of ArgoUML there is no way to show a terminate action where an object instance destroys itself One way is to draw a destroy action that loops back to the object itself give it an action with no name a nd use the style tab to set an invisible li
58. all pos sible artifacts displayed Figure 21 1 Possible artifacts on a collaboration diagram Limitations Concerning Collaboration Diagrams in ArgoUML 21 2 The collaboration diagram is still rather under developed in ArgoUML In particular there is no way to show instance collaborations based on objects and links rather than specification collaborations The biggest difficulties are with the messages There are problems with the sequencing of the messages and their display on the diagram The actions behind them are purely textual in implementation and there is no way to link them back to their associated operations or signals Classifier Role A classifier role is a specialization of a classifier used to show its behavior in a particular context In the UML metamodel Classifier Role is a sub class of Classifier Within a collaboration dia gram classifier roles may be used in one of two ways e To represent the classifier in a particular behavioral context the specification level or e to specify a particular instance of the classifier the instance level In this latter form classifier roles are identical to the instances used in sequence diagrams see Chapter 19 Sequence Diagram Artifact Reference and a collaboration diagram shows the same inform ation as the sequence diagram but in a different presentation 257 Collaboration Diagram Artifact Reference Caution A collaboration diagram should not mix c
59. all the operations see Section 18 7 Operation defined on this class Button 1 click navigates to the selected operation Button 2 gives a pop up menu with two entries which al low reordering the operations Move Up Only available where there are two or more operations listed and the operation selec ted is not at the top It moves the operation up one position e Move Down Only available where there are two or more operations listed and the operation se lected is not at the bottom It moves the operation down one position Owned Elements Text area A listing of artifacts contained within the classes namespace This is where any inner class see Section 18 5 2 Class Property Toolbar will appear Button 1 double click on any of the artifacts navigates to that artifact Tip Most namespace hierarchies should be managed through the package mechanism Namespace hierarchies through classes are best restricted to inner classes Conceivable datatypes signals and interfaces could also appear here but actors and use cases would seem of no value 18 6 Attribute Attribute is a named slot within a class or other Classifier describing a range of values that may 195 Class Diagram Artifact Reference be held by instances of the class In the UML metamodel it is a sub class of St ructuralFeature which is itself a sub class of Feature An attribute is represented in the diagram on a single line within the attribut
60. and details pane Button 1 click on the first of these will expand the editing pane to the full width of the window button 1 click on the second will expand the details pane to the full width of the window There is also a small downward pointing arrow within the horizontal divider bar at its leftmost end Clicking on this will expand the explorer and editing panes to the full depth of the window By using both the top arrow on the vertical divider and the arrow on the horizontal divider it is possible to expand the editing pane to use the entire window The original configuration can be restored by clicking again on these arrows which are now located at the edge of the window 8 4 The status bar The status bar is at the very bottom of the ArgoUML window and is used to display short advisory mes sages In general such messages are self explanatory It is e g used for displaying parsing error messages in case a text entered on the diagram can not be interpreted 69 Chapter 9 The Toolbar 9 1 File operations These buttons have identical functions as their counterparts in the File menu e New See for a full description Section 10 3 1 New e Open Project See for a full description Section 10 3 2 Open Project e Save Project See for a full description Section 10 3 3 Save Project e Print See for a full description Section 10 3 10 Print 9 2 Edit operations These buttons have id
61. and the relationship is many to many 15 17 4 Aggregate End Role in 3 way or More Associ ation Three way or more associations can not have aggregate ends roles This a well formedness rule of the UML 1 4 standard Aggregation and composition are used to indicate whole part relationships and by definition can only apply to binary associations between artifacts To fix this manually select the association and set the aggregation of each of its ends roles to none using the button 2 pop up menu or the property sheet 15 17 5 Wrap DataType This critic is discussed under an earlier design issues category see Section 15 3 1 Wrap DataType 151 Part 3 Model Reference Chapter 16 Top Level Artifact Reference 16 1 Introduction This chapter describes each artifact that can be created within ArgoUML The chapter covers top level general artifacts The following chapters see Chapter 17 Use Case Diagram Artifact Reference through Chapter 23 Deployment Diagram Artifact Reference cover each of the ArgoUML diagrams There is a close relationship between this material and the properties tab of the details pane see Sec tion 13 3 Properties Tab That section covers properties in general in this chapter they are linked to specific artifacts 16 2 The Model The model is the top level artifact within ArgoUML In the UML meta model it is a sub class of pack age In many respects within
62. area Lists the stimuli received by this object Classifier Drop down selector The name of the classifier of which this is an object Caution 227 Sequence Diagram Artifact Reference In the current release of ArgoUML the drop down selector will include all classifiers i e interfaces actors use cases and datatypes as well which is what is wanted on the diagram although it should properly be called an instance rather than an object In practice only instances of classes and actors make much sense Note In the current release of ArgoUML the same graphical presentation is used even if the object is actually representing an instance of an actor when a stick man would be more usual 19 3 Stimulus A stimulus is a communication between two instances and is generated by an action On a sequence dia gram a stimulus is associated with a link an instance of the UML metamodel Stimulus is a sub class of Model an association linking two object instances In Element The link see Section 19 9 Link associated with a stimulus is represented on a sequence diagram in ArgoUML as an arrow between the time lines of the object instances or the object head in the case of stimulus create described below labeled with the name of the action if any and the action separated by acolon The type of line and arrowhead depends on the type of action that generated the stimulus e Stimulus Call Generated by a call
63. by that object Computer Aided Software Engineering The encapsulation of the data associated with an artifact its attrib utes and the actions associated with the artifact its methods A class specifies the characteristics of an artifact An object repres ents an instance of the artifact Classes and objects in UML are represented on Activity Diagrams Class Diagrams Collaboration Diagrams and Sequence Diagrams A UML Diagram showing the structural relationship between classes See Section 5 2 Class Diagrams To be written for more information 291 Glossary Collaboration Collaboration Diagram Collaborator Comprehension and Problem Solving Concept Class Diagram Critic Extend Relationship Generalization Relationship The process whereby several objects cooperate to provide some higher level behavior that is greater than the sum of the behaviors of the objects A UML Diagram showing the dynamic behavior as messages are passed between objects Equivalent to a Sequence Diagram Which representation is appropriate depends on the problem under consid eration An object that participates in a Collaboration A design visualization theory within cognitive psychology The the ory notes that designers must bridge a gap between their mental model of the problem or situation and the formal model of a solution or system This theory suggests that programmers will benefit from 1 Multiple rep
64. can be hidden 18 15 1 Interface Details Tabs The details tabs that are active for interfaces are as follows ToDoltem Standard tab Properties See Section 18 15 2 Interface Property Toolbar and Section 18 15 3 Property Fields For Inter face below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The tick box Display Operations allows the operation compartment to be shown the default or hidden This is a setting valid for only the current diagram The Bounds field defines the bounding box for the package on the diagram Source Standard tab This contains a template for the interface declaration and declarations of associated in terfaces Tagged Values Standard tab In the UML metamodel Interface has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed Warning Since interfaces are by definition abstract they can have no instance and so this tagged value must refer to the properties of the realizing class e semantics from the superclass Classifier The value is a specification of the semantics of the interface e derived from the superclass ModelElement Values true meaning the interface is re dundant it can be formally derived from other element
65. case is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived use cases still have their value in analysis to introduce useful names or con cepts Checklist Standard tab for a Classifier 17 3 2 Use Case Property Toolbar Go up Navigate up through the package structure of the model New use case This creates a new use case within the model but not within the diagram and shows immediately the properties tab for that use case Tip 173 Use Case Diagram Artifact Reference This method of creating a new use case can be confusing It is much better to create a new use case on the diagram of your choice New extension point This creates a new use extension point within the namespace of the current use case with the cur rent use case as its associated use case navigating immediately to the properties tab for that exten sion point Delete This deletes the selected use case from the model Warning This is a deletion from the model not just the diagram To delete a use case from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 17 3 3 Property Fields For Use Case Name Text box The name of the use case Since a use case is a classifier it would be conventional to Capitalize the first letter and initial letters of any component words e g RemoteSensor The name is shown inside the oval representa
66. ceeeeeeeee teen teen es 259 21 3 Association Role 33 3 sks soecticees schon igs sedseeus robin iodo bededasassbiaagaseosacsss 261 21 3 1 Association Role Details Tabs oooocoooccnccnnoconccnnccnnncnoronoronicnnos 261 21 3 2 Association Role Property Toolbar 2 0 0 0 cece cece ceeeeeeeeeeeen ee 262 21 3 3 Property Fields For Association Role oooocococcnccnnccnncccnccnoccnicnnos 262 21 4 Association End Role ooooccocccnccnnconnconnconnconoconnconaconconncnnncnnncnnnnnnnnnoss 263 21 4 1 Association End Role Details Tabs 2 0 0 0 cece cece eee ee eeee ee 263 21 4 2 Association End Role Property Toolbar cece eeee eee eee 264 21 4 3 Property Fields For Association End Role 265 ZU Se Messa Be wes O 266 21 51 Message Details Tabs 3 0 sesc cs cc sch seen sedsiestesseaseeti esa caca apse beneas 266 21 5 2 Message Property Toolbar 0 0 0 0 eee c eee eeeceeeceeeee teen eeenes 267 21 5 3 Property Fields For Message ooocccoconoconcconccnnconoconconacnncnnnronose 267 22 Activity Diagram Artifact Reference coooconoccnccnnccnnccnnconoronccnnconnconnccnnconnconicos 269 22 1 Introduction cesa tipo tale ash a turis 269 xiv ArgoUML Manual de Usuario 22 1 1 Limitations Concerning Activity Diagrams in ArgoUML 269 222 ACUOM Stale rita tiroidea 269 22 2 1 Action State Details Tabs ooooooccnnccncconoconoconocnnncnnccnnccnaronicnnns 270 22 2 2 Action State Property To
67. changes Start the wizard by clicking the Next gt button 123 The Details Pane Figure 13 5 Example of a Wizard The wizard is driven through the first three buttons at the bottom of the ToDo Item tab e lt Back This will take you back to the previous step in the wizard Grayed out if this is the first step e Next gt This will take you back to the next step in the wizard Grayed out if this is the last step e Finish This will commit the changes you have made through the wizard in previous steps and or use the defaults for all next steps Note Not all to do items have wizards If there is no wizard all three buttons will remain grayed out The ArgoUML wizards are non modal i e once started you may select other todo items or do some other actions and all the while the wizard will remeber where it was so if you return to the todo item the wizard will indicate the same step it was on when you left it 13 2 2 The Help Button There is one remaining button at the bottom of the To Do Item tab labeled Help This will fire up a browser to a URL with further help Warning In the V0 20 release of ArgoUML the URLs are generally invalid The few that are valid have no information 13 3 Properties Tab Through this tab the properties of artifacts selected in the explorer or editing pane may be set The prop erties of an artifact may be displayed in one of the following ways 1 Selection of the artifact in th
68. criticos de dise o 3 El uso de listas de tareas pendientes to do lists para comunicar sugerencias desde los criticos de dise o al usuario ademas de permitir al usuario registrar areas para acciones futuras 12 3 3 2 OOA amp D basada en UML 4 El uso de listas de validaci n para guiar al usuario a traves de un proceso complejo Estandares Abiertos UML es en si mismo un estandar abierto ArgoUML sobre todo ha intentado usar estandares abiertos para todas sus interfaces La ventaja clave de la adherencia a los estandares abiertos es que ello permite un facil inter funcionamiento entre aplicaciones y la abilidad de moverse de una aplicaci n a otra como sea ne cesario 3 3 2 1 XML Metadata Interchange XMI XML Metadata Interchange XMI es el estandar para guardar los meta datos que confeccionan un mod elo UML particular En principio esto te permitir tomar el modelo que has creado en ArgoUML y im portarlo dentro de otra herramienta Esto claramente tiene ventajas in permitir al UML alcanzar su meta de ser un estandar para la comunic aci n entre dise adores La realidad no es tan buena Anteriormente a UML 2 0 el archivo XMI no incluye informaci n sobre la representaci n grafica de los modelos as que el dise o del diagrama est perdido ArgoUML rodea este problema guardando la informaci n grafica separada del modelo mira Section 3 4 3 1 Cargando y Guardando 3 3 2 2 Formatos Graficos
69. cubiertas en otro lugar e Descripciones de como ArgoUML funciona internamente e Como mejorar ArgoUML con nuevas caracteristicas y funciones e Una guia de soluci n de problemas e Un indice de referencia r pida para usar ArgoUML Estos est n cubiertos en the Developers Cookbook ht tp argoum stats tigris org documentation defaulthtml cookbook el FAQ ht tp argouml tigris org faqs users html y la Quick Guide ht tp argouml tigris org documentation defaulthtml quickguide 1 3 Visi n General del Manual de Usuario 1 3 1 Estructura del Manual Tutorial 1 3 2 Chapter 2 Introducci n escribiendose proporciona una visi n general de OOA amp D basada en UML incluyendo una guia para obtener ArgoUML instalado y funcionando Desde Chapter 4 Captura de Requerimientos hasta Chapter 7 Code Generation Reverse Engineering and Round Trip Engineering se introduce en cada parte de el dise 0 de procesos desde la captura de los requerimientos inicial hasta el desarrollo y construcci n del proyecto final Cuando cada concepto UML es encontrado su uso es explicado Su uso dentro de ArgoUML es descrito Finalmente un caso de estudio es usado para dar ejemplos de los conceptos en uso Estructura del Manual de Referencia Chapter 8 Introduction es una visi n general del interfaz de usuario y proporciona un resumen del so porte para los varios tipos de diagrama UML en ArgoUML Chapter 10 The Menu bar y Chapter 11 The Exp
70. delete an association from the diagram but keep it within the model use the main menu Remove From Dia gram or press the Delete key 18 11 4 Property Fields For Association Name Text box The name of the association By convention association names start with a lower case let ter with bumpy caps used to indicate words within the name thus salesHandling Note ArgoUML does not enforce any naming convention for associations Tip Although the design critics will advise otherwise it is perfectly normal not to name associations on a class diagram since the relationship is often obvious from the classes or class and interface name Stereotype Drop down selector Association is provided by default with the UML standard stereotype for Asso ciation implicit Stereotyping can be useful when creating associations in the problem domain requirements cap 211 Class Diagram Artifact Reference ture and solution domain analysis as well as for processes based on patterns The stereotype is shown between and below the name of the association on the diagram Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records and allows changing the namespace for the association This is the package hierarchy Connections Text area Lists the ends of this association An associat
71. design goal Unspecified with its slider set by default to priority 1 However it contains no critics and so has no effect 10 9 4 Browse Critics This menu entry brings up a dialog box controlling the individual critics see Figure 10 24 The dialog for Browse Critics Figure 10 24 The dialog for Browse Critics This dialog controls the behavior of individual critics To the left is a list of all the critics to enable them to be switched on or off individually For each critic there are three columns labeled Active Head line and Snoozed The first of these is a check box which may be toggled with button 1 click The second is the headline name of the critic the third indicates if the critic has been snoozed from the to do pane see Chapter 14 The To Do Pane A critic is only really active if the box in the first column is checked and the critic has not been snoozed Any critic for which the box in the first column is unchecked is inactive and will not trigger In addition any to do items associated with that critic will be removed from the to do pane The V0 20 version of ArgoUML has a total of 90 critics a few of which are incompletely implemented They are described in detail by design issue category in the chapter on critics see Chapter 15 The Crit ics To the right of the list are a series of fields titled Critic Details giving detailed control over indi vidual critics Selecting a critic in the list on t
72. elements shown on the new dia gram If a class is currently selected a sequence diagram and a collaboration will be created that repres ent the behaviour of that class This means that the created elements will be shown within the class in the explorer hierarchy under Package centric view and artifacts created on the diagram will be created within the namespace of the collaboration A sequence diagram may not only represent the behavior of a class but also of any other classifier such as interface use case etc It is also possible to make sequence diagrams for an operation 10 6 4 New Collaboration Diagram This menu entry creates a blank collaboration diagram and selects that diagram It also creates a Col laboration UML element which is a container for the elements shown on the new diagram If a package is selected when this menu item is activated the collaboration diagram will be created within a collaboration within that package This means that it will be shown within the collaboration within the package on the explorer hierarchy under Package centric view and artifacts created on the diagram will be created within the namespace of the collaboration within the package Tip This does not prevent artifacts from other namespaces packages appearing on the diagram 89 The Menu bar They can added from the explorer by dragging or by using Add to Diagram from the button 2 pop up menu 10 6 5 New Statechart Diagram Thi
73. find it useful to create this stereotype for yourself see Section 16 5 Stereotype Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 18 4 Stereotype Namespace Drop down selector Records and allows setting of the namespace for the class This is the package hierarchy Button 1 click on the entry will move the class to the selected namespace Modifiers Check box with entries Abstract Leaf Root and Active e Abstract is used to declare that this class cannot be instantiated but must always be sub classed The name of an abstract class is displayed in italics on the diagram Caution If a class has any abstract operations then it should be declared abstract ArgoUML will not enforce this e Leaf indicates that this class cannot be further subclassed while Root indicates it can have no superclass It is possible for a class to be both Abstract and Leaf since its static operations may still be referenced e Active indicates that this class exhibits dynamic behavior and is thus associated with a state or activity diagram Visibility Radio box with four entries public private protected and package Indicates whether the class is visible outside the namespace Client Dependencies Text area Lists the depending ends of the relationship i e the end that makes use of the other end Button 1 double click navigates to th
74. follows ToDoltem Standard tab Properties See Section 19 9 2 Link Property Toolbar and Section 19 9 3 Property Fields For Link below Documentation Standard tab Presentation Standard tab The values for the bounds of the link are downlighted since they are determined by the objects connected Source Standard tab but with no contents Caution A link should not generate any code so having this tab active is probably a mistake Tagged Values Standard tab In the UML metamodel Link has the following standard tagged values defined e persistence from the superclass Instance Showing the permanence of the state inform ation associated with the link Values transitory state is destroyed when the link is des troyed and persistent state is preserved when the link is destroyed e derived from the superclass ModelElement Values true meaning the link is redund ant it can be formally derived from other elements or false meaning it cannot 233 Sequence Diagram Artifact Reference Note Derived links still have their value in analysis and design to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for a Classifier 19 9 2 Link Property Toolbar Go up Navigate u
75. hide the visibility of a package The visibility is shown in UML notation as or Extension Points This checkbox allows to reveal or hide the extensions points compartment of a usecase Bounds This defines the corners of the bounding box for a 2D artifact It comprises four numbers separated by commas These four numbers are respectively i the X coordinate of the upper left corner of the box ii the Y coordinate of the upper left corner of the box iii the width of the box and iv the height of the box All units are pixels on the editing pane This field has no effect on 1D artifacts that link other artifacts associations generalizations etc since their position is constrained by their connectedness In this case the field is downlighted Fill This drop down selector specifies the fill color for 2D artifacts It is not present for line arti facts Selecting No Fill makes the artifact transparant Selecting Custom allows to create other colors then the ones listed It causes the color selector dialog box to appear see Figure 13 9 The Custom Fill Line Color dialog box Line This drop down selector specifies the line color for artifacts Selecting No Fill makes the artifact transparant Selecting Custom allows to create other colors then the ones listed It causes the color selector dialog box to appear see Figure 13 9 The Custom Fill Line Color dialog box Shadow This drop down selector specifies the wi
76. items on the drawings bigger 87 The Menu bar 10 5 4 Adjust Grid This cycles the grid representation on the screen through the following sequence 10 5 5 dots at 16 pixel spacing the default dots at 32 pixel spacing no grid of any form full grid at 16 pixel spacing and full grid at 8 pixel spacing Adjust Grid Snap This cycles the spacing of grid snapping through the following sequence 10 5 6 snap at 8 pixel spacing the default snap at 16 pixel spacing snap at 32 pixel spacing and snap at 4 pixel spacing Note There is no option to turn off snap to grid altogether Caution In the V0 22 version of ArgoUML this is not actually a true snap to grid It just defines the increments by which artifacts are moved around Thus if an item has an X coordinate of 4 and Grid Snap is set to 8 moving will take it to X coordinates of 12 20 28 etc not 8 16 24 etc If you wish to align on true grid snap boundaries you can use the Ar range gt Align To Grid menu see Section 10 7 1 Align Page Breaks This toggles whether page breaks are shown on the diagram as white dotted lines Warning This menu item does not work in ArgoUML VO0 22 10 6 The Create Menu 88 The Menu bar This menu provides for creating the various types of UML diagrams supported by ArgoUML 10 6 1 New Use Case Diagram This menu entry creates a blank use case diagram and selects that diagr
77. left quadrant of the user screen New use case diagrams can be created as needed through Create Diagram on the main menu bar or on the Create Diagram Toolbar They are edited in the editing pane the upper right quadrant of the user screen Actors To add an actor to the diagram use button 1 click on the actor icon on the editing pane toolbar and then button 1 click at the location where you wish to place it The actor can be moved subsequently by button 1 motion i e button 1 down over the actor to select it move to the new position and button 1 re lease to drop the actor in place Multiple actors can be added in one go by using button double click on the actor icon Each sub sequent button 1 click will drop an actor on the diagram A button 1 click on the select icon will stop adding actors The actors name is set in its property panel First select the actor if not already selected on the editing pane using button 1 click Then click on the Properties tab in the details pane The name is entered in the name field and will appear on the screen As a shortcut double button 1 click on the name of the actor in the editing pane or just typing on the keyboard when an actor is selected will allow the name to be edited directly This is a convenient way to enter a name for a new actor Having created the actor you will see it appear in the explorer the upper left quadrant of the user screen This shows all the artifacts cr
78. menu bar In this section we cover behavior that is general across all of ArgoUML In a number of places in ArgoUML text may be directly edited for example the constraint editor see Section 13 7 1 The Constraint Editor The behavior of the mouse when handling text is discussed in the sections that follow Mouse Button Terminology ArgoUML assumes a two button mouse We will refer to the buttons as button 1 and button 2 But ton is the leftmost button on a right handed mouse and sometimes referred to as the select button But ton 2 is the rightmost button on a right handed mouse and is sometimes referred to as the adjust button A single depress and release of a mouse button with the mouse is referred to as a click Two clicks in 66 Introduction quick succession is referred to as a double click Moving the mouse while holding a button down is re ferred to as button motion with the starting point being at button down and the end point at button up Button 1 Click Clicking on an user interface object or on a diagram artifact may establish many different things Most of the behaviour is experienced quite intuitive by the user mainly because the high degree of standard isation even spanning different computer platforms Macintosh PC UNIX ArgoUML follows the Java Look and Feel Design Guidelines by Sun See http java sun com products jlf Hence behaviour of common user interface components is g
79. name by which the source end of an association can reference the target end Note ArgoUML does not enforce any naming convention for association ends Stereotype Drop down selector Association end is provided by default with the UML standard stereotypes for AssociationEnd association global local parameter self Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Association Text box Records the parent association for this association end Button 1 double click on this entry will navigate to that association Type 214 Class Diagram Artifact Reference Drop down selector providing access to all standard UML types provided by ArgoUML and all new classes created within the current model This is the type of the entity attached to this end of the association Tip By default ArgoUML will select the class of the artifact to which the linkend is con nected However an association can be moved to another class by selecting another entry here Multiplicity Drop down menu with edit box The value can be chosen from the drop down box or a new one can be edited in the text box Records the multiplicity of this association end with respect to the other end i e how many instances of this end may be associated with an instance of the other end The multiplicity is shown on the diagram at that end of the associati
80. navigat ing immediately to the properties tab for that stereotype Delete from Model This deletes the pseudostate from the model Warning This is a deletion from the model not just the diagram 20 11 3 Property Fields For Pseudostate Name Text box The name of the pseudostate By convention pseudostate names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Tip Pseudostate names are not shown on the diagram and it is not usually necessary to give them a name Container Text box Shows the container of the pseudostate This is the state hierarchy Button 1 double click on the entry will navigate to the composite state that contains this state or the top level state that is the root of the state containment hierarchy Incoming Text area Lists any incoming transitions for the pseudostate Button 1 double click navigates to the selected transition Outgoing Text area Lists any outgoing transitions for the pseudostate Button 1 double click navigates to the selected transition 20 12 Initial State The initial state is a pseudostate see Section 20 11 Pseudostate representing a source for a single transition to the default state of a composite state It is the state from which any initial transition is made 250 Statechart Diagram Artifact Reference AS a consequence it is not permissible to have incoming tra
81. on the diagram is that of a stimulus associated with a send ac tion i e a solid line with half an open arrow head Note Because the current release of ArgoUML does not fully implement actions there is no en forcement of the relationship to a send action Stimulus Return 232 Sequence Diagram Artifact Reference This tool creates a stimulus associated with a return action on the diagram creating at the same time the associated link between sender and receiving instances All details tabs and properties are identical to to that of stimulus in general see Section 19 3 Stimulus Its graphical representation on the diagram is that of a stimulus associated with a return ac tion i e a dotted line with an open arrow head Note Because the current release of ArgoUML does not fully implement actions there is no en forcement of the relationship to a return action 19 9 Link A link is an instance of an association In the UML metamodel Link is a sub class of Instance Within a sequence diagram links are created indirectly when an associated stimulus is created An link is represented on a sequence diagram in ArgoUML as a line connecting the instances concerned However on a sequence diagram the representation is modified to reflect the type of action associated with the stimulus carried on the link see Section 19 3 Stimulus 19 9 1 Link Details Tabs The details tabs that are active for links are as
82. over an artifact will bring up a pop up menu with a variable num ber of main entries many with a sub menu 12 9 1 Critiques This sub menu gives list of all the critics that have triggered for this artifact Selection of a menu entry causes that entry to be highlighted in the to do pane and its detailed explanation to be placed in the To DoItem tab of the details pane A solid colored line indicates the offending element 12 9 2 Ordering This menu controls the ordering of overlapping artifacts on the diagram It is equivalent to the Re order sub menu of the Arrange menu see Section 10 7 3 Reorder There are four entries e Forward The selected artifacts are moved one step forward in the ordering hierarchy with respect to other artifacts they overlap e Backward The selected artifacts are moved one step back in the ordering hierarchy with respect to other artifacts they overlap e To Front The selected artifacts are moved to the front of any other artifacts they overlap e To Back The selected artifacts are moved to the back of any other artifacts they overlap 12 9 3 Add 116 The Editing Pane This sub menu only appears for artifacts that can have notes attached class interface object state pseudostate or have operations or attributes added class interface There are at most three entries e New Attribute Only appears where the selected artifact is a class Creates a new attribute on the artifact
83. paradigm They can be used as a methodology themselves or as a front end to a more formal methodology such as Booch Wirfs Brock Jacobson etc Although CRC cards were created for teaching they have proven useful for much more They have become an accepted method for analysis and design The biggest contributing factor to their success is the fact that they provide an informal and non threatening environment that is product ive to working and learning G 1 The Card The exact format of the card can be customized to the preferences of the group but the minimal required information is the name of the class it s subclasses and superclasses it s responsibilities and the collab orators for each of those responsibilities The back of the card can be used for a description of the class During the design phase attributes of the class can be recorded on the back as well One way to think of the card is that the front contains the public information and the back contains the encapsulated imple mentation details As a class is defined a card is made for that class with its name entered When a class is assigned to an individual that has only a class name on it the individual or the group selects an ini tial set of responsibilities for the class This initial set should be whatever if anything is immediately obvious 309 The CRC Card Methodology G 2 The Group Whether they are implicitly or explicitly defined the requirements fo
84. portion of the dialog box is an editable combo box labeled Output Directory to spe cify the directory in which code is generated Within this directory a top level directory will be created with the name of the model Further sub directories will be created to reflect the package namespace hierarchy of the model A drop down selector gives access to previously selected output directories Finally at the bottom of the dialog box are two buttons labeled Generate and Cancel Button 1 click on the former will cause the code to be generated button 1 click on the latter will cancel code gen eration 10 8 2 Generate All Classes Shortcut F7 This function behaves as Generate Selected Classes see Section 10 8 1 Generate Se lected Classes would with all classes in the current diagram selected 10 8 3 Generate Code for Project To be Written 10 8 4 Settings for Generate for Project To be Written 10 9 The Critique Menu This menu controls one of ArgoUML s unique features the use of critics to guide the designer The theory behind this is well described in Jason Robbins PhD dissertation ht tp argouml tigris org docs robbins_dissertation http argouml tigris org docs robbins_dissertation Note A word about terminology The critics are background processes which evaluate the cur rent model according to various good design criteria There is one critic for every design criterion The output o
85. propios planes en orden si no que esco gen pasos que son mentalmente menos caros entre las alternativas e Comprensi n y Resoluci n de Problemas Una teor a de visualizaci n de dise o dentro de la psicolog a cognitiva La teor a expone que los dise adores deben cubrir un hueco entre su modelo mental del problema o situaci n y el modelo formal de una soluci n o sistema Esta teor a sugiere que los programadores de beneficiaran de 1 Representaciones multiples como descomposici n sintactica del programa transiciones de estado flujo de control y flujo de datos Estos permiten al programador identificar mejor elementos y rela ciones en el problema y soluci n y por lo tanto mas facilmente crear un mapeo entre sus modelos de situaci n y modelos del funcionamiento del sistema 2 Aspectos familiares de un modelo de situaci n que mejoran las abilidades de los dise adores para formular soluciones 3 3 1 2 Aplicaci n Practica en ArgoUML ArgoUML implementa estas teor as usando un numero de tecnicas 1 El dise 0 de un interfaz de usuario que permite al usuario ver el dise 0 desde un numero de per spectivas diferentes y permite al usuario alcanzar objetivos a traves de un numero de rutas altern ativas 2 El uso de procesos ejecutandose en paralelo con la herramienta de dise 0 evaluando el dise o actu al contra modelos de como un dise o de la mejor practica puede funcionar Estos procesos son conocidos como
86. signal is not associated with the same operation as the original signal so this will have to be done afterwards New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected signal navigating immediately to the properties tab for that stereotype Delete This deletes the signal from the model Warning This is a deletion from the model 18 9 3 Property Fields For Signal Name Text box The name of the signal From their similarity to classes by convention the name of a sig nal has a leading upper case letter with words separated by bumpy caps Note The ArgoUML critics do not complain about signal names that do not have an initial upper case letter Stereotype Drop down selector Signal is provided by default with the UML standard stereotypes for its parent in the UML meta model Classifier metaclass powerType process thread and utility Navigate Stereotype 208 Class Diagram Artifact Reference icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records and allows changing the namespace for the signal This is the package hierarchy of the signal Contexts Text area Lists all the contexts defined for this signal Button 1 double click navigates to the selec ted context button 2 click brings up a pop up menu with one entry e Add Add a n
87. the more general end of the relationship Button 1 Double Click on this entry will navigate to that use case or actor But ton 2 click will give a pop up menu with a single entry Open which will also navigate to that use case or actor Child Text box Shows the use case or actor that is the child in this relationship i e the more specific end of the relationship Button 1 Double Click on this entry will navigate to that use case or actor But ton 2 click will give a pop up menu with a single entry Open which will also navigate to that use case or actor Powertype Drop down selector providing access to all standard UML types provided by ArgoUML and all new classes created within the current model This is the type of the child entity of the generalization Tip This can be ignored for use case analysis The only sensible value to put in would be the child use case type as a classifier this appears in the drop down list Figure 17 2 Example use of a discriminator with generalization 17 9 Extend Extend is a relationship between two use cases Where A extends B it means A describes more specific behavior and B the general version of that behavior In many respects extend is like generalization However the key difference is that the extended use case defines extension points see Section 17 4 Extension Point which are the only places where its beha vior may be extended The extending use case must define at which of t
88. their selected rules to the build in defaults of ArgoUML At the very bottom right is a button labeled OK to be used when all changes are complete button 1 click on this button will close the dialog window The changes are saved when you exit ArgoUML or inme diately by activating the menuitem File gt Save Configuration in the argo user properties file Then there is the Cancel button which cancels all changes made in the dialog Pressing the dialog close icon usually at the top right corner has the same effect as pressing the cancel button Context Sensitive Menu Button 2 Click over any selected artifact in the main area of the explorer will cause a pop up menu to appear Add to Diagram 102 The Explorer This entry on the pop up menu appears for any artifact that could be added to the diagram in the editing pane The item can be placed in a diagram by moving the cursor to the editing pane or a spawned editing pane window where it will appear as a cross and clicking button 1 Caution This menu entry only appears as not grayed out if the diagram in the editor pane allows to contain the artifact and the artifact is not present yet in the diagram ArgoUML will not let you place more than one copy of any particular artifact on a diagram 11 6 2 Delete From Model This entry on the pop up menu appears for any artifact that could be deleted from the model Warning This deletes the artifact from the model com
89. to the action and possibly stimulus associated with it In any case changes to this tab are ig 266 Collaboration Diagram Artifact Reference nored Tagged Values Standard tab In the UML metamodel Message has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the message is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived messages still have their value in analysis and design to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 21 5 2 Message Property Toolbar Go up Navigate up through the package structure New Action This creates a new Action see Section 20 3 Action for the selected object navigating immedi ately to the properties tab for that action New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected message navigating immediately to the properties tab for that stereotype Delete This deletes the message from the model Warning This is a deletion from the model not just the diagram To delete an message from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 21 5 3 P
90. una especificaci n suplementar ia de requerimientos Pasos del Proceso Los pasos en el proceso de captura de requerimientos pueden ser resumidos como sigue 1 Captura una vista general del problema y las caracteristicas deseadas de su soluci n en el docu mento de visi n 2 Identificar los casos de uso y actores desde el documento de visi n y mostrar sus relaciones en uno o mas diagramas de casos de uso 3 Da especificaciones de casos de uso detalladas para cada caso de uso cubriendo el comportamiento normal y alternativo precondiciones y postcondiciones 4 Captura todos los requerimientos no funcionales en una especificaci n de requerimientos suple mentarios En cualquier proceso de desarrollo iterativo priorizaremos y las iteraciones tempranas se enfocaran en capturar el comportamiento clave del los casos de uso mas importantes La mayor a de los procesos de captura de requerimientos modernos est n deacuerdo con que es esen cial que un representante autorizado del cliente est completamente involucrado a traves del proceso 4 3 Salida del Proceso de Captura de Requeri mientos 30 4 3 1 4 3 2 Captura de Requerimientos Casi todo el resultado del proceso de captura de requerimientos es documental El unico diagrama es el diagrama de casos de uso mostrando las relaciones entre casos de uso y actores Documento de Visi n Las secciones tipicas de este documento ser an como sigue e Resum
91. value Return values in UML are simply Parameters marked as return therefore everything here applies to them except where explicitly noted Warning Note that UML allows multiple return values This is possible to support in C as out parameters but currently the generator doesn t supports it This problem is being handled in issue 3553 handle multiple return parameters ht tp argoumL tigris org issues show_bug cgi id 3553 D 1 3 2 Parameter tagged values pointer true false default same as for Attributes reference ditto D 1 4 Preserved sections With each code generation special comments around the member function definitions will be generated like this function Testclass Testclass section 64 88 0 40 76f2e8 ec37965ae0 7fff begin 303 The C Module section 64 88 0 40 76f2e8 ec37 65bae0 7fff end All code you put within the begin and end lines will be preserved when you generate the code again Please do not change anything within these lines because the sections are recognized by this comment syntax As the curly braces are placed within the preserved area attribute initializers are preserved on constructors This also works if you change Method Names after the generation void newOperation std string test fddsaffa section 603522 ec4c7ff768 7ffc begin section 603522 ec4c7f f 768 7ffc end If you delete an Operation in the model The nex
92. web site and the developers mailing list e Report bugs This gives information about how to deal with bugs in ArgoUML It is important that all bugs are reported and all cooperation is appreciated e Legal A statement of the FreeBSD license which covers all the ArgoUML software Caution The various documentation of the project are not all covered by FreeBSD which is really meant for software In particular this manual is covered by the OpenPub license see Appendix F Open Publication License 98 Chapter 11 The Explorer The Explorer was previously called Navigation Pane Tree or sometimes Navigator Pane Tree 11 1 Introduction Figure 11 1 Overview of the explorer shows the ArgoUML window with the explorer highlighted Figure 11 1 Overview of the explorer The explorer allows the user to view the structure of the model from a number of predefined perspect ives It also allows the user to define their own perspetives for custom exploring of the model An important feature related to the cognitive psychology ideas behind ArgoUML is that not all artifacts are necessarily shown in all perspectives Rather the perspectives are used to implement hiding of unin teresting parts of the model 11 2 Mouse Behavior in the Explorer Behavior of the mouse in general and the naming of the buttons is covered in the chapter on the overall user interface see Chapter 8 Introduction 11 2 1 Button 1 Click Wit
93. which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 18 12 2 Association End Property Toolbar Go up Navigate up to the association to which this end belongs Go Opposite 213 Class Diagram Artifact Reference This navigates to the other end of the association New Qualifier This creates a new Qualifier for the selected association end navigating immediately to the proper ties tab for that qualifier Warning Qualifiers are only partly supported in ArgoUML V0 18 Hence activating this button creates a qualifier in the model which is not shown on the diagram Also the proper ties panel for a qualifier equals that of a regular attribute New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected association end nav igating immediately to the properties tab for that stereotype Delete This deletes the selected association end from the model Note This button is downlighted for binary associations since an association needs at least two ends Only for N ary associations this button is accessable and deletes just one end from the association 18 12 3 Property Fields For Association End Name Text box The name of the association end which provides a role name for this end of the associ ation This role name can be used for navigation and in an implementation context provides a
94. 0 8 1 Transition Details Tabs oooocoooccnnconoconiconocnnconoconoconoconoconinnoss 243 20 8 2 Transition Property Toolbar cece cece ce eeeeeeeeeeeeeeenees 243 20 8 3 Property Fields For Transition ocoooccnnconoconcconccnnncnnncnnronaronicnnns 244 20 9 EVEL neno eameds duos tebe de aunnes E E ny E a E ETE esate mene seater 245 20 9 1 2 Event Details Tabs snorre e eee stvbenves ad ieedetal shetty T 245 20 9 2 Event Property Toolbar ooooccnnccnnconnconcconconcnnncnnncnnacnnocnnccnose 246 20 9 3 Property Fields For Event oocoooccnnconcconiconocnncnnnconncnnncnnccnnnnnnss 246 ZO MONG AN 247 20 10 1 Guard Details Tabs oooocccoccnnccnnconoconoconoconconnconnconaconannnnonose 248 20 10 2 Guard Property Toolbar oocoooccnnconnconccnnocnncnnnconoconoconacnnrnnoss 248 20 10 3 Property Fields For Guard ooccooccnnconoconcconccnncnnncnnncnnaconocnnronoss 248 20 11 Pseudostate somos fecg send vshoted a REE E Solas di ess R Ra enla 249 20 11 1 Pseudostate Details Tabs oooocoooccnnccnioconoconoconoconccnnronoroninnnns 249 20 11 2 Pseudostate Property Toolbar ooocoooccncconoconcconocnnncnnconironicnnos 249 20 11 3 Property Fields For Pseudostate ooocoooconcconccnnccnnncnoronoconicnnns 250 20 12 Initial State il alii dnd pibe 250 20 13 Final State iia ista ESER 251 20 13 1 Final State Details Tabs ooooooccnoccnnconoconoconccnnncnnncnnronoroninnnos 251 20 13 2 Final State Propert
95. 1 double click navig ates to the association end AssociationRole Text box Records the parent association role for this association end role Button 1 double click navigates to the association role Type Drop down selector providing access to all standard UML types provided by ArgoUML and all new classes created within the current model This is the type of the entity attached to this end of the association role Multiplicity Editable drop down text entry Allows to alter the multiplicity of this association end role with re spect to the other end i e how many instances of this end may be associated with an instance of the other end The multiplicity is shown on the diagram at that end of the association role All remaining properties See Section 18 12 3 Property Fields For Association End Since these are completely equal to 265 Collaboration Diagram Artifact Reference the fields of an association end they are not repeated here 21 5 Message A message is a communication between two instances of an association role on a specification level col laboration diagram It describes an action which will generate the stimulus associated with the message On a collaboration diagram a message is associated with an association role In the UML metamodel Message is a sub class of ModelElement The message is represented on a collaboration diagram in ArgoUML by its sequence number separated by a colon from the expres
96. 13 3 Dialog box for New To Do Item which allows you to create your own to do item with its own headline which appears in the to do pane priority for the to do pane reference URL and detailed description for fur ther information Figure 13 3 Dialog box for New To Do Item e Resolve Item This pops up a dialog allowing the user to resolve the selected to do item see Figure 13 4 Dialog box for Resolve Item This is an important dialog because it allows you to deal with to do items in ways other than the recommendation of the to do item which is the whole 122 The Details Pane point of their being advisory This dialog box is intended to be used for the following reasons deleting todo items that were manu ally created preventing a single critic to trigger on a single object and dismissing categories of todo items by lowering design concerns or design goals Figure 13 4 Dialog box for Resolve Item At the top are three radio buttons of which by default the last is selected labeled 1 It is not relevant to my goals 2 It is not of concern at the moment and 3 Reason given below If you choose the third of these you should enter a reason in the main text box Tip If you wish to resolve a to do item that is generated by a critic by following its recom mendations just make the recommended changes and the to do item will disappear of its own accord There is no need to use this dialog Warning
97. 2 Advanced Package Diagrams To be written To be written 6 2 2 1 Subpackages To be written To be written 6 2 2 2 Adding DataTypes To be written To be written 6 2 2 3 Adding Stereotypes To be written To be written 6 3 Creating Package Diagrams in ArgoUML 6 3 1 Packages How to work out what goes in packages To be written 54 Design 6 3 1 1 Subpackages To be written To be written 6 3 2 Relationships between packages To be written To be written 6 3 2 1 Dependency To be written To be written 6 3 2 2 Generalization To be written To be written 6 3 2 3 Realization and Abstraction To be written To be written 6 3 3 Advanced Package Features To be written To be written 6 3 3 1 Creating New Datatypes To be written To be written 6 3 3 2 Creating New Stereotypes To be written To be written 6 4 More on Class Diagrams To be written To be written 6 4 1 The Class Diagram To be written To be written 6 4 1 1 Class Attributes To be written To be written 6 4 1 2 Class Operations To be written To be written 6 4 2 Advanced Class Diagrams To be written To be written 6 4 2 1 Realization and Abstraction To be written To be written 6 5 More on Class Diagrams in ArgoUML To be written 6 5 1 Classes To be written More on identifying classes from existing mate
98. 4 Composite State A composite state is a state that contains other states known as sub states allowing hierarchical state machines to be constructed A composite state is represented on a statechart diagram in ArgoUML as a large rectangle with rounded corners with a horizontal line separating the name at the top from the description of the behavior and the model of the sub state machine below The description of the behavior includes the entry exit and do actions and any internal transitions Sub states are placed within a composite machine by placing them entirely within the composite state This can be done at creation time i e when creating the state for the first time in the editing pane Al ternatively an existing state can be dragged onto a composite state The description of a composite state is almost identical to that of a state see Section 20 2 State and so is not duplicated here The only differences is one additional tool one missing field and one additional field which are described as follows New Concurrent Region Adds a new concurrent region to the selected composite state Deferrable Events This field is missing from V0 20 of ArgoUML Subvertices Text area Lists all the sub states contained within this composite state Button 1 double click navigates to the selected entry button 2 gives a pop up menu with two entries e New A submenu pops up with a selection of 7 kinds of states which can
99. 5 1231 Clean Up Diaframma nn eSsp E E IEEE KESS 147 15 13 AAA e E A E E aac ANEN 147 15 13 1 Change Names or Signatures in lt artifact gt 1 0 0 0 eee eee 148 15 13 2 Class Must be Abstract 2 0 0 0 cece eece cece neces ceeeeeeeeeeeeneeenes 148 15 13 3 Add Operations to lt class gt sisisi onnet iseis ai vesat rass 148 15 13 4 Reduce Operations on lt artifact gt oooccooccnnconoconiconicnnncnnncnanonoso 148 15 14 Code Generation lt 2 riri espero a eraa E rote poned perdera 148 15 14 1 Change Multiple Inheritance to interfaces coooccocccnccncccnccnnicnns 148 NN 148 15 16 Inheritance rociar oa au sade eas rta vb inci 148 15 16 1 Revise Attribute Names to Avoid Conflict o oooccoccccncnncnnnccnicnno 149 15 16 2 Remove lt class gt s Circular Inheritance ee cece eeee eee eee 149 15 16 3 Class Must be Abstract meniduri nisen iet ei 149 15 16 4 Remove final keyword or remove subclasses 0eeeeeeee ee 149 15 16 5 Ilegal Generalization 2 0 0 0 cece eee eece ence eeceeeeeeeeeeeeneeeaes 149 15 16 6 Remove Unneeded Realizes from lt class gt ce ceeeeeee eee eee 149 15 16 7 Define Concrete Sub ClasS 0 0 ccc ee cecece eee ceeeeneeeseeneeeeneaes 149 15 16 8 Define Class to Implement lt interface gt coe eeee eee eee 149 15 16 9 Change Multiple Inheritance to interfaces eee eee 150 15 16 10 Make Edge More Visible ooooccncccnnconoconicono
100. 50 5 7 Creating Statechart Diagrams in ArgoUML eee eee een teen eee eeene eens 50 5 7 1 Statechart Diagrams To be Written ocooccoccoconcnoconcnnconcnoroncnoronanos 50 5 7 2 States To be written eresie oieee nos EE EE EEE EEES EEE EE EEES 50 5 7 3 Transitions To be written oooocoococococcnonccncncnncnocnnncncnncnnnnnncnnns 51 5 7 4 Actions To be written oooococoococnccncnccnonnnncncnnoncncnncnncnnncnncnnnnnnoos 51 5 7 5 Advanced Statechart Diagrams To be written o ooccoccoccoconcnocononos 51 5 8 Realization Use Cases To be written ooooococococcocconncnonncononcncnnconcnnncnnns 51 5 9 Creating Realization Use Cases in ArgoUML To be written 1 0 0 0 51 3 10 Case Study To De written icccc vies ion contenta nata decada Rides de 51 SAO ERE Cards ti Dio 51 5 10 2 Concept Class Diagrams To be written ooocooccccccnccnnccnnccnnccnninns 52 5 10 3 System Sequence Diagrams To be written ooocooccncccnccnnconnccnncons 52 5 10 4 System Statechart Diagrams To be written oooooccocccnccnnccnnccnninns 52 5 10 5 Realization Use Cases To be written oooooococnccnoconncncnnconcnoncnnns 52 Oz DESISD aces eases E E vons ad S E EE E ae iGal semeagsscaatenesss 53 6 1 The Design Process To be Written 20 0 0 cece cece eeceeenece cesta eeeeceeeneeaeeneees 53 6 1 1 Class Responsibilities and Collaborators CRC Cards 0 06 53 6 1 2 Package Diagram To be written 0
101. Action Uninterpreted Action e Delete From Model Delete the Entry Action Incoming Text area Lists any incoming transitions for the final state Button 1 double click navigates to the selected transition Internal Transitions Text area Lists all the internal transitions of the state Such transitions neither exit nor enter the state so they do not cause a state change Which means that the Entry and Exit actions are not in voked 252 Statechart Diagram Artifact Reference Button 1 double click navigates to the selected transition 20 14 Junction Junction is a pseudostate see Section 20 11 Pseudostate which is used to split an incoming transition into multiple outgoing transition segments with different guard conditions A Junction is also called a Merge or Static conditional branch The chosen transition is that whose guard is true at the time of the transition A predefined guard denoted else may be defined for at most one outgoing transition This transition is enabled if all the guards labeling the other transitions are false According the UML standard its symbol is a small black circle Alternatively it may be represented by a diamond shape in case of Decision for Activity diagrams ArgoUML only represents a junction on the diagram as a solid white by default diamond and does not support the black circle symbol for a junction 20 15 Choice Choice is a pseudostate see Section 20 11 Pseu
102. ArgoUML Manual de Usuario Tutorial y descripci n de referencia Alejandro Ramirez Philippe Vanpeperstraete Andreas Rueckert Kunle Odutola Jeremy Bennett Linus Tolke Michiel van der Wulp ArgoUML Manual de Usuario Tutorial y descripci n de ref erencia by Alejandro Ramirez Philippe Vanpeperstraete Andreas Rueckert Kunle Odutola Jeremy Bennett Linus Tolke and Michiel van der Wulp Copyright 2004 2005 2006 Michiel van der Wulp Copyright 2003 Linus Tolke Copyright 2001 2002 Jeremy Bennett Copyright 2001 Kunle Odutola Copyright 2000 Philippe Vanpeperstraete Copyright 2000 Alejandro Ramirez Copyright 2000 Andreas Rueckert Abstract Esta version de el manual est planeado para describir la versi n argo core version de ArgoUML Este material puede ser distribuido solo sujeto a los terminos y condiciones establecidos en la Open Publication License v1 0 o posterior Una copia de esta licencia est incluida en la secci n Open Publication License La ltima versi n est actualmente disponible en http www opencontent org openpub http www opencontent org openpub WN PREPACIO A A AS dano xvii AI ON 1 1 1 Origenes y Visi n General de ArgoUML oocccccnnccnccnnccnnconnconccnnconnccnnccnncnnnccnncos 1 1 1 1 Analisis Orientado a Objeto y Dise O ooooccnnconccnnccnnconeconicnnncnnacnnccnanonoso 1 1 1 2 El Desarrollo de ArgoUML sii cccsc c0 nist ssssese sss sebbaagsseosse
103. ArgoUML it behaves similarly to a package see Section 18 2 Package Note ArgoUML is restricted to one model within the tool Standard data types classes and packages are loaded the default see Chapter 24 Built In DataTypes Classes Interfaces and Stereotypes as sub packages of the model These sub packages are not initially present in the model but are added to the model when used 16 2 1 Model Details Tabs The details tabs that are active for the model are as follows ToDoltem Standard tab Properties See Section 16 2 2 Model Property Toolbar and Section 16 2 3 Property Fields For The Model below Documentation Standard tab See Section 13 4 Documentation Tab Stereotype Standard tab This contains a a list of the stereotypes applied to this model and a list of available stereotypes that may be applied to the model Tagged Values Standard tab In the UML meta model Mode1 has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the class is redundant it can be formally derived from other elements or false meaning it cannot 153 Top Level Artifact Reference Derived models have their value in analysis to introduce useful names or concepts and in design to avoid re computation 16 2 2 Model Property Toolbar Go up Navigate up through the composition structure of the model Since the model is the top p
104. Association Classes 210 18 11 2 Association Details Tabs 1 0 0 0 cece eee cee ce ee ceeeceeeeeeeea teenies 210 18 11 3 Association Property Toolbar ooocoooccnncnnoconccnnccnnncnnccnnronicnnos 211 18 11 4 Property Fields For Association oocoooconcconocnnccnnocnnncnnncnaronicnno 211 18 12 Association End avui nd dyn anes ins EE A EESE SE 212 18 12 1 Association End Details Tabs oooooccnocnncconoconccnnccnnccnnccnncnnos 213 18 12 2 Association End Property Toolbar ooocoooccnoconoconccnnccnnccnnccnoso 213 18 12 3 Property Fields For Association End ooocococcnccnnccnnccnnccnncnnncnnos 214 18 13 Dependency se moni miens acd ie seas bat bosses es orto E nte nitro has R settee 216 18 13 1 Dependency Details Tabs ooocoooccnnconicconcccnconoconocnnacnnccnaronoso 216 18 13 2 Dependency Property Toolbar 0 0 0 0 cece cece eee ceeeeeeeee eee 217 18 13 3 Property Fields For Dependency ocoooccncccnncnnconoconncnnncnnnonononose 217 18 14 Generalization coccion ratas nitro nestbevsnceseues E E e E Ae 218 18 Interface io 218 18 15 1 Interface Details Tabs ooooconoccnnconoconoconoconconoconccnnncnnnonanonono 219 18 15 2 Interface Property Toolbar ocoooccnoconoconccnnconoconccnnncnononononoso 220 18 15 3 Property Fields For Interface ooocccoccncconcconcconocnnccnnccnnccninnnos 220 18 16 ADStACuOW escroto tn pies a sino ts dci 222 18 16 1 Abstraction Details Tabs ooooocccnccnncon
105. Click oocoococcnonncononncononocononocononocononocononoconos 99 1 123 B tton Moun oidor ranita rial 99 11 2 4 Button 2 Actions esner aa ei esaa eeraa Teei 100 11 2 5 Button 2 Double Chek repre nde E E a 100 11 3 Keyboard Behavior in the Explorer oooccnnccnnconoconcconccnnocnnocnncnnnrcnicnno 100 11 4 Perspective Selections smiir psies ss betes geasdeacgsedoeasashoteraseteaeass 100 11 37 Contiguring Perspectives sern e o EEE EE EENE SEES 101 11 5 1 The Configure Perspectives dialog cece eee cece tees eeeeeeen es 101 11 6 Context Sensitive Menu osiers o yeee Ei EE E EAS 102 11 6 1 Add to Diari secs e EA E ERNS 102 116 2 Delete From Model reia erae NAE EESE 103 11 6 3 Set Source Path To be written oooocoococccnocncccnncncnncnncnnncnnons 103 L164 Add Package creses neins eson ia a Erer totes gases saaiasboieagssteaabass 103 11 6 5 Add All Classes in Namespace occooccnnconnconnconncnnccnnncnnccnaronicnnos 103 12 The Editing Pane spreen eienenn e ie E a tones EE ENE TEE ES 104 12 1 Introduction ee AEE e E E EA EEEE EEAS 104 12 2 Mouse Behavior in the Editing Pane 0 ee cece cee ce eeeeeeen teenies 104 12 2 1 Button 1 Clk ccoo icon cecesssenel aE S EEE 104 12 2 2 Button 1 Double Click oooococcnoccccnocccononocononoconococononoconanonos 104 12 2 3 Button 1 MOON recocido Vis setae settee 105 12 2 4 Shift and Ctrl modifiers with Button 1 o ooooccoocnoccnocnnncnnccnnnnnn
106. Enumeration can be thought of as simple classes They have no attributes and any operations on them must have no side effects A useful analogy is primitive datatypes in a language like Java The boolean true stands on its own it has no inner structure There are operations for example logical xor on the booleans but when I perform true xor true the result is a booleans true are unchanged by the exercise Within UML 1 4 Enumeration is a sub class of the DataType met The big difference with other DataTypes is that an Enumeration has the Enumeration boolean is defined as having 2 EnumerationLiterals Within ArgoUML new enumerations may be created using the New new boolean and the original 2 aclass EnumerationLiterals E g true and false Enumeration button on the property tabs of the model and packages in which case the new enumeration is restricted in scope to the package as well as the properties tab for datatype and enumeration Note UML 1 4 allows user defined datatypes to be placed on class diagrams This is not yet pos sible in ArgoUML 160 Top Level Artifact Reference 16 4 1 Enumeration Details Tabs The details tabs that are active for enumerations are as follows ToDoltem Standard tab Properties See Section 16 4 2 Enumeration Property Toolbar and Section 16 4 3 Property Fields For Enu meration below Documentation Stan
107. Facility MOF incluyendo UML El Object Constraint Language es un lenguaje de texto preciso que proporciona limitaci n y expresiones de acceso a objeto en cualquier modelo MOF o metamodelo que de otra forma no puede ser expresado por notaci n diagramatical 100 Java Puro Java fu concevido como un lenguaje interpretado No ten a un compilador para producir codigo para cuaquier maquina particular Compila codigo para su propio sistema la Maquina Virtual Java Java Vir tual Machine JVM Escribir un interprete para una JVM es mucho mas facil que escribir un compilador y estas maquinas virtuales est n ahora incorporadas dentro de casi todo Navegador Web Como resultado la mayoria de las maquinas pueden ejecutar Java sin trabajo adicional En caso de que te preguntes porque todos los lenguajes no son como este es por que los lenguajes inter pretados tienden a ser mas lentos que los compilados Sin embargo con el alto rendimiento de los mod ernos PCs la ganancia en portabilidad merece la pena para muchas aplicaciones Mas a n las mod ernas caches multinivel pueden suponer que los lenguajes interpretados que producen un codigo mas denso pueden realmente no ser tan lentas de todas formas Mediante la elecci n de escribir ArgoUML en Java puro se hace inmediatamete disponible para el mayor numero de usuarios con la minima cantidad de esfuerzo Codigo Abierto ArgoUML es un proyecto de c digo abierto Esto significa que cualqu
108. For Extend 20 0 0 cece ceceeece ence eeeeeeeeeeenees 183 17 10 INC es i torso 184 17 10 1 Include Details Tabs oooooccnnccnnccnnconiconccnnconoconncnnacnnncnnnonoss 185 17 10 2 Include Property Toolbar ooocccoccnoconoconccnnconoconocnnacnnacnncnnoss 185 17 10 3 Property Fields For Include oooccccccnccnncccnncnnncnnnnnnccnronicnnos 186 18 Class Diagram Artifact Reference ocoooccnnccnnconnconoconeconconacononnncnnncnnncnnncnnronass 188 18 1 Introduction ceesorcrto erat seep soapee pe sueges py ute dus areas iptables Ran 188 18 1 1 Limitations Concerning Class Diagrams in ArgoUML 188 18 2 Packa fE lo anota eedawns sous bak done ddan crue aan tee estes 188 18 2 1 Package Details Tabs hos ieee o r E E a 189 18 2 2 Package Property Toolbar oocococcnnccnnconoconoconoconoconccnnccnnronicnno 189 18 2 3 Property Fields For Package oocoooccncconccnnccnnconoconncnnncnnncnanonoso 190 18232 Datatype serr i en ene oa pes sae oanshag E e E E E E vena gate ass 191 ES srr erai e EES EEEE ER E EE IKEE EEES 191 185 A E EE E AE E savean alge sot a dd se deaewa sreseagaseasaean 191 18 5 1 Class Details Tabs me 205 ocesscscessseays seein e reee EEEE RT 191 18 5 2 Class Property Toolbar csin aee n E E E E E 192 18 5 3 Property Fields For Class ooocoooccnnconoconoconoconconnconncnnacnnacnnncnoro 193 18 6 Atiri ULC ese eea Ean LN is ia eae 195 18 6 1 Attribute Details Tabs rnern eiei eese
109. I E ee EEn 196 18 6 2 Attribute Property Toolbar ooooccnoccncconcconccnnconoconcnnaccnacnnncnnss 197 18 6 3 Property Fields For Attribute oooocccoccnnconcconcconoconccnnccnnrcnncnnns 197 18 7 Operation sci e o Sots see E NEE EE ES a OEI AEE EES 199 18 7 1 Operation Details Tabs 1 0 0 0 eee cee zesse sestiers tists 200 18 7 2 Operation Property Toolbar oooccnoccnoconocnnccnnconoconcnnacnnacnnccnoso 200 18 7 3 Property Fields For Operation ocoooconoconccnnccnnconoconncnnncnnncnnnonoso 201 18 8 Parameters ralla O E 204 18 8 1 Parameter Details Tabs ooooocococcnnconnconoconocnnconoconocnnacnnccnnnonoro 204 xii ArgoUML Manual de Usuario 18 8 2 Parameter Property Toolbar ooocoooccnnconccnnccnnconoconccnnaccnacnnccnnso 205 18 8 3 Property Fields For Parameter 2 0 0 0 0 ceceeeeceeeceeece teen eeen nena es 205 RAS o FI cist wo eeke wet Gees Sis Ma oats Sse cee So aaa ne dae 207 18 9 1 Stenal Details Tabs 5 osenes eyestass Tratan ds Seabees var seseees 207 18 9 2 Signal Property Toolbar 2 0 0 0 eee cece cence ence eeceeeeeeeeneeenes 208 18 9 3 Property Fields For Signal ooooconoccnoconoconncnnconoconicnnocnnacnnnnnoss 208 18 10 Reception to be Written ocooccoccoccncnoconcnoconcnnroncnnconcnoroncnnconcnnronnns 209 LBV s ASSOCIATION icici pss 2555 a5 sees ages deaadpapets ce sbeseaics Shots ae ssedeangsabneassssedeacass 209 18 11 1 Three way and Greater Associations and
110. In addition not all artifacts will actually display the stereotype on the diagram At present this includes use cases and actors Documentation ArgoUML has some simple documentation facilities associated with artifacts on a diagram In general these should be used only to record the location of material in documents that can be handled by a main stream editor or word processor not the actual documentation itself Documentation for a particular artifact is recorded through the documentation tab in the details pane the quadrant of the user screen at the bottom right In addition annotation may be added to diagrams using the text icon on the editing pane toolbar 42 4 4 7 Captura de Requerimientos The recommendation is that a use case diagram should use the documentation tab of actors to record in formation about the actor or if the actor is complex to refer to a separate document that holds informa tion about the actor The documentation tab of use cases should record the location of the use case specification The inform ation in a use case specification for all but the simplest use cases is too complex to be placed directly in the tab The project should also have a separate vision document and supplementary requirements specification A text annotation on diagrams may be used to refer to these if the user finds this helpful Warning The documentation tab includes a Deprecated check box The state of this fl
111. In the UML metamodel Actor has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed Tip Actors sit outside the system and so their internal behavior is of little concern and this tagged value is best ignored semantics from the superclass Classifier The value is a specification of the semantics of the actor e derived from the superclass ModelElement Values true meaning the actor is redund ant it can be formally derived from other elements or false meaning it cannot Note Derived actors have limited value since they sit outside the system being designed They may have their value in analysis to introduce useful names or concepts Checklist Standard tab for a Classifier 17 2 2 Actor Property Toolbar Go up Navigate up through the package structure of the model 170 Use Case Diagram Artifact Reference Add Actor This creates a new actor within the model but not within the diagram navigating immediately to the properties tab for that actor Tip This method of creating a new actor may be confusing It is much better to create an actor on the diagram Delete This deletes the selected actor from the model Warning This is a deletion from the model not just the diagram To delete an actor fro
112. Instance coooconcccnccnnconoconncnnncnnncnnnonoso 277 23 4 COMPONENE er values er E a E Staaten psumess pants EE A EA NE O AS 278 23 4 1 Component Details Tabs 2 0 0 0 eee cee ce eeceeeceeeseeeeaeeenes 278 23 4 2 Component Property Toolbar 20 0 0 ee eee cee ce eeceeeee teen teen es 279 23 4 3 Property Fields For Component cece eeec eee ee eeeeeeeeee ees 280 23 3 Component Instances is erie i nee sE Reap o ress POSEES EEE EEE OSTRE ERES 280 23 5 1 Component Instance Details Tabs ec ceee cece eee eeeee es 281 23 5 2 Component Instance Property Toolbar cece cece ence eeee ee ee 281 23 5 3 Property Fields For Component Instance 0 0 0 0 cece eeee ee ee 282 23 6 Dependency associated roer io iras voter sasetentass 283 O fs E SA AE NEE E EE E dob EO TT aeed were 283 23 8 Interf ac ay sock eel rae ida Eni 283 23 9 A ces ures ore E rE S E E EEO NEER ESEO 283 ZO ODECE n a a ate ceeds gee ese E N A E a ERNS 284 23 MM ER TN 284 24 Built In DataTypes Classes Interfaces and Stereotypes cooccooccnnccnnconnconoconicnnnne 285 PAN Introduction eeren E tas esh ote ss S TESE i NOEP TEETE PRESO Ra 285 241 1 Package Stricture iioo a E EE i 285 24 1 2 Exposure inthe model isein ni e e epa i Gerris 285 24 2 Built In Datatype ssie ie nere EEEE EEEE Et 285 24 3 Bult In Classes ricos iii sit E ENESES EE EPEE TEPE prosa poi ies 286 24 3 1 Built In Classes From java lang ooocoooccn
113. L Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 196 Class Diagram Artifact Reference Checklist Standard tab for a Attribute 18 6 2 Attribute Property Toolbar Go up Navigate up through the package structure New attribute This creates a new attribute within the owning class of the current attribute navigating immediately to the properties tab for that attribute Tip This is a very convenient way to add a number of attributes one after the other to a class New Datatype This creates a new Datatype see Section 16 3 Datatype for the selected attribute navigating im mediately to the properties tab for that datatype New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected attribute navigating immediately to the properties tab for that stereotype Delete This deletes the attribute from the model Warning This is a deletion from the model not just the diagram If desired the whole attribute compartment can be hidden on the diagram using the style tab see Section 18 6 2 Attribute Property Toolbar or the button 2 pop up menu for the class on the dia gram 18 6 3 Property Fields For Attribute Name Text box The name of the attribute The name of a attribute has a leading lower case letter with words separated by bumpy caps
114. ML This is a convenient shorthand for creat ing a class that is restricted to the namespace of its owning class New class This creates a new class which appears on no diagram within the same namespace as the current class New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected class navigating im mediately to the properties tab for that stereotype Delete This deletes the class from the model Warning This is a deletion from the model not just the diagram To delete a class from the dia gram but keep it within the model use the main menu Remove From Diagram or press the Delete key 18 5 3 Property Fields For Class Name Text box The name of the class The name of a class has a leading capital letter with words separ ated by bumpy caps Note The ArgoUML critics will complain about class names that do not have an initial cap ital 193 Class Diagram Artifact Reference Stereotype Drop down selector Class is provided by default with the UML standard stereotypes for Class implementationClass and type and for Classifier metaclass powertype process threadand utility Tip One stereotype that is not part of the UML standard but is widely used is Singleton used to distinguish classes which have a single static instance and no public constructor Although not part of ArgoUML by default this stereotype is un derstood by the critics You may
115. ML standard stereotype from the superclass Association implicit Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 18 4 Stereotype Namespace 262 Collaboration Diagram Artifact Reference Text box Records the namespace for the association role This is the package hierarchy Button 1 double click on the entry will navigate to the item showm Base Drop down selector Records the association that is the base for the association role The drop down selector shows all associations that exist between the classifiers that correspond with the connected classifier roles Association End Roles Text area Lists the ends of this association role An association role can have any number of ends but two is generally the only useful number link objects can led to a third end on instance level dia grams but this is not supported by ArgoUML For more on association end roles see Section 21 4 Association End Role The names are listed unless the association end role has no name then it is shown as anon As sociationEndRole Button 1 double click on an association end role will navigate to that end Messages Text area Lists the messages that are associated with this association role Button 1 double click navigates to the selected entry 21 4 Association End Role An association end role is a specialization of an associati
116. Operation Stereotype 202 Operation Tagged Values 200 Operation Visibility 202 Opportunistic Design xvii 12 294 Owned Elements of Model 156 of Package 191 P Package 188 Package Details Tabs 189 Package Diagrams 188 Package Generalizations 191 Package Modifiers 190 Package Name 190 Package Namespace 190 Package Owned Elements 191 Package Specializations 191 Package Stereotype 190 Page Setup 76 Pane 294 Parameter 204 of Operation 203 Parameter Default Value 206 Parameter Details Tabs 204 Parameter Initial Value 206 Parameter Kind 206 Parameter Name 205 Parameter Property Fields 205 Parameter Property Toolbar 205 Parameter Stereotype 205 Parameter Tagged Values 204 Parameter Type 206 Parametros no funcionales en el documento de Visi n 31 Parent of Generalization 181 Partes Implicadas en un documento de Visi n 31 PGML 13 PNG 13 Post asumciones de Casos de Use 35 Post condiciones de Caso de Uso 35 Post conditions de Casos de Uso 35 Powertype of Generalization 181 Pre asumciones de Casos de Uso 34 Pre condici n de Caso de Uso 34 Pre condicion de Casos de Uso 34 Print 76 Problem Solving 12 292 Procesos Iterativos 9 Properties of Datatype 156 of Enumeration 161 Property Fields for Association 211 for Association End 214 for Attribute 197 for Class 193 for Datatype 158 for Diagrams 168 for Enumeration 162 for Operation 201 f
117. Panel de Tareas Pendientes con una vista de arbol de los tareas pendientes ordenadas de distintas maneras seleccionadas via la lista desplegable en lo alto del panel Cada vez que ArgoUML es iniciado sin un archivo de proyecto como argumento un nuevo proyecto en blanco es creado Este proyecto contiene un modelo llamado unt it ledModel Este modelo contiene un Diagrama de Clases en blanco llamado Diagrama de clase 1 y un Diagrama de Casos de Uso llamado Diagrama use case 1 El modelo y los dos diagramas vacios se pueden ver en el explorador que es la herramienta principal para navegar a traves de tu modelo Asumamos por un momento que este el el punto donde quieres empezar a modelar un nuevo sistema de compras T quieres darle el nombre purchasingmodel a tu modelo y quieres almacenarlo en un archivo llamado FirstProject 3 4 2 8 2 Guardando un Proyecto El Men Archivo Por ahora ArgoUML guarda diagramas usando un estandar propuesto recientemente Precision Graph ics Markup Language PGML Sin embargo tiene la opci n de exportar datos gr ficos como SVG para aquellos que quieran hacer uso de ello Cuando ArgoUML soporte UML 2 0 almacenar diagra mas usando el UML 2 0 Diagram Interchange format Primero salva el modelo en su estado vacio y sin nombre actual En la barra de men haz click en Archivo luego en Guardar Proyecto como como se muestra en Figure 3 7 Invocando Guardar Proyecto como Figure 3
118. Reference activity diagram all contained elements are deleted too 16 6 3 Property Fields For Diagram Name The name of the diagram There are no conventions for naming diagrams By default ArgoUML uses the space separated diagram name and a sequence number thus Use Case Diagram 1 Tip This name is used to generate a filename when activating the Save Graphics menu item 168 Chapter 17 Use Case Diagram Artifact Reference 17 1 Introduction This chapter describes each artifact that can be created within a use case diagram Note that some sub artifacts of artifacts on the diagram may not actually themselves appear on the diagram There is a close relationship between this material and the properties tab of the details pane see Sec tion 13 3 Properties Tab That section covers properties in general in this chapter they are linked to specific artifacts Figure 17 1 Possible artifacts on a use case diagram shows a use case diagram with all possible arti facts displayed Figure 17 1 Possible artifacts on a use case diagram 17 1 1 ArgoUML Limitations Concerning Use Case Dia grams Use case diagrams are now well supported within ArgoUML There still are some minor limitations though One is that extension points may be shown in a separate compartment on the use case but this is not retained after saving and reloading Note Earlier versions of ArgoUML 0 9 and earlier imple
119. Son mas utiles donde el caso de uso es uno de una serie de casos de uso subsidiarios que estan incluidos en un caso de uso principal donde pueden formar las pre condiciones del siguiente caso de uso que va a ser incluido Caution Como las pre condiciones las post condiciones son mejor evitarlas Colocan una carga en la especificaci n de los flujos de caso de uso para asegurar que la post condici n siempre se mantiene Por lo tanto son tambien una fuente de problemas y trabajo extra e Requerimientos En un mundo ideal el documento de visi n los diagramas de casos de uso las espe cificaciones de casos de uso y la especificacion de requerimientos suplementarios formari n los re querimientos para un proyecto Para la mayor a de los desarrollos lideres del mercado donde la propiedad de los requerimientos es ta dentro del mismo negocio que el equipo que har el desarrollo este no es normalmente el caso El departamento de marketing puede aprender captura de requerimientos basada en casos de uso y an alisis para enlazar con las actividades primarias de sus consumidores Sin embargo para desarrollos externos por contrato los consumidores pueden insistir en una lista de caracteristicas tradicional como la base del contrato Cuando este es el caso esta secci n de la espe cificaci n de casos de uso deber a enlazar con las caracteristicas del contrato que son cubiertas por el caso de uso Esto es hecho a menudo a traves de una h
120. Stereotyping Supplementary Requirement Specification SVG Requirement capturing is the process of identifying what the customer wants from the proposed system See Chapter 4 Cap tura de Requerimientos for a fuller description S ome behavior for which an object is held accountable A respons ibility denotes the obligation of an object to provide a certain beha vior A specific sequence of actions that illustrates behavior A UML Diagram showing the dynamic behavior as messages are passed between objects Equivalent to a Collaboration Diagram Which representation is appropriate depends on the problem under consideration See Section 5 4 Sequence Diagrams To be writ ten for more information Standard Graphical Markup Language Defined by ISO 8879 1986 A procedural programming language intended for simulation Noted for its introduction of objects and coroutines Within a Statechart Diagram a one of the possible configurations of the machine A UML Diagram showing the dynamic behavior of an active Object See Section 5 6 Statechart Diagrams To be written for more in formation Any artifact within UML can be given a stereotype to indicate its as sociation with a particular role in the design A stereotype spqr is generally indicated with the notation lt lt spqr gt gt A stereotype defines a Namespace within the design Examples of stereotypes are lt lt business gt gt and lt lt realizatio
121. Tagged Values Standard tab In the UML metamodel Node has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed e semantics from the superclass Classifier The value is a specification of the semantics of the node derived from the superclass ModelElement Values true meaning the node is redund ant it can be formally derived from other elements or false meaning it cannot Note Derived nodes still have their value in analysis to introduce useful names or con cepts and in design to avoid re computation 274 Deployment Diagram Artifact Reference Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 23 2 2 Node Property Toolbar Go up Navigate up through the package structure New reception This creates a new reception navigating immediately to the properties tab for that reception New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected node navigating im mediately to the properties tab for that stereotype Delete This deletes the node from the model Warning This is a deletion from the model not just the diagram To delete a node from the
122. Those artifacts that have specializations have a sub hierarchy showing the specializations e Class Associations In this view the top level shows the model Beneath this are all diagrams and all classes All classes that have associations have a hierarchy tracking through the associated classes e Residence centric In this view the model is shown at the top level with below it only Nodes and below these only components that reside on the nodes and below these components all elements that reside on the components e State centric In this view the top level shows all the state machines and all activity graphics associated with classes Beneath each state machine is a hierarchy showing the statechart diagram and all of the states Be neath each state is a list of the transitions in and out of the state Beneath each activity graph is a hierarchy showing the activity diagram and all of the action states Beneath each action state is a list of the transitions in and out of the action state e Transitions centric This is very similar to State centric view but under each state machine is listed the diagrams and all transitions on the diagram with states being shown as sub hierarchies under their connected transitions Similarly under each activity graph is listed the diagrams and all transitions on the diagram with ac tion states being shown as sub hierarchies under their connected transitions Composition centric In this view
123. UC ci o o e ado SR 133 14 2 Mouse Behavior in the To Do Pane coocooconcnoconcnoconcnoconcnnconcnnroncnnrononns 133 14 2 1 Button T Click cinco ici dishes cavas creia 133 14 2 2 Button 1 Double Click ooococcnoncccnonccononocononoconococononoconononos 133 14 2 3 Button 2 Actions coococcnonccononocononoconococononorononoronororonororonanonos 133 14 2 4 Button 2 Double Chek epai nai EE O E iaa 133 14 3 Presentation Selection nesi neiii e E EE EE EEES 134 14 4 Iten Count ern ni a Ea EEE EER EE A NEER A N E 134 IS TOS EAS n a Sates a Era une oe Causa E A AEAT 135 13 1 Introd tion nran it eae TE EEE T E E a 135 15 11 Temmology nean e e e E E e EES 135 15 1 2 Desi sn ISSUES cas E S A E EESE eA 135 1522 Uncategorized yepe pe E EEr EERE ph ule TEENE AIEN prepa ostras 135 153 Class Selecon id 135 15 3 1 Wrap Data Type sisssstosssesscsdads ino ieee e E e 135 15 3 2 Reduce Classes in diagram lt diagram gt coooconoconccnnocnncnnnncnnncninnnos 136 15 3 3 Clean Up Diagram sioe esr ecas Taepa ae or TE PE Ero S E TERS 136 15 4 Naming sti o alae easy Seger Peco weet 136 15 4 1 Resolve Association Name Conflict oocooccoccocnoconcnoconcnnroncnnnonos 136 ix ArgoUML Manual de Usuario 15 4 2 Revise Attribute Names to Avoid Conflict ooccoccoccncnoconcnnconos 136 15 4 3 Change Names or Signatures in an Artifact ccooocccnnccccnnccnnnccnnns 137 15 4 4 Duplicate End Role Names for an Association
124. a al ternativa creible a el enfoque funcional en analisis y dise 0 Podemos idientificar un numero de factores 1 La aparici n como corriente dominante de lenguajes de programaci n OO como SmallTalk y par ticularmente C C fu un lenguaje OO pragmatico derivado de C ampliamente usado por causa de su asociaci n con Unix 2 El desarrollo de potentes estaciones de trabajo workstations y con ellas la aparici n dentro de la corriente dominante de entornos de ventanas para los usuarios Los Interfaces Graficos de Usuario Graphical User Interfaces GUI tienen una estructura de objetos inherente 3 Un n mero de proyectos fallidos muy publicitados sugiriendo que el enfoque actual no era satisfact orio Un numero de investigadores propusieron procesos OOA amp D y con ellos notaciones Aquellas que al canzaron cierto exito incluyen Coad Yourdon Booch Rumbaugh OMT OOSE Jacobson Shlaer Mel lor ROOM para dise o de tiempo real y el hibrido Jackson Structured Development Durante los tempranos 1990 se hizo claro que estos enfoques tenian muchas buenas ideas a menudo muy similares Un gran obstaculo fu la diversidad de notaci n significando que los ingenieros tendi an a tener familiaridad con una metodologia OOA amp D en lugar de el enfoque en general UML fu concevido como una notacion com n que ser a de interes para todos los involucrados El estandar original fu gestionado por Rational Software www rational co
125. a composite aggregation loosely known as a composition Caution UML requires that an end with a composition relationship must have a multiplicity of 1 the default 12 9 8 Navigability This sub menu only appears with association artifacts when clicking at one end of the association It is used to control the navigability of the association There are three entries e bidirectional Make the association navigable in both directions e lt classl gt to lt class2 gt Make the association navigable only from lt class1 gt to lt class2 gt In other words lt class1 gt can reference lt class2 gt but not the other way round e lt class2 gt to lt class1 gt Make the association navigable only from lt class2 gt to lt class1 gt In other words lt class2 gt can reference lt class1 gt but not the other way round Note UML does permit an association to be non navigable in both directions ArgoUML will al low this but you will have to set each of the association ends navigation property reached from the property tab of the association and the diagram does not show any arrows in this case This is considered bad design practice it will trigger a critic in ArgoUML so is only of theoretical interest Note UML does not permit navigability from an interface to a class ArgoUML does not prevent this 12 10 Notation Notation is the textual representation on the diagram of a modelelement or its properti
126. a constructor and that there is no operation that updates this value Static Check box for static If unchecked the defaults then the attribute has instance scope If checked then the attribute is static 1 e it has class scope Static attributes are indicated on the diagram by underlining 18 7 Operation An operation is a service that can be requested from an object to effect behavior In the UML metamodel it is a sub class of BehavioralFeature which is itself a sub class of Feature In the diagram an operation is represented on a single line within the operation compartment of the class Its syntax is as follows visibility name parameter list return type expression property string You can edit this line directly in the diagram by double clicking on it All elements are optional and if left unspecified the old values will be preserved A stereotype can be given between any two elements in the line in the format lt lt stereotype gt gt The following properties are recognized to have special meaning abstract concurrency concurrent guarded leaf query root and sequential The visibility is or corresponding to public protected private visibility or pack age visibility respectively static and final optionally appear if the operation has those modifiers Any operation declared static will have its whole entry underlined on the diagram There may be zero or more entries in the parameter
127. a tecno log a puntera de ArgoUML 3 4 Fundamentos de ArgoUML El objeto de esta secci n es ponerte en marcha con ArgoUML Te llevar a traves de obtener el c digo y conseguirlo ejecutar 3 4 1 Empezando 3 4 1 1 Requerimientos del Sistema Puesto que ArgoUML est escrito en Java puro 100 deber a funcionar en cualquier maquina con Java instalado Es necesaria una versi n 1 4 o posterior de Java Puedes tenerlo disponible pero si no puede ser descargada gratis de www java com http www java com Ten en cuenta que solo necesitas el Java Runtime Environment JRE no hay necesidad de descargar el Java Development Kit JDK completo ArgoUML necesita una cantidad razonable de recursos Un PC con 200MHz de procesador 64Mb de RAM y 10Mb de espacio disponible en un disco duro deber a ser adecuado Descarga el c digo de la secci n de Descargas de sitio web del proyecto argouml tigris org http argouml tigris org Escoje la versi n que se ajusta a tus necesidades como se describe en la siguiente secci n 3 4 1 2 Opciones de Descarga Tienes tres opciones para obtener ArgoUML 1 Ejecutar ArgoUML directamente desde el Sitio Web usando Java Web Start Esta el la opci n mas facil 2 Descargar el c digo binario ejecutable Esta es la opci n correcta si pretendes usar ArgoUML regu larmente y no es muy dificil 3 Descargar el c digo fuente usando CVS y compilar tu propia versi n Escoge esta opci n si qui eres m
128. acada es la lista de carpetas con barras de desplazamiento en el centro del di logo Usando la barra de desplazamiento en la derecha puedes moverte arriba y abajo en la lista de carpetas contenida dentro de la carpeta actualmente seleccionada Si puedes desplazarte o no de pende de la cantidad de archivos y carpetas mostradas y ademas como est n mostradas Si todo ajusta entonces la ventana no es desplazable como se ve en la ilustraci n Haciendo Doble Click en una de las carpetas mostradas te introduce hace navegar dentro de esa carpeta permitiendote navegar rapidamante entre la jerarqu a de carpetas de tu disco duro Date cuenta que solo los nombres de carpetas y no nombres de archivo son mostrados en el area naveg able De echo el di logo est actualmente dispuesto deacuerdo para mostrar solo archivos de proyecto ArgoUML con la extension zargo como puede verse en el control de la parte baja de la ventana etiquetado como Archivos de Tipo Ten en cuenta tambien que el nombre de carpeta seleccionado actualmente es mostrado en el control desplegable de la parte alta de la ventana etiquetado como Buscar en Un unico click en una carpeta dentro del area navegable selecciona la carpeta en la pantalla pero no selecciona la carpeta para guardar En la parte superior del di logo sobre el area navegable de selecci n de carpet s hay algunas her ramientas mas para navegar entre carpetas e El control desplegable de Carpeta Haciendo
129. aci n ArgoUML est disponible en formatos zip o tar gz Escoge el primero si eres un usuario de Mi crosoft Windows y el ultimo si est s ejecutando alguna variedad de Unix Desempaquetandolo como sigue e En Windows Descomprime el archivo zip con WinZip o en ultimas versiones of Windows ME XP copia los archivos fuera de la carpeta comprimida y ponlos en un directorio de tu elecci n e En Unix Usa GNU tar para descomprimir y desempaquetar los archivos en un directorio de tu elecci n tar zxvf lt file gt tar gz Si tienes una versi n antigual de tar la opci n z puede no estar disponible as que usa gunzip lt file tar gz tar xvf Deber as tener un directorio conteniendo un numero de archivos jar y un README txt 3 4 1 5 Problemas Descargando Si te quedas completamente atascado y no tienes asistencia local intenta el sitio web particularmente el FAQ http argouml tigris org faqs users html Si esto a n no resuelve el problema intentalo en la lista de correo de usuarios de ArgoUML Te puedes subscribir a traves de la secci n de listas de correo del sitio web del proyecto argouml tigris org http argouml tigris org o envia un mensaje vacio a usersOargouml org mailto users Oargouml org con el asunto subscribe en ingles Puedes entonces enviar tu problema a users argouml org mailto users Cargouml org en ingles and ver como otros usuarios son capaces de ayudar La lista de correo de usuari
130. ackage nothing can happen and this button is allways downlighted New Package This creates a new Package see Section 18 2 Package within the model which appears on no diagram navigating immediately to the properties tab for that package Tip While it can make sense to create Packages of the model this way it is usually a lot clearer to create them within diagrams where you want them New DataType This creates a new DataType see Section 16 3 Datatype within the model which appears on no diagram navigating immediately to the properties tab for that DataType New Enumeration This creates a new Enumeration see Section 16 4 Enumeration within the model which appears on no diagram navigating immediately to the properties tab for that Enumeration New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype within the model navigating imme diately to the properties tab for that stereotype Delete This tool is always downlighted since it is meaningless to delete the model 16 2 3 Property Fields For The Model Name Text box The name of the model The name of a model like all packages is by convention all lower case Note The default name supplied to a new model by ArgoUML untitledModel is thus erroneous and guarantees that ArgoUML always starts up with at least one problem being reported by the design critics 154 Top Level Artifact Reference Ster
131. ady met once The big step is casting everything into concrete terms We move from the abstract concepts of analysis to their con crete realization Once again the recursive and iterative nature of our process means we will come back to the Design phase many times in the future 6 1 The Design Process To be written To be written 6 1 1 Class Responsibilities and Collaborators CRC Cards Strength of CRC cards during Design Spreading Objet Oriented Design Expertise e Design Reviews e Framework for Implementation e Informal Notation e Choice of supporting software components e Performance Requirements In this phase developers replace some of the domain experts in the group but there should always be at least one domain expert in the group The focus of the group moves from what is to be done to how to do it The classes from the solution do main are added to those defined in the analysis phase Think about what classes are needed to make the system work Do you need a List class to hold objects Do you need classes to handle exceptions Do you need wrapper classes for other subsystems New classes that are looked for in this part are classes that support the implementation of the system During the design phase the distinction between class and object becomes important Think about the objects in your scenarios Who creates the objects What happens when it is created and destroyed What is the lifetime of the object
132. ag is not preserved over save and load in the current release of ArgoUML System Boundary Box ArgoUML provides a series of tools to provide arbitrary graphical annotation on diagrams we have already mentioned the text tool These are found at the right hand end of the editing pane toolbar and are fully documented in the reference manual see Chapter 12 The Editing Pane The rectangle tool can be used to draw the boundary box Use the button 2 context sensitive Ordering pop up menu to place it behind everything else However there is no way to change its fill color from the default white You may therefore prefer to draw the boundary box as four lines This is the method used for the diagrams in this chapter Note The editing pane in ArgoUML has a grid to which objects snap to aid in drawing The size of this grid and its effect may be altered through the View menu using Adjust Grid and Adjust Grid Snap This is described fully in the reference manual see Chapter 10 The Menu bar 4 5 Case Study 4 5 1 4 5 1 1 Vision Document A vision document contains more than those things needed for the modeling effort It also contains fin ancial and scheduling pertinent information The following sections are those parts of the Vision Docu ment spelled out in Section 4 3 1 Documento de Visi n above In practice this format need not be followed religiously but is used here for consistency Summary The company wishes to p
133. all modelelements are shown according their composition in the UML metamodel This perspective shows far more modelelements then all others it does not hide anything Hence this view is not so user friendly but very suited for the UML specialist 11 5 Configuring Perspectives The explorer is designed to be user configurable to allow the designer to view in his or her preferred way 11 5 1 The Configure Perspectives dialog button 1 click on the Configure Perspectives icon at the top left of the explorer brings up the ex plorer perspectives dialog see Figure 11 2 The Configure Perspectives dialog box Figure 11 2 The Configure Perspectives dialog box 101 11 6 11 6 1 The Explorer The top half of the dialog contains a list of all the currently defined perspectives and to the right a series of buttons stacked vertically Button click can be used to select a perspective You can select only one perspective at a time Selecting a perspective reveals a text field above the list where the name of the perspective can be ed ited The lower half of the dialog contains two list areas The one on the left labeled Rules Library contains the list of available rules that may be used to create the perspective The one on the right labeled Selected Rules contains the actual rules chosen for the perspective that has been selected in the list of perspectives at the top In both lists you can select only one ru
134. ally are inside nodes A suggestion that component instances represent the logical entities within physical nodes and so should be drawn within a node instance where node instances are shown on the deployment diagram 15 8 7 Classes normally are inside components A suggestion that classes as artifacts making up components should be drawn within components on the deployment diagram 15 8 8 Interfaces normally are inside components A suggestion that interfaces as artifacts making up components should be drawn within components on the deployment diagram 15 8 9 Objects normally are inside components A suggestion that objects as instances of artifacts making up components should be drawn within com ponents or component instances on the deployment diagram 15 8 10 LinkEnds have not the same locations A suggestion that a link e g association connecting objects on a deployment diagram has one end in a 144 The Critics component and the other in a component instance since objects can be in either This makes no sense 15 8 11 Set classifier Deployment Diagram Suggestion that there is an instance object without an associated classifier class datatype on a de ployment diagram 15 8 12 Missing return actions Suggestion that a sequence diagram has a send or call action without a corresponding return action 15 8 13 Missing call send action Suggestion that a sequence diagram has a return action b
135. alog box that allows selecting an already existing signal e New Signal Creates a new Signal and navigates to it When Double text field Only present for a Time Event This allows expressing the time that the event is called The first of the two fields is for the body of the expression and the second one for the language in which it is written Warning In ArgoUML VO0 20 the properties panel of a change event lacks a field to enter the change expression 20 10 Guard A guard is associated with a transition At the time an event is dispatched the guard is evaluated and if 247 Statechart Diagram Artifact Reference false its transition is disabled In the UML metamodel Guard is a child of ModelElement A guard is shown on the diagram by the text of its expression in square brackets 20 10 1 Guard Details Tabs The details tabs that are active for guards are as follows ToDoltem Standard tab Properties See Section 20 10 2 Guard Property Toolbar and Section 20 10 3 Property Fields For Guard below Documentation Standard tab Stereotype Standard tab containing the stereotypes for the guard In the UML metamodel Guard has no standard stereotypes defined Tagged Values Standard tab In the UML metamodel Guard has no standard tagged values defined 20 10 2 Guard Property Toolbar Go up Navigate up through the package structure New Stereotyp This creates a new Ste
136. alog box with changes made to diagrams change of name addition of diagrams deletion of diagrams 10 5 2 Find This menu entry brings up a non modal dialog box for the ArgoUML search engine Figure 10 20 The dialog for Find At the top the dialog box has four tabs labeled Name and Location Last Modified Tagged Values and Constraints Of these all but the first are grayed out in the V0 22 version of ArgoUML because they are not imlemented yet so the first tab is always selected The Name and Location specifies the search to be made It contains the following e A text box labeled Element Name specifies the name of the element or artifact to search for Wild cards may be used here A drop down gives access to find expressions previously used e A text box labeled In Diagram specifies which diagrams are to be searched Again wild cards may be used Both these two text boxes have a default entry of i e match anything e To the right of these two text boxes a selector labeled Element Type allows you to specify the UML metaclass for which you are searching e A selector labeled Find in allows the search to be made over the entire project the default or as a sub search over the results of a previous search When opened a list of all the search result tabs ap pears e Beneath these boxes is the button Clear Tabs This clears the display of tabs with the results from previous searches see below This
137. als are as follows ToDoltem Standard tab Properties See Section 18 9 2 Signal Property Toolbar and Section 18 9 3 Property Fields For Signal be low Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab There is nothing generated for a signal Tagged Values Standard tab In the UML metamodel Signal has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed semantics from the superclass Classifier The value is a specification of the semantics of the signal e derived from the superclass ModelElement Values t rue meaning the signal is redund ant it can be formally derived from other elements or false meaning it cannot Note Derived signals still have their value in analysis to introduce useful names or con cepts and in design to avoid re computation Note 207 Class Diagram Artifact Reference The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 18 9 2 Signal Property Toolbar Navigate up through the package structure New signal This creates a new signal navigating immediately to the properties tab for that signal Caution The
138. also not show the Add to Diagram pop up menu for action states 22 2 3 Property fields for action state Name Text box The name of the action state By convention action state names start with a lower case let ter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Container Text box The container of the action state This shows the otherwise invisible composite state at the top of the containment hierarchy Entry Action Text box Shows the name of the action to be invoked on entry to this action state According the UML standard an Action State is obliged to have an Entry Action Button 1 double click navigates to the shown entry button 2 gives a pop up menu with two entries e New Add a new Entry action of a certain kind This menu has the following 7 submenus to select the kind of action Call Action Create Action Destroy Action Return Action Send Action Ter minate Action Uninterpreted Action e Delete From Model Delete the Entry Action Deferrabl vents Text box The deferrable events of the action state Incoming Text area Lists the transitions that enter this action state Button 1 double click navigates to the selected entry Outgoing Text area Lists the transitions that leave this action state Button 1 double click navigates to the selected entry 22 3 Action This artifact is described in the context of statechart diagrams see Sec
139. alto nivel de los objetos que conformaran la soluci n a veces conocida como dia grama de concepto Introduciremos el diagrama de sequencia y diagrama de estados para capturar requerimientos por el comportamiento global del sistema Finalmente tomaremos los Casos de Uso de la etapa de captura de requerimientos y remoldearlos en el lenguaje del dominio de la soluci n Esto ilustrar las ideas UML de estereotipado y realizaci n 3 2 2 3 Dise 0 Usamos el diagrama de paquetes UML para organizar los componentes del proyecto Luego revisare mos el diagrama de clases diagrama de secuencia y diagrama de estados para mostrar como pueden ser usados recursivamente para dise ar la soluci n completa Durante esta parte del proceso necesitamos desarrollar nuestra arquitectura del sistema para definir como todos los componentes ajustaran juntos y funcionaran Aunque no es estrictamente parte de nuestro proceso miraremos a como el diagrama de colaboraci n UML puede ser usado como una alternativa para o complementar el diagrama de secuencia Similar mente miraremos al diagrama de actividades UML como una alternativa o complemento para el dia grama de estado Finalmente usaremos el diagrama de despliege UML para especificar como el sistema ser finalmente realizado 3 2 2 4 Construcci n UML no est realmente afectado con la escritura de codigo Sin embargo en esta etapa mostraremos como ArgoUML puede ser usado para generaci n d
140. am in the editing pane If a pack age is currently selected then the use case diagram will be created within that package This means that it will be shown within the package on the explorer hierarchy under Package centric view and artifacts created on the diagram will be created within the namespace of the package This does not only apply to a package but also to a class interface use case etc Tip This does not prevent artifacts from other namespaces packages appearing on the diagram They can be added from the explorer using Add to Diagram from the button 2 pop up menu 10 6 2 New Class Diagram This menu entry creates a blank class diagram and selects that diagram in the editing pane If a package is currently selected the class diagram will be created within that package This means that it will be shown within the package on the explorer hierarchy under Package centric view and artifacts created on the diagram will be created within the namespace of the package This does not only apply to a pack age but also to a class interface use case etc Tip This does not prevent artifacts from other namespaces packages appearing on the diagram They can be added from the explorer using Add to Diagram from the button 2 pop up menu 10 6 3 New Sequence Diagram This menu entry creates a blank sequence diagram and selects that diagram in the editing pane It also creates a Collaboration UML element which is a container for the
141. an arbitrary multiplicity 4 4 4 Hierarchical Use Cases 4 4 4 1 Includes The procedure for adding an include relationship is the same as that for adding an association but using the include icon from the editing pane toolbar to join two use cases Since include relationships are directional the order in which the two ends are selected is important The including main use case should be selected first button 1 down and the included subsidiary use case second button 1 release It is possible to name include relationships using the property tab but this is rarely done and will not be displayed on the use case diagram 4 4 4 2 Extends The procedure for adding an extend relationship is the same as that for adding an include relationship but using the extend icon from the editing pane toolbar to join two use cases As with include relationships the order of selection matters In this case the extending subsidiary use case should be selected first button 1 down and the extending main use case second button 1 re lease Note This is the reverse of the include relationship but reflects the way that designer s tend to think The fact that the extend icon s arrow points upward the opposite of the include icon should help remind you of this To set a condition for the extend relationship select the extend relationship in the editing pane button 1 click and then bring up its property tab in the details pane
142. and this menu entry is empty by default 10 11 The Help Menu This menu provides help on the use of ArgoUML It has two entries 10 11 1 System Information This menu entry brings up the system information dialog see Figure 10 25 The dialog for Sys tem Information Figure 10 25 The dialog for System Information Use this menu to describe the system that runs ArgoUML to the system manager or developer Pressing the button Run Garbage Collector not only runs the Java gargage collector but also refreshes the information shown To facilitate copy and paste into e g an email the button Copy Informa tion to System Clipboard is foreseen The Cancel button dismisses the dialog box 10 11 2 About ArgoUML This menu entry brings up the help window for ArgoUML see Figure 10 26 The help window for ArgoUML Figure 10 26 The help window for ArgoUML 97 The Menu bar The window has six tabs which are selected by button 1 click By default the first tab Splash is shown e Splash This displays the picture shown when ArgoUML starts up and the current version number e Version This provides version information on the various packages that make up ArgoUML and some operating system and environment information Credits This details all those who have created ArgoUML including contact details for the vari ous module owners Contact Info This gives the major contact points for the ArgoUML project the
143. anley e Chief Executive Officer Hun Atilla The e Marketing Harry Oil Can 4 5 1 5 Key Features Cash deposit cash withdrawal and account inquiries by customers Customers include people who have accounts at the owning bank as well as people who wish to make withdrawals from accounts in other banks or from credit card accounts Maintenance of the equipment by the bank s engineers This action may be initiated by the engineer on a routine basis It may also be initiated by the equipment that can call the engineer when it detects an in ternal fault Unloading of deposits and loading of cash by officials of the local bank branch These actions occur either on a scheduled basis or when the central computer determines that the cash supply is low or the deposit receptacle is liable to be getting full An audit trail for all activities will be maintained and sent periodically to the bank s central computer It will be possible for the maintenance engineer to save a copy of the audit trail to a diskette for transport ing to the central computer Both dialup and leased line support will be provided The ATM will continue to provide services to cus tomers when communications with the central computer is not available 4 5 1 6 Constraints The project must be completed within nine months It must cost no more than 1 750 000 USD excluding production costs Components may be contracted out but the basic architecture as well as the infrastruc
144. antas instancias del caso de uso Po defecto asumimos que una instancia de un actor interacciona con una instancia de un caso de uso En otros casos podemos etiquetar la multiplicidad de un extremo de la asociaci n una de dos con un n mero para indicar cuantas instancias est n involucradas o con un rango separado por dos puntos Un asterisco es usado para indicar un n mero arbitrario En el ejemplo del Cajero Autom tico solo hay un sistema central pero el puede estar gestionando cu alquier n mero de usos de Cajero Autom tico Por lo tanto colocamos la etiqueta 0 en el ex tremos del caso de uso No se necesita etiqueta en el otro extremo ya que por defecto es uno Un banco local tendr hasta tres oficiales autorizados para cargar y descargar los Cajeros Autom ticos Asi en el extremo del actor de la relaci n con el caso de uso Mantenimiento Ca jero Autom tico colocamos la etiqueta 1 3 Ellos pueden estar tratando con cualquier n mero de Cajeros Automaticos as en el otro extremo colocamos la etiqueta 0 Puede haber cualquier n mero de clientes y puede haber cualquier n mero de sistemas de Cajero Autom tico que pueden usar As a cada extremo de la asociaci n colocamos la etiqueta 0 Figure 4 3 Diagrama de casos de uso para un sistema de Cajero Autom tico mostrando multiplicid 32 Captura de Requerimientos ad muestra el diagrama de casos de uso del Cajero Autom tico con multipli
145. apter 1 Introducci n 1 1 Origenes y Visi n General de ArgoUML 1 1 1 Analisis Orientado a Objeto y Dise 0 1 1 2 Durante la ltima decada el Analisis Orientado a Objeto y Dise o Object Oriented Analysis and Design OOA amp D se ha convertido en el paradigma de desarrollo de software dominante Con ello se ha conseguido un gran avance en los procesos de pensamiento de todos los involucrados en el ciclo de vida del desarrollo des software El soporte de objetos en un lenguaje de programaci n empez con Simula 67 pero fue la aparici n en la decada de 1980 de los lenguajes h bridos como es C Ada y Object Pascal lo que permiti a OOA amp D despegar Estos lenguajes proporcionaban soporte para OO ademas de para programaci n procedural La programaci n Orientada a Objeto se convirti en la corriente dominante Un sistema OO est dise ado y implementado como una simulaci n del mundo real usando artefact os software Esta premisa es tan potente como simple Usando un acercamiento OO para dise ar un sistema puede ser dise ado y testeado o mas correctamente simulado sin tener que construir el sis tema real primero Es el desarrollo durante la decada de 1990 de herramientas para soportar analisis Orientado a Objeto y dise o lo que coloco este enfoque en la corriente dominante Cuando se combina con la capacidad de dise ar sistemas a muy alto nivel una herramienta basada en el enfoque OOA amp D ha permitido la im plementa
146. are as follows ToDoltem Standard tab Properties See Section 20 8 2 Transition Property Toolbar and Section 20 8 3 Property Fields For Trans ition below Documentation Standard tab Presentation Standard tab The values for the bounds of the transition are downlighted since the position of the transition is defined by its end points Stereotype Standard tab In the UML metamodel Transition has no stereotypes defined by default Tagged Values Standard tab In the UML metamodel Transition has no standard tagged values defined Checklist Standard tab for a transition 20 8 2 Transition Property Toolbar 243 Statechart Diagram Artifact Reference Go up Navigate up in the hierarchy to the parent state machine New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected transition navigating immediately to the properties tab for that stereotype Delete This deletes the transition from the model Warning This is a deletion from the model not just the diagram To delete a transition from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 20 8 3 Property Fields For Transition Name Text box The name of the transition By convention transition names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention S
147. are as follows ToDoltem Standard tab Properties See Section 20 9 2 Event Property Toolbar and Section 20 9 3 Property Fields For Event be low Documentation Standard tab Stereotype Standard tab In the UML metamodel an Event has the following standard stereotypes defined e create for a CallEvent only Create is a stereotyped call event denoting that the instance receiving that event has just been created For state machines it triggers the initial transition at the topmost level of the state machine and is the only kind of trigger that may be applied to an initial transition e destroy for a CallEvent only Destroy is a stereotyped call event denoting that the in stance receiving the event is being destroyed Tagged Values Standard tab In the UML metamodel an Event has no standard tagged values defined 20 9 2 Event Property Toolbar Go up Navigate up through the composition structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected event navigating im mediately to the properties tab for that stereotype New parameter This creates a new parameter for the event operation as the current parameter navigating immedi ately to the properties tab for that parameter see Section 18 8 Parameter Delete This deletes the event from the model 20 9 3 Property Fields For Event Name Text box The name of the event By con
148. ares abiertos extensivamente UML XMI SVG OCL y otros 3 ArgoUML es una aplicaci n Java pura 100 Esto permite a ArgoUML funcionar en todas las plata formas para las cuales un puerto fiable de la plataforma Java 2 esta disponible 4 ArgoUML es un proyecto de codigo abierto La disponibilidad del codigo fuente asegura que una nueva generaci n de dise adores de software e investigadores ahora tienen un entorno de trabajo 1 Introducci n probado desde el que pueden conducir el desarrollo y evoluci n de tecnolog as de herramientas CASE UML es el lengueje de modelado OO mas prevalente y java es una de las plataformas de desarrollo OO mas productivas Jason Robbins y el resto de su equipo de investigaci n en la universidad de Califor nia Irvine potenciaron estos beneficios creando ArgoUML El resultado es un entorno y una herrami enta de desarrollo s lida para dise 0 de sistemas OO Es mas proporciona un campo de de pruebas para la evoluci n del desarrollo e investigaci n de herramientas CASE orientadas a objeto Una primera publicaci n de ArgoUML fue disponible en 1998 y mas de 100 000 descargas a mediados de 2001 demostr el impacto que este proyecto ha provocado siendo popular en campos educacionales y comerciales 1 1 3 Encontrando Mas Sobre el Proyecto ArgoUML 1 1 3 1 Como est desarrollado ArgoUML Jason Elliot Robbins fund el Proyecto Argo y proporciono un liderazgo temprano al proyecto Mien tras Jas
149. as a leading capital letter with words separated by bumpy caps Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Component is provided by default with the UML standard stereotypes docu ment executable file library and table ArgoUML also provides the standard Classi fier stereotypes metaclass powertype process threadand utility Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records and allows altering the namespace for the component This is the package hierarchy Modifiers Check box with entries abstract leaf and root e Abstract is used to declare that this component cannot be instantiated but must always be spe cialized e Leaf indicates that this component cannot be further specialized e Root indicates the node can have no generalization Generalizations Text box Lists any component that generalizes this component Specializations Text area Lists any derived components i e those for which this component is a generalization Client Dependencies Text area Lists outgoing dependencies Button 1 double click navigates to the dependency Supplier Dependencies Text area Lists incoming dependencies Button 1 double click navigates to the dependency Residents Text box Lists any residents see Section 23 4 Component d
150. ate flow might look like A A Customer does not require a receipt 1 A At step 1 of the basic flow the customer indicates they do not want a receipt 1 A The basic flow proceeds from step 2 to step 4 and step 5 is not used 1 The convention is to number the various alternate flows as A 1 A 2 A 3 etc The steps within an altern ate flow are then numbered from this So the steps of the first alternate flow would be A 1 1 A 1 2 A 1 3 etc 4 3 3 3 Iterative Development of Use Case Specifications 4 3 4 Iterative development will prioritize the use cases and the first iterations will address the most import ant Early iterations will capture the basic flows of the most important use cases with only essential detail and list the headings of the main alternate flows Later iterations will address the remaining use cases flesh out the steps on individual alternate flows and possibly provide more detail on individual steps Supplementary Requirement Specification This captures the non functional requirements or constraints placed on the system Since use cases are inherently functional in nature they cannot capture this sort of information Note Some analysts like to place non functional requirements in a section at the end of each use case specification containing the non functional requirements relevant to the use case I don t like this for two reasons First key non functional requirements for example about per
151. ation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist 226 Sequence Diagram Artifact Reference Standard tab for a Classifier 19 2 2 Object Property Toolbar Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected object navigating immediately to the properties tab for that stereotype Delete This deletes the object from the model Warning This is a deletion from the model not just the diagram To delete an object from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 19 2 3 Property Fields For Object Name Text box The name of the object By convention object names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Object has no stereotypes by default in the UML standard Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 18 4 Stereotype Namespace Text box Records the namespace for the object This is the package hierarchy Stimuli Sent Text area Lists the stimuli sent to this object Stimuli Received Text
152. ault in the Export Graphics and Export All Graphics menu items e Graphics Export Resolution This allows you to artificially increase the resolution of pro duced graphics The advised setting is Standard To be able to use High or Extra High you usu ally need to start the Java virtual machine with extra memory e argo root The full path to the ArgoUML program i e the argouml jar file e S argo home The ArgoUML home directory which contains the jar files needed by ArgoUML argo ext dir The directory holding ArgoUML extensions by default the ext sub directory of the ArgoUML build directory e Jjava home The home directory of the Java Runtime Environment JRE e user home The user s home directory Used for storing the argo user properties file e user dir The directory from which ArgoUML was started e Startup Directory The directory in which ArgoUML starts file searches etc 10 4 5 3 User Tab This tab allows the user to record additional information of use to the system There are two text boxes provided Figure 10 15 The dialog for Settings User Full Name Allows the user to record her full name e Email Address Allows the user to record his Email address This information is used when requesting to do help by Email 10 4 5 4 Appearance Tab This tab allows the user to specify the LAF Look And Feel and theme i e what the complete ArgoUML UI looks like It comp
153. be added to the model The 7 kinds of states supported are Pseudo State Synch State Stub State Composite State Simple State Final State Submachine State Warning 241 20 5 20 6 20 7 Statechart Diagram Artifact Reference Using this way of adding states to the model is not a good idea since you will have to add the state to the diagram later This can be done by selecting it in the explorer and activating the pop up menu and selecting Add to Diagram It is advisable to use the toolbar of the diagram instead e Delete From Model Delete the selected state from the model Concurrent Region A Concurrent Region is an orthogonal conjunctive component of a composite state allowing concur rency to be constructed A concurrent region is represented on the diagram by a tile of a composite state separated from other re gions by a dashed line ArgoUML currently only supports a horizontal division of a concurrent composite state in regions The description of the details panels of a concurrent region is identical to that of a composite state see Section 20 4 Composite State and so is not duplicated here Submachine State A submachine state is a syntactical convenience that facilitates reuse and modularity It is a shorthand that implies a macro like expansion by another state machine and is semantically equivalent to a com posite state The state machine that is inserted is called the referen
154. ble click navigates to the selected entry button 2 gives a pop up menu with one entry e New Add a new guard Effect Text box Shows the action if any to be invoked as this transition is taken Button entries 1 double click navigates to the selected action button 2 gives a pop up menu with two e New Add a new Effect action of a certain kind This menu has the following submenus to se lect the kind of action Call Action Create Action Destroy Action Return Action Send Action Terminate Action Uninterpreted Action e Delete From Model Delete the selected action from the model 20 9 Event An event is There are a an observable occurrence In the UML metamodel it is a child of ModelElement number of different types of events that are children of event within the UML metamodel e CallEvent Associated with an operation of a class this event is caused by a call to the given oper ation The expected effect is that the steps of the operation will be executed e Signall Event Associated with a signal this event is caused by the signal being raised e TimeEvent An event cause by expiration of a timing deadline e Changel true An event is Event An event caused by a particular expression of attributes and associations becoming represented by its name 20 9 1 Event Details Tabs 245 Statechart Diagram Artifact Reference The details tabs that are active for events
155. bset of the relationships that should be shown available which restricts the ability to show dynamic behavior of deployed code It is not possible to create new interfaces directly on this diagram they can only be added if they are first created in the model by drawing them on a class diagram It is an inconvenience that the alternative representation of an interface as a small circle is not suppor ted 23 2 Node 273 Deployment Diagram Artifact Reference A node is a run time physical object on which components may be deployed In the UML metamodel it is a sub class of Classifier A node is represented on a class diagram as a three dimensional box labeled with its name 23 2 1 Node Details Tabs The details tabs that are active for nodes are as follows ToDoltem Standard tab Properties See Section 23 2 2 Node Property Toolbar and Section 23 2 3 Property Fields For Node be low Documentation Standard tab Presentation Standard tab The Bounds field defines the bounding box for the node on the diagram Warning Beware that in the 0 18 release of ArgoUML the bounding box just refers to the front face of the cube This means that the three dimensional top and side may be ignored for example when determining the limits of a diagram for saving graphics Source Standard tab but with no contents Caution A node should not generate any code so having this tab active is probably a mistake
156. but only one is allowed to commence The others are blocked until the performance of the first operation is complete Caution It is up to the system designer to ensure that deadlock cannot occur It is the re sponsibility of the operation to implement the blocking behavior as opposed to the system e sequential Only one call to an instance of the class with the operation may be outstanding at any one time There is no protection and no guarantee of behavior if the system violates this rule e concurrent Multiple calls to one instance may execute at the same time The operation is re sponsible for ensuring correct behavior This must be managed even if there are other sequential or synchronized guarded operations executing at the time Parameter Text area with entries for all the parameters of the operation see Section 18 8 Parameter A new operation is always created with one new parameter return to define the return type of the operation Button 1 double click on any of the parameters navigates to that parameter Button 2 click brings up a pop up menu with two entries e Move Up Only available where there are two or more parameters and the parameter selected is not at the top It is moved up one position e Move Down Only available where there are two or more parameters listed and the parameter selected is not at the bottom It is moved down one position Raised Signals Text area with entries for all th
157. button 1 click on the tab The text of the condition may be typed in the Condition field Long conditions may be split over several lines if de sired The condition is displayed under the extend label on the diagram It is possible to name extend relationships using the property tab but this is rarely done and will not be displayed on the use case diagram 4 4 4 3 Generalization 41 4 4 5 4 4 6 Captura de Requerimientos The procedure for adding generalizations is the same as for adding extend relationships but using the generalization icon from the editing pane toolbar Since generalization is a directed relationship the order of selection matters The specialized use case should be selected first button 1 down and the generalized second button 1 release It is also possible to add generalizations using small handles that appear to the top and bottom of a use case when it is selected Dragging the handle at the top to another use case will create a generalization The original use case is the specializing end and the use case to which the handle was dragged will be the generalizing end Dragging into empty space will create a new use case to be the generalizing end Similarly dragging on the bottom handle will create a generalization in which the original use case is the generalizing end Generalization is also permitted between actors although its use is beyond the scope of this tutorial Un like us
158. button is downlighted if there are no tabs but the Help tab And finally there is the button Find This causes the search specified in the text boxes and selectors above to be executed The results are displayed in a tab taking up the lower two thirds of the page The lower two thirds of the dialog comprises an initial tab labeled Help giving summary help and further tabs displaying the results of searches These search tabs are labeled with a summary of the 86 The Menu bar search element in diagram and are divided horizontally in two halves Button double clicking on these tabs removes the tab and spawns a new window that contains the tab contents i e the search results This window can be moved and sized at will This does not work for the help tab The top half is labeled Search Results followed by a count of the number of items found It com prises a table with one row for each element artifact and four columns The width of the columns can be adjusted e Type Lists the type of element artifact e Name Lists the name given to the element artifact e In Diagram Where the artifact is visible on a diagram this lists the name of the diagram other wise it shows N A e Description Contains a description of the element artifact In ArgoUML VO0 18 this seems to be restricted to the single entry docs Button 1 click on any row will give more information on that artifact by showing related artifacts in the b
159. can be formally derived from other elements or false meaning it cannot Caution A derived parameter is a meaningless concept Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 204 Class Diagram Artifact Reference 18 8 2 Parameter Property Toolbar Go up Navigate up through the package structure New parameter This creates a new parameter for the for the same operation as the current parameter navigating im mediately to the properties tab for that parameter Tip This is a convenient way to add a series of parameters for the same operation New Datatype This creates a new Datatype see Section 16 3 Datatype in the namespace of the owner of the operation of the parameter navigating immediately to the properties tab for that datatype New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected parameter navigat ing immediately to the properties tab for that stereotype Delete This deletes the parameter from the model Warning This is a deletion from the model not just the diagram If desired the whole operation compartment can be hidden on the diagram using the presentation tab or the button 2 pop up menu for the class on the diagram 18 8 3 Property Fields For Parameter Name Text box The name of the parameter By convention
160. casos de uso mas simples es mostrada en UML usando una relaci n de inclusi n una flecha punteada desde el caso de uso principal hasta el subsidiario con la etiqueta include Figure 4 4 Diagrama de caso de uso para un sistema de Cajero Autom tico mostrando relaciones de inclusi n Las relaciones de inclusi n son buenas para desmantelar los comportamientos de casos de uso en jerar quias Sin embargo podemos tambien querer mostrar un caso de uso que es una extensi n de un caso de uso existente para atender a una circunstancia particular En el ejemplo del Cajero tenemos un caso de uso cubriendo la rutina de mantenimiento del Cajero Mantener Equipamiento Tambien queremos cubrir el caso especial de una reparaci n no programada causada por la detecci n de un fallo interno por parte del Cajero Esto est mostrado en UML por la relaci n de extensi n En el caso de uso principal especificamos un nombre para un lugar en la descripci n donde una extensi n del comportamiento podr a ser ad juntada El nombre y lugar son mostrados en un compartimento separado dentro del ovalo del caso de uso La representaci n de relaci n de extensi n es la misma que la de la relaci n de inclusi n pero con la etiqueta extend Paralelamente a la relaci n de extensi on especificamos la condicion bajo la cual ese comportamiento ser adjuntado Figure 4 5 Diagrama de casos de uso para un sistema de Cajero Autom tico mostrando una re
161. cause its details to be shown in the To Do Item tab of the details pane That tab is automatically selected if it is not currently visible 14 2 2 Button 1 Double Click When applied to the folder icon alongside a hierarchy category this will cause the display of that hier archy to be toggled When applied to a headline button 1 double click will show the diagram for the artifact to which the to do item applies in the editing pane and select the artifact on the diagram using an appropriate clarifier the artifact may be highlighted underlined with a wavy line or surrounded by a colored box as appro priate 14 2 3 Button 2 Actions There are no button 2 functions in the to do pane 14 2 4 Button 2 Double Click 133 The To Do Pane There are no button 2 functions in the to do pane 14 3 Presentation Selection At the top of the pane is a drop down selector controlling how the to do items are presented The to do items may be presented in six different ways This setting is not stored persistently i e it is on its default vallue when ArgoUML is started e By Priority This is the default setting The to do items are organized into three hierarchies by priority High Medium and Low The priority associated with the to do items generated by a partic ular critic may be altered through the Critique gt Browse Critics menu see Sec tion 10 9 4 Browse Critics e By Decision The to do items are organize
162. cconcconccnnncnnncnnnonircnicnnns 286 24 3 2 Built In Classes From java math 2 0 0 0 cece cece eeece teen eeeneeenes 286 24 3 3 Built In Classes From java net ocoooccnnconcconoconccnnncnnncnnronironicnnos 287 24 3 4 Built In Classes From java util 1 0 0 0 cece ceee ce eeceeeee teen teen es 287 24 4 Bult In Interfaces 2 jaccee cis e df calentita 287 24 5 Built Un Stereotypes id eae ek Gaeta 287 O NOS 291 A Supplementary Material for the Case Study oocoooconccnnccnnccnncnnocnnccnnconnconnccnnccnnconnconncos 298 Ast Mtro ducto cesta ricas sence sss setae ssa yeehadebieataas tr reir 298 A 2 Requirements Documents To be written oocooccoccncnoconcnoconcnnroncnoroncnnronannnos 298 A 2 1 Vision Document To be written oooococconocncnnonocncnconcnoconncnnnnonnnnnnos 298 A 2 2 Use Case Specifications To be written oocooccoccncnoconcnoroncnoronanorononns 298 A 2 3 Supplementary Requirements Specification To be written 298 XV ArgoUML Manual de Usuario B UME TeSOUrCES or efor itetectn Seed At Ea 299 Bel The UME specs To DE written evitando rotaciones 299 B 2 UML related papers To be written coooccnccnnccnocnnccnnccnnccnnconnccnnccnnconaconncnnnss 299 B 2 1 UML action specifications To be written ooccooccocnoconcnoroncnnroncnoronanns 299 B 3 UML related websites To be written ooooocococccnocnoconncnncnonnnncncnncnncnnncnnnnnnnos 299 C UML Conformi
163. ced state machine while the state ma chine that contains the submachine state is called the containing state machine The same state machine may be referenced more than once in the context of a single containing state machine In effect a sub machine state represents a call to a state machine subroutine with one or more entry and exit points The entry and exit points are specified by stub states SubmachineState is a child of State The submachine state is depicted as a normal state with the additional include declaration above and separated by a line from its internal transitions compartment The expression following the include reserved word is the name of the invoked submachine ArgoUML currently only supports a horizontal division of a concurrent composite state in regions The description of the details panels of a concurrent region is almost identical to that of a composite state see Section 20 4 Composite State and so is not duplicated here The only difference is one addi tional field Submachine Drop down selector Allows selecting the submachine included within this composite state Stub State A stub state only appears on a submachine state A submachine state represents the invocation of a state machine defined elsewhere In the general case an invoked state machine can be entered at any of its substates or through its default initial pseudostate Similarly it can be exited from any substate or as a result of the i
164. ci n de sistemas mas complejos que los posibles previamente El ltimo factor que ha propulsado OOA amp D ha sido su idoneidad para modelar interfaces graficos de usuario La popularidad de lenguajes graficos orientados a objeto y basados en objeto como Visual Basic y Java refleja la efectividad de este enfoque El Desarrollo de ArgoUML Durante la decada de 1980 un n mero de metodolog as de procesos OOA amp D y notaciones fueron de sarrolladas por diferentes equipos de investigaci n Se hizo patente que habia muchos temas comunes y durante la decada de 1990 un enfoque unificado para la notaci n OOA amp D fu desarrollado bajo el auspicio del Object Management Group http www omg org Este estandar se hizo conocido como el Unified Modeling Language UML y ahora es el lenguaje estandar para comunicar conceptos OO ArgoUML fu concebido como un entorno y herramienta para usar en el analisis y dise o0 de sistemas de software orientados a objeto En este sentido es similar a muchos de las herramientas CASE comer ciales que son vendidas como herramientas para modelar sistemas software ArgoUML tiene un n mero de distinciones muy importantes de muchas de esas herramientas 1 ArgoUML se enfoca en investigaci n en psicolog a cognitiva para proporcionar nuevas caracterist icas que incrementen la productividad soportando las necesidades cognitivas de dise adores y arqui tectos de software orientado a objeto 2 ArgoUML soporta estand
165. cidad representada Figure 4 3 Diagrama de casos de uso para un sistema de Cajero Autom tico mostrando multiplicidad La multiplicidad puede abarrotar un diagrama y a menudo no se muestra excepto donde es cr tico comprenderlo En el ejemplo de Cajero Automatico solo elegiriamos mostrar 1 3 contra el oficial del banco ya que todos los demas son obvios por el contexto 4 3 2 3 Jerarqu as de Casos de Uso En nuestro ejemplo de Cajero Automatico hasta ahora tememos solo tres casos de uso para describir el comportamiento del sistema Mientras los casos de uso siempre deber an describir un trozo significat ivo del comportamiento del sistema si son demasiado generales pueden ser dificiles de describir Podr amos por ejemplo definir el comportamiento del caso de uso Uso Cajero en terminos del com portamiento de los tres casos de uso mas simples Depositar Dinero Retirar Dinero y Consultas de Cuenta El caso de uso principal podr a ser especificado incluyendo el comportamiento de los casos de uso subsidiarios necesarios Similarmente el caso de uso Mantener Cajero podr a ser definido en terminos de dos casos de uso Mantener Equipamiento y Recargar Cajero En este caso los dos actores involucrados en el caso de uso principal est n realmente solo involucrados en uno u otro de los dos casos de uso subsidiarios y es to puede ser mostrado en el diagrama La descomposici n de un caso de uso en sub
166. ck on the entry will navigate to the composite state that contains this state All states are at least contained by the otherwise hidden top level state named top that is the root of the state containment hierarchy Entry Action 237 Statechart Diagram Artifact Reference Text box Shows the name of the action if any to be executed on entry to this state Note This field shows the name of the action while on the diagram the expression of the ac tion is shown Button 1 double click navigates to the selected entry button 2 gives a pop up menu with two entries e New Add a new Entry action of a certain kind This menu has the following submenus to select the kind of action Call Action Create Action Destroy Action Return Action Send Action Ter minate Action Uninterpreted Action e Delete From Model Delete the Entry Action Exit Action Text box Shows the action if any to be executed on exit from this state Button 1 click navigates to the selected action button 2 gives a pop up menu with two entries e New Add a new Exit action of a certain kind This menu has the following submenus to select the kind of action Call Action Create Action Destroy Action Return Action Send Action Ter minate Action Uninterpreted Action e Delete From Model Delete the Exit Action Do Activity Text box Shows the action 1f any to be executed while being in this state Button 1 click navigates to the s
167. ckage stucture for the latter 2 24 2 Built In Datatypes These are the built in atomic types You can change them if you wish However this is not good practice All these can be found in the java lang subpackage of the main model Caution You should be aware that these are Java datatypes They are not mandated by the UML standard These are the standard datatypes For their definition refer to the Java standard e boolean e byte e char 285 Built In DataTypes Classes Interfaces and Stereotypes e double e float int e long short e void Note void is not strictly speaking a type but the absence of type ArgoUML knows about void and allows it as an option where a datatype may be selected 24 3 Built In Classes These are the common classes corresponding to classes defined within the standard Java environment It 1s up to you if you wish to change them These are found in all four subpackages of the java subpackage For a definition of these classes see the Java language and library definitions 24 3 1 Built In Classes From java lang These are the classes within the java lang package e Boolean e Byte e Char e Double e Float e Integer e Long e Object Short e String 24 3 2 Built In Classes From java math These are the classes within the java math package 286 Built In DataTypes Classes Interfaces and Stereotypes e Big Decimal e Big Integer 24 3 3
168. ckages To be written To be written 6 15 2 1 Identifying Packages To be written 60 Design To be written 6 15 2 2 Datatypes and Stereotypes To be written To be written 6 15 3 Class Diagrams To be written To be written 6 15 3 1 Identifying classes To be written To be written 6 15 3 2 Identifying associations To be written To be written 6 15 3 3 Specifying Attributes and Operations To be written To be written 6 15 4 Sequence Diagrams To be written To be written 6 15 4 1 Identifying actions To be written To be written 6 15 5 Collaboration Diagrams To be written To be written 6 15 5 1 Identifying Messages To be written To be written 6 15 6 Statechart Diagrams To be written To be written 6 15 7 Activity Diagrams To be written To be written 6 15 8 The Deployment Diagram To be written To be written 6 15 9 The System Architecture To be written To be written 61 Chapter 7 Code Generation Reverse Engineering and Round Trip Engineering 7 1 Introduction We now have our design fully specified With the right simulator we could actually execute the design and see if it works ArgoUML does not provide such functionality but this functionality has been provided in alternative tools ArgoUML does allow you to generate code from the design in several different programming language
169. class diagram associated with a package the first created if there is more than one or will offer to create one for you if there is none See Figure 12 2 The dialog for adding a new class diagram Figure 12 2 The dialog for adding a new class diagram 12 2 3 Button 1 Motion Where the artifact being added is some form of connector its termination point is shown with button 1 up over the terminating artifact button 1 click may be used in the space between artifacts to create artic ulation points in the connector This is particularly useful where connectors must loopback on them selves Over graphical artifacts button 1 motion will move the artifact to a new position Graphical artifacts that are selected show handles at the corners or ends and these can be used for re sizing Some artifacts e g actor class show special handles called Selection Action Buttons see Sec tion 12 5 Selection Action Buttons at the sides top and bottom which can be dragged to form types of relationship with other artifacts Where the artifact is some form of connector between other items button 1 motion other than at a handle will cause a new handle to be created allowing the connector to be articulated at that point This only works when the connecting line is not straight angled Such new handles can be removed by mov ing them to the end of the connector There are various more detailed effects which are discussed under the
170. classifier role is des troyed e semantics from the superclass Classifier The value is a specification of the semantics of the classifier role e derived from the superclass ModelElement Values true meaning the classifier role is 258 Collaboration Diagram Artifact Reference redundant it can be formally derived from other elements or false meaning it cannot Note Derived classifier roles still have their value in analysis and design to introduce use ful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 21 2 2 Classifier Role Property Toolbar Go up Navigate up through the package structure New reception This creates a new reception navigating immediately to the properties tab for that reception New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected classifier role navig ating immediately to the properties tab for that stereotype Delete This deletes the classifier role from the model Warning This is a deletion from the model not just the diagram To delete an classifier role from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 21 2 3 Property Fields For Classifier Role Name Text box The name of
171. click en la flecha hacia abajo se muestra una vista en ar bol de la jerarquia de la carpeta permitiendote navegar rapidamente en la jerarquia y al mismo tiempo determinar rapidamente donde nos encontramos posicionados en ella e El icono de Subir un Nivel Haciendo click en este icono nos desplazaremos a la carpeta padre de la carpeta actual e El icono de Principal Haciendo click en este icono nos desplazaremos a nuestro directorio home e El icono Nueva Carpeta Haciendo click en este icono crearemos una nueva carpeta llamada Carpeta nueva bajo la carpeta actual Despues de que la carpeta est creada puedes seleccionarla y hacer click en su nombre para cambiarle el nombre a tu elecci n e El icono de Presentaci n de Carpetas 23 OOA amp D basada en UML De acuerdo ahora navegamos al directorio donde queremos guardar nuestro proyecto ArgoUML rellena el Nombre de Archivo con un nombre apropiado como PrimerProyecto y haz click en el boton Guardar Ahora tienes un poryecto activo llamado PrimerProyecto conectado al archivo Primer Proyecto zargo 3 4 3 Salida 3 4 3 1 Cargando y Guardando 3 4 3 1 1 Guardar archivos XMI en ArgoUML ArgoUML guarda la informaci n de diagrama en un archivo PGML con extensi n pgm1 la inform aci n del modelo en un archivo XMI con extensi n xmi y la informaci n sobre el proyecto en un archivo con extensi n argo Mira Section 3 4 3 2 2 Precision Graphics Markup La
172. cnnccnnccnnrcnicnnns 150 ISAT s Containment 33 05 seccsasb feed odes sade seaweed E 150 15 17 1 Remove Circular Composition cece eeecceeceeece teen esse teen es 150 15 17 2 Duplicate Parameter Name oooooccnnccnnccnnconnconnconaconocnnccnnroninnnn 150 15 17 3 Two Aggregate Ends Roles in Binary Association 150 15 17 4 Aggregate End Role in 3 way or More Association 151 SAT Wrap Data Lype ua a Beas 151 3 Model Reference oil asidero shovaadsves OEE PoE PE OSTES 152 16 Top Level Artifact Reference ooooccoccncccnccnnconnconnconnccnnccnnconnconncnnnrnnnrnnrcnaronoss 153 16 1 Introduction cese sientes rola pets E e las Deterioro tdi 153 16 2 The Model oia 153 16 2 1 Model Details Tabs ciiciososion isos rotas conos ns seat siesena s prod 153 16 2 2 Model Property Toolbar oococccoccnnconnconnconnconoconacnnncnnncnoronicnno 154 16 2 3 Property Fields For The Model ooocococnnoccnccnnconoconicnnacnnncnnnonoso 154 16 3 Datatype a O 156 16 3 1 Datatype Details Tabs ooooooconoccnnconoconoconcconconoconconaconacnnncnnss 156 16 3 2 Datatype Property Toolbar coooccnnccncconoconccnnconoconncnnncnnncnanonoso 157 16 3 3 Property Fields For Datatype oocoooconoconoconocnnconoconcnnncnnncnononoso 158 16 4 Enumeration ves ases vers oR E snes geehy tee ge5 94 woe dba ENE AINEET 160 16 4 1 Enumeration Details Tabs 2 0 0 eee cee cc eeceeeee nese teen teenies 161 16 4
173. cocooccoconococonococonococononoconococonanoconanoronanoronanonos 66 8 2 General Mouse Behavior in ArgoUML oooccoccnnccnncnnccnnconnconnccnnccnnconnconnnos 66 vi ArgoUML Manual de Usuario 8 2 1 Mouse Button Terminology coooccocccccnnccnnccnnconnconnccnnconnconaconiconass 66 8 2 2 Button Click cli E AAA NEAS ean 67 8 2 3 Button 1 Double Click sfna ara ann r E R A 68 8 2 4 Button L MONON srie an E E pikes sees eames EE a aa 68 8 2 5 Shift and Ctrl modifiers with Button 1 oo eee eee ee eeee 68 8 2 6 Alt with Button 1 Panning 0 00 0 cece eee cence eeee nner eeeee es 68 8 2 7 Ctrl with Button 1 Constrained Drag ooocoocccnoccnnccnnccnncnnnconnconicinnss 68 8 2 8 Button 2 ACH OMS se sss cssus assem ne sesaoasesvbasnggavasbageedesess EEEE SRo EEE 69 8 2 9 Button 2 Double Click ooooooocccccnncccnccnnconnccnconnconnconnccnnconnconncos 69 8 210 Button 2 Motion wiseso tienne sn a dante a Ee TEES 69 8 3 General Information About Panes oocococcccnnccnnnccnnnccnnnncononccnnnccnnnnccnnccnnnn 69 8 3 L Re SIZIMO Pane S on a E E Gees EEEE S ES 69 8 4 The Status Dar acti e Aria data 69 9 Th Loo Dar 333 cael ik Ses Gea cie EE N 70 SA AA nye INE EAEE E EEE A NEEE E OEST 70 9 2 Edit Opera ONS Ad E eE eas 70 DI VIEW Operations eroii esenee oeae E a beerbesaeiniesestondadeeeatesse8G 70 9 4 Create Operations sire repo ernes EEE EE KES EEE EEEE KET EEEE OREN EERE 71 10 The Menu Dar 3s 25 ususvores sesar ti
174. cos 308 G The CRC Card Methodology s sc3 vss scs anae See Shee ESE dra vente 309 Gide The Card aenieei illo ricino 309 G2 The Group sitiar ai io iii 310 G3 The Session coc a cooressioderke wens 310 G4 The Process sien reka Sa Sactes ash oe W Sostedssoyes adasdive osbstiote dante svemeaggettatwess 310 IN OX nos ons cee cdcgs have breeds a t 311 xvi Prefacio El dise o0 de software es una tarea cognitiva dificil Los dise adores deben construir manualmente dise 0s pero la dificultad principal es la toma de decisiones en lugar de la entrada de datos Si los dise adores mejoran sus capacidades de toma de decisiones ello resultar a en mejores dise os Las herramientas CASE actuales proporcionan automatizaci n e interfaces gr ficos de usuario que re ducen el trabajo manual de construir un dise o y transformar un dise 0 en codigo Ayudan a los dise adores en la toma de decisiones principalmente proporcionando visualizaci n de los diagramas de dise 0 y comprobaciones sintacticas simples Adenas muchas herramientas CASE proporcionan be neficios sustanciales en el area de control de versiones y mecanismos de dise o concurrente Un area de soporte de dise o que no ha sido bien soportada es el analisis de decisiones de dise o Las herramientas CASE actuales son utiles en que proporcionan una GUI Graphic User Interface Inter faz Grafica de Usuario que permite a los dise adores acceder a todas las caracteristicas p
175. cs SVG Un formato de gr ficos vectoriales estandar del World Wide Web Consortium W3C ht 24 OOA amp D basada en UML tp www w3 org TR SVG http www w3 org TR S VG Est soportado por los navegadores modernos pero tambien puedes conseguir un plugin para nave gadores antiguos en adobe com http www adobe com 3 4 3 2 6 Guardando Diagramas como SVG 1 Seleciona svg como el tipo de archivo 2 Teclea el nombre del archivo que quieras con la etiqueta svg al final Ejemplo midia gramauml svg Et viola SVG Pruebalo y juega con el zoom un poco No son perfectos as que si conoces algo sobre representar bonitos SVG haznoslo saber La mayor a de los navegadores modernos soportan SVG Si el tuyo no lo hace prueba Firefox ht tp www mozilla com firefox o consigue un plugin para tu navegador actual en adobe com ht tp www adobe com Note No tendras barras de desplazamiento para tu SVG a menos que este embebido en HTML Buena suerte y haznos saber que encuentras 3 4 3 3 XMI ArgoUML soporta archivos XMI 1 0 1 1 y 1 2 que contengan modelos UML 1 3 y UML 1 4 Para una mejor compatibilidad con ArgoUML exporta tus modelos usando UML 1 4 y XMI 1 1 o 1 2 Asegurate de desactivar cualquier extensi n propietaria tal como datos de diagrama de Poseidon Con versiones UML anteriores a UML 2 0 no es posible salvar informaci n de diagrama asi que no ser n transferidos diagramas Existe ta
176. ct and wish to load it automatically when you start up ArgoUML e Strip non standard diagrams from XMI file during import clear by de fault Checking this item will tell ArgoUML to ignore the Diagram elements when importing XMI files You only need to use this setting if ArgoUML gives an error while importing your XMI file saying that it encountered unrecognized elements named Diagram Some versions of Poseidon are known to create this type of file by default although there s usually an export option to force them to create standard XMI files e UML Profile file org argouml model mdr mof default uml14 xmi by default This is a read only field which shows the current profile being used by ArgoUML If you specified an alternate profile at startup time or a plugin module installed a different profile it will display here In the future this will be a settable field that allows you to select different profiles to match different modeling environments Java C AndroMDA etc 82 The Menu bar 10 4 5 2 Environment Tab Selecting the Environment tab button 1 click on the tab lists several environmental items Note that none of the paths can be altered these are just a matter of record Figure 10 14 The dialog for Settings Environment e Default Graphics Format Here you can select the same graphics formats as in the menu Sec tion 10 3 11 Export Graphics The chosen format is selected by def
177. d ant it can be formally derived from other elements or false meaning it cannot Note This indicates any element with this stereotype has the derived tag set accord ingly Caution Tagged values for a stereotype are rather different to those for elements in the UML core architecture in that they apply to all artifacts to which the stereotype is applied not just the stereotype itself 16 5 2 Stereotype Property Toolbar Go up Navigate up through the package structure of the model Add stereotype This creates a new stereotype see Section 16 5 Stereotype within the model which appears on no diagram navigating immediately to the properties tab for that stereotype 164 Top Level Artifact Reference Delete This deletes the stereotype from the model 16 5 3 Property Fields For Stereotype Name Text box The name of the stereotype There is no convention for naming stereotypes beyond start ing them with a lower case letter Even the standard UML stereotypes vary between all lower case e g metamodel bumpy caps e g systemModel and space separated e g object model Note ArgoUML does not enforce any naming convention for stereotypes Base Class Drop down selector Any stereotype must be derived from one of the metaclasses in the UML metamodel Abstraction Actor Association AssociationEnd Attribute Beha vioralFeature CallEvent Class Classifier Collaboration Comment Com ponent Co
178. d Use button 1 click to uncheck the Navigability box Note This may seem counter intuitive but in fact associations by default are navigable in both directions when no arrows are shown This process is turning off navigation at one end rather than turning it on at the other You will see it is possible to give an association end a name in its property tab This name will appear at that end of the association and can be used to indicate the role being played by an actor or use case in an association For example a time management system for a business may have use cases for completing time sheets and for signing off time sheets An employee actor may be involved in both one as an employee but the other in a role as manager 40 Captura de Requerimientos 4 4 3 2 Setting Multiplicity There are two ways of setting multiplicity at the end of an association 1 Button 2 click over the end of an association will cause a context sensitive pop up menu to appear with a sub menu labeled Multiplicity This allows you to select from 1 the default 0 1 0 and1 2 Bring up the property sheet for the association end as described for setting navigation see the second option in Section 4 4 3 1 Setting Navigation A drop down menu gives a range of multiplicity op tions that may be selected The second of these two approaches has a wider range of options although ArgoUML does not cur rently allow the user to set
179. d into 17 hierarchies by design issue Uncategor ized Class Selection Behavior Naming Storage Inheritance Containment Planned Extensions State Machines Design Patterns Relationships In stantiation Modularity Expected Usage Methods Code Generation and Ste reotypes The details of the critics in each category are discussed in Section 10 9 2 Design Is sues e By Goal ArgoUML has a concept that critics may be grouped according to the user goals they af fect This presentation groups the to do items into hierarchies by goal Caution In the current release of ArgoUML there is only one goal Unspecified and all to do items will appear under this heading By Offender The to do items are organized into a hierarchy according to the artifact that caused the problem Todo items that were manually created with the New ToDo item button i e not by a critic are not listed here e By Poster The to do items are organized into a hierarchy according to which critic generated the to do item The class name of the critic is listed instead of just its headline name since the former is guaranteed to be a unique name By Knowledge Type ArgoUML has the concept that a critic reflects a deficiency in a category of knowledge This presentation option groups the critics according to their knowledge category De signer s Correctness Completeness Consistency Syntax Semantics Optim ization Presentational Organizational
180. d values UML Attributes are mapped to class member variables pointer true the type of the member variable will be a pointer to the attribute type For example if you have the UML Attribute name std string with the pointer tagged value set to true the generated member variable would be std string name false default no pointer modifier is applied reference true the type of the member variable will be a reference to the attribute type 302 The C Module false default no reference modifier is applied usage header will lead for class types to a pre declaration in the header and the include of the re mote class header in the header of the generated class MultiplicityType list slist vector map stack stringmap will define a mul tiplicity as the corresponding STL container if the Multiplicity range of the attribute is vari able for fixed size ranges this setting is ignored set private protected public creates a simple function to set the attribute by a function call by reference is used for class types else call by value place the function in the given visibility area get private protected public as for set D 1 3 Parameters D 1 3 1 Variable passing semantics If a Parameter for an Operation is marked as out or inout the variable will be passed by refer ence default or pointer needs tagged value pointer see above otherwise by
181. dard tab See Section 13 4 Documentation Tab Source Standard tab Stereotype Standard tab The UML metamodel has the following stereotypes defined by default for a Classifier which also apply to an Enumeration e metaclass from the superclass Classifier e powertype from the superclass Classifier e process from the superclass Classifier e thread from the superclass Classifier e utility from the superclass Classifier Tagged Values Standard tab In the UML metamodel Enumeration has no standard tagged values defined 16 4 2 Enumeration Property Toolbar Go up Navigate up through the composition structure New datatype This creates a new datatype see Section 18 5 Class within the same package as the current enu meration New enumeration literal This creates a new enumeration literal within the enumeration navigating immediately to the prop erties tab for that literal New Operation This creates a new operation within the enumeration navigating immediately to the properties tab for that operation New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype within the same package as the enu 161 Top Level Artifact Reference meration navigating immediately to the properties tab for that stereotype Delete from Model This deletes the datatype from the model 16 4 3 Property Fields For Enumeration Name Text box The name of the
182. de Problemas xvil Specializations of Actor 172 of Package 191 of Use Case 175 Standard Graphical Markup Language 295 State 295 State Diagram 295 Statechart Diagram 295 Statechart Diagram Hierarchical 293 Stereotype 163 295 in Use Case Diagrams 42 of Actor 171 of Association 211 of Association End 214 of Class 194 of Datatype 158 of Dependency 218 of Extend Relationship 183 of Extension Point 177 of Generalization 180 of Include Relationship 186 of Model 155 of Operation 202 of Package 190 of Parameter 205 of Signal 208 of Use Case 174 Stereotype Base Class 165 Stereotype Details Tabs 164 Stereotype Modifiers 165 Stereotype Name 165 Stereotype Namespace 165 Stereotype Property Fields 165 Stereotype Property Toolbar 164 Stereotyping 295 Supplementary Requirement Specification 37 295 Suppliers of Dependency 218 SVG 13 295 System Boundary Box in Use Case Diagram 43 System Sequence Diagram 296 System Statechart Diagram 296 T Tagged Values of Association 210 of Association End 213 of Attribute 196 of Class 192 of Datatype 156 of Enumeration 161 of Operation 200 of Parameter 204 of Signal 207 To Do List 296 Toolbars 19 Tools Menu 20 Transition 296 Type of Association End 214 of Attribute 198 of Parameter 206 U 316 Index UML 296 Use Case 38 172 296 Use Case Details Tabs 172 Use Case Diagram 169 296 Use Ca
183. de uso principal en un gran n mero de posiciones y bajo un amplio rango de circunstancias Sin embargo la falta de alguna restricci n hace la generalizaci n muy dificil de especificar con preci si n En general usa una relaci n de extensi n en su lugar La Especificaci n de Casos de Uso Cada caso de uso debe ser documentado para explicar en detalle el comportamiento que est especific ando Este documento es conocido por diferentes nombres en diferentes procesos especificaci n de caso de uso escenario de caso de uso o incluso confusamente solo caso de uso Un caso de uso tipico incluir las siguientes secciones Nombre El nombre del caso de uso al que esto se refiere Objetivo Un resumen de una o dos lineas de que realiza este caso de uso por sus actores e Actores Los actores involucrados en este caso de uso y cualquier contexto con respecto a su parti cipaci n Note Esto no deber a ser una descripci n del actor Eso deber a estar asociado con el actor en el diagrama de casos de uso Pre condici n Ser a mejor llamarlas pre asumciones pero el termino usado en todos sitios es pre condiciones Es una declaraci n de cualesquiera asumciones de simplificaci n que podemos hacer al comienzo del caso de uso En el ejempli del Cajero Automatico podemos hacer la asumci n para el caso de uso de Mantener Equipamiento que un ingeniero est siempre disponible y no necesitamos preocuparnos sobre el
184. dered part of the license Open Publication works are available in source format via the Open Publication home page at ht tp works opencontent org http works opencontent org Open Publication authors who want to include their own license on Open Publication works may do so as long as their terms are not more restrictive than the Open Publication license If you have questions about the Open Publication License please contact David Wiley mailto dw2 Eopencontent org and or the Open Publication Authors List at opal opencontent org mailto opal opencontent org via email To subscribe to the Open Publication Authors List Send E mail to opal request opencontent org with the word subscribe in the body To post to the Open Publication Authors List Send E mail to opal opencontent org or simply reply to a previous post To unsubscribe from the Open Publication Authors List Send E mail to opal request opencontent org with the word unsubscribe in the body 308 Appendix G The CRC Card Methodology A CRC card is ostensibly an index card that is used to represent classes their responsibilities and the in teractions between them The term CRC card is also used to refer to a methodology for object oriented modeling based on their use Kent Beck and Ward Cunningham introduced CRC cards in a paper A Laboratory for Teaching Object Oriented Thinking that was presented at the OOPSLA Object Oriented
185. descriptions of the various tools see Section 12 3 The tool bar 12 2 4 Shift and Ctrl modifiers with Button 1 Where multiple selections are to be made the CTRL key is used with button 1 to add unselected arti facts to the current selection Where an artifact is already selected it is removed from the current selec tion Clicking Button while the SHIFT key is pressed invokes the broom tool which causes the selected ar tifacts and any others swept up with them to be moved with the broom tool see Section 12 3 1 Layout Tools 12 2 5 Alt with Button 1 motion Button 1 down anywhere in the diagram while the ALT key is pressed allows to scroll the canvas in all directions with button 1 motion 12 2 6 Button 2 Actions When used over artifacts in the the editing pane this will display a context dependent pop up menu 105 The Editing Pane Menu entries are highlighted but not selected and sub menus exposed by subsequent mouse motion without any buttons Menu entry selection is with button 1 or button 2 See Section 12 9 Pop Up Menus for details of the specific pop up menus In case multiple elements are selected the pop up menu only appears if all the items are of the same kind In this case the functions apply to all selected elements 12 2 7 Button 2 Double Click This has no effect other than that of button 2 single click 12 2 8 Button 2 Motion This is used to select items i
186. dia gram but keep it within the model use the main menu Remove From Diagram or press the Delete key 23 2 3 Property Fields For Node Name Text box The name of the node The name of a node has a leading capital letter with words separ ated by bumpy caps Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Node is a type of classifier and so it has the default stereotypes of a classifier as defined in the UML standard ArgoUML provides the standard stereotypes for a classifier metaclass powertype process threadand utility Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Allows altering the namespace for the node This is the package hierarchy 275 Deployment Diagram Artifact Reference Modifiers Check box with entries abstract leaf and root e abstract is used to declare that this node cannot be instantiated but must always be special ized The name of an abstract node is displayed in italics on the diagram e leaf indicates that this node cannot be further specialized e root indicates the node can have no generalization Generalizations Text area Lists any node that generalizes this node Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized node
187. dira que hacer y cuando hacerlo pero como hacerlo a me nudo ser dejado a la Referencia de la Interfaz de Usuario No es necesario en este punto leerse toda la Referencia pero deber as echarle un vistazo hasta familiarizarte con como encontrar cosas en ella To do intento ser hecho para dirigirte a la parte apropiada de la Referencia en donde se aplican esos pun tos en el tutorial Figure 3 6 Ventana inicial de ArgoUML muestra la ventana principal de ArgoUML como aparece cuando es entra por primera vez en ArgoUML Figure 3 6 Ventana inicial de ArgoUML Agarra la barra divisoria vertical y muevela atras y adelante Agarra la barra divisoria horizontal y muevela arriba y abajo Juega un poco por ah con las peque as flechas a la izquierda o arriba de las barras divisorias Mira Section 8 3 General Information About Panes 3 4 2 1 El Panel Explorador 17 OOA amp D basada en UML En este momento deber as tomarte tiempo para leer Chapter 11 The Explorer No hay mucho que pue das hacer en este punto con el Panel Explorador ya que no hay nada in el salvo la raiz del arbol actualmente untitledModel y dos diagramas vac os Sin embargo el Panel Explorador es funda mental para casi todo lo que haces y volveremos atras a l una y otra vez en lo sucesivo Hay un control de expansi n y contracci n delante del s mbolo del paquete para untitledModel en el Panel Explorador y el s mbolo de paquete para Me
188. dium en el Panel de Tareas Pendientes Haz click en esos controles y observa que esos paneles son tres widgets que se comportan de forma muy parecida a como se esperar a que hicieran El control de expansi n o contracci n es un signo de mas menos o un pomo dirigido a la derecha o abajo dependiendo del look and feel que has escogido como apariencia En este punto deber as probar las varias opciones disponibles para un look and feel apariencia Usaste el editor que establece el look and feel cuando estabas seleccionando el idioma sin embargo solo lo viste en Ruso Si miras la versi n Espa ola Inglesa en la imagen Section 10 4 5 4 Appearance Tab veras que la combobox de la zona mas alta es para seleccionar el look and feel Cuando el panel se abre por primera vez la caja contiene el valor actual Selecciona otra sal de ArgoUML y reinicialo Seleciona alternativamente Diagrama de clase 1 y Diagrama Use Case 1 observando que el panel de de talle cambia siguiendo los objetos seleccionados en el Explorador El panel de detalle est descrito en el Capitulo 12 No es necesario leer el capitulo 12 en este punto pero tampoco te hara da o 3 4 2 2 El Panel de Edici n Note e Tar a de Lectura e Pasa a traves de un par de cambios e A ade algunas cosas Elimina algunas cosas e Redimensiona cosas e Selecciona cosas con arrastrar y soltar e Seleciona cosas con click y ctrl click e Edita nombres integrados e E
189. do con la publicaci n 0 14 se realizaron cambios por Linus Tolke y Michiel van der Wulp Estos cambios fueron mayoritariamente adaptar el manual a las nuevas funciones y apariencia de la version 0 14 de ArgoUML y la introducci n del in dice Los usuarios y desarrolladores que han contribuido proporcionando ayuda valiosa como revi siones comentarios y observaciones mientras leen y usan este manual son demasiados para ser nombra dos ArgoUML esta disponible gratuitamente y puede ser usado en entornos comerciales Para los terminos de uso mira el acuerdo de licencia presentado cuando tu descargas ArgoUML Estamos proporcionando el codigo fuente de ArgoUML para que puedas revisarlo adecuarlo a tus necesidades y mejorarlo Pas ado el tiempo esperamos que ArgoUML evolucione en una poderosa y util herramienta que todos puedan usar Este Manual de Usuario esta orientado al dise ador quien desea hacer uso de ArgoUML El manual es ta escrito asumiendo familiaridad con UML pero eventualmente puede ayudar a aquellos nuevos en UML El manual esta escrito en DocBook XML y esta disponible como HTML y PDF El proyecto ArgoUML da la bienvenida a aquellos que quieren estar mas involucrados Mira en project website http argouml tigris org para encontrar mas informaci n Dinos que piensas sobre este Manual de Usuario Tus comentarios nos ayudaran a mejorar cosas Mira Section 1 3 3 Retroalimentaci n por el Usuario xviii Ch
190. dostate which is used to split an incoming transition into multiple outgoing transition segments with different guard conditions Hence a Choice allows a dy namic choice of outgoing transitions The chosen transition is that whose guard is true at the time of the transition if more than one is true one is selected at random A predefined guard denoted else may be defined for at most one outgoing transition This transition is enabled if all the guards labeling the other transitions are false Note This sort of pseudostate was formerly called a Branch by ArgoUML A choice is represented on the diagram as a small solid white by default circle reminiscent of a small state icon 20 16 Fork Fork is a pseudostate see Section 20 11 Pseudostate which splits a transition into two or more con current transitions Caution The outgoing transitions should not have guards However ArgoUML will not enforce this A fork is represented on the diagram as a solid black by default horizontal bar Tip This bar can be made vertical by selecting the fork and dragging with button 1 one of its corners 253 Statechart Diagram Artifact Reference 20 17 Join Join is a pseudostate see Section 20 11 Pseudostate which joins two or more concurrent transitions into a single transition Caution The incoming transitions should not have guards However ArgoUML will not enforce this A join is represented on th
191. dth of the shadow if any for 2D artifacts It is not present for line artifacts Figure 13 9 The Custom Fill Line Color dialog box Figure 13 10 The Custom Fill Line Color dialog box Figure 13 11 The Custom Fill Line Color dialog box Source Tab This tab shows the source code that will be generated for this artifact in the selected language ArgoUML generates the code e g for classes and interfaces The code shown here may be saved in the indicated files with the aid of the functions in the Generation menu Figure 13 12 The Source Tab of a class Any code you add will be lost that is not the intention of ArgoUML use an IDE instead 127 The Details Pane The dropdown at the right allows selection of the output file This function is not very useful for lan guages that generate all code for a class within one file but serves its purpose for e g C where a h and cpp file are generated See the figure below Figure 13 13 A C example 13 7 Constraints Tab Constraints are one of the extension mechanisms provided for UML ArgoUML is equipped with a powerful constraint editor based on the Object Constraint Language OCL defined in the UML 1 4 standard Caution The OCL editor implementation for ArgoUML V0 20 doesn t support OCL constraints for elements other than Classes and Features This is something of a general restriction of OCL Although the UML specification claims that there may be a constrain
192. e 186 Include Relationship Namespace 186 Include Relationship Stereotype 186 Included Use Case of Include Relationship 186 Initial Value of Attribute 198 of Parameter 206 Iteration 9 313 Index Iterative Design Process 293 J Jason Robbins 2 Java 293 Jerarqu a de Casos de Uso 33 K Kind of Parameter 206 L Limitaciones en el documento de Visi n 31 Literals of Datatype 160 of Enumeration 163 Location of Extension Point 177 M Mailing lists 2 2 Mealy Machine 293 Menu Bar 19 Method of a Class 293 of an Object 293 Model Details Tabs 153 Model Modifiers 155 Model Name 154 Model Namespace 155 Model Owned Elements 156 Model Stereotype 155 Model Visibility 155 Model The 153 Modifiers of Actor 171 of Association End 215 of Class 194 of Datatype 158 of Enumeration 162 of Model 155 of Operation 202 of Package 190 of Stereotype 165 of Use Case 174 Moore Machine 293 Mouse Behavior in the Explorer 99 Multiplicidad en un Diagrama de Casos de Uso 32 Multiplicity of Association End 215 of Attribute 198 Setting 41 N Name of Actor 171 of Association 211 of Association End 214 of Attribute 197 of Class 193 of Datatype 158 of Dependency 217 of Diagrams 168 of Enumeration 162 of Extend Relationship 183 of Extension Point 177 of Generalization 180 of Include Relationship 186 of Model 154 of Operatio
193. e UML standard provides for such decoration to improve the readability of diagrams Tip These drawing tools provide a useful way to partially support some of the UML features such as general purpose notes that are missing from the current release of ArgoUML Eight tools are provided all grouped into one drop down widget See Figure 12 3 The drawing tools selector Button 1 click on the diagram will place an instance of the graphical item of the same size as the last one placed The size can be controlled by button 1 motion during placement One side or end of the element will be at button 1 down the other side or end at button up In general after they are placed on the diagram graphical elements can be dragged with the Select tool and button 1 and re sized by button motion on the handles after they have been selected Figure 12 3 The drawing tools selector e Rectangle Provides a rectangle e Rounded Rectangle Provides a rectangle with rounded corners There is no control over the de gree of rounding e Circle Provides a circle e Line Provides a line 107 The Editing Pane 12 3 4 Text Provides a text box The text is entered by selecting the box and typing Text is centered hori zontally and after typing the box will shrink to the size of the text However it can be re sized by dragging on the corners Polygon Provides a polygon The points of the polygon are selected by button 1 click and the
194. e Up Only available where there are two or more operations and the operation selected is not at the top It is moved up one e Move Down Only available where there are two or more operations listed and the operation se lected is not at the bottom It is moved down one See Section 18 7 Operation for details of operations Caution ArgoUML treats all operations as equivalent Any operations created here will use the same mechanism as operations for classes Remember that operations on datatypes must have no side effects they are read only This means the query modifier must be checked for all operations Literals Text area Lists all the enumeration literals defined for this datatype Button 1 double click navig ates to the selected literal button 2 click brings up a pop up menu with two entries e Move Up Only available where there are two or more literals and the literal selected is not at the top It is moved up one e Move Down Only available where there are two or more literal not at the bottom It is moved down one Caution s listed and the literal selected is ArgoUML does not actually have a separate concept of a literal The navigations listed above will all navigate to a property sheet equal to an attribute of a class see Sec tion 18 6 Attribute When defining a literal all that matters is its name Other parts of the attribute property sheet should be ignored 16 4 Enumeration
195. e cases there are no generalization handles on actors so generalizations must be created using the toolbar icon It is possible to name generalization relationships using the property tab but this is rarely done If a name is provided it will be displayed on the use case diagram Stereotypes UML has the concept of stereotyping as a way of extending the basic notation It may prove useful for example to model a problem at both the business level and the engineering level For both of these we will need use cases but the use cases at the business level hold a different sort of information to those at the engineering level Very likely they use different language and notation in their underlying use case specifications Stereotypes are used to label UML artifacts such as use cases to indicate that they belong to a certain category Such labels are shown in guillemots above the name of the artifact on the diagram The UML standard defines a number of standard stereotypes and the user may define more stereotypes of his own You will see that ArgoUML has a drop down selector Stereotype on every property tab This is populated with the standard stereotypes to which you may add your own user defined ones The details of stereotyping are beyond the scope of this tutorial The reference manual see Section 16 5 Stereotype documents the support provided in ArgoUML Warning ArgoUML is missing a few of the standard UML stereotypes
196. e codigo Tambien miraremos a como el Diagrama de Casos de Uso UML y la Especificaci n de Casos de Uso son herramientas invalorables para un programa de prueba 3 3 Por que ArgoUML es Diferente En la introducci n listamos las cuatro aspectos clave que hacen a ArgoUML diferente 1 hace uso de ideas de psicologia cognitiva 11 est basado en estandares abiertos 111 es 1009 Java puro y 1v es un proyecto de codigo abierto 11 OOA amp D basada en UML 3 3 1 Psicolog a Cognitiva 3 3 1 1 Teor a ArgoUML est particularmente inspirado en tres teorias dentro de la psicolog a cognitiva i re flexi n en acci n 11 dise 0 oportunista 111 y comprensi n y resoluci n de problemas e Reflexi n en Acci n Esta teor a observa que los dise adores de sistemas complejos no conciven un dise o totalmete formado En su lugar deben construir un dise o parcial evaluarlo reflexionar en el y revisarlo hasta que est n listos para extenderlo mas all Como los desrrolladores trabajan directamete sobre el dise 0 sus modelos mentales de la situaci n del problema mejoran por lo tanto mejoran sus dise os e Dise o Oportunista Una teor a dentro de la psicolog a cognitiva sugiere que aunque los dise adores planean y de scriben su trabajo de una forma jerarquica ordenada en realidad escogen tareas sucesivas basados en el criterio de costo cognitivo Explicado simplemente los dise adores no sigue incluso sus
197. e compartment of the class Its syntax is as follows visibility attributeName type initialValue visibility is or corresponding to public protected private or package visibility re spectively attributeName is the actual name of the attribute being declared type is the type UML datatype class or interface declared for the attribute initialValue is any initial value to be given to the attribute when an instance of the class is created This may be overridden by any constructor operation In addition any attribute declared static will have its whole entry underlined on the diagram 18 6 1 Attribute Details Tabs The details tabs that are active for attributes are as follows ToDoltem Standard tab Properties See Section 18 6 2 Attribute Property Toolbar and Section 18 6 3 Property Fields For Attrib ute below Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab This contains a declaration for the attribute Constraints Standard tab There are no standard constraints defined for Attribute within the UML metamod el Tagged Values Standard tab In the UML metamodel Attribute has the following standard tagged values defined e transient e volatile This is an ArgoUML extension to the UML 1 4 standard to indicate that this attrib ute is realized in some volatile form for example it will be a memory mapped control register Note The UM
198. e dependency and opens its property tab Supplier Dependencies Text area Lists the supplying ends of the relationship i e the end supplying what is needed by the other end 194 Class Diagram Artifact Reference Button 1 double click navigates to the dependency and opens its property tab Generalizations Text area Lists any class that generalizes this class Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized class i e for which this class is a generalization Button 1 double click navigates to the generalization and opens its property tab Attributes Text area Lists all the attributes see Section 18 6 Attribute defined for this class Button 1 double click navigates to the selected attribute Button 2 gives a pop up menu with two entries which allow reordering the attributes e Move Up Only available where there are two or more attributes listed and the attribute selected is not at the top It moves the attribute up one position e Move Down Only available where there are two or more attributes listed and the attribute se lected is not at the bottom It moves the attribute down one position Association Ends Text box Lists any association ends see Section 18 11 Association of associations connected to this class Button 1 double click navigates to the selected entry Operations Text area Lists
199. e derived from the superclass ModelElement Values true meaning the class is redund ant it can be formally derived from other elements or false meaning it cannot Note Derived classes still have their value in analysis to introduce useful names or con cepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for a Classifier 18 5 2 Class Property Toolbar 192 Class Diagram Artifact Reference Go up Navigate up through the package structure New attribute This creates a new attribute see Section 18 6 Attribute within the class navigating immediately to the properties tab for that attribute New operation This creates a new operation see Section 18 7 Operation within the class navigating immedi ately to the properties tab for that operation New reception This creates a new reception navigating immediately to the properties tab for that reception New inner class This creates a new inner class which appears on no diagram within the class This belongs to the class and is restricted to the namespace of the class It exactly models the Java concept of inner class As an inner class it needs no attributes or operations since it shares those of its owner Note Inner class is not a separate concept in U
200. e diagram Also the proper ties panel for a qualifier equals that of a regular attribute 264 Collaboration Diagram Artifact Reference New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected association end role navigating immediately to the properties tab for that stereotype Delete This deletes the selected association end from the model Note This button is downlighted for binary association roles since an association needs at least two ends Only for N ary associations this button is accessable and deletes just one end from the association 21 4 3 Property Fields For Association End Role Name Text box The name of the association end role which provides a role name for this end of the asso ciation role This role name can be used for navigation and in an implementation context provides a name by which the source end of an association role can reference the target end Note ArgoUML does not enforce any naming convention for association end roles Stereotype Drop down selector Association end role is provided by default with the UML standard stereotypes for AssociationEndRole association global local parameter self Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Base Text field that shows the name of the corresponding association end Button
201. e diagram as a solid black by default horizontal bar Tip This bar can be made vertical by selecting the join and dragging with button 1 one of its corners 20 18 Shallow History Shallow History is a pseudostate see Section 20 11 Pseudostate that can remember the last state of its container that was active The history pseudostate points to its default state with a transition arrow just like the initial pseudostate does This transition points to the substate that will become active when there is no history When the container composite state has been active before i e when there is his tory the substate that was active when the container state was exited becomes active again When placed within a multi level hierarchy of composite states the shallow history only remembers the history for states that have the same container as the history pseudostate It does not restore substates deeper in the hierarchy then the history pseudostate itself A shallow history is represented on the diagram as a circle containing the letter H 20 19 Deep History Deep History is a pseudostate see Section 20 11 Pseudostate that can remember the last state of its container that was active The history pseudostate points to its default state with a transition arrow just like the initial pseudostate does This transition points to the substate that will become active when there is no history When the container composite state has been ac
202. e diagram with all possible arti facts displayed Figure 18 2 Possible artifacts on a package diagram 18 1 1 Limitations Concerning Class Diagrams in ArgoUML The current implementation does not allow datatypes to be shown on class diagrams A variant of the class diagram within the UML standard is the object diagram There is currently no sup port for objects or links within ArgoUML Class diagrams Instead the ArgoUML deployment diagram does have both objects and links and can be used to draw object diagrams 18 2 Package The package is the main organizational artifact within ArgoUML In the UML metamodel it is a sub class of both Namespace and GeneralizableElement Note ArgoUML also implements the UML Model artifact as a sub class of package but not the Subsystem artifact 188 Class Diagram Artifact Reference ArgoUML also implements some less common aspects of UML model management In particular the re lationship UML 1 4 defines as Generalization and the sub class dependency Permission for use between packages 18 2 1 Package Details Tabs The details tabs that are active for packages are as follows ToDoltem Standard tab Properties See Section 18 2 2 Package Property Toolbar and Section 18 2 3 Property Fields For Package below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The Bounds field defines the bounding box for th
203. e e tease saanda E pa tapas rosita 91 107 4 NU Be coccion ripio 92 10 7 5 Set Preferred SIZE msn aa esla pinar 92 10 7 6 Toggle Auto Resizing oocooccocccnccnnconnconncnnnccnccnnccnncconccnnconncinncos 92 A aie er dette ans basis eetes E a e E E EE 92 10 8 The Generation Men Ssss e a EARNE E E ease cheats 92 10 8 1 Generate Selected Classes ooococcoocccononocononocononoconococononoconanoconos 92 10 8 2 Generat AT Classes cortita nieta cards 93 10 8 3 Generate Code for Project To be Written oocooccoccncnoconcnnconcnns 93 10 8 4 Settings for Generate for Project To be Written cooocccoonccnnc 93 10 9 The Critique Menu cito iaa ei Ii E E ci 93 10 9 1 Toggle Autos Critiques c ssecccctsesese rinine en eE pea E 94 10 9 2 Design ISSUES ii eiieeii siones ine SE cecdeis GRESE EERE e 94 ISS ties fe ona senses sa EE A EES SES R RE E ETRE h 94 10 94 Browse Critics renon e a E E E A RRR 95 10 10 The Tools Ment tagayan aE Aa A E AEEA E 97 10 11 The Help MENU siisii ses aaeoa EE K vila 97 10 11 1 System Information ooccoccnnccnnconnconnconncnnacononnncnnncnnconnconncinncons 97 10 11 2 About ArgoUME 33 04 ec ssodew Races iria static aiii 97 Fi The Explora rs 99 TIA Introduction anaren e a Coded Ube a oe Sased ast ogh ANE E Come E 99 11 2 Mouse Behavior in the Explorer oooconoccnocnnccnnccnnncnncnnncnnccnnconnconnccnncons 99 PLD Button Ck ais is airis dote denise 99 11 2 2 Button 1 Double
204. e eeee eee eee 145 15 8 12 Missing return actions coocccoccnnccnnccnncnnncnnnconnconaconncnnncnnronicnnss 145 15 8 13 Missing call send action ooccocnocnncnoconcnnconcnnconcnoroncnnconcnnronos 145 15 8 14 No Stimuli on these links oocooccocnoccncnnconcnoconcnnconcnnroncnnronos 145 15 8 15 Set Classifier Sequence Diagram oococnoccnocnnccnnocnnccnnccnnconicnnns 145 ArgoUML Manual de Usuario 15 8 16 Wrong position of these stimuli cece cece cence eeeeeeen es 145 1S OS Relattons hips siii raid ias 145 15 9 17 Errc lar Association uni ii eee es 145 15 9 2 Make lt association gt Navigable ooocoooccncconoconccnnccnnncnnccnoronicnnos 146 15 9 3 Remove Navigation from Interface via lt association gt 146 15 9 4 Add Associations to lt artifact gt coooccnnconcconoconiconccnnncnnncnaroninnnn 146 15 9 5 Remove Reference to Specific Subclass cece eeee eee eeeeee ee 146 15 9 6 Reduce Associations on lt artifact gt oooconoconccnnccnnccnnnnnnncnoconicnnos 146 15 9 7 Make Edge More Visible ooocoooccncccnnconoconcconccnnncnnncnaroninnnos 146 15 10 Instantiation s a cedo Sad Betas irradia eoag bas E aa ea 147 LSU Modularity sonsir NI 147 15 11 1 Classifier not in Namespace of its Association 147 15 11 2 Add Elements to Package lt package gt oooconoccnocnnccnnccnnccnnccnncnnn 147 15 12 Expected Usage oi RR aa Sera ee dah eee 147 1
205. e entry e Open Navigate to the selected sender instance Receiver Text box Identifies the instance which receives this stimulus Button 1 click navigates to the receiver instance button 2 gives a pop up menu with one entry e Open Navigate to the selected receiver instance Warning In the current release of ArgoUML this field is broken It always shows the entry none and the pop up menu is grayed out Namespace Text box Records the namespace for the stimulus This is the package hierarchy Button 1 click on the entry will navigate to the package defining this namespace or the model for the top level namespace 19 4 Stimulus Call This tool creates a stimulus associated with a call action on the diagram creating at the same time the associated link between sender and receiving instances All details tabs and properties are identical to to that of stimulus in general see Section 19 3 Stimulus Its graphical representation on the diagram is that of a stimulus associated with a call ac tion i e a solid line with a solid arrow head 231 19 5 19 6 19 7 19 8 Sequence Diagram Artifact Reference Note Because the current release of ArgoUML does not fully implement actions there is no en forcement of the relationship to a call action Stimulus Create This tool creates a stimulus associated with a create action on the diagram creating at the same time the associated link between sender and rec
206. e explorer or editing panes followed by selection of the properties tab in the details pane or 2 Navigation buttons cause different artifacts to be selected Le the Go Up button on the properties tab the Navigate Back and Navigate Forward buttons in the main tool bar and the various menu items under Edit Select Figure 13 6 A typical Properties tab on the details pane shows a typical properties tab for an artifact in ArgoUML in this case a class Figure 13 6 A typical Properties tab on the details pane 124 The Details Pane At the top left is the icon and name of the type of artifact i e the UML metaclass not the actual name of this particular artifact In this example the property tab is for a class To the right of this is a toolbar of icons relevant to this property tab The first one is always navigation Go up The last is always Delete to delete the selected artifact from the model The ones in between depend on the artifact The remainder of the tab comprises fields laid out in two or three columns Each field has a label to its left The fields may be text boxes text areas drop down selectors radio boxes and check boxes In most but not all cases the values can be changed In the case of text boxes this is sometimes by just typing the required value However for many text boxes and text areas data entry is via a context sensitive pop up menu using button 2 click which offers options to add a
207. e literals listed not at the bottom It is moved down one 16 5 Stereotype and the literal selected is Stereotypes are the main extension mechanism of UML providing a way to derive specializations of the Element in the UML standard metaclasses Stereotype is a sub class of Generalizablel metamodel Stereotypes are supplemented by constraints and tagged values New stereotypes are added from the property tab of almost any artifact Properties of existing stereo types can be reached by selecting the property tab for any artifact with that stereotype and using the 163 Top Level Artifact Reference navstereo button within the property tab 16 5 1 Stereotype Details Tabs The details tabs that are active for stereotypes are as follows ToDoltem Standard tab Properties See Section 16 5 2 Stereotype Property Toolbar and Section 16 5 3 Property Fields For Stereo type below Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab This contains the representation of the stereotype on diagrams its name between and Warning You can edit this entry but it has no effect and when you return to the entry it will be restored to its original value Tagged Values Standard tab In the UML metamodel Stereotype has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the class is redun
208. e name for the name of the file to be opened The file name may be typed directly in here or selected from the directory listing above using button 1 click Beneath this is a drop down selector labeled Files of type to specify a filter on the files to be shown in the directory listing Only files that match the filter are listed The available filters are listed below The default filter 1s the first one which combines all available formats 73 The Menu bar ArgoUML file zargo uml xmi xml zip e ArgoUML compressed project file zargo e ArgoUML project file uml e XML Metadata Interchange xmi e XML Metadata Interchange xml e XMI compressed project file zip 10 3 3 Save Project Shortcut Ctrl S This saves the project using its current file name Use Save Project As to save the project to a different file If no filename is given yet e g after New then this function works exactly as Save Project As Note In certain circumstances there is nothing to save and this menuitem is downlighted E g when the user did not yet alter a loaded project The presence of a in the titlebar of ArgoUML s window indicates that the current project is dirty has been altered and can be saved 10 3 4 Save Project As This opens a dialog allowing you to save the project under a different file name or to specify a file name for the first time if the project is a new project
209. e package on the diagram Source Standard tab This contains a template package declaration appropriate to the entire package In the future this would be part of the code generation activity Tagged Values Standard tab In the UML metamodel Package has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the package is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived packages still have their value in analysis to introduce useful names or con cepts and in design to avoid re computation 18 2 2 Package Property Toolbar Go up Navigate up through the package structure New Package This creates a new package within the package which appears on no diagram navigating immedi ately to the properties tab for that package New Datatype This creates a new Datatype see Section 16 3 Datatype for the selected package navigating im mediately to the properties tab for that datatype New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected package navigating 189 Class Diagram Artifact Reference immediately to the properties tab for that stereotype Delete Package Deletes the package from the model Warning This is a deletion from the model not just the diagram To delete a package from the diagram but keep it within the model use the main
210. e signals see Section 18 9 Signal that can be raised by the oper ation Caution ArgoUML at present V0 18 has limited support for signals In particular they are not linked to signal events that could drive state machines 203 Class Diagram Artifact Reference Button 1 double click on any of the signals navigates to that parameter 18 8 Parameter A parameter is a variable that can be passed In the UML metamodel it is a sub class of ModelEle ment A parameter is represented within the operation declaration in the operation compartment of a class as follows name type name is the name of the parameter type is the type UML datatype class or interface of the parameter The exception is any parameter representing a return value whose type only is shown at the end of the operation declaration 18 8 1 Parameter Details Tabs The details tabs that are active for parameters are as follows ToDoltem Standard tab Properties See Section 18 8 2 Parameter Property Toolbar and Section 18 8 3 Property Fields For Para meter below Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab This contains a declaration for the parameter Tagged Values Standard tab In the UML metamodel Parameter has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the parameter is re dundant it
211. e used to operate the Zoom Slider as follows When the Zoom icon in the tool bar has the focus indicated by the thin blue box around it then pressing the spacebar opens the zoon slider panel Use the arrow keys to increase and decrease the percentage 1 by 1 Use Shift Tab to set the focus to the percentage box where you can edit the given value directly Pressing Enter activates the changed value When the knob has the focus pressing PageUp PageDown increases decreases the percentage by 50 Pressing Home sets the percentage to 500 and End sets it to 0 9 4 Create operations These buttons have identical functions as their counterparts in the Create menu e New Use Case Diagram See for a full description Section 10 6 1 New Use Case Diagram e New Class Diagram See for a full description Section 10 6 2 New Class Diagram e New Sequence Diagram See for a full description Section 10 6 3 New Sequence Diagram New Collaboration Diagram See for a full description Section 10 6 4 New Collaboration Diagram e New Statechart Diagram See for a full description Section 10 6 5 New Statechart Diagram e New Activity Diagram See for a full description Section 10 6 6 New Activity Diagram e New Deployment Diagram See for a full description Section 10 6 7 New Deployment Dia gram 71 Chapter 10 The Menu bar 10 1 10 2 Introduction An important principle behind
212. e uso principales Hemos identificado 6699 66 cliente ingeniero de mantenimiento oficial de sucursal y sistema central como los actores Figure 4 1 Diagrama de casos de uso basico para un sistema de Cajero Automatico muestra como esto puede ser visualizado en un diagrama de casos de uso Los casos de uso son mostrados como ovalos los actores como monigotes incluso cuando son maquinas con lineas conocidas como asociaciones con ectando los casos de uso a los actores que est n involucrados en ellos Un cuadro alrededor de los casos de uso enfatiza la frontera entre el sistema definido por los casos de uso y los actores que son externos Note No todos los analisis gustan de usar un cuadro alrededor de los casos de uso Es un asunto de opci n personal Figure 4 1 Diagrama de casos de uso basico para un sistema de Cajero Automatico 31 Captura de Requerimientos Las siguientes secciones muestran como el diagrama de casos de uso b sico puede ser extendido para mostrar informaci n adicional sobre el sistema que est siendo dise ado 4 3 2 1 Actores Activos y Pasivos Los actores Activos inician la interacci n con el sistema Esto puede ser mostrado colocando una flecha en la asociaci n desde el actor apuntando hacia el caso de uso En le ejemplo del Cajero Automatico el cliente es un actor activo La interacci n con los actores pasivos es iniciada por el sistema Esto puede ser most
213. eas a la Lista de Correo de Usuarios de ArgoUML mailto users Oargouml tigris org En caso de que quisieras a adir en los capitulos sin desarrollar de berias contactar la Lista de Correo de Desarrollador de ArgoUML mailto devCargouml tigris org para comprobar que nadie mas est trabajando en esa parte Te puedes subscribir a cualquiera de las listas de correo a traves de el Sitio Web de ArgoUML http argouml tigris org 1 4 Supuestos Esta publicaci n del manual asume que el lector esta ya muy familiarizado con UML Esto est refle jado en la sobriedad en la descripci n de los conceptos UML en el tutorial El caso de estudio est descrito pero a n no totalmente a traves del tutorial Esto ser realizado en futuras publicaciones del manual Part 1 Tutorial Chapter 2 Introducci n escribiendose Este tutorial te llevar a traves de un tour sobre el uso de ArgoUML para modelar un sistema Un proyecto de ATM automated teller machine cajero automatico ha sido escogido como caso de estudio para demostrar los varios aspectos de modelado que ArgoUML ofrece En subsiguientes sec ciones vamos a desarrollar el ejemplo de Cajero Automatico en una descripci n completa en UML El tutorial sin embargo solo te guiar a traves de parte de ello En este punto deberias crear un directorio para contener tu proyecto Nombra el directorio de forma con sistente con el resto de tu sistema de archivos Deberias nombrar los c
214. eated within the UML design A drop down at the top of the ex plorer controls the ordering of artifacts in the explorer The most useful are the Package centric default and Diagram centric The latter shows artifacts grouped by the diagram on which they appear Use Cases The procedure for adding use cases is the same as that for adding actors but using the use case icon on the editing pane toolbar By default use cases in ArgoUML do not display their extension points for use in extend relationships You can show the extension point compartment in one of two ways 1 Select the use case in the editing pane with button 1 click then select the Style tab in the details 38 Captura de Requerimientos pane and button 1 click on the Display Extension Points check box 2 Use button 2 click over the use case in the editing pane to display a context sensitive pop up menu and from that choose Show Show Extension Point Compartment The same approaches can be used to hide the extension point compartment 4 4 2 1 Adding an Extension Point to a Use Case There are two ways to add an extension point to a use case 1 Select the use case on the editing pane with button 1 click Then click on the Add Extension Point icon on the toolbar and a new extension point with default name and location will be ad ded after any existing extension points Note The Add Extension Point icon is grayed out and unusable unti
215. ecialized nature of these profiles implementation in ArgoUML is postponed until a yet undeter mined moment Table 24 1 Stereotypes defined in UML 1 4 and ArgoUML StereoType Base Element ArgoUML support access Permission yes appliedProfile Package no association AssociationEnd yes auxiliary Class no become Flow no call Usage yes copy Flow no create BehavioralFeature yes create CallEvent yes create Usage yes derive Abstraction yes destroy BehavioralFeature yes destroy CallEvent yes document Abstraction no executable Abstraction no facade Package yes file Abstraction no 288 Built In DataTypes Classes Interfaces and Stereotypes StereoType Base Element ArgoUML support focus Class no framework Package yes friend Permission yes global AssociationEnd yes implementation Class no implementation Generalization yes implicit Association yes import Permission yes instantiate Usage yes invariant Constraint no library Abstraction no local AssociationEnd yes metaclass Class no metamodel Package yes modelLibrary Package no parameter AssociationEnd yes postcondition Constraint no powertype Class no precondition Constraint no process Classifier yes profile Package no realize Abstraction yes refine Abstraction yes requirement Comment yes 289 Built In DataTypes Classes Inte
216. ected 2D items or add and move a new control point on a link Button 1 motion on a selected component s control point will stretch that component s shape e Broom Button 1 motion with this tool provide a broom which will sweep all artifacts along This is a very shortcut way of lining things up The Broom can also be invoked by using SHIFT with button 1 motion when the Select tool is in use The Broom is discussed at length in its own chapter see Section 12 4 The Broom 106 The Editing Pane Tip Additional control of artifact layout is provided through the Arrange menu see Sec tion 10 7 The Arrange Menu 12 3 2 Annotation Tools The annotation tool Comment is used to add a comment to a selected UML artifact Caution Unlike most other tools you use the Select tool to select an artifact and then button 1 click on Comment to create the comment If no element is selected when the comment tool is clicked then the comment is created and put at the left top corner The comment is created alongside the selected artifact empty by default The text can be selected with button 1 double click and edited from the keyboard The UML standard allows comments to be attached to any artifact You can link any comment to aditional elements using the Comment Link tool 12 3 3 Drawing Tools These are a series of tools for providing graphical additions to diagrams Although they are not UML ar tifacts th
217. ected type see Section 18 5 Class Section 18 3 Datatype and Section 18 15 Interface Initial Value Text box with drop down This allows you to set an initial value for the attribute 1f desired this is optional The drop down menu provides access to the common values 0 1 2 and null Caution Any constructor operation may ignore this initial value Visibility Radio box with entries public private protected and package e public The attribute is available to any artifact that can see the owning class e private The attribute is available only to the owning class and any inner classes 198 Class Diagram Artifact Reference e protected The attribute is available only to the owning class or artifacts that are subclasses of the owning class e package The attribute is available only to artifacts contained in the same package Changeability Radio box with entries addOnly changeable and frozen e addOnly Meaningful only if the multiplicity is not fixed to a single value Additional values may be added to the set of values but once created a value may not be removed or altered e changeable There are no restrictions of modification e frozen Also named immutable The value of the attribute may not change during the life time of the owner class The value must be set at object creation and may never change after that This implies that there is usually an argument for this value in
218. ecto zargo El proyecto contiene un paquete de alto nivel llamado unt it ledModel el cual contiene un diagrama de clases y un diagrama de casos de uso Si miramos cuidadosamente a la pantalla podemos ver que la carpeta Medium en el panel de Tar as 26 OOA amp D basada en UML Pendientes el panel de abajo a la izquierda debe contener algunos elementos ya que su icono de acti vaci n est representado Hacer click en este icono abrir la carpeta Medium Una carpeta abierta es indicada por el icono Pero que es este Panel de Tar as Pendientes de todas formas No has grabado nada a n que ha de ser hecho as que donde se originan esos elementos La respuesta el simple y es al mismo tiempo uno de los puntos fuertes de ArgoUML Mientras estas tra bajando en tu modelo UML tu trabajo es monitorizado continuamente y de forma invisible por un trozo de c digo llamado una cr tica de dise o Esto es como un mentor personal que vigila por encima de tu hombro y te notifica cada vez que ve algo cuestionable en tu dise o Las criticas son bastante poco entrometidas Te dan una advertencia amigable pero no te fuerzan dentro de principios de dise 0 que no quieres o no te gusta seguir Tomemos un vistazo de que nos est n di ciendo las cr ticas Haz click en el icono cerca de la carpeta Medium y haz click en el elemento Re visa el nombre del paquete UntitledModel Figure 3 10 Ventana ArgoUML Mostrando el Element
219. ed abstract 15 13 3 Add Operations to lt class gt Suggestion that the specified class has no operations defined This is required for the class to be useful in a design 15 13 4 Reduce Operations on lt artifact gt Suggestion that the artifact class or interface has too many operations for a good design and is at risk of becoming a design bottleneck The Wizard of this critic allows setting of the treshold i e the maximum number of operations allowed before this critic fires Caution This number is not stored persistently and there is no way to reduce it after it has been set higher except by creating more operations until the critic fires again Restarting ArgoUML resets this number to its default 20 15 14 Code Generation Critics concerning code generation in ArgoUML The current version of ArgoUML has one critic in this category 15 14 1 Change Multiple Inheritance to interfaces Suggestion that a class has multiple generalizations which is permitted by UML but cannot be gener ated into Java code because Java does not support multiple inheritance 15 15 Stereotypes Critics concerning stereotypes in ArgoUML The current version of ArgoUML has no critics in this category 15 16 Inheritance 148 The Critics Critics concerning generalization and specialization in ArgoUML The current version of ArgoUML has the following critics in this category 15 16 1 Revise Attribute Names to Avo
220. ed by this license including translations anthologies compil 306 Open Publication License ations and partial documents must meet the following requirements 1 The modified version must be labeled as such 2 The person making the modifications must be identified and the modifications dated 3 Acknowledgement of the original author and publisher if applicable must be retained according to normal academic citation practices 4 The location of the original unmodified document must be identified 5 The original author s or authors name s may not be used to assert or imply endorsement of the res ulting document without the original author s or authors permission F 5 Good Practice Recommendations In addition to the requirements of this license it is requested from and strongly recommended of redis tributors that 1 If you are distributing Open Publication works on hardcopy or CD ROM you provide email notifica tion to the authors of your intent to redistribute at least thirty days before your manuscript or media freeze to give the authors time to provide updated documents This notification should describe modifications if any made to the document 2 All substantive modifications including deletions be either clearly marked up in the document or else described in an attachment to the document 3 Finally while it is not mandatory under this license it is considered good form to offer a free copy of
221. ed interface e Dependency Add a dependency between two artifacts selected using button 1 motion from the de pendent artifact There are also 2 special types of dependency offered here Permission and Usage A Permission is created by default with stereotype Import and is used to import ele ments from one package into another e Attribute Add a new attribute to the currently selected class The attribute is given the default name newAttr of type int and may be edited by button 1 double click and using the keyboard or by selecting with button 1 click after the class has been selected and using the property tab Note This tool is grayed out except when a class is selected e Operation Add a new operation to the currently selected class or interface The operation is given the default name newOperation with no arguments and return type void and may be edited by 109 The Editing Pane button 1 double click and using the keyboard or by selecting with button 1 click after the class has been selected and using the property tab Note This tool is grayed out except when a class or interface is selected e Association Class Add a new association class between two artifacts selected using button 1 motion from the first artifact to the second e Datatype Add a datatype to the diagram For convenience when the mouse is over a selected data type it displays handles at the top and at the bottom which may be click
222. ed or dragged to form a gener alization relationship the target being another datatype There are 2 other elements available here Enumeration and Stereotype These two have similar handles except the one at the top of a stereotype when clicked it creates a metaclass connected by a dependency marked with Mstereotype This eases the creation of stereotype declaration diagrams see the literature on the subject 12 3 6 Sequence Diagram Specific Tools Seven tools are provided specific to UML artifacts on sequence diagrams The detailed properties of these artifacts are described in the section on sequence diagram artifacts see Chapter 19 Sequence Dia gram Artifact Reference e ClassifierRole Add a classifierrole to the diagram e Message with Call Action Add a call message between two classifierroles selected using utton 1 motion from the originating classifierrole to the receiving classifierrole ion e Message with Return Action Add a return message between two classifierroles selected us ng button 1 motion from the originating classifierrole to the receiving classifierrole e Message with Create Action Add a create message between two classifierroles selected us ng button 1 motion from the originating classifierrole to the receiving classifierrole e Message with Destroy Action Add a destroy message between two classifierroles selected using button 1 motion from the originating classifier
223. ee below But ArgoUML V0 20 does always check and refuses to accept any constraint with the slightest error e Configure Constraint Editor This a dialog to configure options in the constraint editor It is also available in the main Constraints tab and is discussed in detail there see Section 13 7 Constraints Tab 130 13 8 The Details Pane To the right of the toolbar is a check box labeled Syntax Assistant unchecked by default which will enable the syntax assistant in the constraint editor If the syntax assistant is enabled six drop down menus are provided in a row immediately below the toolbar These provide standard templates for OCL that when selected will be inserted into the con straint being edited The syntax assistant can be made floating in a separate window by button motion on the small divider area to the left of the row of drop down menus e General General OCL constructors Entries inv inserts an invariant pre inserts a pre condition post inserts a post condition sel f inserts a self reference pre inserts a reference to a value at the start of an operation and result inserts a reference to a previous result e Basic Operators Relational operators and parentheses Entries lt gt lt gt lt gt and e Numbers Arithmetic operators and functions Entries mod div abs max min round and floor e Strings String functions Entri
224. efault If this is selected then ArgoUML will show the initial value of e g attributes in the diagram In UML notation the initial value is shown e g like this newAttr int 1 e Show properties clear by default If this is selected then ArgoUML will show various proper ties between braces E g for an attribute it may show newAttr int frozen e Show types and parameters set by default When this checkbox is unmarked attributes in classes are shown without type indication and operations are shown without parameters This feature may be usefull during the analysis phase of your project If all checkmarks in the Notation Tab are un checked then e g for an attribute ArgoUML may show newAttr And for an operation newOp eration e Show stereotypes in explorer clear by default If this is selected then ArgoUML will show stereotypes next to the icons of the modelelements in the Explorer i e the tree structure at the left hand side e Default shadow width set to 1 by default ArgoUML is able to draw all elements on a dia gram with a shadow Use this setting to adjust the size of the shadow used when the modelelement is created The details tab Presentation allows to set the shadow per modelelement after they are cre ated 10 4 5 6 Modules Tab This tab shows a list of modules that are installed which may be enabled or disabled Since this is a new concept for ArgoUML it currently contains a list
225. eiving instances All details tabs and properties are identical to to that of stimulus in general see Section 19 3 Stimulus Its graphical representation on the diagram is that of a stimulus associated with a create ac tion i e a solid line with a solid arrow head terminating at the head of the created instance Note Because the current release of ArgoUML does not fully implement actions there is no en forcement of the relationship to a create action Stimulus Destroy This tool creates a stimulus associated with a destroy action on the diagram creating at the same time the associated link between sender and receiving instances All details tabs and properties are identical to to that of stimulus in general see Section 19 3 Stimulus Its graphical representation on the diagram is that of a stimulus associated with a destroy action i e a solid line with an open arrow head terminating at a cross at the bottom of the destroyed in stance s time line Note Because the current release of ArgoUML does not fully implement actions there is no en forcement of the relationship to a destroy action Stimulus Send This tool creates a stimulus associated with a send action on the diagram creating at the same time the associated link between sender and receiving instances All details tabs and properties are identical to to that of stimulus in general see Section 19 3 Stimulus Its graphical representation
226. elected action button 2 gives a pop up menu with two entries e New Add a new Do Activity action of a certain kind This menu has the following submenus to select the kind of action Call Action Create Action Destroy Action Return Action Send Ac tion Terminate Action Uninterpreted Action e Delete From Model Delete the Do Activity Deferrable Events Text box Shows a list of events that are candidates to be retained by the state machine if they trig ger no transitions out of the state not consumed Button 1 click navigates to the selected event button 2 on an event gives a pop up menu with the following entries e Select Allows to add already existing events to the list of deferred ones New Add a new event of a certain kind This menu has the following submenus to select the kind of event Call Event Change Event Signal Event Time Event e Delete From Model Delete the event Incoming Text area Lists all the transitions that enter this state Button 1 double click navigates to the selected entry Outgoing Text area Lists all the transitions that leave this state 238 Statechart Diagram Artifact Reference Button 1 double click navigates to the selected action Internal Transitions Text area Lists all the internal transitions of the state Such transitions neither exit nor enter the state so they do not cause a state change Which means that the Entry and Exit actions are not in voked
227. elected using button 1 from the child to the parent e Realization Add a realization between a class and an interface selected using button 1 motion from the realizing class to the realized interface e Dependency Add a dependency between two artifacts selected using button 1 motion from the de pendent artifact e Association Add an association between two artifacts node component class or interface se lected using button 1 motion from the first artifact to the second artifact There are 6 types of associ ation offered here see Figure 12 4 The association tool selector association aggrega tion and composition and all these three can be bidirectional or unidirectional Caution The constraint that associations between classes and interfaces must not be navigable from the interface still applies on deployment diagrams e Object Add an object to the diagram For convenience when the mouse is over a selected object it displays four handles to left right top and bottom which may be dragged to form link relationships e Link Add a link between two artifacts node instance component instance or object selected using button 1 motion The Broom ArgoUML s broom alignment tool is specialized to support the needs of designers in achieving the kind of alignment used in UML diagrams It is common for designers to roughly align objects as they are cre ated or by using simple movement commands The broom is an ea
228. elementos de diagrama 3 4 2 7 1 1 Usando Teclas del Rat n Seleciona los elementos que quieres mover Presionando la tecla Ctrl mientras seleccionas puedes selec cionar muchos elementos para mover el mismo tiempo Ahora presiona tus teclas de flecha Los elementos seleccionados se mueven un poco con cada tecleo 21 OOA amp D basada en UML Si ademas mantienes presionada la tecla Mayusculas Shift se moveran un poco mas r pido 3 4 2 7 1 2 Usando la Barra de Herramientas del Panel de Edici n Haz click en el boton escoba en la barra de herramientas Mueve tu rat n al panel de diagrama haz click derecho y mantenlo Ahora mover tu rat n alinear los elementos 3 4 2 7 2 Colocando Elementos El elemento de men Colocar Arreglo te permite alinear agrupar o desplazar elementos 3 4 2 8 Trabajando con Proyectos 3 4 2 8 1 La Ventana de Inicio Figure 3 6 Ventana inicial de ArgoUML muestra la ventana principal de ArgoUML como aparece justo despues de iniciar El area de cliente de la ventana principal debajo del men y la barra de herramientas est subdividida en cuatro paneles Empezando con el panel superior mas a la izquierda y funcionando continuamente puedes ver el Explorador mostrando una vista de arbol de tu modelo UML el Panel de Edici n con su barra de herramientas dos barras de desplazamiento y un area de gris de dibujado el Panel de Detalles con la solapa de Tareas Pendientes seleccionada y el
229. emas antes en el ciclo de desarrollo Estos procesos usan unas series de mini cascadas definiendo unos pocos requerimientos los mas im portantes primero llevandolos a traves del analisis dise 0 y construcci n para obtener una version temprana del producto con funcionalidad limitada relacionada con los requerimientos mas importantes La retroalimentaci n de este c digo puede ser usada para refinar los requerimientos apuntar prob lemas etc antes de hacer mas trabajo El proceso es entonces repetido para requerimientos adiciones para construir un producto con un paso mas en funcionalidad Otra vez retroalimentaci n adicional puede ser aplicada a los requerimientos El proceso es repetido hasta que finalmente todos los requerimientos han sido implementados y el pro ducto est completo Es esta iteraci n lo que da a estos procesos su nombre Figure 3 3 Esfuerzo In volucrado en los Pasos de un Proceso Iterativo muestra como este proceso se compara con la structura piramidal del Proceso en Cascada Figure 3 3 Esfuerzo Involucrado en los Pasos de un Proceso Iterativo El crecimiento en popularidad de los procesos iterativos est estrechamente unido a el crecimiento de OOA amp D Es la encapsulai n limpia de objetos lo que permite a una parte del sistema ser contruida con trozos para el codigo restante claramente definidos 3 2 1 2 1 El Proceso Racional Unificado Quizas el Proceso Iterativo mejor conocido es el Proc
230. en Una declaraci n del contexto problema y objetivo de la soluti n Objetivos Que estamos intentando alcanzar y como deseamos alcanzarlo Contexto de Mercado o Convenios Contractuales Para un desarrollo guiado por el mercado esto de ber a indicar mercados objetivo diferencidores competitivos eventos motivadores y cosas as Para un desarrollo contractual esto deber a explicar los factores clave contractuales Partes Implicadas Los usuarios en el sentido m s amplio del sistema Muchos de ellos se mapear n en actores o equipamiento de control que se mapea en actores Caracteristicas clave Los aspectos funcionales clave de la soluci n deseada al problema al nivel mas alto Estos se mapear n ampliamente en los casos de uso Es de ayuda poner algo de prior izaci n aqu Limitaci nes Una visi n general de los parametros no funcionales del sistema Estos ser n trata dos detalle en la especificaci n de requerimientos suplementarios e Apendice Un listado de los actores y casos de uso que ser n necesarios para cumplir esta visi n Es util enlazar a estos desde las secciones tempranas para asegurar una cobertura exahustiva Diagrama de Casos de Uso El documento de visi n ha identificado los casos de uso y los actores El diagrama de casos de uso cap tura como interaccionan En nuestro ejemplo de Cajero Automatico hemos identificado cliente usa ca jero mantener cajero y auditar como los tres casos d
231. en or 111 only by the source classifier Generalizations Text area Lists any interface that generalizes this interface Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized interface i e for which this interface is a generalization Button 1 double click navigates to the generalization and opens its property tab AssociationEnds Text box Lists any AssociationEnds see Section 18 12 Association End connected to this inter face Note Associations between classes and interfaces must be navigable only from the class to the interface ArgoUML will create associations between classes and interfaces with the correct navigability but does not prevent the user from altering this Button 1 double click navigates to the selected entry Operations Text area Lists all the operations see Section 18 7 Operation defined on this interface Button 1 double click navigates to the selected operation Button 2 click will show a popup menu with two 221 Class Diagram Artifact Reference items Move Up and Move Down which allow reordering the operations Caution All operations on an interface must be public The ArgoUML critics will complain if this is not the case 18 16 Abstraction An abstraction is a dependency relationship joining two artifacts within the model at different levels of abstraction Within ArgoUML it is principal
232. en a card is up in the air it is an object and can do things The owner announces that he needs to fulfill his responsibility The responsibility is refined into smaller tasks if possible These smaller tasks can be fulfilled by the object is appropriate or they can be fulfilled by interacting with other objects collaborators If no other appropriate class exists you may need to make one and assign it to someone This is the fundamental procedure of the scenario execution G 4 The Process CRC Cards are used in the Analysis and Design phases The process for these phases differ primarily in how the classes and scenarios are chosen In the Analysis phase the classes and scenarios are in the problem space and generally derive from the requirements In the Design phase solution space classes and scenarios are added Additionally in the Analysis phase the very first session starts with no classes or scenarios to select from so a special session creates them 310 Index The use of the index in the document is done a little at random and cannot be trusted Please help in suggesting new index entries A Action 291 Activity Diagram 291 Actor 29 38 169 291 Actor Activo 32 Actor Association Ends 172 Actor Details Tabs 169 Actor Generalizations 172 Actor Modifiers 171 Actor Name 171 Actor Namespace 171 Actor Pasivo 32 Actor Specializations 172 Actor Stereotype 171 Add Action 267 Add Actor 171 Add DataType 154 Add
233. enerally not discussed in this document 8 2 2 On the other hand mouse actions in a diagram may not seem so intuitive to the user since it is specific for ArgoUML Hence they are explained here In short clicking selects or activates the object beneath the mouse pointer and moves the focus i e navigation More in detail the button 1 click may cause the following result 8 2 2 1 Selection Here button 1 is used to choose select an artifact in a list or tree or on a diagram on which subsequent operations will take place Multiple artifacts may be selected by using Shift and or Ctrl in combination with button 1 see Section 8 2 5 Shift and Ctrl modifiers with Button 1 Selection is always clearly in dicated by a colored background On a diagram the selected artifact is indicated with colored blocks at the corners ends of the object Artifacts can be selected or deselected in different ways Button 1 click Deselects all artifacts and selects the one clicked on e Button 1 motion Button motion moving the mouse with the button down in the diagram not on any artifact allows to draw a rectangle around artifacts which will be selected when the button 1 is re leased e Menu functions and shortcuts Many menu operations change selection as side effect e g creating a new diagram Many keyboard shortcuts for menu operations change the selection e g Ctrl A which stands for the Select A11 function 8 2 2 2 Activa
234. enerally suggest how the bad design issue it has identified can be rectified by raising a to do item 15 1 2 Design Issues ArgoUML categorizes critics according the the design issue they address some critics may be in more than one category At present there are 16 such categories Within this manual the descriptions of critics are grouped in sections by design issue 15 2 Uncategorized These are critics that do not fit into any other category ArgoUML has no critics in this category Maybe some will be added in later versions 15 3 Class Selection These are critics concerning how classes are chosen and used ArgoUML has the following critics in this category 15 3 1 Wrap DataType DataTypes are not full classes within UML 1 4 They can only have enumeration literals as values and only support query operations that is operations that do not change the DataType s state 135 The Critics DataTypes cannot be associated with classes unless the DataType is part of a composite black dia mond aggregation Such an association relects the tight binding of a collection of DataType instances to a class instance In effect such a DataType is an attribute of the class with multiplicity Good OOA amp D depends on careful choices about which entities to represent as full objects and which to represent as attributes of objects There are two options to fix this problem e Replace the DataType with a full class e o
235. entical functions as their counterparts in the Edit menu e Remove From Diagram See for a full description Section 10 4 2 Remove From Diagram e Navigate Back See for a full description Section 10 4 1 Select e Navigate Forward See for a full description Section 10 4 1 Select 9 3 View operations The Find button has identical behaviour as its counterpart in the View menu The Zoom button is a more luxurously version of the function in the View menu e Find See for a full description Section 10 5 2 Find e Zoom This is a different version of the menu item for zooming as described in Section 10 5 3 Zoom Clicking with button 1 on the zoom icon opens a panel as in the figure below Figure 9 1 The Zoom slider on the Toolbar Once the panel is open the following actions are possible e Clicking with button 1 on the knob followed by button 1 movement will adjust the zoomfactor e Clicking with button 1 on the shown percentage allows editing the given zoomfactor in percent directly with the keyboard Double clicking on the value shown selects the whole entry for easy overtyping e Clicking with button 1 below or above the knob increases or decreass the zoom factor with 1 Use this function to easily fine adjust the percentage e Clicking with button 1 or button 2 on the Zoom tool or anywhere outside the slider panel closes the 70 The Toolbar panel e The keyboard can b
236. enumeration The primitive enumerations all have lower case names but there is no formal convention Note The default name supplied for a newly created datatype is the empty string Enu merations with empty string names will appear with the name anon Enumera tion in the explorer Namespace Drop down selector Allows changeing the namespace for the enumeration This is the composition hierarchy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that this enumeration cannot be instantiated but must always be specialized Note ArgoUML provides no mechanism for specializing enumerations so this check box is of little use e Leaf indicates that this enumeration can have no further sub types while Root indicates it is a top level enumeration Tip In the absence of specialization of enumerations within ArgoUML these have little value In effect all enumerations are both Root and Final Visibility Radio box with entries public private protected and package Records the visibility for the Enumeration Client Dependencies Text area Lists any elements that depend on this enumeration Caution 162 Top Level Artifact Reference It is not clear that defining dependencies between enumerations makes much sense Supplier Dependencies Text area Lists any elements that this enumeration depends on Caution It is not clear that defining dependencies between e
237. eotype Drop down selector Model is provided by default with the UML standard stereotypes for model systemModel and metamodel and package facade framework stub Stereotyping models is a useful thing although it is of limited value in ArgoUML where you have only a single model Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the model This is the package hierarchy However since the model is at the top of the hierarchy in ArgoUML this box is always empty Visibility Radio box with entries public private protected and package Records the visibility for the model Since ArgoUML only permits one model this has no meaning ful use Modifiers Check box with entries Abstract Leaf and Root e abstract is used to declare that this model cannot be instantiated but must always be special ized The meaning of abstract applied to a model is not that clear It might mean that the model contains interfaces or abstract classes without realizations Since ArgoUML only permits one model this is not a meaningful box to check e Leaf indicates that this model can have no further subpackages while root indicates it is the top level model Within ArgoUML root only meaningfully applies to the Model since all packages sit within the model In the absence of the topLevel stereo
238. erence ToDoltem Standard tab Properties See Section 23 4 2 Component Property Toolbar and Section 23 4 3 Property Fields For Com ponent below Documentation Standard tab Presentation Standard tab The Bounds field defines the bounding box for the component on the diagram Source Standard tab but with no contents Caution A component should not generate any code so having this tab active is probably a mistake Tagged Values Standard tab Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 23 4 2 Component Property Toolbar Go up Navigate up through the package structure New reception This creates a new reception navigating immediately to the properties tab for that reception New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected component navigat ing immediately to the properties tab for that stereotype Delete This deletes the component from the model Warning This is a deletion from the model not just the diagram To delete a component from the diagram but keep it within the model use the main menu Remove From Dia gram or press the Delete key 279 Deployment Diagram Artifact Reference 23 4 3 Property Fields For Component Name Text box The name of the component The name of a component h
239. eries of tabs at the top which are selected by button 1 click The body of a tab is a menu of items to be checked selected or entered specific to the particular tab selected Of these the Properties Tab is by far the most complex with a different presentation for each arti fact within the system The detailed descriptions of the properties tab for each artifact are the subject of separate chapters covering the artifacts that may appear on the various diagrams see Chapter 16 Top Level Artifact Reference through Chapter 23 Deployment Diagram Artifact Reference To Do Item Tab This tab provides control over the various to do items created by the user or raised automatically by the ArgoUML critics discussed in more detail in the section on the Critique menu see Section 10 9 The Critique Menu Figure 13 2 Example of the To Do Item tab on the properties pane shows a typical pane The to do item is selected with button 1 in the to do pane see Chapter 14 The To Do Pane or by using the Critiques context sensitive pop up menu on the editing pane Figure 13 2 Example of the To Do Item tab on the properties pane Customization of the critics behaviour is possible through the Browse critics menu see Sec tion 10 9 4 Browse Critics The body of the tab describes the problem found by the critic and outlines how it can be fixed To the left are four buttons e New To Do Item This launches a dialog box see Figure
240. erramienta de terceros que puede enlazar documentos pro porcionando una prueba automatizada de cobertura de requisitos en tal caso esta secci n no es ne cesaria o puede ser generada automaticamente El tama o final de la especificac 0n de caos de uso depender de la complejidad del caso de uso 35 Captura de Requerimientos Como peque a regla la mayor a de los casos de uso toman alrededor de 10 15 paginas para espe cificar la mayor a de las cuales son flujos alternativos Si el tuyo es mucho mas largo que esto consid era simplificar el caso de uso Si el tuyo es mucho mas peque o considera que el caso de uso esta de scribiendo una parte demasiado peque a del comportamiento 4 3 3 1 Especificando el Flujo Basico Todos los flujos en una especificaci n de casos de uso son lineales esto es que no hay ramas condi cionales Cualesquiera elecciones en los flujos son manejadas especificando otro flujo alternativo que recoge el punto de elecci n Es importante recordar que estamos especificando comportamiento aqui no programandolo Un flujo es especificado como una serie de pasos numerados Cada paso debe implicar alguna inter acci n con un actor o al menos generar un cambio que sea observable externamente por un actor La captura de requerimientos no deber a estar especificando comportamiento interno y oculto del sistema Por ejemplo nosotros podemos dar la siquiente secuencia de pasos para el flujo basico del ca
241. es 12 10 1 Notation Languages ArgoUML supports showing notation in different languages By default all text is shown in UML nota 119 The Editing Pane tion but the menus contain an item to select between Java and UML With plugin modules it is even possible to select other languages such as C and PHP but the current 0 22 version of ArgoUML does not show any difference Figure 12 7 A class in UML notation shows a class in UML notation while Figure 12 8 A class in Java notation shows the same class in Java notation Figure 12 7 A class in UML notation Figure 12 8 A class in Java notation 12 10 2 Notation Editing on the diagram Most text shown on a diagram may be edited by double clicking button 1 on the text This causes a edit box to be shown with the previous text selected ready for amending Also the status bar of ArgoUML i e the small area at the bottom of the ArgoUML window shows an help text that indicates the syntax of the text to be entered Text entry can be concluded by pressing F2 or for single line fields by pressing the enter key Additionally editing can be concluded by clicking somewhere in the diagram outside the edit area Editing notation on the diagram is a very powerful way to enter a lot of model information in a very compact way It is e g possible to create an operation its stereotype all parameters and their types and operation properties visibility concurrenc
242. es To be written To be written 6 9 5 4 History To be written Shallow v Deep To be written 6 10 Activity Diagrams To be written To be written 6 10 1 The Activity Diagram To be written More on this To be written 6 10 1 1 Action States To be written To be written 6 11 Creating Activity Diagrams in ArgoUML To be written 6 11 1 Activity Diagrams To be written To be written 6 11 1 1 Creating an Activity Diagram Select a use case or class then you can create an activity diagram 6 11 2 Action States To be written To be written 59 Design 6 12 Deployment Diagrams To be written To be written 6 12 1 The Deployment Diagram To be written 6 13 Creating Deployment Diagrams in ArgoUML To be written 6 13 1 Nodes To be written To be written 6 13 1 1 Node Instances To be written To be written 6 13 2 Components To be written To be written 6 13 2 1 Component Instances To be written To be written 6 13 3 Relationships between nodes and components To be written To be written 6 13 3 1 Dependency To be written To be written 6 13 3 2 Associations To be written To be written 6 13 3 3 Links To be written To be written 6 14 System Architecture To be written To be written 6 15 Case Study To be written 6 15 1 CRC Cards To be written To be written 6 15 2 Pa
243. es concat size toLower toUpper and substring e Booleans Logical functions Entries or and xor not implies andif then else e Collections Operators and functions on collections bags sets and sequences The large num ber of functions are organized into sub groups e General Functions that apply to all types of collection Entries Collection insert a new collection Set insert a a new set Bag insert a new bag Sequence insert a new sequence size count isEmpt y notEmpt y includes includesAll iterate exists forAll collect select reject union intersection including excluding and sum e Sets Operators and functions that apply only to sets Entries set difference and symmet ricDifference e Sequences Functions that apply to sequences Entries first last at append prepend and subSequence The remainder of the tab comprises a writable text area containing the text to be edited The mouse but tons have their standard behavior within an editable text area see Section 8 2 General Mouse Behavior in ArgoUML In addition cut copy and paste operations may be invoked through the keyboard shortcuts Ctr1 X Ctrl C and Ctr1 V respectively Stereotype Tab This tab shows the available and applied stereotypes for the currently selected modelelement It consists of 2 panels and 2 buttons The buttons allow to move the stereotypes from one list to the other Fig
244. es d erreen TER Ea Ss EERE PASEO NE eE reos artis 72 10 1 NS gs 72 10 2 Mouse Behavior in the Menu Bar oooccnnccnnconccnnicconccnncnnnconccnnconnconnccnnions 72 10 3 The Fle Menu einst oireen tad essa oiei diia 73 10 31 NEW ron wheal enc cycle casting erred Sond N E E da 73 10 32 Open Projectes nenita triste aiii 73 10 3 3 Save Projet t sr n is BAM SR A aes 74 10 3 4 S ave Project ASci ote osume sesh pt eate py A EAE ae A E tes 74 103 5 Revert to Saved oe aE E E E ree hab cheats cda 74 10 3 0 Import XMI ss cccs es seeds ceases sonsdacidea tte dois cti 75 103 7 Export XMI ocn cod isin bisks eE EEES EEEE nia dias eeaed 75 10 3 8 Import A neresen wis rE PEE SESSE GEER SPESE e 75 10 3 9 P ge Setup c vone e o N EE ETEA EA EEE i 76 10 3 10 Printe naar a a E EEE ERS 76 10 3 11 Export Graphics co ccsescsvvevccstsvceecstpeees erros ee Er VEs EES sane eesseavecns 77 10 3 12 Export All Graphics sissies soisi Stas scesn sess oteaeeedeaases 77 10 3 13 NOt at OM sesos tatiana tenn iden se EE EENS TI 10 314 Properties aiii iii aaa ded 78 10 3 15 Saye Configuration eye nee ea pean veces ratios EER EEE eet 79 10 3 16 Most Recent Used Files 2 0 0 0 cece cece cee cece seen secu eens eeneeens 80 NS E 80 104 The Edit Meda a Ue ie ERN 80 LOA O ciosssi sss tees ase ots tossed E soins steeds thes shate oo sig saaebehoiaaeisesdewas hy 80 10 4 2 Remove From Diagram cece cece eee ce eeceeece teen seen sone eens eeas 81 10 4
245. es or Signatures in an Artifact Two operations in lt artifact gt have the same signature This means their name is the same and the list of parameters has the same type Where there are conflicting signatures correct code cannot be generated for mainstream OO languages It also leads to very unclear semantics of the design In comparing signatures this critic considers 1 the name 2 the list of in out and in out parameter types in order and Only if these all match in both type and order will the signatures be considered as the same This follows the line of Java C in ignoring the return parameters for the signature This may be unsat isfactory for some functional OO languages Note Some purists would argue that the comparison should really differentiate between in out and in out parameters However no practical programming language can do this when resolving an overloaded method invocation so this critics lumps them all together 15 4 4 Duplicate End Role Names for an Association The specified association has two or more ends roles with the same name One of the well formedness rules in UML 1 4 for associations is that all end role names must be unique This ensures that there can be unambiguous reference to the ends of the association To fix this manually select the association and change the names of one or more of the offending ends roles using the button 2 pop up menu or the property sheet 15
246. esides UML only Java is partly implemented in V0 22 of ArgoUML 10 3 14 Properties This menu entry brings up a dialog box which allows the user to set various options of the currently loaded project All settings in this dialog are stored in the project file together with the model Figure 10 9 The dialog for Properties Notation The User tab In the User tab you are able to set the following fields e The first field contains the name of the author or responsible for the current project By default the name and email of the creator are filled in so probably you will never need to edit this but it is pos sible e The Project Description field may contain any text that you need to describe the project By default it is empty e The Last saved with ArgoUML field indicates the version of ArgoUML that was used to save this project the last time it was saved This may be usefull if multiple designers have different versions of ArgoUML which may not be backwards compatible all the time Figure 10 10 The dialog for Properties Notation The Notations tab 78 The Menu bar In the Notations tab you are able to set the following fields 10 3 15 The first field is a combobox that allows selection of the project s Notation language By default it lists UML and Java but other languages may be added by plugins See the chapter on Notation for more explanation Section 12 10 Notation Use guillemots
247. esigned to be deployed on this type of node Button 1 double click navigates to the selected entry 23 5 Component Instance A component instance is an instance of a component see Section 23 4 Component which may reside on a node instance see Section 23 3 Node Instance In the UML metamodel ComponentIn 280 Deployment Diagram Artifact Reference stance is a sub class of Instance and is specifically an instance that is derived from a component A component is represented on a class diagram as a box with two small rectangles protruding from its left side labeled with its name A component instance is represented on a sequence diagram in ArgoUML as a box with two small rect angles protruding from its left side labeled with the component instance name if any and component type separated by a colon Tip It is the presence of the colon and the underlining of the name and type that distin guishes a component instance from a component 23 5 1 Component Instance Details Tabs The details tabs that are active for component instances are as follows ToDoltem Standard tab Properties See Section 23 5 2 Component Instance Property Toolbar and Section 23 5 3 Property Fields For Component Instance below Documentation Standard tab Presentation Standard tab The Bounds field defines the bounding box for the component on the diagram Source Standard tab containing just the name o
248. eso Racional Unificado Rational Unified Process RUP de Rational Software www rational com http www rational com Este proceso reconoce que nuestra vista piramidal de porciones iguales de la cascada no es realista En la practica las iteraciones tempranas tienden a ser pesadas en los asuntos de requerimientos de cosas necesitas definir una cantidad razonable incluso para comenzar mientras las iteraciones posteriores tienen mas esfuerzo en las areas de dise o y construcci n RUP reconoce que las iteraciones pueden ser agrupadas en un numero de fases deacuerdo a su etapa en el proyecto global Cada fase puede tener una o mas iteraciones e En la fase del principio inception phase las iteraciones tienden a ser pesadas en asuntos de requeri mientos analisis mientras que cualquier actividad de construcci n debe estar limitada a la emu laci n del dise o dentro de una herramienta CASE e En la fase de elaboraci n elaboration phase las iteraciones tienden a ser completar la especific aci n de los requerimientos y comenzar a centrarse en el analisis y el dise 0 y posiblemente la construcci n del primer codigo real e En la fase de construcci n construction phase los requerimientos y analisis est n mas o menos completos y el esfuerzo de las iteraciones esta mayormente en dise o y construcci n e Finalmente en la fase de desarrollo deployment phase las iteraciones est n centradas sobre la act ividad de la contrucci
249. etails Tabs The details tabs that are active for use cases are as follows ToDoltem Standard tab Properties 172 Use Case Diagram Artifact Reference See Section 17 3 2 Use Case Property Toolbar and Section 17 3 3 Property Fields For Use Case below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The Fill color is used for the use case oval The Display Extension Points check box is used to control whether an extension point compartment is displayed Source Standard tab It would not be usual to provide any code for a use case since it is primarily a vehicle for capturing requirements about the system under construction not creating the solution Tagged Values Standard tab In the UML metamodel UseCase has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed Tip In general the instantiation of use cases is not a major aspect of any design method they are mostly concerned with requirements capture For most OOA amp D methodo logies this tag can safely be ignored e semantics from the superclass Classifier The value is a specification of the semantics of the use case e derived from the superclass ModelElement Values true meaning the use
250. ew context This opens the Add Remove Contexts dialog box see figure below which allows choosing between all possible operations and adding them to the selected list Figure 18 3 The add remove context dialog box 18 10 Reception to be written A reception is 18 11 Association An association on a class diagram represents a relationship between classes or between a class and an interface On a usecase diagram an association binds an actor to a usecase Within the UML metamodel Association is a sub class of both Relationship and General izableElement The association is represented as a solid line connecting actor and usecase or class or interface see Fig ure 18 1 Possible artifacts on a class diagram The name of the association and any stereotype ap pear above the line ArgoUML is not restricted to binary associations See Section 18 11 1 Three way and Greater Associ ations and Association Classes for more on this Associations are permitted between interfaces and classes but UML 1 3 specifies they must only be navigable toward the interface in other words the interface cannot see the class ArgoUML will draw such associations with the appropriate navigation Associations are often not named when their meaning is obvious from the context Note ArgoUML provides no specific way of showing the direction of the association as de scribed in the UML 1 4 standard The naming should attemp
251. exists Predecessors Text area Identifies the messages the completion of whose execution enables this message Button 1 double click navigates to the selected message button 2 gives a pop up menu with one entry e Add Opens a dialog box that allows to select any number of messages See figure below This entry is grayed out when no messages exist Figure 21 3 The add predecessors dialog box 268 Chapter 22 Activity Diagram Artifact Reference 22 1 Introduction This chapter describes each artifact that can be created within an Activity diagram Note that some sub artifacts of artifacts may not actually themselves appear on the diagram There is a close relationship between this material and the Properties Tab of the Details Pane see Sec tion 13 3 Properties Tab That section covers Properties in general in this chapter they are linked to specific artifacts Figure 22 1 Possible artifacts on an activity diagram shows an Activity Diagram with all possible ar tifacts displayed Figure 22 1 Possible artifacts on an activity diagram 22 1 1 Limitations Concerning Activity Diagrams in ArgoUML Activity diagrams are not fully developed yet in ArgoUML Some aspects are not fully implemented or may not behave as expected In particular lacking are call states swim lanes control icons signals sub activities synch states Interactions with other classifiers are provided by an object flow sta
252. f a critic is a critique a statement about some aspect of the model that does not appear to follow good design practice Finally a critique will generally suggest how the bad design issue it has identified can be rectified by raising a to do item Note 93 The Menu bar The critics run as asynchronous processes in parallel with the main ArgoUML tool Changes typically take a second or two to propagate as the critics wake up 10 9 1 Toggle Auto Critique This is a check box controlling whether the critics are running By default it is checked If unchecked then all critics are disabled and any to do items generated by critics the only others being those the de signer has added by hand are hidden in the to do pane 10 9 2 Design Issues This menu entry brings up a dialog box controlling how critics associated with a particular design area are to be handled see Figure 10 22 The dialog for Design Issues Figure 10 22 The dialog for Design Issues ArgoUML categorizes critics according the the design issue they address There are 16 such categories The critics in each category are discussed in detail in the chapter on critics Chapter 15 The Critics The sliders may be set for each category to control the critics that trigger for that category Setting a slider to Of f will disable all critics in that category and remove all associated to do items from the to do pane Setting a slider to a higher
253. f the component instance Caution A component instance should not generate any code so having this tab active is prob ably a mistake Tagged Values Standard tab Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for an Instance 23 5 2 Component Instance Property Toolbar 281 Deployment Diagram Artifact Reference Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected component instance navigating immediately to the properties tab for that stereotype Delete This deletes the component instance from the model Warning This is a deletion from the model not just the diagram To delete a component instance from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 23 5 3 Property Fields For Component Instance Name Text box The name of the component instance By convention component instance names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Component instance has no stereotypes by default in the UML standard Navigate Stereotype icon If a stereotype has been selected this will navi
254. f the cube This means that the three dimensional top and side may be ig nored for example when determining the limits of a diagram for saving graphics Source Standard tab containing just the name of the node instance Caution A node instance should not generate any code so having this tab active is probably a mistake Tagged Values Standard tab Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for an Instance 23 3 2 Node Instance Property Toolbar Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected node instance navig ating immediately to the properties tab for that stereotype Delete This deletes the node instance from the model Warning This is a deletion from the model not just the diagram To delete an node instance from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 23 3 3 Property Fields For Node Instance 277 Deployment Diagram Artifact Reference Name Text box The name of the node instance By convention node instance names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down
255. f this critic allows setting of the treshold i e the maximum number of transitions allowed before this critic fires Caution This number is not stored persistently and there is no way to reduce it after it has been set higher except by creating more transition until the critic fires again Restarting ArgoUML resets this number to its default 10 15 7 2 Reduce States in machine lt machine gt Suggestion that the given state machine has so many states as to be confusing and should be simplified perhaps by breaking into several machines or using a hierarchy The Wizard of this critic allows setting of the treshold i e the maximum number of states allowed be fore this critic fires Caution This number is not stored persistently and there is no way to reduce it after it has been set higher except by creating more states until the critic fires again Restarting ArgoUML re sets this number to its default 20 15 7 3 Add Transitions to lt state gt Suggestion that the given state requires both incoming and outgoing transitions 15 7 4 Add Incoming Transitions to lt artifact gt 141 The Critics Suggestion that the given state requires incoming transitions 15 7 5 Add Outgoing Transitions from lt artifact gt Suggestion that the given state requires outgoing transitions 15 7 6 Remove Extra Initial States Suggestion that there is more than one initial state in the state machine or composite state wh
256. fferent checklists with many possible items Figure 13 18 An example of a checklist for a class Caution In the VO0 20 release of ArgoUML this tab is not completely implemented E g the checks are not saved 132 Chapter 14 The To Do Pane 14 1 Introduction Figure 14 1 Overview of the to do pane shows the ArgoUML window with the to do pane high lighted Figure 14 1 Overview of the to do pane This pane provides access to the advice that comes from the critics processes running within ArgoUML A selector box at the top allows a choice of how the data is presented a button allows the display of the hierarchy to be changed and there is an indicator of the number of to do items identified More information on critics can be found in the discussion of the Critique menu see Section 10 9 The Critique Menu 14 2 Mouse Behavior in the To Do Pane Behavior of the mouse in general and the naming of the buttons is covered in the chapter on the overall user interface see Chapter 8 Introduction 14 2 1 Button 1 Click This action is generally used to select an item for subsequent operations Within the hierarchical display elements which have sub hierarchies may be indicated by when the hier archy is hidden and when the hierarchy is open When these icons are displayed the display of the hierarchy is toggled by button 1 click on these icons Button 1 click over the headline of any to do item will
257. flowstate to the diagram An objectflowstate is an object that is input to or output from an action 12 3 10 Deployment Diagram Specific Tools Ten tools are provided specific to UML artifacts on deployment diagrams The detailed properties of these artifacts are described in the section on deployment diagram artifacts see Chapter 23 Deployment Diagram Artifact Reference Note Remember that ArgoUML s deployment diagrams are also used for component diagrams e Node Add a node to the diagram For convenience when the mouse is over a selected node it dis plays four handles to left right top and bottom which may be dragged to form association relation ships e Node Instance Add a node instance to the diagram For convenience when the mouse is over a selected node instance it displays four handles to left right top and bottom which may be dragged to form link relationships 113 12 4 The Editing Pane Component Add a component to the diagram For convenience when the mouse is over a selected component it displays four handles to left right top and bottom which may be dragged to form de pendency relationships Component Instance Add a component instance to the diagram For convenience when the mouse is over a selected component instance it displays four handles to left right top and bottom which may be dragged to form dependency relationships e Generalization Add a generalization between two artifacts s
258. formance may need to appear in many use cases and it is bad practice to replicate in formation Secondly there are invariably some non functional requirements that are system wide and need a system wide document Hence my preference for a single supplementary requirements specification There should be a section for each of the main areas of non functional requirements The checklist provided by lan Sommerville in his book Software Engineering Third Edn Addison Wesley 1989 is a useful guide e Speed Processor performance user event response times screen refresh time e Size Main memory and possibly caches disc capacity e Ease of use Training time style and detail of help system 37 Captura de Requerimientos e Reliability Mean time to failure probability of unavailability rate of failure availability e Robustness Time to restart after failure percentage of events causing failure probability of data cor ruption on failure e Portability Percentage of target dependent code classes number of target systems To this we should add sections on environment temperature humidity lightening protection status and standards compliance 4 4 Using Use Cases in ArgoUML 4 4 1 4 4 2 ArgoUML allows you to draw use case diagrams When you create a new project it has a use case dia gram created by default named use case diagram 1 Select this by button 1 click on the diagram name in the explorer the upper
259. ftware and the hardware on which it is deployed at run time the deployment dia gram The ArgoUML deployment diagram provides support for both component and deployment diagrams and additionally for object diagrams See Chapter 23 Deployment Diagram Artifact Reference for de tails of the diagram and the artifacts it supports Diagrams are created using the Create drop down menu see Section 10 6 The Create Menu or with the tools on the toolbar see Section 9 4 Create operations Note ArgoUML uses its deployment diagram to create the UML 1 4 component deployment and object diagrams Caution Statechart and activity diagrams are associated with a particular class or operation or the latter also with a package and can only be created when this modelelement has been se lected Warning In ArgoUML version 0 20 the UML 1 4 object diagram as a variant of the class diagram is not directly supported However it is possible to create simple object diagrams within the ArgoUML deployment diagram 16 6 1 Diagram Details Tabs The details tabs that are active for diagrams are as follows ToDoltem Standard tab Properties See Section 16 6 3 Property Fields For Diagram below 16 6 2 Diagram Property Toolbar Go up Navigate up through the package structure of the model Delete This deletes the diagram from the model As a consequence in case of a statechart diagram or an 167 Top Level Artifact
260. g 4 parts of information separated from each other by a dash e The current filename If no filename for the project is set yet then the titlebar shows Unititled e The name of the currently active diagram e The name ArgoUML e An asterisk This item is only present if the current project file is dirty i e it is altered but not yet saved In other words if the asterisk is absent then the current file has not been altered Figure 8 1 Overview of the ArgoUML window At the top of screen is a menu bar which is described in Chapter 10 The Menu bar Below that is the toolbar as described in Chapter 9 The Toolbar The bulk of the window comprises four sub windows or panes Clockwise from top left these are the ex plorer see Chapter 11 The Explorer editing pane see Chapter 12 The Editing Pane details pane see Chapter 13 The Details Pane and to do pane see Chapter 14 The To Do Pane All 4 panes have a tool bar at the top in the details pane it is located under the properties tab An overview of the panes is given in Section 8 3 General Information About Panes Finally at the bottom of the window is a status bar described in Section 8 4 The status bar 8 2 General Mouse Behavior in ArgoUML 8 2 1 Mouse behavior that is specific to the various panes of ArgoUML see Section 8 3 General Informa tion About Panes or the menu bar is discussed in the chapters covering those panes and the
261. g O iio E anh 116 TO 116 129 4 SON leis seer ieegtie sue al E a eed weaned ative E E AE hers 117 129 5 A 30086 ssanttag ss pooceeesegtteantoersestasieag bas EE TGEA 118 12 9 6 Multiplicity seese siise neen e a r a a ke ee 118 129 7 Aggregation cerien eee tied do ees a EPE Sedna seb S E R RE p ie Resa 118 12 9 8 Navigability coronan ii er a EEEa E ESEE EES 119 12 10 Notation nor sas ses a anae IEEE EE EE EEA E AEG AEE 119 12 10 1 Notation Languages 0c ce cece eee ece ence eeeeeeeeeeeeeenees 119 12 10 2 Notation Editing on the diagram 2 0 0 0 cece cece eee e etree eeen es 120 1210 3 Notation Parsing critico bison sede Sor oe dawns neden EE pa 120 13 The Details Panes A reo seo 122 TS eT IntrOducti On meet it dro Coes 122 13 2 ToDo Hen Tabs tie oe es 122 ES NA NOS 123 13 2 2 The Help Button sesen e e EN E EEEN EEEE TEE s 124 13 3 Properties Tab mienie oiread TeRi PEITA PC ESPOR SREE SPIRES ETENE SEES 124 13 4 Documentation Tab ooooccnoccccnocncononoconococononocononocononoconoroconanoronanoronos 125 13 3 Presentation Lab iento ira dois gas Passe aeteeas 126 AE A 127 1357s Constraints Tab escote droits SNR A T oen 128 13 74 The Constraint Editor msie tonen enaa e ae E 130 13 8 Stereotype Tab sic sient aki siden r A E E STESS 131 13 9 Tapped Values Tab sx ccccuetecesvcunessepSsdanes poueses ee ute EE stnee ssh aSecareh wus despsens 132 13 10CGhecklist Tabu i n ars 132 14 The To DO Peto ees 133 14 1 INTO
262. g box pops up as shown in the figure below Figure 21 2 The add context dialog box e Remove Allows removeing classifiers to the list without making use of the dialog box Generalizations Text area Lists any classifierrole that generalizes this classifierrole Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized classifierrole i e for which this classifierrole is a generalization button double click navigates to the generalization and opens its property tab Association End Role Text area Lists the association end roles that are linked to this classifier role Button 1 double click navigates to the selected entry Available Contents Text area Lists the subset of modelelements contained in the base classifier which is used in the collaboration Button 1 double click navigates to the modelelement and opens its property tab Available Features Text box Lists the subset of features of the base classifier which is used in the collaboration button 1 double click navigates to the feature and opens its property tab 260 Collaboration Diagram Artifact Reference 21 3 Association Role An association role is a specialization of an association used to describe an associations behavior in a particular context In the UML metamodel Association Role isa sub class of Association An association role is represented on a collabo
263. gate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records and allows to change the namespace for the component instance This is the package hierarchy Stimuli sent To Be Written Stimuli Received To Be Written Residents Text box Lists any residents see Section 23 4 Component designed to be deployed on this component Button 1 double click navigates to the selected entry Classifiers Drop down selector A Component instance type can be selected here 282 Deployment Diagram Artifact Reference Caution ArgoUML V0 18 lists many more items in the dropdown list then solely Components Beware to select Components only 23 6 Dependency A key part of any component or deployment diagram is to show dependencies For details see Sec tion 18 13 Dependency Caution UML relies on stereotyping of dependencies on component and deployment diagrams to characterize the types of relationship In the current release of ArgoUML there are limita tions in the implementation of dependencies which limit this functionality 23 7 Class A component diagram may show the key internal structure of components including classes within the component For details see Section 18 5 Class Caution Classes can only be added to a component diagram if they already exist in the model by selecting them in the explorer and executing the Add to diagram but
264. gation and composition are used to indicate whole part relationships and by definition the part end cannot be aggregate To fix this identify the part end of the association and use the critic wizard the Next gt button or manually set its aggregation to none using the button 2 pop up menu or the property sheet Composition more correctly called composite aggregation is used where there is a whole part relation ship that is one to one or one to many and the lifetime of the part is inextricably tied to the lifetime of the whole Instances of the whole will have responsibility for creating and destroying instances of the as sociated part This also means that a class can only be a part in one composite aggregation An example of a composite aggregation might be a database of cars and their wheels This is a one to four relationship and the database entry for a wheel is associated with its car When the car ceases to exist in the database so do its wheels Aggregation more correctly called shared aggregation is used where there is a whole part relationship that does not meet the criteria for a composite aggregation An example might be a database of uni versity courses and the students that attend them There is a whole part relationship between courses and 150 The Critics students However there is no lifetime relationship between students and course a student continues to exist even after a course is finished
265. ged Values 196 Attribute Type 198 Attribute Visibility 198 Base of Include Relationship 186 Base Class of Stereotype 165 Base Use Case of Extend Relationship 184 of Extension Point 177 Build 11 15 C Caracteristicas clave en el documento de Visi n 31 CASE 291 Casos de Uso 29 30 Flujo Basico 35 36 Flujos Alternativos 35 36 Jerarqu a 33 Changeability of Association End 216 of Attribute 199 Child of Generalization 181 Class 191 291 Class Details Tabs 191 Class Diagram 188 291 Class Method 293 Class Modifiers 194 Class Name 193 Class Property Fields 193 Class Property Toolbar 192 Class Stereotype 194 Class Tagged Values 192 Clients of Dependency 218 311 Index Code Generation 62 Collaboration 292 Collaboration Diagram 292 Collaborator 292 Comprehension 12 292 Comprension xvii Concept Class Diagram 292 Concurrency of Operation 203 Connections of Association 212 Contexto de Mercado en el documento de Visi n 31 Contexts of Signal 209 Contribuir a el Manual de Usuario 4 Contributing to ArgoUML 2 Cookbook 2 Create Diagram Menu 20 Create Diagram Toolbar 20 Create New Action 267 Actor 38 171 Association in a Use Case Diagram 40 DataType 154 Datatype 189 197 201 205 Enumeration 154 Extend Relationship 182 Extend Relationship in a Use Case Diagram 41 Extension Point 39 174 176 Generalization relationship in a Use Case Diagram 41 Incl
266. generate any code for an association and any code entered here is ignored it will have disappeared when you come back to the association Tagged Values Standard tab In the UML metamodel Association has the following standard tagged values defined persistence Values transitory indicating state is destroyed when an instance is des troyed or persistent marking state is preserved when an instance is destroyed e derived from the superclass ModelElement Values t rue meaning the association is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived associations still have their value in analysis to introduce useful names or concepts and in design to avoid re computation 210 Class Diagram Artifact Reference Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 18 11 3 Association Property Toolbar Go up Navigate up through the package structure of the model For an association this will be the package containing the association New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected association navigat ing immediately to the properties tab for that stereotype Delete This deletes the selected association from the model Warning This is a deletion from the model not just the diagram To
267. hat the activity diagram in the project will not show correctly when reloaded in an old ver sion of ArgoUML again 22 2 1 Action State Details Tabs The details tabs that are active for action states are as follows ToDoltem Standard tab Properties See Section 22 2 2 Action State Property ToolBar and Section 22 2 3 Property fields for action state below Documentation Standard tab Presentation Standard tab The values for the bounds of the action state define the bounding box of the action state Stereotype Standard tab that shows the stereotypes of the action state In the UML metamodel there are no ste reotypes defined by default for a action state Tagged Values Standard tab In the UML metamodel ActionState has no standard tagged values defined 22 2 2 Action State Property ToolBar Go up Navigate up through the containment structure Action states are contained by the otherwise invis ible top state New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected action state navigat ing immediately to the properties tab for that stereotype Delete from Model This deletes the action state from the model Warning This is a deletion from the model not just the diagram It is not possible to delete an action state from the diagram since that concept does not fit the UML standard 270 Activity Diagram Artifact Reference Hence ArgoUML does
268. he artifacts that you have been selecting while navigating the model This button moves you forward to the next one selected after you have used the Navigate Back button to move back If there are no more next artifacts the button is grayed out e Invert Selection This inverts the current selection on the current pane More exact everything that was selected is de selected and everything that was not selected within the current pane is selected 10 4 2 Remove From Diagram Shortcut Delete This removes the currently selected item s from the diagram but not from the model The modelelement can be re added to the diagram by button 2 click on the modelelement in the ex plorer or by dragging it onto the diagram 10 4 3 Delete From Model Shortcut Ctrl Delete This function deletes the selected item s from the model completely If the item to be deleted is also present on another diagram than the current one the dialog box from fig ure X appears Figure 10 12 The dialog for confirmation of Remove from Model 10 4 4 Configure Perspectives This menu item invokes the same dialog as the button at the top of the explorer See Section 11 5 Configuring Perspectives for a complete description 10 4 5 Settings This menu entry brings up a dialog box which allows the user to set various options that control the be havior of ArgoUML see Figure 10 13 The dialog for Settings Preferences 81 The Me
269. he class name and stereotype the second compartment any attributes and the third any operations The last two compartments may optionally be hidden 18 5 1 Class Details Tabs The details tabs that are active for classes are as follows 191 Class Diagram Artifact Reference ToDoltem Standard tab Properties See Section 18 5 2 Class Property Toolbar and Section 18 5 3 Property Fields For Class be low Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The tick boxes Attributes and Operations allow the attributes and operations compartments to be shown the default or hidden This is a setting valid for only the current dia gram that shows the class The Bounds field defines the bounding box for the package on the dia gram Source Standard tab This contains a template for the class declaration and declarations of associated classes Constraints Standard tab There are no standard constraints defined for Class within the UML metamodel Tagged Values Standard tab In the UML metamodel Class has the following standard tagged values defined e persistence from the superclass Classifier Values transitory indicating state is destroyed when an instance is destroyed or persistent marking state is preserved when an instance is destroyed e semantics from the superclass Classifier The value is a specification of the semantics of the class
270. he description of the behavior below The descrip tion of the behavior includes the entry and exit actions and any internal transitions 20 2 1 State Details Tabs The details tabs that are active for states are as follows ToDoltem Standard tab 236 Statechart Diagram Artifact Reference Properties See Section 20 2 2 State Property Toolbar and Section 20 2 3 Property Fields For State below Documentation Standard tab Presentation Standard tab The values for the bounds of the state define the bounding box of the state Stereotype Standard tab Tagged Values Standard tab 20 2 2 State Property Toolbar Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected state navigating im mediately to the properties tab for that stereotype Delete This deletes the state from the model Note This is a deletion from the model not just the diagram You can not just remove a state from the diagram and keep it within the model as is possible in other diagrams 20 2 3 Property Fields For State Name Text box The name of the state By convention state names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Container Text box Shows the container of the state This is the state hierarchy Button 1 double cli
271. he initial set of classes are to be defined The fa cilitator reminds the participants that we are in the analysis phase and are only interested in what needs to be done at the business level and are to leave out anything that smacks of how to do it As a general rule of thumb this means a subset of the nouns from the problem statement see above The group starts with a complete list of all of the nouns in the statement examines each one and decides which are inap propriate crossing them off the list Each class is then assigned to one of the participants 51 Analysis to be continued 5 10 2 Concept Class Diagrams To be written To be written 5 10 2 1 Identifying classes To be written To be written 5 10 2 2 Identifying associations To be written To be written 5 10 3 System Sequence Diagrams To be written To be written 5 10 3 1 Identifying actions To be written To be written 5 10 4 System Statechart Diagrams To be written To be written 5 10 5 Realization Use Cases To be written To be written 52 Chapter 6 Design We now have the problem we are trying to solve specified in the language of a putative solution In the Design Phase we construct all the details of that solution The blurred boundary between Analysis and Design is reflected in their use of many of the same UML tools In this chapter we will mostly be reusing UML technology we have alre
272. he left will populate the fields for that critic The first field on the right is titled Critic Class and then the full name of the class in ArgoUML that implements the critic This name can be used as unique identifier of the critique e g in conversa tions about the critic The first field below this title is a text box labeled Headline giving the complete headline of the crit ic which may be truncated in the list on the left Note In the headline you may see the text lt oc1 gt self lt oc1 gt which will be replaced by the name of the artifact in question when the critic is triggered The next field is a drop down selector labeled Priority The three options available are High Medium and Low and specify the priority category of any to do item generated by this critic This does not alter the priority of the already existing todo items only the newly generated ones Changing the pri ority of a critic is not saved persistently 95 The Menu bar The next field is labeled MoreInfo and contains a URL pointing to further information with a button to the right labeled Go to navigate to that URL Warning In the VO0 20 release of ArgoUML there is no further information available and the Go button is always grayed out and disabled The next field is labeled Description and is a text area with a detailed explanation of what this critic means If the text is too large for the area a scroll bar is provided to the right
273. he selected classifier button 2 click brings a pop up menu with one entry e Add Add a new specification classifier This opens the Add Remove Specifications dialog box see figure below which allows choosing between all possible classifiers and adding or remov ing them to the selected list Figure 18 4 The Add Remove Specifications dialog box 215 Class Diagram Artifact Reference Qualifiers Text box Records the qualifiers for this association end Button 1 double click on this entry will navigate to that qualifier Button 2 click will show a popup menu containing two items Move Up and Move Down which allow reordering the qualifiers Aggregation Radio box with three entries composite none and aggregate Indicates whether the relation ship with the far end represents some type of loose whole part relationship aggregation or tight whole part relationship composite Shared aggregation is shown by a hollow diamond at the whole end of the association Composite aggregation is shown by a solid diamond Note You may not have aggregation at both ends of an association ArgoUML does not en force this constraint The whole end of a composite aggregation should have a multiplicity of one ArgoUML does not enforce this constraint Changeability Radio box with three entries add only changeable and frozen Indicates whether instances of this end of the association end may be i created but not dele
274. hese extension points it adds be havior This makes the use of extend more tightly controlled than general extension and it is thus preferred wherever possible Examples for a travel agent sales system might be the use case for paying for a ticket which has an ex tension point in the specification of the payment Extending use cases may then extend at this point to pay by cash credit card etc Within the UML metamodel Extend is a sub class of Re lationship An extend relationship is represented as a dotted link with an open arrow head and a label extend If a condition is defined it is shown under the extend label see Figure 17 1 Possible artifacts on a use case diagram 17 9 1 Extend Details Tabs 181 Use Case Diagram Artifact Reference The details tabs that are active for extend relationships are as follows Note There is no source tab since there is no source code that could be generated for an extend relationship ToDoltem Standard tab Properties See Section 17 9 2 Extend Property Toolbar and Section 17 9 3 Property Fields For Extend below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds are downlighted since the extend is tied to a particular pair of use cases Source Standard tab You would not expect to generate any code for an extend relationship so this is empty Tagged
275. hin the hierarchical display elements which have sub hierarchies are indicated by when the hier archy is hidden and when the hierarchy is open Button 1 click over the name of any diagram artifact will cause the diagram to be selected and displayed in the editing pane Its details will also be displayed in the details pane Button 1 click over the name of any artifact other than a diagram in the main area of the explorer will cause it to be selected and its details shown in the details pane If the artifact is part of a diagram cur rently displayed in the editing pane it will be highlighted there Note If the artifact is part of a diagram other than that currently displayed in the Editing Pane there will be no change of diagram in the Editing Pane Where button 2 click has been used to bring up a context sensitive pop up menu see below button 1 click is used to select the menu entry required button click outside the menu area will remove it 11 2 2 Button 1 Double Click This has the effect of a button 1 single click and if the tree item was not a leaf it will toggle the hier archy open or close 11 2 3 Button 1 Motion 99 The Explorer Button 1 motion means that you pick up one or more modelelements and drag them to a new location Dropping the modelelement somewhere causes ArgoUML to execute some function that depends on where you drop the modelelements 11 2 3 1 From Explorer to Explorer Releasing the
276. his button is not downlighted when it is not functional i e when no constraint is selected e Edit Constraint This launches the constraint editor in the Constraints tab see Sec tion 13 7 1 The Constraint Editor The editor is invoked on the constraint currently selected in the Constraint Name box Caution In V0 18 of ArgoUML this button is not downlighted when it is not functional i e when no constraint is selected Configure Constraint Editor This a dialog to configure options in the constraint editor see Figure 13 15 Dialog box for configuring constraints Figure 13 15 Dialog box for configuring constraints The dialog box has a check box for the following option e Check type conformance of OCL constraints OCL is strictly typed At the early stages of design it may be helpful to disable type checking rather than follow through all the de 129 The Details Pane tailed specification needed to get type consistency At the bottom are two buttons labeled OK to accept the option changes and Cancel to discard the changes The main body of the constraints tab comprises two boxes a smaller to the left and a larger one to the right The two are separated by two small arrow buttons which control the size of the boxes e Shrink Left Button 1 click on this icon shrinks the box on the left Its effect may be reversed by use of the Shrink Right button see below e Shrink Right Button 1 cl
277. i e for which this node is a generalization Button 1 double click navigates to the specialization and opens its property tab Residents Text box Lists any residents see Section 23 4 Component designed to be deployed on this type of node Button 1 double click navigates to the selected entry 23 3 Node Instance A node instance is an instance of a node where component instances see Section 23 5 Component In stance may reside In the UML metamodel NodeInstance is a sub class of Instance and is spe cifically an instance that is derived from a node A node instance is represented on a deployment diagram in ArgoUML as a three dimensional box labeled with the node instance name if any and node type separated by a colon Tip It is the presence of the colon and the underlining of the name and type that distin guishes a node instance from a node 23 3 1 Node Instance Details Tabs The details tabs that are active for node instances are as follows ToDoltem Standard tab Properties See Section 23 3 2 Node Instance Property Toolbar and Section 23 3 3 Property Fields For Node Instance below Documentation Standard tab 276 Deployment Diagram Artifact Reference Presentation Standard tab The Bounds field defines the bounding box for the node instance on the diagram Warning Beware that in the current release of ArgoUML the bounding box just refers to the front face o
278. ibed here since it is assumed that an ArgoUML user that wants to model for C has basic knowledge of both C and UML Tagged values are one of the main means by which we can define code generation behavior They have a name the tag and a value and are applied to model elements The tagged values in use for the C module have two categories e free format values any St ring is valid except the empty St ring e formated values the value must obey some restrictions e g be one of true or false abbreviated to true false For Boolean tagged values only the values true or false are applicable If a Boolean tagged value does not exist or is invalid for one model element a default value is assumed by the code generator In the bellow documentation the default value is marked Free format tagged values are only significant if present and if the value isn t an empty String When the value must follow some sort of format that is explicitly stated In this case there is the chance that the value is invalid If the value is invalid no assumptions are made the generator will trace the problem and ignore the tagged value Class tagged values constructor true generates a default constructor for the class false default no default constructor is generated unless it is explicitly modeled with the create stereotype header_incl Name of the file to include in the header Note If we desire t
279. ich is not permitted in UML 15 7 7 Place an Initial State Suggestion that there is no initial state in the state machine or composite state 15 7 8 Add Trigger or Guard to Transition Suggestion that a transition is missing either a trigger or guard one at least of which is required for it to be taken 15 7 9 Change Join Transitions Suggestion that the join pseudostate has an invalid number of transitions Normally there should be one outgoing and two or more incoming 15 7 10 Change Fork Transitions Suggestion that the fork pseudostate has an invalid number of transitions Normally there should be one incoming and two or more outgoing 15 7 11 Add Choice Junction Transitions Suggestion that the branch choice or junction pseudostate has an invalid number of transitions Nor mally there should be at least one incoming transition and at least one outgoing transition 15 7 12 Add Guard to Transition Suggestion that the transition requires a guard Caution It is not clear that this is a valid critic It is perfectly acceptable to have a transition without a guard the transition is always taken when the trigger is invoked 15 7 13 Clean Up Diagram This critic is discussed under an earlier design issues category see Section 15 3 3 Clean Up Diagram 15 7 14 Make Edge More Visible 142 The Critics Suggestion that an edge artifact such as an association or abstraction is so short it may be
280. ick on this icon shrinks the box on the right Its effect may be reversed by use of the Shrink Left button see above Finer control can be achieved by using button 1 motion to drag the dividing bar to left and right The box on the left is titled Constraint Name and lists all the constraints if any so far defined for the selected artifact A constraint may be selected by button 1 click The box on the right is labeled Preview and contains the text of the constraint This box only shows some contents if a constraint is selected Where a constraint is too large for the box a scroll bar is provided to the right 13 7 1 The Constraint Editor This is invoked through the use of the Edit Constraint button on the main Constraints tab The constraint editor takes up the whole tab see Figure 13 16 Dialog box for configuring constraints Figure 13 16 Dialog box for configuring constraints Along the top of the tab are a series of icons e Cancel Edit Constraint This exits the constraint editor without saving any changes and re turns to the main Constraints tab e Check OCL Syntax This button invokes a full syntax check of the OCL written in the editor If the syntax is valid the constraint is saved and control returns to the main Constraints tab If the syntax is not valid a dialog box explains the problem Warning Whether type checking is included should be configurable with the Config ure Constraint Editor button s
281. id Conflict This critic is discussed under an earlier design issues category see Section 15 4 2 Revise Attribute Names to Avoid Conflict 15 16 2 Remove lt class gt s Circular Inheritance Suggestion that a class inherits from itself through a chain of generalizations which is not permitted Caution This critic is marked inactive by default in the current release of ArgoUML the only one so marked It will not trigger unless made active 15 16 3 Class Must be Abstract This critic is discussed under an earlier design issues category see Section 15 13 2 Class Must be Ab stract 15 16 4 Remove final keyword or remove subclasses Suggestion that a class that is final has specializations which is not permitted in UML 15 16 5 Illegal Generalization Suggestion that there is a generalization between artifacts of different UML metaclasses which is not permitted Caution It is not clear that such a generalization can be created within ArgoUML It probably indic ates that the diagram was created by loading a corrupt project with an XMI file describing such a generalization possibly created by a tool other than ArgoUML 15 16 6 Remove Unneeded Realizes from lt class gt Suggestion that the specified class has a realization relationship both directly and indirectly to the same interface by realization from two interfaces one of which is a generalization of the other for example Good design depreca
282. iera puede tener una copia gratis del c digo fuente cambiarlo usarlo para nuevos propositos y cosas as La nica gran obligaci n es que t pases tu c digo de la misma forma a otros La naturaleza precisa de que puedes hacer y que no puede varia de un proyecto a otro pero el principio es el mismo La ventaja es que un proyecto peque 0 como ArgoUML subitamente se abre a una gran cantidad de ay uda adicional de aquellos que pueden indagar en sus ideas sobre como el programa puede ser mejorado En cualquier momento pueden ser 10 15 20 o mas personas haciendo contribuciones significantes a ArgoUML Hacer esto comercialmente costar a mas de 1 millon de al a o No es solo un espiritu de puro altruismo Contribuir en un camino para aprender con las manos en la masa sobre software puntero Es una forma de adquirir visibilidad mas de 100 000 personas han descargado ArgoUML hasta la primavera de 2001 Esto es una gran cantidad de buena esperiencia en suma y muchos empleadores potenciales est n viendote Y es genial para el ego El C digo Abierto no excluye ganar dinero Gentleware www gentleware com ht tp www gentleware com vende una versi n comercial de ArgoUML Poseidon Su propuesta de valor 14 OOA amp D basada en UML no es un trozo de c dogo privativo Es el refinamiento comercial y el soporte para librarse de riesgos usando ArgoUML en un desarrollo commercial permitiendo a los clientes tomar ventaja de l
283. ifact Reference pay by cash credit card etc Within the UML metamodel Extension Point isa sub class of ModelElement A use case may display an extension point compartment see Section 17 3 Use Case for details in which extension points are shown with the following syntax name location 17 4 1 Extension Point Details Tabs The details tabs that are active for extension points are as follows ToDoltem Standard tab Properties See Section 17 4 2 Extension Point Property Toolbar and Section 17 4 3 Property Fields For Extension Point below Documentation Standard tab See Section 13 4 Documentation Tab Source Standard tab It would not be usual to provide any code for an extension point since it is external to the system Note The source tab content can be changed but this has no effect Tagged Values Standard tab In the UML metamodel ExtensionPoint has the following standard tagged val ues defined e derived from the superclass ModelElement Values true meaning the extension point is redundant it can be formally derived from other elements or false meaning it cannot Note It is not clear how derived extension points could have any value in analysis 17 4 2 Extension Point Property Toolbar Go up Navigate up to the use case which owns this extension point New Extension Point This creates a new Extension Point below the selected extension poi
284. ification of the semantics of the datatype e derived from the superclass ModelElement Values true meaning the class is redund ant it can be formally derived from other elements or false meaning it cannot Tip While formally available a derived datatype does not have an obvious value and so datatypes should always be marked with derived false 16 3 2 Datatype Property Toolbar Go up Navigate up through the package structure New datatype This creates a new datatype see Section 18 5 Class within the same package as the current data type Tip While it can make sense to create datatypes this way it can be clearer to create them within the package or model where you want them New enumeration literal This creates a new enumeration literal within the datatype navigating immediately to the properties tab for that literal Caution ArgoUML does not actually have a separate concept of a literal The navigation will navigate to the property sheet for an attribute of a class see Section 18 6 Attribute When defining a literal all that matters is its name Other parts of the attribute prop erty sheet should be ignored Also the name of the literal must obey the rules for an Attribute or a critic will fire New Operation This creates a new operation within the datatype navigating immediately to the properties tab for 157 Top Level Artifact Reference that operation New Stereotyp
285. ing of overlapping items There are four reorder options provided Forward The selected artifacts are moved one step forward in the ordering hierarchy with respect to other artifacts they overlap Backward The selected artifacts are moved one step back in the ordering hierarchy with respect to other artifacts they overlap o Front The selected artifacts are moved to the front of any other artifacts they overlap To Back The selected artifacts are moved to the back of any other artifacts they overlap 91 The Menu bar 10 7 4 Nudge This sub menu provides fine adjustment to the positioning of selected artifacts There are four nudge op tions provided e Nudge Left The selected artifacts are moved one pixel to the left e Nudge Right The selected artifacts are moved one pixel to the right e Nudge Up The selected artifacts are moved up one pixel e Nudge Down The selected artifacts are moved up one pixel 10 7 5 Set Preferred Size This menu item acts on all selected items on the current diagram It resets all sizes of all artifacts to its preferred size i e the minimum size for which all text fits inside 10 7 6 Toggle Auto Resizing This menu item is a checkbox that currently does not do anything 10 7 7 Layout This menu item provides an automatic diagram layout function i e when activating this menu item all items on the current class diagram are rearranged according a certain layout algorith
286. ion can have two or more ends For more on association ends see Section 18 12 Association End The names of the association ends are listed unless the association end has no name the case when it is first created in which case anon AssociationEnd is shown Note The only representation of association ends on a diagram is that their name appears at the relevant end of the corresponding association Button 1 double click on an association end will navigate to that end Association Roles Text area To be written Links Text area To be written 18 12 Association End Two or more association ends are associated with each association see Section 17 5 Association Within the UML metamodel AssociationEnd is a sub class of ModelElement The association end has no direct access on any diagram for binary associations The ends of an N ary association may be selected by clicking on the line in the diagram The stereotype name and multiplicity are shown at the relevant end of the parent association see Figure 17 1 Possible artifacts on a use case diagram Where shared or composite aggregation is selected for one association end the opposite end is shown as a solid diamond composite aggregation or hollow diamond shared aggregation Tip Although you can change attributes of association ends when creating a use case model this is often not necessary Many of the properties of an association end rela
287. ipal diagrams all of which are supported by ArgoUML e Use case diagram Used to capture and analyse the requirements for any OOA amp D project See Chapter 17 Use Case Diagram Artifact Reference for details of the ArgoUML use case diagram and the artifacts it supports e Class diagram This diagram captures the static structure of the system being designed showing the classes interfaces and datatypes and how they are related Variants of this diagram are used to show package structures within a system the package diagram and the relationships between particular in stances the object diagram The ArgoUML class diagram provides support for class and package diagrams See Chapter 18 Class Diagram Artifact Reference for details of the artifacts it supports The object diagram is suported on the Deployment diagram e Behavior diagrams There are four such diagrams or strictly speaking five since the use case dia gram is a type of behavior diagram which show the dynamic behavior of the system at all levels e Statechart diagram Used to show the dynamic behavior of a single object class instance This diagram is of particular use in systems using complex communication protocols such as in tele communications See Chapter 20 Statechart Diagram Artifact Reference for details of the ArgoUML statechart diagram and the artifacts it supports e Activity diagram Used to show the dynamic behavior of groups of objects class instance Thi
288. irar el funcionamiento interno de ArgoUML o quieres unirte como desarrollador Esta opci n requiere el JDK completo mira Section 3 4 1 1 Requerimientos del Sistema Las tres opciones est n libremente disponibles a traves del sitio web del proyecto argouml tigris org http argouml tigris org 3 4 1 3 ArgoUML Usando Java Web Start Hay dos pasos para esto 1 Instalar Java Web Start en tu maquina Est disponible en java sun com products javawebstart ht tp java sun com products javawebstart o a traves del enlace Java Web Start en la pagina web http argouml tigris org de ArgoUML 2 Haz click en el enlace Launch latest stable release de la pagina web ht tp argouml tigris org de ArgoUML Java Web Start descargar ArgoUML lo cachear y lo iniciar por primera vez luego en sub 15 OOA amp D basada en UML siguientes inicios comprueba si ArgoUML est actualizado y solo descarga cualquier parte actualizada y luego lo inicia La pagina web http argouml tigris org de ArgoUML tambien proporciona detalles iniciando ArgoUML desde la consola de Java Web Start 3 4 1 4 Descargando el Binario Ejecutable Si escoges descargar el binario ejecutable tendras la elecci n de descargar la ultima versi n estable del c digo la cual ser mas fiable pero no tiene todas las ultimas caracteristicas o la versi n actual la cual ser menos fiable pero tiene mas caracteristicas Escoge deacuerdo con tu situ
289. is to delete the as sociation and recreate it on a diagram whose namespace includes those of all the attached classifiers Caution In the current implementation of ArgoUML this critic does not handle hierarchical namespaces As a consequence it will trigger for associations where the immediate namespaces of the attached classifiers is different even though they are part of the same namespace hierarchy 15 11 2 Add Elements to Package lt package gt Suggestion that the specified package has no content Good design suggests packages are created to put things in Note This will always trigger when you first create a package since you cannot create one that is not empty 15 12 Expected Usage Critics concerning generally accepted good practice in ArgoUML The current version of ArgoUML has one critic in this category 15 12 1 Clean Up Diagram This critic is discussed under an earlier design issues category see Section 15 3 3 Clean Up Diagram y 15 13 Methods 147 The Critics Critics concerning operations in ArgoUML The current version of ArgoUML has the following critics in this category 15 13 1 Change Names or Signatures in lt artifact gt This critic is discussed under an earlier design issues category see Section 15 4 3 Change Names or Signatures in an Artifact 15 13 2 Class Must be Abstract Suggestion that a class that inherits or defines abstract operations must be mark
290. iting Pane outgoing ArgoUML does not enforce this but an ArgoUML critic will complain about any junction that does not follow this rule e Choice Add a choice pseudostate to the diagram Caution A well formed choice should have at least one incoming transition and exactly one out going ArgoUML does not enforce this but an ArgoUML critic will complain about any choice that does not follow this rule e Fork Add a fork pseudostate to the diagram Caution A well formed fork should have one incoming transition and two or more outgoing ArgoUML does not enforce this but an ArgoUML critic will complain about any fork that does not follow this rule e Join Add a join pseudostate to the diagram Caution A well formed join should have one outgoing transition and two or more incoming ArgoUML does not enforce this but an ArgoUML critic will complain about any join that does not follow this rule e Shallow History Add a shallow history pseudostate to the diagram e Deep History Add a deep history pseudostate to the diagram 12 3 9 Activity Diagram Specific Tools Seven tools are provided specific to UML artifacts on activity diagrams The detailed properties of these artifacts are described in the section on activity diagram artifacts see Chapter 22 Activity Diagram Arti fact Reference e Action State Add an action state to the diagram e Transition Add a transition between two action states selected using butto
291. kbox is unmarked attributes in classes are shown without type indication and operations are shown without parameters This feature may be usefull during the analysis phase of your project If all checkmarks in the Notation Tab are un checked then e g for an attribute ArgoUML may show newAttr And for an operation newOp eration Show stereotypes in explorer clear by default If this is selected then ArgoUML will show stereotypes next to the icons of the modelelements in the Explorer i e the tree structure at the left hand side Default shadow width set to by default ArgoUML is able to draw all elements on a dia gram with a shadow for esthetical reasons Use this setting to adjust the size of the shadow used when the modelelement is created The details tab Presentation allows to set the shadow per modelelement after they are created but ArgoUML V0 22 does not retain this latter change after save and load Save Configuration ArgoUML has various user specific configurations that can be set through the Settings entry on the 1 Edit menu see Section 10 4 5 Settings or directly on the various panes Also the main win dow size and location is such a setting Activating this menu entry causes the information to be saved in the file argo user properties The location of this file is in the users home directory which is defined as user home and can be determined as described in Section 10 4 5 2
292. ked through the keyboard shortcuts Ct r1 X Ctrl C and Ct r1 V respectively 13 10 Checklist Tab Conducting design reviews and inspections is one of the most effective ways of detecting errors during software development A design review typically consists of a small number of designers implementers or other project stakeholders holding a meeting to review a software development artifact Many devel opment organizations have developed checklists of common design problems for use in design review meetings Recent research indicated that reviewers inspecting code without meeting makeing use of these checklists are just as effective as design review meetings Hence a checklist feature has been added to ArgoUML that is much in the spirit of design review checklists However ArgoUML s checklists are integrated into the design tool user interface and the design task A software designer using ArgoUML can see a review checklist for any design element The Checklist tab presents a list of check off items that is appropriate to the currently selected design element For ex ample when a class is selected in a design diagram the checklist tab shows items that prompt critical thinking about classes See the figure below Designers may check off items as they consider them Checked items are kept in the list to show what has already been considered while unchecked items prompt the designer to consider new design issues ArgoUML supplies many di
293. l a use case is se lected 2 Select the use case on the editing pane with button 1 click and then select its property tab in the de tails pane A button 2 click over the Extension Points field will bring up a context sensitive pop up menu Select Add to add a new extension point If any extension points already exist they will be shown in this field on the property tab The new ex tension point will be inserted immediately before the entry over which the pop up menu was invoked This ordering can be changed later by using the Move Up and Move Down entries on the pop up menu Whichever method is used the new extension point is selected and its property tab can be displayed in the details pane The name and location of the extension point are free text set in the corresponding fields of the property tab An existing extension point can be edited from its property tab The property tab can be reached in two ways 1 If the extension point compartment for the use case is displayed on the diagram select the use case with button 1 click and then select the extension point with a further button 1 click The property tab can then be selected in the details pane 2 Otherwise select the use case and its property tab in the details pane A button 1 click on the desired entry in the Extension Points field will bring up the property tab for the extension point in the details pane The name and location fields of the extension poi
294. l problema prueba la lista de correo de usuario mira Section 3 4 1 5 Problemas Descargando e JRE equivocada El problema mas com n es no tener una versi n de Java Runtime Environment su ficientemente moderna debe ser 1 4 o posterior e Lenguaje equivocado Si el producto aparece en un idioma que no sabes o no quieres leer vete a el se gundo item de menu por la izquierda en la parte superio de la pantalla Selecciona la entrada de menu mas baja en la lista desplegada Figure 3 5 Estableciendo Idioma en el Panel de Apariencia muestra esto en Ruso Luego haz click en la segunda solapa por abajo en la columna de solapas de la izquierda Despliega la lista como se muestra en Figure 3 5 Estableciendo Idioma en el Panel de Apariencia y selecciona un idioma Puedes ver que los idiomas esta listados en ellos mismos El idioma seleccionado en la muestra es Alem n donde la palabra para Alem n es Deutsch Tendras que salir de ArgoUML y reiniciarlo para que los cambios hagan efecto Usa el boton X de ar riba a la derecha Figure 3 4 Encontrando el Asistente de Configuraci n Figure 3 5 Estableciendo Idioma en el Panel de Apariencia El Interfaz de Usuario de ArgoUML Antes de empezar el Caso de Estudio necesitas familiarizarte con el interfaz de usuario Comienza ley endo la introducci n a la Referenc a de la Interfaz de Usuario Mira Chapter 8 Introduction Mientras pasas a traves de este tutorial se te
295. laci n de extensi n muestra el diagrama de casos de uso del Cajero con una relaci n de extensi n a un caso de uso para reparaciones no programadas El diagrama se est volviendo bastante complejo y as lo hemos dividido en dos uno para el lado del mantenimiento el otro para el uso del cliente y audit or a 33 4 3 3 Captura de Requerimientos El caso de uso Mantener Equipamiento define un nombre Unsched al comienzo de su descripci n El caso de uso extendido Unscheduled Repair es adjuntado ah cuando el Cajero detecta un error in terno Figure 4 5 Diagrama de casos de uso para un sistema de Cajero Autom tico mostrando una relaci n de extensi n Los casos de uso pueden ser enlazados juntos de una forma adicional Un caso de uso puede ser una gen eralizaci n de un caso de uso subsidiario o alternativamente el subsidiario es una especializati n del caso de uso principal Esto es muy parecido a la relaci n de extension pero sin la limitaci n de puntos de extensi n espe cificos en los cuales el caso de uso principal puede ser extendido y sin condiciones sobre cuando puede ser usado el caso de uso subsidiario La generalizaci n est representada en un diagrama de casos de uso por una flecha con una linea con tinua y una punta de flecha blanca desde el subsidiario al caso de uso principal Esto puede ser util cuando un caso de uso subsidiario especializa el comportamiento del caso
296. lassifier roles used as the specifier level and the instance level A classifier role is represented on a sequence diagram in ArgoUML as a plain box labeled with the clas sifier role name if any and classifier separated by a colon Caution A classifier role should properly also show object name if any preceding the classifier role name and separated from it by a slash This allows classifier roles in a specifica tion level diagram to be distinguished from instances in an instance level diagram ArgoUML does show the slash but there is no way to define the instances 21 2 1 Classifier Role Details Tabs The details tabs that are active for classifier roles are as follows ToDoltem Standard tab Properties See Section 21 2 2 Classifier Role Property Toolbar and Section 21 2 3 Property Fields For Classifier Role below Documentation Standard tab Presentation Standard tab Source Standard tab but with no contents Caution A classifier role should not generate any code so having this tab active is probably a mistake Tagged Values Standard tab In the UML metamodel Classifier Role has the following standard tagged val ues defined e persistence from the superclass Classifier Showing the permanence of the state in formation associated with the classifier role Values transitory state is destroyed when the classifier role is destroyed and persistent state is preserved when the
297. le at a time Separating the two areas in the lower half of the dialog are buttons labeled gt gt and lt lt The first of these transfers the rule selected in the library on the left to the list of rules on the right i e it adds a rule to the perspective The second one transfers the rule selected on the right to the library list on the left 1 e 1t removes a rule from the perspective If you hover the mouse over the horizontal line that separates the two halves of the dialog then you see 1t change shape to indicate that you can grab this line and drag it up or down All three titles of the lists show the number of items in the list ArgoUML V0 20 has 8 default perspect 1ves and 68 rules in the library to build perspectives from The buttons at the top right are explained as follows e New This creates a new perspective from scratch with no rules selected with an automatically gener ated name e Remove This removes the selected perspective e Duplicate This creates a copy the selected perspective so it can be used as the basis of a new per spective The new one is named Copy of followed by the original name Move Up This moves the selected perspective one place up in the list This button is downlighted for the topmost perspective Move Down This moves the selected perspective one place down in the list This button is down lighted for the last perspective e Restore Defaults This restores all perspectives and
298. le selection dialog for Import Sources Those fields that are the same as Open Project behave in the same way see Section 10 3 2 Open Project Next to the All Files file filter there is the default filter Java Source File java 75 The Menu bar The first of the two tabs is labeled General and is selected by button 1 click on its tab It provides a combo box for the language selection in VO 18 of ArgoUML only Java can be chosen and the follow ing selections e Descend directories recursively If enabled the default reverse engineering will track through sub directories for any further Java files If not it will restrict to the selected directory e Changed new files only If enabled the default only changed and new files are imported If not all classes will be replaced e Create diagrams from imported code If you unselect this then no diagrams are created i e all data will only be visible in the explorer e Minimise Class icons in diagrams If enabled then the attributes and operations com partiments will not be shown in the classes on the generated class diagrams Note This item is checked by default and is overseen by many users which are then surprised by the result Perform Automatic Diagram Layout If selected then ArgoUML will do its best to layout the generated diagrams automatically If not then all items will be placed at the top left corner of the diagram e Level of i
299. le text box Shows the Bound of the Synch state Which is a positive integer or the value un limited represented by a specifying the maximal count of the SynchState The count is the dif ference between the number of times the incoming and outgoing transitions of the synch state are fired Incoming Text area Lists any incoming transitions for the final state Button 1 double click navigates to the selected transition Outgoing Transitions Text area Lists any outgoing transitions for the final state Button 1 double click navigates to the selected transition 256 Cha pter 21 Collaboration Diagram Artifact Reference 21 1 21 1 1 Introduction This chapter describes each artifact that can be created within a collaboration diagram Note that some sub artifacts of artifacts on the diagram may not actually themselves appear on the diagram There is a close relationship between this material and the properties tab of the details pane see Sec tion 13 3 Properties Tab That section covers Properties in general in this chapter they are linked to specific artifacts Caution Collaboration diagrams are not fully developed yet in ArgoUML Many aspects are not fully implemented or may not behave as expected In particular there are some serious problems with layout of the collaboration roles and messages Figure 21 1 Possible artifacts on a collaboration diagram shows a collaboration diagram with
300. limina images tutorial editoverview gif del sistema de archivos 3 4 2 3 El Panel de Detalles Note Tar a de Lectura e Item Tar as Pendientes Trata las diferencias con otras etiquetas sobre localizaciones de items seleccionados Mantiene detalles para tratarlos en el Panel de Tar as Pendi entes 18 OOA amp D basada en UML e Propiedades Documentaci n e Presentaci n Fuente e Constantes Estereotipo Valores Etiquetados Lista de Validaci n e Elimina images tutorial detailsoverview gif del sistema de archivos 3 4 2 4 El Panel de Tar as Pendientes Note e Tar a de Lectura e Describe prioridades e Resolver items e Relationa a una etiqueta de Item Pendiente en el panel de detalles e Elimina images tutorial todooverview gif del sistema de archivos 3 4 2 5 La Barra de Men y Barras de Herramientas La barra de men y las barras de herramientas dan acceso a todas las caracteristicas principales de ArgoUML As las opciones de men convencionales y de la barra de herramientas que no est n disponibles estan sombreadas y los items de men que invocan un cuadro de dialogo est n seguidos por una elipsis Men Archivo Te permite crear un nuevo proyecto guardar y abrir poryectos importar fuentes desde cualquier sitio cargar y guardar el modelo en y desde una base de datos imprimir el modelo guardar los gr ficos del modelo guardar la configuraci n del model
301. list separated by commas Every entry is a pair of the form name type The return type expression is the type UML datatype class or interface of the result returned 199 Class Diagram Artifact Reference Finally the whole entry is shown in italics if the operation is declared abstract 18 7 1 Operation Details Tabs The details tabs that are active for operations are as follows ToDoltem Standard tab Properties See Section 18 7 2 Operation Property Toolbar and Section 18 7 3 Property Fields For Opera tion below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The Bounds field does allow editing but the changes have no effect Source Standard tab This contains a declaration for the operation Constraints Standard tab There are no standard constraints defined for Operation within the UML metamod el Tagged Values Standard tab In the UML metamodel Operation has the following standard tagged values defined semantics The value is a specification of the semantics of the operation e derived from the superclass ModelElement Values true meaning the operation is re dundant it can be formally derived from other elements or false meaning it cannot Note Derived operations still have their value in analysis to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass f
302. ll become directories namespaces or both 7 2 2 Generating code from interactions and state ma chines This conversion is not as straight forward as the conversion of the static structure It is much more de pending on the target language and target platform In general it is only possible to say the following for interactions e A message is converted into a function call The class of the recipient will have to have a function with the correct name and signature The sender function in the class of the sender will have a call to the function in the recipient e An asynchronous message is converted to either posting a message to be handled by some other thread or a function call to a function that starts a new thread The following describes one possible way to generate state machines e A State Machine is generated to a set of member variables that each method in this class refer to when deciding behavior e A State is generated to a closed set of combination of values on these member variables e An Event is generated as a call to a member method that can change the state These methods would then typically have one big switch statement splitting on the current state 63 Code Generation Reverse Engineering and Round Trip Engineering e A Guard is generated to an if statement in the event member method in the branch for the correct state e A Transition is generated as an assignment of some state variable e An Acti
303. ll eet ds ie dad da 14 3 4 Fundam ntos de ArgoUML pirri seier ensipainos pes Peai EIEEE PRESPOR SETE 15 3 4 1 Empezando soi io er ea o e raae losin ods EEE EEE its 15 3 4 2 El Interfaz de Usuario de ArgoUML ooooccccccnccnnccnnconnconnccnnconnconncos 17 34 3 Salida ssis a as th Mes EEVEE EE SEE EEEE EEE REE 24 3 4 4 Trabajando Con Criticas de Dise 0 ooooccoccnnconnconnccnnconnconiconicnnnns 26 3 5 El Casos de Estudio A escribir ccceccecece cence cece cence sence ee eeneaeeeeaeenens 28 4 Captura de Requerimientos ecet e E r EE S T EEE SEN 29 AD is navies sen O 29 4 2 El Prodeso de Captura de Requerimientos occooccnnconnconoconicnnncnnncnnneninonicnno 29 42 ly Pasos del Proceso conti 30 4 3 Salida del Proceso de Captura de Requerimientos oocoooccnncnnccnnncnnncnnconicnnns 30 4 3 1 Documento d AA A e E EEE 31 4 3 2 Diagrama de Casos de USO ooocococonoconcconccnnonnnccnnconoconccnnconncinncinns 31 4 3 3 La Especificaci n de Casos de USO oocoooccnnccnnconoconocnnocnnocnnicnninnn 34 4 3 4 Supplementary Requirement Specification coooconoccnccnnccnnnnnnccnncnnos 37 4 4 Using Use Cases in ArgoUML ssis rni essees oaod t niske isep I Era ESTs S ks 38 AAT ACTOS A does Guu bs 38 AAD Use CASES e ae a eE a T e at ia 38 FA Z ASSOCIALIO S syreenin e i AEE NE a i EARS 40 4 4 4 Hierarchical Use Cases coccoococonococononocononocononoconococonanoconanoronanonos 41 A ASS Stereotypes e rn e
304. lorer describen la barra de menu y cada una de las subventanas de la interfaz de usuario cono 1 3 3 Introducci n cidas como Paneles Chapter 15 The Critics da detalles de todas las criticas cognitivas dentro del sistema Finalmente ArgoUML enlazar directamente con este manual cuando se de notificaci n de las criticas Chapter 16 Top Level Artifact Reference es una visi n general de los artefactos p e las entidades UML que pueden ser colocadas en diagramas dentro de ArgoUML Los siguientes cap tulos Chapter 17 Use Case Diagram Artifact Reference hasta Chapter 24 Built In DataTypes Classes Inter faces and Stereotypes describen los artefactos que pueden ser creados por medio de cada diagrama de ArgoUML y sus propiedades tambien como algunos artefactos estandar proporcionados con el sistema Se proporciona un Glossary completo Appendix A Supplementary Material for the Case Study propor ciona material para suplementar el estudio de caso usado a lo largo del documento Appendix B UML resources y Appendix C UML Conforming CASE Tools identifican la informaci n subyacente en UML y las herramientas CASE UML Appendix F Open Publication License es una copia de la GNU Free Documentation License Una ambici n futura es proporcionar un indice exhaustivo Retroalimentaci n por el Usuario Por favor cuentanos que piensas sobre el Manual de Usuario Tus comentarios nos ayudar n a hacer mejoras Envia por e mail tus id
305. ly used through its specific stereotype realize to define realization dependencies which link artifacts that specify behavior to the corresponding artifacts that im plement the behavior In the UML metamodel Abstraction is a sub class of Dependency and through that Relation ship An abstraction with stereotype realize is represented on a class diagram as a dotted line with a solid white head at the specifying end Caution All other stereotypes of abstraction should be represented using an open arrow head but this is not supported by ArgoUML 18 16 1 Abstraction Details Tabs The details tabs that are active for abstractions are as follows ToDoltem Standard tab Properties See Section 18 16 2 Abstraction Property Toolbar and Section 18 16 3 Property Fields For Ab straction below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds of the abstraction are downlighted since the association is tied to particular artifacts Source Standard tab This contains the single downlighted text N A Tagged Values Standard tab In the UML metamodel Abstraction has the following standard tagged values 222 Class Diagram Artifact Reference defined e derived from the superclass ModelElement Values true meaning the abstraction is re dundant it can be formally derived from other elements or false meaning it cannot
306. m This function currently only works for classdiagrams For all other types of diagrams the menu item is downlighted 10 8 The Generation Menu This menu provides support for code generation from UML diagrams The functionality is built around the structural information of class diagrams Note Without any plugin modules installed ArgoUML supports only code generation of Java ArgoUML V0 20 supports the following languages by plugin C C php4 php5 Warning Code generation is still very much a work in progress The current version of ArgoUML will generate a structural template for your code but is not able to handle behavioral spe cifications to generate code for the dynamic behavior of the model 10 8 1 Generate Selected Classes This menu entry brings up a dialog box for the ArgoUML code generator see Figure 10 21 The dialog for Generate Selected Classes 92 The Menu bar Figure 10 21 The dialog for Generate Selected Classes Below a label Available Classes the dialog box lists each of the selected classes by name with a check box to the left for each language installed All the checkboxes are initially unchecked Checking any of these boxes will cause code generation for that class Checking multiple languages for a class causes it to be generated in all these languages The buttons Select All and Select None may help when a lot of items have to be selected or deselected In the lower
307. m http www rational com en el cual tres de los investigadores clave en el campo Booch Jacobson y Rumbaugh estuvieron invol ucrados Produjeron documentos describiendo UML v0 9 y v0 91 durante 1996 El esfuerzo fu to mado ampliamente por la industria a traves del Object Management Group OMG ya bien conocido por el estandar CORBA Una primera propuesta 1 0 fu publicada al comienzo de 1997 con una me jorada versi n 1 1 aprobada ese oto o ArgoUML est basado en UML v1 4 la cual fu adoptada por OMG en Marzo del 2000 La versi n oficial actual es UML v1 5 fechada en Marzo del 2003 para ser reemplazada pronto por una revisi n mayor UML v2 0 la cual esta en sus etapas finales de estandarizaci n y se espera completa en 2006 3 2 Procesos Basados en UML para OOA8D Es importante comprender que UML es una notaci n para OOA amp D No describe ning un proceso en particular Cualquier proceso adoptado llevar al sistema por un n mero de fases para ser construido 1 Captura de Requerimientos Esto es donde identificamos los requerimientos para el sistema usando el lenguaje del dominio del probrema En otras palabras describimos el problema en los terminos del cliente 3 2 1 3 2 1 1 OOA amp D basada en UML dominio de la solution En esta etapa aunque pensando en terminos de una soluci n aseguramos mantener las cosas a un alto nivel lejos de detalles concretos de una soluci n especifica lo que es co
308. m the dia gram but keep it within the model use the main menu Remove From Diagram or press the Delete key 17 2 3 Property Fields For Actor Name Text box The name of the actor The diagram shows this name below the stick man figure Since an actor is a classifier it would be conventional to Capitalize the first letter and initial letters of any component words e g RemoteSensor Note ArgoUML does not enforce any naming convention for actors Stereotype Drop down selector Actor is provided by default with the UML standard stereotypes meta class powertype process thread utility for classifiers Stereotypes are of limited value with actors The stereotypes machine organization person and singleton are probably of most use However they are not provided by default with ArgoUML Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the actor This is the package hierarchy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that this actor cannot be instantiated but must always be special ized 171 Use Case Diagram Artifact Reference Caution While actors can be specialized and generalized it is not clear that an abstract actor has any meaning Perhaps it might be used to indicate an actor that does not itself inte
309. ma de conector entre otros elementos otro movimiento boton 1 que no sea en una asa causar que se cree una nueva asa permitiendo al conector ser articulado en ese punto Estos nuevas asas pueden ser eliminadas moviendolas al final del conector 5 Movimiento boton 2 Este es usado para seleccionar elementos en un men sensible al contexto mostrado por el uso de un click del boton 2 Hay otros comportamientos mas especificos que ser n encontrados bajo los casos especificos donde son usados 3 4 2 7 Dibujando Diagramas En general los diagramas son dibujados usando la barra de herramientas del panel de edici n para se leccionar el objeto deseado y haciendo click en el diagrama en la posici n requerida como se describe en Section 3 4 2 6 El Rat n Esa secci n tambien explica el uso del rat n para redimensionar obje tos Los objetos que ya est n en el modelo pero no en un diagrama pueden ser a adidos a un diagrama se leccionando el objeto en el explorador usando Agregar al Diagrama del men desplegado boton 2 sobre ese objeto y entonces haciendo click button 1 en la posici n deseada en el diagrama Ademas de objetos UML la barra de herramaientas del panel Edici n proporciona para los objetos de dibujados generales rectangulos circulos lineas poligonos curvas texto formas de proporcionar in formaci n suplementaria para los diagramas 3 4 2 7 1 Moviendo Elementos de Diagrama Hay muchas maneras para mover
310. mbien una herramienta que convierte XMI a HTML Para mas informaci n mira ht tp www objectsbydesign com projects xmi_to_html_2 html ht tp www objectsbydesign com projects xmi_to_html_2 html 3 4 3 3 1 Usando XMI de Rational Rose 3 4 3 3 2 Usando Models Creados por Poseidon En el di logo Exportar proyecto a XMI asegurate de dejar en blanco la selecci n de Guardar con datos de diagrama 3 4 3 3 3 Usando Modelos Creados por MagicDraw 3 4 3 3 4 XMI Compatibilidad con otras versiones de ArgoUML Las versiones de ArgoUML anteriores a 0 19 7 soportaban UML 1 3 XMI 1 0 Despues de este tiempo el formato de almacenamiento es UML 1 4 XMI 1 2 el cual no es compatible hacia atras Posteriores versiones de ArgoUML leer n proyectos escritos con versiones antiguas pero no vice versa Si puedes 25 OOA amp D basada en UML necesitar volver a una version antigua de ArgoUML deber as ser cuidadoso de guardar una copia de se guridad de tus viejos proyectos Adicionalmente si escribes archivos XMI que necesitan ser leidos por otras herramientas deber as to mar en cuenta las diferentes versiones Las herramientas de modelado UML mas modernas deber an leer 1 4 pero puedes tener generadores de c digo integrados o otras herramientas que est n atadas a UML 1 3 3 4 3 3 5 Importando Otros Formatos XMI dentro de ArgoUML La compatibilidad XMI entre herramientas de modelado UML ha mejorado con los a os pero puedes tener a
311. mented extend and include relation ships by using a stereotyped dependency relationship Although such diagrams will show correctly on the diagram they will not link correctly to the use cases and should be re placed by proper extend and include relationships using the current system 17 2 Actor An actor represents any external entity human or machine that interacts with the system providing in put receiving output or both Within the UML metamodel actor is a sub class of classifier The actor is represented by a stick man figure on the diagram see Figure 17 1 Possible artifacts on a use case diagram 17 2 1 Actor Details Tabs The details tabs that are active for actors are as follows ToDoltem 169 Use Case Diagram Artifact Reference Standard tab Properties See Section 17 2 2 Actor Property Toolbar and Section 17 2 3 Property Fields For Actor be low Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab The fill color is used for the stick man s head Source Standard tab Usually no code is provided for an actor since it is external to the system Note The source tab content can be changed but the changes are not retained Constraints Standard tab ArgoUML only supports constraints on Classes and Features Attributes Operations Receptions and Methods so this tab is grayed out Tagged Values Standard tab
312. mento o seguir creando tu primer dia grama 3 5 El Casos de Estudio A escribir A escribir 28 Chapter 4 Captura de Requerimientos 4 1 Introducci n La captura de requerimientos el el proceso de identificar que quiere el cliente del sistema propuesto La clave en esta etapa es que estamos en el dominio de problema En esta etapa debemos describir todo desde la perspectiva del cliente y en el lenguaje del customer El mayor riesgo que tenemos en la caputra de requerimientos es empezar pensando en terminos de pos ibles soluciones Eso debe esperar hasta la Fase de Analisis mira Chapter 5 Analysis Uno de los pasos de la Fase de Analisis ser tomar los resultados de la Fase de Requerimientos y refundirlos en el len guaje de la soluci n estimada Recuerda que estamos usando un proceso incremental y iterativo Podemos tranquilamente volver atras otra vez al proceso de requerimientos mientras desmontamos el problema en trozos mas peque os cada uno de los cuales debe tener sus requerimientos capturados Ciertamente volveremos atras a traves de la fase de requerimientos en cada iteraci n mientras bus camos definir los requerimientos del sistema mas y mas Note La unica parte de la notaci n de los requerimientos especificada por el estandar UML es el diagrama de casos de uso El resto es especifico del proceso El proceso descrito en este capitulo est muy inspirado en el Rational Unified Proces
313. ments document or whatever you know about the de sired result for a starting point The nouns that are found in whatever you are starting from are a good key to an initial set of classes in the system In a brainstorming session there should be little or no dis cussion of the ideas Record them and filter the results after the brainstorming At this stage the distinc tion between class and object is blurred Once a reasonable set of classes has been defined by the group responsibilities can be added Add re sponsibilities that are obvious from the requirements or the name of the class You don t need to find them all or any for that matter The scenarios will make them more obvious The advantage of finding some in the beginning is that it helps provide a starting place Select the initial scenarios from the requirements document by examining it s verbs in much the same way that we scanned its nouns earlier Then as many walk through sessions as necessary to complete the analysis phase are performed When is enough of the analysis complete that design can begin When all the different responsibilities are in place and the system has become stable After all the normal behavior has been covered excep tional behavior needs to be simulated When you notice that the responsibilities are all in place to sup port the new scenarios and there is little change to the cards this is a sign the you are ready to start design Concept Diagram To be wri
314. menu Remove From Diagram or press the Delete key 18 2 3 Property Fields For Package Name Text box The name of the package The name of a package like all packages is by convention all lower case not containing any periods Note By default a new package has no name defined The package will appear with the name anon Package in the explorer Stereotype Drop down selector Package is provided by default with the UML standard stereotypes for package facade framework metamodel stub topLevel systemModel Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 18 4 Stereotype Namespace Drop down selector Records the namespace for the package This is the package hierarchy Visibility Radio box with four entries public private protected and package Indicates whether the package is visible outside the package Modifiers Check box with entries aostract leaf and root e Abstract is used to declare that this package cannot be instantiated but must always be spe cialized Tip The meaning of abstract applied to a package if not that clear It might mean that the package contains interfaces or abstract classes without realizations This is probably better handled through stereotyping of the package for example facade 190 Class Diagram Artifact Reference e Leaf indicates that this package can have no further sub
315. missed Move the connected artifacts apart to make the edge more visible 15 7 15 Composite Association End with Multiplicity gt 1 An instance may not belong by composition to more than one composite instance You must change the multiplicity at the composite end of the association to either 0 1 or 1 1 1 for your model to make sense Remember that composition is the stronger aggregation kind and aggregation is the weaker The prob lem can be compared to a model where a finger can be an integral part of several hands at the same time This is the second well formedness rule on AssociationEnd in UML 1 4 Design Patterns Critics concerning design pattern usage in ArgoUML 15 8 These relate to the use of patterns as described by the so called Gang of Four ArgoUML also uses this category for critics associated with deployment and sequence diagrams The current version of ArgoUML has the following critics in this category 15 8 1 Consider using Singleton Pattern for lt class gt The class has no non static attributes nor any associations that are navigable away from instances of this class This means that every instance of this class will be identical to every other instance since there will be nothing about the instances that can differentiate them Under these circumstances you should consider making explicit that you have exactly one instance of this class by using the singleton Pattern Using the singleton pattern ca
316. mouse button above a namespace makes the modelelement owned by the namespace In the Package centric explorer perspective this means a straigh forward drag and drop function Use this drap and drop feature to easily move e g classes from one package into another 11 2 3 2 From Explorer to Diagram Dropping a modelelement on the diagram is the equivalent of the Add to Diagram function Hence if the diagram did not yet show this modelelement it is added Use this drap and drop feature e g to easily create a diagram from imported XMI files This because XMI files contain all the modelelements but not any diagram information 11 2 4 Button 2 Actions When used in the the explorer this will display a selection dependent pop up menu Menu entries are highlighted but not selected and sub menus exposed by subsequent mouse motion without any but tons Menu entry selection is with button 1 or button 2 11 2 5 Button 2 Double Click This has no effect other than that of button 2 single click 11 3 Keyboard Behavior in the Explorer All keys active in a tree widget have their normal behaviour When a diagram is selected pressing Ctrl C will copy the diagram in GIF format to the system clip board 11 4 Perspective Selection The artifacts in the ArgoUML model may be configured for displaying in the tree by a number of per spectives To this end a drop down at the top allows selection of the explorer perspective Below tha
317. mport detail Classifiers only Classifiers plus feature specifications Full import The latter is the default e Import source file encoding The value Cp1252 is often the default This string repres ents the coded character set identifier CCSID The second of the two tabs is labeled Java and is selected by button 1 click on its tab It provides two pairs of radio boxes e The first radio box allows selection between modeling attributes of Java classes as UML attributes the default or as UML associations to the class specified e The second radio box allows selection between modeling arrays as new datatypes in their own right the default or as their base datatype with multiplicity 10 3 9 Page Setup This brings up the standard dialog box provided by the operating system to adjust printer paper size ori entation and other options 10 3 10 Print Shortcut Ctrl P This brings up the standard dialog box provided by the operating system allowing the current diagram to be printed out In some cases when the printing is started the dialog box of Figure 10 8 The diagram exceeds page size dialog appears Selecting the Fit to page button does print the whole diagram fitted on one page by scaling it down Which might cause all text to be too small to read in case of big diagrams but it is a quick and easy way to get an usable printout Selecting the Multiple pages option does print unscaled by dividing
318. n 201 of Package 190 of Parameter 205 of Signal 208 of Stereotype 165 of Use Case 174 Namespace of Actor 171 of Dependency 218 of Extend Relationship 184 of Generalization 180 of Include Relationship 186 of Model 155 of Package 190 of Stereotype 165 of Use Case 174 Navigation Pane 99 Setting 40 Tree 99 Navigator Pane 99 Tree 99 New 73 New Action 267 New Actor 171 New DataType 154 New Datatype 189 197 201 205 New Enumeration 154 New Extend Relationship 182 New Extension Point 174 176 New Package 154 New Qualifier 214 264 New Stereotype 154 158 161 177 179 183 185 189 193 197 201 205 208 211 214 217 220 227 234 237 240 244 246 248 250 251 255 259 265 267 270 275 277 279 282 New Use Case 173 Nombre del Caso de Uso 34 Nombre de Caso de Uso 34 314 Index Non functional constraints 37 Non functional requirements 37 O Object 294 Object Constraint Language 294 Object Diagrams 188 Object Management Group 294 Object Method 293 Objetivo del Caso de Uso 34 Objetivo del Caso de Uso 34 Objetivos en el documento de Visi n 31 OCL 294 OMG 294 OOA amp D 294 Open Project 73 Operation 199 Operation Concurrency 203 Operation Details Tabs 200 Operation Modifiers 202 Operation Name 201 Operation Parameter 203 Operation Property Fields 201 Operation Property Toolbar 200 Operation Raised Signals 203
319. n y en particular la prueba del software OOA amp D basada en UML Note Deber a estar claro que la prueba es una parte integral de todas las fases Incluso en las fases tempranas los requerimientos y el dise 0 deberian ser probados y esto es facilitado por una buena herramienta CASE Usaremos un proceso iterativo en este manual que est ligeramente basado en RUP 3 2 1 2 2 Tama o de lteraci n Una buena regla a primera vista es que una iteraci n deber a tomar entre seis y diez semanas para proyectos comerciales tipicos Mas largo y probablemente habras abarcado demasiados requerimientos para hacerlos de una vez Ademas pierdes enfoque en tener la siguiente iteraci n completa Mas corto y probablemente no has tomado en cuenta suficientes requerimientos para hacer un avance significativo En este caso la sobrecarga adicional asociada con una iteraci n puede hacerse un problema El n mero total de iteraciones depende del tama o del proyecto Toma el tiempo estimado trabajando fuera adivinando que es un tema completo en si mismo y dividelo en trozos de 8 semanas La experien cia parece sugerir que las iteraciones se dividiran en una proporcion de alrededor de 1 2 3 3 dentro del estilo RUP de fases de inception elaboration construction y deployment Un proyecto que tiene una gran imprecisi n en su especificaci n algunos proyectos de investigaci n avanzada por ejemplo tenderan a ser mas pesados en sus fases tempranas
320. n 1 motion from the originating action state to the receiving action state e Initial Add an initial pseudostate to the diagram Caution There is nothing to stop you adding more than one initial state to a diagram However to do so is meaningless and one of the critics will complain 112 The Editing Pane e Final State Add a final state to the diagram e Junction Add a junction decision pseudostate to the diagram Caution A well formed junction should have one incoming transition and two or more outgoing ArgoUML does not enforce this but an ArgoUML critic will complain about any junc tion that does not follow this rule e Fork Add a fork pseudostate to the diagram Caution A well formed fork should have one incoming transition and two or more outgoing ArgoUML does not enforce this but an ArgoUML critic will complain about any fork that does not follow this rule e Join Add a join pseudostate to the diagram Caution A well formed join should have one outgoing transition and two or more incoming ArgoUML does not enforce this but an ArgoUML critic will complain about any join that does not follow this rule e CallState Add a callstate to the diagram A call state is an action state that calls a single opera tion Hence the name of the operation being called is put in the symbol along with the name of the classifier that hosts the operation in parentheses under it e ObjectFlowState Add a object
321. n a context sensitive menu popped up by use of button 2 click 12 3 The tool bar The toolbar at the top of the editing pane provides the main functions of the pane The default tool is the Select tool In general button 1 click on any tool selects a tool for one use before reverting to the default tool and button double click selects a tool for repeated use The tools fall into four categories e Layout tools Provide assistance in laying out artifacts on the diagram e Annotation tools Used to annotate artifacts on the diagram e Drawing tools Used to add general graphic artifacts to diagrams e Diagram specific tools Used to add UML artifacts specific to a particular diagram type to the dia gram Some of the tools that are generally not all used so often are combined in a dropdown to take less space on the toolbar See e g Figure 12 3 The drawing tools selector Press the symbol at the right of the tool to pop it open These drop down tools remember their last used tool persistently This means that when ArgoUML starts they show the last tool that was activated the previous time ArgoUML was run 12 3 1 Layout Tools The following two tools are provided in all diagrams in this category e Select This tool provides for general selection of artifacts on the diagram Button 1 click will se lect an artifact CTRL with button 1 can be used to select or deselect multiple artifacts Button 1 mo tion will move sel
322. n gt gt for Use Cases used to distinguish between Use Cases at the requirements phase defined in terms of the problem domain and Use Cases at the analysis phase defined in terms of the solution domain The document capturing non functional requirements that cannot be associated with Use Cases Scalable Vector Graphics format A standard representation of graphics diagrams that use vectors ArgoUML can export diagrams in SVG 295 Glossary System Sequence Diagram System Statechart Diagram To Do List Transition UML Use Case Use Case Diagram Use Case Specification Vision Document W3C A Sequence Diagram used in the Analysis Phase showing the dy namic behavior of the overall system See Chapter 5 Analysis for more information A Statechart Diagram used in the Analysis Phase showing the dy namic behavior of an active top level system objects See Chapter 5 Analysis for more information A feature of ArgoUML allowing the user to record activities that are yet to be completed The change between States in a Statechart Diagram Universal Modeling Language A graphical notation for OOA amp D processes standardized by the OMG ArgoUML supports UML 1 4 UML 2 0 is in the final stages of standardization and should be com plete during 2006 A UML notation for capturing requirements of a system or sub system See Section 4 3 Salida del Proceso de Captura de Requeri mientos for more informati
323. n is not implemented and this button is always grayed out It is for future development e Edit Network Right now critics are implemented in java code That means end users cannot add new critics 96 The Menu bar The idea of a critic network is that they would be a state machine like diagram with several steps Each step would express a condition which collectively with the other steps associated with that crit ic articulates the rule that the critic is providing If the rule fires then remaining steps would define the steps of the wizard to help the user fix the problem The ideas behind this are discussed in Chapter 4 of Jason Robbins PhD disseration ht tp argoumL tigris org docs robbins_dissertation diss4 html In particular look at Figure 1 6 in this chapter and the related discussion A suggested implementation is that the conditions could be written in OCL against the UML meta model A library of predefined conditions and steps would allow end users to build new critics by combining those in novel ways Caution In the V0 20 version of ArgoUML this function is not implemented and this button is always grayed out It is for future development Finally the bottom right of the dialog contains a button labeled OK Button 1 click here dismisses the dialog 10 10 The Tools Menu This menu provides a generic menu attachment point for any plug ins provided with ArgoUML The standard system has no plug in
324. n or explanation of the ele ment to which it is attached Since this tagged value applies to every artifact it is given its own tab in the details pane rather than being part of the Tagged Values tab Figure 13 7 A typical Documentation tab on the details pane shows a typical documentation tab for an artifact in ArgoUML Figure 13 7 A typical Documentation tab on the details pane As you can see many more fields have been added to the Documentation field alone The other fields similarly store their information under tagged values author version since deprecated see The fields on this tab are the same for all artifacts Since UML comments are a kind of documentation they are also shown on this tab with name and 125 13 5 The Details Pane body e Author A text box for the author of the documentation e Version A text box for the version of the documentation e Since A text box to show how long the documentation has been valid e Deprecated A check box to indicate whether this artifact is deprecated i e planned for removal in future versions of the design model e See Pointers to documentation outside the system Documentation Literal text of any documentation Comment Name The names of all comments attached to the modelelement e Body The bodies of all comments attached to this modelelement Tip ArgoUML is not primarily a documentation system For artifacts that require heavy doc
325. n save time and memory space Within ArgoUML this can be done by using the singleton stereotype on this class If it is not your intent to have a single instance you should define instance variables i e non static at tributes and or outgoing associations that will represent differences bewteen instances Having specified class as a singleton you need to define the class so there can only be a single instance This will complete the information representation part of your design To achieve this you need to do the following 1 You must define a static attribute a class variable holding the instance This must therefore have class as its type 2 You must have only private constructors so that new instances cannot be made by other code The creation of the single instance could be through a suitable helper operation which invokes this private constructor just once 3 You must have at least one constructor to override the default constructor so that the default con structor is not used to create multiple instances For the definition of a constructor under the UML 1 4 standard and extensions to that definition accep ted by ArgoUML see Section 15 5 3 Add a Constructor to a Class 15 8 2 Singleton Stereotype Violated in lt class gt 143 The Critics This class is marked with the singleton stereotype but it does not satisfy the constraints imposed on singletons ArgoUML will also accept Singleton ste
326. n the UML metamodel Pseudostate is a sub class of StateVertex The representation of a pseudostate on a statechart diagram in ArgoUML depends on the particular kind of pseudostate initial deepHistory shallowHistory join fork junction and choice ArgoUML lets you place any pseudostate directly by tools for the specific types of pseudostate These are described in sep arate sections below see Section 20 12 Initial State Section 20 14 Junction Section 20 15 Choice Section 20 16 Fork Section 20 17 Join Section 20 18 Shallow History and Sec tion 20 19 Deep History 20 11 1 Pseudostate Details Tabs The details tabs that are active for pseudostates are as follows ToDoltem Standard tab Properties See Section 20 11 2 Pseudostate Property Toolbar and Section 20 11 3 Property Fields For Pseudostate below Documentation Standard tab Presentation Standard tab Stereotype Standard tab containing the stereotypes of the pseudostate In the UML metamodel PseudoState has the no standard stereotypes defined Tagged Values Standard tab In the UML metamodel Pseudostate has no standard tagged values defined 20 11 2 Pseudostate Property Toolbar 249 Statechart Diagram Artifact Reference Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected pseudostate
327. n will pop up the critic headline 115 The Editing Pane e Colored wavy line Used for critics specific to sub components of graphical artifacts For example to underline attributes with a problem within a class e Solid colored line Not seen in ordinary editing but used when a to do item is highlighted from the to do pane see Chapter 14 The To Do Pane by button double click The solid line is used to show all the artifacts affected by the critic for example all stimuli that are out of order 12 7 The Drawing Grid The editing pane is provided with a background grid which can be set in various styles or turned off al together through the menu see Section 10 5 4 Adjust Grid Whatever grid is actually displayed placement of items on the diagram is always controlled by the set ting for grid snap which ranges from 4 to 32 pixels see Section 10 5 5 Adjust Grid Snap 12 8 The Diagram Tab At the bottom of the editing pane is a small tab labeled as As Diagram The concept is that a UML diagram can be displayed in a number of ways for example as a graphical diagram or as a table Each representation would have its own tab and be selected by button 1 click on the tab Earlier versions of ArgoUML did implement a tabular representation but the current release only sup ports a diagram representation so this tab does not have any function 12 9 Pop Up Menus Within the editing pane button 2 click
328. name as another in the current statechart diagram which is bad design and will prevent valid code generation 15 4 12 Revise Name to Avoid Confusion Two names in the same namespace have very similar names differing only by one character Sugges tion this could potentially lead to confusion Caution This critic can be particularly annoying since at times it is useful and good design to have a series of artifacts varl var2 etc It is important to remember that critics offer guidance and are not always correct ArgoUML lets you dismiss the resulting to do items through the to do pane see Chapter 14 The To Do Pane 15 4 13 Choose a Legal Name All artifact names in ArgoUML must use only letters digits and underscore characters This critic sug gests an entity has not met this requirement 15 4 14 Change an Artifact to a Non Reserved Word Suggestion that this artifact s name is the same as a reserved word in UML or within one character of one which is not permitted 15 4 15 Choose a Better Operation Name Suggestion that an operation has not followed the naming convention that operation names begin with lower case letters Caution 138 The Critics Following the Java and C convention most designers give their constructors the same name as the class which begins with an upper case character In ArgoUML this will trig ger this critic unless the constructor is stereotyped create It is importa
329. ncnoconcnoroncnonononos 48 5 2 2 Advanced Class Diagrams To be written oo oocooccncnoconcnnconcnonononos 48 5 3 Creating Class Diagrams in ArgoUML 0 eee cece cence nee ee eece eee eeneees 49 De Sed Classes secs iva A ted O 49 5 3 2 Associations To be written oooocoocococnocnonnnncncnncnncnnncncnnconcnnncnnns 49 5 3 3 Class Attributes and Operations To be written cooccoccoccoccncnoconcnns 49 5 3 4 Advanced Class Features To be written ococoocooccnncncnnconcnnncnnons 49 5 4 Sequence Diagrams To be Written 2 0 0 0 eee cece cence ee ce teen cece een eeneeeee 49 5 4 1 The Sequence Diagram To be written oocooccccccccnnccnnccnnconnccnncono 50 5 4 2 Identifying Actions To be written coooccoccccccnccnnccnnconccnnccnnccnninnns 50 5 4 3 Advanced Sequence Diagrams To be written cooccocccnccnnconnccnncons 50 5 5 Creating Sequence Diagrams in ArgoUML eee ceeeeee eee ce teen eenes 50 5 5 1 Sequence Diagrams esiri onp roto AEE e EE ESS 50 5 5 2 Actions To be written oooococcococcocncnccnonnnncncnnnncncnncnncnnncnnnnnnnnnoos 50 5 5 3 Advanced Sequence Diagrams To be written oooccocccnccnnccnnccnncons 50 5 6 Statechart Diagrams To be Written oocooccocnoconcnoconcnnconcnnconcnoroncnorononnnos 50 5 6 1 The Statechart Diagram To be written 0 0 0 0 cece eee eeeeeeeeer teen eres 50 5 6 2 Advanced Statechart Diagrams To be written oocooccnccoconcnononcnns
330. nconoconoconacnnccnnccnnrcnicnnos 222 18 16 2 Abstraction Property Toolbar ooocoooccncconccnnccnnccnnncnnccnaronicnnos 223 18 16 3 Property Fields For Abstraction oocoooccnoconoconoconocnnncnnrcnaronicnno 223 19 Sequence Diagram Artifact Reference oooccooccnnconoconoconconononcnnncnnaconacnnccnaronose 225 19 1 Introduction osi o e e a se st cased Ere date N E A cdeanas EEES 225 19 1 1 Limitations Concerning Sequence Diagrams in ArgoUML 225 19 2 ODOC cts ccin ve shcses ieee eae oett oTr nt SEEP none cots eee ccsbguvecodeatueassspeutessaeresstiee 225 19 2 1 Object Details Tabs 220 09 seccctecnasscssstoeaacssedssessabriaadesessncsses Esei 226 19 2 2 Object Property Toolbar 2 0 0 0 eee cece eee oa E 227 19 2 3 Property Fields For Object oooocccoccncconcconccnnconoconocnnacnnncnnconono 227 19 3 Stimulus en n NT 228 19 3 1 Stimulus Details Tabs oooooccnnccnnconoconcconconconnconncnnncnnncnononoso 229 19 3 2 Stimulus Property Toolbar 2 0 0 0 cece ee cece eee ceeeeeeeeeeeen teen es 230 19 3 3 Property Fields For Stimulus cece cee cee ce eeee seen eeenes 230 19 4 Stimulus Call gener iss ties saasooa agreed sang eshneed esa adebies GESPOD A EREE S PEES a aSK 231 19 5 Stimulus Create serso in rron aoe EEE O EESE E E aS 232 19 6 Stimulus Destroy w serierne ea r E TE E E e 232 19 7 Stimulus Send eosi nseries ores aaneres EEEE ERE EE EEEE EEEE 232 19 8 Stimulus Return se 3s sccas
331. nctions belong here e g Find and Goto Diagram All changes of settings in this menu apply to all diagrams e g zoom e The Create menu contains all possible diagrams that can be created These functions are context de pendend since they work on the selected modelelement e The Arrange menu allows layout changes in the current diagram which is not the same as the items in the View menu Functions here can not alter the UML model The Generation menu is for Code Generation The functions here work either on the selected modelelements or on the whole project e The Critique menu is specific for settings related to critics which apply for all projects e The Tools menu is currently empty If plugins are installed then their functions appear here e The Help menu contains the usual information and about Mouse Behavior in the Menu Bar Behavior of the mouse in general and the naming of the buttons is covered in the chapter on the overall user interface see Section 8 2 General Mouse Behavior in ArgoUML There is no ArgoUML specif ic behaviour for the menu 72 The Menu bar 10 3 The File Menu These are actions concerned with input and output and the overall management of projects and the ArgoUML system 10 3 1 New Shortcut Ctrl N This initializes a new project within ArgoUML The project is created without a the name It contains a top level Model named unt it ledModel and two empty diag
332. nd Role Property Toolbar and Section 21 4 3 Property Fields For Association End Role below Documentation Standard tab Source Standard tab There is no code generated for an association end role Tagged Values Standard tab In the UML metamodel AssociationEndRole has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the association end role is redundant it can be formally derived from other elements or false meaning it cannot Tip Derived association end roles still have their value in analysis to introduce useful names or concepts and in design to avoid re computation However the tag only makes sense for an association end role if it is also applied to the parent association role Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML 21 4 2 Association End Role Property Toolbar Go up Navigate up to the association role to which this end role belongs Go Opposite This navigates to the other end of the association role New Qualifier This creates a new Qualifier for the selected association end role navigating immediately to the properties tab for that qualifier Warning Qualifiers are only partly supported in ArgoUML V0 18 Hence activating this button creates a qualifier in the model which is not shown on th
333. ne but 228 Sequence Diagram Artifact Reference this still leaves the arrow head showing which is unsightly It is also semantically incor rect anyway to use a destroy action to represent a terminate action 19 3 1 Stimulus Details Tabs The details tabs that are active for stimuli are as follows ToDoltem Standard tab Properties See Section 19 3 2 Stimulus Property Toolbar and Section 19 3 3 Property Fields For Stimulus below Documentation Standard tab Style Standard tab The values for the bounds of the stimulus notionally define the bounding box of the stimulus and its time line However if you change them it will have no effect and the original val ues will be reset when you next revisit the tab Altering the Fill and Shadow entries has no effect Rather bizarrely you can set the Line entry and it will draw a line around the signal which is not a standard UML representation Tip To change the color of the line you should select the associated link click on it a little way from the stimulus and use its style tab see Section 19 9 Link Caution In the current release of ArgoUML changing the values of the Bounds field is pos sible but will make only a temporary change to the position of the stimulus Selecting any artifact on the screen causes the stimulus to return to its original position and the original values to be restored Source Standard tab but with no contents
334. new entry delete an entry or move entries up and down in text areas with multiple entries The first field is almost always a text field Name where the name of the specific artifact can be entered The remaining fields vary depending on the artifact selected The detailed property sheets for all ArgoUML artifacts are discussed in separate chapters for each of the diagram types use case diagram Chapter 17 Use Case Diagram Artifact Reference class diagram Chapter 18 Class Diagram Artifact Reference sequence diagram Chapter 19 Sequence Diagram Arti fact Reference statechart diagram Chapter 20 Statechart Diagram Artifact Reference collaboration diagram Chapter 21 Collaboration Diagram Artifact Reference activity diagram Chapter 22 Activity Diagram Artifact Reference deployment diagram Chapter 23 Deployment Diagram Artifact Reference Property sheets for artifacts that are common to all diagram types have their own chapter Chapter 16 Top Level Artifact Reference Caution ArgoUML will always try to squeeze all fields on to the property sheet If the size of the property tab is too small it may become unusable The solution is to either enlarge the property tab by enlarging the main window or by moving the dividers to left and top 13 4 Documentation Tab Within the UML 1 4 standard all artifacts are children of the Element metaclass The Element metaclass defines a tagged value document ation for comment descriptio
335. ng This is a deletion from the model not just the diagram To delete a extend from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 17 9 3 Property Fields For Extend Name Text box The name of the extend relationship Tip It is quite common to leave extends unnamed in use case analysis Note ArgoUML does not enforce any naming convention for extend relationships Stereotype Drop down selector ArgoUML does not provide any stereotypes by default Tip Stereotyping does not have great value on an extend relationship Note There is no representation of the stereotype of an extend relationship on the diagram 183 Use Case Diagram Artifact Reference Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the extend relationship This is the package hierarchy Button 1 Double Click on the entry will navigate to the package defining this namespace or the model for the top level namespace Base Use Case Drop down selector Shows the use case that is being extended by this extend relationship Button 1 click on this entry will give a drop down menu of all available use cases and an empty entry which may be selected by button 1 click Extension Drop down selector Show the use case that is doing the ex
336. ng CASE Tools soceri ii onea potencien E EEEE etica 300 C 1 Other Open Source Projects To be written ooocooccccccnccnnccnnconnccnnccnnconaconaconase 300 C 2 Commercial Tools To be written o oococconccnccncnncncncnncnncnoncncnncnncnoncnncnannnnoos 300 D The C Module iecmin iii see S E iS rr a 301 Dit Modeling for Cto pta Eae e 301 Dilisl Class tagged Values si00 susesseedsegessyeettestevecads spine suaheent vss westestaeedesene es 301 D 1 2 Attribute tagged Values oooccoccnnccnnccnnconnconeconnconaconcnnncnnncnnncnnncnnronnss 302 D3 Parameters sidad conti wue a E E n tee tend 303 D4 Preserved SCCHONS ii cda dies 303 EB Eimoits and ShortComin gs soei wea gee eres EEEE EEEE eweaesshose shed eum ucsp outs 305 Bil Diagram Canvas SIZE iii iii 305 E 2 Missing A wsapercestapieae ase E a a EE EEE EEE ET 305 F Open Publication License caiete e ene cs ii 306 F 1 Requirements On Both Unmodified And Modified Versions oocccooccncnioccnnccnnnns 306 B22 Copyn ght iii ri O EES E E EEEE E E EES 306 F3 Scope OF DICENSE iesiri n a E E eii E e 306 F 4 Requirements On Modified Works ocooocnnoccnnccnoconoconccnnccnnconnccnnccnncnnnconaconnss 306 F 5 Good Practice Recommendations cee ceee cece eee cn cece eee ece tena eee eeuseeueeeenees 307 F 6 License OPUS certain ino ss ia E asda rcbdacestens 307 F 7 Open Publication Policy Appendix oocccnccnnconccnnccnnccnnconoronccnnccnnccnnccnnconaroni
337. ng the diagram he will see the Java notation too This person can select the UML notation in the File Notation menu and see all diagrams in UML language See Section 10 3 13 Notation Use guillemots for stereotypes clear by default By default ArgoUML uses pairs of less than and greater than lt lt gt gt characters for stereotypes If this box is checked stereotypes on dia grams are shown between true guillemots This feature is presumably added to ArgoUML because guillemots are poorly supported by various fonts and if they are present then they are quite small and poorly visible Independent of the way they are shown when entering stereotypes you can always type real guille mots if your keyboard supports it or their lt lt gt gt equivalents e Show visibility clear by default If this is selected then ArgoUML will show the visibility in dicators in front of e g attributes in the diagram In UML the notation is for public for private for protected and for package E g for an attribute it may show tnewAttr int e Show multiplicity clear by default If this is selected then ArgoUML will show the multipli city of e g attributes in the diagram In UML notation the multiplicity is shown between such as newAttr 0 int This setting has no impact on showing multiplicity near association ends 84 The Menu bar e Show initial value clear by d
338. nguage PGML y Section 3 4 3 3 XMP para ver mas acerca de PGML and XMI respectivamente Todos estos son luego comprimidos en zip en un archivo con extensi n zargo Puedes extraer facil mente el archivo xmi del archivo zargo usando cualquier aplicaci n generica ZIP Intentalo y mira dentro de la magia de Warning Seguramente hacer doble click lanzara una utilidad ZIP si una est instalada y NO Argo 3 4 3 2 Gr ficos e Impresi n 3 4 3 2 1 El Graph Editing Framework GEF GEF es el paquete de software que es el fundamento de los diagramas que aparecen en el Panel de Edici n GEF fu una parte integral de ArgoUML pero ha sido separada Al igual que ArgoUML es un proyecto de c digo abierto disponible via Tigris http www tigris org 3 4 3 2 2 Precision Graphics Markup Language PGMIL PGML es el formato de almacenamiento actual para la informaci n de diagrama usado en ArgoUML En el futuro PGML ser sustituido por el formato UML 2 0 Diagram Interchange 3 4 3 2 3 Aplicaciones Que Abren PGML PGML is un predecesor de SVG mira Section 3 4 3 2 5 Scalable Vector Graphics SVG Fu aban donado por el W3C Consortium Actualmente no hay otras herramientas que conozcamos trabajando en PGML 3 4 3 2 4 Imprimiendo Diagramas Seleciona un diagrama luego vete a Archivo Exportar Diagramas Puedes generar formatos GIF PostScript Encapsulated PostScript o SVG 3 4 3 2 5 Scalable Vector Graphi
339. ning class and any inner classes e protected The operation is available only to the owning class or artifacts that are subclasses of the owning class e package The operation is available only artifacts contained in the same package Modifiers Check box with entries abstract leaf root query and static e abstract This operation has no implementation with this class The implementation must be provided by a subclass Important Any class with an abstract operation must itself be declared abstract e leaf The implementation of this operation must not be overridden by any subclass e root The declaration of this operation must not override a declaration of the operation from a superclass e query This indicates that the operation must have no side effects i e it must not change the state of the system It can only return a value 202 Class Diagram Artifact Reference Caution Operations for user defined datatypes must always check this modifier e static There is only one instance of this operation associated with the class as opposed to one for each instance of the class This is the OwnerScope attribute of a Feature metaclass with in UML Any operation declared static is shown underlined on the class diagram Concurrency Radio box with entries guarded sequential and concurrent e guarded Multiple calls from concurrent threads may occur simultaneously to one instance on any guarded operation
340. nnncnnnonoso 171 UTS Use A coosdscdehy ines oboe Ses saquaden sayeth si dancaaeeahocaasssyethaa dap edteee tens 172 17 3 1 Use Case Details Tabs portada tte 172 17 3 2 Use Case Property Toolbar spessore asepen piis 173 17 3 3 Property Fields For Use Case oooccoccnnoconnccnnconnconoconncnnncnnncnanonoso 174 17 4 Extension POE lt neecctssatoris css dioss r e E E regir ias EE E ES 175 17 4 1 Extension Point Details Tabs ooooconoccnnconoconccnnccnnccnnncnoronicnnos 176 17 4 2 Extension Point Property Toolbar ooococcccnccnnccnnccnnncnnccniconicnnos 176 17 4 3 Property Fields For Extension Point oocoooccnoccnccnnccnnncnncnnncnnicnnos 177 L725 ASSOCLALION 1555 545 sac sstesdente enee A a EEE AEE T EE vest EES 178 17 6 Association End i spinsionens ii oreet eee cee igh rE ES o EEIE S IE ETS 178 17 7 Dependency e Baty cde A EE a N E ANE E NS 178 17 8 Generalizations a cee e Te e E A Ea Eeo 178 17 8 1 Generalization Details Tabs eee cece ce eeceeeee teen teen es 178 17 8 2 Generalization Property Toolbar ooocoooccnnconoconoconccnnncnononinonoso 179 17 8 3 Property Fields For Generalization ooocoooccnccnnccnnccnnncnnccnnccnicnnos 180 A cians c8s ee te ane See doe haem bene thee do a E EA E O EE 181 17 9 1 Extend Details Tabs oooncooccnnccnnconnconoconnconoconaconccnnccnnronicnno 181 17 9 2 Extend Property Toolbar oocccoccnnccnnconcconcconoconaconacnnccnnrcnncnno 182 17 9 3 Property Fields
341. nocido como abstracci n 3 Dise o Tomamos la especificaci n de la fase de Analisis y construimos la soluci n con todo de talle Nos estamos moviendo de la abstracci n del problema a su realizaci n en terminos con cretos 4 Fase de Construcci n Tomamos el dise o actual y lo escribimos en un lenguaje de programaci n real Esto incluye no solo la programaci n si no tambien la prueba de que el programa cumple los requerimientos verificaci n probando que el programa realmente resuelve el problema del cliente validacion y escribiendo toda la documentaci n de usuario Tipos de Procesos En esta secci n miramos a los dos tipos principales de procesos en us por la ingenier a del software Hay otros pero son menos ampliamente usados En a os recientes ha habido tambien un movimiento para reducir el esfuerzo requerido en desarrollar software Esto ha llevado al desarrollo de un numero de variantes ligeras de procesos a menudo conoci das como computacion agil o programaci n extrema que son apropiadas para equipos muy peque os de ingenieros El Proceso en Cascada En este proceso cada etapa del proceso requerimientos analisis y construccion codigo y prueba es completada antes que la siguiente comienze Esto se ilustra en Figure 3 1 El Proceso en Cascada Figure 3 1 El Proceso en Cascada Este es un proceso muy satisfactorio donde los requerimientos est n bien dise ados no se espera que cambien por ejempl
342. nos 139 15 5 3 Add a Constructor to a Class cooccoccocnoconcnnconcnnroncnnconcnnroncnnronos 139 15 5 4 Reduce Attributes on a Class cooccoccocnoconcnoconcnnconcnoroncnoroncnnnonos 140 15 6 Planned Extensions oooooocoronororononorononoronororon oro reno nono rono rotor rnronernronos 140 15 6 1 Operations in Interfaces must be public coooccconcccnnccccnnccnnicnnnns 140 15 6 2 Interfaces may only have operations oocoooconoccnncnnccnnccnnccnnrcnncnnos 140 15 6 3 Remove Reference to Specific Subclass cece cece cece eeeee eee ee ee 141 15 7 State Machines cirio artista da lA road edi eee 141 15 7 1 Reduce Transitions on lt State gt oocoocooccoconcnoconcnoconcnnroncnnroncnnnonos 141 15 7 2 Reduce States in machine lt machine gt coocooccncnnconcnnconcnnconcnnnonos 141 15 7 3 Add Transitions to lt state gt coocoocnoconcnoconcnoconcnorononoconcnnronanaronos 141 15 7 4 Add Incoming Transitions to lt artifact gt 1 0 0 0 cece cece eeeeeeee eee 141 15 7 5 Add Outgoing Transitions from lt artifact gt 2 0 0 0 eee eeee eee 142 15 7 6 Remove Extra Initial States ooccoccocnoccncnnconcnnconcnnroncnnronanaronos 142 15 7 7 Place an Initial State ea coors ccoo das votes ca rara cas serene 142 15 7 8 Add Trigger or Guard to Transition 2 0 0 0 cece eee cence eee eee ee 142 15 7 9 Change Join Transitions ooccoccnnconnccnncnnnconnconoconaconacnnccnnronicnno 142 15 7 10 Change Fork Transitions
343. not actually themselves appear on the diagram There is a close relationship between this material and the Properties Tab of the Details Pane see Sec tion 13 3 Properties Tab That section covers Properties in general in this chapter they are linked to specific artifacts Figure 20 1 Statechart diagram artifacts 1 and Figure 20 2 Statechart diagram artifacts 2 show statechart diagrams with most possible artifacts displayed Figure 20 1 Statechart diagram artifacts 1 Figure 20 2 Statechart diagram artifacts 2 20 1 1 Limitations Concerning Statechart Diagrams in ArgoUML The statechart diagrams support the 7 action types defined CallAtion CreateAction DestroyAction ReturnAction SendAction TerminateAction and UninterpretedAction but there is no way to use the same action more than once Also in a few cases it is not possible to set or select the related elements e g there is no way to select a signal for a SendAction Code generation from statechart diagrams is not developed yet 20 2 State A state models a situation during which some usually implicit invariant condition holds for the parent class This invariant may be a static situation such as an object waiting for some external event to occur or some dynamic activity in progress A state is represented on a statechart diagram in ArgoUML as a rectangle with rounded corners with a horizontal line separating the name at the top from t
344. nown for CORBA and UML Object Oriented Analysis and Design An approach to software problem analysis and design based on objects which encapsulate both data and code See See Section 1 1 1 Analisis Orientado a Objeto y Dise o or any standard textbook on Software Engineer ing UML is a notation to support OOA amp D A theory within cognitive psychology suggesting that although de signers plan and describe their work in an ordered hierarchical fash ion in actuality they choose successive tasks based on the criteria of cognitive cost Simply stated designers do not follow even their own plans in order but choose steps that are mentally least expens ive among alternatives A sub window within the main window of the ArgoUML user inter face A Use Case where the Use Case Diagram and Use Case Specifica tion are in the language of the solution domain rather than the prob lem domain A theory within cognitive psychology which observes that designers of complex systems do not conceive a design fully formed Instead they must construct a partial design evaluate reflect on and revise it until they are ready to extend it further As developers work hands on with the design their mental model of the problem situ ation improves hence improving their design 294 Glossary Requirement Capturing Responsibility Scenario Sequence Diagram SGML Simula 67 State Statechart Diagram Stereotypes and
345. nsitions ArgoUML will not let you create such transitions and if you import a model that has such transitions a critic will complain There can be at most one initial pseudostate in a composite state which must have at most one outgo ing transition An initial state is represented on the diagram as a solid disc 20 13 Final State If a transition reaches a final state it implies completion of the activity associated with that composite state or at the top level of the complete state machine In the UML metamodel FinalState is a child of State Note A final state is a true state with all its attributes not a pseudostate Completion at the top level implies termination i e destruction of the owning object instance The representation of a final state on the diagram is a circle with a small disc at its center 20 13 1 Final State Details Tabs The details tabs that are active for final states are as follows ToDoltem Standard tab Properties See Section 20 13 2 Final State Property Toolbar and Section 20 13 3 Property Fields For Final State below Documentation Standard tab Presentation Standard tab Stereotype Standard tab containing the stereotypes of the final state In the UML metamodel a Final State has the no standard tagged values defined Tagged Values Standard tab In the UML metamodel Final State has no standard tagged values defined 20 13 2 Final State Property Toolba
346. nstance is destroyed or persistent marking state is preserved when an instance is destroyed e derived from the superclass ModelElement Values t rue meaning the association is re 261 Collaboration Diagram Artifact Reference dundant it can be formally derived from other elements or false meaning it cannot Note Derived association roles still have their value in analysis to introduce useful names or concepts and in design to avoid re computation Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for an Association Role 21 3 2 Association Role Property Toolbar Go up Navigate up through the package structure Delete This deletes the association role from the model Warning This is a deletion from the model not just the diagram To delete an association role from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 21 3 3 Property Fields For Association Role Name Text box The name of the association role which is shown on the diagram By convention associ ation role names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Association role is provided by default with the U
347. nstrained Drag When holding down the Ctrl key while dragging with mouse button 1 down on a diagram the movement of the dragged element element will be constrained to one of eight cardinal directions North South East West NE SE SW NW 68 Introduction 8 2 8 Button 2 Actions Button 2 actions are all dependent on the pane or menu bar and discussed in their various chapters 8 2 9 Button 2 Double Click Button 2 actions are all dependent on the pane or menu bar and discussed in their various chapters 8 2 10 Button 2 Motion Button 2 actions are all dependent on the pane or menu bar and discussed in their various chapters 8 3 General Information About Panes The four sub windows of the main ArgoUML window are called panes Clockwise from top left these are the explorer see Chapter 11 The Explorer editing pane see Chapter 12 The Editing Pane details pane see Chapter 13 The Details Pane and to do pane see Chapter 14 The To Do Pane At the top the editing pane is a fool bar 8 3 1 Re sizing Panes You can re size panes by dragging on the divider bars between them To indicate this possibility the mouse cursor changes shape when hovering over the divider bars In addition you will see there are two small left pointing arrows within the vertical divider bars one at the top of the vertical divider bar between explorer and editing pane and one at the top of the vertical di vider bar between to do pane
348. nstraint DataType Exception Flow Generalization Interface Link Model ModelElement Node NodeInstance ObjectFlowState Operation Package Permission Signal Subsystem and Usage or the artifact classes that derive from them The stereotype will then be available to artifacts that derive from that same metaclass or that artifact Namespace Drop down selector Records the namespace for the stereotype This is the package hierarchy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that artifacts that use this stereotype cannot be instantiated but must always be specialized e Leaf indicates that artifacts that use this stereotype can have no further sub types while Root indicates it is a top level artifact Caution Remember that these modifiers apply to the artifacts using the stereotype not just the stereotype Warning ArgoUML neither imposes nor checks that artifacts using a stereotype adopt the ste reotype s modifiers Generalizations Text area Lists any stereotype that generalizes this stereotype 165 Top Level Artifact Reference Caution It is not clear that generalizing stereotypes makes much sense Specializations Text box Lists any specialized stereotype i e for which this stereotype is a generalization Caution It is not clear that specializing stereotypes makes much sense 16 6 Diagram The UML standard specifies eight princ
349. nt navigating immediately to the properties tab of the newly created extension point 176 Use Case Diagram Artifact Reference New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected extension point nav igating immediately to the properties tab for that stereotype Delete This deletes the selected extension point from the model 17 4 3 Property Fields For Extension Point Name Text box The name of the extension point Tip It is quite common to leave extension points unnamed in use case analysis since they are always listed within use cases and extend relationships by their location Note ArgoUML does not enforce any naming convention for extension points Stereotype Drop down selector ArgoUML does not provide any stereotypes for extension points Tip Stereotyping does not have great value on an extension point Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Location Text box A description of the location of this extension point within the owning use case Tip Extension points are always listed within use cases and extend relationships by their location Typically this will be the number name of the paragraph in the specification Base Use Case Text box Shows the base use case within which this extension point is defined Button 1 Double Click will naviga
350. nt may then be edited As a shortcut where the extension point compartment is displayed double click on the extension point allows text to be typed in directly This is parsed to set name and location for the extension point Extension points may be deleted or their ordering changed by using the button 2 pop up menu over the Extension Points field in the use case property tab Having created an extension point it will appear in the explorer upper left quadrant of the user screen 39 Captura de Requerimientos Extension points are always shown in a sub tree beneath their owning use case 4 4 3 Associations To join a use case to an actor on the diagram use button 1 click on the association icon on the editing pane toolbar Hold button 1 down at the use case move to the actor and release button 1 or alternat ively start at the actor and finish at the use case This will create a straight line between actor and use case You can segment the line by holding down button 1 down on the line and moving before releasing A vertex will be added to the line which you can move by button 1 motion A vertex can be removed by picking it up and sliding to one end of the line Multiple associations can be added in one go by using button 1 double click on the association icon Each subsequent button 1 down motion release sequence will join an actor to a use case Use button on the select icon to stop adding associations
351. nt to remember that critics offer guidance and are not always correct ArgoUML lets you dismiss the resulting to do items through the to do pane see Chapter 14 The To Do Pane 15 4 16 Choose a Better Attribute Name Suggestion that an attribute has not followed the naming convention that attribute names begin with lower case letters 15 4 17 Capitalize Class Name Suggestion that a class has not followed the naming convention that classes begin with upper case let ters Note Although not triggering this critic the same convention should apply to interfaces 15 4 18 Revise Package Name Suggestion that a package has not followed the naming convention of using lower case letters with peri ods used to indicated sub packages 15 5 Storage Critics concerning attributes of classes The current version of ArgoUML has the following critics in this category 15 5 1 Revise Attribute Names to Avoid Conflict This critic is discussed under an earlier design issues category see Section 15 4 2 Revise Attribute Names to Avoid Conflict 15 5 2 Add Instance Variables to a Class Suggestion that no instance variables have been specified for the given class Such classes may be cre ated to specify static attributes and methods but by convention should then be given the stereotype 2 2utility 15 5 3 Add a Constructor to a Class You have not yet defined a constructor for class class Constructors initialize new in
352. ntext of the ActivityGraph on its details pane 10 6 7 New Deployment Diagram This menu entry creates a blank deployment diagram and selects that diagram in the editing pane Tip Artifacts from other namespaces packages can be added from the explorer by dragging or by using Add to Diagram from the button 2 pop up menu 10 7 The Arrange Menu This menu provides a range of functions to help in the alignment of artifacts on diagrams within the edit ing pane In general the menu function invoked is applied to any artifact or artifacts currently selected in the editing pane 10 7 1 Align This sub menu aligns the selected items There are seven alignment options provided e Align Tops Aligns the selected artifacts by their top edges e Align Bottoms Aligns the selected artifacts by their bottom edges e Align Rights Shortcut Ctrl R Aligns the selected artifacts by their right edges 90 The Menu bar 10 7 2 Align Lefts Shortcut Ctrl L Aligns the selected artifacts by their left edges Align Horizontal Centers Aligns the selected artifacts so their horizontal centers are in a vertical line Align Vertical Centers Aligns the selected artifacts so their vertical centers are in a hori zontal line Align To Grid Aligns the selected artifacts so their top and right edges are on the grid snap boundary see Section 10 5 5 Adjust Grid Snap edge Tip The alignment is to the current grid snap set
353. nu bar Figure 10 13 The dialog for Settings Preferences The options that can be set up on the various tabs are described in the following sections For each tab there are three buttons at the bottom of the dialog box e OK Activating this button button 1 click applies the chosen settings and exits the dialog e Cancel Selecting this button button 1 click exits the dialog without applying any settings changed since the last Apply or since the dialog started if Apply has not been used e Apply Selecting this button button 1 click applies the chosen settings and remains in the dialog Closing the dialog with the close button in the top corner in the border of the window causes the same effect as Cancel These settings are saved persistently for use by subsequent ArgoUML sessions 10 4 5 1 Preferences Tab Selecting the Preferences tab button 1 click on the tab gives the following options as check boxes e Show Splash Panel set by default If enabled ArgoUML will show a small panel with a picture while starting up Tip The splash panel can be seen by using the Help menu see Section 10 11 2 About ArgoUML e Preload Common Classes set by default If enabled ArgoUML creates class objects of a num ber of classes internally during start up so that instantiation is quicker when they are needed Reload last saved project on startup clear by default Check this item if you al ways work on the same proje
354. numeration makes much sense Generalizations Text area Lists any enumeration that generalizes this enumeration Specializations Text box Lists any specialized enumerations i e for which this enumeration is a generalization Operations Text area Lists all the operations defined on this enumeration Button 1 double click navigates to the selected operation button 2 click brings up a pop up menu with two entries e Move Up Only available where there are two or more operations and not at the top It is moved up one the operation selected is e Move Down Only available where there are two or more operations listed and the operation se lected is not at the bottom It is moved down one See Section 18 7 Operation for details of operations Caution ArgoUML treats all operations as equivalent Any operations created here will use the same mechanism as operations for classes Remember that operations on enumerations must have no side effects they are read only This means the query modifier must be checked for all operations Literals Text area Lists all the enumeration literals defined for this enumeration Button 1 double click nav igates to the selected literal button 2 click brings up a pop up menu with two entries e Move Up Only available where there are two or more literals and the literal selected is not at the top It is moved up one Move Down Only available where there are two or mor
355. nvoked state machine 242 Statechart Diagram Artifact Reference reaching its final state The non default entry and exits are specified through stub states In the UML metamodel StubState is a child of State Every Stub State has a label on the diagram which corresponds to the pathname represented by the Reference State attribute of the stub state The description of the details panels of a stub state is almost identical to that of a pseudo state see Sec tion 20 11 Pseudostate and so is not duplicated here The only difference is one additional field Reference Stat Drop down selector Allows entering the path name of the reference state 20 8 Transition A transition is a directed relation between a source state any kind e g composite state and a destina tion state any kind e g composite state Within the UML metamodel Transition is a sub class of ModelElement A transition is represented on a statechart diagram in ArgoUML as a line with arrow connecting the source to the destination state Next to this line is a string containing the following three parts The trig ger event e g a Call Event which may have parameters between brackets Next follows if any the guard in square brackets Finally if there is an effect e g Call Action defined a slash fol lowed by the expression of the action 20 8 1 Transition Details Tabs The details tabs that are active for transitions
356. o automatizar un sistema manual bien probado La debilidad de este enfoque se muestra problemas menos bien definidos Invaliablemente algunas de las incertidumbres en los requerimientos no ser n clarificados hasta bien entrado el analisis y el dise o o incluso en fases de codificaci n requiriendo volver atras para rehacer trabajo El peor aspecto de esto es que no cuentas con codigo que funcione hasta cerca del final del proyecto y muy a menudo es solo en esta etapa en la que los problemas con los requerimientos originales por ejem plo con la interfaz de usuario se hacen visibles Esto est exacerbado por cada etapa sucesiva requiriendo mas esfuerzo que la anterior as que los costos del decubrimiento de un problema tard 0 son enormemente caros Esto esta ilustrado por la pir amide en Figure 3 2 Esfuerzo Involucrado en los Pasos del Proceso en Cascada Figure 3 2 Esfuerzo Involucrado en los Pasos del Proceso en Cascada El proceso en cascada es probablemente a n el proceso de dise 0 dominante Sin embargo debido a sus limitaciones esta cada vez mas siendo sustituido por procesos iterativos particularmente por proyec tos donde los requerimientos nos est n bien definidos OOA amp D basada en UML 3 2 1 2 Procesos de Desarrollo Iterativo En a os recientes un nuevo enfoque ha sido usado el cual anima a conseguir al menos una parte del codigo funcionando tan pronto como sea posible para conseguir descubrir probl
357. o de Cr tica Re visa el Nombre del paquete UntitledModel muestra como deber a verse tu pantalla ahora Figure 3 10 Ventana ArgoUML Mostrando el Elemento de Cr tica Revisa el Nombre del paquete UntitledModel Observa que tu selecci n est destacada en rojo en el Panel de Tar as Pendientes y que una explic aci n completa aparece ahora en el Panel de Detalles el panel de abajo a la derecha Puedes tener que redimensionar tu Panel de Detalles o desplazarloa hacia abajo para ver el mensaje completo como se muestra en nuestro ejemplo Lo que ArgoUML est intentando decirte es que normalmente los nombres de paquetes est n escritos en minusculas El paquete principal por defecto creado por ArgoUML se llama unt it ledModel y por tanto viola un principio de dise 0 Realmente este podr a ser considerado como un bug dentro de ArgoUML pero es adecuado para demostrar el funcionamiento de las cr ticas En este punto puedes escoger cambiar el nombre del paquete manualmente para imponer silencio en la cr tica de dise o por alg n tiempo o permanentemente o para requerir una explicaci n mas extensa por e mail de un experto No haremos nada de esto volveremos a ello cuando hablemos sobre las cr ticas de dise 0 con mas detalle pero usaremos otra pr ctica caracteristica de ArgoUML una caracteristica de autocor recci n Para hacerlo solo hac click en el boton Siguiente Pr ximo del Panel de Detalles Esto causara que un ai
358. o have multiple headers included this way just use multiple tagged val ues with header_incl as the tag 301 The C Module Other tagged values used for C modeling may also be used this way This note won t be repeated in those cases source_incl Name of the file to include in the source cpp file typedef_public lt source type gt lt type_name gt creates typedef line in the public area of the class with typedef lt source type gt lt type name gt typedef_protected Same as typedef_public but in protected area typedef_private Same as typedef_public but in the private area typedef_global_header Same as typedef_public but in the global area of the header typedef_global_source Same as typedef_global_source but in the source file TemplatePath Directory will search in the specified directory for the template files header_template and cpp_template which are placed in top of the corresponding file The following tags in the template file are replaced by model values IFILENAMEI IDATEI IYEARI IAUTHORI IEMAILI If no such tag is specified the templates are searched in the subdirectory of the root directory for the code gen eration email name domain country replaces the tag IEMAILI of the template file author name replaces the tag IAUTHORI of the template file Note You may simply use the Author property in the documentation property panel D 1 2 Attribute tagge
359. o y salir de ArgoUML Men Editar Te permite seleccionar uno o mas elementos UML en un diagrama deshacer y rehacer ediciones eliminar elementos de diagramas o el modelo completo vaciar la papelera y cambiar la configuraci n Men Visualizar Te permite cambiar entre diagramas encontras objetos en el modelo hacer zoom en un diagrama seleccionar una representaci n de diagrama particular aunque en este momento solo 19 OOA amp D basada en UML hay una seleccionar una etiqueta particular en el men de detalles ajustar la rejilla ver botones en una selecci n y cambiar entre notaci n UML y Java Men Crear Diagrama Te permite crear cualquiera de los siete tipos de diagrama UML clases casos de uso estados actividad colaboraci n desarrollo y secuencia soportados porArgoUML Los diagramas de estado y actividad solo pueden ser creados cuando una clase o actor es seleccion ado incluso las entradas relevantes del men estar n sombreadas si esto no se ha realizado Men Colocar Arreglo Te permite alinear distribuir reordenar y desplazar objetos en un diagrama y establecer la estrategia de distribuci n del diagrama Men Generar Te permite generar c digo Java para las clases seleccionadas o para todas las clases Men Cr tica Te permite cambiar el estado de la funci n de auto cr tica entre activado y des activado establecer el nivel de importancia de los problemas de dise o y metas de dise o y ins
360. of modules that can not be removed and a button to test the concept Pressing this button adds a useless menu item on the Tools menu nothing else Notice also that this is a new modules concept so the old Pluggable modules do not work this way and are not listed 10 4 5 7 Extra Tabs added by Plugins A plug in module has the possibility to add extra tabs One example is C it adds the following tab Figure 10 18 The dialog for Settings C 10 5 The View Menu This menu is used for actions that affect how the various panes are viewed 10 5 1 Goto Diagram This menu entry brings up a dialog box describing all the diagrams in the current project under ArgoUML Figure 10 19 The dialog for Goto Diagram The dialog box contains a table with three columns and one row for each diagram in the current project 85 The Menu bar A scroll bar gives access if the table is too long for the box Double button 1 click on any row will select that diagram in the editing pane The three columns are as follows e Type Lists the type of diagram e Name Lists the name given to the diagram e Description Shows how many nodes and edges there are on the diagrams A node is a 2 D ar tifact and an edge is a connector artifact This dialog box is not modal which allows it to remain open while editing the model for easy naviga tion Warning The V0 22 implementation of ArgoUML does not inmediately update the di
361. ol selector Dependency Add a dependency between two artifacts selected using button 1 motion from the de pendent artifact Generalization Add a generalization between two artifacts selected using button 1 motion from the child to the parent Extend Add an extend relationship between two artifacts selected using button motion from the extended to the extending use case Include Add an include relationship between two artifacts selected using button 1 motion from the including to the included use case Add Extension Point Add an extension point to a selected use case The extension point is given the default name newEP and location loc Where the extension point compartment is dis played the extension point may be edited by button 1 double click and using the keyboard or by se lecting with button 1 click after the use case has been selected and using the property tab Otherwise it may be edited through its property tab selected through the property tab of the owning use case Note 108 The Editing Pane This tool is grayed out except when a use case is selected 12 3 5 Class Diagram Specific Tools Several tools are provided specific to UML artifacts on class diagrams The detailed properties of these artifacts are described in the section on class diagram artifacts see Chapter 18 Class Diagram Artifact Reference e Package Add a package to the diagram e Class Add a class to the diagram
362. olBar 2 0 0 0 ceeccee ce eeceeeee teen teenies 270 22 2 3 Property fields for action state 20 0 0 eee eee eeeceeeceeeee teen teen es 271 22 3 ACUOM iiss asta sos basnG sa seeate ageing Seanaiag sad NOL Gaseestawhas Detseasaweneg ass veda TiRESe ans 271 22 4 Transitions ssoccie i cbeehs Ge ecs icebesks cues caeleb cobs EEEE EEE ESEE 271 22 3 GUATA cf rererere r EE O EESE Sed G AE TREE E Sota n dese deacwa soot EEES REEERE 212 22 6 Initial State cies SE EEEE ARSEN E EEA 272 227 Final State isni a e bank a a ea 272 22 8 J nction DECISION mic tica E Rn 272 UU O d AN E EA E SN 212 22 10 Jom se e a a Sted E Gon a Magen E E E ESA 272 22 VOD ECtELOW State oes se ad a E E O Geese 212 23 Deployment Diagram Artifact Reference ooocconcncccnccnnncnnccnnccnnccnnccnnconnconiconose 273 23 1 Introduction it A A A 273 23 1 1 Limitations Concerning Deployment Diagrams in ArgoUML 273 23 2 Nods tioa an e E E EEE E ETE era EES 273 23 2 1 Node Details Tabs coccion pidas ii Pinas 274 23 2 2 Node Property Toolbar oococooccnnccnnconoconocnnncnnconnconncnnncnnocnnconoso 275 23 2 3 Property Fields For Node oocoocccocccnccnnccnnconnconoconoconoconoronrnnoso 275 23 3 Node Instance seiiher net ees spessiel 276 23 3 1 Node Instance Details Tabs 2 0 0 0 eee eee eee ce eeceeeee teen teen es 276 23 3 2 Node Instance Property Toolbar 2 0 0 0 cece cece eee ceeeee teen eeenes 277 23 3 3 Property Fields For Node
363. omo OOA amp D RD El desarrollo Recursivo puede ser aplicado igualmente bien a procesos de cascada o iterativos No es una alternativa a ellos Un Proceso de Desarrollo para este Manual Para el proposito de este manual usaremos un proceso iterativo descendente con desarrollo recursivo li geramente semejante a RUP El caso de estudio nos llevar a traves de la primera iteraci n aunque al final de la secci n de tutorial del manual miraremos a como el proyecto se desarrollar hasta su final izaci n 10 OOA amp D basada en UML Dentro de la primera iteraci n abordaremos cada uno de las actividades de captura de requerimientos analisis dise 0 y construcci n por turno No todas las partes del procesos est n basadas en UML o ArgoUML Miraremos a que otro material es necesario Dentro de este proceso tendremos una oportunidad para ver los varios diagramas UML en uso El rango completo de diagramas UML y como est n soportados est descrito en el manual de referencia mira Section 16 6 Diagram 3 2 2 1 Captura de Requerimientos Nuestra captura de requerimientos usar el concepto UML de Casos de Uso Empezando con un Vision Document veremos como los Casos de Uso pueden ser desarrollados para describir todos los aspectos del comportamiento del sistema en el dominio del problema 3 2 2 2 Analisis Durante la etapa de analisis introduciremos el concepto de UML de clases para permitirnos construir una visi n de
364. on A UML diagram showing the relationships between Actors and Use Cases See Section 4 3 Salida del Proceso de Captura de Requeri mientos for more information The document capturing the detailed requirements behind a Use Case The top level document describing what the system being developed is to achieve The World Wide Web Consortium www w3c org ht 296 Glossary Waterfall Design Process XMI XML tp www w3c org An international standardization body for all things to do with the World Wide Web A design process where each phase requirements analysis design build test is completed before the next starts See Section 3 2 1 Tipos de Procesos for more information XML Model Interchange format A format for file storage of UML models Currently incomplete since it does not carry all graphical layout information so must be supplemented by files carrying that information eXtensible Markup Language A simplified derivative of SGML defined by W3C 297 Appendix A Supplementary Material for the Case Study A 1 Introduction The case study requires various material mostly documents that live alongside the design diagram A 2 Requirements Documents To be written To be written A 2 1 Vision Document To be written To be written A 2 2 Use Case Specifications To be written To be written A 2 2 1 UC Specification 1 To be written To be written
365. on Modifiers There are 3 modifiers navigable ordered and static All 3 are checkboxes e navigable Indicates that this end can be navigated to from the other end Note The UML 1 4 standard provides a number of options for how navigation is dis played on an association end ArgoUML uses option 3 which means that arrow heads are shown at the end of an association when navigation is enabled at only one end to indicate the direction in which navigation is possible This means that the default with both ends navigable has no arrows e ordered When placed on one end specifies whether the set of links from the other instance to this instance is ordered The ordering must be determined and maintained by Operations that add links It represents additional information not inherent in the objects or links themselves Possibil ities for the checkbox are Unchecked The links form a set with no inherent ordering Checked A set of ordered links can be scanned in order e Static To be written Specification List Designates zero or more Classifiers that specify the Operations that may be applied to an In stance accessed by the AssociationEnd across the Association These determine the minimum inter face that must be realized by the actual Classifier attached to the end to support the intent of the As sociation May be an Interface or another Classifier The type of classifier is indicated by an icon Button double click navigates to t
366. on This chapter describes each artifact that can be created within a Deployment Diagram Note that some sub artifacts of artifacts on the diagram may not actually themselves appear on the diagram There is a close relationship between this material and the Properties Tab of the Details Pane see Sec tion 13 3 Properties Tab That section covers Properties in general in this chapter they are linked to specific artifacts Within ArgoUML the deployment diagram is used for both component diagrams i e without instances showing static dependencies of components and deployment diagrams showing how instances of com ponents are handled by instances of nodes at run time Caution Deployment diagrams are not fully developed yet in ArgoUML Some aspects are not fully implemented or may not behave as expected Notable omissions are the possibility to draw new interfaces and proper stereotyping of the various dependency relationships Figure 23 1 Possible artifacts on a component diagram shows a component diagram with all possible artifacts displayed Figure 23 1 Possible artifacts on a component diagram Figure 23 2 Possible artifacts on a deployment diagram shows a deployment diagram with all pos sible artifacts displayed Figure 23 2 Possible artifacts on a deployment diagram 23 1 1 Limitations Concerning Deployment Diagrams in ArgoUML The deployment diagram is generally well drawn but there are only a su
367. on dialog appears to allow the user to save his work first or cancel the oper ation completely Figure 10 4 The confirmation dialog for Import XMI When the menu is activated the standard filechooser appears see Figure 10 5 The dialog for Im port XMI Beware the fact that this file will only contain the model not any diagram layout Hence the new project will not contain any diagrams Figure 10 5 The dialog for Import XMI 10 3 7 Export XMI This menu item allows to save the complete structure of the UML 1 4 model as a XMI file according the XMI V1 2 standard Beware the fact that this file will only contain the model not any diagram lay out Hence if the XMI file is reloaded with the File Open Project menu then the dia grams are lost When the menu is activated the standard filechooser appears see Figure 10 6 The dialog for Ex port XMI Figure 10 6 The dialog for Export XMI 10 3 8 Import Sources A very powerful feature of ArgoUML is that it can Reverse Engineer Java code to yield a class dia gram This sub menu entry specifies Java code to be imported for reverse engineering The dialog box is similar to that for Open Project see Figure 10 2 The file selection dialog for Open Project but with two extra tabs placed alongside the directory listing as shown in Fig ure 10 7 The file selection dialog for Import Sources Figure 10 7 The fi
368. on end used to describe an association end s behavior in a particular context In the UML metamodel AssociationEndRole is a sub class of AssociationEnd Two or more association end roles are associated with each association role see Section 21 3 Association Role although for ArgoUML the number of ends can only be two The association end role has no direct access on any diagram although its stereotype name and multi plicity is shown at the relevant end of the parent association role see Figure 21 1 Possible artifacts on a collaboration diagram and some of its properties can be directly adjusted with button 2 click Where shared or composite aggregation is selected for one association end role the opposite end is shown as a solid diamond composite aggregation or hollow diamond shared aggregation Note ArgoUML does not currently V0 18 support showing qualifiers on the diagram as de scribed in the UML 1 4 standard Caution An association end role should have the same or stricter attribute values than its base as sociation end In particular its navigability should be no more general There is as yet no critic in ArgoUML to offer advice on this rule 21 4 1 Association End Role Details Tabs The details tabs that are active for association end roles are as follows 263 Collaboration Diagram Artifact Reference ToDoltem Standard tab Properties See Section 21 4 2 Association E
369. on is generated as a function call 7 3 Code Generation in ArgoUML 7 3 1 Static Structure Most of the generation can be done automatically by the provided language modules Files are generated in a directory hierarchy that need to be filled in by the actual code 7 3 2 Interactions and statechart diagrams There is currently no support for this in ArgoUML not for any language 7 4 Reverse Engineering Reverse Engineering is used for two main purposes 1 To get previously developed classed into the model to build upon 2 To get a UML view of previously developed classes to understand how they work Essentially this does the opposite of Code Generation 7 5 Round Trip Engineering Round Trip Engineering makes it possible to switch perspective while doing the design Create some classes in a class diagram Write some code for some of the operations or functions using your favorite editor Move the operations from one class to another in the class diagram ArgoUML currently does not support this for any language 64 Part 2 User Interface Reference Chapter 8 Introduction This chapter describes the overall behavior of the user interface Description of the various component parts the menu bar panes and various diagrams is in separate chapters 8 1 Overview of the Window Figure 8 1 Overview of the ArgoUML window shows the main ArgoUML window The titlebar of the window shows the followin
370. on operations and methods e To describe guards e As a navigation language and e To specify constraints on operations 128 The Details Pane Figure 13 14 A typical Constraints tab on the details pane shows a typical constraint tab for a artifact in ArgoUML in this case a class Figure 13 14 A typical Constraints tab on the details pane Along the top of the tab are a series of icons e New Constraint This creates a new constraint and launches the constraint editor in the Con straints tab for that new constraint see Section 13 7 1 The Constraint Editor The new con straint is created with a context declaration for the currently selected artifact Warning It seems logical that when a new constraint is created it needs to be edited But ArgoUML VO0 20 fails to start the OCL editor upon creation you have to do this by primo selecting the new constraint first secundo rename it and tertio press the Edit Constraint button It is essental for successfully creating a constraint to follow these 4 steps accurately create select rename edit The step to rename is necessary because the validity check will refuse the constraint if its name differs from the name mentioned in the constraint text For the same reason renaming a constraint afterwards is im possible e Delete Constraint The constraint currently selected in the Constraint Name box see be low is deleted Caution In V0 20 of ArgoUML t
371. on permanece activo en el proyecto 1 ha dejado el liderazgo El proyecto continua avanzando fuertemente Hay mas de 300 miembros en la lista de correo de desarrollador mira ht tp argouml tigris org servlets ProjectMailingListList ht tp argouml tigris org servlets ProjectMailingListList Con un par de docenas de ellos formando el nucleo del grupo de desarrollo La lista de correo del desarrollador es el lugar donde toda la discusi n sobre las ultimas tareas toma lugar y los desarrolladores discuten las direcciones que el proyecto deber a tomar Aunque controver tido a veces estas discusiones son mantenidas siempre correctas y amigables sin flame wars y esas co sas as que los novatos newbies no deberian dudar y participar en ellas Siempre tendras una ca lurosa bienvenida all Si quires aprender como se gestiona el proyecto y como contribuir a l vete a ArgoUML Web Site De veloper Zone http argouml tigris org dev html y busca a traves de la documentaci n all expuesta El Libro de Cocina del Desarrollador Developers Cookbook fu escrito especificamente para este proposito 1 1 3 2 Mas sobre la Infraestructura Ademas de la lista de correo del desarrollador existe tambien una lista de correo para usuarios mira The ArgoUML Mailing List List http argouml tigris org servlets ProjectMailingListList donde po demos discutir problemas desde la perspectiva del usuario Los desarrolladores tambien leen esa lis
372. ontenidos y cualquier subdir ectorio de forma equivalente por razones que se haran evidentes El estado del modelo al final de las secciones clave estar disponible en archivos zargo Estos est n disponibles de forma que puedes jugar con varias alternativas y restaurar al estado apropiado del modelo en tu area de trabajo Estos archivos zargo ser n identificados al final de las secciones cuyo trabajo representan El caso de estudio ser un sistema de Cajero Automatico Tu compa oa es FlyByNight Industries T vas a jugar dos papeles El de Gestor de Proyecto Project Manager y el de Analista Dise ador Designer Analyst No vamos a construir ning n Cajero Automatico fisicamente por supuesto Primero te familiarizaras con el producto y luego iremos a traves de un proceso de analisis y desarrollo para un caso de prueba La forma en como tu compa ia organiza su trabajo en proyectos est determinada normalmente por asuntos de politicas y demas cosas por el estilo por tanto fuera del mbito de este documento Iremos dentro de como estructuras el proyecto en s mismo una vez que ha sido definido Chapter 3 OOA amp D basada en UML En este capitulo miramos como UML como notaci n es usado dentro de OOA amp D 3 1 Antecedentes para UML La orientacion a Objeto como concepto ha existido desde la decada de 1960 y como concepto de dise 0 desde 1972 Sin embargo fu en la decada de 1980 que empez a desarrollarse como un
373. oocooccoccncnoconcnoconcnoroncnoroncnnroncnarononns 60 6 15 3 Class Diagrams To be written oocooccoccncnoconcnnconcnoconcnnroncnarononns 61 6 15 4 Sequence Diagrams To be written ooocoooccccccncnnncnnccnnccnnccnnccnninns 61 6 15 5 Collaboration Diagrams To be written cooccoccoccncnoconcnononcnononanns 61 6 15 6 Statechart Diagrams To be written ooooocooccocnoconcnnconcnnnoncnonononns 61 6 15 7 Activity Diagrams To be written coooccocccncccncnnccnncconccnnccnnccnniono 61 6 15 8 The Deployment Diagram To be written 2 0 0 0 eee ence 61 6 15 9 The System Architecture To be written oocoocooconcnoconcnoconcnorononns 61 7 Code Generation Reverse Engineering and Round Trip Engineering 62 Tid IO UCA at 62 O ACA A dveeeec oe ag Wag EEEE od veak E devon ae ag doce eadentes E E 62 7 2 1 Generating Code from the Static Structure ooocooccnccnnccnnccnnconnccnnions 62 7 2 2 Generating code from interactions and state machines 63 7 3 Code Generation in ArgoUML seerne deeree ae n E es Ea aS 64 EAC Statie Structure irre o E E eve el EE E N ee sewer 64 7 3 2 Interactions and statechart diagrams cee cece cece neces eeee eee eees 64 7A Reverse Engineering sicioun es eise E e EOE R KESEKESE Ee se 64 7 5 Round Trip Engineering coetonooio sonrie dia notas eE e E EEEE STEES 64 2 User Interface Reference iia es 65 TN 66 8 1 Overview Of the Window
374. operty Fields For Synch State below Documentation Standard tab Presentation Standard tab Stereotype Standard tab containing the stereotypes of the Synch state In the UML metamodel Synch State has no standard stereotypes defined Tagged Values Standard tab In the UML metamodel Synch State has no standard tagged values defined 20 20 2 Synch State Property Toolbar Go up Navigate up through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected synch state navigat ing immediately to the properties tab for that stereotype Delete from Model This deletes the synch state from the model Warning This is a deletion from the model not just the diagram 20 20 3 Property Fields For Synch State Name Text box The name of the Synch state By convention Synch state names start with a lower case letter and use bumpy caps to divide words within the name 255 Statechart Diagram Artifact Reference Note ArgoUML does not enforce this naming convention Tip Synch state names are not shown on the diagram and it is not usually necessary to give them a name Container Text box Shows the container of the Synch state This is the state hierarchy Button 1 double click on the entry will navigate to the composite state that contains this state or the top level state that is the root of the state containment hierarchy Bound Editab
375. or Parameter 205 for Signal 208 for Stereotype 165 Property Toolbar for Association 211 for Association End 213 for Attribute 197 for Class 192 for Datatype 157 for Enumeration 161 for Operation 200 for Parameter 205 for Signal 208 for Stereotype 164 PS 13 R Raised Signals of Operation 203 Realization Use Case 294 Reflection in Action xvii 12 294 315 Index Relaci n Inclusi n Include 33 Relaci n de Extensi n Extend 33 Relaci n de Inclusi n Include 33 Relati n Extensi n Extend 33 Relationship Extend 41 292 Generalization 41 292 Include 41 293 Remove From Diagram 81 Requerimiento Captura 29 Requerimientos no funcionales 30 Requirement Capturing 295 Responsibility 295 Retroalimentaci n 4 Retroalimentacion por el Usuario 4 Reverse Engineering 64 Robbins Jason 2 Round Trip Engineering 64 S Save Project 74 Scenario 295 Select All 80 Sequence Diagram 295 Setting Multiplicity to an association in a Use Case Diagram 41 Setting Navigation to an association in a Use Case Diagram 40 SGML 295 Shortcut key Alt F4 80 Ctrl A 80 Ctrl Delete 81 Ctrl N 73 Ctrl O 73 Ctrl P 76 Ctrl S 74 Delete 81 F7 93 Signal 207 Signal Contexts 209 Signal Details Tabs 207 Signal Name 208 Signal Property Fields 208 Signal Property Toolbar 208 Signal Stereotype 208 Signal Tagged Values 207 Simula 67 295 Soluci n
376. orador o en el panel de edici n ser resaltado 20 OOA amp D basada en UML En el caso de la Barra de Herramientas del Panel de Edici n ese objeto es seleccionado como el siguiente para ser a adido al diagrama pero solo uno haz doble click para a adir multiples obje tos Puedes a adir al diagrama moviendo el rat n al area de edici n y haciendo click otra vez 2 Doble click boton 1 Esta acci n es identica a la de un solo click excepto cuando es usado con la barra de herramientas del panel de edici n Bajo estas circunstancias el objeto seleccionado ser a adido multiples veces al area de dibujado una por cada click del boton hasta que la herramienta es seleccionada de nuevo o se escoge otra herramienta 3 Click boton 2 Cuando se usa sobre elementos de texto en los paneles del explorador o de detalles o objetos gr ficos en el panel de edici n esto desplegar un men dependiente del contexto Si el elemento no ha sido seleccionado a n ser tambien seleccionado 4 Movimiento boton 1 Donde el click con boton 1 ha sido usado para desplegar un men de la barra de men el movimiento con boton 1 es usado para seleccionar elementos en ese men El movimiento con boton 1 tambien tiene un efecto en el panel de edici n Sobre objetos gr ficos mover el objeto a una nueva posici n Los objetos gr ficos son seleccionados muestran asas y estos pueden ser usados para reescalarlo Donde el objeto es alguna for
377. os es una excelente introducci n a la actividad vital del poryecto Si quieres estar mas involucrado hay listas de correo adicionales que cubren el desarrollo del producto y problemas en la versi n actual y futuras 3 4 1 6 Ejecutando ArgoUML Como ejecutar ArgoUML depende de si usas Microsoft Windows o alguna variedad de Unix e En Windows Inicia una interfaz MSDOS por ejemplo usando Inicio Ejecutar con command en el texto texto de la ventana En la ventana colocate en el directorio que contiene tus archivos de ArgoUML y teclea java jar argouml jar Este metodo tiene la ventaja de que la inform aci n de progreso y depuraci n es visible en la ventana DOS De forma alternativa crea un archivo de proceso por lotes bat conteniendo el comando anterior con un acceso directo a el en el Es critorio El archivo bat deber a terminar con una sentencia de pause en caso de que se cree inform aci n de depuraci n durante la ejecuci n En algunos sistemas simplemente haciendo doble click en el archivo argouml jar funciona En otros hacer esto inicia un programa de compresion de archivos Acude a las instrucciones de tu sistema operativo o busca ayuda para determinar como con figurar esto 16 OOA amp D basada en UML e En Unix Inicia una ventana de terminal y teclea java jar argouml jar 3 4 1 7 Problemas Ejecutando ArgoUML 3 4 2 Es inusual encontrar problemas si has tenido una descarga exitosa Si no puedes resolver e
378. osition relative to the original class and creates a generalization or association a drag from the button to an existing class creates only the generalization or association and a drag to an empty space in the diagram creates a new class at the mouse position and the generalization or association ArgoUML provides some automated layout support so that click ing the subclass button will position the new classes so that they do not overlap Selection action buttons are transparent They have a visibly recognizable rectangular shape and size and they contain an icon that is the same as the icon used for the corresponding type of design element on the standard toolbar However these icons are unfilled line drawings with many transparent pixels This allows selection action buttons to be overlaid onto the drawing area without overly obscuring the diagram itself Also the buttons are only drawn when the mouse is over the selected artifact if any part of the diagram is obscured the mouse can simply be moved away to get a clearer view of the diagram Clarifiers A key feature of ArgoUML are the critics which run in parallel with the main ArgoUML tool When they find a problem they typically raise a to do item and also highlight the problem on the editing pane The graphical techniques used for highlighting are called Clarifiers e Note icon Displayed at the top left of an artifact indicates a critic of that artifact Moving the mouse over the ico
379. ottom half see below Double click on any row describing an artifact on a diagram and that item and diagram will be selected The bottom half of the tab is a table labeled Related Elements and is a table with the same columns as the top half When an element artifact has been selected in the top half this table shows the details of any related elements Tip Enlarging the dialog vertically shows that the Related Items part changes in size but not the Search results part However between them is a divider line and when hovering over this line the mouse pointer changes into a sizing icon and the border between these 2 areas can be moved up or down to redistribute the space in the window Warning This dialog box is not modal which allows it to remain open while editing the model for easy navigation But the V0 22 implementation of ArgoUML does not inmediately update the dialog box with changes made to the found artifacts change of artifact name change of diagram name Deletion of a diagram does not stop the possibility to navigate to it 10 5 3 Zoom This entry brings up a sub entry which allows scaling the view of all diagrams to a factor of its normal size This setting is not saved persistently The sub menu items that can be selected are e Zoom Out Shortcut Ctrl Minus Gives more overview over the drawing e Zoom Reset Returns to the default zoom ratio i e 100 e Zoom In Shortcut Ctrl Equals Makes the
380. ox The name of the action By convention action names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Asynchronous Check box Indicates if a dispatched Stimulus is asynchronous or not Script Double text box with the expression that defines the action This field consists of two parts the first one contains the body script of the expression and the second one contains the particular pro gramming language used to write the expression Recurrence 240 Statechart Diagram Artifact Reference Double Text box An expression stating how many times the Action should be performed The field consists of two parts the first one for the expression the second one for the language it is written in Arguments Text box This is an ordered list with the arguments of the action Button 1 double click on any of the arguments navigates to that argument button 2 click brings up a pop up menu with two entries e New Create a new argument and navigate to it e Remove Deletes the argument from the model Instantiation only for CreateAction Text box This shows the classifier that gets instantiated by the create action Button double click on the classifier navigates to that argument button 2 click brings up a pop up menu with one entry e Add This brings up a dialog box that allows selecting the one classifier that gets created 20
381. ox The name of the interface The name of an interface has a leading capital letter with words separated by bumpy caps Note Unlike classes the ArgoUML critics will not complain about interface names that do not have an initial capital 220 Class Diagram Artifact Reference Stereotype Drop down selector Interface is provided by default with the UML standard stereotypes for the par ent meta class Classifier metaclass powertype process thread and utility Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records and allows changing the namespace for the interface This is the pack age hierarchy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that this interface cannot be instantiated but must always be spe cialized The name of an abstract interface is displayed in italics on the diagram Caution This is meaningless since by definition an interface is an abstract entity The UML 1 3 standard offers no clarification e Leaf indicates that this interface cannot be further specialized while Root indicates it can have no generalizations Visibility Radio box with three entries public protected private and package Indicates whether navigation to this end may be by i any classifier ii only the source classifier and its childr
382. p through the package structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected link navigating im mediately to the properties tab for that stereotype Delete This deletes the link from the model Warning This is a deletion from the model not just the diagram To delete an link from the dia gram but keep it within the model use the main menu Remove From Diagram or press the Delete key 19 9 3 Property Fields For Link Name Text box The name of the link By convention link names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Link has no stereotypes by default in the UML standard Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec 234 Sequence Diagram Artifact Reference tion 18 4 Stereotype Namespace Text box Records the namespace for the link This is the package hierarchy Connections List box Lists the connections of the link i e the link ends Button 1 double click on the entry will navigate to the link end 235 Chapter 20 Statechart Diagram Artifact Reference 20 1 Introduction This chapter describes each artifact that can be created within a statechart diagram Note that some sub artifacts of artifacts on the diagram may
383. packages e Root indicates that it is the top level package Tip Within ArgoUML Root only meaningfully applies to the Model since all packages sit within the model This could be used to emphasize that the Model is at the top level Generalizations Text area Lists any package that generalizes this package Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized package i e for which this package is a generalization button double click navigates to the generalization and opens its property tab Owned Elements Text area A listing of all the packages classes interfaces datatypes actors use cases associations generalizations and stereotypes within the package Button 1 double click on any item listed here navigates to that artifact 18 3 Datatype Datatypes are not specific to packages or class diagrams and are discussed within the chapter on top level artifacts see Section 16 3 Datatype 18 4 Stereotype Stereotypes are not specific to packages or class diagrams and are discussed within the chapter on top level artifacts see Section 16 5 Stereotype 18 5 Class The class is the dominant artifact on a class diagram In the UML metamodel it is a sub class of Clas sifier and GeneralizableElement A class is represented on a class diagram as a rectangle with three horizontal compartments The top compartment displays t
384. pec cionar las cr ticas disponibles Men Herramientas Este men est sombreado permanentemente a menos que halla alguna her ramienta disponible en tu versi n de ArgoUML Men Ayuda Este men te da acceso a detalles de aquellos que crearon el sistema y donde se puede encontrar ayuda adicional Barra de Herramientas de Archivo Esta barra de herramientas contiene algunas de las herramientas del men Archivo Barra de Herramientas de Edici n Esta barra de herramientas contiene algunas de las herramientas de men Edici n Barra de Herramientas de Visualizar Esta barra de herramientas contiene algunas de las herramientas del men Visualizar Barra de Herramientas de Crear Diagrama Esta barra de herramientas contiene algunas de las her ramientas del men Crear Diagrama 3 4 2 6 El Rat n El rat n y los botones del rat n o sus equivalentes con dispositivos de entrada alternativos son usad os en una amplia variedad de formas En esta secci n miraremos a los modos comunes de uso ArgoUML asume el uso de un rat n de dos botones Nos referiremos a los botones como boton 1 y boton 2 El boton 1 es el boton mas a la izquierda en un rat n de diestro y a veces llamado como el boton selecci n El boton 2 es llamado a veces como el boton ajuste 1 Click boton 1 Esta acci n es usada generalmente para seleccionar un elemento para operaciones subsiguientes Si el elemento es un objeto en el expl
385. pen Publication licensed material is permitted Any publication in standard paper book form shall require the citation of the original publisher and au thor The publisher and author s names shall appear on all outer surfaces of the book On all outer sur faces of the book the original publisher s name shall be as large as the title of the work and cited as pos sessive with respect to the title F 2 Copyright The copyright to each Open Publication is owned by its author s or designee F 3 Scope Of License The following license terms apply to all Open Publication works unless otherwise explicitly stated in the document Mere aggregation of Open Publication works or a portion of an Open Publication work with other works or programs on the same media shall not cause this license to apply to those other works The aggregate work shall contain a notice specifying the inclusion of the Open Publication material and appropriate copyright notice SEVERABILITY If any part of this license is found to be unenforceable in any jurisdiction the remain ing portions of the license remain in force NO WARRANTY Open Publication works are licensed and provided as is without warranty of any kind express or implied including but not limited to the implied warranties of merchantability and fit ness for a particular purpose or a warranty of non infringement F 4 Requirements On Modified Works All modified versions of documents cover
386. pen arrow head and a label include see Figure 17 1 Possible artifacts on a use case diagram 184 Use Case Diagram Artifact Reference 17 10 1 Include Details Tabs The details tabs that are active for include relationships are as follows Note There is no source tab since there is no source code that could be generated for an include relationship ToDoltem Standard tab Properties See Section 17 10 2 Include Property Toolbar and Section 17 10 3 Property Fields For Include below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds of the include relationships are downlighted since the in clude relationship is represented by a line between a particular pair of use cases Tagged Values Standard tab In the UML metamodel Include has the following standard tagged values defined e derived from the superclass ModelElement Values true meaning the include relation ship is redundant it can be formally derived from other elements or false meaning it cannot Note Derived include relationships could have their value in analysis to introduce useful names or concepts 17 10 2 Include Property Toolbar Go up Navigate up through the package structure of the model For a include this will be the package con taining the include New Stereotyp This creates a new Stereotype see Section 16 5
387. ping Do not use the properties window dialog fields they are not fully functional and liable to cause you a little frustration In fact it would be interesting to see if you can type stereotypes write in the class attribute box for gen erating XML diagrams 5 3 3 2 Class Attributes To be written To be written 5 3 3 3 Class Operations To be written To be written 5 3 4 Advanced Class Features To be written 5 3 4 1 Association Classes To be written To be written 5 3 4 2 Stereotypes To be written To be written 5 4 Sequence Diagrams To be written To be written 49 Analysis 5 4 1 The Sequence Diagram To be written To be written 5 4 2 Identifying Actions To be written To be written 5 4 3 Advanced Sequence Diagrams To be written To be written 5 5 Creating Sequence Diagrams in ArgoUML 5 5 1 Sequence Diagrams 5 5 1 1 Creating a Sequence Diagram Normally you can just start a sequence diagram right away On the Create Diagram menu choose Sequence 5 5 2 Actions To be written To be written 5 5 3 Advanced Sequence Diagrams To be written To be written 5 6 Statechart Diagrams To be written To be written 5 6 1 The Statechart Diagram To be written Types of statechart diagram Moore Mealy Hierarchical diagrams To be written 5 6 2 Advanced Statechart Diagrams To be written To be written 5 6 2 1
388. pletely not just from the diagram To remove the artifact just from the diagram use the edit menu see Section 10 4 2 Remove From Diagram Caution You can delete a diagram from the model Depending on the type of diagram that might delete all artifacts shown on the diagram To illustrate the differences consider the follow ing examples e Deleting a class diagram does not delete any artifact drawn on it All artifacts that were shown on the diagram remain present in the model This because a class diagram does not map on any artifact according the UML standard V1 4 e Deleting a statechart diagram also deletes the statemachine it represents and hence also all the artifacts owned by the statemachine This because a statechart diagram does map into a StateMachine according the UML standard V1 4 11 6 3 Set Source Path To be written This entry on the pop up ment 11 6 4 Add Package This entry on the pop up menu is available whenever an artifact is selected that may contain a package e g a package After activating this menu the artifact will own a new package 11 6 5 Add All Classes in Namespace This entry on the pop up menu is available for Class Diagrams only Activating this menu item will add all classes in the current namespace to the diagram They will be located at the top left corner obviously a perfect occasion to use the Arrange gt Layout function in the menu 103 Chapter 12
389. point and navigate to it making this use case the owning use case of the extension point Generalizations Text area Lists use cases which are generalizations of this one Will be set whenever a generaliza tion is created on the from this Use Case Button 1 Double Click on a generalization will navigate to that generalization Specializations Text box Lists any specialized use case i e for which this use case is a generalization Button 1 double click navigates to the generalization and opens its property tab Extends Text box Lists any class that is extended by this use case Where an extends relationship has been created button 1 double click will navigate to that relation ship Includes Text box Lists any use case that this use case includes Where an include relationship has been created button 1 Double Click will navigate to that relation ship Association Ends Text box Lists any association ends see Section 18 11 Association of associations connected to this use case Button 1 double click navigates to the selected entry 17 4 Extension Point An extension point describes a point in a use case where an extending use case may provide additional behavior Examples for a travel agent sales system might be the use case for paying for a ticket which has an ex tension point in the specification of the payment Extending use cases may then extend at this point to 175 Use Case Diagram Art
390. poly gon closed with button 1 double click which will link the final point to the first point Spline Provide an open spline The control points of the spline are selected with button 1 and the last point selected with button 1 double click Ink Provide a polyline The points are provided by button motion Use Case Diagram Specific Tools Several tools are provided specific to UML artifacts on use case diagrams The detailed properties of these artifacts are described in the section on use case diagram artifacts see Chapter 17 Use Case Dia gram Artifact Reference Actor Add an actor to the diagram For convenience when the mouse is over a selected actor it dis plays two handles to left and right which may be dragged to form association relationships Use Case Add a use case to the diagram For convenience when the mouse is over a selected use case it displays two handles to left and right which may be dragged to form association relationships and two handles top and bottom which may be dragged to form generalization and specialization rela tionships respectively Association Add an association between two artifacts selected using button 1 motion from the first artifact to the second There are 6 types of association offered here see Figure 12 4 The asso ciation tool selector association aggregation and composition and all these three can be bidirectional or unidirectional Figure 12 4 The association to
391. priority value will enable all critics at or above that priority level within the design issue category Off being the lowest priority Note The sliders are set by default to High for all design categories 10 9 3 Design Goals This menu entry brings up a dialog box controlling how design goals are to be handled see Fig ure 10 23 The dialog for Design Goals Figure 10 23 The dialog for Design Goals ArgoUML has the concept that the designer will have a number of design goals to be achieved for ex ample good structural representation detailed behavioral representation etc Critics are associated with one or more goals This dialog allows the user to specify the priority of each design goal The sliders may be set for each design goal to control the critics that trigger for that goal Setting a slider to zero will disable all critics in that goal and remove all associated to do items from the to do pane Setting a slider to a higher value will enable all critics at or above that priority level within the design is sue category 1 being the highest priority and 5 the lowest 94 The Menu bar Tip It may be useful to think of this function as very similar to Design Issues see Section 10 9 2 Design Issues but with grouping of critics according to the outcomes of OOA amp D rather than grouping according to the structure of UML Warning The V0 20 version of ArgoUML provides a single
392. que lo hacen especial pero no implementa todas las caracteristicas que una herramienta CASE comercial proporciona La publicaci n VO 20 actual de ArgoUML implementa todos los tipos de diagramas de UML 1 4 standard http www omg org cgi bin doc formal 01 09 67 versiones de ArgoUML anteriores a 0 20 implementaban la UML 1 3 standard http www omg org cgi bin doc formal 00 03 01 Est escrito en Java y funciona en todo sistema que proporcione una plataforma Java 2 de Java 1 4 o posterior Usa formatos de archivo abiertos XMI http www omg org cgi bin doc formal 02 01 01 formato XML Metadata Interchange para la informaci n de modelos y PGML ht tp www w3 org TR 1998 NOTE PGML Precision Graphics Markup Language para informaci n gr fica para almacenamiento Cuando ArgoUML implemente UML 2 0 PGML sera sustituido por la especificaci n UML Diagram Interchange XVil Prefacio Este manual es el trabajo acumulativo de muchas personas y ha estado evolucionando durante muchos a os Conectado con la publicaci n 0 10 de ArgoUML Jeremy Bennett escribi gran cantidad de nuevo material que fue a adido a las vestiones anteriores por Alejandro Ramirez Philippe Vanpeper straete y Andreas Rueckert El ademas a adi cosas de algunos de los otros documentos como el libro de cocina de los desarrolladores por Markus Klink y Linus Tolke la Guia R pida por Kunle Odutola y el FAQ Preguntas frecuentes por Dennis Daniels Conecta
393. r Go up Navigate up through the package structure New Stereotyp 251 Statechart Diagram Artifact Reference This creates a new Stereotype see Section 16 5 Stereotype for the selected state navigating im mediately to the properties tab for that stereotype Delete from Model This deletes the final state from the model Warning This is a deletion from the model not just the diagram 20 13 3 Property Fields For Final State Name Text box The name of the final state By convention final state names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Tip Final state names are shown on the diagram but it is not usually necessary to give them a name Container Text box Shows the container of the final state This is the state hierarchy Button 1 double click on the entry will navigate to the composite state that contains this state or the top level state that is the root of the state containment hierarchy Entry Action Text box Shows the name of the action 1f any to be executed on entry to this final state Button 1 double click navigates to the selected entry button 2 gives a pop up menu with two entries e New Add a new Entry action of a certain kind This menu has the following 7 submenus to select the kind of action Call Action Create Action Destroy Action Return Action Send Action Ter minate
394. r change the association aggregation to composite relationship at the DataType end 15 3 2 Reduce Classes in diagram lt diagram gt Suggestion to improve readability by having fewer classes on a diagram If one class diagram has too many classes it may become very difficult for humans to understand Defining an understandable set of class diagrams is an important part of your design The Wizard of this critic allows setting of the treshold i e the maximum number of classes allowed be fore this critic fires Caution This number is not stored persistently and there is no way to reduce it after it has been set higher except by creating more classes until the critic fires again Restarting ArgoUML re sets this number to its default 20 15 3 3 Clean Up Diagram Suggestion that the diagram could be improved by moving artifacts that are overlapping 15 4 Naming These are critics concerning the naming of artifacts The current version of ArgoUML has 18 critics in this category 15 4 1 Resolve Association Name Conflict Suggestion that two association names in the same namespace have the same name This is not permit ted in UML 15 4 2 Revise Attribute Names to Avoid Conflict Suggestion that two attribute names of a class have the same name This is not permitted in UML Note The problem may be caused by inheritance of an attribute through a generalization rela tionship 136 The Critics 15 4 3 Change Nam
395. r inter relationships may be shown as links instances of an association See Sec tion 19 9 Link for details 284 Chapter 24 Built In DataTypes Classes Interfaces and Stereotypes 24 1 Introduction This chapter describes the datatypes classes interfaces and stereotypes which by default are built in to ArgoUML Datatypes classes and interfaces are generally available for use anywhere a class may be selected in the properties tab The most common use is for return type and parameter types in method signatures 24 1 1 Package Structure ArgoUML datatypes classes and interfaces are effectively organized as a hierarchy beneath the overall model itself They are grouped in four packages lang math net and util themselves subpackages of java which is a subpackage of the model itself Figure 24 1 Hierarchy of datatypes classes and interfaces within ArgoUML shows this structure Figure 24 1 Hierarchy of datatypes classes and interfaces within ArgoUML 24 1 2 Exposure in the model You will not find build in DataTypes Classes and Interfaces exposed within the model by default i e they are not present in the explorer However once you select one of the built in DataTypes Classes or Interfaces in the Type combo box on the property sheet of a parameter of an operation of a class then it becomes visible you will find that the DataType Class or Interface has appeared in the model in its correct pa
396. r is not stored persistently and there is no way to reduce it after it has been set higher except by creating more attributes until the critic fires again Restarting ArgoUML resets this number to its default 7 15 6 Planned Extensions Critics concerning interfaces and subclasses Note It is not clear why this category has the name Planned Extensions The current version of ArgoUML has three critics in this category 15 6 1 Operations in Interfaces must be public Suggestion that there is no point in having non public operations in Interfaces since they must be visible to be realized by a class 15 6 2 Interfaces may only have operations Suggestion that an interfaces has attributes defined The UML standard defines interfaces to have opera tions 140 The Critics Caution ArgoUML does not allow you to add attributes to interfaces so this should never occur in the ArgoUML model It might trigger if a project has been loaded with XMI created by an other tool 15 6 3 Remove Reference to Specific Subclass Suggestion that in a good design a class should not reference its subclasses directly through attributes operations or associations 15 7 State Machines Critics concerning state machines ArgoUML has the following critics in this category 15 7 1 Reduce Transitions on lt state gt Suggestion given state is involved in so many transitions it may be a maintenance bottleneck The Wizard o
397. r the system need to be familiar to the people participating in the group The ideal group size for a CRC card session is five or six people This size generally allows everyone to productively participate In groups of larger size productivity is cut by more disagreements and the amount of participation by each is lower If there are more than six people one solution is to have the extra people be present strictly as observers The group five or six people in the core group should be composed of developers domain experts and an object oriented technology facilitator G 3 The Session Before starting a session a part of the problem needs to be selected for the session to focus on Essen tially this means picking the set of classes that are to be used Pick the scenarios that are to be walked through that use the classes picked above Start with scenarios that are part of the systems normal operation first and then exceptional scenarios like error recover later Assign each class to a member of the group Each person should be responsible for at least one class They are the owner of that class for the session Each person records the name of their class on a card One class per card Walk throughs are the heart of the CRC card session To walk through a scenario address each action in it one at a time First decide which class is responsible for this function The owner of the class then picks up his card and holds it up in the air Wh
398. ract with a use case but whose children do e leaf indicates that this actor can have no further children while Root indicates it is a top level actor with no parent Generalizations Text area Lists any actor that generalizes this actor Button 1 double click navigates to the generalization and opens its property tab Specializations Text box Lists any specialized actor i e for which this actor is a generalization The specialized actors can communicate with the same use case instances as this actor Button 1 double click navigates to the generalization and opens its property tab Association Ends Text area Lists any association ends of associations connected to this actor Button 1 double click navigates to the selected entry 17 3 Use Case A use case represents a complete meaningful chunk of activity by the system in relation to its external users actors human or machine It represents the primary route through which requirements are cap tured for the system under construction Within the UML metamodel use case is a sub class of classifier The use case icon is an oval see Figure 17 1 Possible artifacts on a use case diagram It may be split in two with the lower compartment showing extension points Caution By default ArgoUML does not show the extension point compartment It may be revealed by the context sensitive Show menu using button 2 click or from the Presentation tab 17 3 1 Use Case D
399. rado colocando una flecha en la asociaci n desde el caso de uso apuntando hacia el actor En el ejemplo del Cajero Automatico el sistema central es un actor pasivo Este es un buen ejemplo donde la flecha ayuda puesto que nos permite distinguir un sistema conducido por eventos el Cajero Autom tico inicia la interacci n con el sistema central de un sistema de con sulta continua el sistema central interroga al Cajero Autom tico de tiempo en tiempo Donde un actor puede ser una de dos activo o pasivo dependiendo de las circunstancias la flecha puede ser omitida En el ejemplo del Cajero Autom tico el ingeniero del banco se ajusta a esta cat egor a Normalmente el est activo poniendose en funcionamiento en cicles regulares para dar servi cio al Cajero Sin embargo is el Cajero Autom tico detecta un fallo puede convocar al ingeniero para repararlo El uso de flechas en asociaciones es referido como la navegaci n de la asociaci n Veremos esto usado en otro lugar en UML mas tarde Figure 4 2 Diagrama de casos de uso para un Cajero Autom tico mostrando navegaci n muestra el diagrama de casos de uso del Cajero Autom tico con navegaci n representada Figure 4 2 Diagrama de casos de uso para un Cajero Autom tico mostrando navegaci n 4 3 2 2 Multiplicidad Puede ser util mostrar la multiplicidad de asociaciones entre actores y casos de uso Con esto queremos decir cuantas instancias de un actor interacciona con cu
400. rams a class diagram and a use case diagram Caution untitledModel is not a conventional model name most processes suggest models should be build from lower case letters ArgoUML permits you to use any case letters but a critic will trigger to warn that this is not conventional See Section 16 2 The Model for a discussion of this If the model has been altered as indicated by the in the titlebar of ArgoUML s window then activ ating the New function is potentionally not the user s intention since it will erase the changes Hence a confirmation dialog appears to allow the user to save his work first or cancel the operation completely Figure 10 1 The confirmation dialog for New 10 3 2 Open Project Shortcut Ctrl O This opens an existing project from a file Selecting this menu option will open a file selection dialog see Figure 10 2 The file selection dialog for Open Project Figure 10 2 The file selection dialog for Open Project The main body of the dialog is a text area with a listing of all directories and files in the currently selec ted directory which match the current filter see below Navigating in the directory tree is possible by selecting a directory in the drop down selector at the top of this dialog Navigating deeper in the tree may be done by double clicking button 1 on the directory shown in the main text area In the lower portion of the dialog is a text box labeled Fil
401. ration diagram in ArgoUML as a line connecting the in stances concerned However on a sequence diagram the representation is modified to reflect the type of action associated with the stimulus carried on the link see Section 19 3 Stimulus The association role is labeled with the association role name if any An association role shows its name and the association name according the following syntax AssociationRoleName AssociationName in the same manner as a classifier role The more generic syntax is I R C which stands for an Instance named I originating from the Classifier C playing the role R 21 3 1 Association Role Details Tabs The details tabs that are active for association roles are as follows ToDoltem Standard tab Properties See Section 21 3 2 Association Role Property Toolbar and Section 21 3 3 Property Fields For Association Role below Documentation Standard tab Presentation Standard tab The values for the bounds of the association role are downlighted since they are de termined by what they connect Source Standard tab but with no contents Caution An association role should not generate any code so having this tab active is probably a mistake Tagged Values Standard tab In the UML metamodel AssociationRole has the following standard tagged val ues defined e persistence from the superclass Association Values transitory indicating state is destroyed when an i
402. reotype see Section 16 5 Stereotype for the selected guard navigating immediately to the properties tab for that stereotype Delete from Model This deletes the guard from the model Warning This is a deletion from the model not just the diagram 20 10 3 Property Fields For Guard Name Text box The name of the guard By convention guard names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention 248 Statechart Diagram Artifact Reference Transition Text box showing the transition that owns this guard Button 1 double click on the transition navigates to that transition Expression Text box The expression that defines the guard Language Text box This indicates that the expression is written in a particular interpretation language with which to evaluate the text 20 11 Pseudostate A pseudostate encompasses a number of different transient vertices on a state machine diagram They are used typically to connect multiple transitions into more complex state transitions paths For ex ample by combining a transition entering a fork pseudostate with a set of transitions exiting the fork pseudostate we get a compound transition that leads to a set of concurrent target states Pseudostates do not have the properties of a full state and serve only as a connection point for transactions but with some semantic value Withi
403. reotype as defining a singleton A singleton class can have at most one instance This means that the class must meet the design criteria for a singleton see Section 15 8 1 Consider using Singleton Pattern for lt class gt Whenever you mark a class with a stereotype the class should satisfy all constraints of the stereotype This is an important part of making a self consistent and understangle design Using the singleton pat tern can save time and memory space If you no longer want this class to be a singleton remove the singleton stereotype by clicking on the class and selecting the blank selection on the stereotype drop down within the properties tab To apply the singleton pattern you should follow the directions in Section 15 8 1 Consider using Singleton Pattern for lt class gt 15 8 3 Nodes normally have no enclosers A suggestion that nodes should not be drawn inside other artifacts on the deployment diagram since they represent an autonomous physical object 15 8 4 Nodelnstances normally have no enclosers A suggestion that node instances should not be drawn inside other artifacts on the deployment diagram since they represent an autonomous physical object 15 8 5 Components normally are inside nodes A suggestion that components represent the logical entities within physical nodes and so should be drawn within a node where nodes are shown on the deployment diagram 15 8 6 Componentinstances norm
404. resentations such as program syntactic decomposi tion state transitions control flow and data flow These allow the programmer to better identify elements and relationships in the problem and solution and thus more readily create a mapping between their situation models and working system models 2 Familiar aspects of a situation model which improve designers abilities to formulate solutions A Class Diagram constructed during the Analysis Phase to show the main structural components of the problem identified in the Require ments Phase See Chapter 5 Analysis for more information A process within ArgoUML that provides suggestions as to how the design might be improved Suggestions are based on principles within three theories of cognitive psychology reflection in action opportunistic design and comprehension and problem solving A relationship between two Use Cases where the extended Use Case describes a special variant of the extending Use Case A relationship between one generalizing Use Cases and one or more generalized Use Cases where the generalized Use Cases are partic 292 Glossary GUI Hierarchical Statechart Dia gram Include Relationship Iterative Design Process Java Mealy Machine Method of a Class or Object Moore Machine ular examples of the generalizing Use Case Graphical User Interface A Statechart Diagram that contains subsidiary statechart diagrams within individual Sta
405. rfaces and Stereotypes StereoType Base Element ArgoUML support responsibility Comment yes self AssociationEnd yes send Usage yes signalflow ObjectFlowState yes source Abstraction no stateInvariant Constraint no stub Package yes systemModel Package yes table Abstraction no thread Classifier yes topLevel Package yes trace Abstraction yes type Class yes 290 Glossary A Activity Diagram Action Actor Analysis Association Class Association Attribute of a Class or Object CASE Class Class Diagram A UML diagram capturing the dynamic behavior of a system or sub system See Section 6 10 Activity Diagrams To be written for more information Behavior associated with States or Transitions in State Diagram These actions are invocations of Methods and appear on Sequence and Collaboration Diagrams A representation of an agent animate or inanimate on a Use Case Diagram external to the system being designed Analysis is the process of taking the customer requirements and re casting them in the language of and from the perspective of a putative solution A class that characterizes the association between two other classes A relationship between two classes in a Class Diagram or between Use Cases or Use Cases and Actors in a Use Case Diagram An attribute of a class or object is a specification of a data element encapsulated
406. rials and use of stereotypes To be written 55 Design 6 5 2 Class Attributes and Operations To be written To be written 6 5 2 1 Class Attributes To be written To be written 6 5 2 2 Class Operations To be written To be written 6 5 3 Advanced Class Features 6 5 3 1 Operations on Interfaces 6 5 3 1 1 Interfaces that extend interfaces Add a unnamed interface to the current classdiagram by single clicking on the interface icon in the tool bar and then clicking at the diagram pane see Figure 6 1 Selecting the Interface tool Figure 6 1 Selecting the Interface tool Then double click on the interfaces name field to change it s name as shown in Figure 6 2 Interface ar tifact on the Class Diagram Figure 6 2 Interface artifact on the Class Diagram and type a name for it like Test Interface in this case Press Enter when the name is complete You could also enter the name by going to the Properties Tab in the Details Pane after adding the inter face Add another interface with a different by repeating the last 2 steps Then single click on the Generaliza tion icon in the tool bar as shown in Figure 6 3 Generalization on the Class Diagram tool bar Figure 6 3 Generalization on the Class Diagram tool bar move the mouse pointer to the subinterface press the left mouse button and drag the generalization to the superinterface where you release the mouse button
407. rises the following settings 83 The Menu bar Figure 10 16 The dialog for Settings Appearance e Look and Feel The choice made here influences the complete User Interface It only becomes effective when ArgoUML is exited and restarted e Metal Theme This item is downlighted if the Metal LAF is not chosen The choice made here in fluences the complete User Interface It only becomes effective when ArgoUML is exited and restar ted e Smooth edges of diagram lines and text This feature is known as anti aliasing on certain platforms It causes diagonal lines to look much less jagged by making use of several shades of gray This feature only works if the operating system supports it 10 4 5 5 Notation Tab This tab allows the user to specify certain notation settings i e how things are shown on diagrams It comprises the following check boxes All settings here only define the defaults used for new projects If you want to change the way the dia grams in your current project look then see the File Properties menu Figure 10 17 The dialog for Settings Notations e Notation Language UML 1 4 by default This feature allows changing the default notation i e language UML Java used on the diagrams for new projects Suppose that a designer indic ates that the default notation of a project is Java When he saves the project the choice for Java is stored inside the project file If someone else is viewi
408. rma que contiene funciones C para el manejo de imagenes PNG PostScript PS http en wikipedia org wiki PostScript es un lenguaje de descripci n de pagina y lenguaje de programaci n usado primeramente en la areas de publicaci n asistida por ordenador y electronica e Scalable Vector Graphics SVG http en wikipedia org wiki Scalable_Vector_Graphics es un len guaje de marcado XML para describir graficos vectoriales bidimensionales estaticos y animados y de forma declarativa o mediante scrip Es un estandar abierto creado por el World Wide Web Consor 13 OOA amp D basada en UML tium El uso de SVG en la web esta en sus primeros pasos Hay un gran problema en la inercia debida al largo tiempo de uso de formatos basados en mapas de bits y otros formatos como Macromedia Flash or Java applets pero ademas el soporte por navegadores web es todav a desigual con soporte nativo en Opera y Firefox pero Safari y Internet Explorer necesitan un plugin Mira PGML mas ar riba 3 3 2 3 Object Constraint Language OCL 3 3 3 3 3 4 Object Constraint Language OCL http en wikipedia org wiki Object_Constraint_Language es un lenguaje declarativo para describir reglas que se aplican a modelos UML Fu desarrollado en IBM y ahora es parte del estandar UML Inicialmente OCL fu solo una especificaci n formal de una ex tensi n de lenguaje para UML OCL puede ahora ser usado con cualquier metamodelo compatible con Meta Object
409. ro PIN no lo es Hay una zona intermedia entre estos dos extremos Como veremos a menudo es util dividir casos de uso muy grandes en peque os subcasos de uso Por ejemplo podemos tener subcasos de uso cubriendo de positos de dinero retiradas de dinero y consultas de cuenta No hay una regla clara y r pida Algunos arquitectos preferir n un peque 0 numero de casos de uso relativamente grandes otros en en cambio preferir n un gr n n mero de peque os casos de uso Una regla util a primera vista es que cualquier proyecto practico deber a requerir no mas de alrededor de 30 casos de uso si necesita mas deber a ser dividido en proyectos separados Luego mostramos la relaci n entre casos de uso y actores en uno o mas diagramas de casos de uso Para un proyecto grande puede ser necesario mas de un diagrama Normalmente los grupos de casos de uso relacionados son mostrados en un mismo diagrama Debemos luego dar una especificaci n mas detallada de cada caso de uso Esto cubre su comportami ento normal comportamientos alternativos y cualquier precondici n y postcondici n Esto se refleja en un documento conocido como especificaci n de caso de uso o escenario de caso de uso Finalmente puesto que los casos de uso son funcionales en su naturaleza necesitamos un documento para capturar los requerimientos no funcionales capacidad rendimiento necesidades de entorno etc Estos requerimientos son capturados en un documento conocido como
410. roduce and market a line of ATM devices The purpose of this project is to produce the hardware and the software to drive it that are both maintainable and robust 4 5 1 2 Goals To produce better designed products based on newer technology Follow the MDA philosophy of the OMG by producing first a Platform Independent Model PIM As current modeling technology does not admit of maintaining the integrity of the connection between the PIM and Platform Specific Models 43 Captura de Requerimientos PSMs the PIM will become comparatively stable before the first iteration of the PSM is produced The software platform will be Java technology The system will use a simple userid from ATM card and password or PIN mechanism 4 5 1 3 Market Context Equipment currently on the market is based on older technology for both hardware and software This technology has not reached the end of its useful life making it unlikely that the vendors of that gear are going to update it in the near future On the other hand newer technology is available that would put us at a competitive advantage if implemented now 4 5 1 4 Stakeholders Among the stakeholders for this system are the Engineering Department the Maintenance Department and the Central Computer Facility The full list of these stakeholders and the specific individuals repres enting them are e Engineering Bunny Bugs e Maintenance Hardy Oliver e Computer Facility Laurel St
411. role to the receiving classifierrole e Add Vertical Space to Diagram Add vertical space to a diagram by moving all messages below this down Click the mouse at the point where you want the space to be added and drag down the screen vertically the distance which matches the height of the space you d like to have added e Remove Vertical Space in Diagram Remove vertical space from diagram and move all elements below up vertically Click and drag the mouse vertically over the space that you want de leted 12 3 7 Collaboration Diagram Specific Tools Three tools are provided specific to UML artifacts on collaboration diagrams The detailed properties of these artifacts are described in the section on collaboration diagram artifacts see Chapter 21 Collabora tion Diagram Artifact Reference 110 The Editing Pane e Classifier Role Add a classifier role to the diagram e Association Role Add an association role between two classifier roles selected using button 1 motion from the originating classifier role to the receiving classifier role There are 6 types of asso ciation roles offered here see Figure 12 4 The association tool selector association ag gregation and composition and all these three can be bidirectional or unidirec tional e Generalization Add a generalization between two artifacts selected using button 1 from the child to the parent e Dependency Add a dependency between two artifacts
412. rom which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for an Operation 18 7 2 Operation Property Toolbar 200 Class Diagram Artifact Reference Go up Navigate up through the package structure New operation This creates a new operation within the owning class of the current operation navigating immedi ately to the properties tab for that operation Tip This is a very convenient way to add a number of operations one after the other to a class New parameter This creates a new parameter for the operation navigating immediately to the properties tab for that parameter New raised signal This creates a new raised signal for the operation navigating immediately to the properties tab for that raised signal New Datatype This creates a new Datatype see Section 16 3 Datatype in the namespace of the owner of the operation navigating immediately to the properties tab for that datatype New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected operation navigating immediately to the properties tab for that stereotype Delete This deletes the operation from the model Warning This is a deletion from the model not just the diagram If desired the whole operation compartment can be hidden on the diagram using the presentation tab see Sec tion 18 7 2
413. roperty Fields For Message Name Text box The name of a message is usually its sequence number either an integer or a decimal allowing alternative message hierarchies to be clearly described ArgoUML will supply an integer 267 Collaboration Diagram Artifact Reference sequence number by default Stereotype Drop down selector Message has no stereotypes by default in the UML standard Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Interaction Text box Records the Interaction of which the message is a part Button 1 double click on the entry will navigate to the interaction Sender Text box Identifies the classifier role which sent this message Button 1 double click navigates to the sender classifier role Receiver Text box Identifies the classifier role which receives this message Button 1 double click navigates to the receiver classifier role Activator Drop down selector Identifies the message which invokes the behavior that causes the sending of this message Button 1 click allows selecting the message Action Text box Lists the action see Section 20 3 Action this message invokes to raise a stimulus Button 1 double click navigates to the selected action button 2 gives a pop up menu with the fol lowing entry e New Add a new action This item is downlighted if an action already
414. roporcionadas por la herramienta Y soportan el proceso de dise 0 en que permiten al dise ador construir diagramas en el estilo de metodologias de dise 0 populares Pero tipicamente no porporcionan soporte de proceso para guiar al dise ador a traves de la tarea de dise 0 En su lugar los dise adores tipicamente comi enzan con una p gina en blanco y deben recordar cubrir todos los aspectos del dise o ArgoUML es un entorno de dise o orientado a dominio que proporciona soporte cognitivo de dise o orientado a objetos ArgoUML proporciona algunas de las mismas caracteristicas de automatizaci n de una herramienta CASE comercial pero esta enfocado en caracteristicas que soportan las necesidades cognitivas de los dise adores Estas necesidades cognitivas estan descritas por tres teorias cognitivas 1 reflection in action Ze opportunistic design and 3 comprehension and problem solving ArgoUML esta basado en la especificaci n UML 1 4 El nucleo del modelo de repositorio es una im plementaci n de el Java Metadata Interface JMI que directamente soporta MOF y usa la versi n legible por maquina de la especificaci n UML 1 4 proporcionada por OMG Ademas es nuestra meta proporcionar soporte exhaustivo para OCL el Object Constraint Language y XMI el formato XML Model Interchange ArgoUML fue originariamente desarrollado por un peque o grupo de gente como un proyecto de in vestigaci n ArgoUML tiene muchas caracteristicas
415. s 4 2 El Prodeso de Captura de Requerimientos Empezamos con una visi n general del problema que estamos resolviendo y las areas clave de funcion alidad que debemos tratar en cualquier soluci n Este es nuestro documento de visi n y deber a ser de solo algunas p ginas de longitud Por ejemplo la visi n general de un cajero automatico automated teller machine ATM puede ser que deber a soportar lo siguiente 1 Depositos monetarios reembolsos monetarios y consultas de cuenta por los clientes 2 Mantenimiento del equipamiento por los ingenieros del banco y descarga de depositos y carga de dinero por la sucursal local del banco 3 Auditorias de todas las actividades enviadas al sistema central del banco Desde esta visi n general podemos extraer las actividades principales del sistema y los agentes exter nos personas equipamiento que est n involucradas en estas actividades Estas actividades son cono cidad como casos de uso y los agentes externos son conocidos como actores Los actores pueden ser personas o maquinas Desde un punto de vista practico es beneficioso conocer la parte implicada detras de cada maquina puesto que solo ellos ser n capaces de tratar con el proceso de captura de requerimientos 29 4 2 1 Captura de Requerimientos Los casos de uso deber as ser actividades significativas para el sistema Por ejemplo el uso por el cli ente del Cajero Automatico es un caso de uso Introducir un nume
416. s We most likely already in the design had a programming language in mind because some of the design considerations are to care for a specific language The output of this process is the set of files that constitute the program that solves the problem Once again the recursive and iterative nature of our process means we will come back to the Build phase many times in the future There is also another side to this and that is the reverse engineering side If we happen to have an old program that we would like to examine then we could take the files and reverse engineer them to create a design This can be used when trying to understand some not so well documented program or as a quick start for the design work The process of going back and forth between doing changes in the design followed by a code generation and then doing changes in the code followed by a reverse engineering using for every change the best possible perspective is called Round trip Engineering 7 2 Code Generation 7 2 1 The output of the Code Generation is the completed program Depending on the contents of the design we could also generate Unit test cases To do the work we need the design model containing both static and dynamic descriptions of the pro gram Generating Code from the Static Structure It is rather straightforward to do this generation at least as long as we do it for an object oriented lan guage This is some of the basic rules e A cla
417. s diagram is an alternative to the statechart diagram and is better suited to systems with a great deal of user interaction See Chapter 22 Activity Diagram Artifact Reference for details of the ArgoUML activity diagram and the artifacts it supports e Interaction diagrams There are two diagrams in this category used to show the dynamic interac tion between objects class instances in the system e Sequence diagram Shows the interactions typically messages or procedure calls between in stances of classes objects and actors against a timeline Particularly useful where the timing re lationships between interactions are important See Chapter 19 Sequence Diagram Artifact Ref erence for details of the ArgoUML sequence diagram and the artifacts it supports e Collaboration diagram Shows the interactions typically messages or procedure calls between instances of classes objects and actors against the structural relationships between those in stances Particularly suitable where it is useful to relate interactions to the static structure of the system See Chapter 21 Collaboration Diagram Artifact Reference for details of the ArgoUML 166 Top Level Artifact Reference collaboration diagram and the artifacts it supports e Implementation diagrams UML defines two implementation diagrams to show the relationship between the software components that make up a system the component diagram and the relation ship between the so
418. s or false meaning it cannot Note Derived interfaces still have their value in analysis to introduce useful names or concepts and in design to avoid re computation 219 Class Diagram Artifact Reference Note The UML Element metaclass from which all other artifacts are derived includes the tagged element documentation which is handled by the documentation tab under ArgoUML Checklist Standard tab for an Interface 18 15 2 Interface Property Toolbar Go up Navigate up through the package structure New operation This creates a new operation see Section 18 7 Operation within the interface navigating imme diately to the properties tab for that operation New reception This creates a new reception navigating immediately to the properties tab for that reception New interface This creates a new interface in the same namespace as the selected interface navigating immedi ately to the properties tab for the new interface New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected interface navigating immediately to the properties tab for that stereotype Delete This deletes the interface from the model Warning This is a deletion from the model not just the diagram To delete an interface from the diagram but keep it within the model use the main menu Remove From Diagram or press the Delete key 18 15 3 Property Fields For Interface Name Text b
419. s a sequence diagram with all possible ar tifacts displayed Figure 19 1 Possible artifacts on a sequence diagram 19 1 1 Limitations Concerning Sequence Diagrams in ArgoUML The sequence diagram is still rather under developed in ArgoUML The biggest difficulties are with the actions behind the stimuli These are purely textual in implementa tion and there is no way to link them back to their associated operations or signals 19 2 Object An object is an instance of a class In the UML metamodel Ob ject is a sub class of Instance With in a sequence diagram objects may be used to represent a specific instance of a class Unlike collabora tion diagrams see Chapter 21 Collaboration Diagram Artifact Reference sequence diagrams cannot show generic behavior between classifier roles An object is represented on a sequence diagram in ArgoUML as a plain box labeled with the object name if any and class name separated by a colon As links with stimuli to and from other objects are added a time line grows down from the object This is thin where the object does not have control and thick where it does Caution The current release of ArgoUML shows interactions between objects although the UML standard for sequence diagrams is for interaction between instances of any classifier However the actual implementation in ArgoUML permits any classifier to be used with the 225 Sequence Diagram Artifact Reference objec
420. s menu entry creates a blank statechart diagram associated with the currently selected class and se lects that diagram in the editing pane It also creates a Statemachine UML element which is a con tainer for the elements shown on the new diagram Statechart diagrams are associated with a model element capable of dynamic behavior such as a classifi er or a behavioral feature which provides the context for the state machine it represents Suitable model elements are e g a class an operation and a use case If such element is not selected at the time the New Statechart Diagram menu is activated then an unattached statemachine is created To obtain a well formed UML model you have to set the context of the statemachine on its details pane 10 6 6 New Activity Diagram This menu entry creates a blank activity diagram associated with the currently selected class and selects that diagram in the editing pane It also creates a Act ivit yGraph UML element which is a container for the elements shown on the new diagram Activity diagrams are associated with a model element capable of dynamic behavior such as packages classifiers including use cases and behavioral features Suitable model elements are e g a class a use case an operation and a package If such element is not selected at the time the New Activity Diagram menu is activated then an unattached ActivityGraph is created To obtain a well formed UML model you have to set the co
421. s on the current pane ie the last one you clicked in explorer pane editing pane to do pane details pane One rule applies in all cases though the selection on the dia gram editing pane and in the explorer are always synchronised If the editing pane is the current pane First everything in the explorer and on the current dia gram is deselected and then everything that is on the current diagram is selected and if the same items apear in the explorer then they are also there indicated as selected because they are always synchronised If the explorer pane is the current pane All visible items in the explorer pane are selected and 80 The Menu bar non visible items are deselected If the to do pane is the current pane All visible items in the to do pane are selected and non visible items are deselected In fact this works the same as for the explorer pane because both are tree structures If the details pane is the current pane The function only works when the cursor is in certain fields where selecting is possible e g a Name field In such a case the Select All function extends the current selection to the whole field contents e Navigate Back ArgoUML keeps a record of the artifacts that you have been selecting while nav igating the model This button moves you back to the previous one selected If there are no more pre vious artifacts the button is grayed out e Navigate Forward ArgoUML keeps a record of t
422. se Extend Relationships 175 Use Case Extension Points 175 Use Case Generalization 175 Use Case Include Relationships 175 Use Case Modifiers 174 Use Case Name 174 Use Case Namespace 174 Use Case Realization 294 Use Case Specialization 175 Use Case Specification 296 Use Case Stereotype 174 Use Case Hierarchical 41 V View Menu 19 View Toolbar 20 Visibility of Association End 216 of Attribute 198 of Datatype 159 of Enumeration 162 of Model 155 of Operation 202 Vision Document 296 Case Study 43 W W3C 296 Waterfall Design Process 297 X XMI xvii 13 24 25 25 297 XML xvii xviii 297 317
423. selected using button 1 motion from the de pendent artifact e Add Message Add a message to the selected association role Note This tool is grayed out except when an association role is selected 12 3 8 Statechart Diagram Specific Tools Eleven tools are provided specific to UML artifacts on statechart diagrams The detailed properties of these artifacts are described in the section on statechart diagram artifacts see Chapter 20 Statechart Diagram Artifact Reference e Simple State Add a simple state to the diagram Composite State Add a composite state to the diagram All artifacts that are subsequently placed on the diagram on top of the composite state will form part of that composite state e Transition Add a transition between two states selected using button 1 motion from the originat ing state to the receiving state e Synch State Add a synchstate to the diagram e Submachine State Add a submachinestate to the diagram e Stub State Add a stubstate to the diagram e Initial Add an initial pseudostate to the diagram Caution There is nothing to stop you adding more than one initial state to a diagram or composite state However to do so is meaningless and one of the critics will complain e Final State Add a final state to the diagram e Junction Add a junction pseudostate to the diagram Caution A well formed junction should have at least one incoming transition and exactly one 111 The Ed
424. selector Node instance has no stereotypes by default in the UML standard Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Drop down selector Records the namespace for the node instance This is the package hierarchy Stimuli sent To Be Written Stimuli Received To Be Written Residents Text box Lists any residents see Section 23 4 Component designed to be deployed on this type of node Button 1 double click navigates to the selected entry Classifiers Text field A Node instance type can be selected here Caution ArgoUML V0 18 lists many more items in the dropdown list then solely Nodes Be ware to select Nodes only 23 4 Component A component type represents a distributable piece of implementation of a system including software code source binary or executable but also including business documents etc in a human system Components may be used to show dependencies such as compiler and run time dependencies or inform ation dependencies in a human organization In the UML metamodel it is a sub class of Classifier A component is represented on a class diagram as a box with two small rectangles protruding from its left side labeled with its name 23 4 1 Component Details Tabs The details tabs that are active for components are as follows 278 Deployment Diagram Artifact Ref
425. since supervisors can also act as salesmen but not vice versa Generalization is analogous to class inheritance within OO programming Note It is easy to confuse extends relationships between use cases with generalization However extends is about augmenting a use case s behavior at a specific point Generalization is about specializing the behavior throughout the use case Within the UML metamodel Generalization is a sub class of Relationship Generalization is represented as an arrow with white filled head from the specialized use case or actor to the generalized use case or actor see Figure 17 1 Possible artifacts on a use case diagram 17 8 1 Generalization Details Tabs The details tabs that are active for associations are as follows ToDoltem 178 Use Case Diagram Artifact Reference Standard tab Properties See Section 17 8 2 Generalization Property Toolbar and Section 17 8 3 Property Fields For Generalization below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds of the generalization are downlighted since they have no meaning given that the generalization is tied to a particular actor and use case Source Standard tab You would not expect to generate any code for a generalization end so this is empty Tagged Values Standard tab In the UML metamodel Generalization has the following standard
426. sion defining the associated action It is accompagnied by an arrow pointing in the direction of the communication i e the direction of the AssociationRole By convention the name of a message is not shown on the diagram Instead the diagram displays the message sequence number either as an integer or as a decimal number to show hierarchy Warning The current release of ArgoUML does not retaining message positioning after reloading the project i e as if the positions were not stored in the project file 21 5 1 Message Details Tabs The details tabs that are active for messages are as follows ToDoltem Standard tab Properties See Section 21 5 2 Message Property Toolbar and Section 21 5 3 Property Fields For Message below Documentation Standard tab Presentation Standard tab The values for the bounds of the message define the bounding box of the message The Line field defines the arrow color Increasing the Shadow size has an esthetically question able effect Caution In the VO 18 release of ArgoUML changing the position of the message by editing the values of the Bounds field is possible but will make only a temporary change to the position of the message as described above Source Standard tab showing the message number and action expression separated by a colon when UML 1 4 is selected in the drop down Caution A message probably should not generated any code of itself That should be left
427. sos de uso Retirar Dinero en nuestro ejemplo de Cajero Automatico 1 Consumidor indica que se requiere recibo 2 Consumidor introduce cantidad de dinero requerido 3 Cajero Automatico verifica con el ordenador central que el consumidor puede realizar esta op eraci n 4 Cajero Automatico entrega el dinero a el consumidor 5 Cajero Automatico emite recibo al consumidor Recuerda que esta es un sub caso de uso incluido en el caso de uso principal Usar Cajero Automatico el cual presumiblemente manejar la verificaci n de tarjetas y PINs antes de invocar este caso de uso incluido Note El primer paso no es una condici n Tomamos como nuestro flujo b sico el caso donde el consumidor quiere un recibo El caso donde de consumidor no quiere un recibo ser un flujo alternativo 4 3 3 2 Especificando los Flujos Alternativos Esto captura los escenarios alternativos como flujos lineales mediante referencia la flujo b sico Ini cialmente unicamente construimos una lista de los flujos alternativos A A Consumidor no requiere recibo 1 A La cuenta del consumidor no soportar el retiro de dinero 2 A Comunicaci n con el ordenador central est interrumpida 3 A El consumidor cancela la transacci n 4 36 Captura de Requerimientos A El consumidor falla a coger el dinero entregado ay Subsequently we flesh out each alternate flow by reference to the basic flow For example the first al tern
428. ss 105 12 2 5 Alt with Button 1 Motion occoccocnoconcnnconcnnconcnnroncnnroncnnronanaronos 105 12 2 6 Button 2 Actions oococononocononocononocononorononorononoronororonororononoros 105 12 2 7 Button 2 Double Click esor ese e EE iE eTR EE E 106 12 2 8 Button 2 Motion e eraso sn etai an e a Si 106 12 3 The tool bari menine E E E atada ea 106 12 3 4 Layout Tools eii ee ne aina e EEE SEEE EE e EERST 106 1223 2 Annotation Tools espi a nan ins aa ii Eaa i aA 107 12 3 3 Drawing Fools eiren as a a n EEA a O EE 107 12 3 4 Use Case Diagram Specific Tools ee ee ceee cence eeee teenies 108 viii ArgoUML Manual de Usuario 12 3 5 Class Diagram Specific Tools 20 0 0 cece cee cee ceeece teen essa eeenes 109 12 3 6 Sequence Diagram Specific Tools 2 0 0 0 eee eee cece eeeeeeeeee 110 12 3 7 Collaboration Diagram Specific Tools 1 0 0 0 cece eeee eee ee ee 110 12 3 8 Statechart Diagram Specific Tools 2 0 0 0 ee ceee eee eeeeeeeeen es 111 12 3 9 Activity Diagram Specific Tools 2 0 0 0 ee eeeceeeeeeeee teen es 112 12 3 10 Deployment Diagram Specific Tools cece cece eee eeeeee ee 113 12 4 The Broca dia 114 12 3 Selection Action BUttONS apeissonar iron tu eaS a aa EEE ASEET 115 12 0 Clarifiers e 115 12 7 The Drawing Grid escocesa lec tetas gaa e a e r 116 12 8 The Diagram Tab feiss yepe E A creciera rca s Re 116 12 9 Pop Upi Menus ci dt eds 116 12 9 1 CHTQUES dota 116 129 2 Orderin
429. ss will become a class In some target languages like java c they also become files and compilation units e A generalization will become an inheritance If the target language does not support inheritance and we didn t address this during the design some special conversions are required to solve this 62 Code Generation Reverse Engineering and Round Trip Engineering e An attribute will become a member variable e A navigable association will become a member variable Depending on the target language target platform and the association multiplicities this will be a pointer a reference a collection class an entry in some table or map e A non abstract operation in a class will become a method e An abstract operation in a class will become an abstract method e An in parameter in an operation will become a parameter in the method For simple types int boolean this is the normal case For C these will probably const classes For Java this cannot be enforced for classes e An out or in out parameter in an operation will become a referenced parameter in the method For C these will be referenced non const parameters For Java classes this is the default Simple types int boolean must in java be converted to an object of a corresponding class Integer Boolean e The visibilities of the attributes associations and operations will become visibilities on the member variables or methods e Packages wi
430. sssssons safes senns seeceug aE RLE oE EERE E PEPEE TIRS SEES 232 19 9 LINK srin h vest Sees i n E O E EEAS gusesssuned tangs deze 233 19 9 1 Cink Details Tabs iii iodo 233 199 2 Link Property ToolBaf seynna en a EEE S 234 19 9 3 Property Fields For Link oooooccnnconcconiconccnnconoconoconacnnncnnnonoso 234 20 Statechart Diagram Artifact Reference ooocoocccccnnncnnccnnconnconncnnconnconnccnnconaconacos 236 20 1 Introduce Io 236 20 1 1 Limitations Concerning Statechart Diagrams in ArgoUML 236 20 2 States o s oo ssp isons ches be Eek Ee p lore E SE eE ESEA SNO S E oE 236 20 2 1 State Details Tabs ciar pad eaa EEO TE 236 20 2 2 State Property Toolbar oooococcnnccnnconnconoconoconncnnacnnncnnccnaronicnno 237 20 2 3 Property Fields For State comicos cotorra ereas eea rE ER orbe 237 20 3 ACTON sirbe idin ec EEN 239 20 3 1 Action Details Tabs 232 sescces ped esas oetseasusgasssaacesaseaenne apes actual 239 xiii ArgoUML Manual de Usuario 20 3 2 Action Property Toolbar oooocccoccnnccnnconoconnconncnnncnnncnononaronicnno 240 20 3 3 Property Fields For Action ocoooccnnconcconccnnncnncnnncnnncnnncnnncnanonose 240 20 4 Composite State iii o Se ate a ee 241 20 5 Concurrent Regio sardinas tics stat eae ES 242 20 6 Submachine State sevcoscsde doves irritan dintel aser 242 20 7 SUID Stale osos potted cds bia noah dea nsate aa E tessa iria MENGE Meese 242 20 8 Transitlon ici iio 243 2
431. stances such that their attributes have valid values This class probably needs a constructor because not all of its attributes have initial values 139 The Critics Defining good constructors is key to establishing class invariants and class invariants are a powerful aid in writing solid code To fix this add a constructor manually by clicking on class in the explorer and adding an operation us ing the context sensitive pop up menu in the property tab or select class where it appears on a class dia gram and use the Add Operation tool In the UML 1 4 standard a constructor is an operation with the stereotype create Although not strictly standard ArgoUML will also accept Create as a stereotype for constructors By convention in Java and C a constructor has the same name as the class is not static and returns no value ArgoUML will also accept any operation that follows these conventions as a constructor even if it is not stereotyped create Caution Operators are created in ArgoUML with a default return parameter named return You will need to remove this parameter to meet the Java C convention 15 5 4 Reduce Attributes on a Class Suggestion that the class has too many attributes for a good design and is at risk of becoming a design bottleneck The Wizard of this critic allows setting of the treshold i e the maximum number of attributes allowed before this critic fires Caution This numbe
432. stente de renombar sea mostrado dentro del panel de propiedades proponiendo usar el nombre untitledmodel todo en minusculas 3 4 4 2 Cr ticas de Dise o Funcionando El Asistente de Renom brar Paquete Sustitulye el nombre untitledmodel con purchasingmodel y haz click el el botton Terminar Figure 3 11 Ventana de ArgoUML Mostrando el Asistente de Cr tica para Renombrar el Paquete muestra como la ventana de ArgoUML aparecer ahora 27 OOA amp D basada en UML Figure 3 11 Ventana de ArgoUML Mostrando el Asistente de Cr tica para Renombrar el Paquete Observa ahora como la nota de la cr tica de dise o en el panel de Tar as Pendientes desaparece de jando solo la nota A ade elementos al paquete purchasingmodel en la lista de Tar as Pendientes Si esto no ocurre al momento espera algunos segundos ArgoUML hace uso intensivo de muchos hilos de ejecuci n que se ejecutan en paralelo Esto puede causar demoras de algunos segundos antes de que la informaci n se actualize en la pantalla El cambio del nombre del paquete deber a ser reflejado en el explorador en la esquina superior izquierda de tu ventana de ArgoUML Ahora estamos preparados para crear nuestro primer diagrama UML un diagrama de Casos de Uso pero primero guardemos lo que hemos hecho hasta ahora Haz click en el elemento de men Archivo y seleciona Guardar Proyecto Ahora puedes salir de forma segura de ArgoUML sin perder tu trabajo hasta el mo
433. sy way to precisely align objects that are already roughly aligned Furthermore the broom s distribution options are suited to the needs of UML designers making related objects appear evenly spaced packing objects to save diagram space and spreading objects out to make room for new objects The broom also makes it easy to change from horizontal to vertical alignment or from left alignment to right alignment The T shaped icon in ArgoUML s diagram toolbar invokes the broom alignment tool When the mouse button is pressed while in broom mode the designer s initial mouse movement orients the broom to face in one of four directions north south east or west After that mouse drag events cause the broom to advance in the chosen direction withdraw or grow in a lateral direction Like a real world push broom the broom tool pushes diagram elements that come in contact with it This has the effect of align ing objects along the face of the broom and provides immediate visual feedback see the figure below Unlike a real world broom moving backwards allows diagram elements to return to their original posi tion Growing the broom makes it possible to align objects that are not near each other When the mouse button is released the broom disappears and the moved objects are selected to make it easy to manipu late them further 114 12 5 12 6 The Editing Pane Figure 12 5 The Broom If the designer presses the space bar while
434. t and so the diagram can successfully represent instances of actors for example as well as classes 19 2 1 Object Details Tabs The details tabs that are active for objects are as follows ToDoltem Standard tab Properties See Section 19 2 2 Object Property Toolbar and Section 19 2 3 Property Fields For Object be low Documentation Standard tab Presentation Standard tab The values for the bounds of the object notionally define the bounding box of the ob ject and its time line However if you change them it will have no effect and the original values will be reset when you next revisit the tab Source Standard tab but with no contents Caution An object should not generate any code so having this tab active is probably a mis take Tagged Values Standard tab In the UML metamodel Object has the following standard tagged values defined persistence from the superclass Instance Showing the permanence of the state inform ation associated with the object Values transitory state is destroyed when the object is des troyed and persistent state is preserved when the object is destroyed e derived from the superclass ModelElement Values true meaning the object is redund ant it can be formally derived from other elements or false meaning it cannot Note Derived objects still have their value in analysis and design to introduce useful names or concepts and in design to avoid re comput
435. t there is a drop down to select the ordering of the atifacts within the hierarchy The two pos sibilities are Order by Type Name and Order by Name The former groups all items per type and sorts them per group alphabetically on the name The lattter simply sorts on name only The following explorer perspectives may be selected in the drop down at the top e Package centric the default The exploring hierarchy is organized by package hierarchy The top level shows the model Under this are all the top level packages in the model and all the artifacts that are directly in the namespace of the model Beneath each package are all the artifacts that sit within the namespace of that package including any further sub packages which in turn have their own sub hierarchies 100 The Explorer e Class centric Shows classes in their package hierarchy as well as datatypes and use case dia gram elements Similar to the Package centric view but it doesn t show connecting or associating elements e Diagram centric In this view the top level comprises all the diagrams in the model Beneath each diagram is a flat listing of all the artifacts on the diagram Artifacts that have sub artifacts that do not appear on the diagram have their own hierarchy for example attributes and operations of classes e Inheritance centric In this view the top level shows the model Beneath this are all artifacts that have no generalization in the model
436. t for every model element the OCL specification only defines classes interfaces and operations as allowable contexts It is not before OCL 2 0 that a more general definition of allowable contexts is introduced The key issue is that for each context definition you need to define what is the contextual Classifier 1 e the classifier that will be associated with the self keyword The creators of the OCL specification claim that this is not an issue for the OCL specification but rather for UML or some integration task force Conversely it seems that the UML specification people seem to expect this to be defined in the OCL specification which is why we did a first step in that direction in OCL 2 0 So to cut a long story short it appeared that the simplest solution for ArgoUML at the mo ment would be to enable the OCL property panel only for those model elements for which there actually exists a definition of the contextualClassifier in OCL 1 4 These are s above Class Interface and Feature The standard pre defines a small number of constraints for example the xor constraint over a set of as sociations indicating that only one may be manifest for any particular instance The standard also envisages a number of circumstances where general purpose constraints may be use ful e To specify invariants on classes and types in the class model e To specify type invariants for stereotypes e To describe pre conditions and post conditions
437. t has no obvious meaning in any practical design 15 9 3 Remove Navigation from Interface via lt association gt Associations involving an interface can be not be navigable in the direction from the interface This is because interfaces contain only operation declarations and cannot hold pointers to other objects This part of the design should be changed before you can generate code from this design If you do gen erate code before fixing this problem the code will not match the design To fix this select the association and use the Properties tab to select in turn each association end that is not connected to the interface Uncheck Navigable for each of these ends The association should then appear with a stick arrowhead pointed towards the interface When an association between a class and interface is created in ArgoUML it is by default navigable only from the class to the interface However ArgoUML does not prevent to change the navigability af terwards into a wrong situation Which will cause this critic to be triggered 15 9 4 Add Associations to lt artifact gt Suggestion that the specified artifact actor use case or class has no associations connecting it to other artifacts This is required for the artifact to be useful in a design 15 9 5 Remove Reference to Specific Subclass This critic is discussed under an earlier design issues category see Section 15 6 3 Remove Reference to Specific Subclass 15 9
438. t time the class is generated the lost code i e the whole member function definition will be added as comment to the end of the file 304 Appendix E Limits and Shortcomings As all products ArgoUML has some limits Those important to the user are listed in this section E 1 Diagram Canvas Size Due to the underlying diagram editing software the canvas size for diagrams is limited to 6000 units in height and width E 2 Missing functions 305 Appendix F Open Publication License F 1 Requirements On Both Unmodified And Modified Versions The Open Publication works may be reproduced and distributed in whole or in part in any medium physical or electronic provided that the terms of this license are adhered to and that this license or an incorporation of it by reference with any options elected by the author s and or publisher is displayed in the reproduction Proper form for an incorporation by reference is as follows Copyright c lt year gt by lt author s name or designee gt This material may be distrib uted only subject to the terms and conditions set forth in the Open Publication Li cense vX Y or later the latest version is presently available at ht tp www opencontent org openpub http www opencontent org openpub The reference must be immediately followed with any options elected by the author s and or publisher of the document see section VI Commercial redistribution of O
439. t to make this clear The association contains at least two ends which may be navigated to via the association property sheet See Section 18 12 Association End for more information 18 11 1 Three way and Greater Associations and Asso 209 Class Diagram Artifact Reference ciation Classes UML 1 3 provides for N ary associations and associations that are governed by a third associative class Both are supported by ArgoUML N ary associations are created by drawing with the association tool from an existing association to a third class The current implementation of ArgoUML does not allow the inverse drawing from a 3rd class towards an existing association is not possible Association Classes are drawn exactly like a normal association i e between two classes but with a dif ferent dedicated tool from the diagram toolbar 18 11 2 Association Details Tabs The details tabs that are active for associations are as follows ToDoltem Standard tab Properties See Section 18 11 3 Association Property Toolbar and Section 18 11 4 Property Fields For As sociation below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds of the Association have no meaning since they are determ ined by the location of the connected items Changing them has no effect on the dia gram Source Standard tab You would not expect to
440. ta as que generalmente se proporciona ayuda altamente cualificada Antes de postear en esta lista deberias echar un vistazo al user FAQ ht tp argouml tigris org faqs users html mantenido por Ewan R Grantham Mas informaci n sobre ArgoUML y otros asuntos relacionados con UML est tambien disponible en el ArgoUML website http argouml tigris org mantenido por Linus Tolke 1 2 Alcance de Este Manual de Usuario 1 2 1 Audiencia Objetivo La publicaci n altual de este documento esta dirigida a usuarios experimentados de UML en OOA amp D quizas con otras herramientas que desean cambiar a ArgoUML 2 1 2 2 Introducci n Publicaciones futuras soportaran dise adores que conocen OOA amp D y desean adoptar la notaci n UML dentro de su proceso de desarrollo Un objetivo a largo plazo es soportar i aquellos que est n aprendiendo dise o y desean empezar con un proceso OOA amp D que usa notaci n UML y ii gente interesada en dise 0 de codigo modularizado con un GUI Alcance La intenci n es que este documento proporcionar una guia exhaustiva permitiendo a los dise adores usar ArgoUML en toda su extensi n Esto es en dos partes e Un manual tutorial mostrando como trabajar con ArgoUML e Un manual de referencia completo registrando todo lo que puedes hacer con ArgoUML La version 0 22 de este documento lleva a cabo la segunda de ellas En esta guia hay algunas cosas que no encontraras porque est n
441. tagged val ues defined e derived from the superclass ModelElement Values true meaning the generalization is redundant it can be formally derived from other elements or false meaning it cannot Note Derived generalizations still have their value in analysis to introduce useful names or concepts and in design to avoid re computation 17 8 2 Generalization Property Toolbar Go up Navigate up through the package structure of the model For a generalization this will be the pack age containing the generalization New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected generalization nav igating immediately to the properties tab for that generalization Delete This deletes the selected generalization from the model Warning This is a deletion from the model not just the diagram To delete a generalization from the diagram but keep it within the model use the main menu Remove From Dia gram or press the Delete key 179 Use Case Diagram Artifact Reference 17 8 3 Property Fields For Generalization Name Text box The name of the generalization Stereotype Tip It is quite common to leave generalizations unnamed in use case analysis Note ArgoUML does not enforce any naming convention for associations Note There is no representation of the name of a generalization on the diagram Drop down selector Generalization is provided by default
442. tateMachine Text box Shows the name of the parent StateMachine for the transition Button 1 double click navigates to the StateMachine shown State Text box Shows the name of the parent State in case of an internal transition Button 1 double click navigates to the State shown Source Text box Shows the source state for the transition Button 1 double click navigates to the selected entry Target Text box Shows the target state for the transition Button 1 double click navigates to the selected entry Trigger Text box Shows the trigger event if any which invokes this transition Note UML does not require there to be a trigger e g when a guard is defined In this case 244 Statechart Diagram Artifact Reference the transition is taken immediately if the guard is true Button 1 double click navigates to the selected entry button 2 gives a pop up menu with three entries e Select Add This Add an existing trigger event A sub menu opens with 4 choices Call Event Change Event Signal Event Time Event e New Add a new trigger event A sub menu opens with 4 choices Call Event Change Event Sig nal Event Time Event e Delete From Model Delete the trigger event from the model This feature is always down lighted in the current version of ArgoUML Guard Text box Shows the name of a guard if any The expression of a guard must be true before this transition can be taken Button 1 dou
443. te to its use in class diagrams and are of limited relevance to use cases The most useful attributes to con sider altering are the name used as the role name and the multiplicity Note 212 Class Diagram Artifact Reference ArgoUML does not currently support showing qualifiers on the diagram as described in the UML 1 3 standard 18 12 1 Association End Details Tabs The details tabs that are active for associations are as follows ToDoltem Standard tab Properties See Section 18 12 2 Association End Property Toolbar and Section 18 12 3 Property Fields For Association End below Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Source Standard tab This tab contains a declaration for the association end as an instance of the artifact to which it is connected Tagged Values Standard tab In the UML metamodel AssociationEnd has the following standard tagged val ues defined e derived from the superclass ModelElement Values true meaning the association end is redundant it can be formally derived from other elements or false meaning it cannot Tip Derived association ends still have their value in analysis to introduce useful names or concepts and in design to avoid re computation However the tag only makes sense for an association end if it is also applied to the parent association Note The UML Element metaclass from
444. te to the use case Extend Text box Lists all use cases which extend the base use case through this extension point 177 Use Case Diagram Artifact Reference Where an extending use case exists button 1 double click will navigate to that relationship 17 5 Association An association on a use case diagram represents a relationship between an actor and a use case showing that actor s involvement in the use case The invocation of the use case will involve some significant change perceived by the actor Associations are described fully under class diagrams see Section 18 11 Association 17 6 Association End Association ends are described under class diagrams see Section 18 12 Association End 17 7 Dependency Dependencies are described under class diagrams see Section 18 13 Dependency Caution Dependency has little use in use case diagrams It is provided because earlier versions of ArgoUML used it incorrectly to implement include and extends relationships 17 8 Generalization Generalization is a relationship between two use cases or two actors Where A is a generalization of B it means A describes more general behavior and B a more specific version of that behavior Examples for a travel agent sales system might be the use case for making a booking as a generalization of the use case for making a flight booking and a salesman actor being a generalization of a supervisor actor
445. te which is only partly implemented 22 2 Action State An action state represents execution of an atomic action usually the invocation of an action Within the UML metamodel ActionState is a sub class of SimpleState It is a specialized simple state that only has an entry action and with an implicit trigger as soon as that action is completed Caution As a consequence any outgoing transitions from an action state should not have explicit triggers defined ArgoUML will not currently check for this They may have guards to provide a choice where there is more than one transition Note Unlike an ordinary state an internal transition an exit action and a Do activity are not per mitted for action states An action state is represented on an activity diagram in ArgoUML as a rectangle with rounded corners containing the name of the action state Caution 269 Activity Diagram Artifact Reference The UML standard specifies that the text shown in the action state on the activity diagram should contain the expression associated with the entry action which is implemented as such since ArgoUML V0 18 In past versions of ArgoUML 0 16 1 and before the dia gram used to show the action state name Loading a project created by one of the older ver sions causes the project file to be converted to the correct format to conform to the UML standard This process is designed to be transparent for the user and the only drawback is t
446. ted after the target instance is cre ated 11 created and deleted by the source after the target instance is created or 111 not created or deleted by the source after the target instance is created Visibility Radio box with four entries public private protected and package Indicates whether navigation to this end may be by i any classifier ii only by the source classifier or iii only the source classifier and its children 18 13 Dependency Dependency is a relationship between two artifacts showing that one depends on the other Within the UML metamodel Dependency is a sub class of Relationship Dependency is represented as a dashed line with an open arrow head from the depending artifact to that which it is dependent upon 18 13 1 Dependency Details Tabs The details tabs that are active for dependencies are as follows ToDoltem Standard tab Properties See Section 18 13 2 Dependency Property Toolbar and Section 18 13 3 Property Fields For De pendency below 216 Class Diagram Artifact Reference Documentation Standard tab See Section 13 4 Documentation Tab Presentation Standard tab Note The values for the bounds of the dependency are downlighted given the dependency 1s tied to a particular modelelement Tagged Values Standard tab In the UML metamodel Dependency has no tagged values of its own but through superclasses has the following standard tagged values defined
447. tending through this extend relationship Button 1 click on this entry will give a drop down menu of all available use cases and an empty entry which may be selected by button 1 click Extension Points Text box If this use case is or can be extended this field lists the extension points for the use case Note Extension points are listed by their location point rather than their name Where an extension point has been created button 1 double click will navigate to that relationship Button 2 gives a pop up menu with two entries e Add The Ad Remove ExtensionPoints window opens In this window it is possible to build a list of extension points e New Add a new extension point in the list and navigate to it The current extend relationship is added as the first in list of extending relationships of the new extension point Condition Text area Multi line textual description of any condition attached to the extend relationship 17 10 Include Include is a relationship between two use cases Where A includes B it means B described behavior that is to be included in the description of the behavior of A at some point defined internally by A Examples for a travel agent sales system might be the use case for booking travel which includes use cases for booking flights and taking payment Within the UML metamodel Include is a sub class of Relationship An include relationship is represented as a dotted link with an o
448. tes A relationship between two Use Cases where the included Use Case describes part of the functionality of the including Use Case A design process where each all phases requirements analysis design build test are tackled partially in a series of iterations See Section 3 2 1 Tipos de Procesos for more information A fully object oriented programming language introduced by Sun Microsystems More strongly typed than C it compiles to an in terpreted code the Java Virtual Machine JVM The JVM means that Java code should run on any machine that has implemented the JVM The most significant component of Java was integration of the JVM into web browsers allowing code Applets to be download and run over the web ArgoUML is written in Java A Statechart Diagram where actions are associated with States A method of a class or object is a specification of behavior encapsu lated by that object A Statechart Diagram where actions are associated with Transitions 293 Glossary Object OCL OMG OOA amp D Opportunistic Design Pane Realization Use Case Reflection in Action An instance of a Class Classes and objects in UML are represented on Activity Diagrams Class Diagrams Collaboration Diagrams and Sequence Diagrams Object Constraint Language A language for describing constraints within UML The Object Management Group An international industry standard ization body Best k
449. tes such duplication 15 16 7 Define Concrete Sub Class Suggestion that a class is abstract with no concrete subclasses and so can never be realized 15 16 8 Define Class to Implement lt interface gt Suggestion that the interface referred to has no influence on the running system since it is never imple 149 The Critics mented by a class 15 16 9 Change Multiple Inheritance to interfaces This critic is discussed under an earlier design issues category see Section 15 14 1 Change Multiple Inheritance to interfaces 15 16 10 Make Edge More Visible This critic is discussed under an earlier design issues category see Section 15 7 14 Make Edge More Visible 15 17 Containment Critics concerning containment in ArgoUML that is where one artifact forms a component part of an other The current version of ArgoUML has the following critics in this category 15 17 1 Remove Circular Composition Suggestion that there is a series of composition relationships associations with black diamonds that form a cycle which is not permitted 15 17 2 Duplicate Parameter Name Suggestion that a parameter list to an operation or event has two or more parameters with the same name which is not permitted 15 17 3 Two Aggregate Ends Roles in Binary Associ ation Only one end role of a binary association can be aggregate or composite This a well formedness rule of the UML 1 4 standard Aggre
450. th it On the other hand implementing a process without having any data structures for it to operate on is not very meaningful 5 1 1 Class Responsibilities and Collaborators CRC Cards The CRC methodology favors the phenomenonologists preference for analysis It is the equivalent of starting with the use cases the process aspects operations of the class diagrams and scenarios from which sequence diagrams can be initiated CRC cards and the associated methodology are described in detail in Appendix G The CRC Card Meth odology They are used again in the design phase and are further discussed in Chapter 6 Design The strength of CRC cards during analysis e Common Project Vocabulary e Spread Domain Knowledge e Making the Paradigm Shift e Live Prototyping e Identifying Holes in Requirements In this phase the group should consist of two or three domain experts one object oriented technology fa cilitator and the rest of the group made up of people who are responsible for delivering the system 47 5 1 2 5 1 3 5 1 4 5 1 5 5 1 6 Analysis The first time that the Analysis phase occurs a special case of the CRC session happens as there are no classes or scenarios to choose from to define a CRC session At this point a special type of session known as brainstorming is held During this session you identify the initial set of classes in the problem domain by using the problem statement or require
451. the generalization Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the dependency This is the package hierarchy Suppliers Text area Lists the end of the relationship that is supplying what is needed by the other end Button 1 double click on a supplier will navigate to that element Clients Text area Lists the depending ends of the relationship i e the end that makes use of the other end Button 1 double click on a client will navigate to that element 18 14 Generalization Generalization is described under use case diagrams see Section 17 8 Generalization Note Within the context of classes generalization and specialization are the UML terms describ ing class inheritance 18 15 Interface An interface is a set of operations characterizing the behavior of an element It can be usefully thought 218 Class Diagram Artifact Reference of as an abstract class with no attributes and no non abstract operations In the UML metamodel it is a sub class of Classifier and through that GeneralizableElement An interface is represented on a class diagram as a rectangle with two horizontal compartments The top compartment displays the interface name and above it interface and the second any opera tions Just like a class the operations compartment
452. the classifier role By convention classifier role names start with a lower case letter and use bumpy caps to divide words within the name Note ArgoUML does not enforce this naming convention Stereotype Drop down selector Classifier Role is provided by default with the UML standard stereotypes for a classifier metaclass powertype process thread and utility 259 Collaboration Diagram Artifact Reference Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the classifier role which is always the containing Collabora tion Button 1 double click on the entry will navigate to the collaboration Multiplicity Editable drop down selector The default value is which means that there are any number of in stances of this classifierrole that play a role in the collaboration The drop down provides some dif ferent multiplicities E g 1 1 would mean that only one instance plays a role in this collaboration ArgoUML does not restrict you to the predefined ranges for multiplicity You can edit this field freely Base List The names of the classifiers of which this is a classifierrole Button 1 double click navigates to the classifier Button 2 click gives a pop up menu with the following entries e Add Allows adding or removeing classifiers to the list To this end a dialo
453. the diagram in pieces on as many pages as needed Pressing the close button of the dialog does the former option 76 The Menu bar Figure 10 8 The diagram exceeds page size dialog Warning If the current diagram contains no selected artifacts then the whole diagram is printed However if one or more artifacts are selected then only the area they cover is printed If scaling is selected by the Fit to page choice in the dialog box descibed above then the scaling is done on basis of the selected artifacts only If scaling is not chosen or in case it is not needed then all pages containing a selected artifact are printed 10 3 11 Export Graphics This menu entry brings up a dialog box allowing the currently selected diagram in the editing pane to be saved in one of a number of graphic formats The dialog box is identical to that for Open Project see Figure 10 2 The file selection dialog for Open Project except for the Files of type The chosen filetype specifies the graphics format used for saving The filename is automatically extended with the corresponding ending if not entered already A default filename is generated based on the diagram name The available graphics types are e GIF image gif e Encapsulated Postscript file eps e PNG image png e Postscript file ps e Scalable Vector Graphics file svg The graphics format that is selected by default is set in the dialog
454. ting which may be smaller larger or the same as the displayed grid Since items are aligned to the grid snap boundary any way when you place them this menu entry has no effect unless you have either changed the grid snap to a larger value or used one of the other Arrange menu entries to push items off their initial positions Distribute This sub menu distributes the selected items There are four distribution options provided 10 7 3 Distribute Horizontal Spacing The leftmost and rightmost selected artifacts are not moved The others are adjusted horizontally until the horizontal space i e from the right edge of the left artifact to the left edge of the right artifact is the same for all of the selected items Distribute Horizontal Centers The leftmost and rightmost selected artifacts are not moved The others are adjusted horizontally until the distance between the horizontal centers of all the selected items is the same Distribute Vertical Spacing The top and bottom selected artifacts are not moved The others are adjusted vertically until the vertical space i e from the bottom edge of the top artifact to the top edge of the bottom artifact is the same for all of the selected items Distribute Vertical Centers The top and bottom selected artifacts are not moved The others are adjusted vertically until the distance between the vertical centers of all the selected items is the same Reorder This sub menu adjusts the order
455. tion Here button 1 is used to activate the user interface component e g a button The object is usually high lighted when the mouse button is pressed and then activated when the mouse button is released Activat ing an user interface object means that its function is executed 8 2 2 3 Navigation Here button 1 is used to move the focus from one user interface component or diagram artifact to anoth er It is better known under the term keyboard focus This because keyboard commands usually work on the artifact that has the focus The focus is indicated by a hardly visible box around the artifact or for a text entry box by a flashing cursor 8 2 2 4 General Behavior When Editing Text Here button 1 is used to select the point within the text at which operations text entry and deletion will take place 67 Introduction 8 2 3 Button 1 Double Click The behavior of button 1 double click varies betweens panes and is discussed in their chapters 8 2 3 1 General Behavior When Editing Text Here button double click is used to select a complete word or other syntactic unit within the text Sub sequent operations text entry and deletion will replace the selected text 8 2 4 Button 1 Motion 8 2 4 1 General Behavior When Editing Text Here button 1 motion is used to select a range of text Subsequent operations text entry and deletion will replace the selected text 8 2 5 Shift and Ctrl modifiers with Button 1 8
456. tion The V0 20 release of ArgoUML only partially implements actions As a practical conven tion it is suggested that call actions are shown as the name of the operation generating the action with any arguments in parentheses and that send actions are shown as the name of the signal generating the action with any arguments in parentheses Return actions should be shown as the expression for the value they return or empty otherwise Create and des troy actions should shown as create lt target gt and destroy lt target gt Ter minate action should be shown as terminate 239 Statechart Diagram Artifact Reference 20 3 1 Action Details Tabs The details tabs that are active for actions are as follows ToDoltem Standard tab Properties See Section 20 3 2 Action Property Toolbar and Section 20 3 3 Property Fields For Action be low Documentation Standard tab Stereotype Standard tab In the UML metamodel Action has no standard stereotypes defined Tagged Values Standard tab In the UML metamodel Action has no standard tagged value defined 20 3 2 Action Property Toolbar Go up Navigate up through the hierarchical structure New Stereotyp This creates a new Stereotype see Section 16 5 Stereotype for the selected action navigating immediately to the properties tab for that stereotype Delete This deletes the Action from the model 20 3 3 Property Fields For Action Name Text b
457. tion 12 5 Selection Action Buttons They appear at the sides top and bottom and indicate a relationship type Clicking on a Selection Action Button cre ates a new related artifact with the relation of the type that was indicated If the shift key is pressed when hovering the mouse over a selected artifact sometimes different handles are shown which stand for different relation types Where button 2 click has been used to bring up a context sensitive pop up menu see below button 1 click is used to select the menu entry required The pop up menu will be removed by any button click outside of the menu area There are various more detailed effects which are discussed under the descriptions of the various tools see Section 12 3 The tool bar 12 2 2 Button 1 Double Click When used on the tool bar with a tool to add an artifact the selected artifact will be added multiple times to the drawing area once for each further button click until the tool is again selected or another tool chosen When used within the drawing area on an artifact that has sub components double click will select the 104 The Editing Pane sub component for editing creating it if necessary For example double clicking over an operation compartment of a class will select the operation Or cre ate one if there is none yet A special use is with package artifacts on the class diagram A double click on a package will navigate to the
458. tion 20 3 Action 22 4 Transition This artifact is described in the context of statechart diagrams see Section 20 8 Transition 271 Activity Diagram Artifact Reference Caution Remember that action states do not have explicit triggers The transition is implicitly triggered as soon as the entry event of the action state is complete An explicit trigger should not therefore be set The current release of ArgoUML will not check that this constraint is met Note Transitions to and from an ObjectFlowState are dashed to distinguish object flow from control flow 22 5 Guard This artifact is described in the context of statechart diagrams see Section 20 10 Guard 22 6 Initial State This artifact is described in the context of statechart diagrams see Section 20 12 Initial State 22 Final State This artifact is described in the context of statechart diagrams see Section 20 13 Final State 22 8 Junction Decision This artifact is described in the context of statechart diagrams see Section 20 14 Junction 22 9 Fork This artifact is described in the context of statechart diagrams see Section 20 16 Fork 22 10 Join This artifact is described in the context of statechart diagrams see Section 20 17 Join 22 11 ObjectFlowState To Be Written 272 Chapter 23 Deployment Diagram Artifact Reference 23 1 Introducti
459. tion of the use case on the diagram Note ArgoUML does not enforce any naming convention for use cases Stereotype Drop down selector Use case is provided by default with the UML standard stereotypes meta class powertype process thread utility for classifiers Stereotyping can be useful when creating use cases in the problem domain requirements capture and solution domain analysis but none of the predefined stereotypes are well suited to this Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Namespace Text box Records the namespace for the use case This is the package hierarchy Modifiers Check box with entries Abstract Leaf and Root e Abstract is used to declare that this actor cannot be instantiated but must always be special ized 174 Use Case Diagram Artifact Reference e Leaf indicates that this use case can have no further children while Root indicates it is a top level use case with no parent Extension Points Text box If this use case is or can be extended this field lists the extension points for the use case Note Extension points are listed by their location point rather than their name Where an extension point has been created see below button 1 Double Click will navigate to that relationship Button 2 gives a pop up menu with one entry e New Add a new extension
460. tive before i e when there is history the substate that was active when the container state was exited becomes active again When placed within a multi level hierarchy of composite states the deep history remembers the history for all states recursively which are contained in the history pseudostate container It does restore any substates no matter how deep in the hierarchy A deep history is represented on the diagram as a circle containing the symbols H 20 20 Synch State A synch state is for synchronizing concurrent regions of a state machine It is used in conjunction with forks and joins to insure that one region leaves a particular state or states before another region can enter a particular state or states The firing of outgoing transitions from a synch state can be limited by spe cifying a bound on the difference between the number of times outgoing and incoming transitions have fired In the UML metamodel Synch is a child of StateVertex 254 Statechart Diagram Artifact Reference A synch state is shown as a small circle with the upper bound inside it The bound is either a positive in teger or a star for unlimited Synch states are drawn on the boundary between two regions when possible 20 20 1 Synch State Details Tabs The details tabs that are active for Synch states are as follows ToDoltem Standard tab Properties See Section 20 20 2 Synch State Property Toolbar and Section 20 20 3 Pr
461. ton 2 command There is no way to create a new class on a component diagram 23 8 Interface A component or deployment diagram may show components or component instances which implement interfaces For details see Section 18 15 Interface Caution The V0 18 release of ArgoUML uses the same representation of an interface as a class dia gram The UML standard suggests that an interface on a component or deployment dia gram should just be shown as a small open circle connected to the component which real izes that interface Warning There is no way to show the linking of an interface to a component or component instance in the VO 18 release of ArgoUML 23 9 Association Components may be associated to each other For details about associations see Section 18 11 283 Deployment Diagram Artifact Reference Association Where classes or interfaces are shown within components on component diagrams they may be shown linked by associations 23 10 Object Just as components may show the classifiers that make up their internal structure component instances on deployment diagrams may show the classifier instances that make up their internal structure In prac tice the only instance that is of use is an object an instance of a class For details see Section 19 2 Object 23 11 Link Where objects Node Instances or Class Instances are shown within component instances on deploy ment diagrams thei
462. tten To be written System Sequence Diagram To be written To be written System Statechart Diagram To be written To be written Realization Use Case Diagram To be written To be written Documents To be written Use Case Specifications and Supplementary Requirements Specifications recast in solution language To be written 5 2 Class Diagrams To be written 5 2 1 5 2 2 5 2 2 1 To be written The Class Diagram To be written To be written Advanced Class Diagrams To be written To be written Association Classes To be written To be written 48 Analysis 5 3 Creating Class Diagrams in ArgoUML 5 3 1 Classes Identifying class diagrams from existing materials Vision Use Cases etc To be written 5 3 1 1 Using the Note Icon in the Tool Bar Click on your target class Then click on the note icon ArgoUML will generate the link automatically You can also right click to add a note as well Be aware that you can add an undefined number of notes to any one class Warning Be aware that your note will not appear in the source code documentation tab 5 3 2 Associations To be written To be written 5 3 2 1 Aggregation To be written To be written 5 3 3 Class Attributes and Operations To be written To be written 5 3 3 1 Entering Data Into Attributes and Methods Windows Click directly in the class artifact and start ty
463. type this could be used to emphasize that the Model is at the top level Generalizations Text area Lists any model that generalizes this model Note Since there is only one model in ArgoUML there is no sensible specialization or gen eralization that could be created Specializations Text box Lists any specialized model i e for which this model is a generalization Note Since there is only one model in ArgoUML there is no sensible specialization or gen eralization that could be created 155 16 3 16 3 1 Top Level Artifact Reference Owned Elements Text area A listing of the top level packages classes interfaces datatypes actors use cases asso ciations generalizations and stereotypes within the model Button 1 double click on any of the artifacts yields navigating to that artifact Datatype Datatypes can be thought of as simple classes They have no attributes and any operations on them must have no side effects A useful analogy is primitive datatypes in a language like Java The integer 3 stands on its own it has no inner structure There are operations for example addition on the in tegers but when I perform 3 4 the result is a new number 3 and 4 are unchanged by the exer cise Within UML 1 3 DataType is a sub class of the Classifier metaclass It embraces the predefined primitive types byte char double float int long and short the predefined enumeration
464. u mentation notably use cases the use of the See field to point to external documents is more practical Presentation Tab This tab provides some limited control over the graphical representation of artifacts in the diagram in the editing pane Artifacts that do not have any specific direct graphical representation on the screen beyond their textual description do not have style tabs of their own For example the style sheet of an operation on a class will be downlighted Style sheets vary a little from artifact to artifact but Figure 13 8 A typical Presentation tab on the de tails pane shows a typical style tab for an artifact in ArgoUML in this case a class Figure 13 8 A typical Presentation tab on the details pane There may be further fields in some cases e g for a package but most fields are common to many arti facts e Path This checkbox allow to display or hide the path in front of the name of the modelelement It is shown in UML notation with seperators E g the ArgoUML Main class would be shown as org argouml application Main e Attributes This checkbox allows to hide or show the attributes compartment of a class e Operation This checkbox allows to hide or show the operations compartment of a class or inter face 126 13 6 The Details Pane Stereotype This checkbox allows to reveal or hide the stereotypes of a package shown above the name Visibility This checkbox allows to
465. ude Relationship in a Use Case Diagram 41 Package 154 Qualifier 214 264 Stereotype 154 158 161 177 179 183 185 189 193 197 201 205 208 211 214 217 220 227 234 237 240 244 246 248 250 251 255 259 265 267 270 275 277 279 282 Use Case 38 173 Critic 292 Critique Menu 20 D Datatype 156 Datatype Details Tabs 156 Datatype Literals 160 Datatype Modifiers 158 Datatype Name 158 Datatype Properties 156 Datatype Property Fields 158 Datatype Property Toolbar 157 Datatype Stereotype 158 Datatype Tagged Values 156 Datatype Visibility 159 Default Value of Parameter 206 Delete From Model 81 Dependency 216 Dependency Clients 218 Dependency Details Tabs 216 Dependency Name 217 Dependency Namespace 218 Dependency Stereotype 218 Dependency Suppliers 218 Design 7 11 Object Oriented 294 Opportunistic 294 Design Process Iterative 293 Waterfall 297 Details Tabs for Actor 169 for Association 210 for Association End 213 for Attribute 196 for Class 191 for Datatype 156 for Dependency 216 for Diagrams 167 for Enumeration 161 for Extend Relationship 181 for Extension Point 176 for Generalization 178 for Include Relationship 185 for Model 153 for Operation 200 for Package 189 for Parameter 204 for Signal 207 for Stereotype 164 for Use Case 172 Developer Zone 2 Developers Cookbook The 2 Diagram 166 Activity 291 Class
466. under the menu entry Edit Settings 10 3 12 Export All Graphics This menu entry brings up a dialog box to select a directory In this directory for all diagrams in the cur rent project a graphics file is generated The names of the files are deducted from the diagram names The graphics format that is produced is set in the dialog under the Edit menu see Section 10 4 5 Settings 10 3 13 Notation This sub menu presents a radio button selection for notation i e the language in which all textual adorn ments are shown on the diagrams This feature defines the project s notation language There are 2 ways to set the notation language 77 The Menu bar e In the Edit menu see Section 10 4 5 5 Notation Tab in the notation tab of the settings dialog which defines the default notation language for new projects This choice is stored in the argouml properties file e In the File menu item Notation This determines how all textual adornments of figures on all dia grams of the current project are shown This choice is stored in the project file The following 2 notations are build in ArgoUML e UML 1 4 Uses UML notation as the default notation for every modelelement on any diagram e Java Uses Java notation as the default notation for every modelelement on any diagram The following choices are only available if the corresponding plugin languages are installed Cpp CSharp e PHP B
467. ure 13 17 An example of a stereotype tab for a class In the lists between the baseclass of the stereotypes is shown E g in the figure above the thread 131 The Details Pane Classifier stereotype may be applied to all types of classifiers such as Class UseCase 13 9 Tagged Values Tab Tagged values are another extension mechanism provided by UML The user can define name value pairs to be associated with artifacts which define properties of that artifact The names are known as tags UML pre defines a number of tags that are useful for many of its artifacts Note The tag documentation is defined for the top UML metaclass Element and is so available to all artifacts In ArgoUML documentation values are provided through the Documentation tab rather than by using the Tagged Values tab The Tagged Values tab in ArgoUML comprises a two column table with a combo box on the left to select the tagdefinition and an editable box on the right for the associated value There is always at least one empty row available for any new tag The button at the top of this tab allows creation of a new tagdefinition After clicking this button go to the properties tab first to set the name of the new tagdefinition The mouse buttons have their standard behavior within the editable value area see Section 8 2 General Mouse Behavior in ArgoUML In addition when in the value field cut copy and paste operations may be invo
468. us sb erre sone 1 1 1 3 Encontrando Mas Sobre el Proyecto ArgoUML eee ceee eee eee eee 2 1 2 Alcance de Este Manual de Usuario ocooccocnncnocnncnoconcnononcnnrocononoconororonanoconanoronos 2 12 1 Audiencia ODJELIVO ecseri senises erer e EErEE EEIE EEEE ears 2 ELLA OC A T E E a a E E EEEE ER 3 1 3 Visi n General del Manual de Usuario ocoooccnccnncnnncnnccnnconnconccnnconnconnccnncnnnconncos 3 1 3 1 Estructura del Manual Tutorial 1 00 0 0 cee cece eeceecneceeceeeeeeeeeeeaeeeeaeeeeaees 3 1 3 2 Estructura del Manual de Referencia coocooccocnncnoconcnonocononocononocononoconanonos 3 1 3 3 Retroalimentaci n por el Usuario oocooccnnccnnccnnconeconncnnncnnncnnncnnconoccnncnnns 4 1 4 Supuestos pda ral 4 O O E NOS 5 2 Introducci n escriblendose clic ld rosales donen vem 6 3 OOAK amp D basada en UML arisera iore o n EE E E ES E EE 7 3 1 Antecedentes para UME orrneor iseni er esae sas sticks a E eet 7 3 2 Procesos Basados en UML para OOA amp D ocoocccnccnnconnconnccnnconnconnconaconacnnconoss 7 ES A Proceso AA iss coneis rE PEPEE IPSS Ea IES RSE GUE YTRE NES 8 3 2 2 Un Proceso de Desarrollo para este Manual ccceeeeee eee eee 10 3 3 Por que ArgoUML es Diferente ooonccoccncccnccnnccnnconnconocnnconnconnccnnccnnccnncos 11 3 3 1 Psicolog a CODMILIVA serye ane stony sae ss cirrosis 12 3 3 2 Bstandares ADIET S cotton inet ista 13 3 3 3 100 Java PUTO iii a asin 14 3 34 Codigo ADICTO
469. using the broom objects on the face of the broom are distrib uted i e spaced evenly ArgoUML s broom supports three distribution modes objects can be spaced evenly across the space that they use objects can be packed together with only a small gap between them or objects can be distributed evenly over the entire length of the broom s face Repeatedly pressing the space bar cycles among these three distribution modes and displays a brief message indicating the operation just performed Space evenly Pack tightly Spread out and Original Selection Action Buttons When the user selects an artifact ina UML diagram several handles are drawn on it to indicate that it is selected and to provide user interface affordances to resize the node ArgoUML also displays some selection action buttons around the selected artifact See the figure below for some examples of the handles and selection action buttons The two figures for a class differ because for creating the second one the shift key has been depressed Figure 12 6 Some examples of Selection Action Buttons y y Selection action buttons offer common operations on the selected object For example a class node has a button at 12 o clock for adding a superclass one at 6 o clock for adding a subclass and buttons at 3 o clock and 9 o clock for adding associations These buttons support a click or drag interaction a single click creates a new related class at a default p
470. ut no preceding call or send action 15 8 14 No Stimuli on these links Suggestion that a sequence diagram has a link connecting objects without an associated stimulus without which the link is meaningless Warning Triggering this critic indicates a serious problem since ArgoUML provides no mechanism for creating a link without a stimulus It probably indicates that the diagram was created by loading a corrupt project with an XMI file describing a link without a stimulus possibly created by a tool other than ArgoUML 15 8 15 Set Classifier Sequence Diagram Suggestion that there is an object without an associated classifier class datatype on a sequence dia gram 15 8 16 Wrong position of these stimuli Suggestion that the initiation of send call return message exchanges in a sequence diagram does not properly initiate from left to right 15 9 Relationships Critics concerning associations in ArgoUML The current version of ArgoUML has the following critics in this category 15 9 1 Circular Association Suggestion that an association class has a role that refers back directly to itself which is not permitted Warning This critic is meaningless in the VO 14 version of ArgoUML which does not support asso ciation classes 145 The Critics 15 9 2 Make lt association gt Navigable Suggestion that the association referred to is not navigable in either direction This is permitted in the UML standard bu
471. vention event names start with a lower case letter and use bumpy caps to divide words within the name in the same way as operations Note ArgoUML does not enforce this naming convention 246 Statechart Diagram Artifact Reference Tip For call events it makes sense to use the name of the associated operation For signal events it make sense to use the name of the signal prefixed by sig For time events use the time expression prefixed by time and for change events the change expression prefixed by change Namespace Text field Shows the namespace for the event This is the composition hierarchy Parameters Text area with entries for all the actual parameter values of the event see Section 18 8 Parameter Button 1 double click on any of the parameters navigates to that parameter button 2 click brings up a pop up menu with one entry e New Parameter Create a new parameter and navigate to it Transition This shows the transition caused by the event Button 1 double click on the transition navigates to that transition Operations Drop down selector Only present for a Call Event This allows specifying the operation that causes the event when called Signal Text field Only present for a Signal Event This allows specifying the signal that causes the event when called Button 1 double click navigates to the selected signal button 2 gives a pop up menu with two entries e Add This opens a di
472. vs the lifetime of the information held be the object Now is the time to look at what information the objects hold compared to what is requested from other classes or computed on the fly Use the back of the card to record the attributes found for the classes Break you responsibilities into subresponsibilities and list the subresponsibilities indented under the main responsibilities Move the collaborators next to the subresponsibilities that use them After the Collaborator class on your card list the responsibility of the used class that is used in the col laboration After the collaborating responsibilities on your cards list the data passed back by the collab 53 Design orating object in parenthesis Redo the scenarios you did in the analysis phase but know take into consideration all of the design heur istics discussed Make up your own scenarios and try them 6 1 2 Package Diagram To be written To be written 6 1 3 Realization Class Diagrams To be written To be written 6 1 4 Sequence Diagrams and Collaboration Diagrams To be written To be written 6 1 5 Statechart Diagrams and Activity Diagrams To be written To be written 6 1 6 Deployment Diagram To be written To be written 6 1 7 Documents To be written System Architecture To be written 6 2 Package Diagrams To be written To be written 6 2 1 The Package Diagram To be written To be written 6 2
473. ways be spe cialized 158 Top Level Artifact Reference Note ArgoUML provides no mechanism for specializing datatypes so this check box is of little use e Leaf indicates that this datatype can have no further sub types while Root indicates it is a top level datatype Tip In the absence of specialization of datatypes within ArgoUML these have little value In effect all datatypes are both Root and Final Visibility Radio box with entries public private protected and package Records the visibility for the Datatype Client Dependencies Text area Lists any elements that depend on this datatype Caution It is not clear that dependencies between datatypes makes much sense Supplier Dependencies Text area Lists any elements that this datatype depends on Caution It is not clear that dependencies between datatypes makes much sense Generalizations Text area Lists any datatype that generalizes this datatype Caution It is not clear that generalizing datatypes makes much sense Specializations Text box Lists any specialized datatype i e for which this datatype is a generalization Caution It is not clear that specializing datatypes makes much sense Operations Text area Lists all the operations defined on this datatype Button double click navigates to the selected operation button 2 click brings up a pop up menu with two entries 159 Top Level Artifact Reference Mov
474. with the UML standard stereotype im plementation The stereotype is shown between and above or across the generalization Tip Stereotyping generalization does not have great value on a use case diagram The standard stereotype is about implementation and suited to the use of generalization on class diagrams Navigate Stereotype icon If a stereotype has been selected this will navigate to the stereotype property panel see Sec tion 16 5 Stereotype Discriminator Text box The name of a discriminator for the specialization UML 1 3 allows grouping of specializ ations into a number of sets on the basis of this value Namespace Tip The empty string is a valid entry and the default for this field The discriminator is only of practical use in cases of multiple inheritance A class diagram example is shown in Figure 17 2 Example use of a discriminator with generalization Here each type of user should inherit from two sorts of user One distinguishing between local or remote user which can be identified by one discriminator and one indicating their function as a user identified by a different discriminator There is little point in using this within a use case diagram Text box Records the namespace for the generalization This is the package hierarchy 180 Use Case Diagram Artifact Reference Parent Text box Shows the use case or actor that is the parent in this relationship i e
475. y all at once by typing Order customerID int items List void sequential An association e g between two classes is showing many texts close to its middle and ends so its de serves some extra explanation Figure 12 9 A couple of associations with adornments shows two as sociations to clarify the following Figure 12 9 A couple of associations with adornments The association on the right shows that invisible fields where text can be entered become visible once the modelelement is selected The fields are indicated by blue rectangles double click on them with mouse button to start editing The visibility the or is shown together with the association end name but it is not shown for an unnamed association end Likewise the multiplicity is not shown if it is 1 The example figure does not demonstrate this but stereotypes of an association are shown on the dia gram but are not editable And stereotypes of association ends are shown together with the association end name 12 10 3 Notation Parsing 120 The Editing Pane to be written 121 Chapter 13 The Details Pane 13 1 13 2 Introduction Figure 13 1 Overview of the details pane shows the ArgoUML window with the details pane high lighted Figure 13 1 Overview of the details pane For any artifact within the system this pane is where all its associated data is viewed and entered The Pane has a s
476. y Only appears when the visibility of a package is hidden Displays the visibil ity 12 9 5 Modifiers This sub menu only appears with class interface package and use case artifacts It is used to set or clear the values of the various modifiers available e Abstract Set for an abstract artifact e Leaf Set for a final artifact i e one with no subartifacts e Root Set for a root artifact i e one with no superartifacts e Active Set for a artifact with dynamic behavior Note This really ought to be set automatically for artifacts with state machines or activity dia grams 12 9 6 Multiplicity This sub menu only appears with association artifacts when clicking at one end of the association It is used to control the multiplicity at the end of the association nearest the mouse click point There are only four entries a sub set of the range of multiplicities that are available through the property sheet of a as sociation end see Section 17 6 Association End 1 e 0 1 e 1 ep 12 9 7 Aggregation This sub menu only appears with association artifacts when clicking at one end of the association It is 118 The Editing Pane used to control the aggregation at the end of the association nearest the mouse click point There are three entries e none Remove any aggregation e aggregate Make this end a shared aggregation loosely known as an aggregation composite Make this end
477. y Toolbar oooooccnoccnnconioconccnnncnnocnnccnaroninnnos 251 20 13 3 Property Fields For Final State ocoooconnccncconccnnoccnccnnccnircninnnos 252 o sins cs3 hss cave satin e Mab senusact os vod A E dab E SE O EAR 253 20 15 CHOICE 25555 sietcss igh inks ia kg be cas lp a TEE As 253 2OVNG FOLK ci sade O 253 MAT ION ra ori aa 254 ASS HIStory 355ccscs ssascshs saa nesag got eee Ta a a ass TAREE e TT 254 20 19 Deep HIStory cccsviceccssieeccsencees sip eoeecoteweeesstbuveaousanved despyecnessaveresonnee 254 20 20 SYNCH State yese sds ssotss seed sendest ted ooo REEE PESES EER ERE gas T Eeoa 254 20 20 1 Synch State Details Tabs oooocoooccnnconcconoconccnnncnnncnoronoronicnnns 255 20 20 2 Synch State Property Toolbar cece eee cence eeeeeeen seen es 255 20 20 3 Property Fields For Synch State 2 0 0 eee eee cence eeee teen es 255 21 Collaboration Diagram Artifact Reference oooooccoccnccnnccnnccnnconnccnnccnnconaconaconnns 257 211 troduction 53s ssuc eal getecet ised icr cod reia Re 257 21 1 1 Limitations Concerning Collaboration Diagrams in ArgoUML 257 21 2 Classifier Y s onii sees aes sa eectsons veh odes s saad deck Pootaacaseoveasaskoten sss TETEE 257 21 2 1 Classifier Role Details Tabs 2 0 0 0 eee eee cee cee ceeeee teen teen es 258 21 2 2 Classifier Role Property Toolbar cooocoocconoccnccnnccnnncnoconiconicnnos 259 21 2 3 Property Fields For Classifier Role cece cee

ArgoUML: Manual de Usuario - Departamento de Informática da

Contents

Download Pdf Manuals

Related Search

Related Contents

ArgoUML: Manual de Usuario - Departamento de Inform&aacute;tica da

Contents

Download Pdf Manuals

Related Search

Related Contents

ArgoUML: Manual de Usuario - Departamento de Informática da