Commit d6b71464a9307cc096bd04347240eae94e7e36e5
1 parent
2d3361ec
Exists in
master
and in
3 other branches
[icse18] Create related work section
Showing
17 changed files
with
84 additions
and
83 deletions
Show diff stats
icse2018/content/01-introduction.tex
| 1 | 1 | \section{Introduction} |
| 2 | -%Same SPB introduction from OSS articles plus a related work review and brief relevance to this article? | |
| 3 | 2 | |
| 4 | 3 | The difficulty of writing software is an old subject on computer science dating back to 1968 \cite{mcilroy1968software} when the term software crisis was coined. It refers to recurrent problems on software development such as exceeding time and budget expectations, inefficiency, low quality and maintainability among many others that usually culminate in the software not meeting the user expectations or not even being delivered. |
| 5 | 4 | |
| ... | ... | @@ -12,7 +11,3 @@ Knowing it would probably be a waste of time to persuade the government on adopt |
| 12 | 11 | In this paper, we report our experiences on a three-year-long project funded by the Brazilian government, focusing on the development process evolution made throughout that period. Despite all the risks and obstacles, the project final release was delivered one year ago and now has thousands of registered users. This report is not expected to be the final recipe on software development with the public sector, its main goal is to report which techniques have been successful, what adaptations were necessary and what has failed as means to provide other developers a reference when they meet similar situations. |
| 13 | 12 | |
| 14 | 13 | % TODO: Maybe add a roadmap? |
| 15 | - | |
| 16 | -% TODO: A separate section (Related Work) would be the proper place for the paragraph below. | |
| 17 | -%% There are similar previous works that we will review here. Agile methods application on the Brazilian public sector are approached by \cite{melo2010adoccao,de2016using}, but both are experiences limited to pilot projects. Not production-ready one that will provide more accurate data with the real world. On \cite{alleman2003making} the authors describe a production deployment for the US government, but it focus on describing the methodology applied to address long term planning and value estimation. And again on \cite{anderson2005stretching} we see a production software development case and the adaptation proposal that we will follow in this article, but focused on a specific methodology, the CMMI. This article differentiates itself from others by describing a production level software development to the public sector, but unconstrained to any specific aspect of the agile methods or an specific project management methodology on the government side. The focus on this article will be the whole experience of adapting agile methods to the public sector. | |
| 18 | - | ... | ... |
icse2018/content/02-context.tex
| ... | ... | @@ -1,50 +0,0 @@ |
| 1 | -\section{Problem Context} | |
| 2 | -\label{sec:problem_context} | |
| 3 | - | |
| 4 | -During the last few decades, the Brazilian Federal Government has | |
| 5 | -improved its software adoption and development processes. In 2003, the | |
| 6 | -recommendation to adopt Free/Open Source Software (FOSS) become a public | |
| 7 | -policy. In 2007, the Brazilian Government released a portal called | |
| 8 | -Brazilian Public Software (\textit{Software Público Brasileiro} -- SPB, | |
| 9 | -in Portuguese), with the goal of sharing FOSS projects developed by, or | |
| 10 | -for, the Brazilian Government. | |
| 11 | - | |
| 12 | -The Brazilian legal instrument on software contracting | |
| 13 | -(\textit{Instrução Normativa} 04/2012) mandates that public management | |
| 14 | -must consult the SPB Portal to adopt a software solution. The | |
| 15 | -acquisition of a proprietary solution must be explicitly justified by | |
| 16 | -demonstrating that there is no suitable option in the SPB Portal. | |
| 17 | - | |
| 18 | -Since 2009, however, the SPB Portal was having several technical issues. | |
| 19 | -The original codebase was not being developed anymore, and there as a | |
| 20 | -large amount of technical debt to overcome. The system was a modified | |
| 21 | -version of an existing FOSS platform that was not being developed | |
| 22 | -anymore, and the portal maintenance was becoming harder and harder. | |
| 23 | - | |
| 24 | -From January 2014 to June 2016, a new platform for the SPB Portal was | |
| 25 | -designed and developed by the University of Brasília (UnB) and the | |
| 26 | -University of São Paulo (USP) in a partnership with the Brazilian | |
| 27 | -Ministry of Budget, Planning, and Management. This new Portal was | |
| 28 | -designed as an integrated platform for collaborative software | |
| 29 | -development. It includes functionality for social networking, mailing | |
| 30 | -lists, version control system, and source code quality monitoring. In | |
| 31 | -this paper, we present an overview of this new generation of the SPB | |
| 32 | -Portal. | |
| 33 | - | |
| 34 | -The project was developed by a team of 3 professors, 6 professionals, 2 | |
| 35 | -masters students, and approximately 40 undergrad students (not all of | |
| 36 | -them at the same time, though -- graduations and other events triggered | |
| 37 | -changes in the team). | |
| 38 | - | |
| 39 | -\begin{figure}[hbt] | |
| 40 | - \centering | |
| 41 | - \includegraphics[width=.9\linewidth]{figures/home-SPB.png} | |
| 42 | - \caption{The new SPB Portal.} | |
| 43 | - \label{fig:spb} | |
| 44 | -\end{figure} | |
| 45 | - | |
| 46 | -Figure \ref{fig:spb} shows the home page of this integrated platform. | |
| 47 | -The development tried to be as faithful as possible to FOSS development. | |
| 48 | -All development was done in the open, and the changes we needed in the | |
| 49 | -tools user were contributed back to their communities. | |
| 50 | - |
| ... | ... | @@ -0,0 +1,5 @@ |
| 1 | +\section{Related work} | |
| 2 | + | |
| 3 | +There are similar previous works that we will review here. Agile methods application on the Brazilian public sector are approached by \cite{melo2010adoccao,de2016using}, but both are experiences limited to pilot projects. Not production-ready one that will provide more accurate data with the real world. On \cite{alleman2003making} the authors describe a production deployment for the US government, but it focus on describing the methodology applied to address long term planning and value estimation. And again on \cite{anderson2005stretching} we see a production software development case and the adaptation proposal that we will follow in this article, but focused on a specific methodology, the CMMI. | |
| 4 | + | |
| 5 | +This article differentiates itself from others by describing a production level software development to the public sector, but unconstrained to any specific aspect of the agile methods or an specific project management methodology on the government side. The focus on this article will be the whole experience of adapting agile methods to the public sector. | ... | ... |
| ... | ... | @@ -0,0 +1,50 @@ |
| 1 | +\section{Problem Context} | |
| 2 | +\label{sec:problem_context} | |
| 3 | + | |
| 4 | +During the last few decades, the Brazilian Federal Government has | |
| 5 | +improved its software adoption and development processes. In 2003, the | |
| 6 | +recommendation to adopt Free/Open Source Software (FOSS) become a public | |
| 7 | +policy. In 2007, the Brazilian Government released a portal called | |
| 8 | +Brazilian Public Software (\textit{Software Público Brasileiro} -- SPB, | |
| 9 | +in Portuguese), with the goal of sharing FOSS projects developed by, or | |
| 10 | +for, the Brazilian Government. | |
| 11 | + | |
| 12 | +The Brazilian legal instrument on software contracting | |
| 13 | +(\textit{Instrução Normativa} 04/2012) mandates that public management | |
| 14 | +must consult the SPB Portal to adopt a software solution. The | |
| 15 | +acquisition of a proprietary solution must be explicitly justified by | |
| 16 | +demonstrating that there is no suitable option in the SPB Portal. | |
| 17 | + | |
| 18 | +Since 2009, however, the SPB Portal was having several technical issues. | |
| 19 | +The original codebase was not being developed anymore, and there as a | |
| 20 | +large amount of technical debt to overcome. The system was a modified | |
| 21 | +version of an existing FOSS platform that was not being developed | |
| 22 | +anymore, and the portal maintenance was becoming harder and harder. | |
| 23 | + | |
| 24 | +From January 2014 to June 2016, a new platform for the SPB Portal was | |
| 25 | +designed and developed by the University of Brasília (UnB) and the | |
| 26 | +University of São Paulo (USP) in a partnership with the Brazilian | |
| 27 | +Ministry of Budget, Planning, and Management. This new Portal was | |
| 28 | +designed as an integrated platform for collaborative software | |
| 29 | +development. It includes functionality for social networking, mailing | |
| 30 | +lists, version control system, and source code quality monitoring. In | |
| 31 | +this paper, we present an overview of this new generation of the SPB | |
| 32 | +Portal. | |
| 33 | + | |
| 34 | +The project was developed by a team of 3 professors, 6 professionals, 2 | |
| 35 | +masters students, and approximately 40 undergrad students (not all of | |
| 36 | +them at the same time, though -- graduations and other events triggered | |
| 37 | +changes in the team). | |
| 38 | + | |
| 39 | +\begin{figure}[hbt] | |
| 40 | + \centering | |
| 41 | + \includegraphics[width=.9\linewidth]{figures/home-SPB.png} | |
| 42 | + \caption{The new SPB Portal.} | |
| 43 | + \label{fig:spb} | |
| 44 | +\end{figure} | |
| 45 | + | |
| 46 | +Figure \ref{fig:spb} shows the home page of this integrated platform. | |
| 47 | +The development tried to be as faithful as possible to FOSS development. | |
| 48 | +All development was done in the open, and the changes we needed in the | |
| 49 | +tools user were contributed back to their communities. | |
| 50 | + | ... | ... |
icse2018/content/03-materials.tex
icse2018/content/04-methods.tex
| ... | ... | @@ -1,2 +0,0 @@ |
| 1 | -\section{Methods} | |
| 2 | -Here we should describe all the information regarding our data analysis: what questions were asked (and why they were asked) on the questionnaire and the answers, showing that we have taken care to avoid ambiguity and bias; what informations where extracted from gitlab and mailing lists and how they were extracted; and what code metrics were extracted and how have we done that. | |
| 3 | 0 | \ No newline at end of file |
| ... | ... | @@ -0,0 +1,2 @@ |
| 1 | +\section{Methods} | |
| 2 | +Here we should describe all the information regarding our data analysis: what questions were asked (and why they were asked) on the questionnaire and the answers, showing that we have taken care to avoid ambiguity and bias; what informations where extracted from gitlab and mailing lists and how they were extracted; and what code metrics were extracted and how have we done that. | |
| 0 | 3 | \ No newline at end of file | ... | ... |
icse2018/content/05-results.tex
| ... | ... | @@ -1 +0,0 @@ |
| 1 | -\section{Results} |
icse2018/content/06-discussion.tex
| ... | ... | @@ -1 +0,0 @@ |
| 1 | -\section{Discussion} |
| ... | ... | @@ -0,0 +1 @@ |
| 1 | +\section{Results} | ... | ... |
icse2018/content/07-conclusions.tex
| ... | ... | @@ -1 +0,0 @@ |
| 1 | -\section{Conclusions} |
| ... | ... | @@ -0,0 +1 @@ |
| 1 | +\section{Discussion} | ... | ... |
icse2018/content/08-acknowledgements.tex
| ... | ... | @@ -1,14 +0,0 @@ |
| 1 | -\begin{acks} | |
| 2 | - The authors would like to thank Dr. Yuhua Li for providing the | |
| 3 | - matlab code of the \textit{BEPS} method. | |
| 4 | - | |
| 5 | - The authors would also like to thank the anonymous referees for | |
| 6 | - their valuable comments and helpful suggestions. The work is | |
| 7 | - supported by the \grantsponsor{GS501100001809}{National Natural | |
| 8 | - Science Foundation of | |
| 9 | - China}{http://dx.doi.org/10.13039/501100001809} under Grant | |
| 10 | - No.:~\grantnum{GS501100001809}{61273304} | |
| 11 | - and~\grantnum[http://www.nnsf.cn/youngscientsts]{GS501100001809}{Young | |
| 12 | - Scientsts' Support Program}. | |
| 13 | - | |
| 14 | -\end{acks} |
| ... | ... | @@ -0,0 +1 @@ |
| 1 | +\section{Conclusions} | ... | ... |
| ... | ... | @@ -0,0 +1,14 @@ |
| 1 | +\begin{acks} | |
| 2 | + The authors would like to thank Dr. Yuhua Li for providing the | |
| 3 | + matlab code of the \textit{BEPS} method. | |
| 4 | + | |
| 5 | + The authors would also like to thank the anonymous referees for | |
| 6 | + their valuable comments and helpful suggestions. The work is | |
| 7 | + supported by the \grantsponsor{GS501100001809}{National Natural | |
| 8 | + Science Foundation of | |
| 9 | + China}{http://dx.doi.org/10.13039/501100001809} under Grant | |
| 10 | + No.:~\grantnum{GS501100001809}{61273304} | |
| 11 | + and~\grantnum[http://www.nnsf.cn/youngscientsts]{GS501100001809}{Young | |
| 12 | + Scientsts' Support Program}. | |
| 13 | + | |
| 14 | +\end{acks} | ... | ... |
icse2018/main.tex
| ... | ... | @@ -83,13 +83,14 @@ |
| 83 | 83 | \maketitle |
| 84 | 84 | |
| 85 | 85 | \input{content/01-introduction} |
| 86 | -\input{content/02-context} | |
| 87 | -\input{content/03-materials} | |
| 88 | -\input{content/04-methods} | |
| 89 | -\input{content/05-results} | |
| 90 | -\input{content/06-discussion} | |
| 91 | -\input{content/07-conclusions} | |
| 92 | -\input{content/08-acknowledgements} | |
| 86 | +\input{content/02-related_work} | |
| 87 | +\input{content/03-context} | |
| 88 | +\input{content/04-materials} | |
| 89 | +\input{content/05-methods} | |
| 90 | +\input{content/06-results} | |
| 91 | +\input{content/07-discussion} | |
| 92 | +\input{content/08-conclusions} | |
| 93 | +\input{content/09-acknowledgements} | |
| 93 | 94 | |
| 94 | 95 | \bibliographystyle{ACM-Reference-Format} |
| 95 | 96 | \bibliography{bibliography} | ... | ... |