Commit 364bbc8a0c5748cd2082b830745be373bca97515

Authored by Melissa Wen
1 parent dfe4d770

Initial review of process section and small changes in introduction

opensym2017/content/01-introduction.tex
... ... @@ -16,7 +16,7 @@ acquisition of a proprietary solution must be explicitly justified by
16 16 demonstrating that there is no suitable option in the SPB Portal.
17 17  
18 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
  19 +The original codebase was not being developed anymore, and there was a
20 20 large amount of technical debt to overcome. The system was a modified
21 21 version of an existing FOSS platform that was not being developed
22 22 anymore, and the portal maintenance was becoming harder and harder.
... ... @@ -32,7 +32,7 @@ this paper, we present an overview of this new generation of the SPB
32 32 Portal.
33 33  
34 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
  35 +masters students, and approximately 40 undergraduate students (not all of
36 36 them at the same time, though -- graduations and other events triggered
37 37 changes in the team).
38 38  
... ...
opensym2017/content/04-process.tex
1 1 \section{Development Organization and Process}
2 2 \label{sec:process}
3 3  
4   -The SPB members were composed of a variety of professionals with different
5   -levels and skills. Most of them were undergraduate students with major in
6   -software engineering (from 4th semester or upper), hence they could not
7   -dedicate many hours in the project per week. In their daily lives in the
8   -project, they had programming and devops tasks. It is important to highlight
9   -that the students always had the flexibility to negotiate their work hours
10   -during the semester, because we tried to not cause any damage to their grades.
11   -
12   -The development of SPB project required a vast experience and background that
13   -usually undergraduate students do not have yet, for this reason, some senior
14   -developer joined to the project to help with hard issues and to transfer
15   -knowledge to the students. Their main tasks provide solutions for hard
16   -problems, in other words, they worked as a developer. All the senior lived in a
17   -different states spread around Brazil, and all the communication was made via
18   -internet. Finally, those professionals are very skilful and the project could
19   -not afford a full time work for them, as a result, some of them worked
20   -partially on the project.
  4 +The SPB team was composed of a variety of professionals with different levels and skills, where most of them were undergraduate students with major in software engineering (from 4th semester or upper).
  5 +Since the students could not dedicate many hours per week to the project, they always had the flexibility to negotiate their work schedule during the semester in order not to cause any damage to their grades. Their daily work routine in the project included programming and devops tasks.
  6 +
  7 +The development of SPB project required a vast experience and background that usually undergraduate students do not have yet. For this reason, some senior developers have joined to the project to help with hard issues and to transfer knowledge to the students. Their main task was to provide solutions for complex problems, in other words, they worked as a developer. As these professionals are very skillful and the project could not fund a full time work for them, some of them worked partially on the project. In addition, they lived in a different states spread around Brazil which led much of the communication to be made via Internet.
21 8  
22 9 Finally, the last group of actors of this project was composed of employees
23 10 formally working for the Brazilian Government, in the Ministery of Planning,
... ...