Download as
Browse Code »

Commit d8f2396fb52ac3142bdb81b3f352ae3431438037

Authored by Rodrigo Siqueira de Melo
1 parent 7ded138c
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

Review 2

Showing 1 changed file with 36 additions and 16 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @d8f2396
... ... @@ -93,28 +93,34 @@ requirements previously approved.
93 93 mudar em todas as ocorrências de agents por staff, mas checar com o Fabio.
94 94 -->
95 95  
96   -<!-- sugestão: Tira o primeiro challenge e acrescenta um texto no final desta
  96 +In this context, we overcame three distinct challenges: (1) deconstructing
  97 +the widespread belief among government staff that any project in partnership
  98 +with a University is doomed to fail, and (2) dealing with bureaucracies
  99 +involved in the deployment process.
  100 +
  101 +<!-- TODO: explicar o problema, não a solução
  102 +sugestão: Tira o primeiro challenge e acrescenta um texto no final desta
97 103 seção dizendo "no final deu tudo certo: construímos uma ferramenta modular
98 104 (inclui o conteúdo do parágrafo sobre o primeiro challenge) com uma equipe
99 105 heterogênea (coloca a descrição das pessoas) e chegamos a um pacote com
100 106 7 ferramentas blah blah blah
101   --->
102 107  
103   -In this context, we overcame three distinct challenges: (1) finding a system
104   -solution with which government and development team agree, (2) deconstructing
105   -the widespread belief among government staff that any project in partnership
106   -with a University is doomed to fail, and (3) dealing with bureaucracies
107   -involved in the deployment process.
  108 +Siqueira e Melissa:
  109 +Decidir qual era o desafio que a gente queria falar e se vale a pena falar sobre
  110 +eles. Observer que a chamada (1) fala de uma coisa e a expansão da ideia fala
  111 +de outra.
  112 +
  113 +(1) finding a system solution with which government and development team agree,
108 114  
109   -<!-- TODO: explicar o problema, não a solução -->
110 115 To face the first issue, we designed the SPB portal as a CDE with additional
111 116 social features. Due to the complexity of creating such a system from scratch,
112 117 we decided to adapt and integrate existing OSS tools to build a
113 118 system-of-systems [4]. We created a solution that orchestrates multiple
114 119 components and allows us to smoothly provide a unified interface for final
115 120 users, including single sign-on and global searches [1].
  121 +-->
116 122  
117   -Regarding the second problem, our team was not from a typical company,
  123 +To face the first issue, our team was not from a typical company,
118 124 consisting mainly of undergraduate students coordinated by two professors.
119 125 Accordingly, time and resources allocation, accountability, and team
120 126 continuity might be construed as "unprofessional". On the
... ... @@ -178,18 +184,21 @@ https://www.openhub.net/p/mailman
178 184 <!---
179 185 No final do contexto, adicionar um parágrafo final falando que geramos o SPB de forma a integrar 5 sistemas e manter mais de 30 pacotes.
180 186 Os 5 projetos são: Colab, Noosfero, Gitlab, MailMan, and Mezuro.
181   --->
182 187  
183   -The SPB portal is a system-of-systems with 5 integrated software projects. Each
184   -of them had to be tested with its own test suite.
185   -This was not enough, however: we also had to test the platform as a whole. To
186   -do this, we leveraged our choice of Colab (www.github.com/colab) as the
  188 +The SPB portal is a system-of-systems with 5 integrated software projects.
  189 +
  190 +To do this, we leveraged our choice of Colab (www.github.com/colab) as the
187 191 orchestrator in the SPB. Colab is a systems
188 192 integration platform for web applications based on a plugin architecture. In
189 193 SPB, we developed specific plugins
190 194 for each portal software component, such as Gitlab (www.gitlab.com) and
191   -Noosfero (www.noosfero.org). Given that
192   -the plugins also have their own test suites, these suites assume a double role as both
  195 +Noosfero (www.noosfero.org).
  196 +-->
  197 +
  198 +The SPB portal is a system-of-systems, each
  199 +of them had to be tested with its own test suite. This was not enough,
  200 +however: we also had to test the platform as a whole. Given that the plugins
  201 +also have their own test suites, these suites assume a double role as both
193 202 plugin tests and as integration tests.
194 203  
195 204 Both unit and integration tests provided us the performance and security needed
... ... @@ -275,6 +284,13 @@ Ministry leaders and improved the interactions with our team.
275 284  
276 285 ### Responsiveness to Change
277 286  
  287 +<!--
  288 +Every meeting with...
  289 +Paulo:
  290 +Isso era mais no inicio do projeto, e depois nem tanto de fato... mas eh melhor
  291 +refazer para nao ter a pergunta sobre quantas vezes os requisitos mudaram
  292 +-->
  293 +
278 294 Responsiveness was one of the direct benefits of adopting the CD pipeline. The
279 295 ability to react quickly to changes requested by the Ministry was vital
280 296 to the project’s survival for 30 months. Every meeting with the Ministry
... ... @@ -367,6 +383,10 @@ production by the Ministry staff. Second, specific issues of the Ministry
367 383 infrastructure made some validated features not work as expected in the PE.
368 384 That situation gave us arguments to negotiate access to the PE.
369 385  
  386 +<!--
  387 +After understanding it, the Ministry staff helped us negotiate access to a VE
  388 +with the Ministry leaders, creating as an isolated replica of the PE
  389 +-->
370 390 2. _Make project management transparent and collaborative for government
371 391 staff._ Allowing the Ministry staff to track our development process showed them we were fulfilling our commitments.
372 392 They started to interact more actively in the generation of versions and became
... ...