Corporation Financial System
1
INDEX
1. Introduction 2. System Analysis a. Existing System b. proposed System 3. Feasibility Report a. Technical Feasibility b. perational Feasibility
c. Economical Feasibility !. System Re"uirement Speci#ication $ocument a. %er%ie&
b. 'odules $escription c. (rocess Flo& d. S$)* 'ethodology e. So#t&are Re"uirements #. +ard&are Re"uirements ,. System $esign a. $F$
2
b. E-R diagram c. .') d. $ata $ictionary /. Technology $escription 0. *oding 1. Testing 2 $ebugging Techni"ues 3. utput Screens
14. Reports 11. Future Enhancements 12. *onclusion 13. 5ibliography
3
INTRODUCTION
4
Corporation Financial System pro%ides the solution as scholarships or bene#its o# loans #or minority peoples or students through System. Corporation financial system’s history is a dome of many- coloured glass, presenting to insiders a different view from each angle of observation. As we observe the historical dome from different angles the financial system graduates from landed wealth to financial wealth, from family businesses to corporations, from debtor’s prison to limited liability, from mercantilism to laissez-faire, from free banking to central banking. Multinational corporations are not a late development in the corporate form of business organization, but rank among the first corporations organized. A financial system is a framework that facilitates financial transactions, and these transactions re uire an accepted form of money, something that can serve as a medium of e!change, a unit of account, a store of wealth, and a standard of deferred payment. "he various evolutionary threads of corporate development do not necessarily stem from a single root, but the primal seed of the corporate business organizations may have lain embedded in the double-entry method of bookkeeping, which records all business transactions within the logical framework of formula that e uates total business assets with total business liabilities plus owner’s e uity.
5
System Analysis
6
Purpose of the System
Corporation Financial System provides the solution as scholarships or benefits of loans for minority peoples or students through #ystem. E!istin" System • Existing system has no #acility to ma6e re"uest #or putting scholorship
#orms 7loan #orms8 #rom their home or o##ice. • Existing system has no #acility to pro%ide &hich schemes are a%ailable #or Eligible peoples 7minorities8.
Propose# System
The de%elopment o# this ne& system contains the #ollo&ing acti%ities9 &hich try to reco%er the problems #rom the pre%ious system: • • • • • • Secure registration and pro#ile management #acilities #or system users Trac6ing member;s acti%ities and progress. Facilitating communication - $iscussion #orum. 5asic and ad%ance admin #acilities li6e added as #ollo&s A. Admin 5. Applicant *. 'onitor $. Executi%es E. 5oard $irector Num$er of .o#ules The system a#ter care#ul analysis has been identi#ied to be presented &ith the #ollo&ing modules: The 'odules in%ol%ed are 1. Admin 2. 'onitor 3. 5oard $irector !. executi%e ,. applicant
14
The
/. Security and Authentication 0. Reports
A#min .o#ule 1. Admin collects %arious minorities #inancial corporation o##ices and load that details to the system. 2. Admin can %ie& the %arious details o# minorities; #inancial corporation o##ices. 3. (ost the aims and ob=ecti%es o# this system. !. Register a%ailable loan details and scheme details. ,. (ro%ide the details o# channeli>ing agencies. /. Admin can register the details o# board directors9 executi%es9 monitors in this system. 0. Eie& the details o# board directors9 executi%es9 monitors o# this system. 1. Eie& the applicant loan re"uest details and assign to executi%e. 3. Eie& his personal pro#ile. 14. Send %arious mails according to system to the system users.
'oar# Director .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details.
15
3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. E!ecuti*e .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. 14. (ost the details o# success stories o# successors
.onitor .o#ule 1. %ie& his personal pro#ile.
16
2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. Applicant .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. 14. Apply #or the loans and %ie& the status o# loans details.
17
Security an# Authentication 1. .ser Registration. 2. )ogin as board director or monitor or executi%e9 Administrator 3. *hange pass&ord !. Forgot (ass&ord Reports In this 'odule the administrator9 board director9 monitor9 executi%e can generate di##erent types o# reports.
18
Process Flo+
19
The 'odel 2 architecture #or designing FS( pages is in reality9 'odel Eie& *ontroller 7'E*8 applied to &eb applications. +ence the t&o terms can be used interchangeably in the &eb &orld. 'E* originated in SmallTal6 and has since made its &ay into Fa%a community. 'odel 2 architecure and its deri%ati%es are the cornerstones #or all serious and industrial strength &eb applications designed in the real &orld. +ence it is essential #or you understand this paradigm thoroughly. The main di##erence bet&een 'odel 1 and 'odel 2 is that in 'odel 29 a controller handles the user re"uest instead o# another FS(. The controller is implemented as a Ser%let. The #ollo&ing steps are executed &hen the user submits the re"uest. 1. The *ontroller Ser%let handles the user;s re"uest. 7This means the hyperlin6 in the FS( should point to the controller ser%let8. 2. The *ontroller Ser%let then instantiates appropriate Fa%a5eans based on the re"uest parameters 7and optionally also based on session attributes8. 3. The *ontroller Ser%let then by itsel# or through a controller helper communicates &ith the middle tier or directly to the database to #etch the re"uired data. The *ontroller sets the resultant Fa%a5eans 7either same or a ne& one8 in one o# the #ollo&ing contexts @ re"uest9 session or application. The controller then dispatches the re"uest to the next %ie& based on the re"uest .R). The Eie& uses the resultant Fa%a5eans #rom Step ! to display data. Gote that there is no presentation logic in the FS(. The sole #unction o# the FS( in 'odel 2 architecture is to display the data #rom the
20
!.
,.
/.
Fa%a5eans set in the re"uest9 session or application scopes.
'odel-2 Architecture.
21
SD&C .ET%ODO&O/IES
22
This document play a %ital role in the de%elopment o# li#e cycle 7S$)*8 as it describes the complete re"uirement o# the system. It means #or use by de%elopers and &ill be the basic during testing phase. Any changes made to the re"uirements in the #uture &ill ha%e to go through #ormal change appro%al process. S(IRA) ' $E) &as de#ined by 5arry 5oehm in his 1311 article9 AA spiral 'odel o# So#t&are $e%elopment and Enhancement. This model &as not the #irst model to discuss iterati%e de%elopment9 but it &as the #irst model to explain &hy the iteration models. As originally en%isioned9 the iterations &ere typically / months to 2 years long. Each phase starts &ith a design goal and ends &ith a client re%ie&ing the progress thus #ar. Analysis and engineering e##orts are applied at each phase o# the pro=ect9 &ith an eye to&ard the end goal o# the pro=ect. The steps #or Spiral 'odel can be generali>ed as #ollo&s: • The ne& system re"uirements are de#ined in as much details as possible. This usually in%ol%es inter%ie&ing a number o# users representing all the external or internal users and other aspects o# the existing system. A preliminary design is created #or the ne& system. A #irst prototype o# the ne& system is constructed #rom the preliminary design. This is usually a scaled-do&n system9 and represents an approximation o# the characteristics o# the #inal product. A second prototype is e%ol%ed by a #our#old procedure: 1. E%aluating the #irst prototype in terms o# its strengths9 &ea6ness9 and ris6s. 2. $e#ining the re"uirements o# the second prototype. 3. (lanning an designing the second prototype. !. *onstructing and testing the second prototype.
23
• •
•
•
At the customer option9 the entire pro=ect can be aborted i# the ris6 is deemed too great. Ris6 #actors might in%ol%ed de%elopment cost o%erruns9 operating-cost miscalculation9 or any other #actor that could9 in the customer;s =udgment9 result in a less-than-satis#actory #inal product. The existing prototype is e%aluated in the same manner as &as the pre%ious prototype9 and i# necessary9 another prototype is de%eloped #rom it according to the #our#old procedure outlined abo%e. The preceding steps are iterated until the customer is satis#ied that the re#ined prototype represents the #inal product desired. The #inal system is constructed9 based on the re#ined prototype. The #inal system is thoroughly e%aluated and tested. Routine maintenance is carried on a continuing basis to pre%ent large scale #ailures and to minimi>e do&n time.
•
• • •
The follo+in" #ia"ram sho+s ho+ a spiral mo#el acts li0e
24
Fi" 1234Spiral .o#el
AD5ANTA/ES • Estimates7i.e. schemes schedule etc .8 become more relistic as &or6 progresses9 because important issues disco%ed earlier.
25
• •
It is more able to cope &ith the changes that are so#t&are de%elopment generally entails. So#t&are engineers can get their hands in and start &oring on the core o# a pro=ect earlier.
26
SOFT6ARE RE7UIRE.ENT AND %ARD6ARE RE7UIRE.ENT
27
Soft+are Re-uirements
perating System .ser Inter#ace *lient-side Scripting (rogramming )anguage Beb Applications I$Eing agencies78 1! : %ie& *hannli>ing agencies78 , : post scheme details78 ! : %ie& aims ob=ecti%es78 Aims b=ecti%es 3 : post aims ob=ecti%es78 1 : Register minorities #inancial c orporation o##ices78 Admin 'inorities Financial *orporation o##ice 2 : %ie& minorities #inancial c orporation o##ic es78
*hannli>ing agencies
0 : post loan details78 / : %ie& scheme details78
11 : %ie& applican loan re"uests and assign to executi%es78 12 : %ie& Success Stories78 Success Stories
)oan Re"uests
62
'oar# Director
Register Channlizing agencies
Loans Schemes
* ! vie% Channlizing agencies"# ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details"# & ! vie% scheme details"# Minorities Financial Corporation office ! vie% minorities financial corporation offices"# 0oard 1irector $ ! vie% aims objectives"# ) ! vie% Success St ories"# Aims Objectives Success Stories
.onitor
Register Channlizing agencies
Loans Schemes
* ! vie% Channlizing agencies"# ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details"# & ! vie% scheme details"# Minorities Financial Corporation office ! vie% minorities financial corporation offices"# Monitor $ ! vie% aims objectives"# ) ! vie% Success St ories"# Aims Objectives Success Stories
E!ecuti*e
63
Schemes
Loans
Register Channlizing agencies
Aims Objectives
( ! vie% board directors- e.ecutives- monitor details"# Minorities Financial Corporation office
' ! vie% loan details"# & ! vie% scheme details"#
* ! vie% Channlizing agencies"#
$ ! vie% aims objectives"# Loan Requests + ! vie% assign loan requests and give status of requests"#
! vie% minorities financial corporation offices"# Success Stories ) ! vie% Success St ories"# 2.ecutive
Applicant
Loans Schemes Register
Channlizing agencies ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details and appl3 for loan"# * ! vie% Channlizing agencies"# Minorities Financial Corporation office
Aims Objectives & ! vie% scheme details"# ! vie% minorities financial corporation offices"# $ ! vie% aims objectives"# Success Stories + ! vie% status of loan requests"# Loan Requests Applicant ) ! vie% Success Stories"#
64
Acti*ity Dia"rams
65
66
67
A#min Acti*ity Dia"ram
Admin
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
Register Aims Objectives Register MFC Officess post scheme 43pes
post loans Send 2mails vie% Success stories
5ie% MFC Offices vie% Scheme 43pes vie% Loans
vie% Aims Objectives
Register board directors- e.ecutives- monitors
68
'oar# Director Acti*ity Dia"ram
0oard 1irector
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices vie% Scheme 43pes
vie% Success stories Send 2mails vie% Loans vie% board directors- e.ecutives- monitors 5ie% 2mails
69
.onitor Acti*ity Dia"ram
Monitor
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices vie% Scheme 43pes
vie% Success stories Send 2mails vie% Loans vie% board directors- e.ecutives- monitors 5ie% 2mails
70
E!ecuti*e Acti*ity Dia"ram
2.ecutive
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices
vie% Loans
vie% Success stories Send 2mails 6ost Succes Stories 5ie% 2mails
vie% Scheme 43pes
vie% board directors- e.ecutives- monitors
71
Applicant Acti*ity Dia"ram
Applicant
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices
vie% Loans and appl3 5ie% Loan status
vie% Success stories Send 2mails 5ie% 2mails
vie% Scheme 43pes
6ost Succes Stories
vie% board directors- e.ecutives- monitors
72
Architecture Dia"ram
73
Component Dia"ram
74
75
Deployment Dia"ram
76
77
Data Dictionary
78
User.aster
Column Name .serid .sername (ass&ord )ogintype &ocation city State country ,ip contactno Email Photo S-uestion Sans+er
Data type Gumber 5archar8 Earchar2 Earchar2 *archar8 5archar8 5archar8 5archar8 5archar8 5archar8 5archar8 'lo$ 5archar8 5archar8
Si,e
Constratints (rimary 6ey
83 24 1, 83 1< 1< 1< 13 13 93
ed 'ar6up )anguage89 but speciali>ed to hypertext and adapted to the Beb. The idea behind +ypertext is that instead o# reading text in rigid linear structure9 &e can easily =ump #rom one point to another point. Be can na%igate through the in#ormation based on our interest and pre#erence. A mar6up language is simply a series o# elements9 each delimited &ith special characters that de#ine ho& text or other items enclosed &ithin the elements should be displayed. +yperlin6s are underlined
85
or emphasi>ed &or6s that load to other documents or some portions o# the same document. +T') can be used to display any type o# document on the host computer9 &hich can be geographically at a di##erent location. It is a %ersatile language and can be used on any plat#orm or des6top. +T') pro%ides tags 7special codes8 to ma6e the document loo6 attracti%e. +T') tags are not case-sensiti%e. .sing graphics9 #onts9 di##erent si>es9 color9 etc.9 can enhance the presentation o# the document. Anything that is not a tag is part o# the document itsel#. 5asic +T') Tags: LM ---N speci#ies comments *reates hypertext lin6s Formats text as bold Formats text in large #ont. *ontains document L*EGTERN...L5.) 5eyond the language9 there is the Fa%a %irtual machine. The Fa%a %irtual machine is an important element o# the Fa%a technology. The %irtual machine can be embedded &ithin a &eb bro&ser or an operating system. nce a piece o# Fa%a code is loaded onto a machine9 it is %eri#ied. As part o# the loading process9 a class loader is in%o6ed and does byte code %eri#ication ma6es sure that the code that;s has been generated by the compiler &ill not corrupt the machine that it;s loaded on. 5yte code %eri#ication ta6es place at the end o# the compilation process to ma6e sure that is all accurate and correct. So byte code %eri#ication is integral to the compiling and executing o# Fa%a code. %erall $escription
93
Java Source
Java byte code
JavaVM
(icture sho&ing the de%elopment process o# FAEA (rogram Fa%a programming uses to produce byte codes and executes them. The #irst box indicates that the Fa%a source code is located in a. Fa%a #ile that is processed &ith a Fa%a compiler called =a%ac. The Fa%a compiler produces a #ile called a. class #ile9 &hich contains the byte code. The .*lass #ile is then loaded across the net&or6 or loaded locally on your machine into the execution en%ironment is the Fa%a %irtual machine9 &hich interprets and executes the byte code. >a*a Architecture Fa%a architecture pro%ides a portable9 robust9 high per#orming en%ironment #or de%elopment. Fa%a pro%ides portability by compiling the byte codes #or the Fa%a Eirtual 'achine9 &hich is then interpreted on each plat#orm by the run-time en%ironment. Fa%a is a dynamic system9 able to load code &hen needed #rom a machine in the same room or across the planet. Compilation of co#e Bhen you compile the code9 the Fa%a compiler creates machine code 7called byte code8 #or a hypothetical machine called Fa%a Eirtual 'achine 7FE'8. The FE' is supposed to execute the byte code. The FE' is created #or o%ercoming the issue o# portability. The code is &ritten and compiled #or one machine and interpreted on all machines. This machine is called Fa%a Eirtual 'achine.
Java
.Class
94
*ompiling and interpreting Fa%a Source *ode
Java PC Compiler Java
Source Code ……….. ………..
SPARC (Platform ndependent! Macintosh Compiler Byte code
nterpreter (PC! Java nterpreter (Macintosh! Java nterpreter (Spare!
………..
Compiler
…………
$uring run-time the Fa%a interpreter tric6s the byte code #ile into thin6ing that it is running on a Fa%a Eirtual 'achine. In reality this could be a Intel (entium Bindo&s 3, or SunSAR* station running Solaris or Apple 'acintosh running system and all could recei%e code #rom any computer through Internet and run the Applets. Simple Fa%a &as designed to be easy #or the (ro#essional programmer to learn and to use e##ecti%ely. I# you are an experienced *TT programmer9 learning Fa%a &ill be e%en easier. 5ecause Fa%a inherits the *D'C4OD'C 'ri#"e I# possible9 use a (ure Fa%a F$5* dri%er instead o# the 5ridge and an dri%er. This completely eliminates the client con#iguration re"uired by $5* $5*.
It also eliminates the potential that the Fa%a E' could be corrupted by an error in the nati%e code brought in by the 5ridge 7that is9 the 5ridge nati%e library9 the $5* dri%er manager library9 the $5* dri%er library9 and the database client library8. 6hat Is the >D'C4 OD'C 'ri#"e? The F$5*- $5* 5ridge is a F$5* dri%er9 &hich implements F$5* operations by translating them into database #or &hich an $5* $5* operations. To dri%er is a%ailable. $5* it appears The 5ridge is as a normal application program. The 5ridge implements F$5* #or any implemented as the Sun.=dbc.odbc Fa%a pac6age and contains a nati%e library used to access $5*. The 5ridge is a =oint de%elopment o# Innersole and Fa%a So#t.
102
>D'C connecti*ity The F$5* pro%ides database-independent connecti%ity bet&een the F2EE plat#orm and a &ide range o# tabular data sources. F$5* technology allo&s an Application *omponent (ro%ider to: ? (er#orm connection and authentication to a database ser%er ? 'anager transactions ? 'o%e SU) statements to a database engine #or preprocessing and execution ? Execute stored procedures ? Inspect and modi#y the results #rom Select statements
103
Data$ase A database management system 7$5'S8 is computer so#t&are designed #or the purpose o# managing databases9 a large set o# structured data9 and run operations on the data re"uested by numerous users. Typical examples o# $5'Ss include (ostgreSU)9 racle9 $529 'icroso#t Access9 'icroso#t SU) Ser%er9 Firebird9 SU)ite9 File'a6er and Sybase Adapti%e Ser%er 'ySU)9
Enterprise. $5'Ss are typically used by $atabase administrators in the creation o# $atabase systems. Typical examples o# $5'S use include accounting9 human resources and customer support systems.
riginally #ound only in large companies &ith the computer hard&are needed to support large data sets9 $5'Ss ha%e more recently emerged as a #airly standard part o# any company bac6 o##ice.
Description A $5'S is a complex set o# so#t&are programs that controls the organi>ation9 storage9 management9 and retrie%al o# data in a database. A $5'S includes: ? A modeling language to de#ine the schema o# each database hosted in the $5'S9 according to the $5'S data model. • The #our most common types o# organi>ations are the hierarchical9 net&or69 relational and ob=ect models. In%erted lists and other methods are also used. A gi%en database management system may pro%ide one or more o# the #our models. The optimal structure depends on the natural organi>ation o# the applicationRs data9 and
104
on the applicationRs re"uirements 7&hich include transaction rate 7speed89 reliability9 maintainability9 scalability9 and cost8. • The dominant model in use today is the ad hoc one embedded in SU)9 despite the ob=ections o# purists &ho belie%e this model is a corruption o# the relational model9 since it %iolates se%eral o# its #undamental principles #or the sa6e o# practicality and per#ormance. 'any $5'Ss also support the pen $atabase *onnecti%ity A(I that supports a standard &ay #or programmers to access the $5'S. ? $ata structures 7#ields9 records9 #iles and ob=ects8 optimi>ed to deal &ith %ery large amounts o# data stored on a permanent data storage de%ice 7&hich implies relati%ely slo& access compared to %olatile main memory8.
? A database "uery language and report &riter to allo& users to interacti%ely interrogate the database9 analy>e its data and update it according to the users pri%ileges on data. • • It also controls the security o# the database. $ata security pre%ents unauthori>ed users #rom %ie&ing or updating the database. .sing pass&ords9 users are allo&ed access to the entire database or subsets o# it called sub schemas. For example9 an employee database can contain all the data about an indi%idual employee9 but one group o# users may be authori>ed to %ie& only payroll data9 &hile others are allo&ed access to only &or6 history and medical data. • I# the $5'S pro%ides a &ay to interacti%ely enter and update the database9 as &ell as interrogate it9 this capability allo&s #or
105
managing personal databases. +o&e%er9 it may not lea%e an audit trail o# actions or pro%ide the 6inds o# controls necessary in a multiuser organi>ation. These controls are only a%ailable &hen a set o# application programs are customi>ed #or each data entry and updating #unction.
? A transaction mechanism9 that ideally &ould guarantee the A*I$ properties9 in order to ensure data integrity9 despite concurrent user accesses 7concurrency control89 and #aults 7#ault tolerance8. • • It also maintains the integrity o# the data in the database. The $5'S can maintain the integrity o# the database by not allo&ing more than one user to update the same record at the same time. The $5'S can help pre%ent duplicate records %ia uni"ue index constraintsS #or example9 no t&o customers &ith the same customer numbers 76ey #ields8 can be entered into the database. See A*I$ properties #or more in#ormation 7Redundancy a%oidance8.
The $5'S accepts re"uests #or data #rom the application program and instructs the operating system to trans#er the appropriate data. Bhen a $5'S is used9 in#ormation systems can be changed much more easily as the organi>ationRs in#ormation re"uirements change. Ge& categories o# data can be added to the database &ithout disruption to the existing system. rgani>ations may use one 6ind o# $5'S #or daily transaction processing and then mo%e the detail onto another computer that uses another $5'S better suited #or random in"uiries and analysis. %erall systems design
106
decisions are per#ormed by data administrators and systems analysts. $etailed database design is per#ormed by database administrators. $atabase ser%ers are specially designed computers that hold the actual databases and run only the $5'S and related so#t&are. $atabase ser%ers are usually multiprocessor computers9 &ith RAI$ dis6 arrays used #or stable storage. *onnected to one or more ser%ers %ia a high-speed channel9 hard&are database accelerators are also used in large %olume transaction processing en%ironments. $5'Ss are #ound at the heart o# most database applications. Sometimes $5'Ss are built around a pri%ate multitas6ing 6ernel &ith built-in net&or6ing support although no&adays these #unctions are le#t to the operating system.
107
S7& Structured Uuery )anguage 7SU)8 is the language used to manipulate relational databases. SU) is tied %ery closely &ith the relational model.
In the relational model9 data is stored in structures called relations or tables . SU) statements are issued #or the purpose o#:
Data #efinition $e#ining tables and structures in the database 7$$) used to create9 alter and drop schema ob=ects such as tables and indexes8.
Data manipulation $atabase8.
.sed to manipulate the data &ithin those schema
ob=ects 7$') Inserting9 .pdating9 $eleting the data9 and Uuerying the
A schema is a collection o# database ob=ects that can include: tables9 %ie&s9 indexes and se"uences
)ist o# SU) statements that can be issued against an schema are:
racle database
• • •
A&TER - *hange an existing table9 %ie& or index de#inition 7$$)8 AUDIT - Trac6 the changes made to a table 7$$)8 CO..ENT - Add a comment to a table or column in a table 7$$)8
108
• • • • • • • • • • • •
CO..IT - 'a6e all recent changes permanent 7$') - transactional8 CREATE - *reate ne& database ob=ects such as tables or %ie&s 7$$)8 DE&ETE - $elete ro&s #rom a database table 7$')8 DROP - $rop a database ob=ect such as a table9 %ie& or index 7$$)8 /RANT - Allo& another user to access database ob=ects such as tables or %ie&s 7$$)8 INSERT - Insert ne& data into a database table 7$')8 No AUDIT - Turn o## the auditing #unction 7$$)8 RE5O@E - $isallo& a user access to database ob=ects such as tables and %ie&s 7$$)8 RO&&'AC@ - .ndo any recent changes to the database 7$') Transactional8 SE&ECT - Retrie%e data #rom a database table 7$')8 TRUNCATE - $elete all ro&s #rom a database table 7can not be rolled bac68 7$')8 UPDATE - *hange the %alues o# some data items in a database table 7$')8
109
SER5&ETS Introduction The Fa%a &eb ser%er is Fa%aSo#tRs o&n &eb Ser%er. The Fa%a &eb ser%er is =ust a part o# a larger #rame&or69 intended to pro%ide you not =ust &ith a &eb ser%er9 but also &ith tools. To build customi>ed net&or6 ser%ers #or any Internet or Intranet clientards
EclipseRs &idgets are implemented by a &idget tool6it #or Fa%a called SBT9 unli6e most Fa%a applications9 &hich use the Fa%a standard Abstract Bindo& Tool6it 7ABT8 or S&ing. EclipseRs user inter#ace also le%erages an intermediate D.I layer called FFace9 &hich simpli#ies the construction o# applications based on SBT. Eclipse employs plug-ins in order to pro%ide all o# its #unctionality on top o# 7and including8 the rich client plat#orm9 in contrast to some other applications &here #unctionality is typically hard coded. This plug-in
117
mechanism is a light&eight so#t&are componentry #rame&or6. In addition to allo&ing Eclipse to be extended using other programming languages such as * and (ython9 the plug-in #rame&or6 allo&s Eclipse to &or6 &ith typesetting languages li6e )aTeH9 net&or6ing applications such as telnet9 and database management systems. The plug-in architecture supports &riting any desired extension to the en%ironment9 such as #or con#iguration management. Fa%a and *ES support is pro%ided in the Eclipse S$X. The 6ey to the seamless integration o# tools &ith Eclipse is the plug-in. Bith the exception o# a small run-time 6ernel9 e%erything in Eclipse is a plug-in. This means that a plug-in you de%elop integrates &ith Eclipse in exactly the same &ay as other plug-insS in this respect9 all #eatures are created e"ual. The Eclipse S$X includes the Eclipse Fa%a $e%elopment Tools9 o##ering an I$E &ith a built-in incremental Fa%a compiler and a #ull model o# the Fa%a source #iles. This allo&s #or ad%anced re#actoring techni"ues and code analysis. The I$E also ma6es use o# a &or6space9 in this case a set o# metadata o%er a #lat #ile space allo&ing external #ile modi#ications as long as the corresponding &or6space PresourceP is re#reshed a#ter&ards. The Eisual Editor pro=ect allo&s inter#aces to be created interacti%ely9 hence allo&ing Eclipse to be used as a RA$ tool. The follo+in" is a list of nota$le pro=ects an# plu"4in for the Eclipse IDE2 These pro=ects are maintained by the Eclipse community and hosted by the Eclipse Foundation. 12 Core pro=ects Rich *lient (lat#orm 7(lat#orm8 is the core #rame&or6 that all other Eclipse pro=ects are built on.
118
Fa%a $e%elopment Tools 7F$T8 pro%ides support #or core Fa%a SE. This includes a standalone #ast incremental compiler. 82 Tools pro=ects *a*a EE Ser*ers Follo&ing the success o# the Fa%a plat#orm9 the term application ser%er sometimes re#ers to a Fa%a (lat#orm--Enterprise Edition 7F2EE8 or Fa%a EE , application ser%er. Among the better 6no&n Fa%a Enterprise Edition application ser%ers are Beb)ogic Ser%er 75EA89 F5oss 7Red +at89 BebSphere 7I5'89 FRun 7Adobe89 Apache Deronimo 7Apache Foundation9 based on I5' BebSphere89 racle *!F 7 racle *orporation89 Sun Fa%a System Application Ser%er 7Sun 'icrosystems8 and Dlass#ish Application Ser%er 7based on Sun Fa%a System Application Ser%er8. Fa%a application ser%er &as the #irst open source application ser%er to ha%e achie%ed o##icial compliance &ith the Fa%a Enterprise Speci#ication. 5EA deli%ered the #irst Fa%a EE , certi#ied application ser%er #ollo&ed by Sun 'icrosystemsR re#erence implementation Dlass#ish.
122
The Beb modules are ser%lets and Fa%a Ser%er (ages9 and business logic is built into Enterprise Fa%a5eans 7EF5-3 and later8. The +ibernate pro=ect o##ers an EF5-3 container implementation #or the F5oss Application ser%er. Tomcat #rom Apache and F nAS #rom into &hich these modules can be put. A Fa%a Ser%er (age 7FS(8 is a ser%let #rom Fa%a that executes in a Beb containerKthe Fa%a e"ui%alent o# *DI scripts. FS(s are a &ay to create +T') pages by embedding re#erences to the ser%er logic &ithin the page. +T') coders and Fa%a programmers can &or6 side by side by re#erencing each otherRs code #rom &ithin their o&n. Fa%a5eans are the independent class components o# the Fa%a architecture #rom Sun 'icrosystems. The application ser%ers mentioned abo%e mainly ser%e Beb applications. Some application ser%ers target net&or6s other than the Beb: Session Initiation (rotocol ser%ers9 #or instance9 target telephony net&or6s. b=ectBeb are typical o# containers
Scope of The De*elopment Pro=ect Data$ase Tier The concentration is applied by adopting the racle 1.1
Enterprise %ersions. SU) is ta6en as the standard "uery language. The o%erall business rules are designed by using the po&er o# ()ed architecture. The components are designed using $ream&ea%er and Fa%a ser%er pages po&er the dynamic o# the page design. Data 'ase Connecti*ity Tier
123
The communication architecture is designed by concentrated on the standards o# struts and Fa%a 5eans. The database connecti%ity is established using the Fa%a $atabase connecti%ity. >'OSS F5oss Application Ser%er 7or F5oss AS8 is a #ree so#t&are < open source Fa%a EE-based application ser%er. 5ecause it is Fa%a-based9 F5oss AS is crossplat#orm9 usable on any operating system that Fa%a supports. En*ironment F5oss AS !.4 is a F2EE 1.! application ser%er9 &ith embedded Tomcat ,.,. Any FE' bet&een 1.! and 1., is supported. F5oss can run on numerous operating systems including Bindo&s9 'ac S H9 many ( SIH plat#orms9 and others9 as long as a suitable FE' is present. F5oss AS !.2 is also a F2EE 1.! application ser%er9 but EF5 3 is deployed by de#ault. It re"uires F$X ,. Tomcat / is bundled &ith it. Gext F5oss AS , &ill be Fa%a EE , application ser%er. Pro#uct features ? Failo%er 7including sessions8 ? )oad balancing ? $istributed caching 7using F5oss *ache9 a standalone product8 ? $istributed deployment 7#arming8 ? Enterprise Fa%a5eans %ersion 3
124
125
Co#in"
.FCOffice2=sp LYZ page languageQP=a%aP importQP=a%a.util.VP pageEncodingQPIS 11,3-1PYN LYZpage importQPcom.6&s.m#c.dao..ser'aster$A PYN LYZpage importQPcom.6&s.m#c.bean..ser'aster5eanPYN LY String path Q re"uest.get*ontext(ath78S
126
String
base(ath
Q
re"uest.getScheme78TP:
1
INDEX
1. Introduction 2. System Analysis a. Existing System b. proposed System 3. Feasibility Report a. Technical Feasibility b. perational Feasibility
c. Economical Feasibility !. System Re"uirement Speci#ication $ocument a. %er%ie&
b. 'odules $escription c. (rocess Flo& d. S$)* 'ethodology e. So#t&are Re"uirements #. +ard&are Re"uirements ,. System $esign a. $F$
2
b. E-R diagram c. .') d. $ata $ictionary /. Technology $escription 0. *oding 1. Testing 2 $ebugging Techni"ues 3. utput Screens
14. Reports 11. Future Enhancements 12. *onclusion 13. 5ibliography
3
INTRODUCTION
4
Corporation Financial System pro%ides the solution as scholarships or bene#its o# loans #or minority peoples or students through System. Corporation financial system’s history is a dome of many- coloured glass, presenting to insiders a different view from each angle of observation. As we observe the historical dome from different angles the financial system graduates from landed wealth to financial wealth, from family businesses to corporations, from debtor’s prison to limited liability, from mercantilism to laissez-faire, from free banking to central banking. Multinational corporations are not a late development in the corporate form of business organization, but rank among the first corporations organized. A financial system is a framework that facilitates financial transactions, and these transactions re uire an accepted form of money, something that can serve as a medium of e!change, a unit of account, a store of wealth, and a standard of deferred payment. "he various evolutionary threads of corporate development do not necessarily stem from a single root, but the primal seed of the corporate business organizations may have lain embedded in the double-entry method of bookkeeping, which records all business transactions within the logical framework of formula that e uates total business assets with total business liabilities plus owner’s e uity.
5
System Analysis
6
Purpose of the System
Corporation Financial System provides the solution as scholarships or benefits of loans for minority peoples or students through #ystem. E!istin" System • Existing system has no #acility to ma6e re"uest #or putting scholorship
#orms 7loan #orms8 #rom their home or o##ice. • Existing system has no #acility to pro%ide &hich schemes are a%ailable #or Eligible peoples 7minorities8.
Propose# System
The de%elopment o# this ne& system contains the #ollo&ing acti%ities9 &hich try to reco%er the problems #rom the pre%ious system: • • • • • • Secure registration and pro#ile management #acilities #or system users Trac6ing member;s acti%ities and progress. Facilitating communication - $iscussion #orum. 5asic and ad%ance admin #acilities li6e added as #ollo&s A. Admin 5. Applicant *. 'onitor $. Executi%es E. 5oard $irector Num$er of .o#ules The system a#ter care#ul analysis has been identi#ied to be presented &ith the #ollo&ing modules: The 'odules in%ol%ed are 1. Admin 2. 'onitor 3. 5oard $irector !. executi%e ,. applicant
14
The
/. Security and Authentication 0. Reports
A#min .o#ule 1. Admin collects %arious minorities #inancial corporation o##ices and load that details to the system. 2. Admin can %ie& the %arious details o# minorities; #inancial corporation o##ices. 3. (ost the aims and ob=ecti%es o# this system. !. Register a%ailable loan details and scheme details. ,. (ro%ide the details o# channeli>ing agencies. /. Admin can register the details o# board directors9 executi%es9 monitors in this system. 0. Eie& the details o# board directors9 executi%es9 monitors o# this system. 1. Eie& the applicant loan re"uest details and assign to executi%e. 3. Eie& his personal pro#ile. 14. Send %arious mails according to system to the system users.
'oar# Director .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details.
15
3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. E!ecuti*e .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. 14. (ost the details o# success stories o# successors
.onitor .o#ule 1. %ie& his personal pro#ile.
16
2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. Applicant .o#ule 1. %ie& his personal pro#ile. 2. Eie& the minorities #inancial corporation o##ices details. 3. Eie& the aim and ob=ecti%es o# this system. !. Eie& the a%ailable scheme details. ,. Eie& the channeli>ing agencies details. /. Eie& %arious loans o# this system. 0. Eie& success stories pro%ided in this system. 1. Eie& executi%es 9monitors9 and board directors pro#iles. 3. +e can interact &ith system users though emails. 14. Apply #or the loans and %ie& the status o# loans details.
17
Security an# Authentication 1. .ser Registration. 2. )ogin as board director or monitor or executi%e9 Administrator 3. *hange pass&ord !. Forgot (ass&ord Reports In this 'odule the administrator9 board director9 monitor9 executi%e can generate di##erent types o# reports.
18
Process Flo+
19
The 'odel 2 architecture #or designing FS( pages is in reality9 'odel Eie& *ontroller 7'E*8 applied to &eb applications. +ence the t&o terms can be used interchangeably in the &eb &orld. 'E* originated in SmallTal6 and has since made its &ay into Fa%a community. 'odel 2 architecure and its deri%ati%es are the cornerstones #or all serious and industrial strength &eb applications designed in the real &orld. +ence it is essential #or you understand this paradigm thoroughly. The main di##erence bet&een 'odel 1 and 'odel 2 is that in 'odel 29 a controller handles the user re"uest instead o# another FS(. The controller is implemented as a Ser%let. The #ollo&ing steps are executed &hen the user submits the re"uest. 1. The *ontroller Ser%let handles the user;s re"uest. 7This means the hyperlin6 in the FS( should point to the controller ser%let8. 2. The *ontroller Ser%let then instantiates appropriate Fa%a5eans based on the re"uest parameters 7and optionally also based on session attributes8. 3. The *ontroller Ser%let then by itsel# or through a controller helper communicates &ith the middle tier or directly to the database to #etch the re"uired data. The *ontroller sets the resultant Fa%a5eans 7either same or a ne& one8 in one o# the #ollo&ing contexts @ re"uest9 session or application. The controller then dispatches the re"uest to the next %ie& based on the re"uest .R). The Eie& uses the resultant Fa%a5eans #rom Step ! to display data. Gote that there is no presentation logic in the FS(. The sole #unction o# the FS( in 'odel 2 architecture is to display the data #rom the
20
!.
,.
/.
Fa%a5eans set in the re"uest9 session or application scopes.
'odel-2 Architecture.
21
SD&C .ET%ODO&O/IES
22
This document play a %ital role in the de%elopment o# li#e cycle 7S$)*8 as it describes the complete re"uirement o# the system. It means #or use by de%elopers and &ill be the basic during testing phase. Any changes made to the re"uirements in the #uture &ill ha%e to go through #ormal change appro%al process. S(IRA) ' $E) &as de#ined by 5arry 5oehm in his 1311 article9 AA spiral 'odel o# So#t&are $e%elopment and Enhancement. This model &as not the #irst model to discuss iterati%e de%elopment9 but it &as the #irst model to explain &hy the iteration models. As originally en%isioned9 the iterations &ere typically / months to 2 years long. Each phase starts &ith a design goal and ends &ith a client re%ie&ing the progress thus #ar. Analysis and engineering e##orts are applied at each phase o# the pro=ect9 &ith an eye to&ard the end goal o# the pro=ect. The steps #or Spiral 'odel can be generali>ed as #ollo&s: • The ne& system re"uirements are de#ined in as much details as possible. This usually in%ol%es inter%ie&ing a number o# users representing all the external or internal users and other aspects o# the existing system. A preliminary design is created #or the ne& system. A #irst prototype o# the ne& system is constructed #rom the preliminary design. This is usually a scaled-do&n system9 and represents an approximation o# the characteristics o# the #inal product. A second prototype is e%ol%ed by a #our#old procedure: 1. E%aluating the #irst prototype in terms o# its strengths9 &ea6ness9 and ris6s. 2. $e#ining the re"uirements o# the second prototype. 3. (lanning an designing the second prototype. !. *onstructing and testing the second prototype.
23
• •
•
•
At the customer option9 the entire pro=ect can be aborted i# the ris6 is deemed too great. Ris6 #actors might in%ol%ed de%elopment cost o%erruns9 operating-cost miscalculation9 or any other #actor that could9 in the customer;s =udgment9 result in a less-than-satis#actory #inal product. The existing prototype is e%aluated in the same manner as &as the pre%ious prototype9 and i# necessary9 another prototype is de%eloped #rom it according to the #our#old procedure outlined abo%e. The preceding steps are iterated until the customer is satis#ied that the re#ined prototype represents the #inal product desired. The #inal system is constructed9 based on the re#ined prototype. The #inal system is thoroughly e%aluated and tested. Routine maintenance is carried on a continuing basis to pre%ent large scale #ailures and to minimi>e do&n time.
•
• • •
The follo+in" #ia"ram sho+s ho+ a spiral mo#el acts li0e
24
Fi" 1234Spiral .o#el
AD5ANTA/ES • Estimates7i.e. schemes schedule etc .8 become more relistic as &or6 progresses9 because important issues disco%ed earlier.
25
• •
It is more able to cope &ith the changes that are so#t&are de%elopment generally entails. So#t&are engineers can get their hands in and start &oring on the core o# a pro=ect earlier.
26
SOFT6ARE RE7UIRE.ENT AND %ARD6ARE RE7UIRE.ENT
27
Soft+are Re-uirements
perating System .ser Inter#ace *lient-side Scripting (rogramming )anguage Beb Applications I$Eing agencies78 1! : %ie& *hannli>ing agencies78 , : post scheme details78 ! : %ie& aims ob=ecti%es78 Aims b=ecti%es 3 : post aims ob=ecti%es78 1 : Register minorities #inancial c orporation o##ices78 Admin 'inorities Financial *orporation o##ice 2 : %ie& minorities #inancial c orporation o##ic es78
*hannli>ing agencies
0 : post loan details78 / : %ie& scheme details78
11 : %ie& applican loan re"uests and assign to executi%es78 12 : %ie& Success Stories78 Success Stories
)oan Re"uests
62
'oar# Director
Register Channlizing agencies
Loans Schemes
* ! vie% Channlizing agencies"# ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details"# & ! vie% scheme details"# Minorities Financial Corporation office ! vie% minorities financial corporation offices"# 0oard 1irector $ ! vie% aims objectives"# ) ! vie% Success St ories"# Aims Objectives Success Stories
.onitor
Register Channlizing agencies
Loans Schemes
* ! vie% Channlizing agencies"# ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details"# & ! vie% scheme details"# Minorities Financial Corporation office ! vie% minorities financial corporation offices"# Monitor $ ! vie% aims objectives"# ) ! vie% Success St ories"# Aims Objectives Success Stories
E!ecuti*e
63
Schemes
Loans
Register Channlizing agencies
Aims Objectives
( ! vie% board directors- e.ecutives- monitor details"# Minorities Financial Corporation office
' ! vie% loan details"# & ! vie% scheme details"#
* ! vie% Channlizing agencies"#
$ ! vie% aims objectives"# Loan Requests + ! vie% assign loan requests and give status of requests"#
! vie% minorities financial corporation offices"# Success Stories ) ! vie% Success St ories"# 2.ecutive
Applicant
Loans Schemes Register
Channlizing agencies ( ! vie% board directors- e.ecutives- monitor details"# ' ! vie% loan details and appl3 for loan"# * ! vie% Channlizing agencies"# Minorities Financial Corporation office
Aims Objectives & ! vie% scheme details"# ! vie% minorities financial corporation offices"# $ ! vie% aims objectives"# Success Stories + ! vie% status of loan requests"# Loan Requests Applicant ) ! vie% Success Stories"#
64
Acti*ity Dia"rams
65
66
67
A#min Acti*ity Dia"ram
Admin
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
Register Aims Objectives Register MFC Officess post scheme 43pes
post loans Send 2mails vie% Success stories
5ie% MFC Offices vie% Scheme 43pes vie% Loans
vie% Aims Objectives
Register board directors- e.ecutives- monitors
68
'oar# Director Acti*ity Dia"ram
0oard 1irector
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices vie% Scheme 43pes
vie% Success stories Send 2mails vie% Loans vie% board directors- e.ecutives- monitors 5ie% 2mails
69
.onitor Acti*ity Dia"ram
Monitor
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices vie% Scheme 43pes
vie% Success stories Send 2mails vie% Loans vie% board directors- e.ecutives- monitors 5ie% 2mails
70
E!ecuti*e Acti*ity Dia"ram
2.ecutive
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices
vie% Loans
vie% Success stories Send 2mails 6ost Succes Stories 5ie% 2mails
vie% Scheme 43pes
vie% board directors- e.ecutives- monitors
71
Applicant Acti*ity Dia"ram
Applicant
Login
2nter username and pass%ord
failure
Success
MFC Offices
Aims Objectives
Scheme43pes
Loans
SuccessStories
Register
2mails
vie% Aims Objectives 5ie% MFC Offices
vie% Loans and appl3 5ie% Loan status
vie% Success stories Send 2mails 5ie% 2mails
vie% Scheme 43pes
6ost Succes Stories
vie% board directors- e.ecutives- monitors
72
Architecture Dia"ram
73
Component Dia"ram
74
75
Deployment Dia"ram
76
77
Data Dictionary
78
User.aster
Column Name .serid .sername (ass&ord )ogintype &ocation city State country ,ip contactno Email Photo S-uestion Sans+er
Data type Gumber 5archar8 Earchar2 Earchar2 *archar8 5archar8 5archar8 5archar8 5archar8 5archar8 5archar8 'lo$ 5archar8 5archar8
Si,e
Constratints (rimary 6ey
83 24 1, 83 1< 1< 1< 13 13 93
ed 'ar6up )anguage89 but speciali>ed to hypertext and adapted to the Beb. The idea behind +ypertext is that instead o# reading text in rigid linear structure9 &e can easily =ump #rom one point to another point. Be can na%igate through the in#ormation based on our interest and pre#erence. A mar6up language is simply a series o# elements9 each delimited &ith special characters that de#ine ho& text or other items enclosed &ithin the elements should be displayed. +yperlin6s are underlined
85
or emphasi>ed &or6s that load to other documents or some portions o# the same document. +T') can be used to display any type o# document on the host computer9 &hich can be geographically at a di##erent location. It is a %ersatile language and can be used on any plat#orm or des6top. +T') pro%ides tags 7special codes8 to ma6e the document loo6 attracti%e. +T') tags are not case-sensiti%e. .sing graphics9 #onts9 di##erent si>es9 color9 etc.9 can enhance the presentation o# the document. Anything that is not a tag is part o# the document itsel#. 5asic +T') Tags: LM ---N speci#ies comments *reates hypertext lin6s Formats text as bold Formats text in large #ont. *ontains document L*EGTERN...L5.) 5eyond the language9 there is the Fa%a %irtual machine. The Fa%a %irtual machine is an important element o# the Fa%a technology. The %irtual machine can be embedded &ithin a &eb bro&ser or an operating system. nce a piece o# Fa%a code is loaded onto a machine9 it is %eri#ied. As part o# the loading process9 a class loader is in%o6ed and does byte code %eri#ication ma6es sure that the code that;s has been generated by the compiler &ill not corrupt the machine that it;s loaded on. 5yte code %eri#ication ta6es place at the end o# the compilation process to ma6e sure that is all accurate and correct. So byte code %eri#ication is integral to the compiling and executing o# Fa%a code. %erall $escription
93
Java Source
Java byte code
JavaVM
(icture sho&ing the de%elopment process o# FAEA (rogram Fa%a programming uses to produce byte codes and executes them. The #irst box indicates that the Fa%a source code is located in a. Fa%a #ile that is processed &ith a Fa%a compiler called =a%ac. The Fa%a compiler produces a #ile called a. class #ile9 &hich contains the byte code. The .*lass #ile is then loaded across the net&or6 or loaded locally on your machine into the execution en%ironment is the Fa%a %irtual machine9 &hich interprets and executes the byte code. >a*a Architecture Fa%a architecture pro%ides a portable9 robust9 high per#orming en%ironment #or de%elopment. Fa%a pro%ides portability by compiling the byte codes #or the Fa%a Eirtual 'achine9 &hich is then interpreted on each plat#orm by the run-time en%ironment. Fa%a is a dynamic system9 able to load code &hen needed #rom a machine in the same room or across the planet. Compilation of co#e Bhen you compile the code9 the Fa%a compiler creates machine code 7called byte code8 #or a hypothetical machine called Fa%a Eirtual 'achine 7FE'8. The FE' is supposed to execute the byte code. The FE' is created #or o%ercoming the issue o# portability. The code is &ritten and compiled #or one machine and interpreted on all machines. This machine is called Fa%a Eirtual 'achine.
Java
.Class
94
*ompiling and interpreting Fa%a Source *ode
Java PC Compiler Java
Source Code ……….. ………..
SPARC (Platform ndependent! Macintosh Compiler Byte code
nterpreter (PC! Java nterpreter (Macintosh! Java nterpreter (Spare!
………..
Compiler
…………
$uring run-time the Fa%a interpreter tric6s the byte code #ile into thin6ing that it is running on a Fa%a Eirtual 'achine. In reality this could be a Intel (entium Bindo&s 3, or SunSAR* station running Solaris or Apple 'acintosh running system and all could recei%e code #rom any computer through Internet and run the Applets. Simple Fa%a &as designed to be easy #or the (ro#essional programmer to learn and to use e##ecti%ely. I# you are an experienced *TT programmer9 learning Fa%a &ill be e%en easier. 5ecause Fa%a inherits the *D'C4OD'C 'ri#"e I# possible9 use a (ure Fa%a F$5* dri%er instead o# the 5ridge and an dri%er. This completely eliminates the client con#iguration re"uired by $5* $5*.
It also eliminates the potential that the Fa%a E' could be corrupted by an error in the nati%e code brought in by the 5ridge 7that is9 the 5ridge nati%e library9 the $5* dri%er manager library9 the $5* dri%er library9 and the database client library8. 6hat Is the >D'C4 OD'C 'ri#"e? The F$5*- $5* 5ridge is a F$5* dri%er9 &hich implements F$5* operations by translating them into database #or &hich an $5* $5* operations. To dri%er is a%ailable. $5* it appears The 5ridge is as a normal application program. The 5ridge implements F$5* #or any implemented as the Sun.=dbc.odbc Fa%a pac6age and contains a nati%e library used to access $5*. The 5ridge is a =oint de%elopment o# Innersole and Fa%a So#t.
102
>D'C connecti*ity The F$5* pro%ides database-independent connecti%ity bet&een the F2EE plat#orm and a &ide range o# tabular data sources. F$5* technology allo&s an Application *omponent (ro%ider to: ? (er#orm connection and authentication to a database ser%er ? 'anager transactions ? 'o%e SU) statements to a database engine #or preprocessing and execution ? Execute stored procedures ? Inspect and modi#y the results #rom Select statements
103
Data$ase A database management system 7$5'S8 is computer so#t&are designed #or the purpose o# managing databases9 a large set o# structured data9 and run operations on the data re"uested by numerous users. Typical examples o# $5'Ss include (ostgreSU)9 racle9 $529 'icroso#t Access9 'icroso#t SU) Ser%er9 Firebird9 SU)ite9 File'a6er and Sybase Adapti%e Ser%er 'ySU)9
Enterprise. $5'Ss are typically used by $atabase administrators in the creation o# $atabase systems. Typical examples o# $5'S use include accounting9 human resources and customer support systems.
riginally #ound only in large companies &ith the computer hard&are needed to support large data sets9 $5'Ss ha%e more recently emerged as a #airly standard part o# any company bac6 o##ice.
Description A $5'S is a complex set o# so#t&are programs that controls the organi>ation9 storage9 management9 and retrie%al o# data in a database. A $5'S includes: ? A modeling language to de#ine the schema o# each database hosted in the $5'S9 according to the $5'S data model. • The #our most common types o# organi>ations are the hierarchical9 net&or69 relational and ob=ect models. In%erted lists and other methods are also used. A gi%en database management system may pro%ide one or more o# the #our models. The optimal structure depends on the natural organi>ation o# the applicationRs data9 and
104
on the applicationRs re"uirements 7&hich include transaction rate 7speed89 reliability9 maintainability9 scalability9 and cost8. • The dominant model in use today is the ad hoc one embedded in SU)9 despite the ob=ections o# purists &ho belie%e this model is a corruption o# the relational model9 since it %iolates se%eral o# its #undamental principles #or the sa6e o# practicality and per#ormance. 'any $5'Ss also support the pen $atabase *onnecti%ity A(I that supports a standard &ay #or programmers to access the $5'S. ? $ata structures 7#ields9 records9 #iles and ob=ects8 optimi>ed to deal &ith %ery large amounts o# data stored on a permanent data storage de%ice 7&hich implies relati%ely slo& access compared to %olatile main memory8.
? A database "uery language and report &riter to allo& users to interacti%ely interrogate the database9 analy>e its data and update it according to the users pri%ileges on data. • • It also controls the security o# the database. $ata security pre%ents unauthori>ed users #rom %ie&ing or updating the database. .sing pass&ords9 users are allo&ed access to the entire database or subsets o# it called sub schemas. For example9 an employee database can contain all the data about an indi%idual employee9 but one group o# users may be authori>ed to %ie& only payroll data9 &hile others are allo&ed access to only &or6 history and medical data. • I# the $5'S pro%ides a &ay to interacti%ely enter and update the database9 as &ell as interrogate it9 this capability allo&s #or
105
managing personal databases. +o&e%er9 it may not lea%e an audit trail o# actions or pro%ide the 6inds o# controls necessary in a multiuser organi>ation. These controls are only a%ailable &hen a set o# application programs are customi>ed #or each data entry and updating #unction.
? A transaction mechanism9 that ideally &ould guarantee the A*I$ properties9 in order to ensure data integrity9 despite concurrent user accesses 7concurrency control89 and #aults 7#ault tolerance8. • • It also maintains the integrity o# the data in the database. The $5'S can maintain the integrity o# the database by not allo&ing more than one user to update the same record at the same time. The $5'S can help pre%ent duplicate records %ia uni"ue index constraintsS #or example9 no t&o customers &ith the same customer numbers 76ey #ields8 can be entered into the database. See A*I$ properties #or more in#ormation 7Redundancy a%oidance8.
The $5'S accepts re"uests #or data #rom the application program and instructs the operating system to trans#er the appropriate data. Bhen a $5'S is used9 in#ormation systems can be changed much more easily as the organi>ationRs in#ormation re"uirements change. Ge& categories o# data can be added to the database &ithout disruption to the existing system. rgani>ations may use one 6ind o# $5'S #or daily transaction processing and then mo%e the detail onto another computer that uses another $5'S better suited #or random in"uiries and analysis. %erall systems design
106
decisions are per#ormed by data administrators and systems analysts. $etailed database design is per#ormed by database administrators. $atabase ser%ers are specially designed computers that hold the actual databases and run only the $5'S and related so#t&are. $atabase ser%ers are usually multiprocessor computers9 &ith RAI$ dis6 arrays used #or stable storage. *onnected to one or more ser%ers %ia a high-speed channel9 hard&are database accelerators are also used in large %olume transaction processing en%ironments. $5'Ss are #ound at the heart o# most database applications. Sometimes $5'Ss are built around a pri%ate multitas6ing 6ernel &ith built-in net&or6ing support although no&adays these #unctions are le#t to the operating system.
107
S7& Structured Uuery )anguage 7SU)8 is the language used to manipulate relational databases. SU) is tied %ery closely &ith the relational model.
In the relational model9 data is stored in structures called relations or tables . SU) statements are issued #or the purpose o#:
Data #efinition $e#ining tables and structures in the database 7$$) used to create9 alter and drop schema ob=ects such as tables and indexes8.
Data manipulation $atabase8.
.sed to manipulate the data &ithin those schema
ob=ects 7$') Inserting9 .pdating9 $eleting the data9 and Uuerying the
A schema is a collection o# database ob=ects that can include: tables9 %ie&s9 indexes and se"uences
)ist o# SU) statements that can be issued against an schema are:
racle database
• • •
A&TER - *hange an existing table9 %ie& or index de#inition 7$$)8 AUDIT - Trac6 the changes made to a table 7$$)8 CO..ENT - Add a comment to a table or column in a table 7$$)8
108
• • • • • • • • • • • •
CO..IT - 'a6e all recent changes permanent 7$') - transactional8 CREATE - *reate ne& database ob=ects such as tables or %ie&s 7$$)8 DE&ETE - $elete ro&s #rom a database table 7$')8 DROP - $rop a database ob=ect such as a table9 %ie& or index 7$$)8 /RANT - Allo& another user to access database ob=ects such as tables or %ie&s 7$$)8 INSERT - Insert ne& data into a database table 7$')8 No AUDIT - Turn o## the auditing #unction 7$$)8 RE5O@E - $isallo& a user access to database ob=ects such as tables and %ie&s 7$$)8 RO&&'AC@ - .ndo any recent changes to the database 7$') Transactional8 SE&ECT - Retrie%e data #rom a database table 7$')8 TRUNCATE - $elete all ro&s #rom a database table 7can not be rolled bac68 7$')8 UPDATE - *hange the %alues o# some data items in a database table 7$')8
109
SER5&ETS Introduction The Fa%a &eb ser%er is Fa%aSo#tRs o&n &eb Ser%er. The Fa%a &eb ser%er is =ust a part o# a larger #rame&or69 intended to pro%ide you not =ust &ith a &eb ser%er9 but also &ith tools. To build customi>ed net&or6 ser%ers #or any Internet or Intranet clientards
EclipseRs &idgets are implemented by a &idget tool6it #or Fa%a called SBT9 unli6e most Fa%a applications9 &hich use the Fa%a standard Abstract Bindo& Tool6it 7ABT8 or S&ing. EclipseRs user inter#ace also le%erages an intermediate D.I layer called FFace9 &hich simpli#ies the construction o# applications based on SBT. Eclipse employs plug-ins in order to pro%ide all o# its #unctionality on top o# 7and including8 the rich client plat#orm9 in contrast to some other applications &here #unctionality is typically hard coded. This plug-in
117
mechanism is a light&eight so#t&are componentry #rame&or6. In addition to allo&ing Eclipse to be extended using other programming languages such as * and (ython9 the plug-in #rame&or6 allo&s Eclipse to &or6 &ith typesetting languages li6e )aTeH9 net&or6ing applications such as telnet9 and database management systems. The plug-in architecture supports &riting any desired extension to the en%ironment9 such as #or con#iguration management. Fa%a and *ES support is pro%ided in the Eclipse S$X. The 6ey to the seamless integration o# tools &ith Eclipse is the plug-in. Bith the exception o# a small run-time 6ernel9 e%erything in Eclipse is a plug-in. This means that a plug-in you de%elop integrates &ith Eclipse in exactly the same &ay as other plug-insS in this respect9 all #eatures are created e"ual. The Eclipse S$X includes the Eclipse Fa%a $e%elopment Tools9 o##ering an I$E &ith a built-in incremental Fa%a compiler and a #ull model o# the Fa%a source #iles. This allo&s #or ad%anced re#actoring techni"ues and code analysis. The I$E also ma6es use o# a &or6space9 in this case a set o# metadata o%er a #lat #ile space allo&ing external #ile modi#ications as long as the corresponding &or6space PresourceP is re#reshed a#ter&ards. The Eisual Editor pro=ect allo&s inter#aces to be created interacti%ely9 hence allo&ing Eclipse to be used as a RA$ tool. The follo+in" is a list of nota$le pro=ects an# plu"4in for the Eclipse IDE2 These pro=ects are maintained by the Eclipse community and hosted by the Eclipse Foundation. 12 Core pro=ects Rich *lient (lat#orm 7(lat#orm8 is the core #rame&or6 that all other Eclipse pro=ects are built on.
118
Fa%a $e%elopment Tools 7F$T8 pro%ides support #or core Fa%a SE. This includes a standalone #ast incremental compiler. 82 Tools pro=ects *a*a EE Ser*ers Follo&ing the success o# the Fa%a plat#orm9 the term application ser%er sometimes re#ers to a Fa%a (lat#orm--Enterprise Edition 7F2EE8 or Fa%a EE , application ser%er. Among the better 6no&n Fa%a Enterprise Edition application ser%ers are Beb)ogic Ser%er 75EA89 F5oss 7Red +at89 BebSphere 7I5'89 FRun 7Adobe89 Apache Deronimo 7Apache Foundation9 based on I5' BebSphere89 racle *!F 7 racle *orporation89 Sun Fa%a System Application Ser%er 7Sun 'icrosystems8 and Dlass#ish Application Ser%er 7based on Sun Fa%a System Application Ser%er8. Fa%a application ser%er &as the #irst open source application ser%er to ha%e achie%ed o##icial compliance &ith the Fa%a Enterprise Speci#ication. 5EA deli%ered the #irst Fa%a EE , certi#ied application ser%er #ollo&ed by Sun 'icrosystemsR re#erence implementation Dlass#ish.
122
The Beb modules are ser%lets and Fa%a Ser%er (ages9 and business logic is built into Enterprise Fa%a5eans 7EF5-3 and later8. The +ibernate pro=ect o##ers an EF5-3 container implementation #or the F5oss Application ser%er. Tomcat #rom Apache and F nAS #rom into &hich these modules can be put. A Fa%a Ser%er (age 7FS(8 is a ser%let #rom Fa%a that executes in a Beb containerKthe Fa%a e"ui%alent o# *DI scripts. FS(s are a &ay to create +T') pages by embedding re#erences to the ser%er logic &ithin the page. +T') coders and Fa%a programmers can &or6 side by side by re#erencing each otherRs code #rom &ithin their o&n. Fa%a5eans are the independent class components o# the Fa%a architecture #rom Sun 'icrosystems. The application ser%ers mentioned abo%e mainly ser%e Beb applications. Some application ser%ers target net&or6s other than the Beb: Session Initiation (rotocol ser%ers9 #or instance9 target telephony net&or6s. b=ectBeb are typical o# containers
Scope of The De*elopment Pro=ect Data$ase Tier The concentration is applied by adopting the racle 1.1
Enterprise %ersions. SU) is ta6en as the standard "uery language. The o%erall business rules are designed by using the po&er o# ()ed architecture. The components are designed using $ream&ea%er and Fa%a ser%er pages po&er the dynamic o# the page design. Data 'ase Connecti*ity Tier
123
The communication architecture is designed by concentrated on the standards o# struts and Fa%a 5eans. The database connecti%ity is established using the Fa%a $atabase connecti%ity. >'OSS F5oss Application Ser%er 7or F5oss AS8 is a #ree so#t&are < open source Fa%a EE-based application ser%er. 5ecause it is Fa%a-based9 F5oss AS is crossplat#orm9 usable on any operating system that Fa%a supports. En*ironment F5oss AS !.4 is a F2EE 1.! application ser%er9 &ith embedded Tomcat ,.,. Any FE' bet&een 1.! and 1., is supported. F5oss can run on numerous operating systems including Bindo&s9 'ac S H9 many ( SIH plat#orms9 and others9 as long as a suitable FE' is present. F5oss AS !.2 is also a F2EE 1.! application ser%er9 but EF5 3 is deployed by de#ault. It re"uires F$X ,. Tomcat / is bundled &ith it. Gext F5oss AS , &ill be Fa%a EE , application ser%er. Pro#uct features ? Failo%er 7including sessions8 ? )oad balancing ? $istributed caching 7using F5oss *ache9 a standalone product8 ? $istributed deployment 7#arming8 ? Enterprise Fa%a5eans %ersion 3
124
125
Co#in"
.FCOffice2=sp LYZ page languageQP=a%aP importQP=a%a.util.VP pageEncodingQPIS 11,3-1PYN LYZpage importQPcom.6&s.m#c.dao..ser'aster$A PYN LYZpage importQPcom.6&s.m#c.bean..ser'aster5eanPYN LY String path Q re"uest.get*ontext(ath78S
126
String
base(ath
Q
re"uest.getScheme78TP: