Home

User guide and best practices for NDT-Profile 2.X Proyect NDT

1. ssssssseenennnnne 110 Figure 84 Toolbox design classes socio 114 Figure 85 Standard properties and tagged values of a data access class 115 Figure 86 Standard properties and tagged values of a class of business sssses 117 Figure 87 Standard properties and tagged values of a class presentation 119 Figure 88 Structure of the construction phase cccssesceeessssssssssssessssscsesessessessessesesseseeseeseeseesaesateess 122 Figure 89 DPS StTUCIUTE o ciaiccemeredecswinithsiacmssbacndoushesnnnrsbapunntnbricnstsetanndaadhadaunvehanaletelanonadekdamsdestinedenecebanaehsibeecns 123 mellis Mug 124 Figure 91 Toolbox Implantation tests ncn Sese ilatina ias 124 Figure 92 Standard properties of an Implantation tests occocconconoconicoconononnnononacononcnonoronoononnrnnons 125 Figure 93 Tagged values of an Implantation tests sss 126 Figure 94 Toolbox for system tests nnne nnn 127 Figure 95 Standard properties of a system test sss 128 Figure 96 Toolbox for acceptance tests sse 130 Figure 97 Standard properties of an acceptance tests sssssseeennnnes 131 Figure 98 Toolbox execution TOS 133 Figure 99 Standard properties of a battery o
2. 143 Table A II Rom 144 Page 8 of 144 As e 25 User guide and best practices for NDT Profile 2 X INGSEMERIA WEB Y TESTING TEMPRANO 1 Objectives of the paper This document comes as a result of the work of 10 years of the band s Web Artifactering Research and Early Testing at the University of Seville One of the main products obtained in these years is the development methodology NDT oriented web environments and hypermedia On the web http www iwt2 org can find a compilation of the most important works produced in these 10 years as well as support NDT tools mentioned in the following sections Page 9 of 144 2 User guide and best practices for NDT Profile 2 X IWT2 5 INGSEMERIA WEB Y TESTING TEMPRANO 2 Introduction to NDT Suite Navigational Development Techniques NDT is a methodology for developing Web and hypermedia systems NDT Suite is a set of tools to implement the methodology NDT NDT Suite supports all phases of requirements analysis design construction and implantation testing and maintenance all based on the methodology Metrics V3 A merger carried out is based on defining a process similar to V3 Metrics but using UML models and extensions of them perform NDT as well as their artifactering processes guided by models NDT Suite consists of three tools which are NDT Profile NDT Quality and NDT Driver 2 1 NDT Profile NDT Profile is a tool on a defined profile based on the NDT metamo
3. 10 EE A Po o o II 10 MEN e OI 10 HEN PIN m 10 v MEE ok Maz RERO 11 3 Description of IND I PTOIMIG asada 12 ONEE 00 007 Ooh coo tte 12 A A 14 A PP PA 16 4 UML Modeling with Enterprise Architect General rules ocoooonoooooocooccorcoranranrononooos 20 E Oo f 20 4 1 1 Ues cnc Ee 22 AL o ne ee ee 22 A ile ee EE 23 IRMEM 00 005 A 33 5 Good practices common to all elements sse 37 E SEM Tm 37 A SSP 37 TA oe ce 00000 MEER 38 5 4 Linking the documents A 39 oM o eee eee ee 41 EM MENS 44 o A 46 9 ECU Po el ot OE 47 AE hw RR e OOO 49 IA A 51 IAN 99 10 2 1 Process MO Sanrio eee eee 54 10 2 2 Identifying SETWICES veranda oie ainia 94 10 3 Storage Requirements visir italia 56 15 2 NEW Mal ae aaa 61 10 5 Requirements of StakeholderS ccccccscsessssecsecsecsrssessrsesssscsecsecaesseseeseeseessascaesatsanseneateeass 62 10 6 FUNCIONA eq UI unit 66 10 7 Interaction requirements nnns 69 Or Pi 69 10 7 2 A 15 IA A PP E A 78 10 8 Non functional requirements ooocoocnnonoonconconcononinonnonncononnooncononnnonnoononnrononnrn cnn non noo nonnonncnnss 81 MES Iu STI 85 il Sence DEI cri A 87 11 2 Content classes nennen nnne nnne nnne nnne 90 jo am NMIN A pat ere een E 94 UNE ic Ao ee ee 94 1159 2 NOG ee ee eee 97 io I asa 100 Mt MIA ria 102
4. NN tg Tagged Values Figure 54 Tagged values of a frase Page 72 of 144 2 User guide and best practices for NDT Profile 2 X IWT2 5 I GIEMISIRIA WEB Y TESTING TEMPRANO Required fields are the name author description at least one button type artifact and at least one artifact type box In addition each frase must have one or more associated actors who are the ones who can perform these searches In the FR artifact there are a number of fields that are mandatory Name Name Each frase should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format FR XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of frases Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Artifact type button uicontrol The frases should have at least one artifact type uicontrol button indicating its functionality This button has to be completed mandatory the name alias and description This information is extended with Figure 52 Artifact type text box uicontrol The frases should have at least one artifact type uicontrol text box which indicate a data This button has to be completed mandatory the name and descr
5. ccocccccccccoccccconconcononnononononconconoononnonnnononnononnconor non non nonnnnnos 88 Figure 69 Content classes Toolbox ocoooocconconoonocccococconconconoonoonoononconconcnoo nor nno non non corno nnn nnn nnn nnn nnns 91 Figure 70 Standard properties of persistent classes seen 92 Figure 71 Tagged values of a class analysis c ccccccssescsscssssscssssessesssssseseeseessesaesaesasesseseeseesaesansansatees 93 Figure 72 Study Toolbox for actors crios E EE 94 Figure 73 Standard properties of an actor to study 95 Figure 74 Tagged values of an actor to study 96 Figure 75 Toolbox for navigational model classes sse 97 Figure 76 Standard properties and values of a node labeled ooooococccccnoonooncononanonornonnonnrnnonoso 98 Figure 77 Standard properties and tagged values of a query cccocccccccccnconccnnononncnnonononononnnononncnnonnononnns 100 Figure 78 Properties labeled standards and values of an index sss 102 Figure 79 Properties standards and values of a menu labeled esses 104 gets SUICIDIO cani aaa 107 mers P unireolnoc 107 Figure 82 Toolbox design services cescssssssssssesssssssssseseessesseseeseessesseseesensaeserserseeseesaeesessaesaesansensensas 109 Figure 83 Standard properties of a design service
6. PM1 PM Comentarios Criticidad Fecha de detecci n Fecha de resoluci n Tipo Values Adaptativo Aumentativo Correctivo Figure 103 Tagged Values In PM and IS artifacts there are a number of fields that are mandatory for the description of requests and incidents are considered correct This series of fields are Name Name Each menu should be classified with a code and a descriptive name As shown in Table 44 the name of the enhancement requests must meet the following format PM XX Name where XX is a two digit number or exceptionally three figures if there is a number high demands for improvement In the case of software impact the name must meet the following format IS XX Name where XX is a two digit number or exceptionally three figures if there is a high number of incidences software Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Type tagged value This field indicates the type of incident is being treated In the case of software incidents the type must necessarily be corrective In the case of requests to improve the rate must be adjusted or increased Criticality tagged value This value indicates the degree of criticality that has the resolution of the effect that model
7. Page 109 of 144 IWT 4 e User guide and best practices for NDT Profile 2 X BEEN MGENERLA WEB Y TESTING TEMPRANO Figure 83 is observed standard properties of the Services Required fields are the name of the artifact the author description and attributes required Q Servicio Servicio SS D Responsable del Do A Aubiol Tert os pack Atb Tert A Responsable T ciko 4 A20b0b03 Tert A De emkbsr 4 Atgbtitolb Terb nats Athis Tert sTawosom p Abies Terb Eviter de Negock 4 AUbtbo Tert q Tpimcack T cilcae Abies Terb A was Ubro Terb Stereotype Servicio Author GRUPO IwT2 m Status Scope Complexity Language J AUDIDIO Terb A Entotes Excepciones 4 Atbibii Terb eLocalac no Atbibiz Terb A Gesti n de Cambios AUgbtibi Terb Gesti n de Vik AUgbibiL Terb q Pesportables A Atbrbis Tert Dueto A Atbipi6 Terp A coi ited A AtW Terb dubmado 4 20b0b18 Tert 4 oP Oat Atbipio Tert A Eeguidiad Atb Tert 4 Moiltrbacks Fact A At bitCE Terb A MoE o T cil Atb Terb A Artus A At bttcx Terb A aD Epa Mikii Atbitcl Terb Marina lirocacioi po A Atbrtcs Terb 4 Tiempo medio de res A ATDS Terb Tiempo marino de re A AUDIO Ter A cum hate A Atb Terb Ma Mh Th Mh Th Th Th TM Th hh TT hh
8. Page 43 of 144 rr 25 User guide and best practices for NDT Profile 2 X iV La EE INGEMERIA WEB Y TESTING TEMPRANO 7 Version Control The change control sheet has a description of each of the versions to be delivering the project You will not need to enter a profuse detail because it is managed through baselines as explained in paragraph 3 3 but shall explain the changes to the generic level For this section offers only an artifact the artifact Version Control Below are properties Version Control standards ES Control de Versiones Control de Versiones General Details Require Constraints Links Scenario Files Ta 1 Name Control de Versiones Stereotype Control de Versiones Abstract Author GRUPO IWT2 v DIR Scope Public Complexity Easy Escher Alias Language Jaya HAL Persistence Keywords Phase 10 Version 00 Y A ovo Notes Figure 31 Properties Version control standards The standard properties are the name which must be present version description and baseline file which will be associated as if a document is involved as explained in paragraph5 4 Page 44 of 144 4 e User guide and best practices for NDT Profile 2 X 5 DA H IMSEMERLA WEB Y TESTING TEMPRANO Table 11 Version Control Rules Version Control Diagrams There must be many version control artifacts as there are versions of the d
9. Parameter Default Arguments Figure 14 Choosing details Details tab Through the Details tab Figure 14 can access the attributes and operations of the artifacts through the buttons Attributes and Operations respectively The attributes are required in various artifacts RA NA Services CL CLn NO QU PR and AD and operations are required in the NO and NE Furthermore through the Collection Classes button specifies whether the artifact is a collection The other fields and functions in the Details tab have no specific use in NDT and therefore not relevant in this guide Page 25 of 144 nt User guide and best practices for NDT Profile 2 X pum i IMSEMERLA WEB Y TESTING TEMPRAM In Figure 15 we can see the screen through which you can add attributes to an artifact the General tab CL 00 Ejemplo Attributes atributo General Detail Constraints Tagged Values Name atributd Alias Derived Static Type le x GJ OProperty C Const Scope Private Stereotype Containment Not Specified Initial Notes descripcion maus 4 E Name Type Initial Value amp atributo entero Figure 15 Screen attributes When you define an attribute it must have a mandatory name type description and cardinality The cardinality is completed in the Detail tab as shown in Figure 16 Page 26 of 144 cs re NH amm i INGENIERA WEB Y TESTING TEMPRANS d User guide and best practices for NDT Profile
10. c cccccsccsecsscssssscsssssscsecsecsesseesessessessaecaecaesaeseeseeseessascatcaesansensenses 41 Table 30 eue SOL tele ei ratos 43 EA 45 Table 12 ODISCUVES Uli cali 46 Table 13 Viability Study Nomenclature ooooocoococccnconconconoonanoncononnconoonoonoonoonoononconcononnconoo noe nannnnonos 48 Table 14 Nomenclature Requirements cccccccecssccsscssscsesssesseccsescsescsnscsesseecsascsescstscatssesuesnectseteeates 49 Table 15 Objectives Rules OBU ccccccccsssssssssscsessssscsscsessessessessesseseseseesseseessesaesaueesseseeseeseesersaesaneateass 93 Tabl 16 Service REIR 56 Table 17 Rules of Storage Requirements R essen nennen nnn 61 Table 18 Natures New Rules INA 62 Table 19 RulesOrACIOBHAC iaa 65 Table 20 Functional Requirements Rules RF sse 69 Table 21 Frase les FRR sentencias 15 Table 22 Display Prototype Rules PV ccccccccsscsscsssssssesssssssecsscsecsssessessessessesseseesassassesseseeseesensatsateass 78 Table pM Sto Rules LI NND 81 Table 24 Rules of nonfunctional requirements RNF cccccccccscsscsccscssssscsessecessecssssssessessesessesaesatass 84 Table 25 Nomenclature Analysis ssec idee qux ia telde idee d dns dudit standen 85 Table 26 Technique AA 89 Table 27 Analysis Services Rules sse nnne nnn nnn
11. Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Page 98 of 144 gt User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO Artifact associated Alias This field specify the artifact from which the artifact generates current in this case the prototype display that comes Attributes in Details tab Attributes button The attributes are created from uicontrol artifacts not of type button How to add attributes is explained in paragraph 4 2 Figure 15 Remember that a mandatory attribute must have a name type description and a cardinality Operations in Details tab button Operations The procedures were created from the artifacts uicontrol button type How to add operations are explained in paragraph 4 2 Figure 17 Remember that a transaction has to be necessarily a name alias and description There are also other fields are optional but recommended that the form is completed for a better definition of the nodes These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected amo
12. Diagram Types gy SOMF 22 Objetivos SPEM EXT ta Strategic Modeling TH Servicios a Web Modeling TS Requisitos de Almacenamiento m SoaML a Y Actores del Sistema Diagramas Control TS Requisitos Funcionales a Diagramas EVS ES Frases m Diagramas DRS 5 Prototipos de Visualizaci n gy Diagramas DAS zm ta Diagramas DDS a Diagramas DPP ta Diagramas DMS Figure 37 Create a new Process Diagram to define the business model 10 2 2 Identifying Services Within the business model we also find a folder for the identification of services Here we describe the existing services that have been identified as capable of being incorporated into the system Figure 38 shows the defined toolbox for services More tools DRS Servicios SubSistema Servicio Gestion de Cambios Gesti n de Vida A 2 e a iz r oS I a PF E Hee df o Commo 2 pa Figure 38 Toolbox for services Page 54 of 144 ed r s User guide and best practices for NDT Profile 2 X IM INGENERLA WEB Y TESTING TEMPRANO To create a service just click on to the artifact Service toolbox and drag to the diagram where you want to model In Figure 39 to observe the standard properties of services ES Servicio Servicio General Require Constraints Links Scenario Files Tagged Values Name Servicio Stereotype Servicio vl m Author GRUPO IWT2 Status v S cope Publ
13. sS User guide and best practices for NDT Profile 2 X IWr2 INGENERLA WEB Y TESTING TEMPRANO 4 UML Modeling with Enterprise Architect General rules The following are proposed general rules of the different elements of UML that we find in NDT Profile 4 1 Diagrams No limit on the number of diagrams or new packages can be created within a package To create diagrams in any of the sections of the project works as follows select the package where you want to create the diagram Then select the icon Figure 2 of the project toolbox and select the type of diagrams corresponding to the phase where you are Can also be added by selecting the folder in which you want to add the diagram and clicking the right mouse button positioned on Add and select Add diagram The result is shown in Figure 11 There are several groups of diagrams defined one for each phase of NDT Profile Within each there are a set of diagrams as shown in Figure 11 There are other groups predefined by the tool diagrams including UML diagrams are Mame INICIO Type Select From Diagram Types gy UML Structural d Objetivos 22 UML Behavioral f Procesos m Extended T3 Servicios a Diagramas Control T8 Requisitos de Almacenamiento 2 Diagramas EVS TH Actores del Sistema gt Diagramas DRS Requisitos Funcionales gj Diagramas DAS LY T3 Requisitos Interacci n a Diagramas DDS TS Requisitos No Funcionales 2 Diagramas DPS a Diagramas DMS a Archima
14. 94 don An 54 Figure 39 Properties of a Service Standards ccccccsscsessessssscsscsecsecsccsesessessesseseessessssessesseseeseesaesaesasees 55 Figure 40 Toolbox for information requirements cccccscsscessssccssssecsscssssssessessessessesescessesseseesaesaesatsasees 57 Figure 41 Standard properties of a storage requirement oococccccnccnccnconcnnnononononnonnonncnnonnnonoranonnonnonnnnnos 58 Foute 42 Dala TYPES A ia 60 Figure 43 Tagged values of a storage requirement sese 60 Figure 44 Tagged values of a new nature ccccscsecessssssssssessessessceessessessessessesaeseseeseeseesaesaesateaseeeeesaes 62 Figures ss A AP o o e 63 Figure 46 Standard properties of an actor ooococccccnconconocnnononinononnonnoononnoononnnonononoononnonnon non nnn 64 Figure 47 Tagged values of an actor ccoo tito 64 Figure 48 Toolbox for functional require Ment ccccccccssccscsssssssscsscsscsesssssssessessessecsesessesseseeseesensatsasees 66 Page 5 of 144 gum e P User guide and best practices for NDT Profile 2 X IM 125 IHWEEMERLA WEB Y TESTING TEMPRAMO List of Figures Figure 49 Standard properties of a functional requirement sseeeenne 67 Figure 50 Tagged values of a functional requiremMenlt ooocococccccociccnocononanononncnnonoronononn cn cononnnononnonnnnnos 68 Figure 51 WOOD ON for ASES A rn afud ii E A 70 F
15. B U A i 7 cena j Cae Figure 85 Standard properties and tagged values of a data access class In the AD artifact there are a number of fields that are mandatory for the description of the kind of access to data is considered correct This series of fields are Name Name Every kind of presentation should be classified with a code and a descriptive name As shown in Table 35 the name must meet the following format AD XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of types of presentation Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Page 115 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMSEMERLA WEB Y TESTING TEMPRANO Artifact associated Alias This field shall specify the artifact from which the artifact generates current in this case the kind of content that is appropriate Attributes in Details tab Attributes button The way to add attributes is explained in paragraph 4 2 Figure 15 Remember that a mandatory attribute must have a name type description and cardinality
16. Figure 22 Display tab labeled values cc cccccsesssssscsscsecsecsecsessesesescesceeseeseeseeseeseessassassatsaesaesaseesenss 33 Figure 23 General properties of a conductor cccscsesssscsscsececsesseesessessssceecaecaesanseesenseuseascatsatsansaneaneeess 34 Figure 24 Tab to define conditions in a connector sse 35 Figure 25 Tab target source and role of a CONNECTOF ocooccccccccccccocconccnconconcnnonnonnonnnnnononnnononncononnonnnnnnos 36 Figure 26 Sample accord us usu unctio hates 37 Figure 27 Linking the documents nnne nnn nnn 39 Figure 28 Toolbox Participants vesical 41 Figure 29 Standard properties of ParticiDAnts c ccecscsscsscsccsecsrssssssssssssscsecsecsesseseessaseeseascaecatsansanseeeeess 42 Figure 30 Participants tagged values essen nnn nnt 43 Figure 31 Properties Version control Standards c ccccscssssssssssssssssssessesesseserseeseessasseeseesaesrsersrsenss 44 Figures 2 EVO Uds ee 4T PIQUE DRS UC T ea ee RE 50 Figure 34 Toolboxes customization sesssssseeseeseeeeenennnnn nnne 51 Figure 35 Fere lor TOP CONS I ERE 51 Figure 36 Properties of an objective standard c ccccccsscsesscssssscsecsecssssssssecsessessessecsesecsesseseeseesaesatsaeees 52 Figure 37 Create a new Process Diagram to define the business model
17. INGENIERA WEB Y TESTING TEMPRANO Table 24 Rules of nonfunctional requirements RNF Diagrams nonfunctional requirements Diagram type has a non functional requirements All content must be RNF in the diagram No Functional Requirements Definition The name of the artifact is RNF XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled There is no other with the same number RNF All are within the diagram RNF Language is NDT Requisitos The type of the attribute belongs to the language of the artifact Page 84 of 144 Sa E INGENERLA WEB Y TESTING TEMPRANOS gt User guide and best practices for NDT Profile 2 X H 11 System Analysis The analysis phase will contain the resulting products to analyze define and structure the requirements in the previous phase The codes for each artifact are shown in Table 25 Table 25 Nomenclature Analysis Analysis Name Services Service XX Name Classes CL XX Name Natures New Classes CLn XX Name Process Classes CP XX Name Actor Studio AE XX Name Nodes NO XX Name Queries QU XX Name Indexes IN XX Name Menus ME XX Name The document structure analysis system and its relation to the structure of packages NDT profile shown in Figure 65 Page 85 of 144 NT e amp User guide and best practices for NDT Profile 2 X END INGENIERLA WEB Y TESTING TE MuR Baum R G 749 Bl Fase DAS 7 1 DEFI
18. M12 g p Po O Sa INGENERLA WEB Y TESTING TEMPRANO More tools DRS Requisitos de Interacci n SubSistema FR LI PV Boton Etiqueta Caja de Texto Checkbox Combobox Radio Linea Horizontal Linea Vertical Interactua con Participa en Common 4 A E m i EAD DU Po r uh A DAA A Figure 51 Toolbox for frases To create a frase simply click on the toolbox to the artifact FR and drag to the diagram where you want to model To create a uicontrol on the FR element simply click on the item and drag over the FR to which he wishes to associate As storage requirements have attributes such frases have uicontrol associated Then in Figure 52 explains how an element described uicontrol Page 70 of 144 User guide and best practices for NDT Profile 2 X IW12 INGENERLA WEB Y TESTING TEMPRANO ES Caja de Texto Caja de texto General Require Constraints Links Scenario Files Tagged Values Name Caja de texto Stereotype Text m Abstract Author GRUPO IWT2 Status vi Scope Public y Complexity E asy y Alias Language none x Persistence w Keywords Phase 1 0 Version 10 utut ha hu a a a 72 F Caja de texto ELLLIL ELLE LLL LLL L ALL CLIO 77 AAA AAA AAA AAA AAA Figure 52 Uicontrol properties of an artifact These artifacts are also uicontrol properties to be completed such as the name Name field description Field Notes and th
19. ME MESS rr ted 103 11 4 Abstract interface model nnn nnns 105 Page 3 of 144 pue amp User guide and best practices for NDT Profile 2 X INGENIERA WEB Y TESTING TIEPIPISAMN I IZ S 21 0112 cto estatico talas ee ee ees 106 12 1 CSIC SS ICC artista 108 122 Architectural OEM Winona oe 113 12 9 Model design CLASS OS ica 113 12 3 1 Data A e 0 o o A 114 To Sm 116 e PESO Nr abia 118 124 Prototype DOS lease dodo ee ee 120 12 5 ENysicalGala Move lactato ogro edi 121 1 Moenen ER mm 122 Ta SOW SUOMI VO 123 14 1 Implantation Tests c cc cesecsssssssessesssecseessscsessescsesseseecsessessseseessseseessaeseeseessaeseeseaesaesaeenees 124 FZ CN SCR 127 14 3 Acceptance Tests nennen nnnm nnn nnn nnns nnne inna tn 129 144 Execution Tesis TU 133 15 Maintenance of RICETTE 136 16 Generate doculmerntetiOn sacssesssevcirk usi pna petierit bove nci 140 17 Repair and Compact tne EAP ens aa 142 o 143 19 Bibliography and references ccccccceccssssssssssssssssscsecsesessessessssessaeseseeseeseesausassesseseeseessesaesaneates 144 Page 4 of 144 gum e P User guide and best practices for NDT Profile 2 X IM 125 IHWEEMERLA WEB Y TESTING TEMPRAMO List of Figures List of Figures Figure 1 Main screen of Enterprise Architect 12 Figure 2 Choosing items in the tOOlDOX cececcss
20. Test Performed in the artifact there are a number of fields that are mandatory for the description of the battery of tests is considered correct Name campo Name Each test system must have a descriptive name Author campo Author This field contains the name of the company or person in the company responsible for defining the artifact Description campo Notes This field describes the depth of detail that the author deems appropriate the artifact being treated Start Date Tagged value Enter the date at which begins to run the battery of tests End Date tagged value Indicate the date that ends the battery of tests Total Tests Tagged value Indicate the number of tests have been completed successfully Incorrect Tests Tagged value Indicate the number of tests that have not been completed successfully Total Tests Tagged value Total number of tests that have been implemented in the battery of tests Page 134 of 144 5 User guide and best practices for NDT Profile 2 X IWT2 1 MO INSEMERIA WEB Y TESTING TEMPRANO Attributes Within the Details tab Attributes button The way to add attributes is similar to how you do on the Services From the toolbox drag a test attribute to the artifact In the name shall indicate the name of the test In addition each attribute has two more tagged values described below Date Tagged value of Attributes Result Tagged value of Attributes There are als
21. This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Page 104 of 144 User guide and best practices for NDT Profile 2 X There are also other fields is optional but recommended that the form is completed for a better definition of the menus These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Menus can be connected to any other artifact of the navigation model using the links Navigate shown in Figure 75 To use this connector simply click on it in the toolbox click on the menu origin and drag to the destination artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 34 Rules Menu ME Defining Menus The name of the artifact is ME XX X
22. 1 SOFTWARE ISSUES DIAGRAMS 1 1 SOFTWARE INCIDENTS DIAGRAMS C 1 2 DEFINITION SOFTWARE ISSUES 8 f 5 2 REQUESTS FOR IMPROVEMENT 2 1 REQUESTS FOR IMPROVEMENT DIAGRAMS TS 2 1 REQUESTS FOR IMPROVEMENT DIAGRAMS 2 2 DEFINITION REQUESTS FOR IMPROVEMENT E Project Browser de Figure 100 Structure of DMS This phase consists of defining two types of artifacts software issues and requests for improvement Table 44 Maintenance Nomenclature Name Software Issues IS XX Name Requests For Improvement PM XX Name The Software Issues are software errors detected during the execution of the system and involving the detection of an error that contradicts the set of requirements defined for the system The Requests For Improvement are proposals that the user can take to improve the system in terms of interface navigation functionality etc The set of tools for the definition of maintenance artifacts shown below in Figure 101 SubSistema PM IS Procede de Implica a NS VI Figure 101 Toolbox The standard properties are the same for both types of artifacts which are observed in the Figure 102 Page 136 of 144 WT2 4 e User guide and best practices for NDT Profile 2 X IMGENERLA WEB Y TESTING TEMPRANO Author METI IWT2 Status INIA Figure 102 Standar properties Page 137 of 144 gt User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO
23. 144 j oOo IMSENERLA WEB Y TESTING TEMPRANO Interactua con 7 Interactua con Participa en T AC 01 Usuario Participa en Participa en Interactua cons alnteractua cons Figure 55 Connections interaction artifacts Frases can be linked to any other artifact interaction LI or PV through the connector Interacts with which appears in the toolbox seen in Figure 51 This connector denotes a ship relationship between interaction artifacts as shown in Figure 55 To use this connector simply click on the toolbox to select click on the source artifact interaction and drag to the destination artifact interaction in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide In addition to this connector the frases are linking to the actors through the connector Join which appears in the toolbox as seen in Figure 51 This connector denotes a relationship between interaction artifacts and actors as shown in Figure 55 To use this connector simply first drag the actor to the diagram of prototype display click on the toolbox to select click and drag on the actor to display the prototype of the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector
24. 2 X CL 00 Ejemplo Attributes atributo General Detail Multiplicity Lower bound 14 Upper bound _ Ordered Multiplicity Collection Attribute is a Collection C Allow Duplicates Container Type Transient Figure 16 Entry screen cardinality The cardinality has to be introduced in the fields Upper bound and Lower bound For example if the cardinality 0 would have to enter a 0 in Lower bound and a in Upper bound If these fields are not filled the cardinality shown is 1 1 In Figure 17 We can see the screen through which you can add operation to an artifact the General tab Page 27 of 144 INGENERLA WEB Y I 5156 TEMPRAN NO 00 Ejemplo Operation operacion General Behavior Pre Post Tagged Values Name operacion Pamete Edi Parametess Return Type void v Static Scope ibli v abstract Const Stereotype Retun Aray Pure Concurrency Sequential _ Synchronized _ Is Query Alias Notes descripci n de ejemplo S Operations 8 B ve Name Return Type Parameters operacion void Figure 17 Screen operations Required fields in operations are the name description and alias In the alias field must be the name of the RF artifact referenced by the operation The other fields and tabs do not have a defined use in NDT though can be used to enhance the description of the operations Require tab has no functionality in NDT so it w
25. AC artifact there are a number of fields that are mandatory for the description of the actor is considered correct This series of fields are Name Name Each actor should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format AC XX Nombre where XX is a two digit number or exceptionally three figures if there are a large number of players Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the language in which it is the artifact There might NDT Requisitos There are also other fields are optional but recommended that the form is completed for a better definition of the actors These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Importance tagged value This value indicates the importance that the system is the concept that models the artifact to the customer Must be chosen one o
26. BPM Governance attribute Specification of the policies implemented by the service to be defined in the SOA governance model Security attribute Specification of the security restrictions that apply to the service to be defined in the SOA governance model Monitoring function attribute Functional monitoring indicators that apply to the service to be defined in the SOA governance model Alerts attribute Levels and types of warning based on indicators defined above Availability attribute Indicates the slot or slots and days on which the service can be used For example from 8 00 to 20 00 from Monday to Friday except public holidays or 24hx7d as Maximum number of invocations time attribute Indicates the maximum number of invocations to a customer may perform in a defined time unit for example 10 invocation per second Maximum response time attribute Maximum message processing Page 89 of 144 amp User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Clauses attribute Other clauses that may apply to the particular hiring and where appropriate non compliance Operations in Details tab button Operations The services must have at least one operation How to add operations are explained in paragraph 4 2 Figure 17 Remember that a transaction of a service has to be necessarily a name parameters return value and description There are also ot
27. DDS Senicios HOT Pruebas del Sistema DMS Mantenimeentn objetos Lu eaa x default b JB etes Lg Tagged Values Ej Pan amp Zoom d Properties tel Toolbox Vriibility Figure 2 Choosing items in the toolbox In the profile of NDT has seven sets of tools one for each of the phases of the life cycle which covers NDT Control Changes and participants to cover those sections NDT Viability study to cover the Viability study phase NDT Requirements to cover the requirements artifactering phase NDT Analysis to cover the phase of analysis NDT Design to cover the design phase NDT Tests to cover the testing phase NDT Maintenance to cover the maintenance phase At each time the development team will select the set of tools for the phase at which they are working Page 13 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 INGENERLA WEB Y TESTING TEMPRAMO Above right is the Project Browser marked with the number 3 in Figure 1 which allows you to navigate the project Here are packages diagrams elements and properties of elements From here you can drag and drop items between folders or drag to the active diagram In addition right clicking on the elements can perform different actions on them If the panel does not display the Project Browser it displays the menu by clicking on View gt Project Browser or by pressing Alt 0 Bottom right panels are different marked with the number 4 i
28. INGEMERIA WEB Y TESTING TEMPRANO The attribute name must begin in lower case using the CamelCase notation The language of the appliance must be a valid programming language The type attribute is not empty The type attribute must be a type of language fixture The description attribute is filled A CL CLn for each RA NA Each attribute of the RA NA is in the CL CLn The type attribute of the CL CLn is equal to the RA NA The cardinality of the attribute of the CL CLn is equal to the RA NA If there is an attribute of type RA in the RA NA there is an association between CL CLn equivalent The cardinality of the association is the cardinality of the attribute to create the association in the RA NA 11 3 Navigation Model The navigation model can vary substantially depending on the actor at all times to interact with the system So the actors are defined in the study from the actors defined in the requirements and conduct a navigation diagram for each of the actors under study Table 29 Navigation Class Rules Navigation Class Diagram You must have a navigational chart type Model All nodes Queries Indexes and menus should be contained in the diagram Artifacts can only be linked to others through the links Navigate 11 3 1 Actors studio The actors under study are defined as groups of actors defined requirements and artifacts are represented by AE XX in NDT Profile This will only be required when the computer de
29. QU qui atributo int tags Comentarios A Figure 77 Standard properties and tagged values of a query In the artifact QU there are a number of fields that are mandatory for the description of the query is considered correct This series of fields are Page 100 of 144 amp User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Name Name the name must meet the following format QU XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of queries Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Artifact associated Alias This field specify the artifact from which the artifact generates current in this case the prototype display that comes Attributes in Details tab Attributes button The attributes are created from uicontrol artifacts not of type button How to add attributes is explained in paragraph 4 2 Figure 15 Remember that a mandatory attribute must have a name type description and a cardinality Operations in Details tab button Operations The procedures were created f
30. Th Th Th TT TT TT Th NT hh hh TT Th Th Th TT TTT ope Tacit ho Ja Figure 83 Standard properties of a design service Page 110 of 144 User guide and best practices for NDT Profile 2 X IWT2 MO ll INSEMERIA WEB Y TESTING TEMPRANO In the artifact design services there are a number of fields that are mandatory for the service description to be correct In the case of service attributes they are added to the artifact from the Toolbox DDS Services seen in Figure 67 To do this click on the toolbox is the attribute to add and drag the desired service These mandatory fields are Name Name As shown in Table 25 the name must meet the following format Service XX Nombre where XX is a two digit number or exceptionally three figures if there is a high number of services Author Author field This field contains the name of the company or person in the company responsible for defining the service Description Field Notes This field is described with the depth of detail that the author deems appropriate the service that is being treated Responsible Domain attribute This field indicates the person with ultimate responsibility of the domain Technical Manager Domain attribute This field indicates the person responsible for the domain Space attribute general taxonomic grouping of service Originates namespaces that begin with the generic branch of taxonomy and concludes with the
31. To PROFILE 2 0 eap Figure 6 Baselines versioning Add a version and the description Note is optional and always under the NDT standard Once the baseline is established and can continue working At any time you can see the status prior to the changes You can see the changes as shown in Figure 7 Manage Baselines Current Baselines For Package NDT PROFILE 2 0 Name V 4 Notes C Show Differences NDT PROFILE 0 0 NDT Profile 2 0 NDT PROFILE 1 0 Baseline time 06 11 2009 11 39 27 Restore to Baseline New Baseline Delete Selected Load Uther Baselines w Export File Compare Model to File Connected To PROFILE 2 0 eap Figure 7 Comparing with the previous state Select the baseline and press Show Differences button From now displays a tree of the entire profile or the phase that has undergone a baseline as shown in Figure 8 Page 17 of 144 User guide and best practices for NDT Profile 2 X Madel Elements Status Property Madel Baseline E za NOT PROFILE 2 0 Hikari false false Ir MOD Ch ng author GRUPO IWT2 GRUPO IWT2 PARTICIPANTES Chang Complexity 1 L CONTROL DE VERSIONES IsLeat false false OBJETIVOS DEL PROYECTO Chang sspec ihe Ehe fp Fase EYS Chang Keywords Bo Fas DAS i Multiplicity fy 1 OBJETIVOS DEL SISTEMA Chang Name OFS ___ DES l Hotes La fase de ingenieria de requisitos tiere lt font color O000000 gt La fase de 2 y 1 1 DIAGRAMAS DE OBJETIVOS Model
32. customer The structure of the system design document and its relationship to the structure of packages NDT profile shown in Figure 80 Page 106 of 144 A12 amp User guide and best practices for NDT Profile 2 X YY Lax P INGEMERIA WEB Y TESTING TEMPRANO Project Browser x Babe 2 itt B Fase DDS 1 DESIGN SERVICES a 1 1 SERVICE DIAGRAMS E 1 1 SERVICE DIAGRAMS 1 2 SERVICES a 1 2 DESCRIPTION OF THE SYSTEM ARCHITECTURE a 2 1 TECHNOLOGICAL ENVIRONMENT a amp 2 1 TECHNOLOGICAL ENVIRONMENT a 2 2 DESCRIPTION OF EXTERNAL ACCESS TO OTHER SYSTEMS 3 DESCRIPTION OF EXTERNAL ACCESS TO OTHER SYSTEMS a 2 3 SYSTEM PERFORMANCE REPORT 3 SYSTEM PERFORMANCE REPORT ES 2 4 SYSTEM SECURITY REPORT 3 SYSTEM SECURITY REPORT a 7 2 5 REPORT OF ADAPTATION SYSTEM FOR LOPD 3 REPORT OF ADAPTATION SYSTEM FOR LOPD fa C 2 6 REPORT ON GROWTH FORECAST SYSTEM T REPORT ON GROWTH FORECAST SYSTEM a 7 3 DESIGN CLASSES MODEL a 3 1 DESIGN CLASS DIAGRAM TA 3 1 DESIGN CLASS DIAGRAM 3 2 PRESENTATION C 3 3 BUSINESS 3 4 DATA ACCESS T 4 PROTOTYPE DESIGN T PROTOTYPE DESIGN 5 5 PHYSICAL MODEL DATA a 5 1 DESIGN OF PHYSICAL MODEL DATA TA DESIGN OF PHYSICAL MODEL DATA 5 2 DATA DICTIONARY 6 DOCUMENTATION aE seas TAO EMERIT ATTN Oy Project Browser by pa Figure 80 Structure DDS Corresponding tools for the definition of design artifacts are shown in Figure 81 NDT Control de Cambios
33. deployment Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Constraints Constraints tab In a functional requirement must be defined mandatory restrictions These need to be detailed in the Constraints tab as described in paragraph 4 2 of this guide Figure 18 and the rates may have are pre condition and post conditions If the functionality does not have any restrictions both as pre condition post condition will make clear that does not apply Diagram of activities or scenarios The tests must necessarily be described by scenarios or an activity diagram Both options are available the first by Scenarios tab seen in Figure 92 and the second by double clicking on the test If you want the functionality that will be used to describe a complex activity diagrams mandatory which are described further in Section 4 1 2 Input Parameters tagged value Indicate those input parameters necessary to run the test Expected results tagged value Indicate the output result should be obtained for the test to be considered satisfactory There are also other fields are optional but recommended that the form is completed for a better definition of functional requirements These are Status Status Field This field co
34. gt WT INGENERIA WEB Y TEST G TEMP A User guide and best practices for NDT Profile 2 X Proyect NDT Suite 2 X Author IWT2 Group Version 02 03 Date 07 04 2011 A yum e es User guide and best practices for NDT Profile 2 X IM 125 INGENIERA WEB Y TESTING TEMPRANO Version Control Sheet Version Control Sheet User guide and best practices for NDT Profile 2 X 07 04 2011 CONTROL DE VERSIONES Description Reason version Filing Date 01 00 Initial document 12 09 2008 01 01 Added appliances aintenance 02 03 2009 management system 01 02 Fixed numbering of tables and figures 07 03 2009 01 03 Incorporated the changes requested by the 17 03 2008 technicians of the Technical Bureau of Quality and Project Management 01 04 Technical Reviews Technical Bureau of 31 03 2009 Quality and Project Management 02 00 Review the document for its adaptation to 26 11 2009 NDT 2 X Profile 02 01 Correcting errors after changes in NDT 2 X 13 04 2010 Profile 02 02 Correcting mistakes by Julian Garcia 05 05 2010 02 03 The information from the definition of 07 04 2011 functional requirements is completed Page 2 of 144 gem User guide and best practices for NDT Profile 2 X i Cr t IHEEMERLA WEB Y TESTING TEMPRAMO Index 1 Objectives of the paper c cc cesesccsscsecsecssssreseesesecssccsecsecsessesseseessussasaecaeseuseesanseeseessasaesansansaneateeess 9 2 HOC UICTONN to PA SUING TEmmE
35. has an identification code The codes for each artifact are shown in Table 42 Table 42 Test Nomenclature Testing Name Implantation Tests PI XX Name System Tests PS XX Name Acceptance Tests PA XX Name The set of tools for defining tests are shown below in Figure 90 Page 123 of 144 NT 25 User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO NDT Control de Cambios y Participantes NDT Estudio de Viabilidad del Sistema NDT Requisitos del Sistema NDT An lisis del Sistema NDT Dise o del Sistema p i DPS Pruebas de Implantaci n NDT Mantenimiento del Sistema d DPS Pruebas de Sistemas ArchiMate DPS Pruebas de Aceptaci n BPMN 1 0 DPS Ejecuci n de las Pruebas BPMN 1 1 Figure 90 Test Artifacts 14 1 Implantation Tests Implantation tests are directed to the Department of Systems Define the tests to be performed once implemented the system to verify implementation Figure 48 shows the toolbox to model definite evidence of implementation artifacts such as IP More tools DPP Pruebas de Implantaci n P3 SubSistema edt Pl Common Saar ae a u Ya 3 4 T IF Figure 91 Toolbox Implantation tests To create an Implantation tests simply click on the toolbox to the PI artifact and drag to the diagram where you want to model For more information about working with use case diagrams please read section 4 1 1 of this guide which ex
36. is individually identified on any criterion or point of view when interacting with the system Experience says that to identify the basic agents that interact with a web system there may be different criteria used The implementation of each one of them results in the identification of a particular group of basics actors Each basic actor corresponds to a role individualized interaction with the system software When considering this task does not have to worry about whether a single person or user can act as different actors the actors must be considered in the application environment Figure 45 shows the model defined toolbox system players such as AC artifacts Page 62 of 144 NT 25 User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO More tools DRS Actores del Sistema Figure 45 Actor s Toolbox To create an actor just click on the toolbox to the artifact AC and drag to the diagram where you want to model In Figure 46 y Figure 47 shows an actor property standards and values labeled Page 63 of 144 WT2 e e User guide and best practices for NDT Profile 2 X IMSEMNERLA WEB Y TESTING TEMPRANO 5R cmd SS y 10 Vesiore 10 SS rs Z z E 2 p PA aje Z z Z 7 pA a o N Tagged values E Figure 47 Tagged values of an actor Page 64 of 144 if i ak d A ey 1 L1 WU Y Am it I GIEMISIRIA WEB Y TESTING TEMPRANO The
37. is selected with the combobox Multiplicity The remaining fields and Tagged Values tab do not have specific functionality NDT Profile although its use is not restricted and is allowed to enrich the description of the connectors Page 36 of 144 D User guide and best practices for NDT Profile 2 X IM 2 IMSEMERLA WEB Y TESTING TEMPRANO 5 Good practices common to all elements 5 1 Subsystems In some large systems may be convenient to separate each set of artifacts in different folders or sub systems To do this there is a toolbox for each subsystem artifact that creates a new folder and within this the diagram for the type of artifact that created it So we got to classify each type of artifact in different folders These artifacts despite being in different folders can be dragged to any diagram besides being able to trace through matrix or diagram a more organized way 5 2 Traceability Matrixs A traceability matrix is an Enterprise Architect screen Figure 26 where the rows represent the elements of a model defined by the user and the columns represent other elements of another model or even the same model is also defined by the user Selecting a cell intersection of a row with a column ie intersection of two elements Enterprise Architect automatically adds a link in this case a traceability relationship between the two Source 312 DEFINICION DE Type Ra Link Type Realisation im Profle DAS OB
38. new natures determine all the storage needs are identified during the interviews Specifically a storage requirement represents an important concept for the need to store information on your system Figure 40 shows the defined toolbox for storage requirements also shared for new natures Page 56 of 144 NT 25 User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO More tools DRS Requisitos de Almacenamiento C3 SubSistema mt RA ndt NA Common a D A 53 de A EJ 3 0 8 Y T IF Figure 40 Toolbox for information requirements To create a storage requirement simply click on the toolbox in RA and drag the artifact to the diagram where you want to model Figure 40 shows a storage requirement and property standards Page 57 of 144 ee User guide and best practices for NDT Profile 2 X z NH aum o4 IWGENERLA WEB Y TESTING TEMPRANS ES Class RA1 General Details Require Constraints Links Scenario Files Name RAT Stereotype RA v C Abstract Author GRUPOIWT2 Status Proposed Scope Public v Complexity Easy Alias Language Java Persistence v Keywords Phase 10 Version 1 0 Notes 2 A as Figure 41 Standard properties of a storage requirement In the RA artifact there are a number of fields that are mandatory for the description of the requirement for storage is correct This series of fie
39. or to subversion or the corresponding file Page 122 of 144 E User guide and best practices for NDT Profile 2 X IWT2 INGENIERA WEB Y TESTING TEMPRANO 14 System Tests The test phase in contrast to other phases is performed in parallel with other life cycle phases The structure of packages NDT profile shown in Figure 89 Project Browser X Babe Ue Er G ittd la Fase DPS 3 1 DEFINITION OF SCOPE OF TESTS 3 DEFINITION OF SCOPE OF TESTS a 1 2 DEFINITION OF TEST ENVIRONMENT 3 DEFINITION OF TEST ENVIRONMENT a 2 3 TEST PLANNING F TEST PLANNING 1 4 IMPLANTATION TEST e 2 4 1 IMPLANTATION TEST DIAGRAMS C 4 2 DEFINITION OF IMPLANTATION TEST GJ 5 SYSTEMS TEST 1 5 1 SYSTEMS TEST DIAGRAMS C 5 2 DEFINITION OF SYSTEMS TEST 1 6 ACCEPTANCE TESTS 1 6 1 ACCEPTANCE TESTS DIAGRAMS C 6 2 DEFINITION OF ACCEPTANCE TESTS a 1 7 EXECUTION TESTS 29 7 EXECUTION TESTS 8 DOCUMENTATION ad As y Project Browser Og Figure 89 DPS Structure The test phase is divided basically into a series of documents and the definition of test artifacts The documents have to describe the depth and scope of testing the environmental requirements necessary for the execution of the tests and the timing of the tests These documents should be attached to the PAD file as described in Section 5 4 In the second part we must define three types of test artifacts Each artifact
40. to not have to be related The detection step is really based menu to ensure the quality of the final navigation model The inclusion of menus in the navigation model will be aimed at ensuring that all parts of the navigational model are reachable from any other point Figure 75 shows the toolbox to model rates as an artifact of type ME In Figure 79 we see the standard properties of a menu modeled as an artifact of type ME Page 103 of 144 e 25 User guide and best practices for NDT Profile 2 X E INGENERLA WEB Y TESTING TEMPRANO ES ME ME1 General Details Require Constraints Links Scenario Files Name ME1 Stereotype ME vl Abstract Author GRUPO IWT2 Status Scope Public Complexity Easy Alias Language Java Persistence v Keywords Notes tags Comentarios I AAA Figure 79 Properties standards and values of a menu labeled In the ME artifact there are a number of fields that are mandatory for the description of the menu is considered correct This series of fields are Name Name Each menu should be classified with a code and a descriptive name As shown in Table 25 the name must meet the following format ME XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of menu Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes
41. with uppercase The description is filled No other AC with the same number Page 65 of 144 amp User guide and best practices for NDT Profile 2 X IW 2 INGEMNERLA WEB Y TESTING TEMPRAMO Language is NDT Requisitos The type of the attribute belongs to the language of the artifact 10 6 Functional requirements A functional requirement defines the behavior of a specific functionality of the system The systems also have to collect what is to be able to do with the information and the functional possibilities of it The functional requirements answer the question of what can be done in the system To perform the capture and definition of functional NDT uses two techniques On the one hand proposes using use case diagrams Jacobson 1995 which graphically represent the system functionality However the exclusive use of diagrams may be too ambiguous in some cases Therefore NDT proposes these diagrams accompany textual information collected via patterns that clarify its meaning and what they represent Figure 48 se shows the toolbox model defined functional requirements More tools DRS Requisitos Funcionales P SubSistema edt RF Common a DAERA EB aun Ba Tow IF w Figure 48 Toolbox for functional requirements To create a functional requirement simply click on the RF artifact in the toolbox and drag to the diagram where you want to model For more information about working with use
42. x LI OBJ x PV OBJ x RNF BPMN x Servicios BPMN x RF BPMN x Servicios servicios DRS x servicios DAS RA x CL NA x CLn RF x CP FRx QU LI x IN PV x NO servicios DAS x servicios DDS CL x AD CLn x AD CP x NE QU x PR IN x PR NO x PR CL x Table RF x PS RF x PA User guide and best practices for NDT Profile 2 X Description Traceability between the objectives of the system and related storage requirements Traceability between system objectives and new natures Traceability between system objectives and actors Traceability between system objectives and functional requirements Traceability between system objectives and frases Traceability between system objectives and listings Traceability between the objectives of the system and display prototypes Traceability between the objectives of the system and non functional requirements Relations between business model and services identified Relations between business model and requirements functions Relations between business model and services identified Traceability between services requirements and services analytical Traceability between the requirements of storage and persistence classes Traceability between the new nature and persistence classes Traceability between the functional requirements and the kinds of processes Traceability between the frases and queries Traceability between lists and indexes Traceability between prototypes and visualizati
43. y Participantes Ld NDT Estudio de Viabilidad del Sistema NDT Requisitos del Sistema b NDT An lisis del Sistema di NDT Diseno del Sistema gt DDS Servicios NDT Pruebas Del Proyecto DDS Clases de Dise o NDT Mantenimiento del Sistema Figure 81 Design Toolboxes Page 107 of 144 5 User guide and best practices for NDT Profile 2 X IWT2 mM lt IMEEMERIA WEB Y TESTING TEMPRAMO 12 1 Design Services After defining the services that we encountered in the project will proceed at this phase the technical design of such services Figure 82 shows the toolbox identified for services such artifacts Page 108 of 144 NT 4 e User guide and best practices for NDT Profile 2 X Am i INGENERIA WEB Y TESTING TEMPRANO More tools SubSistema Servicio Responsable del Dominio Espacio Responsable T cnico del Dominio Definicion Taxonomia Semantica Entidades de Negocio Tipificacion T cnica Operaciones Mensajes Tipos Errores Excepciones Localizaci n Gesti n de Cambios Gestion de Vida Responsable Dueno Consultado Informado Politicas Seguridad Monitorizaci n Funcional Monitorizaci n T cnica Alertas Disponibilidad M xima n mero de invocaciones tiempo Tiempo medio de respuesta Tiempo m ximo de respuesta Cl usulas Common 8 A zu Me 5 BB 2 8 wh Uu999999990999999999099099090909 9090909020202025l PF ou Figure 82 Toolbox design services
44. you want to work in the tool box as shown in Figure 2 For example to select the tools of requirements in the toolbox select the More tools is positioned on NDT System Requirements and select the corresponding toolbar PRDCA PL D EVS RS Communication Iinbrractasn Timing ET Actorty Campen Depirment Profid Melancdel Analysis Budineds Medeing Custom Requirements Maintenance Weer botertace WSDL WM Seem Data Modeling Dacumentatian annie BPMN 1 0 PMA 1 1 Data Flow Diagrams K ME MindMapping HOME Version Psparol EA A EAT TETTE f get TEIE Ar ni m wdied 1407 2008 213653 1005 PROFILE 2 0 o de Ingenieria Web y Testing Temprano ersidad de Sevilla jembre 2 009 LJ t amp amp FiMICI H DE SERVICIOS 5 z MODELO DE CLASES DE AN LISIS Ir 3 MODELO DE MAVEGACI N u 4 MODELO DE INTER AL ABSTRACTA J 1 OBUETIVOS DEL SISTEMA a 3 MODELOS DE MRGOCIO E 2 CAT LOGO DE REGUISITOS oe ADT PRORLE 20 Meanie Expo I 41 DEFINICI M DEL ALCANCE DE LAG PRUEBAS A DEL SISTEMA Sj tt DEFIMICIGN DEL ENTDRHO DE LAS PRUEBAS F 3 PLAMIFICACI N DE FRUEBAS FRUEBAS DE MPLANTACI N ges MOT PROFLE 2 0 Versi n Espa F apes DMS Lj 4 INCIDENCIAS SOFTWARE 5 2 PETICIONES DE MEJORA k DES Objetivos AT N e oc LI E wa 1 5 F i E NOT PROFILE 2 0 Versi n Espa ol amice gt INICI PARTICIPANTES
45. 2 X IW 125 INGENERLA WEB Y TESTING TEMPRANO More tools IT DRS Requisitos de Interacci n SubSistema FR LI PV Boton Etiqueta Caja de Texto Checkbox Combobox Radio Linea Horizontal Linea Vertical Interactua con Participa en UNSNBDBDBgJEUUU4UT VPP amp i Common aA Fz Bess ui va IOR NA PF ou Figure 56 Toolbox to display prototypes Figure 56 displays the toolbox for modeling and visualization prototype artifacts PV To create a prototype display simply click on the toolbox in the artifact PV diagram and drag to where you want to model To create an item uicontrol on the PV simply click on the item and drag over PV to which he wishes to associate The way to describe an item uicontrol has already been detailed in the previous section in particular in Figure 52 The following standards are observed properties of a prototype visualization in Figure 57 Page 76 of 144 NT e 25 User guide and best practices for NDT Profile 2 X EF Am d INGENERLA WEB Y TESTING TEMPRANO ES PV Pv1 X LL omm General Require Constraints Links Scenario Files Tagged Values Name Stereotype PV vi m Abstract Author GRUPO IWT2 Status v Scope Public Complexity Easy v Alias Language none v Persistence vi Keywords Phase 1 0 Version 1 0 DNO EAN AAAAAAAAAAASAA SARA Figure 57 Properties of a
46. B Y TESTING TEMPRANO OBJ 0BJ 00 Ejemplo General Details Require Constraints Links Scenario Files Name OBJ 00 Ejemplo Stereotype OBJ v Abstract Author GRUPO IWT2 Status Scope Public vi Complexity E asy Alias Language Jaya Persistence v Keywords Y Phase 10 Version 1 0 Notes B U YA x X Descripci n Estabilidad 2 Seleccionar Importancia Seleccionar Urgencia Seleccionar IAS Figure 36 Properties of an objective standard In the artifact OBJ there are a number of fields that are mandatory for the description of the objectives is considered correct This series of fields are Name Name field Each objectives hould be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format OBJ XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of objectives Author Author field This field contains the name of the company or person in the company responsible for defining the target Description Field Notes This field is described with the depth of detail that the author deems appropriate the objective being treated Stability tagged value This value reflects the probability of labeling an object through changes in its definition Importance tagged value This value indicates the importance of the fact that the system meets the goal for the client Pa
47. CONTROL DE VERSIONES DECETIVOS DEL PROYECTO Fani EvS Fases DES sFases DAS Fases DOS Fases DPS fases DM a Gy PROFE 2 0 d ig AYUDA E d E E Project Brower gi Resources Th Model Views El presente sistemas de carpelas ofrece una estnictura A bate para la elaboraci n de documentaci n de los o proveclos Software La estroctura de carpetas es fija aunque si el proyecto nn DRS Servicios cubre alguna de las fases la carpeta referente a la misma eL mar MOP PROFILE 20 Vemm E puede eliminare Serabeq Modeling E DRS Requisitos de Smacmamimte pe a aproj Se recombenda acceder al manual de buenas pr cbeas de HOT Profile come referente para el uso correcto de este We DES Actores del Sistema ia DRS Requisitos de Almacenamiento Mo de este profile profile aunque ei mismo se encuenta autadecurmentado ok b DES Bequisitet Finci nales z nara facil zr al trabajo B EN Comm regia general los artefactos sg iran seleccionado de NDT Control de Cambios y Participantes gt DES Frames j 1 la ool bos romespondiente y eg iran agregando a bog HDT Estudia de viabilidad del Sistema d ORS Prototipos de Virualraci m diagramas preeslaslacidos m E p i Ur NDT Requisitos del Sistema 2 ORS amp equisrbss o Funcionales En caso de ser modelos Gime Fearn un ride de documentos se acompa ar al fichero eap que contenga HDT Andinn dal Crifiema el perfil la s guients estnarhuea dae carpetas
48. DT Profile 2 X IW 125 INGENERLA WEB Y TESTING TEMPRANO More tools DDS Clases de Dise o SubSistema Presentaci n Acceso a datos 3 ndt ndt adt Negocio ndt Jy AS Common SBaGAE8 amp B a A Ata ta v Figure 84 Toolbox design classes 12 3 1 Data Access A data access artifact is the evolution of the artifacts of the content model of analysis Since each type of content CL CLn generates a data access class with the same attributes In Figure 85 we see the standard properties of an artifact access to data modeled as an artifact of type AD Page 114 of 144 T 25 User guide and best practices for NDT Profile 2 X F ve INGEN ERLA WEE Y Ti Tae TEMPRANO 9 e A 3 3 08 389 0358 93 98 e 5 Aa Me 3 2 9 9 8 amp 8 E Acceso a datos AD1 8 amp 8 aa u uau u u au 39 XM s Ma a a 23 General Details Require Constraints Links Scenario Files Tagged Values ADT 9 75 wm wm Name Paquete Tecnologia JSF fate r a Stereotype Acceso a datos mim _ Abstract ap epe ue terres Author GRUPO IWT2 Status xi A gt 7 A Scope Public v Complexity Eas v Acceso a datos 4 3 A Alas anguage ADA Alias l guage NDT Requisitos v Z Persistence mi Keywords atributo String Phase 1 0 Version 1 0 Notes tags 2 Al Y Nombre_Clase
49. EN A Precision amp Scale I ET New Save Delete Defined Datatypes for Programming Languages Product Datatype Size Unit Default Max NDT Requisitos Date NDT Requisitos Decimal NDT Requisitos File NDT Requisitos Hour NDT Requisitos Integer NDT Requisitos Logic NDT Requisitos Text Length 255 255 Close Help Figure 42 Data Types Tagged Values Figure 43 Tagged values of a storage requirement Page 60 of 144 r 5 User guide and best practices for NDT Profile 2 X Am d INGIEMIERIA WEB Y TESTING TEMPRANO Table 17 Rules of Storage Requirements RA Storage Requirements Diagrams You must have a diagram of type storage requirements All RA and NA should be contained in the diagram Storage Requirements Definition You must have a diagram of type storage requirements All RA should be contained in the diagram The name of the artifact is RA XX X Name The artifact name must be unique using the CamelCase notation and starting in uppercase The description is filled Language is NDT Requisitos There is no other RA with the same number The attribute name is not empty The name of the attribute must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute belongs to the language of the artifact The description attribute is filled 10 4 New natures The new natures together with storage requirements dete
50. FINITION OF STORAGE REQUIREMENTS 12 ACTORS DIAGRAMS gj 13 DEFINITION OF ACTORS IM THE SYSTEM ig 14 USE CASE DIAGRAMS 15 DEFINITION OF CASES USE SYSTEM 18 INTERACTION DIAGRAM 17 INTERACTION ARTIFACTS 18 HON FUNCTIONAL REQUIREMENTS DIAGRAMS nae Ein oz e no 208 31 18 DEFINITION OF HON FUNHCTIDNAL REQUIREMENTS Z0 GLOSSARY WES ST 4 Start Page oP HELF S 4 DOCUMENTATION 1 0 4 RQAQAA RES xe Ready El a 75 9 D Ttt 0 2 gg NOT PROFILE 2 0 2 p MAIN d HELP a PARTICIPANTS j CONTROL OF VERSION OBJECTIVES OF PROJECT Fase EVS BH Fase DAS E 1 OBJECTIVES OF THE SYSTEM m E 2 BUSINESS MODELS 2 3 CATALOGUE OF REQUIREMENTS Os NIAI TA 4 DOCUMENTATION master document Fase DAS Fase DDS B Fases IMPLEMENTATION B Fase DPS E Fase DMS e a 4 a 4 4 a 4 w 4 b Dij Project Browser ET 1 SS Default Style 7 Were E NUM Figure 104 Master Document DRS 2 Then select the Master Document Documentation DRS displayed in the diagram above 3 We go to Project Documentation Ritch Text Format RTF Report Alternatively you can press F8 to open the options window Page 140 of 144 de E i Am YA IWGENERLA WEB Y TESTING TEMPRANS 5 User guide and best practices for NDT Profile 2 X IM 12 Generate RTF Documentation Templates Options Advanced Element Filter
51. IWT2 Status v Scope Public v Complexity E asy v Alias Language Java Persistence v Keywords piigi Phase 1 0 Version 1 0 IN g ALLE IN1 A Notes Am w y tags g a 4 Comentarios Figure 78 Properties labeled standards and values of an index The IN artifact there are a number of fields that are mandatory for the description of the index is considered correct This series of fields are Page 102 of 144 if i ak d A oe L S ku Y Am it INSEMERIA WEB Y TESTING TEMPRANO Name Name Each index should be classified with a code and a descriptive name As shown in Table 25 the name must meet the following format IN XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of indexes Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact There are also other fields are optional but recommended that the form is completed for a better definition of the indices These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected am
52. J x RA ll Tage LOBETNOSDEL E Type on Dieta Sauce gt Toot E Eu ODS Entidad x Clases de Dise o BE DD5 Interface x Clases de Dise o BM DDS Servidos DAS Servicios DO Bd ORS AC x PV BE DR5 067 x FR E nip E L 55 CET e Mi i M zac a rame e i er de Resources Model Wiews Figure 26 Sample traceability matrix All artifacts should have defined traceability relationships Thus at any time is possible to know what objectives to satisfy the requirements what requirements implement the classes which classes persist in the database tables etc The origin of the traceability relationship should be the element that implements and destination of the item implemented For example between a functional requirement of the requirements phase and a class analysis of traceability there is an association with class origin and destination functional requirement if the class participates in the implementation of behavior defined in the functional requirement Traceability matrixs included in NDT Profile are described in Table 7 Page 37 of 144 IWT2 IMSEMERLA WEB Y TESTING TEMPRANO Table 7 Traceability Matrix Phases DRS DRS DRS DRS DRS DRS DRS DRS DRS DRS DRS DRS DAS DRS DAS DRS DAS DRS DAS DRS DAS DRS DAS DRS DAS DAS DDS DAS DDS DAS DDS DAS DDS DAS DDS DAS DDS DAS DDS DAS DDS DRS DPS DRS DPS Matrix OBJ x RA OBJ x NA OBJ x AC OBJ x RF OBJ x FR OBJ
53. L x Acceso a Datos CLn x Acceso a Datos CP x Negocio QLI x Presentacion IN x Presentacion NO x Presentacion CL x Table RF x PS RF x P pem Y Project Browser Og Resources A Mo del Views Figure 4 List of traceability matrixs They are ordered by the phase to be completed and to access them simply double clicking it Table 3 Traceability matrixs Rules Best practices Traceability matrixs defined in the proyect can not be changed and should be completed those belonging to the phase where the project is As in the case of the folder structure traceability matrixs defined in the draft can not be changed in their structure and all must be completed In Section 5 2 expands on the information on how to use traceability matrixs included in NDT profile Page 15 of 144 IW 2 INGENIERA WEB Y TESTING TEMPRANO 3 3 Baselines At any time during the project changes are required to compare the different versions that are emerging in the NDT Profile To solve the problem using the reference or baseline state as it is called in Enterprise Architect The baselines are images of a point in the process You can create as many baselines as needed see Figure 5 lt is used in different versions of each profile and each phase of NDT That is you can create baselines generally Profile or locally EVS DRS DAS DDS DPS An example of creating a baselined for the entire project once created artifacts
54. NERLA WEB Y TESTING TEMPRANO General Require Constraints Links Scenario Files Tagged Values Name LI1 A A Stereotype LI vC C Abstract MEE UU now y Staus m MIL Scope Public m Complexity Easy y A MS Language none y Oe Ad Roi ibis a e Phase 1 0 Version 1 0 Notes B IU Aj ziz ix C N UA Figure 60 Properties of a list The properties of a listing standards are the same as those of a frase as shown above lts tagged values are the same as those of a target also shown above Tagged Values Xx n EJES Y d c LIT LI Comentarios Estabilidad Fuentes Importancia Urgencia 1 D 1 1 E a 1 a 1 L 1 1 x a 1 a Note m Tagged Val QQ pan amp Zoom An pr operties Testing Figure 61 Tagged values of a list Page 80 of 144 e s User guide and best practices for NDT Profile 2 X E A x Re AA INGEMERIA WEB Y TESTING TEMPRANO In the listings the mandatory and optional features are also the same as in the frases so you will not be described again The listings can be linked with any other artifact of interaction through the connector Interact with and with actors using the link Join which appear in the toolbox seen in Figure 59 These connectors are explained in paragraph 10 7 1 and shown in Figure 55 Table 23 Listing Rules Ll Diagrams Listings You must have a diagram of type of interaction requ
55. NITION OF SERVICES a 2 1 1 SERVICE DIAGRAMS 42 1 1 SERVICE DIAGRAMS 7 1 2 SERVICES fa 2 CONTENTS CLASS MODEL fa 2 2 1 CONTENTS CLASS DIAGRAM 42 2 1 CONTENTS CLASS DIAGRAM 2 2 DEFINITION OF CONTENTS CLASSES 5 2 3 NEW NATURES a 1 3 PROCESS CLASSES MODEL a I 3 1 PROCESS CLASS DIAGRAM TA 3 1 PROCESS CLASS DIAGRAM 7 3 2 DEFINITION PROCESS CLASSES f 2 4 NAVIGATION MODEL a C 4 1 DEFINITION OF ACTORS IN STUDIO fa E 4 1 1 ACTORS IN STUDIO DIAGRAM 5 3 1 1 ACTORS IN STUDIO DIAGRAM gt 4 1 2 DEFINITION OF ACTORS IN STUDIO a 7 4 2 NAVIGATION MODEL FOR ACTORS STUDIO m 2 4 2 1 AE 01 NAVIGATION MODEL A 4 2 2 NODOS 7 4 2 3 QUERYS Q 4 2 4 NDICES 4 2 5 MENU a 5 ABSTRACT INTERFACE MODEL 3 ABSTRACT INTERFACE MODEL C 6 DOCUMENTATION B Fase DDS P 3 Fase IMPLEMENTATION v Fase DPS E Fase DMS 3 E Project Browser Se Figure 65 DAS Structure Corresponding tools for the definition of the artifacts of analysis are shown in Figure 66 NDT Control de Cambios y Participantes NDT Estudio de Viabilidad del Sistema NDT Requisitos del Sistema NDT An lisis del Sistema DAS Servicios NDT Dise o del Sistema DAS Clases de Contenido NDT Pruebas Del Proyecto DAS Clases de Procesos NDT Mantenimiento del Sistema DAS Actores de Estudio ArchiMate DAS Modelo Navegacional BPMN 1 0 BPMN 1 1 Figure 66 Toolboxes analysis Page 86 of 144 d
56. Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other ME with the same number The language of the ME must be a valid programming language 11 4 Abstract interface model In general the recommendation for the development of the abstract interface is to use the HTML prototypes generated by NDT Prototypes However teams can develop a prototype interface based on the needs or model they prefer No activity is seen as a compulsory but is recommended for use because it is very valid as validation technique with users It will be necessary to link the folder where are these prototypes which should be the folder docs das abstract interface The form of link is as described in Section 5 4 Page 105 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 INGENERLA WEB Y TESTING TEMPRANO 12 System Design The design phase includes the specifics of how the analysis will be implemented in the machine It is oriented to the concrete platform with which they go to work and should match the structure of the future code It then describes how to model each element of the analysis using the tools provided Each artifact has an identification code The codes for each artifact are shown in Table 35 Table 35 Design Nomenclature Design Name Services Service XX Nombre Presentation PR XX Name Business NE XX Name Data Access AD XX Name Table According
57. Nomenclature Requirement Name Storage Requirement RA XX Name New nature NA XX Name Actor AC XX Name Functional Requirement RF XX Name Frase FR XX Name Display Prototype PV XX Name Listing LI XX Name Nonfunctional requirement RNF XX Name In this section as well as setting the corresponding artifacts it should create a series of documents such as System Limits Current Situation Study of Alternatives and Description of the Proposed Solution These documents should be attached to the EAP file as described in Section 5 4 The artifacts of the Viability Study are exactly the same as defined in the following paragraph requirements although at the phase of Viability study are not described as deeply If a project is not implemented Viability Study this folder has been deleted Page 48 of 144 25 User guide and best practices for NDT Profile 2 X i x E INGENERLA WEB Y TESTING TEMPRANO 10 Requirements The following describes the various NDT artifacts defined for the Requirements how to enter the information into the tool Enterprise Architect and rules to follow As mentioned earlier each artifact has an identification code The codes for each artifact are shown in Table 14 Table 14 Nomenclature Requirements Requirement Name Objective OBJ XX Name Service Service XX Name Storage Requirement RA XX Name New nature NA XX Name Actor AC XX Name Functional Requirement RF XX Name Frase FR XX Name Display Prototyp
58. O is the CL corresponding to the RA attribute of PV The cardinality of the attribute is not equal to the PV The operation in NO is of the class Control of the operation of PV If there is a single bond not multiple between two PV a link must be identical between the two corresponding NO If there is a link between PV and FR the same should be a link between NO and corresponding QU The NO language must be a valid programming language Page 99 of 144 am vy E amm 51i IMGENERLA WEB Y TESTING TEMPRANO 4 User guide and best practices for NDT Profile 2 X 11 3 3 Queries A query represents those points where the navigation system requests user information that is essential to continue browsing The queries are generated from the frases Basically every frase creates a query and artifacts uicontrol than button type prototype become uicontrol attributes and button type artifacts become the operations of the queries Figure 75 shows the toolbox to model the queries along with other navigational model classes such as an artifact of QU In Figure 77 we see the standard properties of a query modeled as an artifact of type QU E QU QU1 General Details Require Constraints Links Scenario Files Tal Name QU1 Stereotype QU mim Abstract Author GRUPO IWT2 Status Scope Public i Complexity Easy Alias Language Java Persistence v Keywords Phase 1 Version 1 0 Notes
59. Persistence rs 08J OBJ1 Model Phase 1 0 10 B9 11 DIAGRAMAS DE OBJETIVOS Model Sont rem CUNG EE TODOS ropos i 1 2 DEFINICI N DE OBJETIVOS Modell Stereotype Fase Fase FS 1 OBJETIVOS DEL SISTEMA Baselr Type Package Package Y 2 MODELOS DE NEGOCIO Version 1 0 1 0 J 22 IDENTIFICACI N DE SERVICI M y 221 DIAGRAMAS DE SERVICI Model Concurrency R3 221 DIAGRAMAS DE SER Model Cardinality f 222 SERVICIOS Model Ste ES 22 IDENTIFICACI N DE SERV Baselir o 21 MODELOS DE PROCESOS Mower 3 CAT LOGO DE REQUISITOS gp AYUDA Chang Fase DAS Chang lj Fase DDS Chang Fase DPS fal Fase DMS Chang Figure 8 Full status display of each of the artifacts And depending on the changes made some triangles are displayed on the icons of the artifacts with different colors green indicates that the object is new compared to the baseline or previous version red indicates an object has been deleted blue is a modified object and finally the yellow indicates a moved object folders You can also view the status of the properties and attributes of each appliance On the right side of the window of comparison the properties of the elements that have been modified are shaded in blue Above the window of comparison is a series of buttons with different uses The button bar is shown in Figuea 9 Figuea 9 Buttons comparison baselines For example the second button having selected an item it
60. RS Structure Page 50 of 144 7 e User guide and best practices for NDT Profile 2 X EE ve INGENERLA WEB Y TESTING TEMPRANO Corresponding tools for the definition of requirements artifacts are shown in Figure 34 NDT Control de Cambios y Participantes b NOT Estudio de Viabilidad del Sistema b NDT Requisitos del Sistema 1 DRS Objetivos NDT An lisis del Sistema DRS Servicios NDT Dise o del Sistema b DRS Requisitos de Almacenamiento NDT Pruebas Del Proyecto b DRS Actores del Sistema NDT Mantenimiento del Sistema b DRS Requisitos Funcionales ArchiMate DRS Requisitos de Interacci n BPMN 1 0 DRS Requisitos No Funcionales BPMN 1 1 m mM Figure 34 Toolboxes customization 10 1 System Objectives The objectives describe the needs to the system These objectives are identified in interviews with clients and users and defined by the artifact that provides OBJ in NDT Profile Figure 35 shows the objectives defined for the toolbox Toolbox x More tools DRS Objetivos 3 SubSistema nde OB ZA esSubObjetivo de Common BBAE B ev ww a GB A a T fa Figure 35 Toolbox for goals To create an objective just click on the toolbox in the OBJ and drag to the diagram where you want to model Figure 36 shows an objective standard properties and tagged values Page 51 of 144 25 User guide and best practices for NDT Profile 2 X E INGENERLA WE
61. S n HE ue a ases DOS Page CONSTRLUCCIN Dez BREE RD E H El presente sistemas de carpetas co una estructura base para la elaboraci n de documentaci n de los propecios sofware La estructura de carpetas es fija aunque si el proyecto no cubra alguna de las fases la c referente a la misma puede eliminarse Se recomienda acceder al marmal de buenas pr cticas de NDT Pro le como rente para el uso comec o de este profile aunque simo se encuentra autodocu ara ge ir n selecti rnes St rr agregando a los diagramas preestablecidos Figure 1 Main screen of Enterprise Architect Page 12 of 144 Ae e Sd CE oi IW 2 EE INGEMERIA WEB Y TESTING TEMPRANO User guide and best practices for NDT Profile 2 X In the center marked with number 1 in Figure 1 is the working area on which the plot develops open This is where you see all the elements that are drawn on the diagram that is currently active Just below is a set of tabs that correspond to the diagrams that are open A work area must be adding the artifacts links or other items deemed necessary from the toolbox marked with number 2 in Figure 1 Each diagram type has an associated toolbox which will activate when the diagram is displayed If the panel does not display the toolbox it is displayed by clicking on the menu View gt Toolbox or by pressing Alt 5 You can also select the set of tools with which
62. TORAGE REQUIREMENTS DIAGRAMS 3 1 2 STORAGE REQUIREMENTS 3 1 3 NEW NATURE 3 2 ACTORS REQUIREMENTS 3 2 1 ACTORS DIAGRAMS TE 3 2 1 ACTORS DIAGRAMS 3 2 2 DEFINITION OF ACTORS IN THE SYSTEM 3 3 FUNCTIONAL REQUIREMENTS 3 3 1 FUNCTIONAL REQUIREMENTS DIAGRAMS 22 3 3 1 FUNCTIONAL REQUIREMENTS DIAGRAMS 3 3 2 DEFINITION OF FUNCTIONAL REQUIREMENTS 3 4 INTERACTION REQUIREMENTS 3 3 4 1 INTERACTION DIAGRAM TE 3 4 1 INTERACTION DIAGRAM 3 4 2 DEFINITION OF FRASES 3 4 3 DEFINITION OF LISTINGS SYSTEM 3 4 4 DEFINITION OF DISPLAY PROTOTYPE 3 5 NON FUNCTIONAL REQUIREMENTS 3 5 1 DIAGRAMS NON FUNCTIONAL REQUIREMENTS 72 3 5 1 DIAGRAMS NON FUNCTIONAL REQUIREMENTS C 3 5 2 DEFINITION OF NON FUNCTIONAL REQUIREMENTS ES 4 STUDY OF ALTERNATIVES 4 STUDY OF ALTERNATIVES D 5 DESCRIPTION OF THE PROPOSED SOLUTION 3 DESCRIPTION OF THE PROPOSED SOLUTION mi EM Faces POS W Project Browser i R H H a Figure 32 EVS Structure In addition it has been defined in the profile of NDT a set of tools for the study of Viability For the definition of the artifacts should be used artifacts existing set of tools that will be charged to open the diagram you want to describe The following table lists the artifacts in the Viability study phase and the structure of the name Page 47 of 144 sS User guide and best practices for NDT Profile 2 X IW12 INGENERLA WEB Y TESTING TEMPRANO Table 13 Viability Study
63. There are also other fields are optional but recommended that the form is completed for a better definition of the nodes These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Classname tagged value This field shows the exact name of the class that is implemented Package tagged value This field shows the exact name of the package containing the class implements Technology tagged value This field is indicated by a drop down technology in the classroom The design classes can connect to any other appliance model design classes through the links AS Association shown in Figure 84 To use this connector simply click on it in the toolbox click on the home appliance and drag to the target artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 38 Data Access Rules AD Definition of Data Access Classes The name of the artifact is AD XX X Name The name of the artifact must use the CamelCase notation starting with u
64. You select the profile or the phase in the Project Browser and with the right mouse button you select Package Control gt Manager Baselines Project Browser No w E I Jr AN e i d L oe Configure Ctrl Alt P Package Control gt Manage Baselines Ctrl Alt B RET t u9 New Model root node New View el Add a New Model using Wizard d Find In Project Browser Ctrl Mayusculas F Compare with XMI file Expand Branch Collapse Branch Import Model from XMI Ctrl Alt T Import a Model Branch f Export Model to XMI Ctri Alt E Get Package d Ly Rich Text Format RTF Report F8 HTML Report Mayusculas F8 Re synch all statuses with VC providers Diagrams Only Report Ctrl Mayusculas F8 Version Control Settings Copy Reference Update Package Status AX Delete Project Root _INCIDENCIAS SOFTWARE Help PETICIONES DE MEJORA Figure 5 Accessing the management baselines If needed add a new baseline version by clicking on the button New Baseline Page 16 of 144 NT 25 User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANOS Manage Baselines Current Baselines For Package NDT PROFILE 2 0 NDT PROFILE 0 0 NDT Profile 2 0 Restore to Baseline New Baseline X Name NOT PROFILE 2 0 Other Baselines v Version 1 0 Mote Baseline time 06 11 2009 11 39 27 Import File Export File Lao Lees J Connected
65. ackage will present the implementation details of the evidence The test kits are a set of tests taken from the previous sections made by a participant in the project In Figure 98 show defined toolbox for modeling the outcome of the execution test Toolbox x More tools DPS Ejecuci n de las Pruebas adt SubSistema edt Prueba Realizada Q Prueba Realiza Common Figure 98 Toolbox execution Test To create a battery of tests simply click on the toolbox in the engine tests and drag to the diagram where you want to model Figure 95 shows a battery of tests modeled as an artifact of type Tests Performed and their property standards Page 133 of 144 d User guide and best practices for NDT Profile 2 X Z Sa E C M EU SUPPE E CH IE A Le tear 1 yo Scenario Files Tagged Values IE A Name Bater a de pruebas Y Stereotype Pruebas Realizada v m Abstract Pruebas Realizada Author GRUPO IWT2 Status Bateria de pruebas Scope Public vi Complexity E asy Alias Language NDT Requisitos Persistence vi Keywords Prueba una prueba int Phase 1 0 Version 1 0 Advanced Notes B U tags Fecha Fin Fecha Inicio Pruebas Correctas Pruebas Incorrectas Pruebas Totales MAAAAAAAAAAAAAAAAAAAASSSSSSS SSS SSS SSS SSS SSS SSS Figure 99 Standard properties of a battery of tests Tagged values of all tests are identical so are the same as shown in Figure 99
66. actices for NDT Profile 2 X IWT2 MO ll INSEMERIA WEB Y TESTING TEMPRANO Constraints Constraints tab In a functional requirement must be defined mandatory restrictions These need to be detailed in the Constraints tab as described in paragraph 4 2 of this guide Figure 18 and the rates may have are pre condition and post conditions If the functionality does not have any restrictions both as pre condition post condition will make clear that does not apply Diagram of activities or scenarios The tests must necessarily be described by scenarios or an activity diagram Both options are available the first by Scenarios tab seen in Figure 92 and the second by double clicking on the test If you want the functionality that will be used to describe a complex activity diagrams mandatory which are described further in Section 4 1 2 Input Parameters tagged value Indicate those input parameters necessary to run the test Expected results tagged value Indicate the output result should be obtained for the test to be considered satisfactory There are also other fields are optional but recommended that the form is completed for a better definition of functional requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different ver
67. ages the traceability of artifacts through the use of traceability matrixs The traceability matrix is a visualization tool that allows you to see comfortably and globaly all relationships between two groups of artifacts eg between requirements and use cases or between use cases and classes This makes it the perfect tool to add a large number of relationships quickly and therefore the perfect tool to define traceability between two sets of artifacts You can to use the Resources panel Figure 4 to access the list of traceability matrixs defined in NDT Profile If the panel is not displayed it is displayed by clicking on the menu View Resources or by pressing Alt 6 Page 14 of 144 IWT2 4 es E a INSEMERLA WEB Y TESTING TEMPRANO User guide and best practices for NDT Profile 2 X Resources B Matrix Profiles e amp 01 DRS GB 02 DRS a 03 DRS EB 04 DRS amp O5 DRS El 06 DRS EH 07 DRS al 08 DRS E 09 DRS amp 10 DRS amp 20 TRZ Sa 21 TRZ ES 22 TR2 eb 23 TRZ e 24 TRZ ab 25 TRZ eb 26 TRZ e 30 TRZ BE 31 TRZ E 32 TRZ B 33 TRZ EH 34 TRZ E 35 TRZ E 36 TRZ Sal 37 TRZ e 40 TRZ E 41 TRZ OB x RA OBJ x NA OBJ x AC OBJ x RF OBJ x FR OBJ x LI OBJ x PV OBJ x RNF BPMN x Servicios BPMN x RF Servicios DRS xServicios DAS R x CL NA x CLn RF X CP FR x QU LI x IN PV x NO Servicios DAS xServicios DDS C
68. al Requirements All RF must be contained in the diagram Functional Requirements Definition The name of the artifact is RF XX X Name The name of the RF must be in the infinitive The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other RF with the same number The RF is an activity diagram or scenarios The scenarios should have name description and type normal or exception The scenarios must be numbered sequentially The activity diagram must have a start node end node and at least one activity All objects in the activity diagram has to be named The activities must have an outgoing link and at least one inbound link The starting node has to have an outgoing link The end node must have at least one inbound link Links from a decision node must have a value in their guards If the RF has constraints must have a name description and a type pre condition or post condition In the diagram all have an associated RF AC or RF is part of another Language is NDT Requirements The type of the attribute belongs to the language of the artifact 10 7 Interaction requirements 10 7 1 Frases The way in which models how the user wants to retrieve information is through the frases A frase is an information retrieval approach in the system Figure 51 shows the toolbox model defined frases such as artifacts FR Page 69 of 144 e User quide and best practices for NDT Profile 2 X
69. any other information it deems appropriate Date tagged value This field may indicate the date on which the test was carried out modeling artifact Test result tagged value This field indicates the output result obtained in the test run Table 43 Rules of Evidence PI PS PA Test Diagram Each type of test should have a diagram of type Implementation Tests All PI PS and PA should be contained in their respective diagrams Definition Test The name of the artifact is PI XX X Name PS XX X Name or PA XX X Name The name of Pl PS or PA must be in the infinitive The name of the artifact must use the CamelCase notation starting with uppercase The description is filled There is no other test with the same numbering The test is an activity diagram or scenarios The scenarios should have a name and description The scenarios must be numbered sequentially The activity diagram must have a start node end node and at least one activity All objects in the activity diagram has to be named The activities must have an outgoing link and at least one inbound link The start node must have an outgoing link The end node must have at least one inbound link If the test constraints must have a name and description In the diagram all tests have an associated AC is either part of other testing Page 132 of 144 25 User guide and best practices for NDT Profile 2 X IWT2 IMSEMERIA WEB Y TESTING TEMPRANO 14 4 Execution Tests This p
70. are shown grouped according to the phase where they are committed Viability Study Requirements Analysis Design and Testing In addition it also validates the traceability between phases and controls the consistency between each phase It also checks that the resulting prototype is navigable 2 3 NDT Driver NDT Driver allows automatically taking as input a file developed by NDT Profile 2 X execute the transformations defined in NDT methods For this it is essential that the NDT Quality tool does not report any grave bugs Page 10 of 144 User guide and best practices for NDT Profile 2 X IW 125 INGENERLA WEB Y TESTING TEMPRANO This tool only generates the basic models of the phase in question providing a starting point to you for you complete these basic models 2 4 Using this manual This manual describes in detail the use of NDT Profile and the best practices that are mandatory The support tools may be used only if we follow the good practices identified in this manual Table 1 Manual usage rules 2am Best practices e Good practice in this manual are mandatory in all projects developed on NDT Profile There shall stand any deliverable that has changed or omitted the structure of information and best Page 11 of 144 IWT 4 e User guide and best practices for NDT Profile 2 X Jj pa IMSEMERLA WEB Y TESTING TEMPRANO 3 Description of NDT Profile 3 1 Packages and folder structure NDT Profile is
71. best practices for NDT Profile 2 X NWT 2 INGENERLA WEB Y TESTING TEMPRANO 6 Participants This section should include all instances of participants indicating their data roles and so on This will be used artifacts Participants toolbox selecting the appropriate artifact depending on the category of participant Figure 28 shows the toolbox Participants More tools NDT PARTICIPANTES Cliente Proveedor Comite Equipo de Proyecto Equipo de Desarrollo Pertence a Dy F Common m A uw B E 4 LU oU IF a TP l d Figure 28 Toolbox Participants The following table lists the artifacts in Participants and structure of the name Table 9 Nomenclature of Participants Requirement Name Client Name Provider Name Committee Name Project Team EP XX Name Development Team ED XX Name The artifact represents the Customer of the final product so will the name of the agency or company represents The artifact represents the company provider that develops the system The artifact Committee representing each of the persons belonging to the various committees that had the project eg monitoring work etc May be associated with the Client Page 41 of 144 X x ic d e User guide and best practices for NDT Profile 2 X Mm d INGENERIA WEB Y TESTING TEMPRANO The artifact Project Team represents the people involved in the project Typically there is a role defined by
72. bute is not empty The type of the attribute is an RA or an attribute of this The description attribute is filled The name of the operations must be the name of an RF The description of the operation is filled Language is NDT Requisitos The type of the attribute belongs to the language of the artifact 10 7 3 Listings A list model the result of a search expressing those fields that are necessary to show for later viewing access to the corresponding prototype Page 78 of 144 gt User guide and best practices for NDT Profile 2 X M12 g p Sa INGENERLA WEB Y TESTING TEMPRANO More tools DRS Requisitos de Interacci n SubSistema FR LI PV Boton Etiqueta Caja de Texto Checkbox Combobox Radio Linea Horizontal Linea Vertical Interactua con Participa en Common A i m 2 5i ta Po Po T a V EXT SFmMONNDODODOGODOOPS HHO Figure 59 Toolbox for listings Figure 56 displays the toolbox for the modeling of the artifacts listed as LI To create a listing simply click on the toolbox in the artifact LI and drag to the diagram where you want to model To create a uicontrol on the Ll element simply click on the item and drag over the Ll to which he wishes to associate The way to describe an item uicontrol has already been detailed in the previous section in particular in Figure 52 The following standards are observed properties of a list in Figure 57 Page 79 of 144 IWT INGE
73. butes and button type artifacts become nodes operations Then in Figure 75 we see the toolbox to model the nodes along with other navigational model classes such as an artifact of NO More tools DAS Modelo Navegacional edt NO edt QU edt IN nt ME Y Navega a Origen Destino Y Navega a Bi Direccional Common Ba BAE B B amp B 5 ut zu Un Tw IF Figure 75 Toolbox for navigational model classes In Figure 76 we see the standard properties of a node modeled as a artifact type NO Page 97 of 144 ee User guide and best practices for NDT Profile 2 X F Ma NH aum i MEERERLA WEB Y TESTING TEMPRANS ES NO NO1 General Details Require Constraints Links Scenario Files Tabela Name NO1 Stereotype NO v Abstract Author GRUPO IwT2 v Status Scope Public v Complexity E asy Alias Language Java Persistence v Keywords Phase Version 1 0 Notes Va NO NO1 atributo Text tags Comentarios SSS Figure 76 Standard properties and values of a node labeled In the artifact NO there are some fields that are mandatory for the description of the node is considered correct This series of fields are Name Name Each node should be classified with a code and a descriptive name As shown in Table 25 the name must meet the following format NO XX Nombre where XX is a two digit number or exceptionally three figures if there are a large number of nodes
74. case diagrams please read section 4 1 1 of this guide which explains how to be these diagrams Figure 49 shows a functional requirement and its standard properties Page 66 of 144 Era He A x dE E RF RF1 Name Stereotype Author Scope Alias Phase Notes General Require Constraints Links GRUPO IwT2 Public Version 1 0 Scenario Files Tagged Values a o wl Status w Complexity Easy Language none Keywords Figure 49 Standard properties of a functional requirement The tagged values of a functional requirement are shown in Figure 50 Abstract Page 67 of 144 amp User guide and best practices for NDT Profile 2 X Sa E HES ae RF1 RF Comentarios Estabilidad Frecuencia Esperada Fuentes Importancia Urgencia Figure 50 Tagged values of a functional requirement In the RF artifact there are a number of fields that are mandatory for the description of functional requirement is considered correct This series of fields are Name Name Each functional requirement should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format RF XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of functional requirements Author Author field This field contains the name of the company or person in the company responsible
75. ckname and a description There are also other fields are optional but recommended that the form is completed for a better definition of the nodes These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Classname tagged value This field shows the exact name of the class that is implemented Package tagged value This field shows the exact name of the package containing the class implements Technology tagged value This field is indicated by a drop down technology in the classroom The design classes can connect to any other appliance model design classes through the links AS Association shown in Figure 84 To use this connector simply click on it in the toolbox click on the home appliance and drag to the target artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 40 Class Rules presentation PR Class Definition display The name of the artifact is PR XX X Name The name of the artifact must use the CamelCase
76. completed for a better definition of non functional requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Importance tagged value This value indicates the importance that the system is the concept that models the artifact to the customer Must be chosen one of the presets Urgency tagged value This value indicates the urgency of the fulfillment of the concept that models the artifact Must be chosen one of the presets Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Stability tagged value This value reflects the probability of labeling the appliance undergoes changes in its definition Must be chosen one of the presets Sources tagged value This value reports the sources of the version of the appliance Tagged Values x E RNF1 RNF Comentarios Estabilidad Fuentes Importancia Urgencia usc tp Tagged Values Q pan amp Zoom S Properties Y Testing A Figure 64 Tagged values of a non functional requirement Page 83 of 144 D User guide and best practices for NDT Profile 2 X bz
77. cssecssescsscsecsecsecsessecsecessessesseseeseesaesessesseseeseesaesaesatsasees 13 Figure 3 Toolbox Project Browser nnne nnne nnn nnn 14 Figure 4 List of traceability matrixs sss codec il 15 Figure 5 Accessing the management baselines ooococcccocionconconconcononoconcnnnonnon noo noonnononn non nnnnonncnnnonos 16 Figure 6 Baselines versioning esses nnn nnn inni 17 Figure 7 Comparing with the previous State ccccccscscssssssssssssssssssssssessessessessessesessesesseseesersaesansasees 17 Figure 8 Full status display of each of the artifacts 18 Figuea 9 Buttons comparison baselines sess 18 Fig ra 10 Import and export baselines amanece 19 Figure 11 Choosing the Chart DVD ecce tincta tl tmo llo etse 20 Figure 12 Example use case diagram well built 22 Figure 13 Properties Window General tab c cccssssscsssssssssssssssesseseseessessessessessesessesseseeseeseesaesansasees 24 Figure 14 Choosing details Details tab 25 Figure 15 CP SCID UGS NN 26 Figure 16 Entry screen cardinality ccccscsssssssssrcsssssessessessesseseeseessesseeseeseeseesersersersaesseesaesaesrsersensanss 2 Figure We SCPC TOCA OINS R 28 Figure 18 Screen artifact conditions sees E TT 29 Figure 19 Visualizing the links of an artifact 30 Figure 20 Defining the phases of an artifact seen 31 Figure 21 Tab File INKO RE 32
78. dels on Enterprise Architect After a comparative study of 10 tools this was the one that offered greater support and offered better benefits The profile on Enterprise offers a range of tools and artifacts definition for working with NDT methodology allowing for easy document management This profile is distributed as an empty project in Enterprise Architect The use of NDT Profile offers the possibility to have all the NDT artifacts in a simple way since they are integrated into the tool itself but in addition also supports all UML models and integrate them easily in the methodology NDT As a new NDT Profile 2 X provides a set of templates that automatically generate a document for some of the life cycle phases Specifically the phases of requirements the phase of analysis the phase of design and the phase testing of the system For more information view 16 Generate documentation 2 2 NDT Quality NDT Quality automates some of the methodological review of a project developed with NDT Profile creating a report with a description of the inconsistencies that were found during the review further verifying that the transition from requirements analysis and design analysis done correctly NDT Quality generates a report consisting of a series of mistakes These errors are classified as Mild and Graves and review specific aspects of the NDT methods such as fault complete definitions error in definitions of constraints etc Errors also
79. diagram or all charts is to appear all use cases have been defined 4 1 2 Activity diagrams You can use activity diagrams in the definition of functional and performance requirements on the behavior of test cases To help build some activity diagrams semantically correct and then identifies a series of practices must be met when developing these types of diagrams Page 22 of 144 IW INGENERLA WEB Y TESTING TEMPRAMO Table 6 Activity Diagram Rules e Good practice for activity diagrams Each activity diagram must have a unique starting point In addition there must be one and only one diagram flow between the start and the first activity Each activity diagram must have at least one end node This node should have no outflow All activity will take one and only one outflow This flow can not have any saves All outflows from a decision should have a different guard That is a decision may not have more than one output stream with the same care All activities of an activity diagram must be defined in their own activity diagram There can be no more than an activity diagram with the same name All activities and decisions involved in the activity diagram to display in the activity diagram In addition all associations involving members of the activity diagram to display in the activity diagram There can be more of a flow between the same two elements of an activity diagram There can be no more than one activity with the sa
80. distributed as an empty project for the Enterprise Architect tool which functions as a template for creating new projects The developmental phases included in the project are the phases defined in Metric These phases will be identified by the following abbreviations EVS System viability study document DRS System requirements document DAS System analysis document DDS System design document DPS System test document DMS System maintenance document Additionally it introduces a series of folders with information about the project PARTICIPANTS outline the companies and individuals who participate in the project VERSION CONTROL describing the different baselines baselines OBJECTIVES OF THE PROJECT describing the goals to be achieved in the project Once the template is opened the computer is the main screen shown in Figure 1 NOTE The distribution shown in Figure 1 could be modified if the user of the tool Enterprise Architect would have altered according to your preferences TERT opta de PRONN 1208 0300 Documentaci n MOT ant 2 0 ER Academii Elle Edit yew projet Diagram Element Jools Addins Settings Window Help 21 x rw MA Dam A omma 6 Aaa BA BE smi dignius 4 AEE Ea x EN P oP Package Disgam Apuda created 9 0208 18 26 51 moded 09 01 2010 182503 56 O27 x 1168 x Mni PEN Jana ma t4 E ga NOT PROFILE 2 0 E mao Ayuda E PARTICIPANTES m Ej CONTROL DE VERSIONE
81. e Local File Last Write Notes Files Filename Figure 21 Tab File links These files are external and unlike documents that are appended to a document no space in the project EAP That yes if you choose to link a local file if the project is desired EAP send a person who has to open from another network you must send the EAP along with the documents which have been linked It is also recommended that along with the EAP is to create a series of folders to hold documents that are required in the different phases that defines NDT introduced in the File Path on the file path not just the full path initially shown as Enterprise Architect The folder structure we propose is the following along with the EAP it creates a docs folder and within the folders control evs drs das dds dps and dms Each folder corresponds to each of the phases defined in NDT Profile The next tab is the Tagged Values tab This tab is shown as observed in Figure 22 Page 32 of 144 rr 25 User guide and best practices for NDT Profile 2 X Ay E TE M IEEE INGEMERIA WEB Y TESTING TEMPRANO E RF RF 502 RF 502 RF Comentarios Estabilidad Frecuencia Esperada Fuentes Importancia Urgencia Figure 22 Display tab labeled values The functionality of this tab is to show tagged values to be defined for each artifact Displays the same information as the Tagged Values tab as described in paragraph jError No se enc
82. e 2 X provides a set of templates designed in Enterprise Architect The life cycle stages for which we have this functionality are the requirements phase analysis phase design phase and testing of the system phase For each of these phases in NDT Profile exists a package called DOCUMENTATION which is designed the master document Thanks to this set of templates Enterprise Architect lets you completely automatically generate a structured document with all information collected at each stage of the life cycle mentioned above Below is shown the procedure to obtain the document associated with the requirements phase For the remaining phases the procedure is entirely analogous 1 Once you open the project created on the basis of NDT Profile 2 X tool open the logic diagram located in the package DRS 4 DOCUMENTATION e PROFILE 2 0 ingl s Con Ayuda Actualizada 17 05 2010 EA UTA File Edit View Project Diagram Element Tools Add Ins Settings Window Help agr dd A Getting Started m O B o a ee T c E Qd default T Logical Diagram 4 DOCUMENTATION created 01 09 2010 16 34 17 modified 01 09 2010 17 1x EEE master documents DRS ij 1 CONTROL OF VERSION 2 OBJECTIVES OF PROJECT 3 PARTICIPANTS 4 OBJECTIVES DIAGRAMS Bj 5 DEFINITION OF OBJECTIVES 6 PROCESS MODELS T SERVICE DIAGRAMS 8 SERVICES 8 CATALOGUE OF REQUIREMENTS 10 STORAGE REQUIREMENTS DIAGRAMS 11 DE
83. e PV XX Name Listing LI XX Name Nonfunctional requirement RNF XX Name Page 49 of 144 INGENERLA WEB Y TESTING TEMPRAMO The structure of the system requirements document DRS shown in Figure 33 Project Browser Babe wm a G tt O hf PROJECT OBJECTIVES m Fase EvS a B Fase DRS 2 1 OBJECTIVES OF THE SYSTEM 5 2 BUSINESS MODELS 2 J 3 CATALOGUE OF REQUIREMENTS a 7 3 1 STORAGE INFORMATION REQUIREMENTS a J 3 1 1 STORAGE REQUIREMENTS DIAGRAMS Q3 3 1 1 STORAGE REQUIREMENTS DIAGRAMS C 3 1 2 DEFINITION OF STORAGE REQUIREMENTS CJ 3 1 3 DEFINITION OF NEW NATURES 2 J 3 2 DEFINITION OF ACTORS a 2 3 2 1 ACTORS DIAGRAMS 2 3 2 1 ACTORS DIAGRAMS 7 3 2 2 DEFINITION OF ACTORS IN THE SYSTEM a CJ 3 3 FUNCTIONAL REQUIREMENTS a 7 3 3 1 USE CASE DIAGRAMS 9 3 3 1 USE CASE DIAGRAMS C 3 3 2 DEFINITION OF CASES USE SYSTEM a 7 3 4 INTERACTION REQUIREMENTS a O 3 4 1 INTERACTION DIAGRAM FE 3 4 1 INTERACTION DIAGRAM 7 3 4 2 DEFINITION OF FRASES SYSTEM C 3 4 3 DEFINITION OF LISTINGS SYSTEM C 3 4 4 DEFINITION OF DISPLAY PROTOTYPE SYSTEM a 2 3 5 NON FUNCTIONAL REQUIREMENTS a 7 3 5 1 NON FUNCTIONAL REQUIREMENTS DIAGRAMS 3 5 1 NON FUNCTIONAL REQUIREMENTS DIAGRAMS C 3 5 2 DEFINITION OF NON FUNCTIONAL REQUIREMENTS C 4 DOCUMENTATION B Fase DAS B Fase DDS O Fase CONSTRUCCI N fX re nne e Gi Project Browser er esources 1 4 Figure 33 D
84. e and best practices for NDT Profile 2 X a E INGENERLA WEB Y TESTING TEMPRANO EPA PAT General Require Constraints Links Scenario Files Tagged Values Name P 1 Stereotype PA vlc Abstract Author GRUPO IWT2 Status Scope Public v Complexity Easy Alias Language none ie fed LO 7 Keywords Z 2 7 7 Notes sk PT PP PI Pg P fo Figure 97 Standard properties of an acceptance tests The tagged values of all tests are identical so are the same as shown in Figure 93 The PA artifact there are a number of fields that are mandatory for the description of the acceptance test is considered correct This series of fields are Name Name Each acceptance test to be classified with a code and a descriptive name As shown in Table 42 the name must meet the following form PA XX Name where XX is a two digit number or exceptionally three figures if there is a large number of acceptance tests Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Page 131 of 144 User guide and best practices for NDT Profile 2 X Constraints Constraints tab In a functional requirement must be defined mandatory restrictions These need to be deta
85. e connector artifact These fields are not editable because it is an intrinsic property of the connector In the Name field can give a name to the connector which will appear next to the line drawn in the diagram In the Direction field we can select the direction in which the connector Source gt Destination Destination gt Source Bi Directional and Unespecified there is an arrow indicating the direction in those certain types of connectors In the field Stereotype can give the link In the case of links defined specifically for NDT profile this field displays the stereotype that extends the link no amendment Page 34 of 144 rr 25 User guide and best practices for NDT Profile 2 X IvV Lo EE INGEMERIA WEB Y TESTING TEMPRANO is advisable In addition the Notes field you can add a description to the link but is not binding in NDT Profile In the next tab Constraints as shown in Figure 24 we can define conditions for the link RF RF 502 Ejempla AC 00 Actor Ejemplo E UseCase Properties General Constraints Source Role Target Role Tagged Values Constraint Type Pre condition vi Defined Constraints Constraint Constraint T ype Figure 24 Tab to define conditions in a connector This tab is exactly equal to the Constraints tab of the artifacts as described in the preceding paragraph The two tabs below Source and Target Role Role refer to the role of origin and destination of t
86. e created Author field must contain the name of the company or person who has shaped the item In the Notes field should develop a description of the item In the field Language should indicate the language of the artifact being in EVS and DRS language NDT Requisitos DAS and DDS the chosen programming language currently NDT Driver works only with C and Java and the model data the database you are using Oracle MySQL and SQLServer These properties are unless otherwise noted a subset of the required fields to fill in the modeling elements Page 24 of 144 sS User guide and best practices for NDT Profile 2 X IW12 INGENERLA WEB Y TESTING TEMPRANO The Alias field is used to reference other artifact from which the element has been built that want to model generally used in automatic transformations performed by NDT Driver This field is required for some types of artifacts NO QU IN ME PR NE and AD The Status field can be used to indicate the status of the item The Version field can be used to indicate the version of the item These fields are optional unless otherwise noted the NDT modeling elements The other fields have no use in NDT although its use is not restricted ES Class RA1 General Details Require Constraints Links Scenario Files Ta 1 Concurrenc Y Cardinality vi oncurrenc Visibility y 2 wr uarde O Active Attributes O Synchronous v Templates Type
87. e element to which reference Alias field In the event that the uicontrol is a button it will in the Alias field the name of functional requirements to take the functionality In the event that is of type text box and refer to some attribute of a storage requirement or full RA also should be reflected in the Alias field In addition if an artifact uicontrol was only visible to one or more of the actors that is associated with the frase we will use the pre condition constraint Constraints tab for that Returning to the frases the standard properties of this artifact are shown in Figure 53 Page 71 of 144 NT e amp User guide and best practices for NDT Profile 2 X INGENIERLA WEB Y TESTING TE Bun E FR FRI X General Require Constraints Links Scenario Files Name FA1 Stereotype FR v Lad Abstract Author GRUPO IWT2 y Status v Scope Public v Complexity E asy v Alias Language none v Persistence v Keywords Phase 1 0 Version 1 0 Notes AAA Figure 53 Standard properties of a frase The tagged values are shown in Figure 54 Tagged Values API AAA IA AAA AAA AAA AAA AA AA AAA AAA AAA AAA AAA AAA AAA AAA AAA DAA AAA AIDA IDA M FRI FR Comentarios Estabilidad Fuentes Importancia Urgencia aF Rs FRI SAAS AAS AAAS RARA AAA AA NNNNN ANN NS NN AAA AAA SSS NN
88. e name must meet the following format Service XX Nombre where XX is a two digit number or exceptionally three figures if there is a high number of services Author Author field This field contains the name of the company or person in the company responsible for defining the service Description Field Notes This field is described with the depth of detail that the author deems appropriate the service that is being treated Language field Language This field specifies the programming language in which it is the artifact Space attribute general taxonomic grouping of service Originates namespaces that begin with the generic branch of taxonomy and concludes with the most specific Is best Page 88 of 144 2 User guide and best practices for NDT Profile 2 X IWT2 5 INGSEMERIA WEB Y TESTING TEMPRANO represented by the names of each of the nodes between them eg junta andalucia ccul empleados Information provided by membership in a repository Definition attribute Full description of the service Must be indexable by search artifacts Taxonomy attribute node of the taxonomy of services to which it belongs Information provided by membership in a repository Semantics attribute List of keywords to the evaluations made by search artifacts Adjectives and nouns are often intimately related to the functionality of the service Business Entities attribute List of business entities related to th
89. e service Be taken in this field the main institutions associated with the business in case of using auxiliary entities that fall outside the scope of the functionality will not be included Typing technique attribute Any service must be established technically Here is the tree of typing services Table 26 Technique Typing Service Ra z Tip Subtipo Descripci n TYPOLOGY PROCESS COORDINATION processes Is responsible for performing logic functions of processes decision making timing etc FUNCTIONAL BUSINESS Encapsulates business logic atomized PROXY Provides a remote business functionality implemented by distributed applications applications TECHNOLOGICAL Provides horizontal sharing security session etc Dispatcher facades Provides functionality outside the business calculations helpers Change management attribute data are versions branches of development obsolete features compatibility date related responsible for the changes reasons for them history of previous versions etc Management of life attribute Data related to the state it was found service in certain contexts development testing integration production For example maintains that the active versions of a service in development are x and x 1 while production is x 3 It also maintains data dependencies should be minimal in the case of services which may be by the membership of service to a
90. ear in different folders for each phase Thus in the docs folder will turn the following folders control evs drs das dds dps and dms E Artifact ALCANCE DEL SISTEMA General Require Constraints Links Scenario Fies Tagged Values File Path docs evs Alcance del Sistema dod Type Local File vi Last Write 15 09 2009 10 52 30 Size 1857 k Notes Files Filename Type Figure 27 Linking the documents To Link a document you have to double click on the Document appliance go to the Files tab and the File Path field select the file you want to attach Then you have to leave only the relative path eg docs drs Documento doc since this way you can open the document from Enterprise Architect This can be seen In Figure 27 If the document is not very extensive you can enter in the corresponding fixture Notes field since from version 7 5 of Enterprise Architect has a WYSIWYG editor that lets you several options for formatting text Page 39 of 144 25 User guide and best practices for NDT Profile 2 X WI EE INGEMERIA WEB Y TESTING TEMPRANO Table 8 Rules Documents Documents Document type artifact must have a document link or if it is not too large the content is entered in the Notes field File Path field must contain a relative path so you can open the document directly from the Enterprise Architect Page 40 of 144 25 User guide and
91. eating a line that models the connector if you want to edit its properties would have to double click on the connector through the display properties described in paragraph 4 3 of this guide In addition software issues or Requests For Improvement can be linked between them by links Comes from shown in Figure 101 to indicate that an software issues is created to complement other software issues To use this connector simply click on it in the toolbox click on the incidence of origin and drag to the incidence of destination in the diagram After creating a line that models the connector if you want to edit its properties would have to double click on the connector through the display properties described in paragraph 4 3 of this guide Table 45 Rules Maintenance IS PM Maintenance Chart You must have a maintenance type diagram All IS and PM must be contained in their respective diagrams May link only comes from or involves Maintenance Definition The name of the artifact is IS XX X Name or PM XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other IS or PM with the same number Page 139 of 144 e amp User guide and best practices for NDT Profile 2 X A12 g p Poo ve INGENERLA WEB Y TESTING TEMPRANO 16 Generate documentation To facilitate the generation of a document for each of the main stages of the life cycle of a software project NDT Profil
92. elds that are mandatory for the description of the kind of presentation is considered correct This series of fields are Name Name Every presentation class should be classified with a code and a descriptive name As shown in Table 35 the name must meet the following format PR XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of types of presentation Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Artifact associated Alias This field shall specify the artifact from which the artifact generates current in this case the prototype display that comes Page 119 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMSEMERLA WEB Y TESTING TEMPRANO Attributes in Details tab Attributes button The way to add attributes is explained in paragraph 4 2 Figure 15 Remember that a mandatory attribute must have a name type description and a cardinality Operations in Details tab button Operations The way to add operations are explained in paragraph 4 2 Figure 17 Remember that a transaction has to be necessarily a name ni
93. ember that a transaction of a service has to be necessarily a name parameters return value and description There are also other fields are optional but recommended that the form is completed for a better definition of services These are Status Status Field This field contains the situation where the service is in its development process The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the service This field is meaningless when it comes to large systems where version management is a critical task And the service has to be associated with two diagrams One of them is associated by default which is the WSDL diagram Toolbox is complete with predefined WSDL brings Enterprise Architect 7 5 Another Page 112 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 INGENIERA WEB Y TESTING TEMPRANO diagram is required SOAML Component diagram which should be created This diagram is predefined in Enterprise Architect 7 5 Additionally it is advisable to make a sequence diagram of the service For this we will use the diagram that comes default Sequence SOAML Enterprise Architect 7 5 Table 37 Design Services Rules Definition of Design Services You must have a type diagram Services The name and description must be filled Each service that is not the repository of services has to be at least the attributes that appea
94. f tests 134 Page 6 of 144 User guide and best practices for NDT Profile 2 X IMGEMERLA WEB Y TESTING TEMPRANO List of Figures Figure 100 Structure of DMS crono droit 136 FOr TO TOODO nen A E A E E RE 136 Figure 102 Standar properties venis aan 197 Figure 109 Tagged V AICS 138 Figure 104 Master Document DRS ccccsescccssssscsscssesesecsecsessessecsessesessessesseseesaesessassassesseseesansateateass 140 Figure 105 Window options in BA ainda 141 Figure 106 Compact EAP MES RNC EN E 142 Page 7 of 144 gum e P User guide and best practices for NDT Profile 2 X IM 125 IHWEEMERLA WEB Y TESTING TEMPRAMO List of Tables List of Tables Table 1 Manual usage TU GS ucscaseciriasksickaidktinckmcx tdi nerui etit cer d ws b HH ba A RA rh ert nr e reme t 11 Table 2 Rules and structures packages Packages c cccscscscscsscsssssssssssceseecseseessessesseesassaesrseseeees 14 Table 3 Traceability matrixs RU ES o ooooocococnnoonocanoncocnnonconononconononconorononnconnoononnnoncononenonncnononncinninns 15 Table 4 Rules of the DaSellfi8S ie ettet cirio ida peres ttt d 19 Table 5 Types of diagrams for sections of the draft ocoocononnonocnnononacononanonnranornrononononoronoononncnnons 21 Table 6 Activity Diagram Rules scopus onines a Rau or Rt ur BR aia 23 tablet Traceabihty MATIX NR m 38 Table 8 Rules DOCUS eros 40 Table 9 Nomenclature of Participants
95. f the functional requirement By default the functional requirement is of low complexity but it is recommended that there is at least one of high complexity Page 68 of 144 f 25 User guide and best practices for NDT Profile 2 X Eee t ASIE li INGSEMERLA WEB Y TESTING TEMPRANO Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Importance tagged value This value indicates the importance that the system is the concept that models the artifact to the customer Must be chosen one of the presets Urgency tagged value This value indicates the urgency of the fulfillment of the concept that models the artifact Must be chosen one of the presets Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Stability tagged value This value reflects the probability of labeling the appliance undergoes changes in its definition Must be chosen one of the presets Sources tagged value This value reports the sources of the version of the appliance Frequency expected tagged value this includes the frequency with which it is expected to be implemented the functionality that represents the artifact Table 20 Functional Requirements Rules RF Functional Requirements Diagrams Must have a diagram of type Function
96. f the presets Urgency tagged value This value indicates the urgency Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Stability tagged value This value reflects the probability of labeling the appliance undergoes changes in its definition Must be chosen one of the presets Sources tagged value This value reports the sources of the version of the appliance The generalization between actors is permitted and is manifested by the connector Inherited from existing in the toolbox of Actors To use this connector simply click on it in the toolbox click on the original actor and drag to the target actor in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Every actor should have at least one relationship with a use case or to extend to actors having at least one use case because if an actor does not define an entity outside the system who have no connection with the same what is irrelevant Table 19 Rules of Actors AC Actors Diagrams You must have a type diagram Actors All AC must be contained in the diagram You may only link by link inherits from Definition of Actors The name of the artifact is AC XX X Name The name of the artifact must use the CamelCase notation starting
97. for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Constraints Constraints tab In a functional requirement must be defined mandatory restrictions This need to be detailed in the Constraints tab as described in paragraph 4 2 of this guide Figure 18 and the type may have are pre condition and post conditions If the functionality does not have any restrictions both as pre condition post condition will make clear that does not apply Diagram of activities or scenarios The functional requirements must necessarily be described by scenarios or an activity diagram Both options are available the first by Scenarios tab seen in Figure 20 and the second by double clicking on the RF If you want the functionality that will be used to describe a complex activity diagrams mandatory which are described further in Section 4 1 2 Language field Language This field specifies the language in which it is the artifact There might NDT Requisitos There are also other fields are optional but recommended that the form is completed for a better definition of functional requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Complexity Complexity field This field contains the complexity o
98. ge 52 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Urgency tagged value This value indicates the urgency There are also other fields are optional but recommended that the form is completed for a better definition of objectives These are Status Status Field This field contains the situation where the objective is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the objective This field is meaningless when it comes to large systems where version management is a critical task Attributes in Details tab Attributes button Optionally you can add attributes to the objective if deemed necessary How to add attributes is explained in paragraph 4 2 Figure 15 Comments tagged value This field allows the author to the objective indicate any other information it deems appropriate Objectives can be linked together through the connector is SubObjective of which appears in the toolbox as seen in Figure 35 This connector denotes an aggregation relationship between objectives To use this connector simply click on the toolbox to select click on the source object and drag to the target destination in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector go
99. going to the properties screen that is described in paragraph 4 3 of this guide Page 74 of 144 IW INGENERLA WEB Y TESTING TEMPRAMO Table 21 Frase Rules FR Frase Diagrams You must have a diagram of type of interaction requirements All FR must be contained in the diagram The FR can only link to other artifacts for interaction through the link interacts with The FR can only bind to the AC using the link Join Defining Frases The name of the artifact is FR XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled There is no other with the same number FR The attribute name is not empty The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is an RA or an attribute of this The description attribute is filled Language is NDT Requisitos The type of the attribute belongs to the language of the artifact 10 7 2 Display Prototypes A prototype display allows navigation to express the possibilities existing in the system besides making reference to what data is displayed to each of the actors and what functionality is associated to each module of reporting To get these prototypes we should do a study of the objectives and interviews Also having defined the requirements and frases of the above tasks helps to identify them better sS User guide and best practices for NDT Profile
100. gramming language 12 3 3 Presentation A presentation artifact is the evolution of artifacts from the navigation model NO QU e IN Since each artifact model navigation artifact generates a presentation on the design model classes with the same attributes and or operations if any In Figure 87 we see the standard properties of an artifact of presentation modeled as an artifact of PR Page 118 of 144 INGENERLA WEB Y TESTING TEMPRANO gt User guide and best practices for NDT Profile 2 X 9 e 3X 3 33 38 3 9 X g DIDIT E Presentaci n PR1 E a X 3 3 4 8 amp amp PH ar 2 3 3M General Details Require Constraints Links Scenario Files Tagged Values _ 9 2 39 35 3q Name PRI lt 9s 9 9 9 83 ww wm tags Nombre Clase 4 Paquete Tecnologia JSF Jr ae ee ROMS Stereotype Presentaci n mm Abstract ee ee Author GRUPO IWT2 Status vi e 241 z ve Scope Public Complexity E asy Presentaci n Z las anguage UA PR1 Alias guage NDT Requisitos xi f Persistence Keywords E o p atributo String y Phase 1 0 Version 1 0 a operacioni vol A Bi Us Z Z Z Z Z Figure 87 Standard properties and tagged values of a class presentation In the PR artifact there are a number of fi
101. he link Both tabs are equal and can be seen in Figure 25 Page 35 of 144 S User guide and best practices for NDT Profile 2 X IWr2 INGENERLA WEB Y TESTING TEMPRANO E UseCase Properties General Constraints Source Role Target Role Tagged Values AC 00 Actor Ejemplo Role Alias Role Notes Derived Derived Union Containment Unspecified Owned Access Public Multiplicity Aggregation none Ix J Fx v ES EJ Target Scope instance Ordered Navigability Navigable Allow Duplicates X Changeable none Constraint s Qualifier s Stereotype imi Member Type Figure 25 Tab target source and role of a connector This tab has special relevance within NDT Profile in the transformation of storage requirements RA and NA to artifacts of the content model of the analysis phase CL and CLn If using NDT Driver for automatic processing and focusing on the transformation RA to CL there will be a link between two CL if any of the RA of which must have a specific data type another RA Then the role will link the name of the specific data as cardinality Multiplicity the cardinality of specific data If this were done manually the role should be selected with the first combobox that appears which show the attributes of the source element in the case of being in the Source tab Role or destination should be Role the Target tab The cardinality of the link
102. her fields are optional but recommended that the form is completed for a better definition of services These are Status Status Field This field contains the situation where the service is in its development process The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the service This field is meaningless when it comes to large systems where version management is a critical task Table 27 Analysis Services Rules Definition of Services You must have a type diagram Services The name and description must be filled Each service that is not the repository of services has to be at least the attributes that appear in the toolbox If a service is in the service repository you must have all the data and have to crawl into this diagram not to be in the project folder browser The attributes must have completed compulsory at least the name type and stereotype Operations must have filled the name parameters return value and description 11 2 Content classes The content model class represents the class diagram derived from the information storage requirements Allows for modeling how to structure the information handled in the system Figure 48 shows the toolbox model defined content classes such as artifacts of CL in the case of classes that come from the RA requirements and CLn type artifacts for classes that come from the NA of require
103. ic vi Complexity E asy ae Alias Language Java v Gedi n de Cambios Keywords atributol Texto Phase 1 0 Version 1 0 Gedi n de Vida M Atributo Texto oles Figure 39 Properties of a Service Standards Service in the artifact there are a number of fields that are required for the service description to be correct In the case of service attributes they are added to the artifact from the Toolbox DRS Services seen in Figure 38 To do this click on the toolbox is the attribute to add and drag the desired service A screen to assign the desired value These mandatory fields are Name Name field Each goal should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format Service XX Nombre where XX is a two digit number or exceptionally three figures if there is a high number of services Author Author field This field contains the name of the company or person in the company responsible for defining the service Page 55 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Description Field Notes This field is described with the depth of detail that the author deems appropriate the service that is being treated Change management attribute It s data of the versions branches of development obsolete features compatibility date related responsible for the changes rea
104. igure 52 Uicontrol properties of an artifact sss 71 Figure 53 Standard properties of a frase oo cccccssssssssssscsecsecsecsessessessessaesaecaecseseeseeseeseuscascaecatsansaneeneeass 72 Figure 54 Tagged values of a frase csccssccssssssssssessessesecessessessessesesseseesseseeseesaesausesseseeseeseesaesensansatees 72 Figure 55 Connections interaction artifacts nnns 74 Figure 56 Toolbox to display prototypes ocooccccoccccoccccnocccoconnconoonooncononnonnnonnonnoo noo noo ncononnnonncnnorncnnonnos 76 Figure 57 Properties of a prototype display oococcoccocococccoonnonoanonncononncononononnonnoncoonoonoononnnnononnornonnonnso TT Figure 58 Tagged values of a prototype display eene TT Figure 59 WOON OK TOR NS UNS NS 79 Figure 60 Properties Of a list nnne nnn nns 80 Figure 61 Tagged values Of a list nennen nnn nnns 80 Figure 62 Toolbox for non functional requirements cccccccsscsscsscsscssssessssessessessesssssssessassessesaesateasees 81 Figure 63 Properties of a non functional requirement oooccccccnonoonnononinoconinonnonnnononncononnnonorononnonnrnnonnss 82 Figure 64 Tagged values of a non functional requirement essen 83 Figure 69 DAS SUCIO tos 86 Figure 66 1T00lb0xes analysis ss 86 Figure 67 Analysis Services Toolbox nnne nnne nnn nnns 87 Figure 68 Properties of a Service Standards
105. iled in the Constraints tab as described in paragraph 4 2 of this guide Figure 18 and the rates may have are pre condition and post conditions If the functionality does not have any restrictions both as pre condition post condition will make clear that does not apply Diagram of activities or scenarios The tests must necessarily be described by scenarios or an activity diagram Both options are available the first by Scenarios tab seen in Figure 92 and the second by double clicking on the test If you want the functionality that will be used to describe a complex activity diagrams mandatory which are described further in Section 4 1 2 Input Parameters tagged value Indicate those input parameters necessary to run the test Expected results tagged value Indicate the output result should be obtained for the test to be considered satisfactory There are also other fields are optional but recommended that the form is completed for a better definition of functional requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate
106. ill not be defined in this guide Constraints tab is where you can define the different conditions that apply to the artifacts that define it In Figure 18 we can see the contents of the tab NT 4 e User guide and best practices for NDT Profile 2 X laz H IMSEMERLA WEB Y TESTING TEMPRANO S CL CL 00 Ejemplo General Details Require Constraints Links Scenario Files L4 gt Constraint condici n Type Invariant v Status Approved v descripci n de la condici n Figure 18 Screen artifact conditions A condition must be defined name Constraint text box the type and description The type has to be invariant Invariant for RA and NA or Pre Condition or Post Condition for RF and PS On the Links tab displaying links to other artifacts This tab allows you to sort the artifacts linked by name stereotype or connection among others as shown in Figure 19 Page 29 of 144 NT e 25 User guide and best practices for NDT Profile 2 X VV Lo EE INGEMERIA WEB Y TESTING TEMPRANO E CL CL 00 Ejemplo General Details Require Constraints Links Scenario Files Relationships Element 4 ElementSt Type Connection Stereotype OBJ1 OBJ OBJ Association Serviciol Servicio Servicio Association Figure 19 Visualizing the links of an artifact Scenarios tab is used to describe the behavior of an RF through scenarios As explained below specifically in paragraph concerning Functional Requireme
107. ing to the properties screen that is described in paragraph 4 3 of this guide Then in Table 15 we make a short summary of those rules that must meet the definition of a NDT Profile target Table 15 Objectives Rules OBJ Object diagrams Diagram has a artifact OBJ All OBJ must be contained in the diagram The only links that should appear are those of the toolbox Defining Objectives The name of the artifact is OBJ XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled There is no other with the same number OBJ Stability of tagged values importance and urgency are required The only link between OBJ is the toolbox is SubObjective of 10 2 Business model When the development process is oriented to services and SOA environments or when there is no defined a Viability study and want to get an overview of the business models of the system this section should detail NDT Profile Page 53 of 144 7 e User guide and best practices for NDT Profile 2 X IEEE ve INGENERLA WEB Y TESTING TEMPRANO 10 2 1 Process models In the first of the folders that comprise the business model process models will document all system business process models using BPMN In the folder find a diagram of processes If we add more diagrams there is no need to create it by selecting the type of diagram shown in Figure 37 Name 2 1 MODELOS DE PROCESOS Type Select From
108. ion is filled There is no other with the same number QU The attribute name is not blank The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is a CL or an attribute of this The description attribute is filled There is a QU per FR Each attribute FR is in the QU The type attribute in QU is the CL corresponding to the RA attribute of FR The cardinality of the attribute is equal to the QU FR Page 101 of 144 amp User guide and best practices for NDT Profile 2 X he TE ASIE i MEERERLA WEB Y TESTING TEMPRANS If there is a link between PV and FR the same should be a link between NO and corresponding QU The language of QU must be a valid programming language 11 3 4 Indexes An index represents those points where the user navigation you get a list of possible results to be displayed All referrals to the same information The indices are generated from a multiple bond between display prototypes If the link between two display prototypes has cardinality multiple between nodes generated an index is created connecting the two Figure 75 shows the toolbox to model rates as an artifact of type IN In Figure 78 we see the standard properties of an index modeled as an artifact of type IN E IN IN1 x General Details Require Constraints Links Scenario Files Tals l gt Name T Stereotype IN mim Abstract Autor GRUPO
109. iption If the information displayed comes from a reporting requirement indicate in the alias This information is extended with Figure 52 Language field Language This field specifies the language in which it is the artifact There might NDT Requisitos There are also other fields are optional but recommended that the form is completed for a better definition of the frases These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Importance tagged value This value indicates the importance that the system is the concept that models the artifact to the customer Must be chosen one of the presets Urgency tagged value This value indicates the urgency of the fulfillment of the concept that models the artifact Must be chosen one of the presets Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Stability tagged value This value reflects the probability of labeling the appliance undergoes changes in its definition Must be chosen one of the presets Sources tagged value This value reports the sources of the version of the appliance Page 73 of
110. irements All LI should be contained in diagram The LI can only be linked to others through the link interacts with Definition Lists The name of the artifact is LI XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled There is no other LI with the same number The attribute name is not empty The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is an RA or an attribute of this The description attribute is filled The name of the operations must be the name of an RF The description of the operation is filled Language is NDT Requisitos The type of the attribute belongs to the language of the artifact 10 8 Non functional requirements Non functional requirements are requirements do not cover in any of the foregoing A nonfunctional requirement is a requirement that specifies criteria that can be used to judge the operation of a system rather than specific behaviors Figure 62 shows the toolbox model defined as non functional requirements such artifacts RNF More tools DRS Requisitos No Funcionales edt RNF Common a 3A FE B B a u Ks 3 4 T w IF w Figure 62 Toolbox for non functional requirements Page 81 of 144 E User guide and best practices for NDT Profile 2 X IWT2 INGENIERA WEB Y TESTING TEMPRANO To create a nonfunctional requirement si
111. lds are Name Name field Each artifact should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format RA XX Nombre where XX is a two digit number or exceptionally three figures if there are a large number of storage requirements Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Page 58 of 144 User guide and best practices for NDT Profile 2 X IWT2 MO ll INSEMERIA WEB Y TESTING TEMPRANO Language field Language This field specifies the language in which it is the artifact There might NDT Requisitos Specific data within the Details tab Attributes button The specific data set of descriptors representing a RA from the point of view of users and the client How to add attributes is explained in paragraph 4 2 Figure 15 Remember that a mandatory attribute must have a name a type See Figure 42 a description and cardinality There are also other fields are optional but recommended that the form is completed for a better definition of the storage requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined
112. ly three figures if there is a large number of non functional requirements CLn XX Nombre in the case of the CL n Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Page 92 of 144 s User guide and best practices for NDT Profile 2 X E A ey a AA INGEMERIA WEB Y TESTING TEMPRANO Attributes in Details tab Attributes button The attributes represent the set of descriptors of a CL from the point of view of users and the client How to add attributes is explained in paragraph4 2 Figure 15 Remember that a mandatory attribute must have a name type description and cardinality There are also other fields are optional but recommended that the form is completed for a better definition of the classes These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments
113. me name in the same activity diagram 4 2 Artifacts Double clicking on any artifact are standard properties as shown in Figure 13 The standard properties are those properties already identified by Enterprise Architect for each appliance When adding a new artifact you must fill out the properties defined as mandatory in this manual Also highly recommended is not compulsory to fill in the properties Figure 13 shows all possible standard properties which are available for all artifacts that inherit from class OBJ Service RA NA CL CLn NO QU IN ME PR NE AD PM and IS The artifacts that inherit from another type of element for example AC or RF will not have any of the tabs but they have match those defined below Page 23 of 144 rr 25 User guide and best practices for NDT Profile 2 X MAP p INGEMERIA WEB Y TESTING TEMPRANO General Details Require Constraints Links Scenario Files Tas l gt Name RAT Stereotype RA vC Abstract Author GRUPO IWT2 a Status Proposed Scope Public v Complexity E asy Alias Language Jaya Persistence Keywords Phase 1 0 Version 1 0 Notes Figure 13 Properties Window General tab The Name field must contain the name of the element to create according to the specific nomenclature which will be detailed in the tables of nomenclature of the different phases Stereotype field is automatically filled with the stereotype of the element w
114. ments Page 90 of 144 7 lt User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO Toolbox x More tools DAS Clases de Contenido D SubSistema CL CLn Asociaci n Composici n Generalizaci n Agregaci n Clases Asociacion ndt ndt Pp A P As Common i3 D Po e A wf Figure 69 Content classes Toolbox To create a class simply click on the toolbox to the artifact CLn or CL and drag to the diagram where you want to model To see the standard properties of a class you will double click on the CL showing the screen of Figure 70 Page 91 of 144 4 25 User guide and best practices for NDT Profile 2 X E INGENERLA WEB Y TESTING TEMPRANO E CL CL 00 Ejemplo General Details Require Constraints Links Scenario Files 1 Name Stereotype CL v Ln Abstract Author GRUPO IwT2 Status Scope Public v Complexity Easy Alias Language Jaya A CL CL 00 Ejemplo atributo entero AOS OR Persistence v Keywords Phase 1 0 Version Notes B U A Figure 70 Standard properties of persistent classes In CL and CLN artifacts there are a number of fields that are mandatory for the description of classes of persistence is considered correct This series of fields are Name Name the name must meet the following format CL XX Nombre where XX is a two digit number or exceptional
115. most specific Is best represented by the names of each of the nodes between them eg joint andalucia ccul empleados Information provided by membership in a repository Definition attribute Full description of the service Must be indexable by search artifacts Taxonomy attribute node of the taxonomy of services to which it belongs Information provided by membership in a repository Semantics attribute List of keywords to the evaluations made by search artifacts Adjectives and nouns are often intimately related to the functionality of the service Business Entities attribute List of business entities related to the service Be taken in this field the principals associated with the business in case of using auxiliary entities that fall outside the scope of the functionality will not be included Technical Typing attribute Any service must be established technically Here is the tree of typing services Table 36 Technical Typing Services Ra z Tipo TYPOLOGY PROCESS COORDINATION Coordinates a sequence or flow formed by several processes PROCESS Is responsible for performing logic functions of processes decision making timing etc FUNCTIONAL BUSINESS Encapsulates business logic atomized PROXY Provides a remote business functionality implemented by distributed applications WRAPPER Encapsulates business functionality provided by legacy applications TECHNOLOGICAL CONTROL Provides ho
116. mply click on the toolbox in the artifact RNF and drag to the diagram where you want to model ES RNF RNF1 General Details Require Constraints Links Scenario Files Ta gt Name RNF1 Stereotype RNF vi m Abstract Author GRUPO IWT2 vi Status Scope Public a Complexity Easy Alias Language Jaya Persistence v Keywords Phase 10 Version 1 0 Notes Figure 63 Properties of a non functional requirement In the artifact RNF there are a number of fields that are mandatory for the description of non functional requirement is considered correct This series of fields are Name Name Every non functional requirement to be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format RNF XX Nombre where XX is a two digit number or exceptionally three figures if there are a large number of non functional requirements Page 82 of 144 User guide and best practices for NDT Profile 2 X Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the language in which it is the artifact There might NDT Requisitos There are also other fields are optional but recommended that the form is
117. n Figure 1 of various utilities These are Notes pane which displays the item description that is currently active or Tagged Values panel which shows the tagged values of the artifacts This last is necessary since there are mandatory tagged values and although they are optional the tagged values give us important information about the artifacts To display the Tagged Values panel to be activated in the menu View gt Tagged Values or press Ctrl Shift 6 Within the project browser is a series of options Figure 3 to create document diagram classes folders search and advance and delay in the browser Figure 3 Toolbox Project Browser With the first button create a folder which hangs directly from the project In NDT Profile this button is not necessary to use it The second button lets you create a package The third button opens the dialog box to create a new diagram The fourth button opens the dialog box to create a new document Table 2 Rules and structures packages Packages e Best practices The folder structure of NDT Profile can not be modified You can only create new folders within existing folders It can import elements from one folder to another by dragging with the mouse or the move of Enterprise Architect The folder PROFILE should never be changed 3 2 Traceability Matrixs Maintain traceability between the artifacts of a project is one of the most important tasks in software projects NDT Profile man
118. ng the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Nodes can connect to any other appliance model navigation Navigate through the links shown in Figure 75 To use this connector simply click on it in the toolbox click on the source node and drag to the destination artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 31 Rules of nodes NO Defining Nodes The name of the artifact is NO XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other NO with the same number The attribute name is not blank The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is a CL or an attribute of this The description attribute is filled The name of the operations must be the name of an RF The description of the operation is filled There is one NO for each PV Each attribute of the PV is in the NO The type attribute in N
119. nnn nnn 90 Table 28 Persistence Class Rules CL and CLN sess 93 Table 29 Navigation Class Rules ssssssseseseeseee eene 94 Table 30 Rules of Actors Studio AE rm 96 Ho NU o Nodes NO isane i E A 99 Table 32 Rules Queries QU sarira ET O 101 Table 33 Rules OF Indices AIN Pesar 103 Table 34 Rules Menu ME nennen nnn nnne nnns 105 Table 35 Design Nomenclature essen nennen nnn nnn 106 Table 36 Technical Typing Services cccccccscsssssssssscsscsscsssssssessessesssseseseeseesseseesausessessessesseseesansaesatsaees 111 Table 37 Design Services Rules i essi repe tote Fatti eo pR GRE rui miram Ee Rete esclusi RR talca cicle 113 Table 38 Data Access Rules AD 116 Table 39 Business Rules s m 118 Table 40 Class Rules presentation PR nnns 120 Table 41 Physical Model Rules Data oooooccooccccononocccconconcnnnonncnnnonnconnonnoononononnconnonnoonnnnncnnnnnons 121 Table 42 Test NOMEN GAT vns dime 123 Table 43 Rules of Evidence PI PS PB sseccactsstasosiszastesiesdecieundhiaquocelacutaleseneadustiasnsimadtadilecdncdiidenstloatinntadtasiensd i 132 Table 44 Maintenance Nomenclature cccccccecssssssessessssssssssssssessesseeseessesseseeseeseeseesaesseesaesaesrsrsentanss 136 Table 45 Rules Maintenance IS PM ennt nnne nnns 139 Ico DOC m
120. notation starting with uppercase The description is filled No other PR with the same number The attribute name is not empty The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is an AD or an attribute of this The description attribute is filled The name of the operations should begin in lowercase using the CamelCase notation The operation description is filled There is a PR for each navigation artifact except ME The language of PR must be a valid programming language 12 4 Prototype Design If necessary because there has been reached with the definition of the abstract interface in the design phase can address the development of a prototype implementation to validate the user responsible for the area Page 120 of 144 User guide and best practices for NDT Profile 2 X he A KR Ame 3 IWGENERLA WEB Y TESTING TEMPRANS It is advisable from the prototypes generated by NDT Prototypes and modify them by adding functionality requirements and needs of the user area 12 5 Physical data model For systems that are based on relational databases it will be necessary to develop the entity relationship model The entity relationship model is defined by the entity relationship diagram and data dictionary describing each of the elements that appear in the diagram Table 41 Physical Model Rules Data Design Physical Data Model You mu
121. ntains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Page 126 of 144 User guide and best practices for NDT Profile 2 X Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Date tagged value This field may indicate the date on which the test was carried out modeling artifact Test result tagged value This field indicates the output result obtained in the test run 14 2 System Tests The system tests are derived from the use cases defined during the requirements phase These represent the functional tests performed on the system Figure 94 shows the toolbox set to model the system testing artifacts such as PS More tools DPP Pruebas de Sistemas C SubSistema edt pS Common aa AE amp e a Ka 3 4 i uh Figure 94 Toolbox for system tests To create a system test simply click on the toolbox to the PS artifact and drag to the diagram where you want to model For more information about working with use case diagrams please read section 4 1 1 of this guide which explains how to be these diagrams Figure 95 shows a system test modeled as an a
122. nts a RF can be defined by using activity diagrams or scenarios If you choose this second option through this tab shown in Figure 20 we can describe the scenarios Page 30 of 144 lt User guide and best practices for NDT Profile 2 X MAP EE INGEMERIA WEB Y TESTING TEMPRANO E RF RF 502 General Require Constraints Links Scenario Files Taggec 1 Scenario Type 1 Escenario normal Normal descripci n del escenario mediante pasos 1 Paso 1 2 Paso2 Scenarios p Name Type 1 Escenario normal Normal 1 1 Escenario de errores Excepci n Figure 20 Defining the phases of an artifact The scenarios should have a name type must be Basic Path Alternate or Exception you cannot add more types in NDT and a description detailing the steps in this scenario There must always be a scenario like Basic Path The sequence of the normal scenario is to be by consecutive numbers 1 2 3 however the sequence of scenarios of exception must be a composite number 2 1 3 1 3 2 In short the scenarios should be an ordered sequence of numbered steps and jumps should not appear in it If desired you can use the structured specification that provides Enterprise Architect 8 The next tab Files refers to files that are linked to an artifact either a document image or any other file type The interface offers this tab is the one shown in Figure 21 Page 31 of 144 File Path Typ
123. o other fields are optional but recommended that the form is completed for a better definition of functional requirements These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task In addition batteries of tests must be linked to the project participants that made by the Realize link shown in the toolbox of Figure 98 taking as origin the participant to be dragged from the package of participants and target the battery of tests performed After creating a line that models the connector if you want to edit its properties would have to double click on the connector through the display properties described in paragraph 4 3 of this guide Page 135 of 144 7 amp User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO 15 Maintenance of the system The maintenance process in contrast to other processes running in development is a process that begins when the project moved into production and ends when the system falls into disuse The structure of system maintenance document shown in Figure 100 Project Browser x Beate ar Qr 4 n Fase DMS a T 1 SOFTWARE ISSUES a 7 1
124. o wc wur amp User guide and best practices for NDT Profile 2 X IM l INGENERLA WEB Y TESTING TEMPRANO 11 1 Service Definition Having identified the services at the phase of System Requirements will be two types of services Those are of the repository of the client already defined and designed and the services we have identified for our project It is the latter the services that we define in this phase The definition of services is to gather the most relevant information associated with it Figure 67 shows the toolbox set to artifacts such Services More tools DAS Servicios SubSistema Servicio Espacio Definici n Taxonom a Semantica Entidades de Negocio Tipificacion T cnica Operaciones Gestion de Vida Politicas Seguridad Monitorizacion Funcional Alertas Disponibilidad Maximo numero de invocaciones tiempo Tiempo medio de respuesta Tiempo maximo de respuesta Clausulas 5 nett Y 0 Y Q Y 0 Y Q Gesti n de Cambios Y 0 Y Q Y Q Y Q Y Y 8 Common ia Fa Pa im A a Figure 67 Analysis Services Toolbox Figure 68 is Observed standard properties of the Services Page 87 of 144 A E A12 5 User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO Servicio a P t Jj General Require Constraints Links Scenario Files Tagged Values A Espacio AtributoO1 Texto A Definici n Stereo
125. ocument There must be many baselines xml as there are versions of the document Each version control artifact must have a baseline linker This document should be in the folder docs baseline In the Files tab in the File Path field must have the relative path Page 45 of 144 ui E gt User guide and best practices for NDT Profile 2 X j Z INGENERLA WEB Y TESTING TEMPRANS 8 Project Objectives This paragraph shall include either a linked document or a generic description of the project in the Notes field if it is not very extensive In any case the information provided should not be too detailed and should provide an overview of the objectives to achieve with the project Table 12 Objectives Rules Document Objectives Link it must have a document This document should be in the folder docs objectives In the Files tab in the File Path field must have the relative path If the document is short you could fill in the Notes field and would not require the linking of the document Page 46 of 144 ats dt ES r E INGENERLA WEB Y TESTING TEMPRANO 9 System Viability Study EVS The structure of the documentation of the Viability study is shown in Figure 32 Bate 2 d tt 0 fa za Fase EYS 1 SYSTEM LIMITS 3 SYSTEM LIMITS ES 2 CURRENT SITUATION CURRENT SITUATION D 3 DEFINITION OF REQUIREMENTS a 3 1 STORAGE REQUIREMENTS 3 1 1 STORAGE REQUIREMENTS DIAGRAMS 9 3 1 1 S
126. on nodes Traceability between the services of analysis and design services Traceability between classes of content and data access classes Traceability between classes nature of content and data access classes Traceability between classes and types of business processes Traceability between queries and presentation classes Traceability between the indexs and types of presentation Traceability between the nodes and presentation classes Traceability between content classes and the tables of physical data model Traceability between the functional requirements and system testing Traceability between requirements and functional acceptance tests 5 3 Best practices for artifacts These rules apply to all artifacts to fill in all phases Documents EVS DRS DAS DDS DPS y DMS All artifacts requirements use cases classes test cases packages etc Should have a name and description that provides value In addition as discussed below all elements have a numerical code This code may not match the numbering of two artifacts of the same type Every element must have a description including specifications scenarios etc Page 38 of 144 25 User guide and best practices for NDT Profile 2 X IWT2 INGENIERA WEB Y TESTING TEMPRANO 5 4 Linking the documents Along with the delivery of the file with Profile EAP is to attach a folder called docs which contains all documents attached in the different Document type artifacts that app
127. ong the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate The index can be connected to any other navigation artifact model using the links Navigate shown in Figure 75 To use this connector simply click on it in the toolbox click on the background rate and drag to the destination artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 33 Rules of Indices IN Defining Indexes The name of the artifact is IN XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled IN no other with the same number There is an IN for each multiple bond between two PV the IN will have a link to each PV The language of IN must be a valid programming language 11 3 5 Menus A menu is a navigation point from which the user can go to several different options The difference between the menu and the index is that in the index all the items listed refer to the same information In a menu of options from which you can choose
128. ove Replication 2 Wordpad Resolve Replication Conflicts W Windows Explorer Customize Fa a r Options Ctrl F9 Figure 106 Compact EAP files Page 142 of 144 4 d Proyecto NDT Suite 2 X qe E INGENIERLA WEB Y TESTING TEMPRANO User guide and best practices for NDT Profile 2 X 18 Glossary The following are the terms used in this document Table 46 Glossary Term Description Enterprise Architect Enterprise Architect CASE Computer Aided Software Artifactering NDT Navigational Development Techniques Page 143 of 144 nr gt Proyecto NDT Suite 2 X IW i t User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO 19 Bibliography and references The following are the relevant references Table 47 Bibliography Reference Title NDT http www iwt2 orq No Codigo Page 144 of 144
129. plains how to be these diagrams Figure 92 shows an Implantation tests modeled as an artifact of type PI and property standards Page 124 of 144 IWT 4 e User guide and best practices for NDT Profile 2 X Amm INGENERIA WEB Y TESTING TEMPRANO ES Pl PI 00 Ejemplo PI 00 Ejemplo Stereotype PI MM mim Abstract Author GRUPO IWT2 m Status Scope Public v Complexity Easy Alias Language none Keywords Advanc A4 ttt tts i PI PI 00 Ejemplo Bp VF FF FK FP AAA KE v ra Figure 92 Standard properties of an Implantation tests Page 125 of 144 4t Qe y We dl UB a Er Am 5 INGSEMERIA WEB Y TESTING TEMPRANO ETT EJ Y PI 00 Ejemplo Pl Comentarios Fecha de realizaci n Par metros de entrada Resultado de la prueba Resultado esperado B notes Q Tagged va V Pan amp Zoom ES Properties Y Testin Figure 93 Tagged values of an Implantation tests In the Pl artifact there are a number of fields that are mandatory for the description of the test of implementation is considered correct This series of fields are Name Name Each Implantation tests to be classified with a code and a descriptive name As shown in Table 42 the name must meet the following format PI XX Name where XX is a two digit number or exceptionally three figures if there is a large number of tests
130. ppercase The description is filled No other AD with the same number The attribute name is not empty The attribute name must begin in lower case using the CamelCase notation The type attribute is not empty The type of the attribute is an AD or an attribute of this The description attribute is filled There is a AD for each type of content Each attribute of a CL is in the AD The cardinality of the attribute of AD is equal to the CL The language of AD must be a valid programming language 12 3 2 Business A business artifact is the evolution of the process classes From each CP is generated an artifact of business with the same operations Page 116 of 144 gt User guide and best practices for NDT Profile 2 X INGENERLA WEB Y TESTING TEMPRANO T mM go 9 IR z m x me cee eer O oes hee ATA A ee A General Details Require Constraints Links Scenario Files Tagged Values AICA Name NE1 ET PE ey Stereotype Negocio vi Abstract AN NL PP Author GRUPO IwT2 vi Status Scope i Complexity Negocio p Public v plexity E asy NE1 Alias Language NDT Requisitos operacion void Persistence vi Keywords Version 1 0 tags Nombre Clase Paquete Tecnologia JSF IO Figure 86 Standard properties and tagged values of a class of business NE in the artifact there are a number of fields that are mandatory for the description of the kind of b
131. prototype display The standard properties of a prototype display are the same as those of a frase as shown above Its tagged values are the same as those of a target also shown above Tagged Values X E ji m E PV1 PV Comentarios Estabilidad Fuentes Importancia Urgencia Figure 58 Tagged values of a prototype display Page 77 of 144 M INGENERLA WEB Y TESTING TEMPRAMO In the prototype view mandatory and optional data are also the same as in the frases so you will not be described again The prototype display can be linked with any other artifact with each other through interaction and Interacts With the connector and actors through the Join link which appears in the toolbox seen in Figure 56 These connectors are explained in paragraph 10 7 1 and shown in Figure 55 Table 22 Display Prototype Rules PV Diagrams Display Prototype You must have a diagram of type of interaction requirements All PV should be contained in the diagram The PV can only link to other artifacts for interaction through the link interacts with The PV can only bind to the AC by binding Join Prototype Definition Display The name of the artifact is PV XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other PV with the same number The attribute name is not empty The attribute name must begin in lower case using the CamelCase notation The type attri
132. r in the toolbox If a service is in the service repository you must have all the data and have to crawl into this diagram not to be in the project folder browser Every service must have an associated WSDL diagram Every service must have an associated SoaML Component diagram 12 2 Architectural Overview To begin to define the design of any system it is necessary to define the technology architecture system This part is divided into a diagram to define the technological environment and a series of documents In the diagram of this folder should be described the technological environment the programming language programming environment etc Should be discussed with a level of detail that does not lead to errors For this use the diagram of components that are created by default in NDT Profile The remaining documents must describe how the system accesses to external systems the performance expected of the system security mechanisms adaptation to the LOPD or the anticipation of future growth These documents should be attached to the eap file as described in Section 5 4 12 3 Model design classes In the class model will be the evolution of the types of analysis including the necessary design patterns classes and methods needed for proper implementation Figure 84 shows the defined toolbox for design class shared among the business classes presentation and data access Page 113 of 144 sS User guide and best practices for N
133. responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Page 95 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMSEMERLA WEB Y TESTING TEMPRANO Language field Language This field specifies the programming language in which it is the artifact There are also other fields are optional but recommended that the form is completed for a better definition of the actors These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Collection Collection Classes button in the Details tab Through this section shall indicate if the class is a collection If it were not would not have to fill anything Comments tagged value This field allows the author to the target indicate any other information it deems appropriate EJES Y tx AE1 AE Comentarios Um m S A SON So m Ws Notes 9 Tagged Va a Pan Zoom Art Properties nf Testing Figure 74 Tagged values of an actor to study As for the actors of the system requirements
134. rizontal sharing security session etc Dispatcher fagades UTILITY Provides functionality outside the business calculations helpers Messages attribute This is the information they require operations to vary their behavior The message is return Usually represented by input and output parameters Page 111 of 144 2 User guide and best practices for NDT Profile 2 X IWT2 5 INSEMERIA WEB Y TESTING TEMPRANO Type attribute Constraints of form and content of messages It is recommended that type definitions are standard and serializable Errors Exceptions attribute Possible malfunctions of operations Location attribute Point of service invocation Change management attribute data are versions branches of development obsolete features compatibility date related responsible for the changes reasons for them history of previous versions etc Life Management attribute Data related to the state it was found service in certain contexts development testing integration production For example maintains that the active versions of a service in development are x and x 1 while production is x 3 It also maintains data dependencies should be minimal in the case of services which may be by the membership of service to a BPM Responsible attribute Responsible for the deliverables of the contract service Owner attribute Maximum level of escalation in terms of the contract service Re
135. rmine all the storage needs are identified during the interviews The new natures are different storage requirements that the NA defined information requirements that already exist in other systems which will make use of or are new domains that are defined specifically for the system that being modeled The properties of a new nature are the same as those of a storage requirement so the figures seen above are also valid for the new natures The tagged values of nature are shown in Figure 44 Page 61 of 144 amp gt User guide and best practices for NDT Profile 2 X IW 2 INGENIERA WEB Y TESTING TEMPRANO NA1 NA Comentarios Estabilidad Fuentes Importancia Urgencia m Tagged Values 4 Figure 44 Tagged values of a new nature Table 18 Natures New Rules NA Defining New Natures You must have a diagram of type New Natures Every NA should be contained in the diagram The name of the artifact is NA XX X Name The artifact name must be unique using the CamelCase notation and starting in uppercase The description is filled There is no other with the same number NA The attribute name is not empty The name of the attribute must begin in lower case using the CamelCase notation The type attribute is not empty The description attribute is filled Language is NDT Requisitos The type of the attribute belongs to the language of the artifact 10 5 Requirements of stakeholders A basic actor is all actor that
136. rom the artifacts uicontrol button type How to add operations are explained in paragraph 4 2 Figure 17 Remember that a transaction has to be necessarily a name alias and description There are also other fields are optional but recommended that the form is completed for a better definition of the nodes These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate The queries can be connected to any other appliance model navigation Navigate through the links shown in Figure 75 To use this connector simply click on it in the toolbox click on the query source and drag to the destination artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 32 Rules Queries QU Defining Queries The name of the artifact is QU XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The descript
137. rtifact of type PS and property standards Page 127 of 144 e 25 User guide and best practices for NDT Profile 2 X E INGENERLA WEB Y TESTING TEMPRANO ES PS PS 00 Ejemplo General Require Constraints Links Scenario Files Taggec 41 gt Name PS5 00 Ejemplo Stereotype PS m Abstract Author GRUPO IWT2 Status Scope Public Complexity Easy Alias Language lt none gt Keywords Proce 10 Version 1 0 Notes B i U A BAP Fg m Wc LALALA A WANY Ux CODO NA it lo ds s e S Figure 95 Standard properties of a system test The tagged values of all tests are identical so are the same as shown in Figure 93 In the PS artifact there are a number of fields that are mandatory for the description of the system test is considered correct This series of fields are Name Name Each system test to be classified with a code and a descriptive name As shown in Table 42 the name must meet the following format PS XX Name where XX is a two digit number or exceptionally three figures if there is a large number of system tests Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Page 128 of 144 User guide and best pr
138. s Other Filters Project Constants Word Substitution Codepage Master Document acumentaci n DAS Output to File C salida rtf RT Resource Document Use Template Edit Template Use Language Substitutions View Document on Completion Use Internal Viewer Include all Diagram Elements in Report Optimize For Open Office View Figure 105 Window options in EA 4 Indicate where to save the output document and click the Generate button Page 141 of 144 eu E Am d INGENERIA WEB Y TESTING TEMPRANO NT 4 User guide and best practices for NDT Profile 2 X 17 Repair and Compact the EAP file If you are using the EAP file and your project is not working on a data server you need to take several steps to make our project is as safe as possible Because when we are working with the Enterprise Architect is generated much junk information that makes our file it is large we have to regularly doing two operations that would e Repair EAP File e Compact EAP File Both operations are in the menu Tools Manage EAP File as shown in Figure 106 gj Spell Check Project Ctrl F Spell Check Current Package Ctrl Mayusculas F7 ea Spelling Language Data Management gt care Run Patch dy Compact EAP File di Export Reference Data Make Design Master uil Import Reference Data i Create New Replica Import Technology Ba Synchronize Replicas G ate MDG hnology File gig lec 9 Rem
139. s the artifact within the system Must be chosen one of the predefined values There are also other fields are optional but recommended that the form is completed to better define the menus These are Status Status Field This field contains the situation where the artifact is in the process of development The value must be selected among the possible predefined shown Version Field Version Through this field are managed by different versions of artifact This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author intended to indicate any other information it deems appropriate Page 138 of 144 gt User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Date of resolution tagged value This field may indicate the date on which the incidence has been determined that the engine model All software issues or Requests For Improvement to define traceability relationships with the affected artifacts It is up to the project coordinator to define whether such artifacts comply with the requirements analysis or system design To this end the artifact can be connected to any other artifact using the links project Implies to shown in Figure 101 To use this connector simply click on it in the toolbox click on the incidence of origin and drag to the destination artifact in the diagram After cr
140. shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Importance tagged value This value indicates the importance that the system is the concept that models the artifact to the customer Must be chosen one of the presets Urgency tagged value This value indicates the urgency Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Stability tagged value This value reflects the probability of labeling the appliance undergoes changes in its definition Must be chosen one of the presets Sources tagged value This value reports the sources of the version of the appliance Interval time tagged value This value indicates how long the artifact is effective It can take two values Present and Present and past There is define the type of specific data defined Since this is a phase in the early life cycle the type must be detailed in the NDT Requisitos language Next Figure 42 shows the different types of data allowed in NDT Profile for storage requirements Page 59 of 144 IWT 25 User guide and best practices for NDT Profile 2 X P IMSEMERLA WEB Y TESTING TEMPRANO Programming Languages Datatypes Product Name In DT Requisitos zj Add Product Datatype rSie Common T ype Length Z
141. sions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Comments tagged value This field allows the author to the target indicate any other information it deems appropriate Date tagged value This field may indicate the date on which the test was carried out modeling artifact Test result tagged value This field indicates the output result obtained in the test run The system tests should define traceability relationships between elements of the system test and use cases 14 3 Acceptance Tests The acceptance tests are a subset of system tests and are intended to be held by end users Figure 96 shows the toolbox to model definite acceptance testing artifacts such as PA Page 129 of 144 S User guide and best practices for NDT Profile 2 X IW 125 INGENERLA WEB Y TESTING TEMPRANO More tools DPP Pruebas de Aceptaci n P4 SubSistema nt PA Common 28 AE amp a a E Ya 3 4 Ta fg Figure 96 Toolbox for acceptance tests To create an acceptance test simply click on the toolbox in the PA artifact and drag to the diagram where you want to model For more information about working with use case diagrams please read section 4 1 1 of this guide which explains how to be these diagrams Figure 97 shows a system test modeled as an artifact of type PA and property standards Page 130 of 144 25 User guid
142. sons for them history of previous versions etc Management of life attribute Data related to the state it was found service in certain contexts development testing integration production For example maintains that the active versions of a service development are x and x 1 while the output is x 3 It also maintains data dependencies should be minimal in the case of services which may be by the membership of service to a BPM There are also other fields are optional but recommended that the form is completed for a better definition of services They are Status Status Field This field contains the situation where the service is in its development process The value must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the service This field is meaningless when it comes to large systems where version management is a critical task Table 16 Service Rules Service Diagrams You must have a type diagram Services All Services are to be contained in the diagram Definition of Services The name and description must be filled Each service that is not the repository of services has to be at least the attributes that appear in the toolbox If a service is in the service repository you must have all data and has to crawl to the diagram not to be in the project folder browser 10 3 Storage Requirements The storage requirements along with
143. ssible connections For example if you want to complete that section of storage requirements should open the diagram in Section 3 1 1 of the DRS folder Once opened to add a new storage requirement is selected in the toolbox the RA artifact and drag it to the center panel When you add an item this is incorporated into the folder where you will find the diagram in the above example Figure 11 in the folder 3 1 1 This artifact must then move to the folder 3 1 2 which is where the storage requirements defined Page 21 of 144 User guide and best practices for NDT Profile 2 X AA I GIEMISIRIA WEB Y TESTING TEMPRANO 4 1 1 Use Case Diagrams When describing both the functionality of the system as all tests are used use case diagrams These diagrams have to meet certain basic rules modeling so they can consider valid something not always seen when you do this type of diagram In Figure 12 we can see an well example RE RF 502 Ejerpplo Figure 12 Example use case diagram well built First in a use case diagram must appear at least one actor since it has to specify who can perform the functionality In addition all use cases should have a link to the actor or have a relationship include or extend both are defined by UML with a use case linked to an actor The link to the actor has to be of use and their properties can be edited as discussed later in section 4 3 It is also a fundamental requirement in the
144. st have a diagram of type Data Modeling Data Modeling with the toolbox All Tables should be contained in the diagram Data Dictionary The name of the artifact must meet the specific nomenclature marked by the client The table alias is the name of CL from which The type of artifact is table The description is filled The field name is not empty The type field is not empty The alias of the fields is the name of the attribute from which CL The description of the fields is filled Page 121 of 144 Es User guide and best practices for NDT Profile 2 X WT2 em F ve MEERERLA WEB Y TESTING TEMPRANS 13 Implementation The implementation phase consists simply of products resulting from the implementation of the conceptual framework defined in previous phases The structure of packages NDT profile shown in Figure 88 Project Browser EA G t Fase IMPLEMENTATION 3 1 SOURCE CODE T SOURCE CODE a 2 DB SCRIPT DB SCRIPT a 3 IMPLEMENTATION PLAN 59 IMPLEMENTATION PLAN 4 USER MANUAL i USER MANUAL 5 5 TRANSITION TO PRODUCTION IMFORM T TRANSITION TO PRODUCTION IMFORM Far E seas NDS ey Project Browser de Figure 88 Structure of the construction phase The implementation phase is divided basically in a series of documents These documents should be attached to the eap file as described in Section 5 4 Source documents and DB script need not be filled but must contain a link
145. tagged value This field allows the author to the target indicate any other information it deems appropriate Tagged Values x Ic CL1 CL Comentarios Tt gt Tagged Val La Figure 71 Tagged values of a class analysis Persistent classes can be bound together by the connectors aggregation association composition and generalization that appears in the toolbox Figure 69 Figure 35 These connectors are extensions of the connectors aggregation association composition and generalization of UML To make use of these connectors simply click on the toolbox to select the connector click on the class of origin and drag to the target class in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 28 Persistence Class Rules CL and CLN Diagrams Display Prototype You must have a diagram of type persistent classes All CL and CLn should be contained in the diagram Prototype Definition Display The name of the artifact is CL XX X Name or CLn XX X Name The artifact name must be unique using the CamelCase notation and starting in uppercase The artifact has description There is no other RA with the same number The attribute name is not empty Page 93 of 144 e s User guide and best practices for NDT Profile 2 X E A b x AA
146. te gy BPMN 1 0 A nmaa Tarca Figure 11 Choosing the Chart Type The correlation between the sections of the project and the different types of diagram of the Enterprise Architect tool are shown in Table 5 The sections are not included in the table does not have any associated diagram can be used as a type of diagram free choice or use a text document Annex Page 20 of 144 25 User guide and best practices for NDT Profile 2 X b i AA INGEMERIA WEB Y TESTING TEMPRANO Table 5 Types of diagrams for sections of the draft Paragraph PARTICIPANTS VERSION CONTROL EVS Storage Requirements EVS Actors EVS Functional Requirements EVS Interaction Requirements EVS Nonfunctional requirements DRS Objectives DRS Process Models DRS Identification Services DRS Storage Requirements DRS Actors DRS Functional Requirements DRS Interaction Requirements DRS Nonfunctional requirements DAS Definition of Services DAS Content Types DAS Process Classes DAS Actors Studio DAS Navigation Classes DDS Design Services DDS Design Services 1 DDS Design Services 2 DDS Design Services 3 DDS Technological Environment DDS Design Classes DDS Physical Data Model DPS Implementation Testing DPS System Testing DPS Acceptance Tests DMS Software Issues DMS Improvement Petitions Chart Type Control Diagrams NDT Participants Control Diagrams NDT Version Con
147. tects that actors can be grouped to reduce the need to develop models for different actors alike Figure 72 shows the model defined toolbox actors More tools DAS Actores de Estudio mot AE Hereda de Common amp DB AS E 3 0G V3 BG T IF w Figure 72 Study Toolbox for actors To create an actor just click on the toolbox in the artifact AE and drag to the diagram where you want to model In Figure 73 and Figure 74 shows an actor to study their properties and their values labeled standards Page 94 of 144 e 25 User guide and best practices for NDT Profile 2 X IWIZ EE INGEMERIA WEB Y TESTING TEMPRANO ES AE AET Name AE Stereotype AE pim C Abstract Author GRUPO IWT2 Status Scope Public v Complexity E asy Alias Language none DS ML x IAEA CLA lg La a Keywords 1 0 Version 1 0 N Ss LLLA Figure 73 Standard properties of an actor to study In the artifact AE there are a number of fields that are mandatory for the description of the actor is considered correct This series of fields are Name Name Each actor should be classified with a code and a descriptive name As shown in Table 14 the name must meet the following format AE XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of players Author Author field This field contains the name of the company or person in the company
148. the study generalization between actors is permitted and is manifested with the existing connector Inherits From the toolbox of Figure 74 To use this connector simply click on it in the toolbox click on the original actor and drag to the target actor in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 30 Rules of Actors Studio AE Diagrams Actors Studio You must have a type diagram Actors studio All actors must be studied in the diagram contents You may only link by link inherited from Definition of Actors Studio The name of the artifact is AE XX X Name The name of the artifact must use the CamelCase notation starting with uppercase Page 96 of 144 s User guide and best practices for NDT Profile 2 X M12 INGENERLA WEB Y TESTING TEMPRANO The description is filled No other AE with the same number There is one AE for each AC The language of the appliance must be a valid programming language 11 3 2 Nodes A node is a point of navigation where the user can work with information retrieve or modify data in the system and have the same functional possibilities The nodes are generated from the prototype display Basically each prototype display generates a node and the artifacts uicontrol than button type prototype become uicontrol attri
149. the value labeling May be linked to Provider or Client The artifact development team representing the developers of the system May be linked to Provider or Client All artifacts have the same standard properties name author description Here we showed one of them ES Cliente Cliente1 Stereotype Cliente mim Abstract Author GRUPO IwT2 v Status Scope Public Complexity E asy ACE Alias Language none 2 D Keywords a 2 Phase ES Figure 29 Standard properties of Participants Page 42 of 144 NT e User guide and best practices for NDT Profile 2 X IMSEMERLA WEB Y TESTING TEMPRANO No tagged values for participants Client Provider and Committee but there is a tagged value type participants Participant Team and Development Team Project For these the value has to be completed mandatory labeling Tagged Values 2 Equipo de Desarrollol Equipo de Desarrollo A Z d Tipo Participante Seleccionar Tipo As IS pc ge rrollo1 puto ipo Figure 30 Participants tagged values Table 10 Rules of Participants Diagrams of Participants Must contain all participants according to the outline of the organization The only links that should appear are those of the toolbox The artifact name of the Project Team is an EP XX X Name The name of the Artifact Development Team is ED XX X Name Project Team and Development Team should be selected on the values labeled type
150. trieved attribute Who should be consulted before taking any action on this contract service Informed attribute Who should be informed of any decision or action to be taken on this contract service Politics attribute Specification of the policies implemented by the service to be defined in the SOA governance model Segurity attribute Specification of the security restrictions that apply to the service to be defined in the SOA governance model Functional Monitoring attribute Functional monitoring indicators that apply to the service to be defined in the SOA governance model Technical Monitoring attribute Alerts attribute Levels and types of warning based on indicators defined above Availability attribute Indicates the slot or slots and days on which the service can be used For example from 8 00 to 20 00 from Monday to Friday except public holidays or 24hx7d as Maximum number of invocations time attribute Indicates the maximum number of invocations that a client can perform in a defined time unit for example 10 invocations per second Average response time attribute Maximum response time attribute Maximum message processing Clauses attribute Other clauses that may apply to the particular hiring and where appropriate non compliance Operations in Details tab button Operations The services must have at least one operation How to add operations are explained in paragraph 4 2 Figure 17 Rem
151. trol Diagrams EVS Storage Requirements Diagrams EVS System Actors Diagrams EVS Functional Requirements Diagrams EVS Interaction Requirements Diagrams EVS Nonfunctional requirements Diagrams DRS Objectives Diagrams DRS Processes Diagrams DRS Services Diagrams DRS Storage Requirements Diagrams DRS Actors Diagrams DRS Functional Requirements Diagrams DRS Interaction Requirements Diagrams DRS Nonfunctional requirements Diagrams DAS Services Diagrams DAS Content Types Diagrams DAS Process Classes Diagrams DAS Sequence Diagram Diagrams DAS Actors Studio Diagrams DAS Navigational Model Diagrams DDS WSDL SOAML SoaML Component Diagram SOAML SoaML Sequence Diagram Diagrams DDS Technological Environment Diagrams DDS Design Classes Diagrams DDS Data Modeling Diagrams DPS Implementation Testing Diagrams DPS System Testing Diagrams DPS Acceptance Tests Diagrams DMS Maintenance Diagrams DMS Maintenance 1 Each service must have an associated diagram WSDL 2 Each service must have an associated SoaML Component diagram 3 Each service can have an associated SoaML Sequence diagram These diagrams are already created in their appropriate folder so just go adding artifacts to the diagram When you open the diagram the toolkit will be charged for the phase you are working making it easy to add appliances as they will be available only those that can be added to the diagram and po
152. type Servicio mm At buto02 Texto E Author GRUPO IWT2 vl Status Taxonom a A Atributo03 Texto LM Scope Public vl Complexity E asy Sem ntica Alas a Atr butoO4 Texto f l Entidades de Negocio E Keywords A Atributo05 Texto gt Phase 1 0 Version 1 0 Advanced Tipificaci n T cnica E Advanced 4 Atributo06 Texto I Notes Gestion de Cambios A At butoO7 Texto 4 Gestion de Vida E Atr butoOS Texto Seguridad Atributo09 Texto A Monitorizaci n Funcional Atributo10 Texto Alertas Atributo11 Texto Disponibilidad Atributo12 Texto Name Serviciol Language Java M ximo n mero de invocaciones tiempo Atributo13 Texto A Tiempo medio de respuesta Atributo14 Texto Tiempo maximo de respuesta Atributo15 Texto Clausulase Atributo16 Texto Operaciones Operacion int Aceptar Figure 68 Properties of a Service Standards The artifact analysis services there are a number of fields that are mandatory for the service description to be correct In the case of service attributes they are added to the artifact from the Toolbox DAS Services seen in Figure 67 To do this click on the toolbox is the attribute to add and drag the desired service These mandatory fields are Name Name Each goal should be classified with a code and a descriptive name As shown in Table 25 th
153. ue must be selected among the possible predefined shown Version Field Version Through this field manage the different versions of the appliance This field is meaningless when it comes to large systems where version management is a critical task Classname tagged value This field shows the exact name of the class that is implemented Package tagged value This field shows the exact name of the package containing the class implements Technology tagged value This field is indicated by a drop down technology in the classroom The design classes can connect to any other appliance model design classes through the links AS Association shown in Figure 84 To use this connector simply click on it in the toolbox click on the home appliance and drag to the target artifact in the diagram Once you create a line that models the connector if you want to edit its properties would have to double click on the connector going to the properties screen that is described in paragraph 4 3 of this guide Table 39 Business Rules NE Business Class Definition The name of the artifact is NE XX X Name The name of the artifact must use the CamelCase notation starting with uppercase The description is filled No other NE with the same number The name of the operations should begin in lowercase using the CamelCase notation The operation description is filled There is a NE for each artifact CP The language of PR must be a valid pro
154. uentra el origen de la referencia that is the left is the name and takes the value right 4 3 Connectors In NDT artifacts can be linked through the connectors The connectors are links between two artifacts with a number of properties described in this section We can see an example of two artifacts in this case an actor and a functional requirement linked to a Use type connector in Figure 23 Page 33 of 144 User guide and best practices for NDT Profile 2 X E Een RF RF 502 Ejeropla AC O0 Actor Ejemplo E UseCase Properties General Constraints Source Role Target Role Tagged Values Source AC 00 Actor Ejemplo Target RF 502 Ejemplo Name usa Alias Direction Source Destination v Style Custom Stereotype v Figure 23 General properties of a conductor On the General tab to observe the basic properties of the connector In the title of the window shows the name of the type of connector that has been used in this case UseCase This type of connector is generic UML although there are many other connectors that are specifically defined UML extensions in NDT Profile These connectors are specified within the artifacts that make use of them in the paragraphs of the life cycle phase it is concerned although the properties of the connectors are common to all In the Source field shows the artifact of origin of the connector and in the Target field shows the destination of th
155. usiness is considered correct This series of fields are Name Name Every business class should be classified with a code and a descriptive name As shown in Table 35 the name must meet the following format NE XX Nombre where XX is a two digit number or exceptionally three figures if there is a large number of business classes Author Author field This field contains the name of the company or person in the company responsible for defining the artifact Description Field Notes This field is described with the depth of detail that the author deems appropriate the artifact being treated Language field Language This field specifies the programming language in which it is the artifact Artifact associated Alias This field shall specify the artifact from which the artifact generates current in this case the prototype display that comes Page 117 of 144 amp User guide and best practices for NDT Profile 2 X IW 2 IMEEMERIA WEB Y TESTING TEMPRAMO Operations in Details tab button Operations The way to add operations are explained in paragraph 4 2 Figure 17 Remember that a transaction has to be necessarily a name nickname and a description There are also other fields are optional but recommended that the form is completed for a better definition of the nodes These are Status Status Field This field contains the situation where the artifact is in the process of development The val
156. will revert to its current state as it was used as the baseline for comparison The tenth button displays a menu of options to configure the items displayed in the window of comparison in order to restrict what types of items are displayed You can create as many as deemed appropriate baselines necessary and always according to the versions of the deliverables that are made Note The baselines occupy space within the file eap since they are stored inside To avoid excessive increase in size eap and corrupt is recommended to be exported to xml and disposed of eap To export you should select the appropriate baseline click the Export File button and select the location to save When you need to see the baseline just import the xml file which you want to compare the current model To do so click on the Import File button and select the xml file on your hard drive The location of these buttons is shown in Figura 10 Page 18 of 144 INGENERLA WEB Y TESTING TEMPRAMO Manage Baselines Current Baselines For Package NDT PROFILE 2 0 Name Y 4 Notes NOT PROFILE 0 0 NOT Profile 2 0 NOT PROFILE 1 0 Baseline time 06 11 2009 11 39 27 Delete Selected Connected To PROFILE 2 0 eap Figura 10 Import and export baselines Table 4 Rules of the baselines em Best practices e With each deliverable document is to be delivered in a baseline xml encompassing the entire profile indicating the version and date Page 19 of 144

User guide and best practices for NDT-Profile 2.X Proyect NDT

Contents

Download Pdf Manuals

Related Search

Related Contents