Commit faeb4387dae4762a3493222b9361268436b1d545
1 parent
d2eade6d
Exists in
master
and in
3 other branches
initial version of the Requirements section
Showing
3 changed files
with
71 additions
and
1 deletions
Show diff stats
opensym2017/content/03-requirements.tex
| 1 | \section{Requirements} | 1 | \section{Requirements} |
| 2 | \label{sec:requirements} | 2 | \label{sec:requirements} |
| 3 | 3 | ||
| 4 | -... | 4 | +In 2013, the SPB Portal had more than 600 thousand unique visitors, generating |
| 5 | +more than 16 million page views with about 50 million hits. By evaluating only | ||
| 6 | +the main projects, there were more than 15 thousand downloads and 4 thousand | ||
| 7 | +messages exchanged in their forums. This data illustrates the potential of the | ||
| 8 | +SPB Portal, even with some limitations in the past. | ||
| 9 | + | ||
| 10 | +By preparing the evolution project described in this paper, the Brazilian | ||
| 11 | +government promote 3 events to collect the requirements, in particular from | ||
| 12 | +society point of view: (i) an online form to collect general ideas; (ii) a | ||
| 13 | +face-to-face meeting with society in general; (iii) a workshop to review the | ||
| 14 | +SPB concepts and requirements with IT stockholders from the Brazilian | ||
| 15 | +government and public organization. | ||
| 16 | + | ||
| 17 | +After these 3 rounds discussing the new SPB Portal, Brazilian government listed | ||
| 18 | +about 145 requirements and developed and mind | ||
| 19 | +model\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}} | ||
| 20 | +to guide the SPB portal evolution. In this scenario, the 10 most voted | ||
| 21 | +requirements are: | ||
| 22 | + | ||
| 23 | +\begin{enumerate} | ||
| 24 | + | ||
| 25 | +\item Source code repository with public access. | ||
| 26 | +\item Visit community pages without login. | ||
| 27 | +\item Distributed version control system. | ||
| 28 | +\item Scores of users and developers collaboration. | ||
| 29 | +\item Search software by features. | ||
| 30 | +\item Integration with social networks. | ||
| 31 | +\item Repository for future ideas and requirements. | ||
| 32 | +\item Friendly URL to access a public software community pages. | ||
| 33 | +\item User feedback about a public software. | ||
| 34 | +\item Experience report about the use of a public software. | ||
| 35 | + | ||
| 36 | +\end{enumerate} | ||
| 37 | + | ||
| 38 | +\begin{figure}[hbt] | ||
| 39 | + \centering | ||
| 40 | + \includegraphics[width=\linewidth]{figures/requirements.png} | ||
| 41 | + \caption{Technological requirement overview.} | ||
| 42 | + \label{fig:requirements} | ||
| 43 | +\end{figure} | ||
| 44 | + | ||
| 45 | + | ||
| 46 | +However, there were other requirements based on the experience of the IT | ||
| 47 | +stakeholders from the Brazilian government and from the Brazilian FOSS | ||
| 48 | +community (that UnB and USP were representing too in this project). The new | ||
| 49 | +platform just could work properly if there is a unique authentication to use | ||
| 50 | +the set of tools that could provide features to cover. Moreover, a unified | ||
| 51 | +interface was an important non-functional requirement to make easy the user | ||
| 52 | +experience into the new platform. | ||
| 53 | + | ||
| 54 | +At the first moment, we wish to release a initial version to replace the old | ||
| 55 | +SPB portal. For that, the first version available in production needed to | ||
| 56 | +provide some features: | ||
| 57 | + | ||
| 58 | +\begin{enumerate} | ||
| 59 | + | ||
| 60 | +\item Organized public software catalog. | ||
| 61 | +\item Social network environment (profile for users, software pages, and community pages). | ||
| 62 | +\item Content Management Systems (CMS) features. | ||
| 63 | +\item Web-based Git repository manager with wiki and issue tracking features. | ||
| 64 | +\item Mailing lists and discussion forums. | ||
| 65 | + | ||
| 66 | +\end{enumerate} | ||
| 67 | + | ||
| 68 | +Other requirements also were planned during the conceptual phase of the SPB | ||
| 69 | +evolution project such as an integrated search engine and a web-based source | ||
| 70 | +code static analysis. Therefore, by analyzing all of these requirements, we | ||
| 71 | +propose a technological requirement overview, illustrated in Figure | ||
| 72 | +\ref{fig:requirements} to guide the development of the new SPB Portal once we | ||
| 73 | +have designed this project to be built based on existing FOSS tools. | ||
| 74 | + |
99 KB
45.4 KB