diff --git a/proinfodatadoc/.gitignore b/proinfodatadoc/.gitignore
new file mode 100644
index 0000000000000000000000000000000000000000..2e89efd5b258885ba6d2a8626e7f3332632aabe3
--- /dev/null
+++ b/proinfodatadoc/.gitignore
@@ -0,0 +1,7 @@
+*.aux
+*.log
+*.bbl
+*.blg
+*.toc
+*.pdf
+*~
diff --git a/proinfodatadoc/AUTHORS b/proinfodatadoc/AUTHORS
new file mode 100644
index 0000000000000000000000000000000000000000..f183dd2de0647eaf4b4bef1f2502e5eb951c42bc
--- /dev/null
+++ b/proinfodatadoc/AUTHORS
@@ -0,0 +1,31 @@
+C3SL - Centro de Computacao Cientifica e Software Livre
+
+Agtha Cristina de Nadai
+Adriano da Luz
+Aryane Ast dos Santos
+Bruno Cesar Ribas
+Carlos Carvalho
+Cleide Luzia Bonfim Possamai
+Daniel Weingaertner
+Danilo Kiyoshi Simizu Yorinori
+Diego Giovane Pasqualin
+Eduardo Cunha de Almeida
+Erik Alexandre Pucci
+Fabiano Silva
+Felipe Cys Laskoski
+Guilherme Zasyeki Machado
+Jorge Augusto Meira
+Josiney de Souza
+Juliana Bueno
+Klismann Smoger Mottin
+Luis Carlos Erpen de Bona
+Marcos Castilho
+Marcos Sunye
+Pedro Eugenio Rocha
+Renan Franca De Miranda
+Ricardo Tavares De Oliveira
+Rubens Massayuki Suguimoto
+Thiago Henrique Dos Santos Picharski
+Tiago Rodrigo Kepe
+Victor Tarabola Cortiano
+Vinicius Kwiecien Ruoso
diff --git a/proinfodatadoc/COPYING b/proinfodatadoc/COPYING
new file mode 100644
index 0000000000000000000000000000000000000000..94a9ed024d3859793618152ea559a168bbcbb5e2
--- /dev/null
+++ b/proinfodatadoc/COPYING
@@ -0,0 +1,674 @@
+ GNU GENERAL PUBLIC LICENSE
+ Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+ Preamble
+
+ The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+ The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works. By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users. We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors. You can apply it to
+your programs, too.
+
+ When we speak of free software, we are referring to freedom, not
+price. Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+ To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights. Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+ For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received. You must make sure that they, too, receive
+or can get the source code. And you must show them these terms so they
+know their rights.
+
+ Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+ For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software. For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+ Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so. This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software. The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable. Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products. If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+ Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary. To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+ The precise terms and conditions for copying, distribution and
+modification follow.
+
+ TERMS AND CONDITIONS
+
+ 0. Definitions.
+
+ "This License" refers to version 3 of the GNU General Public License.
+
+ "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+ "The Program" refers to any copyrightable work licensed under this
+License. Each licensee is addressed as "you". "Licensees" and
+"recipients" may be individuals or organizations.
+
+ To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy. The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+ A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+ To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy. Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+ To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies. Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+ An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License. If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+ 1. Source Code.
+
+ The "source code" for a work means the preferred form of the work
+for making modifications to it. "Object code" means any non-source
+form of a work.
+
+ A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+ The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form. A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+ The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities. However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work. For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+ The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+ The Corresponding Source for a work in source code form is that
+same work.
+
+ 2. Basic Permissions.
+
+ All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met. This License explicitly affirms your unlimited
+permission to run the unmodified Program. The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work. This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+ You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force. You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright. Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+ Conveying under any other circumstances is permitted solely under
+the conditions stated below. Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+ 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+ No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+ When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+ 4. Conveying Verbatim Copies.
+
+ You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+ You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+ 5. Conveying Modified Source Versions.
+
+ You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+ a) The work must carry prominent notices stating that you modified
+ it, and giving a relevant date.
+
+ b) The work must carry prominent notices stating that it is
+ released under this License and any conditions added under section
+ 7. This requirement modifies the requirement in section 4 to
+ "keep intact all notices".
+
+ c) You must license the entire work, as a whole, under this
+ License to anyone who comes into possession of a copy. This
+ License will therefore apply, along with any applicable section 7
+ additional terms, to the whole of the work, and all its parts,
+ regardless of how they are packaged. This License gives no
+ permission to license the work in any other way, but it does not
+ invalidate such permission if you have separately received it.
+
+ d) If the work has interactive user interfaces, each must display
+ Appropriate Legal Notices; however, if the Program has interactive
+ interfaces that do not display Appropriate Legal Notices, your
+ work need not make them do so.
+
+ A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit. Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+ 6. Conveying Non-Source Forms.
+
+ You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+ a) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by the
+ Corresponding Source fixed on a durable physical medium
+ customarily used for software interchange.
+
+ b) Convey the object code in, or embodied in, a physical product
+ (including a physical distribution medium), accompanied by a
+ written offer, valid for at least three years and valid for as
+ long as you offer spare parts or customer support for that product
+ model, to give anyone who possesses the object code either (1) a
+ copy of the Corresponding Source for all the software in the
+ product that is covered by this License, on a durable physical
+ medium customarily used for software interchange, for a price no
+ more than your reasonable cost of physically performing this
+ conveying of source, or (2) access to copy the
+ Corresponding Source from a network server at no charge.
+
+ c) Convey individual copies of the object code with a copy of the
+ written offer to provide the Corresponding Source. This
+ alternative is allowed only occasionally and noncommercially, and
+ only if you received the object code with such an offer, in accord
+ with subsection 6b.
+
+ d) Convey the object code by offering access from a designated
+ place (gratis or for a charge), and offer equivalent access to the
+ Corresponding Source in the same way through the same place at no
+ further charge. You need not require recipients to copy the
+ Corresponding Source along with the object code. If the place to
+ copy the object code is a network server, the Corresponding Source
+ may be on a different server (operated by you or a third party)
+ that supports equivalent copying facilities, provided you maintain
+ clear directions next to the object code saying where to find the
+ Corresponding Source. Regardless of what server hosts the
+ Corresponding Source, you remain obligated to ensure that it is
+ available for as long as needed to satisfy these requirements.
+
+ e) Convey the object code using peer-to-peer transmission, provided
+ you inform other peers where the object code and Corresponding
+ Source of the work are being offered to the general public at no
+ charge under subsection 6d.
+
+ A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+ A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling. In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage. For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product. A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+ "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source. The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+ If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information. But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+ The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed. Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+ Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+ 7. Additional Terms.
+
+ "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law. If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+ When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it. (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.) You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+ Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+ a) Disclaiming warranty or limiting liability differently from the
+ terms of sections 15 and 16 of this License; or
+
+ b) Requiring preservation of specified reasonable legal notices or
+ author attributions in that material or in the Appropriate Legal
+ Notices displayed by works containing it; or
+
+ c) Prohibiting misrepresentation of the origin of that material, or
+ requiring that modified versions of such material be marked in
+ reasonable ways as different from the original version; or
+
+ d) Limiting the use for publicity purposes of names of licensors or
+ authors of the material; or
+
+ e) Declining to grant rights under trademark law for use of some
+ trade names, trademarks, or service marks; or
+
+ f) Requiring indemnification of licensors and authors of that
+ material by anyone who conveys the material (or modified versions of
+ it) with contractual assumptions of liability to the recipient, for
+ any liability that these contractual assumptions directly impose on
+ those licensors and authors.
+
+ All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10. If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term. If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+ If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+ Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+ 8. Termination.
+
+ You may not propagate or modify a covered work except as expressly
+provided under this License. Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+ However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+ Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+ Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License. If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+ 9. Acceptance Not Required for Having Copies.
+
+ You are not required to accept this License in order to receive or
+run a copy of the Program. Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance. However,
+nothing other than this License grants you permission to propagate or
+modify any covered work. These actions infringe copyright if you do
+not accept this License. Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+ 10. Automatic Licensing of Downstream Recipients.
+
+ Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License. You are not responsible
+for enforcing compliance by third parties with this License.
+
+ An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations. If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+ You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License. For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+ 11. Patents.
+
+ A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based. The
+work thus licensed is called the contributor's "contributor version".
+
+ A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version. For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+ Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+ In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement). To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+ If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients. "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+ If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+ A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License. You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+ Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+ 12. No Surrender of Others' Freedom.
+
+ If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all. For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+ 13. Use with the GNU Affero General Public License.
+
+ Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work. The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+ 14. Revised Versions of this License.
+
+ The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time. Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+ Each version is given a distinguishing version number. If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation. If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+ If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+ Later license versions may give you additional or different
+permissions. However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+ 15. Disclaimer of Warranty.
+
+ THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. Limitation of Liability.
+
+ IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+ 17. Interpretation of Sections 15 and 16.
+
+ If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Programs
+
+ If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+ To do so, attach the following notices to the program. It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+ <one line to give the program's name and a brief idea of what it does.>
+ Copyright (C) <year> <name of author>
+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+ If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+ <program> Copyright (C) <year> <name of author>
+ This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+ This is free software, and you are welcome to redistribute it
+ under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+ You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+ The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library. If this is what you want to do, use the GNU Lesser General
+Public License instead of this License. But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.
diff --git a/proinfodatadoc/func_e_requi/Makefile b/proinfodatadoc/func_e_requi/Makefile
new file mode 100644
index 0000000000000000000000000000000000000000..99fbe0aacfc3c8845493f01b12553f59a2ac8ce1
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/Makefile
@@ -0,0 +1,6 @@
+all:
+ pdflatex relatorio
+ pdflatex relatorio
+
+clean:
+ rm -f *.aux *.log *.bbl *.blg *.toc *~
diff --git a/proinfodatadoc/func_e_requi/README b/proinfodatadoc/func_e_requi/README
new file mode 100644
index 0000000000000000000000000000000000000000..94f115d079961cefef9b3bde46ea831fe8d354a0
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/README
@@ -0,0 +1,3 @@
+Este documento tem como objetivo fornecer informações sobre funcionalidades
+e requisitos do projeto PROINFODATA
+
diff --git a/proinfodatadoc/func_e_requi/agente.tex b/proinfodatadoc/func_e_requi/agente.tex
new file mode 100644
index 0000000000000000000000000000000000000000..3b97354263042c7a891e7fd92e5e22d82cfe303b
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/agente.tex
@@ -0,0 +1,92 @@
+% Escrever sobre o agente
+\section{Sistema de Coleta}
+
+O Sistema de Coleta é responsável por coletar os dados das escolas e
+armazená-los no servidor. Os dados são gerados nas escolas pelo Agente
+de Coleta, copiados para o servidor central através do
+uso de um \textit{Web Service} e então armazenados com o auxílio do Sistema
+de Armazenamento.
+
+O método de coleta de dados é baseado no esquema de cliente-servidor, onde
+o cliente é um agente de coleta instalado nas máquinas das escolas e o servidor
+é o receptor de dados, localizado em uma central.
+
+O Agente de Coleta é o aplicativo instalado nas escolas\footnote{O processo
+de instalação é descrito no Manual do Usuário, encontrado no portal do
+projeto, na seção Documentação.}. Ele é composto por três módulos:
+geração do inventário do sistema~\ref{sub:xml}, sistema de
+comunicação com o servidor~\ref{sub:webservice} e sistema de atualização
+automática~\ref{sub:autoupdate}.
+
+\subsection{Geração de Arquivo de Inventário}
+\label{sub:xml}
+
+O arquivo de inventário reúne informações relevantes sobre a máquina e seu
+uso na escola. Entre elas:
+
+\begin{itemize}
+ \item Código do INEP da escola;
+ \item Disco: modelo, capacidade e espaço utilizado;
+ \item Quantidade de memória;
+ \item Modelo do Processador;
+ \item Sistema Operacional: kernel e distribuição;
+ \item MAC Address;
+ \item Carga da máquina: dowload e upload;
+\end{itemize}
+
+Em sua versão para Linux, essas informações são coletadas da máquina com a
+utilização de \textit{scripts} feitos na linguagem \textit{Shell Script} e
+armazenados localmente em um arquivo no formato XML (EXtensible Markup
+Language). Todas as distribuições Linux mais comuns apresentam suporte
+para a linguagem Shell e por este motivo ela foi escolhida para esta tarefa.
+
+A versão Windows desse módulo foi desenvolvida em \textit{Python}, cujo
+interpretador foi integrado com o instalador do agente.
+
+\subsection{Comunicação Cliente-Servidor}
+\label{sub:webservice}
+
+No projeto, o uso de Web Services está relacionado aa comunicação com o
+servidor. Web Services provêem meios padronizados de interoperabilidade entre diferentes
+aplicativos, que executam em várias plataformas e/ou ambientes. São
+caracterizados por serem interoperáveis e extensíveis pois são desenvolvidos em
+Extensible Markup Language (XML). Proporcionam mecanismos de autenticação,
+transferência de binários, encriptação dos dados, certificados digitais,
+descrição de recursos, além de utilizarem o
+Hipertext Transfer Protocol (HTTP) como protocolo de transporte, o
+que permite a conexão e transferência de dados com o servidor mesmo quando o
+cliente dispõe de um \textit{firewall} ou \textit{proxy}.
+
+No cliente, o \textit{Web Service} foi escrito na linguagem C (em ambas as
+versões, Linux e Windows), ao passo que no servidor a linguagem utilizada
+foi Java.
+
+O servidor \textit{Web Service} agrega os serviços de recepção e validação
+dos dados coletados, além da geração do pacote de instalação do agente e
+utiliza como ferramentas de apoio o
+Tomcat\footnote{http://tomcat.apache.org/} e o
+Axis\footnote{http://ws.apache.org/axis/}.
+
+\subsection{Atualização Automática}
+\label{sub:autoupdate}
+
+O agente de coleta foi preparado para se atualizar automaticamente quando
+necessário. Essa medida é muito importante para eventuais correções e
+principalmente adição de novas funcionalidades, sem que seja necessária
+intervenção manual nas escolas.
+
+O processo acontece da seguinte maneira:
+
+\begin{itemize}
+\item Antes do envio dos dados, o agente de coleta ativa se comunica com o
+servidor, através do \textit{Web Service}
+para identificar qual a versão do agente mais atual disponível;
+\item Se a versão do agente da escola estiver desatualizada em relação à versão
+do servidor, o processo de atualização automática é iniciado;
+\item O agente localiza o novo pacote no servidor e baixa na máquina da
+escola as atualizações necessárias;
+\item O agente de coleta descompacta o pacote atualizado, substitui os
+arquivos da versão anterior e pode assim modificar configurações locais,
+implementar novas funcionalidades ou corrigir problemas.
+\end{itemize}
+
diff --git a/proinfodatadoc/func_e_requi/bd.tex b/proinfodatadoc/func_e_requi/bd.tex
new file mode 100644
index 0000000000000000000000000000000000000000..95c9bdd9abab45cd03f3e202cc9b707830b9f873
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/bd.tex
@@ -0,0 +1,82 @@
+% Escrever sobre o BD
+\\
+\\
+\\
+\\
+\section{Banco de Dados}
+
+O sistema de banco de dados do Proinfodata foi desenvolvido a partir de uma
+arquitetura típica de armazenamento de dados em grande escala chamado Data
+Warehouse (DW). O objetivo desta arquitetura é otimizar as operações de
+leitura e escrita, favorecendo as operações de análise de dados.
+
+Uma arquitetura de DW é composta basicamente de três etapas: carregamento, armazenamento e leitura
+de dados. O objetivo desta divisão em etapas é aumentar o desempenho global do sistema onde
+operações de características diferentes (i.e., escrita, leitura) são direcionadas para estruturas diferentes.
+
+Outro objetivo no uso dessa divisão é dar versatilidade ao sistema de armazenamento em que cada
+divisão possa fazer uso da tecnologia mais apropriada independente das demais. Neste contexto, será
+possível a substituição de uma tecnologia empregada por outra sem gerar impacto no resto do sistema.
+
+Nesta proposta dividimos as três etapas em dois bancos de dados distintos
+um banco de dados temporário e outro de histórico (figura ~\ref{fig:estrutura}).
+
+\begin{figure}[h]
+\centering
+\includegraphics[scale=0.50]{estrutura.png}
+\caption{Estrutura do banco de dados}
+\label{fig:estrutura}
+\end{figure}
+
+O banco de dados temporário (ou Staging area) é responsável por receber as conexões do Servidor Web
+e consolidar os dados. A Staging area implementa a etapa de carregamento de dados.
+
+O banco de dados de histórico, ou DW propriamente dito, é responsável por ler, armazenar e consolidar
+as informações da Staging area. O DW implementa a etapa de armazenamento de dados.
+
+A etapa de leitura de dados foi implementada através de Data Marts (DM) onde cada DM é
+desenvolvido de acordo com sub-conjuntos de relatórios específicos (e.g., uso, inventário, auditoria, etc).
+
+O Banco de Dados foi implementado usando tecnologia baseada em código aberto, no nosso caso, o
+sistema gerenciador de banco de dados (SGBD) PostgreSQL.
+
+\subsection{Staging Area}
+
+A Staging Area é um Banco de dados que receberá as conexões do servidor web para escrita dos dados
+coletados durante o dia, conforme política de conexão entre escolas e servidor web. Esse banco
+tem seus dados excluídos logo após a coleta diária que será realizada pelo DW. O objetivo da Staging
+area é suportar duas operações muito custosas sem impactar a geração e leitura de relatórios. As duas
+operações são: conexão ao banco de dados e escrita dos dados. Conexões são operações custosas para
+o banco de dados e neste projeto medimos aproximadamente 200.000 conexões por dia, cada uma escrevendo
+dados individualmente e paralelamente.
+
+\subsection{Data Warehouse}
+
+O Data Warehouse é o Banco de dados responsável por armazenar todo o histórico de dados do projeto. O
+DW irá ler a Staging area onde os dados são carregados, uma vez ao dia em horário pré
+determinado. O DW possui uma modelagem de dados direcionada para operações de leitura de fácil
+entendimento e grande desempenho.
+
+\subsection{Data Marts}
+
+Os Data Mars são sub-conjuntos de dados do DW. Esses sub-conjuntos serão determinados conforme o
+interesse das consultas. O objetivo dos DMs é aumentar o desempenho global, criando estruturas
+específicas para cada universo de relatórios, como por exemplo: Inventário, Uso, Auditoria e etc.
+
+\subsection{Modelagem do Banco}
+
+O que torna o Data Warehouse um sistema de alto desempenho é que as informações que se situam em
+vários sistemas serão reunidas em um banco de dados de forma dimensional.
+
+Neste modelo as tabelas são desnormalizadas buscando aumentar o desempenho, ao contrário da
+modelagem relacional onde tabelas são normalizadas para evitar redundância. O aumento do
+desempenho é devido ao menor uso de operações de junção nas consultas.
+
+O modelo de dados dimensional é composto por dois tipos de tabelas: tabelas de dimensão e tabelas de
+fatos. A tabela de dimensão armazena os dados descritivos (e.g., escola, endereço, etc). A tabela de fatos
+armazena as transações (e.g., uso, carga da rede, etc).
+
+Estas tabelas podem ser modeladas de duas formas: estrela ou floco de neve que é similar ao estrela
+onde as dimensões são normalizadas. Nesse projeto usamos o modelo dimensional estrela
+que possui melhor desempenho.
+
diff --git a/proinfodatadoc/func_e_requi/capa.png b/proinfodatadoc/func_e_requi/capa.png
new file mode 100644
index 0000000000000000000000000000000000000000..367fa40fb08eff0544501d1ebff1c6b5b74b3fc9
Binary files /dev/null and b/proinfodatadoc/func_e_requi/capa.png differ
diff --git a/proinfodatadoc/func_e_requi/consideracoes.tex b/proinfodatadoc/func_e_requi/consideracoes.tex
new file mode 100644
index 0000000000000000000000000000000000000000..137f2e73bda31a3a5434027afc38bc93b95374b5
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/consideracoes.tex
@@ -0,0 +1,2 @@
+% Escrever considerações/conclusão sobre o documento
+\section{Considerações}
diff --git a/proinfodatadoc/func_e_requi/estrutura.png b/proinfodatadoc/func_e_requi/estrutura.png
new file mode 100644
index 0000000000000000000000000000000000000000..a2d6ab88fc360cc6c1759aaddf54555dc6ad2bc5
Binary files /dev/null and b/proinfodatadoc/func_e_requi/estrutura.png differ
diff --git a/proinfodatadoc/func_e_requi/here.sty b/proinfodatadoc/func_e_requi/here.sty
new file mode 100755
index 0000000000000000000000000000000000000000..869e566a1b408558c39956d7c1103ceb6e0ff661
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/here.sty
@@ -0,0 +1,152 @@
+%% Save file as: HERE.STY Source: FILESERV@SHSU.BITNET
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\iffalse
+ here.sty
+ %%%%%%%%%%
+ here.sty gives environments such as figure and table a [H] option
+ which means `PUT IT HERE'. As opposed to the standard [h] option which
+ means `You may put it here if you wish'.
+
+ David Carlisle
+ carlisle@uk.ac.man.cs
+ 13 September 1991
+\fi
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%
+% If you have Mittelbach's doc.sty, this file may be formatted with a
+% command like: latex here.sty
+% (You do not need doc.sty to {\em use} this style.)
+%
+% To create a faster loading .sty file, copy this file to here.doc
+% Then remove all the lines beginning with a `%' from the .sty file. This
+% may be done with docstrip.tex, or your text editor. The following two
+% lines may also be deleted from the .sty file.
+\ifcat a\noexpand @\let\next\relax\else\def\next{%
+ \documentstyle[here,doc]{article}\MakePercentIgnore}\fi\next
+%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% \textwidth=365pt ^^A Allow macrocode text with 75 columns.
+% \CodelineIndex ^^A Code lines numbered.
+% \DisableCrossrefs ^^A No Cross references.
+%
+% \title{here.sty}
+% \author{D. P. Carlisle}
+% \date{13 Sept 1991}
+% \begin{document}
+% \maketitle
+% \begin{abstract}
+% \verb|here.sty| gives environments such as {\tt figure} and {\tt table} a
+% {\tt [H]} option which means `PUT IT HERE'. As opposed to the standard
+% {\tt [h]} option which means `You may put it here if you wish'.%
+% \end{abstract}
+%
+% \begin{figure}[H]
+% This figure will not float, even if this causes a bad page break.
+% \caption{It may be captioned as usual.}
+% \end{figure}
+%
+% Many people have problems with \LaTeX's floating environments. A common
+% complaint is that all the environments appear at the end of the document
+% (or chapter). Many users try to correct this behaviour by using the {\tt
+% [h]} option. Incorect use of this option, in particular using just {\tt
+% [h]} rather than a more liberal option such as {\tt [hp]} actually makes
+% the problem worse!
+%
+% \LaTeX\ will only position a float (even one with the {\tt [h]} option)
+% in a position which does not violate the rules for float placement set by
+% the document style. These rules are determined by the following
+% parameters:\\
+% \begin{tabular}{ll}
+% \verb|\c@topnumber|& Number of floats allowed at the top of a
+% column.\\
+% \verb|\topfraction|& Fraction of column that can be devoted to
+% floats.\\
+% \verb|\c@dbltopnumber|\\ \verb|\dbltopfraction|& Same as above, but for
+% double-column floats.\\
+% \verb|\c@bottomnumber|\\ \verb|\bottomfraction|& Same as above for
+% bottom of page.\\
+% \verb|\c@totalnumber|& Number of floats allowed in a single column,\\
+% & including in-text floats.\\
+% \verb|\textfraction|& Minimum fraction of column that must contain
+% text.\\
+% \verb|\floatpagefraction|& Minimum fraction of page that must be taken
+% up by\\& float page.
+% \end{tabular}%
+%
+% The default settings (in \verb|article.doc| for {\tt article} style) for
+% these parameters make it difficult to set floats if the document has a
+% lot of small floats. The result is that \LaTeX\ `holds them back' in the
+% hope of finding a better place later. At the end of the document (or at a
+% \verb|\clearpage|) it gives up and outputs all the remaining floats.
+%
+% It may be seen from the above paragraph that the `correct' way to handle
+% float problems is to write a style file modifying these parameters,
+% however for many purposes, authors to not want a float at all, they just
+% use the {\tt figure} or {\tt table} environments to get the correct
+% spacing, and a counter that may be referenced. This style option
+% provides an easy solution in this case. If the {\tt [H]} option is
+% specified, the environment will not float even if it causes a bad page
+% break, or breaks the rules specified in the above parameters. The main
+% drawback is that if the [H] option is used in one figure, and the
+% following figure uses the {\tt [t]} option, then the second figure may
+% float in front of the first.
+%
+% Note that the {\tt [H]} should not be used in conjunction with the other
+% options. {\tt [Htp]} is not allowed by this style. The {\tt h} option may
+% still be used, so {\tt [htp]} is OK.
+% \typeout{End of the Introduction and Examples.}
+% \typein[\answer]%
+% {Do you want an annotated listing of the macro definitions (y/n) ?}
+% \def\next{y}\ifx\answer\next\else\expandafter\stop\fi
+%
+% \section{The Macros}
+% First we make sure that this file is only loaded once.
+% \begin{macrocode}
+\ifx\@Hxfloat\@Hundef\else\expandafter\endinput\fi
+% \end{macrocode}
+%
+% \begin{macro}{\@Hxfloat}
+% Now we can save the original version of \verb|\@xfloat|.
+% \begin{macrocode}
+\let\@Hxfloat\@xfloat
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\@xfloat}
+% The new version of \verb|@xfloat| looks for a \verb|[H]| argument.
+% If it is present \verb|\@HHfloat| is called, otherwise the original macro
+% (renamed to \verb|\@Hfloat|) is called.
+% \begin{macrocode}
+\def\@xfloat#1[{\@ifnextchar{H}{\@HHfloat{#1}[}{\@Hxfloat{#1}[}}
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\@HHfloat}
+% First gobble the \verb|[H]|. Note that {\tt H} should not be used in
+% conjunction with the other placement options, nor as the value of the
+% default placement, as set in \verb|\fps@|{\it type}.
+% \begin{macrocode}
+\def\@HHfloat#1[H]{%
+% \end{macrocode}
+% Locally redefine the end of the environment.
+% \begin{macrocode}
+\expandafter\let\csname end#1\endcsname\end@Hfloat
+% \end{macrocode}
+% Add the vertical space, and define \verb|\caption|. Also reset
+% \verb|\parindent| for compatibility with the standard {\tt [h]} option.
+% \begin{macrocode}
+\vskip\intextsep\def\@captype{#1}\parindent\z@
+% \end{macrocode}
+% The final \verb|\ignorespaces| is needed to gobble any spaces or newlines
+% after the {\tt[H]} tokens.
+% \begin{macrocode}
+\ignorespaces}
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\end@Hfloat}
+% Add the same vertical space as would be added by a float placed with
+% {\tt[h]}.
+% \begin{macrocode}
+\def\end@Hfloat{\vskip \intextsep}
+% \end{macrocode}
+% \end{macro}
+% \end{document}
+
diff --git a/proinfodatadoc/func_e_requi/id.tex b/proinfodatadoc/func_e_requi/id.tex
new file mode 100644
index 0000000000000000000000000000000000000000..07e64a0651884ff42528b1985375c627fb533edf
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/id.tex
@@ -0,0 +1,2 @@
+% descrever projeto, cliente e coordenadores
+\section{Identificação do Documento}
diff --git a/proinfodatadoc/func_e_requi/intro.tex b/proinfodatadoc/func_e_requi/intro.tex
new file mode 100644
index 0000000000000000000000000000000000000000..0a922a62d56bf6830107e48868453f03b21e70de
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/intro.tex
@@ -0,0 +1,5 @@
+\section{Introdução}
+
+Este documento tem o objetivo de apresentar as funcionalidades e requisitos do
+projeto Monitoramento Automático dos Laboratórios das Escolas Públicas
+Brasileiras.
diff --git a/proinfodatadoc/func_e_requi/objetivos.tex b/proinfodatadoc/func_e_requi/objetivos.tex
new file mode 100644
index 0000000000000000000000000000000000000000..2f80327ce824970744ad236f1ea32d162d0b0205
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/objetivos.tex
@@ -0,0 +1,2 @@
+% Objetivo do documento, breve explicação sobre a estrutura deste.
+\section{Objetivos}
diff --git a/proinfodatadoc/func_e_requi/observacoes.tex b/proinfodatadoc/func_e_requi/observacoes.tex
new file mode 100644
index 0000000000000000000000000000000000000000..475bfa9f3baeab7b35cffa08c56a70247bda9257
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/observacoes.tex
@@ -0,0 +1,2 @@
+% Escrever observacoes, se houverem
+%\section{Observações}
diff --git a/proinfodatadoc/func_e_requi/portal.tex b/proinfodatadoc/func_e_requi/portal.tex
new file mode 100644
index 0000000000000000000000000000000000000000..396e46544e2a3d69f80f7d49347d72cfc47d4243
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/portal.tex
@@ -0,0 +1,210 @@
+% Escrever sobre o portal
+\section{Portal}
+
+O Portal do PROINFODATA é o meio pelo qual as informações coletadas das escolas
+pelo Agente e armazenadas no Banco de Dados são organizadas e apresentadas. O
+Portal possui três módulos principais (além da tela inicial):
+Instalação~\ref{sub:inst}, Acompanhamento~\ref{sub:acom} e
+Documentação~\ref{sub:doc}.
+
+\subsection{Instalação}
+\label{sub:inst}
+
+Este módulo permite ao usuário (técnicos e responsáveis das escolas) fazer o
+\textit{download} do instalador do Agente PROINFODATA, em duas versões: uma para
+sistemas Linux; outra para Windows.
+
+Na versão para Linux, o usuário deverá informar, na própria página \textit{web},
+o INEP da escola e, caso exista, as informações do \textit{proxy}. Em seguida, o
+usuário deverá clicar em "Validar" para ser validado pelo servidor: se o INEP
+estiver correto (isto é, constar no Banco de Dados, cujos valores são
+atualizados a partir do \textit{Web Service} do MEC), serão apresentadas na tela
+as informações da respectiva escola, em conjunto com as configurações digitadas
+do \textit{proxy}. O usuário então deverá confirmar as informações, para então o
+servidor gerar um pacote de instalação (em \textit{Shell Script}) que conterá o
+Agente com as configurações adequadas.
+
+Na versão para Windows, o usuário deverá baixar o respectivo instalador indicado
+na página e executá-lo. Durante a execução, o usuário deverá confirmar as
+informações de INEP e proxy, que serão verificadas pelo instalador através do
+servidor.
+
+\subsection{Acompanhamento}
+\label{sub:acom}
+
+Este módulo agrega e apresenta as informações coletadas pelo Agente instalado
+nas escolas através de gráficos e relatórios contendo dados específicos.
+
+Esta seção está organizada pela tela inicial, da Busca Rápida, pelo menu
+contendo os diferentes gráficos e pelo projeto ao qual a máquina monitorada está
+vinculada.
+
+Os gráficos com informações diferenciadas são agregados hierarquicamente por
+país, região, estado e cidade\footnote{Para navegar pelos níveis da hierarquia
+basta clicar na barra desejada, no gráfico de barras. No último nível é gerado
+o relatório por cidade.}, mostram os dados do projeto que estiver selecionado no
+módulo de Acompanhamento e estão organizadas nas seguintes diferentes páginas:
+
+\begin{itemize}
+ \item Página de Disponibilidade - acompanhamento das máquinas das escolas
+que possuem o Agente instalado:
+ \begin{itemize}
+ \item Gráfico de Barras: total absoluto de máquinas com o agente
+instalado na data atual (por país, região, estado e cidade).
+ \item Pizza: percentual das máquinas com o agente instalado na data
+atual (por país, região, estado e cidade).
+ \item Linha: comparativo do total de máquinas com o agente instalado
+nos últimos seis meses (por país, região, estado e cidade).
+ \item Legenda:
+ \begin{itemize}
+\item Sinalização verde: total de máquinas cuja última conexão com o servidor
+ocorreu a menos de 10 dias.
+\item Sinalização amarela: total de máquinas cuja última conexão com o servidor
+ocorreu entre 11 e 30 dias.
+\item Sinalização vermelha: total de máquinas cuja última conexão com o servidor
+ocorreu há mais de 30 dias.
+ \end{itemize}
+ \item Relatório gerado no último nível: ao clicar no gráfico de
+barras, o sistema disponibiliza um relatório, em formato PDF, com dados sobre os
+contatos que a máquina da escola realizou com o servidor central: identificação
+da máquina, data do último contato com o servidor central, quantidade de dias
+desde o último contato e quantidade de contatos realizados no mês.
+ \end{itemize}
+
+% ------------------------------------------------------------------------------
+
+ \item Página de Inventário - relação das máquinas com o Agente PROINFODATA
+instalado:
+ \begin{itemize}
+ \item Gráfico de Barras: total de máquinas com o agente instalado na
+data atual (por país, região, estado e cidade).
+ \item Linha: comparativo do total de máquinas com o agente instalado
+nos últimos seis meses (por país, região, estado e cidade).
+ \item Legenda:
+ \begin{itemize}
+\item Sinalização verde: total de máquinas com o Agente instalado.
+ \end{itemize}
+ \item Relatório gerado no último nível: ao clicar no gráfico de
+barras, o sistema disponibiliza um relatório, no formato PDF, sobre o inventário
+de cada máquina instalada: sistema operacional, processador, memória e disco.
+ \end{itemize}
+
+% ------------------------------------------------------------------------------
+
+ \item Página de Auditoria $\to$ Parque computacional instalado - relação das
+máquinas com e sem o Agente instalado (previstas segundo informações do MEC):
+ \begin{itemize}
+ \item Gráfico de Barras: total absoluto de máquinas com e sem o
+agente instalado na data atual (por país, região, estado e cidade).
+ \item Pizza: percentual das máquinas com e sem o agente instalado na
+data atual (por país, região, estado e cidade).
+ \item Linha: comparativo do total de máquinas com e sem o agente
+instalado nos últimos seis meses (por país, região, estado e cidade).
+ \item Legenda:
+ \begin{itemize}
+\item Sinalização verde: total de máquinas com o agente de coleta instalado.
+\item Sinalização roxa: total de máquinas sem o agente de coleta instalado.
+ \end{itemize}
+ \item Relatórios gerados no último nível: ao clicar na barra verde
+do gráfico de barras, o sistema disponibiliza a relação de quantidade de
+máquinas disponibilizadas pelo MEC e quantidade de máquinas com o agente de
+coleta instalado. Ao clicar na barra roxa do gráfico de barras, o sistema
+disponibiliza a relação das escolas que não possuem nenhuma máquina com o agente
+de coleta instalado.
+ \end{itemize}
+
+% ------------------------------------------------------------------------------
+
+ \item Página de Auditoria $\to$ Alteração de inventário - relação das
+máquinas que sofreram alteração maior que 10\% do disco ou da memória:
+ \begin{itemize}
+ \item Gráfico de Barras: total absoluto de máquinas com alteração do
+disco (HD) e com alteração de memória na data atual (por país, região, estado e
+cidade).
+ \item Pizza: percentual das máquinas sem modificação de inventário,
+com diminuição do disco e com diminuição de memória na data atual (por país,
+região, estado e cidade).
+ \item Linha: comparativo do total de máquinas que sofreram alteração
+do HD e de máquinas que sofreram alteração da memória nos últimos seis meses
+(por país, região, estado e cidade).
+ \item Legenda:
+ \begin{itemize}
+\item Sinalização verde: total de máquinas sem modificação de inventário.
+\item Sinalização vermelha: total de máquinas que sofreram alteração de disco.
+\item Sinalização roxa: total de máquinas que sofreram alteração de memória.
+ \end{itemize}
+ \item Relatório gerado no último nível: ao clicar no gráfico de
+barras, o sistema disponibiliza um relatório da alteração, para
+menor, do inventário das máquinas com o agente de coleta instalado. Os
+componentes relacionados são o inventário antigo e o inventário novo (sistema
+operacional, processador, memória e disco) da máquina que sofreu diminuição do
+disco e/ou da memória, com uma indicação ao lado do componente alterado.
+ \end{itemize}
+\end{itemize}
+
+Projetos identificados e monitorados pelo Agente:
+
+\begin{itemize}
+ \item Máquinas PROINFO;
+ \item UCA Classmates;
+ \item UCA Server;
+ \item Projetores PROINFO.
+\end{itemize}
+
+A Busca Rápida é uma ferramenta apresentada ao usuário (qualquer pessoa) para
+facilitar a geração dos relatórios. Nela, o usuário escolhe o tipo de relatório,
+de projeto e a respectiva Cidade (Escola e Data, no caso do Relatório de Uso da
+Rede) para o sistema gerar e disponibilizar para \textit{download} o relatório
+escolhido.
+
+O menu superior apresenta o projeto sobre o qual os gráficos e relatórios serão
+gerados. Ao escolher um projeto, caso não haja gráficos selecionados, é mostrado
+ao usuário a página dos gráficos de Disponibilidade como padrão. Se houver
+alguma página de gráficos previamente selecionada, então essa mesma página será
+carregada, porém no projeto escolhido.
+
+O menu esquerdo permite ao usuário escolher quais páginas dos gráficos serão
+gerados e mostrados na tela. Ao escolher uma página, caso não haja projeto
+selecionado, será mostrada a página do projeto das Máquinas PROINFO. Caso haja
+um projeto selecionado, será mantido o projeto e mudada apenas a página.
+
+\subsection{Documentação}
+\label{sub:doc}
+
+Este módulo contém:
+
+\begin{itemize}
+ \item Manual do Usuário, que descreve o Portal e apresenta um
+passo-a-passo de como instalar o Agente PROINFODATA;
+ \item Página e links sobre o código fonte dos sistemas desenvolvidos para o
+PROINFODATA;
+ \item Wiki com informações sobre o \textit{framework} \textit{Pentaho
+Business Intelligence}\footnote{http://www.pentaho.com/}, descrevendo como foi
+feita a instalação, configuração, utilização e peculariedades desse
+\textit{software}.
+\end{itemize}
+
+\subsection{Sistema e Código Fonte}
+
+O Portal está escrito em HTML, Java (JSP) e JavaScript (JS). Ele funciona em
+conjunto com \textit{Pentaho Business Intelligence Server}, Tomcat (que vem
+integrado ao Pentaho) e Axis.
+
+O \textit{Pentaho BI Server} é responsável por manter os servidores \textit{Web
+Services} funcionando (inclusive o servidor com o qual o Agente Cliente se
+comunica e envia informações da máquina). E para facilitar o gerenciamento dessa
+ferramenta é utilizado o \textit{software}
+daemontools\footnote{http://cr.yp.to/daemontools.html}.
+
+Os gráficos e relatórios são gerados, respectivamente, com o auxílio das
+ferramentas \textit{Pentaho Design Studio} e \textit{Pentaho Report Designer}. O
+resultado é então publicado no servidor do Pentaho, em formatos XML, XACTION,
+PRPT, entre outros, ficando acessível pelo HTML/JS/JSP do Portal, responsável
+por apresentar e organizar as páginas do Portal.
+
+Além disso, o \textit{Pentaho BI Server} possui um portal próprio, com
+acessibilidade limitada (usuário e senha, voltado ao uso interno e do MEC), que
+permite a criação de consultas, gráficos e relatórios personalizados, contando
+com o auxílio da ferramenta \textit{Pentaho Mondrian Schema Workbench}, que
+permite gerar cubos de consultas ao Banco de Dados, para facilitar esse
+processo de criação personalizada.
diff --git a/proinfodatadoc/func_e_requi/relatorio.tex b/proinfodatadoc/func_e_requi/relatorio.tex
new file mode 100644
index 0000000000000000000000000000000000000000..8eac276849c4cea45564fff5ad677640d82b5f9e
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/relatorio.tex
@@ -0,0 +1,46 @@
+\documentclass[a4paper,11pt]{article}
+\usepackage[top=3cm,right=2.5cm,bottom=2.5cm,left=3cm]{geometry}
+\usepackage[brazil]{babel}
+\usepackage[utf8]{inputenc}
+\usepackage{indentfirst}
+\usepackage{graphicx}
+\usepackage{here}
+
+
+\begin{document}
+
+%\title{PROINFODATA\\\small{Funcionalidades e Requisitos}}
+
+%\author {
+%C3SL - Centro de Computação Científica e Software Livre
+% }
+
+%\date{\today}
+%\maketitle
+
+\begin{figure}[h]
+ \begin{center}
+ \includegraphics[scale=0.3]{capa.png}
+ \end{center}
+\end{figure}
+
+\clearpage
+
+\tableofcontents
+
+\clearpage
+
+% Add sections
+%\input{id.tex}
+\input{intro.tex}
+\input{sol.tex}
+\input{portal.tex}
+%\input{objetivos.tex}
+\input{bd.tex}
+\input{agente.tex}
+\input{requisitos.tex}
+\input{observacoes.tex}
+%\input{consideracoes.tex}
+
+
+\end{document}
diff --git a/proinfodatadoc/func_e_requi/requisitos.tex b/proinfodatadoc/func_e_requi/requisitos.tex
new file mode 100644
index 0000000000000000000000000000000000000000..cde0fd75a7b076a4f7519e8aa289a5b51fc30d66
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/requisitos.tex
@@ -0,0 +1,44 @@
+% Requisitos de software e hardware
+
+\section{Requisitos}
+
+Esta seção descreve os requisitos de hardware e software necessários para
+implementação e uso dos sistemas de armazenamento, coleta e acompanhamento
+do projeto PROINFODATA.
+
+\subsection{Hardware}
+
+Para o sistema de coleta, que inclui o agente de coleta e o módulo de
+comunicação com o servidor e é instalado nas escolas, o único requisito é o
+de conexão com a internet.
+
+O sistema de armazenamento e acompanhamento, quando instalados na mesma
+máquina, possuem o seguinte requisito mínimo de hardware:
+
+\begin{itemize}
+\item SuperMicro MBD-X8SAX-O single LGA1366 socket server board (ou
+superior).
+\item 01 Intel XEON W3570 3.2GHz, 8M cache 6.8GT/sec
+\item 01 RM31212ML 3U rack chassis, 12 hotswap drive bays, slide rails,
+\item 01 Redundant 650W power supply Zippy R3G-6650P
+\item 06 4GB ECC DDR3-1333 Unbuffered SDRAM Module 24GB RAM total
+\item 01 3ware 9650SE-12ML – 12 port RAID (SATA)
+\item 12 1TB WD1002FYBS Raid Edition 3 SATA300 HDD 10TB RAID6, em RAID 10
+\item 01 Onboard Dual GbE (1000T) ethernet on motherboard
+\end{itemize}
+
+
+\subsection{Software}
+
+Requisitos de software para o portal, banco de dados e servidor webservice:
+
+\begin{itemize}
+\item Pentaho BI Server 3.5+ (já vem com o Tomcat)
+\item Axis 1.4+
+\item Java (JDK) 6u16+
+\item PostgreSQL 8.3+
+\item daemontools
+\item Pentaho Report Designer 3.0 e 3.8+
+\item Pentaho Mondrian Schema Workbech
+\item Pentaho Design Studio
+\end{itemize}
diff --git a/proinfodatadoc/func_e_requi/sol.tex b/proinfodatadoc/func_e_requi/sol.tex
new file mode 100644
index 0000000000000000000000000000000000000000..7d7093781a70fc2d3931b4ed8ffe10aef1741cbf
--- /dev/null
+++ b/proinfodatadoc/func_e_requi/sol.tex
@@ -0,0 +1,32 @@
+\section{Visão Geral da Solução}
+
+O sistema funciona a partir de um único portal, no qual se pode:
+– obter o agente para instalação nas escolas;
+– acessar o sistema de monitoramento;
+– obter a documentação do sistema.
+
+\subsection{Módulos}
+O projeto esta dividido em dois módulos: \
+
+\begin{enumerate}
+\item{Sistema de Coleta}
+ \begin{enumerate}
+ \item[1.1] {Instalação;}
+ \item[1.2] {Atualização Automática;}
+ \item[1.3] {Estrutura:}
+ \begin{enumerate}
+ \item[•] {Agente de coleta;}
+ \item[•] {Agente de comunicação (Cliente);}
+ \item[•] {Agente de comunicação (Servidor).}
+ \end{enumerate}
+ \end{enumerate}
+\item{Sistema de monitoramento}
+ \begin{enumerate}
+ \item[2.1] {Disponibilidade;}
+ \item[2.2] {Inventário;}
+ \item[2.3] {Auditoria.}
+ \end{enumerate}
+\end{enumerate}
+
+As próximas seções descrevem o detalhamento de cada item. \
+
diff --git a/proinfodatadoc/relat_tecnico/Makefile b/proinfodatadoc/relat_tecnico/Makefile
new file mode 100644
index 0000000000000000000000000000000000000000..99fbe0aacfc3c8845493f01b12553f59a2ac8ce1
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/Makefile
@@ -0,0 +1,6 @@
+all:
+ pdflatex relatorio
+ pdflatex relatorio
+
+clean:
+ rm -f *.aux *.log *.bbl *.blg *.toc *~
diff --git a/proinfodatadoc/relat_tecnico/README b/proinfodatadoc/relat_tecnico/README
new file mode 100644
index 0000000000000000000000000000000000000000..94f115d079961cefef9b3bde46ea831fe8d354a0
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/README
@@ -0,0 +1,3 @@
+Este documento tem como objetivo fornecer informações sobre funcionalidades
+e requisitos do projeto PROINFODATA
+
diff --git a/proinfodatadoc/relat_tecnico/ambiente.tex b/proinfodatadoc/relat_tecnico/ambiente.tex
new file mode 100644
index 0000000000000000000000000000000000000000..56603b0745703c5fe50a9a80756019f6a0cec81a
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/ambiente.tex
@@ -0,0 +1,65 @@
+% Descrever ambiente de homologação. Máquinas físicas e virtuais.
+\section{Ambiente de Homologação}
+
+O ambiente de homologação atual está instalado em servidores do C3SL,
+localizados na Universidade Federal do Paraná (UFPR) e é composto por uma
+série de máquinas.
+
+A figura~\ref{fig:ambiente} apresenta de forma resumida como está estruturado
+o ambiente de homologação.
+
+\begin{figure}[h]
+ \begin{center}
+ \includegraphics[scale=0.7]{ambientehomologacao.png}
+ \caption{Ambiente de Homologação.}
+ \label{fig:ambiente}
+ \end{center}
+\end{figure}
+
+Abaixo enumeradas as máquinas físicas utilizadas, suas configurações e
+funções no processo de homologação.
+
+\begin{itemize}
+ \item \textit{colombard}: utilizada para homologação do sistema de
+ acompanhamento e armazenamento, além do módulo servidor do sistema de
+ coleta (servidor \textit{Web Service}). A máquina possui a seguinte
+ configuração:
+ \begin{itemize}
+ \item Dual-Core AMD Opteron(tm) Processor 2220 2.8GHz
+ \item 8GB de memória RAM
+ \item 7TB HD
+ \end{itemize}
+
+ \item \textit{beamish}: máquina que comporta as máquinas virtuais
+ utilizadas para homologação do agente. Configuração:
+ \begin{itemize}
+ \item Intel(R) Pentium(R) 4 CPU 3.20GHz
+ \item 4GB memória RAM
+ \item 250GB HD
+ \end{itemize}
+
+ \item \textit{win}: máquina utilizada para testar o agente em plataforma
+ windows. Configuração:
+ \begin{itemize}
+ \item Intel(R) Core(TM) i5 650 3.20GHz
+ \item 4GB memória RAM
+ \item 500GB HD
+ \end{itemize}
+
+ \item \textit{win83}: máquina do projeto PROINFO (pregão 83/2008),
+ utilizada para testes do agente em plataforma windows. Configuração:
+ \begin{itemize}
+ \item Intel(R) Celeron(R) E1500 2.20GHz
+ \item 1GB memória RAM
+ \item 160GB HD
+ \end{itemize}
+
+ \item \textit{le4}: máquina do projeto PROINFO (pregão 83/2008),
+ utilizada para homologação do agente no Linux Educacional 4.0.
+ \begin{itemize}
+ \item Intel(R) Celeron(R) E1500 2.20GHz
+ \item 1GB memória RAM
+ \item 160GB HD
+ \end{itemize}
+
+\end{itemize}
diff --git a/proinfodatadoc/relat_tecnico/ambientehomologacao.png b/proinfodatadoc/relat_tecnico/ambientehomologacao.png
new file mode 100644
index 0000000000000000000000000000000000000000..2f502ef5f2e0ba67e8818d4f6fa459c5eb3b3b6b
Binary files /dev/null and b/proinfodatadoc/relat_tecnico/ambientehomologacao.png differ
diff --git a/proinfodatadoc/relat_tecnico/ambientehomologacao.svg b/proinfodatadoc/relat_tecnico/ambientehomologacao.svg
new file mode 100644
index 0000000000000000000000000000000000000000..fc60c9101c2e0f45c731d3beda4aa7c9551db32f
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/ambientehomologacao.svg
@@ -0,0 +1,434 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ width="210mm"
+ height="297mm"
+ id="svg2"
+ version="1.1"
+ inkscape:version="0.48.1 r9760"
+ sodipodi:docname="ambientehomologacao.svg"
+ inkscape:export-filename="/home/diego/c3sl/seed2/proinfodoc/relat_tecnico/ambientehomologacao.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90">
+ <defs
+ id="defs4" />
+ <sodipodi:namedview
+ id="base"
+ pagecolor="#ffffff"
+ bordercolor="#666666"
+ borderopacity="1.0"
+ inkscape:pageopacity="0.0"
+ inkscape:pageshadow="2"
+ inkscape:zoom="1.7427686"
+ inkscape:cx="331.68833"
+ inkscape:cy="830.00063"
+ inkscape:document-units="px"
+ inkscape:current-layer="layer1"
+ showgrid="false"
+ showguides="true"
+ inkscape:guide-bbox="true"
+ inkscape:window-width="1366"
+ inkscape:window-height="744"
+ inkscape:window-x="0"
+ inkscape:window-y="24"
+ inkscape:window-maximized="1" />
+ <metadata
+ id="metadata7">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ <dc:title></dc:title>
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <g
+ inkscape:label="Camada 1"
+ inkscape:groupmode="layer"
+ id="layer1">
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.53278577;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect2985"
+ width="702.31049"
+ height="432.92712"
+ x="3.7560489"
+ y="35.454159" />
+ <text
+ xml:space="preserve"
+ style="font-size:16px;font-style:normal;font-weight:bold;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans;-inkscape-font-specification:Sans Bold"
+ x="15.611"
+ y="57.393444"
+ id="text2987"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan2989"
+ x="15.611"
+ y="57.393444">Ambiente de Homologação</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="28.17337"
+ y="93.151199"
+ id="text3001"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3003"
+ x="28.17337"
+ y="93.151199"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Física</tspan><tspan
+ sodipodi:role="line"
+ x="28.17337"
+ y="110.6512"
+ id="tspan3005">Hostname: colombard</tspan><tspan
+ sodipodi:role="line"
+ x="28.17337"
+ y="128.1512"
+ id="tspan3007">SO: Debian 5.0.8 lenny</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.44068146;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009"
+ width="131.91245"
+ height="105.66801"
+ x="35.49511"
+ y="174.16188"
+ ry="11.404311"
+ rx="12.049792" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="45.272018"
+ y="191.30542"
+ id="text3011"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013"
+ x="45.272018"
+ y="191.30542"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Serviço:</tspan><tspan
+ sodipodi:role="line"
+ x="45.272018"
+ y="206.30542"
+ id="tspan3015">Sistema de </tspan><tspan
+ sodipodi:role="line"
+ x="45.272018"
+ y="221.30542"
+ id="tspan3017">Acompanhamento:</tspan><tspan
+ sodipodi:role="line"
+ x="45.272018"
+ y="236.30542"
+ id="tspan3239">- Pentaho</tspan><tspan
+ sodipodi:role="line"
+ x="45.272018"
+ y="251.30542"
+ id="tspan3241">- Tomcat</tspan><tspan
+ sodipodi:role="line"
+ x="45.272018"
+ y="266.30542"
+ id="tspan3263">- Apache</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="208.5901"
+ y="191.19186"
+ id="text3011-3"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-8"
+ x="208.5901"
+ y="191.19186"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Serviço:</tspan><tspan
+ sodipodi:role="line"
+ x="208.5901"
+ y="206.19186"
+ id="tspan3015-0">Sistema de </tspan><tspan
+ sodipodi:role="line"
+ x="208.5901"
+ y="221.19186"
+ id="tspan3017-4">Armazenamento:</tspan><tspan
+ sodipodi:role="line"
+ x="208.5901"
+ y="236.19186"
+ id="tspan3261">- PostgreSQL</tspan><tspan
+ sodipodi:role="line"
+ x="208.5901"
+ y="251.19186"
+ id="tspan3198">- Servidor</tspan><tspan
+ sodipodi:role="line"
+ x="208.5901"
+ y="266.19186"
+ id="tspan3200"> WebService</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.42498752;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect2999-9"
+ width="328.58258"
+ height="225.35863"
+ x="357.21075"
+ y="73.022232" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="368.52698"
+ y="92.832779"
+ id="text3001-0"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3003-5"
+ x="368.52698"
+ y="92.832779"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Física</tspan><tspan
+ sodipodi:role="line"
+ x="368.52698"
+ y="110.33278"
+ id="tspan3005-6">Hostname: beamish</tspan><tspan
+ sodipodi:role="line"
+ x="368.52698"
+ y="127.83278"
+ id="tspan3007-7">SO: Debian 5.0.8 lenny</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="377.59665"
+ y="167.8119"
+ id="text3011-4-3"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-0-8"
+ x="377.59665"
+ y="167.8119"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Virtual:</tspan><tspan
+ sodipodi:role="line"
+ x="377.59665"
+ y="182.8119"
+ id="tspan3017-47-9">Hostname: brd3</tspan><tspan
+ sodipodi:role="line"
+ x="377.59665"
+ y="197.8119"
+ id="tspan3126">SO: Debian 6.0 x86</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="378.86218"
+ y="238.74106"
+ id="text3011-4-3-4"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-0-8-4"
+ x="378.86218"
+ y="238.74106"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Virtual:</tspan><tspan
+ sodipodi:role="line"
+ x="378.86218"
+ y="253.74106"
+ id="tspan3017-47-9-3">Hostname: brd4</tspan><tspan
+ sodipodi:role="line"
+ x="378.86218"
+ y="268.74106"
+ id="tspan3126-9">SO: SUSE 11.1 x86</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.38456941;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7-1-8"
+ width="152.19922"
+ height="69.745598"
+ x="525.75854"
+ y="145.23924"
+ ry="26.692759"
+ rx="0" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="535.66064"
+ y="168.46042"
+ id="text3011-4-3-6"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-0-8-7"
+ x="535.66064"
+ y="168.46042"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Virtual:</tspan><tspan
+ sodipodi:role="line"
+ x="535.66064"
+ y="183.46042"
+ id="tspan3017-47-9-0">Hostname: brd5</tspan><tspan
+ sodipodi:role="line"
+ x="535.66064"
+ y="198.46042"
+ id="tspan3126-4">SO: Fedora 13 x86</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="536.92615"
+ y="239.38956"
+ id="text3011-4-3-4-8"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-0-8-4-4"
+ x="536.92615"
+ y="239.38956"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Virtual:</tspan><tspan
+ sodipodi:role="line"
+ x="536.92615"
+ y="254.38956"
+ id="tspan3017-47-9-3-8">Hostname: brd6</tspan><tspan
+ sodipodi:role="line"
+ x="536.92615"
+ y="269.38956"
+ id="tspan3126-9-1">SO: Ubuntu 11.04 x86</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.38530272;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7-1-7-6"
+ width="152.78021"
+ height="69.745598"
+ x="525.45447"
+ y="219.98257"
+ ry="26.692759"
+ rx="0" />
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.38456941;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7-1-8-5"
+ width="152.19922"
+ height="69.745598"
+ x="366.64545"
+ y="144.99365"
+ ry="26.692759"
+ rx="0" />
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.38530272;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7-1-7-6-8"
+ width="152.78021"
+ height="69.745598"
+ x="366.34137"
+ y="219.73698"
+ ry="26.692759"
+ rx="0" />
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.44072357;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-3"
+ width="131.91245"
+ height="105.68822"
+ x="193.46048"
+ y="174.30971"
+ ry="11.979633"
+ rx="12.049792" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="33.853607"
+ y="335.12183"
+ id="text3001-04"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3003-8"
+ x="33.853607"
+ y="335.12183"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Física</tspan><tspan
+ sodipodi:role="line"
+ x="33.853607"
+ y="352.62183"
+ id="tspan3005-7">Hostname: win</tspan><tspan
+ sodipodi:role="line"
+ x="33.853607"
+ y="370.12183"
+ id="tspan3007-1">SO: Windows 7</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.29137906;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7"
+ width="131.91245"
+ height="46.196667"
+ x="35.175346"
+ y="390.13251"
+ ry="10.723811"
+ rx="12.049792" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="44.952255"
+ y="409.27603"
+ id="text3011-2"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-7"
+ x="44.952255"
+ y="409.27603"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Serviço:</tspan><tspan
+ sodipodi:role="line"
+ x="44.952255"
+ y="424.27603"
+ id="tspan3263-0">Agente de coleta</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.33199543;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect2999-5-3"
+ width="327.77386"
+ height="137.86572"
+ x="357.4704"
+ y="314.95273" />
+ <text
+ xml:space="preserve"
+ style="font-size:14px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="368.78662"
+ y="334.79965"
+ id="text3001-04-1"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3003-8-8"
+ x="368.78662"
+ y="334.79965"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Máquina Física</tspan><tspan
+ sodipodi:role="line"
+ x="368.78662"
+ y="352.29965"
+ id="tspan3005-7-9">Hostname: le4</tspan><tspan
+ sodipodi:role="line"
+ x="368.78662"
+ y="369.79965"
+ id="tspan3007-1-6">SO: Linux Educacional 4.0</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.29137906;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect3009-7-4"
+ width="131.91245"
+ height="46.196667"
+ x="376.10837"
+ y="391.81033"
+ ry="9.0024128"
+ rx="12.049792" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-weight:normal;line-height:125%;letter-spacing:0px;word-spacing:0px;fill:#000000;fill-opacity:1;stroke:none;font-family:Sans"
+ x="385.88528"
+ y="410.95386"
+ id="text3011-2-3"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan3013-7-3"
+ x="385.88528"
+ y="410.95386"
+ style="font-weight:bold;-inkscape-font-specification:Sans Bold">Serviço:</tspan><tspan
+ sodipodi:role="line"
+ x="385.88528"
+ y="425.95386"
+ id="tspan3263-0-3">Agente de coleta</tspan></text>
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.42498752;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect2999-9-8"
+ width="328.58258"
+ height="225.35863"
+ x="17.029387"
+ y="73.245407" />
+ <rect
+ style="fill:none;stroke:#000000;stroke-width:0.33199543;stroke-miterlimit:4;stroke-dasharray:none"
+ id="rect2999-5-3-9"
+ width="327.77386"
+ height="137.86572"
+ x="18.335945"
+ y="314.95273" />
+ </g>
+</svg>
diff --git a/proinfodatadoc/relat_tecnico/atividades.tex b/proinfodatadoc/relat_tecnico/atividades.tex
new file mode 100644
index 0000000000000000000000000000000000000000..88685f6ed6cc1248787a629dfd9f9a5198dc85c3
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/atividades.tex
@@ -0,0 +1,4 @@
+% Atividades realizadas, incluindo melhorias, atualizações, reuniões,
+% validação de código, etc
+\section{Atividades Realizadas}
+
diff --git a/proinfodatadoc/relat_tecnico/capa.png b/proinfodatadoc/relat_tecnico/capa.png
new file mode 100644
index 0000000000000000000000000000000000000000..cc929861576048f2bc11d74c94d11e4c43356723
Binary files /dev/null and b/proinfodatadoc/relat_tecnico/capa.png differ
diff --git a/proinfodatadoc/relat_tecnico/consideracoes.tex b/proinfodatadoc/relat_tecnico/consideracoes.tex
new file mode 100644
index 0000000000000000000000000000000000000000..5693cd952d4b3c5c7f5c917e6dbb0dfd52c8ebe5
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/consideracoes.tex
@@ -0,0 +1,6 @@
+% Escrever considerações/conclusão sobre o documento
+\section{Considerações}
+
+O projeto ProinfoData ...
+
+O C3SL (Centro de Computação Científica e Software Livre)
diff --git a/proinfodatadoc/relat_tecnico/controle.tex b/proinfodatadoc/relat_tecnico/controle.tex
new file mode 100644
index 0000000000000000000000000000000000000000..0b3114fcc8307568ea5d147a5ace8e3cf00c995e
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/controle.tex
@@ -0,0 +1,34 @@
+% Descreve método de testes utilizado e demandas em andamento, caso existam
+\section{Controle de Versões}
+
+O controle de versões do projeto é feito com a utilização da ferramenta
+GIT\footnote{http://git-scm.com/} e pode ser acompanhado através do website
+\texttt{http://git.c3sl.ufpr.br/}. Os diferentes sistemas presentes no
+projeto foram divididos em vários repositórios, apresentados na
+tabela~\ref{tab:repos}:
+
+\begin{table}[h]
+\centering
+\begin{tabular}{|l|l|l|}
+ \hline
+ \textbf{Nome} & \textbf{Sistema} & \textbf{Descrição} \\
+ \hline
+ database.git & Armazenamento & Scripts relacionados ao Banco de Dados \\
+ portal.git & Acompanhamento & Portal de acompanhamento \\
+ proinfodoc.git & Geral & Documentação do projeto \\
+ client.git & Coleta & Comunicação com o servidor \\
+ server.git & Coleta & Parte servidor do Coleta, Web Service \\
+ coleta.git & Coleta & Scripts para coleta de inventário \\
+ windows-coleta.git & Coleta & Coleta de inventário Windows \\
+ windows-installer.git & - & Instalador do agente Windows \\
+ buildpackage.git & - & Montagem do instalador do agente para Linux \\
+ \hline
+\end{tabular}
+\label{tab:repos}
+\caption{Repositórios GIT do projeto PROINFODATA}
+\end{table}
+
+Toda alteração previamente testada validade pela equipe de desenvolvimento
+(ver seção~\ref{sec:valida}) é submetida então ao sistema
+de controle de versão e devidamente comentada, de forma a elucidar os
+motivos que levaram a alteração a ser feita.
diff --git a/proinfodatadoc/relat_tecnico/here.sty b/proinfodatadoc/relat_tecnico/here.sty
new file mode 100755
index 0000000000000000000000000000000000000000..869e566a1b408558c39956d7c1103ceb6e0ff661
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/here.sty
@@ -0,0 +1,152 @@
+%% Save file as: HERE.STY Source: FILESERV@SHSU.BITNET
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\iffalse
+ here.sty
+ %%%%%%%%%%
+ here.sty gives environments such as figure and table a [H] option
+ which means `PUT IT HERE'. As opposed to the standard [h] option which
+ means `You may put it here if you wish'.
+
+ David Carlisle
+ carlisle@uk.ac.man.cs
+ 13 September 1991
+\fi
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%
+% If you have Mittelbach's doc.sty, this file may be formatted with a
+% command like: latex here.sty
+% (You do not need doc.sty to {\em use} this style.)
+%
+% To create a faster loading .sty file, copy this file to here.doc
+% Then remove all the lines beginning with a `%' from the .sty file. This
+% may be done with docstrip.tex, or your text editor. The following two
+% lines may also be deleted from the .sty file.
+\ifcat a\noexpand @\let\next\relax\else\def\next{%
+ \documentstyle[here,doc]{article}\MakePercentIgnore}\fi\next
+%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% \textwidth=365pt ^^A Allow macrocode text with 75 columns.
+% \CodelineIndex ^^A Code lines numbered.
+% \DisableCrossrefs ^^A No Cross references.
+%
+% \title{here.sty}
+% \author{D. P. Carlisle}
+% \date{13 Sept 1991}
+% \begin{document}
+% \maketitle
+% \begin{abstract}
+% \verb|here.sty| gives environments such as {\tt figure} and {\tt table} a
+% {\tt [H]} option which means `PUT IT HERE'. As opposed to the standard
+% {\tt [h]} option which means `You may put it here if you wish'.%
+% \end{abstract}
+%
+% \begin{figure}[H]
+% This figure will not float, even if this causes a bad page break.
+% \caption{It may be captioned as usual.}
+% \end{figure}
+%
+% Many people have problems with \LaTeX's floating environments. A common
+% complaint is that all the environments appear at the end of the document
+% (or chapter). Many users try to correct this behaviour by using the {\tt
+% [h]} option. Incorect use of this option, in particular using just {\tt
+% [h]} rather than a more liberal option such as {\tt [hp]} actually makes
+% the problem worse!
+%
+% \LaTeX\ will only position a float (even one with the {\tt [h]} option)
+% in a position which does not violate the rules for float placement set by
+% the document style. These rules are determined by the following
+% parameters:\\
+% \begin{tabular}{ll}
+% \verb|\c@topnumber|& Number of floats allowed at the top of a
+% column.\\
+% \verb|\topfraction|& Fraction of column that can be devoted to
+% floats.\\
+% \verb|\c@dbltopnumber|\\ \verb|\dbltopfraction|& Same as above, but for
+% double-column floats.\\
+% \verb|\c@bottomnumber|\\ \verb|\bottomfraction|& Same as above for
+% bottom of page.\\
+% \verb|\c@totalnumber|& Number of floats allowed in a single column,\\
+% & including in-text floats.\\
+% \verb|\textfraction|& Minimum fraction of column that must contain
+% text.\\
+% \verb|\floatpagefraction|& Minimum fraction of page that must be taken
+% up by\\& float page.
+% \end{tabular}%
+%
+% The default settings (in \verb|article.doc| for {\tt article} style) for
+% these parameters make it difficult to set floats if the document has a
+% lot of small floats. The result is that \LaTeX\ `holds them back' in the
+% hope of finding a better place later. At the end of the document (or at a
+% \verb|\clearpage|) it gives up and outputs all the remaining floats.
+%
+% It may be seen from the above paragraph that the `correct' way to handle
+% float problems is to write a style file modifying these parameters,
+% however for many purposes, authors to not want a float at all, they just
+% use the {\tt figure} or {\tt table} environments to get the correct
+% spacing, and a counter that may be referenced. This style option
+% provides an easy solution in this case. If the {\tt [H]} option is
+% specified, the environment will not float even if it causes a bad page
+% break, or breaks the rules specified in the above parameters. The main
+% drawback is that if the [H] option is used in one figure, and the
+% following figure uses the {\tt [t]} option, then the second figure may
+% float in front of the first.
+%
+% Note that the {\tt [H]} should not be used in conjunction with the other
+% options. {\tt [Htp]} is not allowed by this style. The {\tt h} option may
+% still be used, so {\tt [htp]} is OK.
+% \typeout{End of the Introduction and Examples.}
+% \typein[\answer]%
+% {Do you want an annotated listing of the macro definitions (y/n) ?}
+% \def\next{y}\ifx\answer\next\else\expandafter\stop\fi
+%
+% \section{The Macros}
+% First we make sure that this file is only loaded once.
+% \begin{macrocode}
+\ifx\@Hxfloat\@Hundef\else\expandafter\endinput\fi
+% \end{macrocode}
+%
+% \begin{macro}{\@Hxfloat}
+% Now we can save the original version of \verb|\@xfloat|.
+% \begin{macrocode}
+\let\@Hxfloat\@xfloat
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\@xfloat}
+% The new version of \verb|@xfloat| looks for a \verb|[H]| argument.
+% If it is present \verb|\@HHfloat| is called, otherwise the original macro
+% (renamed to \verb|\@Hfloat|) is called.
+% \begin{macrocode}
+\def\@xfloat#1[{\@ifnextchar{H}{\@HHfloat{#1}[}{\@Hxfloat{#1}[}}
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\@HHfloat}
+% First gobble the \verb|[H]|. Note that {\tt H} should not be used in
+% conjunction with the other placement options, nor as the value of the
+% default placement, as set in \verb|\fps@|{\it type}.
+% \begin{macrocode}
+\def\@HHfloat#1[H]{%
+% \end{macrocode}
+% Locally redefine the end of the environment.
+% \begin{macrocode}
+\expandafter\let\csname end#1\endcsname\end@Hfloat
+% \end{macrocode}
+% Add the vertical space, and define \verb|\caption|. Also reset
+% \verb|\parindent| for compatibility with the standard {\tt [h]} option.
+% \begin{macrocode}
+\vskip\intextsep\def\@captype{#1}\parindent\z@
+% \end{macrocode}
+% The final \verb|\ignorespaces| is needed to gobble any spaces or newlines
+% after the {\tt[H]} tokens.
+% \begin{macrocode}
+\ignorespaces}
+% \end{macrocode}
+% \end{macro}
+% \begin{macro}{\end@Hfloat}
+% Add the same vertical space as would be added by a float placed with
+% {\tt[h]}.
+% \begin{macrocode}
+\def\end@Hfloat{\vskip \intextsep}
+% \end{macrocode}
+% \end{macro}
+% \end{document}
+
diff --git a/proinfodatadoc/relat_tecnico/id.tex b/proinfodatadoc/relat_tecnico/id.tex
new file mode 100644
index 0000000000000000000000000000000000000000..c13f13df1013b7c9aada1ad4b40d736ec5dcfcd5
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/id.tex
@@ -0,0 +1,9 @@
+% descrever projeto, cliente e coordenadores
+\section{Identificação do Documento}
+
+O projeto ProinfoData tem como objetivo acompanhar o estado de funcionamento
+dos laboratórios Proinfo, permitindo ao MEC detectar possíveis irregularidades.
+
+Cliente?
+
+Coordenadores?
diff --git a/proinfodatadoc/relat_tecnico/introducao.tex b/proinfodatadoc/relat_tecnico/introducao.tex
new file mode 100644
index 0000000000000000000000000000000000000000..5235e6b78adc5b3753720fb94ae424d83f3834d2
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/introducao.tex
@@ -0,0 +1,6 @@
+\section{Introdução}
+
+Este documento tem como objetivo descrever as atividades desenvolvidas no
+projeto PROINFODATA, bem como apresentar o ambiente necessário para a
+homologação e os modelos de testes e validação de código utilizados no
+projeto.
diff --git a/proinfodatadoc/relat_tecnico/relatorio.tex b/proinfodatadoc/relat_tecnico/relatorio.tex
new file mode 100644
index 0000000000000000000000000000000000000000..038ee23ef0a75d5d755d2b2b7acddb4cb1dbbfa1
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/relatorio.tex
@@ -0,0 +1,42 @@
+\documentclass[a4paper,11pt]{article}
+\usepackage[top=3cm,right=2.5cm,bottom=2.5cm,left=3cm]{geometry}
+\usepackage[brazil]{babel}
+\usepackage[utf8]{inputenc}
+\usepackage{indentfirst}
+\usepackage{graphicx}
+\usepackage{here}
+
+\begin{document}
+
+%\title{PROINFODATA\\\small{Relatório Técnico}}
+
+%\author {
+%C3SL - Centro de Computação Científica e Software Livre
+% }
+
+%\date{\today}
+%\maketitle
+
+\begin{figure}[h]
+ \begin{center}
+ \includegraphics[scale=0.3]{capa.png}
+ \end{center}
+\end{figure}
+
+\clearpage
+
+\tableofcontents
+
+\clearpage
+
+% Add sections
+%\input{id.tex}
+\input{introducao.tex}
+\input{ambiente.tex}
+\input{testes.tex}
+\input{controle.tex}
+%\input{atividades.tex}
+%\input{consideracoes.tex}
+
+
+\end{document}
diff --git a/proinfodatadoc/relat_tecnico/testes.tex b/proinfodatadoc/relat_tecnico/testes.tex
new file mode 100644
index 0000000000000000000000000000000000000000..3dd0fbe49c30a1dbb86b94270b59e92023ae98ff
--- /dev/null
+++ b/proinfodatadoc/relat_tecnico/testes.tex
@@ -0,0 +1,142 @@
+% Descreve método de testes utilizado e demandas em andamento, caso existam
+\section{Testes e Validação de Código}
+\label{sec:valida}
+
+O laboratório de homologação foi montado logo no início do projeto. Desde
+então toda nova proposta de alteração nos sistemas foi antes verificada com a
+utilização do ambiente.
+
+Após testes no ambiente de homologação, as alterações são ainda discutidas
+pela equipe de desenvolvimento antes de serem aplicadas em definitivo no
+ambiente de produção. Para tal utilizam-se listas de e-mails.
+
+O motivo desta dupla checagem é, além de garantir um padrão em todo código
+produzido, identificar possibilidades de inserção de erros não detectados
+pelos pelo programador original no processo de homologação.
+
+O processo de testes do Proinfodata é realizado seguindo um roteiro previamente
+definido, de acordo com as funcionalidades que foram agregadas ou sofreram
+alterações.
+Os eventuais erros encontrados são registrados no sistema utilizado
+internamente pela equipe do C3SL para acompanhamento da resolução de bugs
+(trac).
+Após a correção, nova versão é gerada e submetida a novos testes e assim,
+sucessivamente, até que todos os erros críticos sejam satisfatoriamente
+corrigidos.
+Abaixo é apresentado um exemplo do roteiro que contém o planejamento do
+conjunto mínimo de testes a ser realizado. Além dos testes sugeridos no
+roteiro, são realizados outros testes de acordo com a percepção do responsável
+pela atividade.
+
+\subsection { Exemplo de plano de testes do agente ProInfoData }
+Os passos abaixo deverão ser executados tanto SEM proxy quanto COM um proxy
+configurado!
+Além disso, deve-ser testar em máquinas normais (ProInfo ou qualquer), UCA
+Classmates (tanto a nova da Positivo quanto a antiga da CCE)
+e no UCA Server.
+O Projetor ProInfo da Diebold e já foi testado (a atualização deverá acontecer
+automaticamente).
+
+\begin{enumerate}
+\item Baixar e instalar o agente a partir da colombard, usando diversos INEPs,
+ como 12017000.
+ \begin{enumerate}
+ \item [1.1] Verificar se há um corrompimento no agente. Caso exista,
+ significa que os pacotes (instalação e atualização) podem conter algum
+ erro. Neste caso, executar um script específico para verificar isso,
+ descobrindo se existe algum problema nos pacotes. Isso pode ser feito
+ logo após a instalação e logo após uma atualização.
+ \end{enumerate}
+
+\item Verificar se a instalação ocorreu corretamente.
+ \begin{enumerate}
+ \item [2.1] Verificar se todos os arquivos do agente estão lá, se a versão
+ está correta e se as permissões e donos também.
+
+ \item [2.2] Verificar em "/etc/sudoers" se o arquivo contém uma e apenas uma
+ linha/regra/código que dá permissão de root sem password para o usuário
+ seed\_mec. (Será a última linha com "seed\_mec ALL=NOPASSWD: ALL").
+ \end{enumerate}
+
+\item Testar coleta e envio do XML com inventário da máquina. Verificar se o XML
+ coletado contém todas as informações do inventário e que elas estão corretas.
+ Em especial, verificar a tag "project" dentro do XML, para saber se ela
+ está de acordo com o projeto ao qual a máquina faz parte:
+ 0 - Máquinas ProInfo;
+ 1 - UCA Classmates;
+ 2 - UCA Servers;
+ 3 - Projetores ProInfo.
+ Também dar atenção para os dados da rede: só deverão existir (valor
+ diferente de 0) se forem máquinas ProInfo. Se for uma máquina dos projetos
+ 1-3, o valor deverá ser 0.
+
+ \begin{enumerate}
+ \item [3.1] Executar (como usuário seed\_mec, rodar "agent.sh") o agente e
+ verificar os resultados no log (Observação: a coleta de rede demorará
+ ao menos um dia para acontecer - a partir das 0h do dia seguinte ao
+ da instalação. Até lá, espera-se que o agente não consiga gerar nem
+ enviar o XML);
+
+ \item [3.2] Esperar a execução automática do agente e verificar os
+ resultados no log, para saber se tudo ocorreu corretamente (envio do
+ XML - talvez seja necessário esperar até o dia seguinte para acontecer,
+ por causa da coleta de rede);
+ \end{enumerate}
+
+ \item Testar a auto-atualização do agente, modificando o valor dentro do
+ arquivo version (para qualquer outro, inclusive um valor
+ "corrompido"). Verificar se o agente consegue baixar o pacote de
+ atualização. Verificar se o link para update (de download do pacote
+ de atualização) está correto (ver log do cliente).
+
+ \begin{enumerate}
+ \item [4.1] Executar o agente (como seed\_mec, rodar "agent.sh") e
+ verificar se o pacote de atualização foi corretamente baixado e
+ instalado;
+
+ \item [4.2] Esperar a próxima execução do agente e verificar se o pacote de
+ atualização foi corretamente baixado e instalado;
+
+ \item [4.3] Lembrar de verificar se os arquivos não estão corrompidos, com
+ um script auxiliar que eu vou repassar depois.
+ \end{enumerate}
+
+ \item Executar o "integrity-checker.sh" e verificar se ele retorna algum
+ erro e, caso aconteça, significa que algum arquivo está corrompido
+ (hash está errada, quando compara com as hashs em .md5sum - ou
+ corrompimento, ou modificação manual, com excessão dos logs e
+ arquivos de dados, que não têm uma contraparte em .md5sum) e o agente
+ deve baixar a atualização e se autoatualizar.
+
+ \begin{enumerate}
+ \item [5.1] Modificar um arquivo propositalmente e rodar o
+ "integrity-checker.sh", que deve forçar a atualização do agente.
+ Verificar resultados.
+ \end{enumerate}
+
+ \item Baixar novamente o agente e instalar por cima da instalação atual,
+ verificando se o agente foi mesmo/consegue ser reinstalado.
+
+ \item Testar o instalador em todas as vertentes possíveis, como quando
+ existe um agente previamente instalado (que deverá ser substituído
+ pelo novo agente).
+
+ \begin{enumerate}
+ \item [7.1] Modificar as permissões do crontab do usuário seed\_mec para 000
+ (para isso, o usuário já deverá existir). Assim será possível verificar
+ se a instalação retorna um erro e realiza a coleta de informações do
+ agente instalado.
+
+ \item [7.2] Verificar se todos os links descritos durante a instalação estão
+ corretos.
+
+ \item [7.3] Verificar se o arquivo de log, em caso de erro durante a
+ execução do novo agente instalado, está sendo criado corretamente (com
+ conteúdo) e se o instalador ainda mostra na tela as mensagens finais
+ (a partir de "feito!", ou se o resultado está ficando dentro do arquivo
+ de log.
+ \end{enumerate}
+
+ \item Testar qualquer outro aspecto que julgar necessário.
+
+\end{enumerate}