Reutilización de requisitos de usuario: el modelo mecano

Vista sencilla de ítem
dc.contributor.authorLaguna, Miguel A.spa
dc.contributor.authorGarcía Peñalvo, Francisco Joséspa
dc.contributor.authorLópez, Óscarspa
dc.contributor.googlescholarLaguna, Miguel A. [d1iPS-0AAAAJ]spa
dc.contributor.googlescholarGarcía Peñalvo, Francisco José [dpYhOkMAAAAJ]
dc.contributor.illustratorLaguna, Miguel A. [0000-0001-9107-749X]spa
dc.contributor.orcidGarcía Peñalvo, Francisco José [0000-0001-9987-5584]
dc.contributor.orcidLaguna, Miguel A. [0000-0001-9107-749X]
dc.contributor.researchgateGarcía Peñalvo, Francisco José [Francisco-Garcia-Penalvo]
dc.date.accessioned2020-10-27T00:21:28Z
dc.date.available2020-10-27T00:21:28Z
dc.date.issued2002-12-01
dc.description.abstractLos 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.spa
dc.description.abstractenglishThe 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.eng
dc.format.mimetypeapplication/pdfspa
dc.identifier.instnameinstname:Universidad Autónoma de Bucaramanga UNABspa
dc.identifier.issn2539-2115
dc.identifier.issn1657-2831
dc.identifier.repourlrepourl:https://repository.unab.edu.co
dc.identifier.urihttp://hdl.handle.net/20.500.12749/9058
dc.language.isospaspa
dc.publisherUniversidad Autónoma de Bucaramanga UNAB
dc.relationhttps://revistas.unab.edu.co/index.php/rcc/article/view/1102/1074
dc.relation.referencesW.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.
dc.relation.referencesRaquel Anaya.Desarrollo y gesti ́on de componentes reutilizables en el marco de Oasis.PhDthesis, Universidad Polit ́ecnica de Valencia, 1999.
dc.relation.referencesG. Booch, J. Rumbaugh, and I. Jacobson.The Unified Modeling Language User Guide.Addison–Wesley, 1999.
dc.relation.referencesJ. W. Brackett. Software Requirements. Curriculum Module SEI–CM–19–1.2, Software Engi-neering Institute, Carnegie Mellon University, 1990. http://www.sei.cmu.edu.
dc.relation.referencesFrank Buschmann, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal.Pat-tern Oriented Software Architecture: A System of Patterns. John Wiley & Sons, 1996.
dc.relation.referencesPeter Clark and Bruce Porter. Building Concept Representations from Reusable Components.InProceedings of theAAAI’97, pages 369–376, 1997.
dc.relation.referencesJacob L. Cybulski. Patterns in Software Requirements Reuse. InProceedings of 3rd AustralianConference on Requirements Engineering ACRE’98, Deakin University, Geelong, Australia,pages 135–153, 1998.
dc.relation.referencesOscar D ́ıaz and Juan Jos ́eRodr ́ıguez. Change case analysis.Journal of Object-Oriented Pro-gramming (JOOP), 12(9):9–15,48, February 2000.
dc.relation.referencesA. Dur ́an, B. Bern ́ardez, A. Ruiz, and M. Toro. A Requirements Elicitation Approach Basedin Templates and Patterns. InWER’99 Proceedings, Buenos Aires, 1999.
dc.relation.referencesA. Finkelstein. Re–use of Formatted Requirements Specifications.Software EngineeringJour-nal, 3(5):186–197, May 1998.
dc.relation.referencesW. Frakes and S. Isoda. Success factors of systematic reuse.IEEE Software, 11(5):15–18,September 1994.
dc.relation.referencesE. Gamma, R. Helm, R. Johnson, and J. Vlissides.Design Patterns: Elements of ReusableObject-Oriented Software. Addison-Wesley, 1995.
dc.relation.referencesFrancisco J. Garc ́ıa.Modelo de Reutilizaci ́on Soportado por Estructuras Complejas de Reuti-lizaci ́on Denominadas Mecanos. PhD thesis, Universidad de Salamanca, 2000.
dc.relation.referencesFrancisco 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.
dc.relation.referencesC. Goti. A business classification for business rules. Technical Report TR03.563, IBM, SantaTeresa Lab., San Jos ́e, EEUU, 1994.
dc.relation.referencesMartin 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
dc.relation.referencesI. 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.
dc.relation.referencesI. Jacobson, M. Christerson, P. Jonsson, and G. ̈Overgaard.Object–Oriented Software Engi-neering: A Use Case Driven Approach. Addison–Wesley, 4aedition, 1993.
dc.relation.referencesIvar Jacobson, Martin Griss, and Patrik Jonsson.Software Reuse. Architecture, Process andOrganization for Bussiness Success. ACM Press. Addison-Wesley, 1997..
dc.relation.referencesK. 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.
dc.relation.referencesMiguel 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.
dc.relation.referencesW. Lam. Achieving Requirements Reuse: A Domain-Specific Approach from Avionics.TheJournal of Systems and Software, 38(3):197–209, September 1997.
dc.relation.referencesK. 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
dc.relation.referencesW.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.
dc.relation.referencesP. Loucopoulos. Bussiness Rules Modelling: Conceptual Modelling and Object-Oriented Spec-ifications. InProceedings of the IFIP Conference, TC8/WG8.1, 1991.
dc.relation.referencesM. Lowry and R. Duran.The Handbook of Artificial Intelligence, chapter Knowledge-BasedSoftware Engineering, pages 241–322. Addison-Wesley, 1989.
dc.relation.referencesOscar 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
dc.relation.referencesOscar 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.
dc.relation.referencesM. Mannion, H. Kaindl, and J. Wheadon. Reusing Single System Requirements from Ap-plication Family Requirements. InProceedings of the International Conference on SoftwareEngineering, 1999.
dc.relation.referencesT. Moriarty. Business rule analysis.Database Programming & Design, 6(4):66–69, 1993
dc.relation.referencesKlaus Pohl. Requirements engineering: An overview. Technical Report TR 96/2, CREWS,1996.
dc.relation.referencesJeffrey S. Poulin. Integrated support for software reuse in computer-aided software engineering(CASE).ACM SIGSOFT Software Engineering Notes, 18(4):75–82, 1993.
dc.relation.referencesRub ́en Prieto-D ́ıaz. Implementing faceted classification for software reuse.Communications ofthe ACM, 34(5):89–97, May 1991.
dc.relation.referencesP. 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.
dc.relation.referencesSema Group.Euroware User’s Manual. Sema Group, 1996.
dc.relation.referencesA. 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).
dc.relation.referencesM. Silva.Las Redes de Petri en la Inform ́atica y la Autom ́atica. Editorial AC, Madrid, 1985.
dc.relation.referencesMark 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.
dc.relation.referencesAlistair 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.
dc.relation.referencesJ. B. Warmer and A. G. Kleppe.The Object Constraint Language: Precise Modeling withUML. Addison–Wesley, 1999.
dc.relation.referencesWfMC.Workflow management coalition terminology and glosary.Tech-nicalReportWFMC-TC-1011,WorkflowManagementCoalition,Brussels,http://www.aiim.org/wfmc/standards/docs/glossy3.pdf, 1996.
dc.relation.urihttps://revistas.unab.edu.co/index.php/rcc/article/view/1102
dc.rightsDerechos de autor 2002 Revista Colombiana de Computación
dc.rights.accessrightsinfo:eu-repo/semantics/openAccessspa
dc.rights.creativecommonsAtribución-NoComercial-SinDerivadas 2.5 Colombia*
dc.rights.urihttp://creativecommons.org/licenses/by-nc-sa/4.0/*
dc.rights.urihttp://creativecommons.org/licenses/by-nc-nd/2.5/co/
dc.sourceRevista Colombiana de Computación; Vol. 3 Núm. 2 (2002): Revista Colombiana de Computación; 1-19
dc.subjectInnovaciones tecnológicas
dc.subjectCiencia de los computadores
dc.subjectDesarrollo de tecnología
dc.subjectIngeniería de sistemas
dc.subjectInvestigaciones
dc.subjectTecnologías de la información y las comunicaciones
dc.subjectTIC´s
dc.subject.keywordsTechnological innovationseng
dc.subject.keywordsComputer scienceeng
dc.subject.keywordsTechnology developmenteng
dc.subject.keywordsSystems engineeringeng
dc.subject.keywordsInvestigationseng
dc.subject.keywordsInformation and communication technologieseng
dc.subject.keywordsICT'seng
dc.subject.keywordsRequirements reuseeng
dc.subject.keywordsMeccano modeleng
dc.subject.lembInnovaciones tecnológicasspa
dc.subject.lembCiencias de la computaciónspa
dc.subject.lembDesarrollo tecnológicospa
dc.subject.lembIngeniería de sistemaseng
dc.subject.proposalReutilización de requisitosspa
dc.subject.proposalModelo de mecanospa
dc.titleReutilización de requisitos de usuario: el modelo mecano
dc.title.translatedReuse of User Requirements: The Mecano modeleng
dc.type.coarhttp://purl.org/coar/resource_type/c_7a1f
dc.type.driverinfo:eu-repo/semantics/article
dc.type.hasversioninfo:eu-repo/semantics/acceptedVersion
dc.type.localArtículospa
dc.type.redcolhttp://purl.org/redcol/resource_type/CJournalArticle

Archivos

Bloque original

Mostrando 1 - 1 de 1
Miniatura
Nombre:
1102-Texto del artículo-3230-1-10-20100728 (1).pdf
Tamaño:
709.84 KB
Formato:
Adobe Portable Document Format
Descripción:
Artículo
Descargar

Colecciones

Revista Colombiana de Computación