03-requirements.txt: minor reviews

Antonio Terceiro
1 parent 31a7b521
Showing 1 changed file with 65 additions and 63 deletions Show diff stats
opensym2017/content/03-requirements.tex
@@ -8,17 +8,17 @@ messages exchanged in their forums. These data illustrates the potential of the
 SPB Portal, even with several limitations in the past.
 By preparing the evolution project described in this paper, the Brazilian
-government promote 3 events to collect the requirements, in particular from
-society point of view: (i) an on-line form to collect general ideas; (ii) a
+government promoted 3 events to collect the requirements, in particular from
+society point of view: (i) an online form to collect general ideas; (ii) a
 face-to-face meeting with society in general; (iii) a workshop to review the
 SPB concepts and requirements with IT stakeholders from the Brazilian
 government and public organizations.
 After these 3 rounds discussing the new SPB platform, the Brazilian government
 listed about 145 requirements and developed a ``mind
-mapping''\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
+map''\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
 to guide the SPB portal evolution. In this scenario, the 10 most voted
-requirements are, for example:
+requirements were, for example:
 \begin{enumerate}
@@ -43,20 +43,21 @@ requirements are, for example:
 \end{figure}
-Moreover, there were other requirements based on the experience of the IT
+here were other requirements based on the experience of the IT
 stakeholders from the Brazilian government and from the Brazilian FOSS
-community (that UnB and USP were representing too in this project). The new
-platform just could work properly if there is a unique authentication to use
-the provided tools. Additionally, a unified interface was an important
-non-functional requirement to make easy the user experience into the new
-platform.
+community (that UnB and USP were representing too in this project). The
+new platform would only work properly if there is a unique
+authentication to use the provided tools. Additionally, a unified
+interface was an important non-functional requirement to have a better
+user experience in the new platform.
-At the first moment, we wish to release an initial version to replace the old
-SPB portal. For that, the first version must have some features such as:
+At the first moment, we desired to release an initial version that could
+replace the old SPB portal. For that, the first version should have
+features such as:
 \begin{enumerate}
-\item Organized public software catalog.
+\item An organized public software catalog.
 \item Social network environment (profiles for users, software pages, and community pages).
 \item Content Management Systems (CMS) features.
 \item Web-based Git repository manager with wiki and issue tracking features.
@@ -64,39 +65,42 @@ SPB portal. For that, the first version must have some features such as:
 \end{enumerate}
-Other requirements also were planned during the conception phase of the SPB
-evolution project such as an integrated search engine and a web-based source
-code static analysis monitor. Therefore, by analyzing all of these
-requirements, we propose the technological requirements overview, as
-illustrated in Figure \ref{fig:requirements}, to guide the development of the
-new SPB platform. In other words, we have designed the SPB evolution project
-based on existing FOSS tools. However, the integration of several existing
-systems that already was implemented in different programming language and
-frameworks, adding features such as a unique authentication, a unified
-interface, and a search engine, as well as, other back-end features, is not a
-trivial work.
-
-The new SPB platform is fully an integrated environment, as we can see in
-Figure \ref{fig:requirements}, being very advanced comparing to other related
-projects and initiatives. For example, the USA government has a platform
-designed to improve access to the federal government developed
+Other requirements were also planned during the conception phase of the
+SPB evolution project, such as an integrated search engine and a
+web-based source code static analysis monitor. By analyzing all of these
+requirements, we proposed the technological requirements overview
+illustrated in Figure \ref{fig:requirements} to guide the development of
+the new SPB platform. In other words, we have designed the SPB evolution
+project based on existing FOSS tools. However, the integration of
+several existing systems that were already implemented in different
+programming languages and frameworks, adding features such as a
+centralized authentication, unified interface, and a search engine, as
+well as, other back-end features, would require a non-trivial amount of
+work.
+
+The new SPB platform is a fully integrated environment, as we can see in
+Figure \ref{fig:requirements}, being very advanced in comparison with
+related projects and initiatives. For example, the USA government has a
+platform designed to improve access to the federal government developed
 software\footnote{\url{https://code.gov}}.  Code.gov is an interface to
-organize the USA government projects and, in short, make easy that their users
-and developers obtain some information and access their source code
+organize the USA government projects and, in short, make it easy for
+users and developers to obtain information and access their source code
 repositories at GitHub. However, there are not social networking and CMS
-features, as well as, other communication resources provided by that platform.
+features, as well as, other communication resources provided by that
+platform.
 Additionally, there are two initiatives in Europe:
 OSOR\footnote{\url{https://joinup.ec.europa.eu/community/osor}} and
-OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR) is a
-community hosted in the JoinUp platform powered by the European Commission.
-OSOR aims exchanging information, experiences and best practices around FOSS
-solutions for use in public administrations. Summarily, it helps to find a FOSS
-made available by other public administrations, providing access to information
-such as news, events, studies and solutions related to implementation of open
-source software. It also offers forum discussions and community mailing lists,
-but it does not have an integrated source code repository manager and for the
-each project has a link to its own external repository (or its tarball file).
+OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR)
+is a community hosted in the JoinUp platform powered by the European
+Commission.  OSOR aims at exchanging information, experiences and best
+practices around the use of FOSS in the public administration. It helps
+to find a FOSS made available by other public administrations, providing
+access to information such as news, events, studies and solutions
+related to implementation of open source software. It also offers forum
+discussions and community mailing lists, but it does not have an
+integrated source code repository manager and for the each project there
+is a link to its own external repository (or its tarball file).
 %
 OW2 is a FOSS community to promote the development of FOSS middleware, generic
 business applications, cloud computing platforms and foster a community and
@@ -104,33 +108,31 @@ business ecosystem. In short, it aims to support the development, deployment
 and management of distributed applications with a focus on FOSS middleware and
 related development and management tools.
 %
-Moreover, from the European Commission in 2007 until 20011, there were the
-QualiPSo project that aims to provide to FOSS users, developers, and consumers,
-quality resources and expertise on the various topics related to FOSS. The
+Moreover, from the European Commission in 2007 until 20011, there was the
+QualiPSo project that aimed at providing FOSS users, developers, and consumers,
+with quality resources and expertise on the various topics related to FOSS. The
 QualiPSo project also had planned to develop a platform called QualiPSo
 Factory but it was not fully completed.
-In Latin American has an initiative based on the SPB project called ``Software
+In Latin American there is an initiative based on the SPB project called ``Software
 Publico Regional''\footnote{\url{http://softwarepublicoregionalbeta.net}}. From
-the practical point of view, it provides a customized Gitlab instance to share
+a practical point of view, it provides a customized Gitlab instance to share
 the source code and documentation of the project from the involved countries.
 %
-Such as Brazil, Chile has its own portal also called ``Software
-Publico''\footnote{\url{http://www.softwarepublico.gob.cl}}. The user can create
-content in the communities (news items, documents, wiki pages), but all
-repository is available at the Bitbucket
+Like Brazil, Chile has its own portal also called ``Software
+Publico''\footnote{\url{http://www.softwarepublico.gob.cl}}. Users can create
+content in the communities (news items, documents, wiki pages), but
+source code repositories are available at the Bitbucket
 platform\footnote{\url{https://bitbucket.org/softwarepublico}}.
-The Brazilian government needed to evolute the SPB project that exists since
-2005. In 2013, when we started this project, the SPB Portal had about 200
-thousand registered users. We could not just contact these users and ask them
-to register an account at Github as well. Moreover, after the Edward Snowden
-case, the Brazilian government approved a specific law decree (8.135/2013) to
-rule its communication service. Summarily, services like Gmail, Google Drive,
-Dropbox, Live, Outlook, iCloud, as well, Google Groups, Github, and so forth,
-these tools could not be used by a Brazilian public agent as tool for your
-work. To use these kinds of services the Brazilian government needs to provide
-them to itself.  Thus, we developed our own solution to cover all the
-requirements, producing a complete governmental integrated platform for
-collaborative software development.
-
+The Brazilian government needed to evolve the SPB project that
+existedince 2005. In 2013, when we started this project, the SPB Portal
+had about 200 thousand registered users. We could not just contact these
+users and ask them to register an account at Github as well. Moreover,
+after the Edward Snowden case, the Brazilian government approved a
+specific law decree (8.135/2013) to rule its communication services,
+requiring the public administration to host its information systems to
+be provided by itself, what rules out usage of private platforms,
+specially ones provided by foreign companies. We thus developed our own
+solution to cover all the requirements, producing a complete
+governmental integrated platform for collaborative software development.