Interoperability in e-Government Solutions: The Case of Brazilian Federal Universities

• Alberto Oliveira Universidade de São Paulo
• Marcelo Eler Universidade de São Paulo

DOI: https://doi.org/10.5753/sbsi.2017.6059

Resumo

Governments use Information and Communication Technology (ICT) to provide citizens, organizations and governments with online services and tools. One of the key factors in this context is system interoperability, since it promotes the exchange of information among systems in different levels. Achieving high levels of interoperability, however, is challenging because it involves different concepts, business processes, standards, languages, ontologies and laws. The Brazilian government has defined the e-PING Interoperability Standards to specify the guidelines for achieving interoperability in different levels, but many public organizations cannot completely implement the interoperability aspects in their solutions. Therefore, the purpose of this paper is to present an investigation we conducted with the ICT departments of the Brazilian federal universities to understand whether and how they use the e-PING interoperability standards, and what are the main challenges. Results show that most universities do not fully implement interoperability requirements mainly because of a shortage of ICT staff, lack of knowledge and lack of clear instructions on how to achieve interoperability using the e-PING standards. Such findings allow us to identify several improvements on the Brazilian egovernment strategy.

Palavras-chave: Interoperabilidade, governo digital, e-governo, e-PING, Brasil

Referências

Abdullah, N.N.B. et al. 2011. Communication patterns of agile requirements engineering. Proceedings of the 1st Workshop on Agile Requirements Engineering. (jul. 2011), 1–4.

Baruah, N. 2015. Requirement management in agile software environment. Proceedings of the 2015 International Conference on Soft Computing and Software Engineering. 62, (dez. 2015), 81–83.

Carrizo, D. et al. 2008. Study of elicitation techniques adequacy. Proceedings of the 11th Workshop on Requirements Engineering. 11, (jan. 2008), 104–114.

Chen, J.Q. et al. 2007. Light-Weight Development Method: a Case Study. International Conference on Service Systems and Service Management. (jun. 2007), 1–6.

Chow, T. e Cao, D. 2008. A survey study of critical success factors in agile software projects. Journal of Systems and Software. 81, (ago. 2008), 961–971.

Clear, T. 2003. Documentation and agile methods. SIGCSE Bulletin. 35, 2 (jun. 2003), 12–13.

Daneva, M. et al. 2013. Agile requirements prioritization in large-scale outsourced system projects: An empirical study. Journal of Systems and Software. 86, 5 (maio 2013), 1333– 1353.

Dimitrijević, S. et al. 2015. A comparative study of software tools for user story management. Information and Software Technology. 57, (jan. 2015), 352–368.

Dragicevic, S. et al. 2014. Use of method for elicitation, documentation, and validation of software user requirements (MEDoV) in agile software development projects. Proceedings - 6th International Conference on Computational Intelligence, Communication Systems and Networks. (maio 2014), 65–70.

Ernst, N.A. et al. 2014. Agile requirements engineering via paraconsistent reasoning. Information Systems. 43, (jul. 2014), 100–116.

Gandomani, T.J. et al. 2013. Obstacles in moving to agile software development methods; At a Glance. Journal of Computer Science. 9, 5 (jan. 2013), 620–625.

Gayer, S. et al. 2016. Lightweight Traceability for the Agile Architect. Computer. 49, 5 (maio 2016), 64–71.
Ghanbari, H. et al. 2015. Utilizing online serious games to facilitate distributed requirements elicitation. Journal of Systems and Software. 109, (nov. 2015), 32–49.

Haugset, B. e Stålhane, T. 2012. Automated acceptance testing as an agile requirements engineering practice. Hawaii International Conference on System Sciences. 45, (jan. 2012), 5289–5298.

Heikkila, V.T. et al. 2015. A Mapping Study on Requirements Engineering in Agile Software Development. Euromicro Conference on Software Engineering and Advanced Applications. 41, (ago. 2015), 199–207.

Hoda, R. et al. 2010. How much is just enough? Some Documentation Patterns on Agile Projects. Proceedings of the 15th European Conference on Pattern Languages of Programs. 15, (jul. 2010), 1–13.

Inayat, I. et al. 2015. A systematic literature review on agile requirements engineering practices and challenges. Computers in Human Behavior. 51, (out. 2015), 915–929.

Inayat, I. et al. 2012. Socio-technical aspects of requirements-driven collaboration (RDC) in agile software development methods. IEEE Conference on Open Systems. (out. 2012), 1–6.

Jaqueira, A. et al. 2012. Desafios de Requisitos em Métodos Ágeis: Uma Revisão Sistemática. Brazilian Workshop on Agile Methods. 3, (jan. 2012), 49–60.

Kajko-Mattsson, M. 2008. Problems in agile trenches. Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement. (out. 2008), 111–119.

Käpyaho, M. e Kauppinen, M. 2015. Agile requirements engineering with prototyping: A case study. International Requirements Engineering Conference. 23, (ago. 2015), 334– 343.

Kelly, S. 2010. Towards an evolutionary framework for agile requirements elicitation. Proceedings of the 2nd ACM SIGCHI symposium on Engineering interactive computing systems. (jun. 2010), 349–352.

Kumar, M. et al. 2010. Towards knowledge assisted agile requirements evolution. Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering. (maio 2010), 16–20.

Liskin, O. et al. 2014. Understanding the role of requirements artifacts in kanban. Proceedings of the 7th International Workshop on Cooperative and Human Aspects of Software Engineering. (jun. 2014), 56–63.

Liu, L. e Lu, Y. 2012. Application of agile method in the enterprise website backstage management system: Practices for extreme programming. International Conference on Consumer Electronics, Communications and Networks (CECNet). 2, (abr. 2012), 2412–2415.

Lucia, A. De e Qusef, A. 2010. Requirements Engineering in Agile Software Development. Journal Of Emerging Technologies In Web Intelligence. 2, 3 (ago. 2010), 212–221.

Mahmud, I. e Veneziano, V. 2011. Mind-mapping: An effective technique to facilitate requirements engineering in agile software development. International Conference on Computer and Information Technology. 14, (dez. 2011), 157– 162.

Maiden, N. e Jones, S. 2010. Agile Requirements Can We Have Our Cake and Eat It Too? IEEE Software. 27, 3 (maio 2010), 87–88.

Manifesto for Agile Software Development: 2001. http://agilemanifesto.org/.

Mead, N.R. et al. 2008. Incorporating Security Requirements Engineering into the Dynamic Systems Development Method. 32th Annual IEEE International Computer Software and Applications Conference. 32, (ago. 2008), 949–954.

Mendes, T.S. et al. 2016. Impacts of Agile Requirements Documentation Debt on Software Projects : A Retrospective Study. Proceedings of the 31st Annual ACM Symposium on Applied Computing. 31, (abr. 2016), 1290–1295.

Mishra, D. e Mishra, A. 2011. Pattern detection for conceptual schema recovery in data-intensive systems. Journal of Software: Evolution and Process. 23, (jan. 2011), 549–564.

Paetsch, F. et al. 2003. Requirements engineering and agile software development. Proceedings. 12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises. 12, (jun. 2003), 1–6.

Ramesh, B. et al. 2010. Agile requirements engineering practices and challenges: an empirical study. IEEE Software. 25, 1 (fev. 2010), 449–480.

Rubin, E. e Rubin, H. 2011. Supporting agile software development through active documentation. Requirements Engineering. 16, 2 (jun. 2011), 117–132.

Schön, E.-M. et al. 2017. Agile Requirements Engineering: A Systematic Literature Review. Computer Standards & Interfaces. 49, (jan. 2017), 79–91.

Sillitti, A. et al. 2005. Managing Uncertainty in Requirements: a Survey in Documentation-driven and Agile Companies. IEEE International Software Metrics Symposium. 11, (set. 2005), 1–10.

Soares, H.F. et al. 2015. Investigating the Link between User Stories and Documentation Debt on Software Projects. International Conference on Information Technology - New Generations. 12, (abr. 2015), 385–390.

Stankovic, D. et al. 2013. A survey study of critical success factors in agile software projects in former Yugoslavia IT companies. Journal of Systems and Software. 86, 6 (jun. 2013), 1663–1678.

Stettina, C.J. e Heijstek, W. 2011. Necessary and Neglected? An Empirical Study of Internal Documentation in Agile Sotware Development Teams. Proceedings of the 29th ACM international conference on Design of communication. 29, (out. 2011), 159–166.

Stettina, C.J. e Kroon, E. 2013. Is there an agile handover? An empirical study of documentation and project handover practices across agile software teams. International Conference on Engineering, Technology and Innovation, ICE 2013 and IEEE International Technology Management Conference. (jun. 2013), 1–12.

Tarhan, A. e Yilmaz, S.G. 2014. Systematic analyses and comparison of development performance and product quality of Incremental Process and Agile Process. Information and Software Technology. 56, 5 (maio 2014), 477–494.

Trkman, M. et al. 2016. Using business process models to better understand the dependencies among user stories. Information and Software Technology. 71, (mar. 2016), 58– 76.

Vlaanderen, K. et al. 2011. The agile requirements refinery: Applying SCRUM principles to software product management. Information and Software Technology. 53, 1 (jan. 2011), 58–70.

Wan, J. et al. 2013. Case Study on Critical Success Factors of Running Scrum. Journal of Software Engineering and Applications. 6, (fev. 2013), 59–64.