Robustness Diagram: a bridge between business modelling and system design
Autor(a) principal: | |
---|---|
Data de Publicação: | 2001 |
Outros Autores: | , |
Tipo de documento: | Relatório |
Idioma: | eng |
Título da fonte: | Repositório Institucional da UFRJ |
Texto Completo: | http://hdl.handle.net/11422/1900 |
Resumo: | Use case driven development has proven being a good approach for capturing problem semantics in an orderly, structured description. However, it specifies an abstraction beyond practicity to guide system design process. Robustness diagrams are a simple solution for drafting a more formal description for business modelling. This very simplicity may, however, detract its value, falling short of capturing the rich business semantics. Stereotyping is the essence behind its robustness diagram mechanics. Symbols convey the abstraction necessary to catch the model semantics. Increasing the number of stereotypes we can achieve a closer match from model to design. Rules carefully stated for robustness diagram can help to translate highleveI information into well-behaved and predictable symbolic descriptions. This enhancement to robustness diagram helps to patch the gap between abstract model and project into a paved continuum. It has been used to train programmers to extract working and consistent systems out of use case specifications. |
id |
UFRJ_1920dd50c40f3580ef385800d1774595 |
---|---|
oai_identifier_str |
oai:pantheon.ufrj.br:11422/1900 |
network_acronym_str |
UFRJ |
network_name_str |
Repositório Institucional da UFRJ |
repository_id_str |
|
spelling |
Robustness Diagram: a bridge between business modelling and system designProjeto de sistemasModelagem de negóciosCNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAOUse case driven development has proven being a good approach for capturing problem semantics in an orderly, structured description. However, it specifies an abstraction beyond practicity to guide system design process. Robustness diagrams are a simple solution for drafting a more formal description for business modelling. This very simplicity may, however, detract its value, falling short of capturing the rich business semantics. Stereotyping is the essence behind its robustness diagram mechanics. Symbols convey the abstraction necessary to catch the model semantics. Increasing the number of stereotypes we can achieve a closer match from model to design. Rules carefully stated for robustness diagram can help to translate highleveI information into well-behaved and predictable symbolic descriptions. This enhancement to robustness diagram helps to patch the gap between abstract model and project into a paved continuum. It has been used to train programmers to extract working and consistent systems out of use case specifications.BrasilInstituto Tércio Pacitti de Aplicações e Pesquisas Computacionais2017-05-08T15:13:37Z2023-12-21T03:00:54Z2001-12-30info:eu-repo/semantics/publishedVersioninfo:eu-repo/semantics/reportPais, A. P. V.; Oliveira, C. E. T.; Leite, P. H. P. M. Robustness diagram: a bridge between business modelling and system design. Rio de Janeiro: NCE/UFRJ. 2001. 7 p. (Relatório Técnico 07/01)http://hdl.handle.net/11422/1900engRelatório Técnico NCEPais, Ana Paula ValenteOliveira, Carlo Emmanoel Tolla deLeite, Paulo Henrique P. Martinsinfo:eu-repo/semantics/openAccessreponame:Repositório Institucional da UFRJinstname:Universidade Federal do Rio de Janeiro (UFRJ)instacron:UFRJ2023-12-21T03:00:54Zoai:pantheon.ufrj.br:11422/1900Repositório InstitucionalPUBhttp://www.pantheon.ufrj.br/oai/requestpantheon@sibi.ufrj.bropendoar:2023-12-21T03:00:54Repositório Institucional da UFRJ - Universidade Federal do Rio de Janeiro (UFRJ)false |
dc.title.none.fl_str_mv |
Robustness Diagram: a bridge between business modelling and system design |
title |
Robustness Diagram: a bridge between business modelling and system design |
spellingShingle |
Robustness Diagram: a bridge between business modelling and system design Pais, Ana Paula Valente Projeto de sistemas Modelagem de negócios CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO |
title_short |
Robustness Diagram: a bridge between business modelling and system design |
title_full |
Robustness Diagram: a bridge between business modelling and system design |
title_fullStr |
Robustness Diagram: a bridge between business modelling and system design |
title_full_unstemmed |
Robustness Diagram: a bridge between business modelling and system design |
title_sort |
Robustness Diagram: a bridge between business modelling and system design |
author |
Pais, Ana Paula Valente |
author_facet |
Pais, Ana Paula Valente Oliveira, Carlo Emmanoel Tolla de Leite, Paulo Henrique P. Martins |
author_role |
author |
author2 |
Oliveira, Carlo Emmanoel Tolla de Leite, Paulo Henrique P. Martins |
author2_role |
author author |
dc.contributor.author.fl_str_mv |
Pais, Ana Paula Valente Oliveira, Carlo Emmanoel Tolla de Leite, Paulo Henrique P. Martins |
dc.subject.por.fl_str_mv |
Projeto de sistemas Modelagem de negócios CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO |
topic |
Projeto de sistemas Modelagem de negócios CNPQ::CIENCIAS EXATAS E DA TERRA::CIENCIA DA COMPUTACAO |
description |
Use case driven development has proven being a good approach for capturing problem semantics in an orderly, structured description. However, it specifies an abstraction beyond practicity to guide system design process. Robustness diagrams are a simple solution for drafting a more formal description for business modelling. This very simplicity may, however, detract its value, falling short of capturing the rich business semantics. Stereotyping is the essence behind its robustness diagram mechanics. Symbols convey the abstraction necessary to catch the model semantics. Increasing the number of stereotypes we can achieve a closer match from model to design. Rules carefully stated for robustness diagram can help to translate highleveI information into well-behaved and predictable symbolic descriptions. This enhancement to robustness diagram helps to patch the gap between abstract model and project into a paved continuum. It has been used to train programmers to extract working and consistent systems out of use case specifications. |
publishDate |
2001 |
dc.date.none.fl_str_mv |
2001-12-30 2017-05-08T15:13:37Z 2023-12-21T03:00:54Z |
dc.type.status.fl_str_mv |
info:eu-repo/semantics/publishedVersion |
dc.type.driver.fl_str_mv |
info:eu-repo/semantics/report |
format |
report |
status_str |
publishedVersion |
dc.identifier.uri.fl_str_mv |
Pais, A. P. V.; Oliveira, C. E. T.; Leite, P. H. P. M. Robustness diagram: a bridge between business modelling and system design. Rio de Janeiro: NCE/UFRJ. 2001. 7 p. (Relatório Técnico 07/01) http://hdl.handle.net/11422/1900 |
identifier_str_mv |
Pais, A. P. V.; Oliveira, C. E. T.; Leite, P. H. P. M. Robustness diagram: a bridge between business modelling and system design. Rio de Janeiro: NCE/UFRJ. 2001. 7 p. (Relatório Técnico 07/01) |
url |
http://hdl.handle.net/11422/1900 |
dc.language.iso.fl_str_mv |
eng |
language |
eng |
dc.relation.none.fl_str_mv |
Relatório Técnico NCE |
dc.rights.driver.fl_str_mv |
info:eu-repo/semantics/openAccess |
eu_rights_str_mv |
openAccess |
dc.publisher.none.fl_str_mv |
Brasil Instituto Tércio Pacitti de Aplicações e Pesquisas Computacionais |
publisher.none.fl_str_mv |
Brasil Instituto Tércio Pacitti de Aplicações e Pesquisas Computacionais |
dc.source.none.fl_str_mv |
reponame:Repositório Institucional da UFRJ instname:Universidade Federal do Rio de Janeiro (UFRJ) instacron:UFRJ |
instname_str |
Universidade Federal do Rio de Janeiro (UFRJ) |
instacron_str |
UFRJ |
institution |
UFRJ |
reponame_str |
Repositório Institucional da UFRJ |
collection |
Repositório Institucional da UFRJ |
repository.name.fl_str_mv |
Repositório Institucional da UFRJ - Universidade Federal do Rio de Janeiro (UFRJ) |
repository.mail.fl_str_mv |
pantheon@sibi.ufrj.br |
_version_ |
1815455963047526400 |