Download as
Browse Code »

Commit 5233528fc7d865d3340f28034d1ad7de0d3d16b2

Authored by Paulo Meireles
1 parent f5ba1f66
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

reviewing the Requirements section

Showing 1 changed file with 60 additions and 26 deletions   Show diff stats
opensym2017/content/03-requirements.tex
  Diff comments   View file @5233528
... ... @@ -12,13 +12,13 @@ government promote 3 events to collect the requirements, in particular from
12 12 society point of view: (i) an online form to collect general ideas; (ii) a
13 13 face-to-face meeting with society in general; (iii) a workshop to review the
14 14 SPB concepts and requirements with IT stockholders from the Brazilian
15   -government and public organization.
  15 +government and public organizations.
16 16  
17   -After these 3 rounds discussing the new SPB Portal, Brazilian government listed
18   -about 145 requirements and developed and mind
  17 +After these 3 rounds discussing the new SPB platform, the Brazilian government listed
  18 +about 145 requirements and developed a mind
19 19 model\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
20 20 to guide the SPB portal evolution. In this scenario, the 10 most voted
21   -requirements are:
  21 +requirements are, for example:
22 22  
23 23 \begin{enumerate}
24 24  
... ... @@ -29,16 +29,16 @@ requirements are:
29 29 \item Search software by features.
30 30 \item Integration with social networks.
31 31 \item Repository for future ideas and requirements.
32   -\item Friendly URL to access a public software community pages.
  32 +\item Friendly URL to access a public software community page.
33 33 \item User feedback about a public software.
34   -\item Experience report about the use of a public software.
  34 +\item Report of the experience about the use of a public software.
35 35  
36 36 \end{enumerate}
37 37  
38 38 \begin{figure}[hbt]
39 39 \centering
40 40 \includegraphics[width=\linewidth]{figures/technological-requirements.png}
41   - \caption{Technological requirement overview.}
  41 + \caption{Technological requirements overview.}
42 42 \label{fig:requirements}
43 43 \end{figure}
44 44  
... ... @@ -47,43 +47,77 @@ Moreover, there were other requirements based on the experience of the IT
47 47 stakeholders from the Brazilian government and from the Brazilian FOSS
48 48 community (that UnB and USP were representing too in this project). The new
49 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. Additionally, a unified
  50 +the provided tools. Additionally, a unified
51 51 interface was an important non-functional requirement to make easy the user
52 52 experience into the new platform.
53 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:
  54 +At the first moment, we wish to release an initial version to replace the old
  55 +SPB portal. For that, the first version must have some features such as:
57 56  
58 57 \begin{enumerate}
59 58  
60 59 \item Organized public software catalog.
61   -\item Social network environment (profile for users, software pages, and community pages).
  60 +\item Social network environment (profiles for users, software pages, and community pages).
62 61 \item Content Management Systems (CMS) features.
63 62 \item Web-based Git repository manager with wiki and issue tracking features.
64 63 \item Mailing lists and discussion forums.
65 64  
66 65 \end{enumerate}
67 66  
68   -Other requirements also were planned during the conceptual phase of the SPB
  67 +Other requirements also were planned during the conception phase of the SPB
69 68 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 platform once we
73   -have designed this project to be built based on existing FOSS tools. However, the integration of several existing systems implemented in different programming language and frameworks, providing unique authentication, interface apparency, and search engine, as well as, other back-end features, is not a trivial work.
74   -
75   -
76   -The new SPB platform is fully an integrated environment, 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 on GitHub. However, there are not social networking and CMS features, as well as, other communication resources provided by the platform.
  69 +code static analysis monitor. Therefore, by analyzing all of these
  70 +requirements, we propose the technological requirements overview, as
  71 +illustrated in Figure \ref{fig:requirements}, to guide the development of the
  72 +new SPB platform. In other words, we have designed the SPB evolution project
  73 +based on existing FOSS tools. However, the integration of several existing
  74 +systems that already was implemented in different programming language and
  75 +frameworks, adding features such as a unique authentication, a unified
  76 +interface, and a search engine, as well as, other back-end features, is not a
  77 +trivial work.
  78 +
  79 +The new SPB platform is fully an integrated environment, as we can see in
  80 +Figure \ref{git:requirements}, being very advanced comparing to other related
  81 +projects and initiatives. For example, the USA government has a platform
  82 +designed to improve access to the federal government developed software.
  83 +Code.gov is an interface to organize the USA government projects and, in short,
  84 +make easy that their users and developers obtain some information and access
  85 +their source code repositories at GitHub. However, there are not social
  86 +networking and CMS features, as well as, other communication resources provided
  87 +by that platform.
77 88 %https://code.gov
78 89  
79   -There are two initiatives from Europe: OSOR and OW2. The Open Source Observatory (OSOR) is a community hosted in JoinUp that is a environment powered by the European Commission. OSOR aims exchanging information, experiences and best practices around open source solutions for use in public administrations. Summarily, it helps to find an open source software 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 once for the each project has a link to its own external repository (or its tarball file).
  90 +Also, there are two initiatives in Europe: OSOR and OW2. The Open Source
  91 +Observatory (OSOR) is a community hosted in the JoinUp platform powereded by
  92 +the European Commission. OSOR aims exchanging information, experiences and best
  93 +practices around FOSS solutions for use in public administrations. Summarily,
  94 +it helps to find an FOSS made available by other public administrations,
  95 +providing access to information such as news, events, studies and solutions
  96 +related to implementation of open source software. It also offers forum
  97 +discussions and community mailing lists, but it does not have an integrated
  98 +source code repository manager and for the each project has a link to its own
  99 +external repository (or its tarball file).
80 100 %https://joinup.ec.europa.eu/community/osor
81   -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 facilitate the development, deployment and management of distributed applications with a focus on FOSS middleware and related development and management tools.
  101 +OW2 is a FOSS community to promote the development of FOSS middleware, generic
  102 +business applications, cloud computing platforms and foster a community and
  103 +business ecosystem. In short, it aims to support the development, deployment
  104 +and management of distributed applications with a focus on FOSS middleware and
  105 +related development and management tools.
82 106 %http://ow2.org
83   -Moreover, in the past, there were the QualiPSo project to provide to FOSS users, developers, and consumers, quality resources and expertise on the various topics related to free and open source software. That project have tried to develop a platform called QualiPSo Factory but it was not fully completed.
84   -
85   -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.
  107 +Moreover, from the European Commission in 2007 until 20011, there were the
  108 +QualiPSo project that aims to provide to FOSS users, developers, and consumers,
  109 +quality resources and expertise on the various topics related to FOSS. The
  110 +QualiPSo project also have plained to develop a platform called QualiPSo
  111 +Factory but it was not fully completed.
  112 +
  113 +In Latin American has an initiative based on the SPB project called Software
  114 +Publico Regional. From the practical point of view, it provides a customized
  115 +Gitlab instance to share the source code and documentation of the project from
  116 +the involved countries.
86 117 %http://softwarepublicoregionalbeta.net/
87   -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.
  118 +Such as Brazil, Chile has its own portal also called Software Publico. The user
  119 +can create content in the communities (news items, documents, wiki pages), but
  120 +all repository is available at the Bitbucket platform.
88 121 %http://www.softwarepublico.gob.cl -> https://bitbucket.org/softwarepublico
89 122  
  123 +%TODO: fazer o gancho final para linkar com a seção da arquitetura
... ...