Download as
Browse Code »

Commit b98868602a1795dc486048b6e166280e3ebcc9da

Authored by Melissa Wen
1 parent f2e42ca6
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[OpenSym] Relate references

Showing 5 changed files with 38 additions and 69 deletions   Show diff stats
opensym2017/content/01-introduction.tex
  Diff comments   View file @b988686
... ... @@ -26,8 +26,6 @@ of expertise in real-world software development of its agents produces a
26 26 situation of inneficient software development contracts and
27 27 unjustifiable expending of taxpayers' money.
28 28  
29   -% TODO: ^ references
30   -
31 29 Since 2009, the SPB Portal was having several technical issues. The original
32 30 codebase was not being developed anymore, also, there was a large amount of
33 31 knowingly non-optimal or wrong design decisions to overcome (in other words,
... ... @@ -43,8 +41,8 @@ developed, among January 2014 and June 2016, by the University of
43 41 Brasília (UnB) and the University of São Paulo (USP) in a partnership
44 42 with the Brazilian Ministry of Budget, Planning, and Management (MP). It
45 43 was designed as an integrated platform for collaborative software
46   -development, and includes functionality for social networking, mailing
47   -lists, version control system, and source code quality monitoring. To
  44 +development \cite{bobr2003}, and includes functionality for social networking,
  45 +mailing lists, version control system, and source code quality monitoring. To
48 46 coordinate and develop this project during 30 months, UnB received from
49 47 the Brazilian Federal Government a total of 2,619,965.00 BRL (about
50 48 750,000.00 USD in June 2016).
... ... @@ -65,7 +63,11 @@ the master students were from USP. Regarding the designers and senior
65 63 developers, 7 of 8 they were living outside of Brasília: Curitiba/Brazil, São
66 64 Paulo/Brazil, Ribeirão Preto/Brazil, Salvador/Brazil, Santo Domingo/Dominican
67 65 Republic, and Montreal/Canada. In other words, we had a team working in
68   -distributed collaborative virtual environment.
  66 +distributed collaborative virtual environment. This diversity of actors and
  67 +the relationships between industry, academy and government also made
  68 +the project a valued opportunity to explore the benefits and challenges of
  69 +using FLOSS\cite{kon2011,deKoenigsberg2008, fagerholm2013, fagerholm2014} and
  70 +Agile\cite{steghofer2016, harzl2017} practices for Software Engineering education.
69 71  
70 72 Figure \ref{fig:spb} shows the home page of this integrated platform.
71 73 All development was done in the open, and the changes we needed in the
... ... @@ -80,15 +82,14 @@ released in June 2016.
80 82 In this paper, we present an overview of this new generation of the SPB
81 83 Portal. The paper shares the methodology employed to develop this project,
82 84 in partnership with the Brazilian Federal Government, to comply with its
83   -requirements at the same time to be as faithful as possible to FOSS development.
84   -Moreover, we discuss several lessons learned to provide a distributed
85   -collaborative virtual environment involving a large undergraduate student team
86   -and remote senior developers. Lastly, we released an unprecedented platform for
87   -the Brazilian government applying empirical software development methods. This
88   -case can help other projects to overcome similar software engineering challenges
89   -in the future, as well as to illustrate how universities can improve the
90   -real-world experience of their students by means of this kind of project.
91   -
  85 +requirements at the same time to be as faithful as possible to FOSS development
  86 +\cite{mockus2002, tosi2015}. Moreover, we discuss several lessons learned to provide a
  87 +distributed collaborative virtual environment involving alarge undergraduate student
  88 +team and remote senior developers. Lastly, we released an unprecedented platform for
  89 +the Brazilian government applying empirical software development methods. This case
  90 +can help other projects to overcome similar software engineering challenges in the
  91 +future, as well as to illustrate how universities can improve the real-world
  92 +experience of their students by means of this kind of project.
92 93  
93 94 The remainder of this work is organized as follows.
94 95 Section \ref{sec:spb}...
... ...
opensym2017/content/02-spb.tex
  Diff comments   View file @b988686
... ... @@ -32,7 +32,7 @@ license, and the BSD license.
32 32 The original incarnation of SPB portal has been designed in 2005 and
33 33 released in 2007. From a practical point of view, it is a web system
34 34 that has consolidated itself as an environment for sharing software
35   -projects. It provides a space (community) for each software.
  35 +projects \cite{freitas2008}. It also provides a space (community) for each software.
36 36 Therefore, it was designed to include tools that promote collaboration
37 37 and interaction in communities (by managers, users, and developers) of
38 38 the projects, according to the practices used in FOSS communities. This
... ... @@ -43,12 +43,13 @@ Initially, the purpose of the portal was only to share the software developed
43 43 in the Brazilian government, to reduce the costs of hiring software. However,
44 44 it was observed that when softwares were released, their communities were
45 45 formed around those software with several people collaborating and sharing the
46   -results obtained through the use of those solutions. In this way, some software
47   -development cooperatives and private companies have shown an interest in making
48   -their software available on the SPB platform.
  46 +results obtained through the use of those solutions, as commonly occurs in OSS
  47 +\cite{ducheneaut2005}. In this way, some software development cooperatives and
  48 +private companies have shown an interest in making their software available on
  49 +the SPB platform.
49 50  
50   -The concept of Brazilian Public Software goes beyond FOSS. In addition
51   -to being licensed under a FOSS license, a SPB needs to have explicit
  51 +The concept of Brazilian Public Software goes beyond FOSS \cite{freitas2008}.
  52 +In additionto being licensed under a FOSS license, a SPB needs to have explicit
52 53 guarantees that it is a public good, and that project must be available
53 54 on the SPB portal. Being a true public good assumes requirements that
54 55 can not be met solely by means of FOSS licensing. For example, there
... ...
opensym2017/content/03-relatedworks.tex
  Diff comments   View file @b988686
1   -\section{Related Work}
2   -\label{sec:relatedwork}
  1 +\section{Related Works}
  2 +\label{sec:relatedworks}
3 3  
4 4 The new SPB platform presented in this paper is a fully integrated
5 5 environment, as we can see in Figure \ref{fig:requirements}, being very
... ... @@ -31,11 +31,13 @@ business ecosystem. In short, it aims to support the development, deployment
31 31 and management of distributed applications with a focus on FOSS middleware and
32 32 related development and management tools.
33 33 %
34   -Moreover, from the European Commission in 2007 until 20011, there was the
35   -QualiPSo project that aimed at providing FOSS users, developers, and consumers,
36   -with quality resources and expertise on the various topics related to FOSS. The
37   -QualiPSo project also had planned to develop a platform called QualiPSo
38   -Factory but it was not fully completed.
  34 +Moreover, in 2007 the European Comission published a study examined the impact
  35 +the development and distribution of FLOSS by public bodies has on eGovernment
  36 +services, the economy, and the information society \cite{ghosh2004}. And there
  37 +was between 2007 until 2011 the QualiPSo project that aimed at providing
  38 +FOSS users, developers, and consumers, with quality resources and expertise on
  39 +the various topics related to FOSS. The QualiPSo project also had planned to
  40 +develop a platform called QualiPSo Factory but it was not fully completed.
39 41  
40 42 In Latin American there is an initiative based on the SPB project called ``Software
41 43 Publico Regional''\footnote{\url{http://softwarepublicoregionalbeta.net}}. From
... ...
opensym2017/spb.bib
  Diff comments   View file @b988686
... ... @@ -173,25 +173,15 @@
173 173 numpages = {10},
174 174 url = {http://doi.acm.org/10.1145/2889160.2889181},
175 175 doi = {10.1145/2889160.2889181},
176   - acmid = {2889181},
177 176 publisher = {ACM},
178 177 address = {New York, NY, USA},
179 178 keywords = {Agile methodogies, Scrum, project-based learning, software engineering education, teaching},
180 179 }
181 180  
182 181 @article{bobr2003,
183   - added-at = {2007-11-01T10:10:38.000+0100},
184 182 author = {Booch, Grady and Brown, Alan W.},
185   - biburl = {https://www.bibsonomy.org/bibtex/23600fee0632a9dcc34d9d082b73d2d9f/carsten},
186   - file = {BoBr03.pdf:BoBr03.pdf:PDF},
187   - interhash = {00c68a7c5438edeff30e1831ff5ad1cb},
188   - intrahash = {3600fee0632a9dcc34d9d082b73d2d9f},
189 183 journal = {Advances in Computers},
190   - keywords = {cscw development diss tool work},
191   - owner = {ritterskamp},
192 184 pages = {?},
193   - standort = {Ordner},
194   - timestamp = {2007-11-01T10:16:29.000+0100},
195 185 title = {Collaborative Development Environments},
196 186 volume = {59},
197 187 year = {2003}
... ... @@ -209,20 +199,13 @@
209 199 }
210 200  
211 201 @inproceedings{tosi2015,
212   - added-at = {2015-04-17T00:00:00.000+0200},
213 202 author = {Tosi, Davide and Lavazza, Luigi and Morasca, Sandro and Chiappa, Marco},
214   - biburl = {https://www.bibsonomy.org/bibtex/241e61dfdcfdb6ebcea3c9f011dfae555/dblp},
215 203 booktitle = {OSS},
216 204 editor = {Damiani, Ernesto and Frati, Fulvio and Riehle, Dirk and Wasserman, Anthony I.},
217   - ee = {http://dx.doi.org/10.1007/978-3-319-17837-0_11},
218   - interhash = {ac902fdd114e51b034384d71a1090792},
219   - intrahash = {41e61dfdcfdb6ebcea3c9f011dfae555},
220 205 isbn = {978-3-319-17836-3},
221   - keywords = {dblp},
222 206 pages = {114-123},
223 207 publisher = {Springer},
224 208 series = {IFIP Advances in Information and Communication Technology},
225   - timestamp = {2015-06-18T14:03:53.000+0200},
226 209 title = {Surveying the Adoption of FLOSS by Public Administration Local Organizations.},
227 210 url = {http://dblp.uni-trier.de/db/conf/oss/oss2015.html},
228 211 volume = {451},
... ...
opensym2017/spb.tex
  Diff comments   View file @b988686
... ... @@ -77,7 +77,7 @@
77 77 % re-using, if desired). Use \emtpyauthor when submitting for review
78 78 % so you remain anonymous.
79 79 \def\plaintitle{Brazilian Public Software Portal: an integrated platform for collaborative development}
80   -\def\plainauthor{Paulo Meirelles, Melissa Wen, Antonio Terceiro, Rodrigo Siqueira, Lucas Kanashiro, Hilmer Neri}
  80 +\def\plainauthor{Paulo Meirelles, Antonio Terceiro, Hilmer Neri, Melissa Wen, Ridrigo Siqueira, Lucas Kanashiro}
81 81 \def\emptyauthor{}
82 82 \def\plainkeywords{Brazilian Public Software, Free/Libre/Open Source Software, Software Evolution, Integrated Platform.}
83 83 \def\plaingeneralterms{Documentation, Standardization}
... ... @@ -132,36 +132,18 @@
132 132  
133 133 \numberofauthors{6}
134 134 \author{%
135   - \alignauthor{Paulo Meirelles\
  135 + \alignauthor{Paulo Meirelles,\\Hilmer Neri\
136 136 \affaddr{Faculty Gama (FGA) \\ University of Bras\'ilia}\\
137 137 \affaddr{Gama, Brazil}\\
138   - \email{paulormm@unb.br}\\
139   - }
140   - \alignauthor{Melissa Wen\\
141   - \affaddr{FLOSS Competence Center \\ University of S\~ao Paulo}\\
142   - \affaddr{São Paulo, Brazil}\\
143   - \email{melissa.srw@gmail.com}\\
144   - }
145   - \alignauthor{Antonio Terceiro\\
  138 + \email{\{paulormm,hilmer\}@unb.br}}\\
  139 + \alignauthor{Antonio Terceiro,\\Melissa Wen\\
146 140 \affaddr{Colivre}\\
147 141 \affaddr{Salvador, Brazil}\\
148   - \email{terceiro@colivre.coop.br}\\
149   - }
150   - \alignauthor{Rodrigo Siqueira\\
151   - \affaddr{FLOSS Competence Center \\ University of S\~ao Paulo}\\
152   - \affaddr{São Paulo, Brazil}\\
153   - \email{siqueira@ime.usp.br}\\
154   - }
155   - \alignauthor{Lucas Kanashiro\\
  142 + \email{\{terceiro,melissa\}@colivre.coop.br}}\\
  143 + \alignauthor{Rodrigo Siqueira,\\Lucas Kanashiro\\
156 144 \affaddr{FLOSS Competence Center \\ University of S\~ao Paulo}\\
157 145 \affaddr{São Paulo, Brazil}\\
158   - \email{lkd@ime.usp.br}\\
159   - }
160   - \alignauthor{Hilmer Neri\\
161   - \affaddr{Faculty Gama (FGA) \\ University of Bras\'ilia}\\
162   - \affaddr{Gama, Brazil}\\
163   - \email{hilmer@unb.br}
164   - }
  146 + \email{\{siqueira,lkd\}@ime.usp.br}}\\
165 147 }
166 148  
167 149 \maketitle
... ...