Compare View

switch
from
...
to
 
Commits (6)
Showing 4 changed files   Show diff stats
opensym2017/content/00-abstract.tex
  Diff comments   View file @31e88fd
@@ -25,7 +25,30 @@ project. @@ -25,7 +25,30 @@ project.
25 25
26 \end{abstract} 26 \end{abstract}
27 27
28 -\category{H.5.m.}{Information Interfaces and Presentation (e.g. HCI)}  
29 -{Miscellaneous} 28 +\category{K.6.1}{Project and People Management}{Systems development}
  29 +
  30 +
  31 +
  32 +\begin{comment}
  33 +%%%%%%%%%%%%%%%
  34 +\begin{CCSXML}
  35 +<ccs2012>
  36 +<concept>
  37 +<concept_id>10011007.10011074</concept_id>
  38 +<concept_desc>Software and its engineering~Software creation and management</concept_desc>
  39 +<concept_significance>500</concept_significance>
  40 +</concept>
  41 +<concept>
  42 +<concept_id>10011007.10011074.10011134</concept_id>
  43 +<concept_desc>Software and its engineering~Collaboration in software development</concept_desc>
  44 +<concept_significance>500</concept_significance>
  45 +</concept>
  46 +</ccs2012>
  47 +\end{CCSXML}
  48 +
  49 +\ccsdesc[500]{Software and its engineering~Software creation and management}
  50 +\ccsdesc[500]{Software and its engineering~Collaboration in software development}
  51 +%%%%%%%%%%%%%%%
  52 +\end{comment}
30 53
31 \keywords{\plainkeywords} 54 \keywords{\plainkeywords}
opensym2017/content/01-introduction.tex
  Diff comments   View file @31e88fd
@@ -3,14 +3,13 @@ @@ -3,14 +3,13 @@
3 3
4 The Brazilian Government released in the year 2000 the Eletronic Government 4 The Brazilian Government released in the year 2000 the Eletronic Government
5 program (eGov) aiming at democratizing information access and improving the 5 program (eGov) aiming at democratizing information access and improving the
6 -public provision quality of service and information. In 2003, the Brazilian  
7 -President created a 6 +public provision quality of service and information. In 2003, the Federal Government created a
8 committee\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/ 7 committee\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/
9 DecretoComite}} for implementation of Free/Libre/Open Source Software 8 DecretoComite}} for implementation of Free/Libre/Open Source Software
10 (FLOSS\footnote{In this work, the acronym ``FLOSS'' is used as a representative 9 (FLOSS\footnote{In this work, the acronym ``FLOSS'' is used as a representative
11 for ``Free Software'', ``Open Source Software'' (OSS), and``Free/Open Source 10 for ``Free Software'', ``Open Source Software'' (OSS), and``Free/Open Source
12 -Software'' (FOSS).}) and thereafter the Chief of Staff of Brazil sent a  
13 -circular- letter to all Ministries in which the recommendation to adopt FLOSS 11 +Software'' (FOSS).}) and thereafter a
  12 +circular-letter was sent to all Ministries in which the recommendation to adopt FLOSS
14 became a public 13 became a public
15 policy\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/circulardoministro}}. 14 policy\footnote{\url{http://www.softwarelivre.gov.br/documentos-oficiais/circulardoministro}}.
16 In 2007, the Brazilian Public Software Portal (\textit{Portal do Software 15 In 2007, the Brazilian Public Software Portal (\textit{Portal do Software
opensym2017/content/04-researchdesign.tex
  Diff comments   View file @31e88fd
1 \section{Open Questions} 1 \section{Open Questions}
2 \label{sec:researchdesign} 2 \label{sec:researchdesign}
3 3
4 -In this paper, we aim to share our experience designing and developing the new  
5 -SPB Portal by reporting, alongside the technical efforts carried out, our  
6 -empirical work process and the lessons learned. In the begins of the new SPB  
7 -Portal project, we had in mind 3 main challenges to overcome, as explained in  
8 -the following open questions. 4 +In this paper, we share our experience in designing and developing the new
  5 +SPB Portal by reporting the technical efforts carried out, our
  6 +empirical work process, and the lessons learned. The new SPB Portal project
  7 +presented three main challenges, related to the open questions described below.
9 8
10 \begin{description} 9 \begin{description}
11 10
12 \item [Q1:] \textit{Which strategy could be used to integrate several existing 11 \item [Q1:] \textit{Which strategy could be used to integrate several existing
13 -FLOSS tools to promote the collaborative software development?} 12 +FLOSS tools to promote a collaborative software development?}
14 % 13 %
15 Based on an extensive list of functional requirements defined by the Brazilian 14 Based on an extensive list of functional requirements defined by the Brazilian
16 -Federal Government, we selected some FLOSS systems to form our solution,  
17 -generating a non-trivial integration among them. We looked for system that  
18 -together could provide the largest subset possible of the requirements, and 15 +Federal Government, we selected some FLOSS systems to compose our solution,
  16 +engineering a nontrivial integration among them. We looked for the systems set
  17 +realizing the largest possible subset of the requirements list. However, we
19 were fully aware that we would need to improve those systems in order to 18 were fully aware that we would need to improve those systems in order to
20 -provide the rest. We were also convinced that it would be impossible to provide 19 +satisfy the remaining requirements. We were also convinced that it would be impossible to satisfy
21 all of those requirements with a single tool. 20 all of those requirements with a single tool.
22 21
23 \item [Q2:] \textit{How to involve students in real-world projects interacting with 22 \item [Q2:] \textit{How to involve students in real-world projects interacting with
24 real customers?} 23 real customers?}
25 % 24 %
26 Our team was mainly composed of software engineering undergraduate 25 Our team was mainly composed of software engineering undergraduate
27 -students, who had the opportunity to interact with senior developers and  
28 -designers on the team, as well as with the team of technicians and  
29 -managers from the Brazilian Government, and the management team from  
30 -UnB. For the majority of the students, this was a first professional experience. We have define an approach to involve the undergraduate students in this project with a central role in our development process. 26 +students, who had the opportunity to interact with the UnB managers,
  27 +senior developers, designers, and even with technicians and
  28 +managers from the Brazilian Government.
  29 +For the majority of the students, this was a first professional experience.
  30 +Even though, our development process defined a central role on students participation.
31 31
32 -\item [Q3:] \textit{How to introduce the FLOSS collaborative and agile  
33 -practices to governmental development process?} 32 +\item [Q3:] \textit{How to introduce collaborative and agile
  33 +practices typical in FLOSS environments in the governmental development process?}
34 % 34 %
35 -The Brazilian government works based on a very traditional way regarding  
36 -software developing, frequently focusing on documents. We have need to convince  
37 -them to accept the idea of open scope and empirical development. They have  
38 -certain expectations about the development of project according to RUP 35 +The software development on Brazilian government is based on a very traditional way,
  36 +frequently focusing documentation deliveries. We had to convince
  37 +them to accept the idea of open scope and empirical development. They had
  38 +certain expectations about the project development according to RUP
39 (Rational Unified Process) and PMBOK (Project Management Body of Knowledge) 39 (Rational Unified Process) and PMBOK (Project Management Body of Knowledge)
40 -approaches, what not match our work based on agile and FLOSS practices. We have  
41 -created strategies that would support different these organizational cultures. 40 +approaches, which mismatched our work style based on agile and FLOSS practices. So we
  41 +created strategies to conciliate these different organizational cultures within the project.
42 42
43 \end{description} 43 \end{description}
opensym2017/spb.tex
  Diff comments   View file @31e88fd
@@ -5,44 +5,11 @@ @@ -5,44 +5,11 @@
5 % copyright statement. 5 % copyright statement.
6 6
7 % Copyright 7 % Copyright
8 -\CopyrightYear{2017}  
9 -%\setcopyright{acmcopyright}  
10 -\setcopyright{acmlicensed}  
11 -%\setcopyright{rightsretained}  
12 -%\setcopyright{usgov}  
13 -%\setcopyright{usgovmixed}  
14 -%\setcopyright{cagov}  
15 -%\setcopyright{cagovmixed}  
16 -% DOI  
17 -\doi{http://dx.doi.org/10.475/123_4}  
18 -% ISBN  
19 -\isbn{123-4567-24-567/08/06}  
20 -%Conference  
21 -\conferenceinfo{CHI'16,}{May 07--12, 2016, San Jose, CA, USA}  
22 -%Price  
23 -\acmPrice{\$15.00}  
24 -  
25 -% Use this command to override the default ACM copyright statement  
26 -% (e.g. for preprints). Consult the conference website for the  
27 -% camera-ready copyright statement.  
28 -  
29 -%% HOW TO OVERRIDE THE DEFAULT COPYRIGHT STRIP --  
30 -%% Please note you need to make sure the copy for your specific  
31 -%% license is used here!  
32 -% \toappear{  
33 -% Permission to make digital or hard copies of all or part of this work  
34 -% for personal or classroom use is granted without fee provided that  
35 -% copies are not made or distributed for profit or commercial advantage  
36 -% and that copies bear this notice and the full citation on the first  
37 -% page. Copyrights for components of this work owned by others than ACM  
38 -% must be honored. Abstracting with credit is permitted. To copy  
39 -% otherwise, or republish, to post on servers or to redistribute to  
40 -% lists, requires prior specific permission and/or a fee. Request  
41 -% permissions from \href{mailto:Permissions@acm.org}{Permissions@acm.org}. \\  
42 -% \emph{CHI '16}, May 07--12, 2016, San Jose, CA, USA \\  
43 -% ACM xxx-x-xxxx-xxxx-x/xx/xx\ldots \$15.00 \\  
44 -% DOI: \url{http://dx.doi.org/xx.xxxx/xxxxxxx.xxxxxxx}  
45 -% } 8 +\CopyrightYear{2017}
  9 +\setcopyright{acmlicensed}
  10 +\conferenceinfo{OpenSym '17,}{August 23--25, 2017, Galway, Ireland}
  11 +\isbn{978-1-4503-5187-4/17/08}\acmPrice{\$15.00}
  12 +\doi{https://doi.org/10.1145/3125433.3125471}
46 13
47 % Arabic page numbers for submission. Remove this line to eliminate 14 % Arabic page numbers for submission. Remove this line to eliminate
48 % page numbers for the camera ready copy 15 % page numbers for the camera ready copy