[i3eSW] Data about software components

Melissa Wen
1 parent a15978eb
Showing 1 changed file with 18 additions and 14 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -141,10 +141,24 @@ active participants in the deploy operations.
  
 ## Our Continuous Delivery Pipeline
  
+The SPB portal is a system-of-systems with five integrated software projects.
+Colab (www.github.com/colab), a systems integration platform for web
+applications based on a plugin architecture, orchestrates communication 
+among them. For this, we had also to develop specific plugins for each portal
+software component.
+
+<!--- Falta dados do Colab e a soma destes ao total --->
+These software component have different levels of complexity and size. Colab
+has had X commits which represent Y lines of code, Gitlab, 64.446 commits and
+502.597 lines, Noosfero, 14.175 commits and 607.490 lines, Mezuro, 9.007 commits
+and 217.828 lines, and, finally, Mailman with 19.101 commits and 180.871 lines.
+We can thus realize, with only the sum of the integrated projects, we have a
+platform that totals more than 106.729 commits and 1.508.786 lines of code.
+
 ![The SPB Deployment Pipeline](figures/pipeline_3.png)
  
 Figure 1 presents our CD pipeline. It follows a typical deployment pipeline
-[3], adapted to the technical and organizational context of our project and the
+[3], adapted to the technical and organizational complexity of our project and the
 use of OSS best practices. The pipeline started when new code arrived.  A new
 feature might require changes to more than one SPB integrated software project.
 Notice that each one of them could be modified independently. As the code went
@@ -165,19 +179,9 @@ https://www.openhub.net/p/mailman
  
 ### Automated Tests
  
-<!---
-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.
-Os 5 projetos são: Colab, Noosfero, Gitlab, MailMan, and Mezuro.
--->
-
-The SPB portal is a system-of-systems with 5 integrated software projects. Each
-of them, as well as the entire platform, had to be tested. These software
-components have their own test suite. Colab (www.github.com/colab), a systems
-integration platform for web applications based on a plugin architecture,
-orchestrates communication among them. Therefore, we developed specific plugins
-for each portal software component, such as Gitlab (www.gitlab.com) and
-Noosfero (www.noosfero.org). Each plugin also has its own test suite, working
-also as integration tests.
+As a software integration, the entire SPB platform, as well as each of its
+components need to be tested. Futhermore, the plugins developed to integrate a
+component has its own test suite, and this also work as integration tests.
  
 Both unit and integration tests provided us the performance and security needed
 to guarantee the stability of components and the platform. If any test suite
...	...	@@ -141,10 +141,24 @@ active participants in the deploy operations.
141	141
142	142	## Our Continuous Delivery Pipeline
143	143
	144	+The SPB portal is a system-of-systems with five integrated software projects.
	145	+Colab (www.github.com/colab), a systems integration platform for web
	146	+applications based on a plugin architecture, orchestrates communication
	147	+among them. For this, we had also to develop specific plugins for each portal
	148	+software component.
	149	+
	150	+<!--- Falta dados do Colab e a soma destes ao total --->
	151	+These software component have different levels of complexity and size. Colab
	152	+has had X commits which represent Y lines of code, Gitlab, 64.446 commits and
	153	+502.597 lines, Noosfero, 14.175 commits and 607.490 lines, Mezuro, 9.007 commits
	154	+and 217.828 lines, and, finally, Mailman with 19.101 commits and 180.871 lines.
	155	+We can thus realize, with only the sum of the integrated projects, we have a
	156	+platform that totals more than 106.729 commits and 1.508.786 lines of code.
	157	+
144	158	![The SPB Deployment Pipeline](figures/pipeline_3.png)
145	159
146	160	Figure 1 presents our CD pipeline. It follows a typical deployment pipeline
147		-[3], adapted to the technical and organizational context of our project and the
	161	+[3], adapted to the technical and organizational complexity of our project and the
148	162	use of OSS best practices. The pipeline started when new code arrived. A new
149	163	feature might require changes to more than one SPB integrated software project.
150	164	Notice that each one of them could be modified independently. As the code went
...	...	@@ -165,19 +179,9 @@ https://www.openhub.net/p/mailman
165	179
166	180	### Automated Tests
167	181
168		-<!---
169		-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.
170		-Os 5 projetos são: Colab, Noosfero, Gitlab, MailMan, and Mezuro.
171		--->
172		-
173		-The SPB portal is a system-of-systems with 5 integrated software projects. Each
174		-of them, as well as the entire platform, had to be tested. These software
175		-components have their own test suite. Colab (www.github.com/colab), a systems
176		-integration platform for web applications based on a plugin architecture,
177		-orchestrates communication among them. Therefore, we developed specific plugins
178		-for each portal software component, such as Gitlab (www.gitlab.com) and
179		-Noosfero (www.noosfero.org). Each plugin also has its own test suite, working
180		-also as integration tests.
	182	+As a software integration, the entire SPB platform, as well as each of its
	183	+components need to be tested. Futhermore, the plugins developed to integrate a
	184	+component has its own test suite, and this also work as integration tests.
181	185
182	186	Both unit and integration tests provided us the performance and security needed
183	187	to guarantee the stability of components and the platform. If any test suite
...	...