Use of Checklist for Requirements Revalidation in Legacy Software: Case Study RETEC

被引:0
|
作者
Neves, D. V. [1 ]
Prietch, S. S. [1 ]
机构
[1] Univ Fed Mato Grosso, Campus Rondonopolis, Cuiaba, Brazil
关键词
Requirements Engineering; Electronic Journal; Data Base;
D O I
10.1109/TLA.2016.7785954
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
The technologies employed in computer systems have evolved quickly in recent years. Not always the institutions manage to stay updated to new technologies and often they keep using obsolete technologies. The migration of those systems to new platforms come up against many difficulties with regard to restructuring and migration to modern platforms, understanding what the system does, or should to do. Based on this principle, the problem in hand is to conduct activities related to an electronic journal, which currently are performed out manually. In this sense, this study aims to adapt and include RETEC to the national magazine publishing model, called SEER, as well as examine if the features of this platform meets the needs of publishers. The methodology adopted the following steps: requirements elicitation, implementation stage and system validation. During this study, it was also developed a requirement validation methodology by conducting a checklist test. The method developed allowed specifications, in the requirements document, to be verified and validated in an objective, efficient and standardized way. Therefore, the methodology developed and used in this study has characteristics that make it feasible to be applied during inspection and validation of requirements for a good quality software with a low number of errors, independently of analyzed tool.
引用
收藏
页码:4208 / 4213
页数:6
相关论文
共 50 条
  • [1] The Use of Design Thinking in Agile Software Requirements Survey: A Case Study
    Canedo, Edna Dias
    da Costa, Ruyther Parente
    [J]. DESIGN, USER EXPERIENCE, AND USABILITY: THEORY AND PRACTICE, DUXU 2018, PT I, 2018, 10918 : 642 - 657
  • [2] Validating software requirements with enactable use case descriptions
    Kanyaru, John Mathenge
    Phalp, Keith
    [J]. REQUIREMENTS ENGINEERING, 2009, 14 (01) : 1 - 14
  • [3] Validating software requirements with enactable use case descriptions
    John Mathenge Kanyaru
    Keith Phalp
    [J]. Requirements Engineering, 2009, 14 : 1 - 14
  • [4] Requirements for Security Enhancements to Legacy Software with RUP
    Mocanu, Virgil
    [J]. INFORMATION SECURITY JOURNAL, 2010, 19 (04): : 226 - 236
  • [5] Requirements for a COTS software component: A case study
    Ljerka Beus-Dukic
    Andy Wellings
    [J]. Requirements Engineering, 1998, 3 (2) : 115 - 120
  • [6] Special checklist for security requirements in software development site
    Hwang, Sun-myung
    [J]. MUE: 2007 International Conference on Multimedia and Ubiquitous Engineering, Proceedings, 2007, : 1172 - 1176
  • [7] A case study involving the use of Z to aid requirements specification in the software engineering course
    Hasson, P
    Cooper, S
    [J]. 17TH CONFERENCE ON SOFTWARE ENGINEERING EDUCATION AND TRAINING, PROCEEDINGS, 2004, : 84 - 89
  • [8] A checklist for evaluating the software problem management model:: A case study
    Jantti, Marko
    Miettinen, Aki
    Vahakainu, Kyosti
    [J]. PROCEEDINGS OF THE IASTED INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, 2007, : 7 - +
  • [9] Defect Prediction on a Legacy Industrial Software: A Case Study on Software with Few Defects
    Koroglu, Yavuz
    Sen, Alper
    Kutluay, Doruk
    Bayraktar, Akin
    Tosun, Yalcin
    Cinar, Murat
    Kaya, Hasan
    [J]. 2016 IEEE/ACM 4TH INTERNATIONAL WORKSHOP ON CONDUCTING EMPIRICAL STUDIES IN INDUSTRY (CESI), 2016, : 14 - 20
  • [10] Concept of unified use case model for software requirements specification
    Zmeyev, Oleg A.
    Politov, Arsenty M.
    Chayka, Yana M.
    [J]. VESTNIK TOMSKOGO GOSUDARSTVENNOGO UNIVERSITETA-UPRAVLENIE VYCHISLITELNAJA TEHNIKA I INFORMATIKA-TOMSK STATE UNIVERSITY JOURNAL OF CONTROL AND COMPUTER SCIENCE, 2015, 32 (03): : 91 - 98