Download as
Browse Code »

Commit 5b2bc0bbfa211add879f8a70a71d612194608c41

Authored by Paulo Meireles
2 parents b7455ac4 8f844bdb
Exists in master

Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles

Showing 1 changed file with 22 additions and 22 deletions   Show diff stats
opensym2017/content/04-researchdesign.tex
  Diff comments   View file @5b2bc0b
1 1 \section{Open Questions}
2 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 9 \textbf{Q1:} \textit{Which strategy could be used to integrate several existing
11   -FLOSS tools to promote the collaborative software development?}
  10 +FLOSS tools to promote a collaborative software development?}
12 11 %
13 12 Based on an extensive list of functional requirements defined by the Brazilian
14   -Federal Government, we selected some FLOSS systems to form our solution,
15   -generating a non-trivial integration among them. We looked for system that
16   -together could provide the largest subset possible of the requirements, and
  13 +Federal Government, we selected some FLOSS systems to compose our solution,
  14 +engineering a nontrivial integration among them. We looked for the systems set
  15 +realizing the largest possible subset of the requirements list. However, we
17 16 were fully aware that we would need to improve those systems in order to
18   -provide the rest. We were also convinced that it would be impossible to provide
  17 +satisfy the remaining requirements. We were also convinced that it would be impossible to satisfy
19 18 all of those requirements with a single tool.
20 19  
21 20 \textbf{Q2:} \textit{How to involve students in real-world projects interacting with
22 21 real customers?}
23 22 %
24 23 Our team was mainly composed of software engineering undergraduate
25   -students, who had the opportunity to interact with senior developers and
26   -designers on the team, as well as with the team of technicians and
27   -managers from the Brazilian Government, and the management team from
28   -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.
  24 +students, who had the opportunity to interact with the UnB managers,
  25 +senior developers, designers, and even with technicians and
  26 +managers from the Brazilian Government.
  27 +For the majority of the students, this was a first professional experience.
  28 +Even though, our development process defined a central role on students participation.
29 29  
30   -\textbf{Q3:} \textit{How to introduce the FLOSS collaborative and agile
31   -practices to governmental development process?}
  30 +textbf{Q3:} \textit{How to introduce collaborative and agile
  31 +practices typical in FLOSS environments in the governmental development process?}
32 32 %
33   -The Brazilian government works based on a very traditional way regarding
34   -software developing, frequently focusing on documents. We have need to convince
35   -them to accept the idea of open scope and empirical development. They have
36   -certain expectations about the development of project according to RUP
  33 +The software development on Brazilian government is based on a very traditional way,
  34 +frequently focusing documentation deliveries. We had to convince
  35 +them to accept the idea of open scope and empirical development. They had
  36 +certain expectations about the project development according to RUP
37 37 (Rational Unified Process) and PMBOK (Project Management Body of Knowledge)
38   -approaches, what not match our work based on agile and FLOSS practices. We have
39   -created strategies that would support different these organizational cultures.
  38 +approaches, which mismatched our work style based on agile and FLOSS practices. So we
  39 +created strategies to conciliate these different organizational cultures within the project.
... ...