03-requirements.tex
3.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
\section{Requirements}
\label{sec:requirements}
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 stockholders from the Brazilian
government and public organization.
After these 3 rounds discussing the new SPB Portal, Brazilian government listed
about 145 requirements and developed and mind
model\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:
\begin{enumerate}
\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 pages.
\item User feedback about a public software.
\item Experience report about the use of a public software.
\end{enumerate}
\begin{figure}[hbt]
\centering
\includegraphics[width=\linewidth]{figures/requirements.png}
\caption{Technological requirement overview.}
\label{fig:requirements}
\end{figure}
However, 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 set of tools that could provide features to cover. Moreover, 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 a initial version to replace the old
SPB portal. For that, the first version available in production needed to
provide some features:
\begin{enumerate}
\item Organized public software catalog.
\item Social network environment (profile 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.
\end{enumerate}
Other requirements also were planned during the conceptual phase of the SPB
evolution project such as an integrated search engine and a web-based source
code static analysis. Therefore, by analyzing all of these requirements, we
propose a technological requirement overview, illustrated in Figure
\ref{fig:requirements} to guide the development of the new SPB Portal once we
have designed this project to be built based on existing FOSS tools.