03-requirements.tex 6.21 KB

In 2013, the SPB Portal had more than 600 thousand unique visitors, generating
more than 16 million page views with about 50 million hits. By evaluating only
the main projects, there were more than 15 thousand downloads and 4 thousand
messages exchanged in their forums. This data illustrates the potential of the
SPB Portal, even with some 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 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
to guide the SPB portal evolution. In this scenario, the 10 most voted
requirements are, for example:


\item Source code repository with public access.
\item Visit community pages without login.
\item Distributed version control system.
\item Scores of users and developers collaboration.
\item Search software by features.
\item Integration with social networks.
\item Repository for future ideas and requirements.
\item Friendly URL to access a public software community page.
\item User feedback about a public software.
\item Report of the experience about the use of a public software.


  \caption{Technological requirements overview.}

Moreover, there 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.

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:


\item 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.
\item Mailing lists and discussion forums.


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{git: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 software.
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 repositories at GitHub. However, there are not social
networking and CMS features, as well as, other communication resources provided
by that platform.

Also, there are two initiatives in Europe: OSOR and OW2. The Open Source
Observatory (OSOR) is a community hosted in the JoinUp platform powereded 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 is a FOSS community to promote the development of FOSS middleware, generic
business applications, cloud computing platforms and foster a community and
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
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
Publico Regional. From the 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. The user
can create content in the communities (news items, documents, wiki pages), but
all repository is available at the Bitbucket platform.
%http://www.softwarepublico.gob.cl -> https://bitbucket.org/softwarepublico

%TODO: fazer o gancho final para linkar com a seção da arquitetura