![\"metamodel\"](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" "\\"metamodel\\"\/")
<\/figure><\/div>\n\n\n\n\n\n\n\n
![\"task](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/task-list.png\")
<\/figure>\n<\/div>\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities…). They could represent a “to-do” list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n![\"resource](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/resource-list.png\")
<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n![\"card](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/card.png\")
<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n![\"semantic](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/semantic-precedence.png\")
<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n![\"card](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/card-flow.png\")
<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n![\"type](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/type-of-card-flow.png\")
<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n![\"\"\/](\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/2021\/03\/examples-of-graphic-notation.png\")
<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","protected":false,"raw":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n\n\n\n\n
<\/figure>\n<\/div>\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n"},"excerpt":{"rendered":"","protected":false,"raw":""},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_es_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
Descripci\u00f3n de los elementos que usamos en la notaci\u00f3n gr\u00e1fica propuesta para representar patrones de herramientas basadas en tableros (board-based tools). Con la siguiente simbolog\u00eda representamos un total de seis elementos diferentes, que son parte de nuestro metamodelo (ver primera figura). Todos los elementos tienen el mismo nombre en el metamodelo y en su correspondiente notaci\u00f3n gr\u00e1fica, para su correcta identificaci\u00f3n. A continuaci\u00f3n, explicamos cu\u00e1les son esos s\u00edmbolos y elementos, qu\u00e9 representan y c\u00f3mo deben usarse para representar el patr\u00f3n de un tablero.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n\n\n\n\n
<\/figure>\n<\/div>\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan tareas (acciones, actividades...). Pueden representar una lista de cosas por hacer (\"to-do list\"), un listado de las tareas a realizar para completar un proyecto, las tareas de cada fase de un proceso, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nListas que contienen cartas que representan recursos o informaci\u00f3n. Pueden representar textos, ideas, personas, conceptos o recursos abstractos.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nLas cartas son la forma de representar aquel contenido que manejamos con el uso del tablero. Pueden representar tareas o informaci\u00f3n\/recursos. Dependiendo del software espec\u00edfico que usemos y las necesidades del usuario, las cartas pueden tener etiquetas, fecha de vencimiento, persona asignada, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nSi tenemos Precedencia Sem\u00e1ntica en un tablero, significa que nuestras listas tienen un determinado orden entre ellas, que debe estar definido por el contexto del problema a representar. Este orden puede ser temporal, jer\u00e1rquico, secuenciado\/ordenado (como las etapas de un proceso), etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nLas cartas podr\u00e1n fluir entre las listas del tablero que est\u00e9n remarcadas con un rect\u00e1ngulo, como en la imagen izquierda. Puede que solo est\u00e9n enmarcadas algunas listas (un subconjunto) o todas las listas del tablero, dependiendo del contexto del problema. El flujo de cartas estar\u00e1 determinado por su tipo (ver siguiente elemento de la notaci\u00f3n gr\u00e1fica).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDependiendo de cu\u00e1l de las figuras de la imagen izquierda se encuentre en la parte inferior de la representaci\u00f3n gr\u00e1fica del tablero, el flujo de cartas permitido ser\u00e1 uno de esos tres tipos. Libre (\"Free\") si no hay ninguna restricci\u00f3n, \"Precedence\" si el flujo de cartas es acorde a la precedencia sem\u00e1ntica de las listas del tablero, o \"Complex\", si obedece alguna regla que deba ser definida en el contexto del problema.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. <\/p>\n\n\n\n
FIGURE A<\/strong>: SCRUM BOARD DESIGN<\/h5>\n\n\n\nFigure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) by means of three Lists(depicted as rectangles). They are Task lists because they store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly a Semantic precedence defined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d This is depicted by means of a dashed arrow that links the two corresponding lists. Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is a Card flow between the three lists, which is represented by means of a rectangle that groups them. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according to the semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
FIGURE <\/strong>B: TRAVEL BOARD DESIGN<\/h5>\n\n\n\nThe second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n
\n\n\n\n\n\n<\/figure>\n<\/div>\n\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_es_post_name":"graphic-notation-for-board-based-patterns","_es_post_excerpt":"","_es_post_title":"Graphic notation for board-based patterns","_en_post_content":"\n
Graphic notation for board-based patterns<\/h1>\n\n\n\n
ENGLISH
Description of the elements that we use in the graphic notation for representing board-based patterns. With the following simbols, we represent six of the elements that are part of our metamodel (first figure). All of them have the same name in the metamodel and in the corresponding graphic notation. Here we give an explanation about their simbols and elements, what do they represent and their use.<\/p>\n\n\n\n
<\/figure><\/div>\n\n\n\n\n\n\n\n
<\/figure>\n<\/div>\n\n\n\nTASK LIST<\/strong><\/h3>\n\n\n\nLists that contain cards that represent tasks (actions, activities...). They could represent a \"to-do\" list, a pending chores list, an enumerate of the tasks needed to make up a project, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nRESOURCE LIST<\/strong><\/h3>\n\n\n\nLists that contain resources or information cards. They could represent texts, ideas, people, concepts or abstract resources.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD<\/strong><\/h3>\n\n\n\nCards are the way to represent what we handle using of the board. They can represent cards or resources\/information. Depending on the specific software and user needs, they can have labels, tags, due dates, people assigned, etc.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nSEMANTIC PRECEDENCE<\/strong><\/h3>\n\n\n\nIf there is Semantic Precedence in a board, our lists have a determined order between them, determined by the context of the problem. It could be a temporal order, a hierarchical precedence or a sequenced relation of steps of a project.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nCARD FLOW<\/strong><\/h3>\n\n\n\nCards are able to flow between the lists that are framed by the rectangle of the image. There could be framed only a subset of lists or all the lists in the board, depending on the context of the problem. Flow will be determined by its specific type (see next element).<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n<\/figure>\n<\/div>\n\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n<\/div>\n\n\n\nTYPE OF CARD FLOW<\/strong><\/h3>\n\n\n\nDepending on which figure is at the bottom of the representation of the board, the flow allowed will be one of those three. Free, if there is no restriction, Precedence if the card flow is determined by the Semantic Precedence of the board, and Complex if it obeys obeys some rule that must be defined in the context of the problem.<\/p>\n<\/div>\n<\/div>\n\n\n\n
\n\n\n\nEXAMPLES OF USE<\/strong><\/h3>\n\n\n\n<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n
Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning<\/title>\n<meta name=\"description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<link rel=\"canonical\" href=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"og:description\" content=\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\" \/>\n<meta property=\"og:site_name\" content=\"ECP - Enterprise Conversation Planning\" \/>\n<meta property=\"article:modified_time\" content=\"2021-04-07T15:40:28+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\">\n\t<meta name=\"twitter:data1\" content=\"6 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"ECP - Enterprise Conversation Planning\",\"description\":\"Research on Digitalized Productivity Management - University of Seville\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/grupo.us.es\/ecplab\/en\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"http:\/\/grupo.us.es\/ecplab\/wp-content\/uploads\/elementor\/thumbs\/metamodel-p4plv73ti2v4x5rk3a8dqzzjwob1aj2uvgv01outy6.png\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#webpage\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns - ECP - Enterprise Conversation Planning\",\"isPartOf\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#primaryimage\"},\"datePublished\":\"2021-03-23T08:31:08+00:00\",\"dateModified\":\"2021-04-07T15:40:28+00:00\",\"description\":\"Description of the elements of our proposed graphic notation for defining every board-based template, their simbols, meanings and uses.\",\"breadcrumb\":{\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/en\/\",\"name\":\"Portada\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"url\":\"https:\/\/grupo.us.es\/ecplab\/graphic-notation-for-board-based-patterns\/\",\"name\":\"Graphic notation for board-based patterns\"}}]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222"}],"collection":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/comments?post=222"}],"version-history":[{"count":50,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions"}],"predecessor-version":[{"id":412,"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/pages\/222\/revisions\/412"}],"wp:attachment":[{"href":"https:\/\/grupo.us.es\/ecplab\/wp-json\/wp\/v2\/media?parent=222"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n\n\n\nWe are going to illustrate how this metamodel can be used to model boarddesigns by means of two examples. Figure 3.a shows a Scrum board design thatmodels three possible states of a project task (\u201cTo Do\u201d, \u201cDoing\u201d and \u201cDone\u201d) bymeans of threeLists(depicted as rectangles). They areTask listsbecausethey store cards that represent tasks. We represent it with a tick in the upper-left corner of each list. In this board, there is clearly aSemantic precedencedefined between \u201cTo Do\u201d and \u201cDoing\u201d, and between \u201cDoing\u201d and \u201cDone.\u201d Thisis depicted by means of a dashed arrow that links the two corresponding lists.Finally, when using the board, cards will move between the lists to signal that wehave started performing a task (move from \u201cTo Do\u201d to \u201cDoing\u201d) and that we havefinished a task (move from \u201cDoing\u201d to \u201cDone\u201d). Therefore, there is aCard flowbetween the three lists, which is represented by means of a rectangle that groupsthem. An icon at the bottom of the rectangle indicates the type ofCard Flow,which can be either free, precedence, or complex (represented by a tilde, an arrow, or an asterisk, respectively). In this case, the movement will be according tothe semantic precedence defined by the context of the problem.<\/p>\n\n\n\n
The second example (Figure 3.b) depicts a board design to organize infor-mation related to a trip. There are four lists (\u201cTravel & Hotel\u201d, \u201cPlaces to see\u201d,\u201cFood\u201d, and \u201cTransport\u201d) that contain information or resources, as indicated bythe document icon in the upper left corner of each list. In this case, lists areindependent of each other, so there is no semantic precedence between them.Furthermore, cards do not flow between lists. Instead, this board design includessome default cards as examples of the information that can be added in two ofthe four lists (\u201cPlaces to see\u201d and \u201cTransport\u201d). They are represented by meansof rectangles inside the list.<\/p>\n\n\n\n
It is important to note that, except for the name of the lists and the default cards contained in them, all the information about the board designs described above is currently specified in natural language in the description of the template or some predefined cards with information about how to use the board. Therefore, one advantage of the metamodel is that it makes this information explicit in a structured way, and hence, it can be used as a foundation to automate parts of its management like the card flow.<\/p>\n","_en_post_name":"graphic-notation-for-board-based-patterns","_en_post_excerpt":"","_en_post_title":"Graphic notation for board-based patterns","edit_language":"en"},"yoast_head":"\n