Reutilización de requisitos de usuario: el modelo mecano
Los requisitos de un Sistema de Informaci ́on se presentan de muy diversas formas. Sualmacenamiento en un repositorio y las relaciones entre s ́ı y con otros elementos re-utilizables pueden condicionar el ́exito o fracaso de todo un programa de reutilizaci ́on.Es necesario introducir un grado m ́ıni...
- Autores:
-
Laguna, Miguel A.
García Peñalvo, Francisco José
López, Óscar
- Tipo de recurso:
- Trabajo de grado de pregrado
- Fecha de publicación:
- 2002
- Institución:
- Universidad Autónoma de Bucaramanga - UNAB
- Repositorio:
- Repositorio UNAB
- Idioma:
- spa
- OAI Identifier:
- oai:repository.unab.edu.co:20.500.12749/9058
- Acceso en línea:
- http://hdl.handle.net/20.500.12749/9058
- Palabra clave:
- Innovaciones tecnológicas
Ciencia de los computadores
Desarrollo de tecnología
Ingeniería de sistemas
Investigaciones
Tecnologías de la información y las comunicaciones
TIC´s
Technological innovations
Computer science
Technology development
Systems engineering
Investigations
Information and communication technologies
ICT's
Requirements reuse
Meccano model
Innovaciones tecnológicas
Ciencias de la computación
Desarrollo tecnológico
Ingeniería de sistemas
Reutilización de requisitos
Modelo de mecano
- Rights
- License
- Derechos de autor 2002 Revista Colombiana de Computación
id |
UNAB2_e54d528e0cd89822f8b074a4be1ebc3b |
---|---|
oai_identifier_str |
oai:repository.unab.edu.co:20.500.12749/9058 |
network_acronym_str |
UNAB2 |
network_name_str |
Repositorio UNAB |
repository_id_str |
|
dc.title.none.fl_str_mv |
Reutilización de requisitos de usuario: el modelo mecano |
dc.title.translated.eng.fl_str_mv |
Reuse of User Requirements: The Mecano model |
title |
Reutilización de requisitos de usuario: el modelo mecano |
spellingShingle |
Reutilización de requisitos de usuario: el modelo mecano Innovaciones tecnológicas Ciencia de los computadores Desarrollo de tecnología Ingeniería de sistemas Investigaciones Tecnologías de la información y las comunicaciones TIC´s Technological innovations Computer science Technology development Systems engineering Investigations Information and communication technologies ICT's Requirements reuse Meccano model Innovaciones tecnológicas Ciencias de la computación Desarrollo tecnológico Ingeniería de sistemas Reutilización de requisitos Modelo de mecano |
title_short |
Reutilización de requisitos de usuario: el modelo mecano |
title_full |
Reutilización de requisitos de usuario: el modelo mecano |
title_fullStr |
Reutilización de requisitos de usuario: el modelo mecano |
title_full_unstemmed |
Reutilización de requisitos de usuario: el modelo mecano |
title_sort |
Reutilización de requisitos de usuario: el modelo mecano |
dc.creator.fl_str_mv |
Laguna, Miguel A. García Peñalvo, Francisco José López, Óscar |
dc.contributor.author.spa.fl_str_mv |
Laguna, Miguel A. García Peñalvo, Francisco José López, Óscar |
dc.contributor.illustrator.spa.fl_str_mv |
Laguna, Miguel A. [0000-0001-9107-749X] |
dc.contributor.googlescholar.spa.fl_str_mv |
Laguna, Miguel A. [d1iPS-0AAAAJ] |
dc.contributor.googlescholar.none.fl_str_mv |
García Peñalvo, Francisco José [dpYhOkMAAAAJ] |
dc.contributor.orcid.none.fl_str_mv |
García Peñalvo, Francisco José [0000-0001-9987-5584] Laguna, Miguel A. [0000-0001-9107-749X] |
dc.contributor.researchgate.none.fl_str_mv |
García Peñalvo, Francisco José [Francisco-Garcia-Penalvo] |
dc.subject.none.fl_str_mv |
Innovaciones tecnológicas Ciencia de los computadores Desarrollo de tecnología Ingeniería de sistemas Investigaciones Tecnologías de la información y las comunicaciones TIC´s |
topic |
Innovaciones tecnológicas Ciencia de los computadores Desarrollo de tecnología Ingeniería de sistemas Investigaciones Tecnologías de la información y las comunicaciones TIC´s Technological innovations Computer science Technology development Systems engineering Investigations Information and communication technologies ICT's Requirements reuse Meccano model Innovaciones tecnológicas Ciencias de la computación Desarrollo tecnológico Ingeniería de sistemas Reutilización de requisitos Modelo de mecano |
dc.subject.keywords.eng.fl_str_mv |
Technological innovations Computer science Technology development Systems engineering Investigations Information and communication technologies ICT's Requirements reuse Meccano model |
dc.subject.lemb.spa.fl_str_mv |
Innovaciones tecnológicas Ciencias de la computación Desarrollo tecnológico |
dc.subject.lemb.eng.fl_str_mv |
Ingeniería de sistemas |
dc.subject.proposal.spa.fl_str_mv |
Reutilización de requisitos Modelo de mecano |
description |
Los requisitos de un Sistema de Informaci ́on se presentan de muy diversas formas. Sualmacenamiento en un repositorio y las relaciones entre s ́ı y con otros elementos re-utilizables pueden condicionar el ́exito o fracaso de todo un programa de reutilizaci ́on.Es necesario introducir un grado m ́ınimo de normalizaci ́on en los requisitos para quepuedan ser realmente reutilizables, lo que se consigue inicialmente mediante la uti-lizaci ́on de patrones. Por otro lado, es preciso obtener conjuntos consistentes de req-uisitos relacionados con elementos reutilizables de otros niveles de abstracci ́on paraobtener una interfaz externa de reutilizaci ́on de elementos m ́as complejos. Por ́ultimo,se proponen gu ́ıas para encontrar pautas comunes a distintos elementos y obtener req-uisitos gen ́ericos adaptables mediante parametrizaci ́on a m ́ultiples situaciones (lo queimplica parametrizaci ́on de los elementos de dise ̃no o implementaci ́on relacionados).En este art ́ıculo se avanzan soluciones a estos problemas, basadas en la experiencia conrepositorios. |
publishDate |
2002 |
dc.date.issued.none.fl_str_mv |
2002-12-01 |
dc.date.accessioned.none.fl_str_mv |
2020-10-27T00:21:28Z |
dc.date.available.none.fl_str_mv |
2020-10-27T00:21:28Z |
dc.type.coar.fl_str_mv |
http://purl.org/coar/resource_type/c_2df8fbb1 |
dc.type.driver.none.fl_str_mv |
info:eu-repo/semantics/article |
dc.type.local.spa.fl_str_mv |
Artículo |
dc.type.coar.none.fl_str_mv |
http://purl.org/coar/resource_type/c_7a1f |
dc.type.redcol.none.fl_str_mv |
http://purl.org/redcol/resource_type/CJournalArticle |
format |
http://purl.org/coar/resource_type/c_7a1f |
dc.identifier.issn.none.fl_str_mv |
2539-2115 1657-2831 |
dc.identifier.uri.none.fl_str_mv |
http://hdl.handle.net/20.500.12749/9058 |
dc.identifier.instname.spa.fl_str_mv |
instname:Universidad Autónoma de Bucaramanga UNAB |
dc.identifier.repourl.none.fl_str_mv |
repourl:https://repository.unab.edu.co |
identifier_str_mv |
2539-2115 1657-2831 instname:Universidad Autónoma de Bucaramanga UNAB repourl:https://repository.unab.edu.co |
url |
http://hdl.handle.net/20.500.12749/9058 |
dc.language.iso.spa.fl_str_mv |
spa |
language |
spa |
dc.relation.none.fl_str_mv |
https://revistas.unab.edu.co/index.php/rcc/article/view/1102/1074 |
dc.relation.uri.none.fl_str_mv |
https://revistas.unab.edu.co/index.php/rcc/article/view/1102 |
dc.relation.references.none.fl_str_mv |
W.M.P. van der Aalst. Three Good reasons for Using a Petri-net-based Workflow ManagementSystem. InProceedings of the International Working Conference on Information and ProcessIntegration in Enterprises (IPIC’96), pages 179–201, 1996. Raquel Anaya.Desarrollo y gesti ́on de componentes reutilizables en el marco de Oasis.PhDthesis, Universidad Polit ́ecnica de Valencia, 1999. G. Booch, J. Rumbaugh, and I. Jacobson.The Unified Modeling Language User Guide.Addison–Wesley, 1999. J. W. Brackett. Software Requirements. Curriculum Module SEI–CM–19–1.2, Software Engi-neering Institute, Carnegie Mellon University, 1990. http://www.sei.cmu.edu. Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal.Pat-tern Oriented Software Architecture: A System of Patterns. John Wiley & Sons, 1996. Peter Clark and Bruce Porter. Building Concept Representations from Reusable Components.InProceedings of theAAAI’97, pages 369–376, 1997. Jacob L. Cybulski. Patterns in Software Requirements Reuse. InProceedings of 3rd AustralianConference on Requirements Engineering ACRE’98, Deakin University, Geelong, Australia,pages 135–153, 1998. Oscar D ́ıaz and Juan Jos ́eRodr ́ıguez. Change case analysis.Journal of Object-Oriented Pro-gramming (JOOP), 12(9):9–15,48, February 2000. A. Dur ́an, B. Bern ́ardez, A. Ruiz, and M. Toro. A Requirements Elicitation Approach Basedin Templates and Patterns. InWER’99 Proceedings, Buenos Aires, 1999. A. Finkelstein. Re–use of Formatted Requirements Specifications.Software EngineeringJour-nal, 3(5):186–197, May 1998. W. Frakes and S. Isoda. Success factors of systematic reuse.IEEE Software, 11(5):15–18,September 1994. E. Gamma, R. Helm, R. Johnson, and J. Vlissides.Design Patterns: Elements of ReusableObject-Oriented Software. Addison-Wesley, 1995. Francisco J. Garc ́ıa.Modelo de Reutilizaci ́on Soportado por Estructuras Complejas de Reuti-lizaci ́on Denominadas Mecanos. PhD thesis, Universidad de Salamanca, 2000. Francisco J. Garc ́ıa, Juan M. Corchado, and Miguel A. Laguna. CBR Applied to Developmentwith Reuse Based on mecanos. InProceedings of the 13th International Conference on SoftwareEngineering and Knowledge Engineering, june 13-15, 2001. Buenos Aires, 2001. C. Goti. A business classification for business rules. Technical Report TR03.563, IBM, SantaTeresa Lab., San Jos ́e, EEUU, 1994. Martin L. Griss, John Favaro, and Massimo D’Alessandro. Integrating feature modeling withRSEB. InProceedings of the Fifth International Conference on Software Reuse (ICSR-5),pages 76–85, 2-5 June, 1998. Victoria, B. C., Canada, June 1998. IEEE Computer Society,IEEE Press I. Jacobson. Object Oriented Development in an Industrial Environment. InOOPSLA -Conference proceedings on Object-Oriented Programming Systems, Languages and Applications,pages 183–191, Orlando, FL USA, ACM, 1987. I. Jacobson, M. Christerson, P. Jonsson, and G. ̈Overgaard.Object–Oriented Software Engi-neering: A Use Case Driven Approach. Addison–Wesley, 4aedition, 1993. Ivar Jacobson, Martin Griss, and Patrik Jonsson.Software Reuse. Architecture, Process andOrganization for Bussiness Success. ACM Press. Addison-Wesley, 1997.. K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak, and A. S. Peterson. Feature-Oriented Do-main Analysis (FODA). Feasibility study. Technical Report CMU/SEI-90-TR21 (ESD-90-TR-222), Software Engineering Institute, Carnegie-Mellon University, Pittsburgh, Pennsylvania15213, November 1990. Miguel A. Laguna, Jos ́eM.Marqu ́es, and Francisco J. Garc ́ıa. A user requirements elicitationtool.ACM SIGSOFT Software Engineering Notes, 26(2):35–37, March 2001. W. Lam. Achieving Requirements Reuse: A Domain-Specific Approach from Avionics.TheJournal of Systems and Software, 38(3):197–209, September 1997. K. Lee, KC. Kang, W. Chae, and BW. Choi. Feature-based approach to object-orientedengineering of applications for reuse.Software-Practice and Experience, 30(9):1025–1046, July2000 W.J. Lee, S.D. Cha, and Y.R. Kwon. Integration and Analysis of Use Cases Using Mod-ular Petri Nets in Requirement Engineering.IEEE Transactions on Software Engineering,24(12):1115–1130, December 1998. P. Loucopoulos. Bussiness Rules Modelling: Conceptual Modelling and Object-Oriented Spec-ifications. InProceedings of the IFIP Conference, TC8/WG8.1, 1991. M. Lowry and R. Duran.The Handbook of Artificial Intelligence, chapter Knowledge-BasedSoftware Engineering, pages 241–322. Addison-Wesley, 1989. Oscar L ́opez, Miguel Angel Laguna, and Jos ́e Manuel Marqu ́es. Generaci ́on Autom ́atica deCasos de Uso para Desarrollo de Software Basado en Reutilizaci ́on. InActas de las V Jornadasde Ingenier ́ıa del Software y Bases de Datos, pages 89–101, Valladolid, November 2000 Oscar L ́opez, Miguel Angel Laguna, and Jos ́eManuelMarqu ́es. Reutilizaci ́on del Software apartir de Requisitos Funcionales en el Modelo de Mecano: Comparaci ́on de Escenarios. InActas de IDEAS 2001,SanJos ́e, Costa Rica, April 2001. M. Mannion, H. Kaindl, and J. Wheadon. Reusing Single System Requirements from Ap-plication Family Requirements. InProceedings of the International Conference on SoftwareEngineering, 1999. T. Moriarty. Business rule analysis.Database Programming & Design, 6(4):66–69, 1993 Klaus Pohl. Requirements engineering: An overview. Technical Report TR 96/2, CREWS,1996. Jeffrey S. Poulin. Integrated support for software reuse in computer-aided software engineering(CASE).ACM SIGSOFT Software Engineering Notes, 18(4):75–82, 1993. Rub ́en Prieto-D ́ıaz. Implementing faceted classification for software reuse.Communications ofthe ACM, 34(5):89–97, May 1991. P. Sawyer and G. Kontoya. Software Requirements, in Guide to the Software EngineeringBody of Knowledge, Version 0.95. Technical report, May 2001. http://www.swebok.org. Sema Group.Euroware User’s Manual. Sema Group, 1996. A. Silva. Across Version/Variant requirement traceability in avionics software developmentand testing. InProceedings of the 2nd European Reuse Workshop (ERW’98), pages 179–198,November, 4-6, 1998. Madrid (Spain), November 1998. European Software Institute (ESI). M. Silva.Las Redes de Petri en la Inform ́atica y la Autom ́atica. Editorial AC, Madrid, 1985. Mark Simos, Dick Creps, Carol Klingler, Larry Levine, and Dean Allemang. Organizationdomain modeling (ODM) guidebook - version 2.0. Technical Report STARS-VC-A025/001/00,Lockheed Martin Tactical Defense Systems, 9255 Wellington Road Manassas, VA 22110-4121,June 1996. Alistair G. Sutcliffe, Neil A. M. Maiden, Shailey Minocha, and Darrel Manuel. Support-ing scenario-based requirements engineering.IEEE Transactions on Software Engineering,24(12):1072–1088, December 1998. J. B. Warmer and A. G. Kleppe.The Object Constraint Language: Precise Modeling withUML. Addison–Wesley, 1999. WfMC.Workflow management coalition terminology and glosary.Tech-nicalReportWFMC-TC-1011,WorkflowManagementCoalition,Brussels,http://www.aiim.org/wfmc/standards/docs/glossy3.pdf, 1996. |
dc.rights.none.fl_str_mv |
Derechos de autor 2002 Revista Colombiana de Computación |
dc.rights.coar.fl_str_mv |
http://purl.org/coar/access_right/c_abf2 |
dc.rights.uri.*.fl_str_mv |
http://creativecommons.org/licenses/by-nc-sa/4.0/ |
dc.rights.uri.none.fl_str_mv |
http://creativecommons.org/licenses/by-nc-nd/2.5/co/ |
dc.rights.creativecommons.*.fl_str_mv |
Atribución-NoComercial-SinDerivadas 2.5 Colombia |
rights_invalid_str_mv |
Derechos de autor 2002 Revista Colombiana de Computación http://creativecommons.org/licenses/by-nc-sa/4.0/ http://creativecommons.org/licenses/by-nc-nd/2.5/co/ Atribución-NoComercial-SinDerivadas 2.5 Colombia http://purl.org/coar/access_right/c_abf2 |
dc.format.mimetype.spa.fl_str_mv |
application/pdf |
dc.publisher.none.fl_str_mv |
Universidad Autónoma de Bucaramanga UNAB |
publisher.none.fl_str_mv |
Universidad Autónoma de Bucaramanga UNAB |
dc.source.none.fl_str_mv |
Revista Colombiana de Computación; Vol. 3 Núm. 2 (2002): Revista Colombiana de Computación; 1-19 |
institution |
Universidad Autónoma de Bucaramanga - UNAB |
bitstream.url.fl_str_mv |
https://repository.unab.edu.co/bitstream/20.500.12749/9058/2/1102-Texto%20del%20art%c3%adculo-3230-1-10-20100728%20%281%29.pdf.jpg https://repository.unab.edu.co/bitstream/20.500.12749/9058/1/1102-Texto%20del%20art%c3%adculo-3230-1-10-20100728%20%281%29.pdf |
bitstream.checksum.fl_str_mv |
84eab7ce62b803a59019d188d1586c8a 138b9e8e6045d5ed97dd90f9d9e9493a |
bitstream.checksumAlgorithm.fl_str_mv |
MD5 MD5 |
repository.name.fl_str_mv |
Repositorio Institucional | Universidad Autónoma de Bucaramanga - UNAB |
repository.mail.fl_str_mv |
repositorio@unab.edu.co |
_version_ |
1814277321507471360 |
spelling |
Laguna, Miguel A.f4490357-4aba-4eb7-9b04-2433186954b8García Peñalvo, Francisco Josédbacbf5f-2619-4db6-9213-1c09ba7726abLópez, Óscar257dcd48-347c-4458-8778-f440bc91c99cLaguna, Miguel A. [0000-0001-9107-749X]Laguna, Miguel A. [d1iPS-0AAAAJ]García Peñalvo, Francisco José [dpYhOkMAAAAJ]García Peñalvo, Francisco José [0000-0001-9987-5584]Laguna, Miguel A. [0000-0001-9107-749X]García Peñalvo, Francisco José [Francisco-Garcia-Penalvo]2020-10-27T00:21:28Z2020-10-27T00:21:28Z2002-12-012539-21151657-2831http://hdl.handle.net/20.500.12749/9058instname:Universidad Autónoma de Bucaramanga UNABrepourl:https://repository.unab.edu.coLos requisitos de un Sistema de Informaci ́on se presentan de muy diversas formas. Sualmacenamiento en un repositorio y las relaciones entre s ́ı y con otros elementos re-utilizables pueden condicionar el ́exito o fracaso de todo un programa de reutilizaci ́on.Es necesario introducir un grado m ́ınimo de normalizaci ́on en los requisitos para quepuedan ser realmente reutilizables, lo que se consigue inicialmente mediante la uti-lizaci ́on de patrones. Por otro lado, es preciso obtener conjuntos consistentes de req-uisitos relacionados con elementos reutilizables de otros niveles de abstracci ́on paraobtener una interfaz externa de reutilizaci ́on de elementos m ́as complejos. Por ́ultimo,se proponen gu ́ıas para encontrar pautas comunes a distintos elementos y obtener req-uisitos gen ́ericos adaptables mediante parametrizaci ́on a m ́ultiples situaciones (lo queimplica parametrizaci ́on de los elementos de dise ̃no o implementaci ́on relacionados).En este art ́ıculo se avanzan soluciones a estos problemas, basadas en la experiencia conrepositorios.The requirements of an Information System come of very diverse formats. Their stor-age in a repository and the relationships between them and with another reusableelements could condition the success or failure of a reuse program. It is necessary tointroduce a minimum degree of normalization in the requirements, so that they can bereally reusable. This is achieved initially by means of patterns. On the other hand,we must define consistent groups of requirements, related to reusable elements of otherabstraction levels, in order to obtain an external interface for the reuse of complexelements. Lastly, we propose a guide to find common rules to different elements andobtain generic requirements, adaptive by means of parameterization to multiple situ-ations (what imply parameterization of design and implementation elements). In thisarticle we advance solutions to these problems, based on the experience with reposito-ries.application/pdfspaUniversidad Autónoma de Bucaramanga UNABhttps://revistas.unab.edu.co/index.php/rcc/article/view/1102/1074https://revistas.unab.edu.co/index.php/rcc/article/view/1102W.M.P. van der Aalst. Three Good reasons for Using a Petri-net-based Workflow ManagementSystem. InProceedings of the International Working Conference on Information and ProcessIntegration in Enterprises (IPIC’96), pages 179–201, 1996.Raquel Anaya.Desarrollo y gesti ́on de componentes reutilizables en el marco de Oasis.PhDthesis, Universidad Polit ́ecnica de Valencia, 1999.G. Booch, J. Rumbaugh, and I. Jacobson.The Unified Modeling Language User Guide.Addison–Wesley, 1999.J. W. Brackett. Software Requirements. Curriculum Module SEI–CM–19–1.2, Software Engi-neering Institute, Carnegie Mellon University, 1990. http://www.sei.cmu.edu.Frank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal.Pat-tern Oriented Software Architecture: A System of Patterns. John Wiley & Sons, 1996.Peter Clark and Bruce Porter. Building Concept Representations from Reusable Components.InProceedings of theAAAI’97, pages 369–376, 1997.Jacob L. Cybulski. Patterns in Software Requirements Reuse. InProceedings of 3rd AustralianConference on Requirements Engineering ACRE’98, Deakin University, Geelong, Australia,pages 135–153, 1998.Oscar D ́ıaz and Juan Jos ́eRodr ́ıguez. Change case analysis.Journal of Object-Oriented Pro-gramming (JOOP), 12(9):9–15,48, February 2000.A. Dur ́an, B. Bern ́ardez, A. Ruiz, and M. Toro. A Requirements Elicitation Approach Basedin Templates and Patterns. InWER’99 Proceedings, Buenos Aires, 1999.A. Finkelstein. Re–use of Formatted Requirements Specifications.Software EngineeringJour-nal, 3(5):186–197, May 1998.W. Frakes and S. Isoda. Success factors of systematic reuse.IEEE Software, 11(5):15–18,September 1994.E. Gamma, R. Helm, R. Johnson, and J. Vlissides.Design Patterns: Elements of ReusableObject-Oriented Software. Addison-Wesley, 1995.Francisco J. Garc ́ıa.Modelo de Reutilizaci ́on Soportado por Estructuras Complejas de Reuti-lizaci ́on Denominadas Mecanos. PhD thesis, Universidad de Salamanca, 2000.Francisco J. Garc ́ıa, Juan M. Corchado, and Miguel A. Laguna. CBR Applied to Developmentwith Reuse Based on mecanos. InProceedings of the 13th International Conference on SoftwareEngineering and Knowledge Engineering, june 13-15, 2001. Buenos Aires, 2001.C. Goti. A business classification for business rules. Technical Report TR03.563, IBM, SantaTeresa Lab., San Jos ́e, EEUU, 1994.Martin L. Griss, John Favaro, and Massimo D’Alessandro. Integrating feature modeling withRSEB. InProceedings of the Fifth International Conference on Software Reuse (ICSR-5),pages 76–85, 2-5 June, 1998. Victoria, B. C., Canada, June 1998. IEEE Computer Society,IEEE PressI. Jacobson. Object Oriented Development in an Industrial Environment. InOOPSLA -Conference proceedings on Object-Oriented Programming Systems, Languages and Applications,pages 183–191, Orlando, FL USA, ACM, 1987.I. Jacobson, M. Christerson, P. Jonsson, and G. ̈Overgaard.Object–Oriented Software Engi-neering: A Use Case Driven Approach. Addison–Wesley, 4aedition, 1993.Ivar Jacobson, Martin Griss, and Patrik Jonsson.Software Reuse. Architecture, Process andOrganization for Bussiness Success. ACM Press. Addison-Wesley, 1997..K. C. Kang, S. G. Cohen, J. A. Hess, W. E. Novak, and A. S. Peterson. Feature-Oriented Do-main Analysis (FODA). Feasibility study. Technical Report CMU/SEI-90-TR21 (ESD-90-TR-222), Software Engineering Institute, Carnegie-Mellon University, Pittsburgh, Pennsylvania15213, November 1990.Miguel A. Laguna, Jos ́eM.Marqu ́es, and Francisco J. Garc ́ıa. A user requirements elicitationtool.ACM SIGSOFT Software Engineering Notes, 26(2):35–37, March 2001.W. Lam. Achieving Requirements Reuse: A Domain-Specific Approach from Avionics.TheJournal of Systems and Software, 38(3):197–209, September 1997.K. Lee, KC. Kang, W. Chae, and BW. Choi. Feature-based approach to object-orientedengineering of applications for reuse.Software-Practice and Experience, 30(9):1025–1046, July2000W.J. Lee, S.D. Cha, and Y.R. Kwon. Integration and Analysis of Use Cases Using Mod-ular Petri Nets in Requirement Engineering.IEEE Transactions on Software Engineering,24(12):1115–1130, December 1998.P. Loucopoulos. Bussiness Rules Modelling: Conceptual Modelling and Object-Oriented Spec-ifications. InProceedings of the IFIP Conference, TC8/WG8.1, 1991.M. Lowry and R. Duran.The Handbook of Artificial Intelligence, chapter Knowledge-BasedSoftware Engineering, pages 241–322. Addison-Wesley, 1989.Oscar L ́opez, Miguel Angel Laguna, and Jos ́e Manuel Marqu ́es. Generaci ́on Autom ́atica deCasos de Uso para Desarrollo de Software Basado en Reutilizaci ́on. InActas de las V Jornadasde Ingenier ́ıa del Software y Bases de Datos, pages 89–101, Valladolid, November 2000Oscar L ́opez, Miguel Angel Laguna, and Jos ́eManuelMarqu ́es. Reutilizaci ́on del Software apartir de Requisitos Funcionales en el Modelo de Mecano: Comparaci ́on de Escenarios. InActas de IDEAS 2001,SanJos ́e, Costa Rica, April 2001.M. Mannion, H. Kaindl, and J. Wheadon. Reusing Single System Requirements from Ap-plication Family Requirements. InProceedings of the International Conference on SoftwareEngineering, 1999.T. Moriarty. Business rule analysis.Database Programming & Design, 6(4):66–69, 1993Klaus Pohl. Requirements engineering: An overview. Technical Report TR 96/2, CREWS,1996.Jeffrey S. Poulin. Integrated support for software reuse in computer-aided software engineering(CASE).ACM SIGSOFT Software Engineering Notes, 18(4):75–82, 1993.Rub ́en Prieto-D ́ıaz. Implementing faceted classification for software reuse.Communications ofthe ACM, 34(5):89–97, May 1991.P. Sawyer and G. Kontoya. Software Requirements, in Guide to the Software EngineeringBody of Knowledge, Version 0.95. Technical report, May 2001. http://www.swebok.org.Sema Group.Euroware User’s Manual. Sema Group, 1996.A. Silva. Across Version/Variant requirement traceability in avionics software developmentand testing. InProceedings of the 2nd European Reuse Workshop (ERW’98), pages 179–198,November, 4-6, 1998. Madrid (Spain), November 1998. European Software Institute (ESI).M. Silva.Las Redes de Petri en la Inform ́atica y la Autom ́atica. Editorial AC, Madrid, 1985.Mark Simos, Dick Creps, Carol Klingler, Larry Levine, and Dean Allemang. Organizationdomain modeling (ODM) guidebook - version 2.0. Technical Report STARS-VC-A025/001/00,Lockheed Martin Tactical Defense Systems, 9255 Wellington Road Manassas, VA 22110-4121,June 1996.Alistair G. Sutcliffe, Neil A. M. Maiden, Shailey Minocha, and Darrel Manuel. Support-ing scenario-based requirements engineering.IEEE Transactions on Software Engineering,24(12):1072–1088, December 1998.J. B. Warmer and A. G. Kleppe.The Object Constraint Language: Precise Modeling withUML. Addison–Wesley, 1999.WfMC.Workflow management coalition terminology and glosary.Tech-nicalReportWFMC-TC-1011,WorkflowManagementCoalition,Brussels,http://www.aiim.org/wfmc/standards/docs/glossy3.pdf, 1996.Derechos de autor 2002 Revista Colombiana de Computaciónhttp://creativecommons.org/licenses/by-nc-sa/4.0/http://creativecommons.org/licenses/by-nc-nd/2.5/co/Atribución-NoComercial-SinDerivadas 2.5 Colombiahttp://purl.org/coar/access_right/c_abf2Revista Colombiana de Computación; Vol. 3 Núm. 2 (2002): Revista Colombiana de Computación; 1-19Innovaciones tecnológicasCiencia de los computadoresDesarrollo de tecnologíaIngeniería de sistemasInvestigacionesTecnologías de la información y las comunicacionesTIC´sTechnological innovationsComputer scienceTechnology developmentSystems engineeringInvestigationsInformation and communication technologiesICT'sRequirements reuseMeccano modelInnovaciones tecnológicasCiencias de la computaciónDesarrollo tecnológicoIngeniería de sistemasReutilización de requisitosModelo de mecanoReutilización de requisitos de usuario: el modelo mecanoReuse of User Requirements: The Mecano modelinfo:eu-repo/semantics/articleArtículohttp://purl.org/coar/resource_type/c_7a1fhttp://purl.org/coar/resource_type/c_2df8fbb1http://purl.org/redcol/resource_type/CJournalArticleTHUMBNAIL1102-Texto del artículo-3230-1-10-20100728 (1).pdf.jpg1102-Texto del artículo-3230-1-10-20100728 (1).pdf.jpgIM Thumbnailimage/jpeg9080https://repository.unab.edu.co/bitstream/20.500.12749/9058/2/1102-Texto%20del%20art%c3%adculo-3230-1-10-20100728%20%281%29.pdf.jpg84eab7ce62b803a59019d188d1586c8aMD52open accessORIGINAL1102-Texto del artículo-3230-1-10-20100728 (1).pdf1102-Texto del artículo-3230-1-10-20100728 (1).pdfArtículoapplication/pdf726874https://repository.unab.edu.co/bitstream/20.500.12749/9058/1/1102-Texto%20del%20art%c3%adculo-3230-1-10-20100728%20%281%29.pdf138b9e8e6045d5ed97dd90f9d9e9493aMD51open access20.500.12749/9058oai:repository.unab.edu.co:20.500.12749/90582022-11-24 19:58:55.58open accessRepositorio Institucional | Universidad Autónoma de Bucaramanga - UNABrepositorio@unab.edu.co |