ntroducere

Proiectul cu Tema : Realizarea unei pagin web interactive la firma Agenia Cronos utliznd PHP si MySQL a fost
realizat n urma analizei asupra sistemului de activitate al unei firme care are nevoie de o paginta web pe internet.
Scopul acestei lucrari este analiza sistemului existent, analiza ageniei din punct de vedere economic, construirea
arhitecturii noului sitem si proiectarea logic i fizic a componentelor lui. Astfel se va obine proiectarea sistemului
informatic n condiiile abordrii structurate a noului sitem. Pe baza proiectului se va realiza o aplicaie utiliznd PHP i
MySQL.
Pe aceast pagina se vor gasi toate informaiile despre firm si baza de date a candidailor (pentru angajarea sau
studiul peste hotare) i companiilor (care ofera locuri de munca sau de studii), ct i date adiministrative ale firmei.
Prin realizarea acestei aplicaii membrii ageniei vor avea acces la bazele de date de pe internet, vor putea
modifica(aduga sau terge) datele prin introducerea numelui de utilizator i parola.
n urma analizei sistemului vor fi evideniate puctele slabe si cele forte ale firmei , se va propune o noua soluie
informatica pentru mbunatirea , rezolvarea problemelor de transfer de date, ct si securizarea lor din cadrul
ageniei.
La realizarea acestui proiect se vor folosi metode de proiectarea a sistemelor informatice, programarea n PHP i
MySQL a aplicaiei.
Capitolul 1
Studiul , analiza i prezentarea sistemului actual
Rolul i poziia ageniei n sistemul economico- social naional i n ramura de activitate
Agenia CRONOS este o firma cu sediul n Bucureti, Romnia i a fost nfiinat n anul 2004 de ctre un cetean
romn. Ea a aprut datorit faptului ca s-a nregistrat un numr mare de persoane plecate ilegal la munc n Italia din
Romnia. Prin intermediul acestei agenii omerii, dorind angajarea la munca peste hotare, se nregistrau n baza de
date a ageniei , cu toate datele personale(nume,vrsta,specialitate,diplom de studii , etc.) ndeplinind formularul de
nscriere. n moment ce agenia colabora cu mai multe firme- companii din Italia,gsea locuri de munca sau studii
pentru ceteni straini(n acest caz ceteni romni.) Prin contractul de colaborare ntre firme i agenie se intocmeau
contracte de munca ( la consulatul din Bucuresti), se efectuau legalizri ale actelor necesare pentru viza de munca sau
studiii i se asigura transportul.
Una din cauzele principale ale migraiei ilegale peste hotare, preponderent a forei de munca din Romnia soldat n
majoritatea cazurilor cu consecinte grave) trafic de fiine umane, n mod special de femei,decese,munca la negru,
destramarea multor familii, copii orfani etc.) rezida n lipsa accesului la informaii veridice despre modalitaile de
angajare legal n straintate.
Astfel , n 2002 au fost aprobai agenii economici titulari ai licenelor pentru activitatea legal de plasare n cmpul
muncii al lucratorilor emigrani n alte state, n urma careia a aprut Agenia Cronos .
Studiul i analiza sitemului existent al Ageniei Cronos
Agenia Cronos , este o agenie care are sediul central n Bucuresti
1.2.1 Caracteristici generale ale sistemului
Agenia Cronos caut firme, organizaii, companii care ofera locuri de munca pentru strini. ntocmete contracte de
colaborare cu acestea, primesc informaii sptmnal de cereri i respectiv, n urma analizei , datele, informaiile se
trimit reprezentanilor din Romnia prin :
Pot diplomatic
DHL
TNT
UPS
Pota, Fax sau Internet
Reprezentantul, nregistreaz n baza de date omeri, specialiti, persoane ce doresc s se angajeze la munca peste
hotare, conform cererii . Sptmnal, sunt trimise rapoarte prin aceleai mijloace sediului central .
Vicedirectorul analizeaz cererea i oferta de muca si trimite Directorului central propuneri si sugestii. Acesta din urm
analizeaz, accepta, aproba sau respinge propunerea. Propunerea acceptat este trimisa Directorului Adjunct . Acesta
numete agentul care trebuie s ntocmeasc actele cu firma, compania care cere brae de munca. n acelai timp
reprezentana caut persoanele solicitate.
Urmeaz eliberarea Contractelor de Munc i al Vizelor cu ajutorul consultanilor reprezentani . Dup ridicarea vizelor
are loc plecarea angajailor la locul de munc organizat de catre agentul reprezentant. Dupa expirarea termenului de
munca sunt obligai s se intoarc n ar.








Incearca pe www.documentareonline.com
Documentareonline.com are ca principal obiect de activitate oferirea de consultanta si
bibliografie pentru realizarea diferitelor proiecte stiintifice. Documentareonline.com
dispune de cea mai mare arhiva cu disertatii din Romania, oferind o mare parte din
resursele necesare in procesul de documentare si aprofundare a cunostintelor, cu
precadere in vederea sustinerii examenului de licenta. Toate disertatiile sunt bine
documentate, beneficiaza de o tehnoredactare impecabila, folosesc diacritice, au note de
subsol, tabele, grafice anexe si studii de caz.
eased.
[19][20]

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II.
[6]
PHP 5 included
new features such as improved support for object-oriented programming, the PHP Data Objects
(PDO) extension (which defines a lightweight and consistent interface for accessing databases),
and numerous performance enhancements.
[21]
In 2008 PHP 5 became the only stable version
under development. Late static binding had been missing from PHP and was added in version
5.3.
[22][23]

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,
2008, because of the GoPHP5 initiative,
[24]
provided by a consortium of PHP developers
promoting the transition from PHP 4 to PHP 5.
[25][26]

PHP interpreters are available on most existing 32-bit and 64-bit operating systems, either by
building them from the PHP source code, or by using pre-built binaries.
[27]
For the PHP versions
5.3 and 5.4, the only available Microsoft Windows binary distributions were 32-
bit x86 builds,
[28][29]
requiring Windows 32-bit compatibility mode while using Internet Information
Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64 builds
available for Microsoft Windows.
[30]

PHP 6 and Unicode[edit]
PHP received mixed reviews due to lacking native Unicode support at the core language
level.
[31][32]
In 2005, a project headed by Andrei Zmievski was initiated to bring native Unicode
support throughout PHP, by embedding the International Components for Unicode (ICU) library,
and representing text strings as UTF-16 internally.
[33]
Since this would cause major changes both
to the internals of the language and to user code, it was planned to release this as version 6.0 of
the language, along with other major features then in development.
[34]

However, a shortage of developers who understood the necessary changes, and performance
problems arising from conversion to and from UTF-16, which is rarely used in a web context, led
to delays in the project.
[35]
As a result, a PHP 5.3 release was created in 2009, with many non-
Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its
current form was officially abandoned, and a PHP 5.4 release was prepared containing most
remaining non-Unicode features from PHP 6, such as traits and closure re-binding.
[36]
Initial
hopes were that a new plan would be formed for Unicode integration, but as of 2014 none has
been adopted.
During the years before the release of PHP 5.3 and 5.4, some books were published based on
the expected feature set of PHP 6.0, including both the Unicode work and the features which
were later backported to other releases. There is therefore some debate over whether a new
major version of PHP, with or without Unicode support, should be called "PHP 6", or if the version
should be skipped to avoid confusion.
Release history[edit]
Key
Color Meaning Development
Red Old release No development
Yellow Stable release Security fixes
Green Stable release Bug and security fixes
Blue Future release New features
Ver
sio
n
Rele
ase
date
Sup
port
ed
until
[
37]

Notes
1.0
8
June
199
5

Officially called "Personal Home Page Tools (PHP Tools)". This is the first use
of the name "PHP".
[6]

2.0
1
Nov
emb
er
199

7
3.0
6
June
199
8
20
Octo
ber
2000
Development moves from one person to multiple developers. Zeev Suraski and
Andi Gutmans rewrite the base for this version.
[6]

4.0
22
May
200
0
23
Janu
ary
2001
Added more advanced two-stage parse/execute tag-parsing system called the
Zend engine.
[38]

4.1
10
Dec
emb
er
200
1
12
Marc
h
2002
Introduced 'superglobals' ($_GET, $_POST, $_SESSION, etc.)
[38]

4.2
22
April
200
2
6
Sept
emb
er
2002
Disabled register_globals by default. Data received over the network is not
inserted directly into the global namespace anymore, closing possible security
holes in applications.
[38]

4.3
27
Dec
emb
er
200
2
31
Marc
h
2005
Introduced the command-line interface (CLI), to supplement the CGI.
[38][39]

4.4
11
July
200
5
7
Augu
st
2008
Fixed a memory corruption bug, which required breaking binary compatibility
with extensions compiled against PHP version 4.3.x.
[40]

5.0
13
July
200
4
5
Sept
emb
er
2005
Zend Engine II with a new object model.
[41]

5.1
24
Nov
emb
er
200
5
24
Augu
st
2006
Performance improvements with introduction of compiler variables in re-
engineered PHP Engine.
[41]
Added PHP Data Objects (PDO) as a consistent
interface for accessing databases.
[42]

5.2
2
Nov
emb
er
200
6
6
Janu
ary
2011
Enabled the filter extension by default. Native JSON support.
[41]

5.3
30
June
200
9
July
2014
[43]

Namespace support; late static bindings, Jump label (limited goto),
Native closures, Native PHP archives (phar), garbage collection for circular
references, improved Windows support, sqlite3, mysqlnd as a replacement for
libmysql as underlying library for the extensions that work with MySQL, fileinfo
as a replacement for mime_magic for better MIME support, the
Internationalization extension, and deprecation of ereg extension.
5.4
1
Mar
ch
201
2
1
Marc
h
2015
[44]

Trait support, short array syntax support. Removed
items: register_globals, safe_mode, allow_call_time_pass_referenc
e,session_register(), session_unregister() and session_is_regist
ered(). Built-in web server.
[45]
Several improvements to existing features,
performance and reduced memory requirements.
5.5
20
June
201
20
June
2016
Support for generators, finally blocks for exceptions handling, OpCache
(based on Zend Optimizer+) bundled in official distribution.
[46]

3
[44]

5.6
No
date
set
3
year
s
after
relea
se
[44]

Constant scalar expressions, variadic functions, argument unpacking, new
exponentiation operator, extensions of the use operator, new phpdbg debugger
as a SAPI module, and other smaller improvements.
[47]

Beginning on June 28, 2011, the PHP Group began following a timeline for when new versions of
PHP will be released.
[44]
Under this timeline, at least one release should occur every month. Once
per year, a minor release should occur which can include new features. Every minor release
should at least have 2 years of security and bug fixes, followed by at least 1 year of only security
fixes, for a total of a 3 year release process for every minor release. No new features (unless
small and self-contained) will be introduced into a minor release during the 3-year release
process.
Syntax[edit]
Main article: PHP syntax and semantics


eased.
[19][20]

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II.
[6]
PHP 5 included
new features such as improved support for object-oriented programming, the PHP Data Objects
(PDO) extension (which defines a lightweight and consistent interface for accessing databases),
and numerous performance enhancements.
[21]
In 2008 PHP 5 became the only stable version
under development. Late static binding had been missing from PHP and was added in version
5.3.
[22][23]

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,
2008, because of the GoPHP5 initiative,
[24]
provided by a consortium of PHP developers
promoting the transition from PHP 4 to PHP 5.
[25][26]

PHP interpreters are available on most existing 32-bit and 64-bit operating systems, either by
building them from the PHP source code, or by using pre-built binaries.
[27]
For the PHP versions
5.3 and 5.4, the only available Microsoft Windows binary distributions were 32-
bit x86 builds,
[28][29]
requiring Windows 32-bit compatibility mode while using Internet Information
Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64 builds
available for Microsoft Windows.
[30]

PHP 6 and Unicode[edit]
PHP received mixed reviews due to lacking native Unicode support at the core language
level.
[31][32]
In 2005, a project headed by Andrei Zmievski was initiated to bring native Unicode
support throughout PHP, by embedding the International Components for Unicode (ICU) library,
and representing text strings as UTF-16 internally.
[33]
Since this would cause major changes both
to the internals of the language and to user code, it was planned to release this as version 6.0 of
the language, along with other major features then in development.
[34]

However, a shortage of developers who understood the necessary changes, and performance
problems arising from conversion to and from UTF-16, which is rarely used in a web context, led
to delays in the project.
[35]
As a result, a PHP 5.3 release was created in 2009, with many non-
Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its
current form was officially abandoned, and a PHP 5.4 release was prepared containing most
remaining non-Unicode features from PHP 6, such as traits and closure re-binding.
[36]
Initial
hopes were that a new plan would be formed for Unicode integration, but as of 2014 none has
been adopted.
During the years before the release of PHP 5.3 and 5.4, some books were published based on
the expected feature set of PHP 6.0, including both the Unicode work and the features which
were later backported to other releases. There is therefore some debate over whether a new
major version of PHP, with or without Unicode support, should be called "PHP 6", or if the version
should be skipped to avoid confusion.
Release history[edit]
Key
Color Meaning Development
Red Old release No development
Yellow Stable release Security fixes
Green Stable release Bug and security fixes
Blue Future release New features
Ver
sio
n
Rele
ase
date
Sup
port
ed
until
[
37]

Notes
1.0
8
June
199
5

Officially called "Personal Home Page Tools (PHP Tools)". This is the first use
of the name "PHP".
[6]

2.0
1
Nov
emb
er
199
7

3.0
6
June
199
8
20
Octo
ber
2000
Development moves from one person to multiple developers. Zeev Suraski and
Andi Gutmans rewrite the base for this version.
[6]

4.0
22
May
200
0
23
Janu
ary
2001
Added more advanced two-stage parse/execute tag-parsing system called the
Zend engine.
[38]

4.1
10
Dec
emb
er
200
1
12
Marc
h
2002
Introduced 'superglobals' ($_GET, $_POST, $_SESSION, etc.)
[38]

4.2
22
April
200
2
6
Sept
emb
er
2002
Disabled register_globals by default. Data received over the network is not
inserted directly into the global namespace anymore, closing possible security
holes in applications.
[38]

4.3
27
Dec
emb
er
200
2
31
Marc
h
2005
Introduced the command-line interface (CLI), to supplement the CGI.
[38][39]

4.4
11
July
200
5
7
Augu
st
2008
Fixed a memory corruption bug, which required breaking binary compatibility
with extensions compiled against PHP version 4.3.x.
[40]

5.0
13
July
200
4
5
Sept
emb
er
2005
Zend Engine II with a new object model.
[41]

5.1
24
Nov
emb
er
200
5
24
Augu
st
2006
Performance improvements with introduction of compiler variables in re-
engineered PHP Engine.
[41]
Added PHP Data Objects (PDO) as a consistent
interface for accessing databases.
[42]

5.2
2
Nov
emb
er
200
6
Janu
ary
2011
Enabled the filter extension by default. Native JSON support.
[41]

6
5.3
30
June
200
9
July
2014
[43]

Namespace support; late static bindings, Jump label (limited goto),
Native closures, Native PHP archives (phar), garbage collection for circular
references, improved Windows support, sqlite3, mysqlnd as a replacement for
libmysql as underlying library for the extensions that work with MySQL, fileinfo
as a replacement for mime_magic for better MIME support, the
Internationalization extension, and deprecation of ereg extension.
5.4
1
Mar
ch
201
2
1
Marc
h
2015
[44]

Trait support, short array syntax support. Removed
items: register_globals, safe_mode, allow_call_time_pass_referenc
e,session_register(), session_unregister() and session_is_regist
ered(). Built-in web server.
[45]
Several improvements to existing features,
performance and reduced memory requirements.
5.5
20
June
201
3
20
June
2016
[44]

Support for generators, finally blocks for exceptions handling, OpCache
(based on Zend Optimizer+) bundled in official distribution.
[46]

5.6
No
date
set
3
year
s
after
relea
se
[44]

Constant scalar expressions, variadic functions, argument unpacking, new
exponentiation operator, extensions of the use operator, new phpdbg debugger
as a SAPI module, and other smaller improvements.
[47]

Beginning on June 28, 2011, the PHP Group began following a timeline for when new versions of
PHP will be released.
[44]
Under this timeline, at least one release should occur every month. Once
per year, a minor release should occur which can include new features. Every minor release
should at least have 2 years of security and bug fixes, followed by at least 1 year of only security
fixes, for a total of a 3 year release process for every minor release. No new features (unless
small and self-contained) will be introduced into a minor release during the 3-year release
process.
Syntax[edit]
Main article: PHP syntax and semantics

eased.
[19][20]

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II.
[6]
PHP 5 included
new features such as improved support for object-oriented programming, the PHP Data Objects
(PDO) extension (which defines a lightweight and consistent interface for accessing databases),
and numerous performance enhancements.
[21]
In 2008 PHP 5 became the only stable version
under development. Late static binding had been missing from PHP and was added in version
5.3.
[22][23]

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,
2008, because of the GoPHP5 initiative,
[24]
provided by a consortium of PHP developers
promoting the transition from PHP 4 to PHP 5.
[25][26]

PHP interpreters are available on most existing 32-bit and 64-bit operating systems, either by
building them from the PHP source code, or by using pre-built binaries.
[27]
For the PHP versions
5.3 and 5.4, the only available Microsoft Windows binary distributions were 32-
bit x86 builds,
[28][29]
requiring Windows 32-bit compatibility mode while using Internet Information
Services (IIS) on a 64-bit Windows platform. PHP version 5.5 made the 64-bit x86-64 builds
available for Microsoft Windows.
[30]

PHP 6 and Unicode[edit]
PHP received mixed reviews due to lacking native Unicode support at the core language
level.
[31][32]
In 2005, a project headed by Andrei Zmievski was initiated to bring native Unicode
support throughout PHP, by embedding the International Components for Unicode (ICU) library,
and representing text strings as UTF-16 internally.
[33]
Since this would cause major changes both
to the internals of the language and to user code, it was planned to release this as version 6.0 of
the language, along with other major features then in development.
[34]

However, a shortage of developers who understood the necessary changes, and performance
problems arising from conversion to and from UTF-16, which is rarely used in a web context, led
to delays in the project.
[35]
As a result, a PHP 5.3 release was created in 2009, with many non-
Unicode features back-ported from PHP 6, notably namespaces. In March 2010, the project in its
current form was officially abandoned, and a PHP 5.4 release was prepared containing most
remaining non-Unicode features from PHP 6, such as traits and closure re-binding.
[36]
Initial
hopes were that a new plan would be formed for Unicode integration, but as of 2014 none has
been adopted.
During the years before the release of PHP 5.3 and 5.4, some books were published based on
the expected feature set of PHP 6.0, including both the Unicode work and the features which
were later backported to other releases. There is therefore some debate over whether a new
major version of PHP, with or without Unicode support, should be called "PHP 6", or if the version
should be skipped to avoid confusion.
Release history[edit]
Key
Color Meaning Development
Red Old release No development
Yellow Stable release Security fixes
Green Stable release Bug and security fixes
Blue Future release New features
Ver
sio
n
Rele
ase
date
Sup
port
ed
until
[
37]

Notes
1.0
8
June
199
5

Officially called "Personal Home Page Tools (PHP Tools)". This is the first use
of the name "PHP".
[6]

2.0
1
Nov
emb
er
199
7

3.0
6
June
199
20
Octo
ber
Development moves from one person to multiple developers. Zeev Suraski and
Andi Gutmans rewrite the base for this version.
[6]

8 2000
4.0
22
May
200
0
23
Janu
ary
2001
Added more advanced two-stage parse/execute tag-parsing system called the
Zend engine.
[38]

4.1
10
Dec
emb
er
200
1
12
Marc
h
2002
Introduced 'superglobals' ($_GET, $_POST, $_SESSION, etc.)
[38]

4.2
22
April
200
2
6
Sept
emb
er
2002
Disabled register_globals by default. Data received over the network is not
inserted directly into the global namespace anymore, closing possible security
holes in applications.
[38]

4.3
27
Dec
emb
er
200
2
31
Marc
h
2005
Introduced the command-line interface (CLI), to supplement the CGI.
[38][39]

4.4
11
July
200
5
7
Augu
st
2008
Fixed a memory corruption bug, which required breaking binary compatibility
with extensions compiled against PHP version 4.3.x.
[40]

5.0
13
July
200
4
5
Sept
emb
er
Zend Engine II with a new object model.
[41]

2005
5.1
24
Nov
emb
er
200
5
24
Augu
st
2006
Performance improvements with introduction of compiler variables in re-
engineered PHP Engine.
[41]
Added PHP Data Objects (PDO) as a consistent
interface for accessing databases.
[42]

5.2
2
Nov
emb
er
200
6
6
Janu
ary
2011
Enabled the filter extension by default. Native JSON support.
[41]

5.3
30
June
200
9
July
2014
[43]

Namespace support; late static bindings, Jump label (limited goto),
Native closures, Native PHP archives (phar), garbage collection for circular
references, improved Windows support, sqlite3, mysqlnd as a replacement for
libmysql as underlying library for the extensions that work with MySQL, fileinfo
as a replacement for mime_magic for better MIME support, the
Internationalization extension, and deprecation of ereg extension.
5.4
1
Mar
ch
201
2
1
Marc
h
2015
[44]

Trait support, short array syntax support. Removed
items: register_globals, safe_mode, allow_call_time_pass_referenc
e,session_register(), session_unregister() and session_is_regist
ered(). Built-in web server.
[45]
Several improvements to existing features,
performance and reduced memory requirements.
5.5
20
June
201
3
20
June
2016
[44]

Support for generators, finally blocks for exceptions handling, OpCache
(based on Zend Optimizer+) bundled in official distribution.
[46]

5.6
No
date
3
year
Constant scalar expressions, variadic functions, argument unpacking, new
exponentiation operator, extensions of the use operator, new phpdbg debugger
set s
after
relea
se
[44]

as a SAPI module, and other smaller improvements.
[47]

Beginning on June 28, 2011, the PHP Group began following a timeline for when new versions of
PHP will be released.
[44]
Under this timeline, at least one release should occur every month. Once
per year, a minor release should occur which can include new features. Every minor release
should at least have 2 years of security and bug fixes, followed by at least 1 year of only security
fixes, for a total of a 3 year release process for every minor release. No new features (unless
small and self-contained) will be introduced into a minor release during the 3-year release
process.
Syntax[edit]
Main article: PHP syntax and semantics