Download as
Browse Code »

Commit bee1d5d681ceaabbae065e926e0abca4c35313cc

Authored by Antonio Terceiro
1 parent 31a7b521
Exists in master and in 2 other branches icse2018, siqueira_fix

03-requirements.txt: minor reviews

Showing 1 changed file with 65 additions and 63 deletions   Show diff stats
opensym2017/content/03-requirements.tex
  Diff comments   View file @bee1d5d
... ... @@ -8,17 +8,17 @@ messages exchanged in their forums. These data illustrates the potential of the
8 8 SPB Portal, even with several limitations in the past.
9 9  
10 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 on-line form to collect general ideas; (ii) a
  11 +government promoted 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 13 face-to-face meeting with society in general; (iii) a workshop to review the
14 14 SPB concepts and requirements with IT stakeholders from the Brazilian
15 15 government and public organizations.
16 16  
17 17 After these 3 rounds discussing the new SPB platform, the Brazilian government
18 18 listed about 145 requirements and developed a ``mind
19   -mapping''\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
  19 +map''\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, for example:
  21 +requirements were, for example:
22 22  
23 23 \begin{enumerate}
24 24  
... ... @@ -43,20 +43,21 @@ requirements are, for example:
43 43 \end{figure}
44 44  
45 45  
46   -Moreover, there were other requirements based on the experience of the IT
  46 +here were other requirements based on the experience of the IT
47 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 provided tools. Additionally, a unified interface was an important
51   -non-functional requirement to make easy the user experience into the new
52   -platform.
  48 +community (that UnB and USP were representing too in this project). The
  49 +new platform would only work properly if there is a unique
  50 +authentication to use the provided tools. Additionally, a unified
  51 +interface was an important non-functional requirement to have a better
  52 +user experience in the new platform.
53 53  
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:
  54 +At the first moment, we desired to release an initial version that could
  55 +replace the old SPB portal. For that, the first version should have
  56 +features such as:
56 57  
57 58 \begin{enumerate}
58 59  
59   -\item Organized public software catalog.
  60 +\item An organized public software catalog.
60 61 \item Social network environment (profiles for users, software pages, and community pages).
61 62 \item Content Management Systems (CMS) features.
62 63 \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:
64 65  
65 66 \end{enumerate}
66 67  
67   -Other requirements also were planned during the conception phase of the SPB
68   -evolution project such as an integrated search engine and a web-based source
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{fig: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
  68 +Other requirements were also planned during the conception phase of the
  69 +SPB evolution project, such as an integrated search engine and a
  70 +web-based source code static analysis monitor. By analyzing all of these
  71 +requirements, we proposed the technological requirements overview
  72 +illustrated in Figure \ref{fig:requirements} to guide the development of
  73 +the new SPB platform. In other words, we have designed the SPB evolution
  74 +project based on existing FOSS tools. However, the integration of
  75 +several existing systems that were already implemented in different
  76 +programming languages and frameworks, adding features such as a
  77 +centralized authentication, unified interface, and a search engine, as
  78 +well as, other back-end features, would require a non-trivial amount of
  79 +work.
  80 +
  81 +The new SPB platform is a fully integrated environment, as we can see in
  82 +Figure \ref{fig:requirements}, being very advanced in comparison with
  83 +related projects and initiatives. For example, the USA government has a
  84 +platform designed to improve access to the federal government developed
83 85 software\footnote{\url{https://code.gov}}. Code.gov is an interface to
84   -organize the USA government projects and, in short, make easy that their users
85   -and developers obtain some information and access their source code
  86 +organize the USA government projects and, in short, make it easy for
  87 +users and developers to obtain information and access their source code
86 88 repositories at GitHub. However, there are not social networking and CMS
87   -features, as well as, other communication resources provided by that platform.
  89 +features, as well as, other communication resources provided by that
  90 +platform.
88 91  
89 92 Additionally, there are two initiatives in Europe:
90 93 OSOR\footnote{\url{https://joinup.ec.europa.eu/community/osor}} and
91   -OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR) is a
92   -community hosted in the JoinUp platform powered by the European Commission.
93   -OSOR aims exchanging information, experiences and best practices around FOSS
94   -solutions for use in public administrations. Summarily, it helps to find a FOSS
95   -made available by other public administrations, providing access to information
96   -such as news, events, studies and solutions related to implementation of open
97   -source software. It also offers forum discussions and community mailing lists,
98   -but it does not have an integrated source code repository manager and for the
99   -each project has a link to its own external repository (or its tarball file).
  94 +OW2\footnote{\url{http://ow2.org}}. The Open Source Observatory (OSOR)
  95 +is a community hosted in the JoinUp platform powered by the European
  96 +Commission. OSOR aims at exchanging information, experiences and best
  97 +practices around the use of FOSS in the public administration. It helps
  98 +to find a FOSS made available by other public administrations, providing
  99 +access to information such as news, events, studies and solutions
  100 +related to implementation of open source software. It also offers forum
  101 +discussions and community mailing lists, but it does not have an
  102 +integrated source code repository manager and for the each project there
  103 +is a link to its own external repository (or its tarball file).
100 104 %
101 105 OW2 is a FOSS community to promote the development of FOSS middleware, generic
102 106 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
104 108 and management of distributed applications with a focus on FOSS middleware and
105 109 related development and management tools.
106 110 %
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
  111 +Moreover, from the European Commission in 2007 until 20011, there was the
  112 +QualiPSo project that aimed at providing FOSS users, developers, and consumers,
  113 +with quality resources and expertise on the various topics related to FOSS. The
110 114 QualiPSo project also had planned to develop a platform called QualiPSo
111 115 Factory but it was not fully completed.
112 116  
113   -In Latin American has an initiative based on the SPB project called ``Software
  117 +In Latin American there is an initiative based on the SPB project called ``Software
114 118 Publico Regional''\footnote{\url{http://softwarepublicoregionalbeta.net}}. From
115   -the practical point of view, it provides a customized Gitlab instance to share
  119 +a practical point of view, it provides a customized Gitlab instance to share
116 120 the source code and documentation of the project from the involved countries.
117 121 %
118   -Such as Brazil, Chile has its own portal also called ``Software
119   -Publico''\footnote{\url{http://www.softwarepublico.gob.cl}}. The user can create
120   -content in the communities (news items, documents, wiki pages), but all
121   -repository is available at the Bitbucket
  122 +Like Brazil, Chile has its own portal also called ``Software
  123 +Publico''\footnote{\url{http://www.softwarepublico.gob.cl}}. Users can create
  124 +content in the communities (news items, documents, wiki pages), but
  125 +source code repositories are available at the Bitbucket
122 126 platform\footnote{\url{https://bitbucket.org/softwarepublico}}.
123 127  
124   -The Brazilian government needed to evolute the SPB project that exists since
125   -2005. In 2013, when we started this project, the SPB Portal had about 200
126   -thousand registered users. We could not just contact these users and ask them
127   -to register an account at Github as well. Moreover, after the Edward Snowden
128   -case, the Brazilian government approved a specific law decree (8.135/2013) to
129   -rule its communication service. Summarily, services like Gmail, Google Drive,
130   -Dropbox, Live, Outlook, iCloud, as well, Google Groups, Github, and so forth,
131   -these tools could not be used by a Brazilian public agent as tool for your
132   -work. To use these kinds of services the Brazilian government needs to provide
133   -them to itself. Thus, we developed our own solution to cover all the
134   -requirements, producing a complete governmental integrated platform for
135   -collaborative software development.
136   -
  128 +The Brazilian government needed to evolve the SPB project that
  129 +existedince 2005. In 2013, when we started this project, the SPB Portal
  130 +had about 200 thousand registered users. We could not just contact these
  131 +users and ask them to register an account at Github as well. Moreover,
  132 +after the Edward Snowden case, the Brazilian government approved a
  133 +specific law decree (8.135/2013) to rule its communication services,
  134 +requiring the public administration to host its information systems to
  135 +be provided by itself, what rules out usage of private platforms,
  136 +specially ones provided by foreign companies. We thus developed our own
  137 +solution to cover all the requirements, producing a complete
  138 +governmental integrated platform for collaborative software development.
... ...