1
TABLE OF CONTENTS Acknowledgement……………………………………………………………… … Preface of project………………………………………………………………….. Certicate………………………………………………………………………… ……. Introduction to project…………………………………………………………… Project objectives…………………………………………………………………… Advantages …………………………………………………………………………… Sstem development lifeccle…………………………………………………. !easibilit stud……………………………………………………………………… "rawback of t#e e$isting sstem……………………………………………. Project plan…………………………………………………………………………… "evelopment tools……………………………………………………………….. %ables %ables used…………………………………………………………………………..
&
'odules used………………………………………………………………………. ()* diagram…………………………………………………………………………. !ront end used……………………………………………………………………. Coding…………………………………………………………………………… …… reference of t#e project………………………………………………………
ACKNOWLEDGEMENT !or most of all we e$press our indebt to t#e Almig#t for bestowing us wit# t#e favorable circumstances and keeping us in #ig# spirits. +o #uman endeavor can be accomplis#ed wit#out constant guidance and support .I am ver muc# pleased to bring out t#is report in sc#edules time, for t#is credit a feeling of elevation insists us on e$pressing our #eartiest t#anks and gratitude to our coordinators and project guide Ms. Heena Karla of #is valuable guidance and constant encouragement during t#e course of project of librar management sstem and enabled us to reac# t#is stage. -it#out w#ose uniue guidance and supervision along wit# constructive critics and immense #elp, t#is project would never #ave. I would like to e$press m gratitude and o/er sincere t#anks to m friends.
0
ast but not list I would like to t#ank t#e parents wit#out t#eir #earted support t#is project would #ave not been completed.
PREFACE OF THE PROJECT ibrar management sstem as per now is a website t#at s going to be used to t o manage t#e 2ow of books in a librar. librar. -it# t#e intentions of #aving it as our software . It3s a ver tedious, time consuming as well as error error prone prone job dealing wit# manual database will depend more on t#e administrator. administrator. It3s developed generall genera ll to #elp on t#e management of books in a single librar. librar. A user can be able to access books online. And can order t#em online and t#e deliver can be done to t#eir door steps.
4
CERTIFICATE %#is is to certif management sstem embodies t#e original work t#at is done b NICHOLAS NICH OLAS SSELY SSELYAZI ,NANZIRI CLARE and BERNICE MUSANINKA during project submission as fulllment of t#e reuirement for t#e sstem design project of Ba!el"rs "# C"$%&'er A%%l(a'("n56t# semester7 of PUNJAB COLLEGE OF TECHNICAL EDUCATION.
8
INTRODUCTION OF THE PROJECT ibrar management sstem ensures t#e e/ective use of t#e te$ts books t#at will be available in t#e book store. %#is management can be able to record a number of te$ts books in t#e data base. 9nlike t#e le sstem. -#ere b t#e details were used to be stored in les. And t#e could succumb to some problems give like t#e termite, re #a:ards, and rats, among ot#ers. %#is can store an number of data because its storage is unlimited.
6
PROJECT OBJECTI)ES As all ot#er projects, t#is project #as its objectives t#at are being followed as it is being developed. •
•
•
•
•
%o #andle all primar information reuired to calculate mont#l statements. Separate database is maintained to #andle all t#e details reuired for correct statement calculation and generation. %o introduce more user friendliness in t#e various activities suc# as record updating and maintenance . Similarl, record maintenance and updating can also be accomplis#ed b using t#e identication of t#e customer wit# all details being automaticall generated. %#ese details are also being promptl automaticall updated in t#e master le t#us keeping t#e record absolutel up to date. %#e sstem #as maintained in t#e database or les and #owever wants to retrieve can3t retrieve unless aut#ori:ed.
'ore securit
;
•
!or publicit purposes
•
ess time consuming
•
Proper database (as to use5user interface7
•
-ork transforms from manual to automatic
•
!eedback
•
AD)ANTAGES I #ave designed t#e given proposed sstem in t#e Asp.+et to automate t#e process of t#e book store<ibrar. %#is project is useful for t#e aut#orities w#ic# keep track of all t#e users registered. %#e following steps t#at give t#e detailed information of t#e need of proposed sstem are=
Per#"r$ane* "uring past several decades, t#e records are supposed to be manuall #andled for all activities. %#e manual #andling of t#e record is time consuming and #ig#l prone to error.
%o improve t#e performance of t#e ibrar 'anagement Sstem, t#e computeri:ed sstem is to be undertaken. %#is project is full computeri:ed and user friendl even t#at an of t#e members can see t#e report and status of t#e compan.
>
E+(en,* %#e basic need of t#is website is e?cienc. %#e website s#ould be e?cient so t#at w#enever a new user submits #is<#er details t#e website is updated automaticall. %#is record will be useful for ot#er users instantl.
C"n'r"l* %#e complete control of t#e project is under t#e #ands of aut#ori:ed person w#o #as t#e password to access t#is project and illegal access is not supposed to deal wit#. All t#e control is under t#e administrator and t#e ot#er members #ave t#e rig#ts to just see t#e records not to c#ange an transaction or entr.
Se&r(',* Securit is t#e main criteria for t#e proposed sstem. Since illegal access ma corrupt t#e database. So securit #as to be given in t#is project.
TOOLS-PLATFORM %#is project is developed using t#e tools, w#ic# are most suited for development of t#e application package. %#ese tools are as follows= 1. Asp.+et 5for font end7 Advantages It #as a ver good grap#ical user interface It #as online coding It3s compatible to sl database ver well It is user friendl &. S@ S(*(* 5for database storage as back end7
B
HARDWARE AND SOFTWARE REUIREMENTS 'inimum ardware *euirements= Processor= 'emor=
Intel Pentium I 1DE
ard disk= 'onitor=
4DE DA Color 'onitor
'inimum Software *euirements=
Fperating sstem= -indows GP onwards Application software= Asp.+et 5front end7 S@ S(*(* 5for database as back end7
S,s'e$ S'&/, 0 Anal,s(s PRINCIPLES OF SYSTEM ANALYSIS 1. 9nderstand t#e problem before ou begin to create t#e analsis model. &. "evelop prototpes t#at enable a user to understand #ow #uman mac#ine interaction will occur. 0. *ecord t#e origin of and t#e reason for ever reuirement. 4. 9se multiple views of reuirements like building data, function and be#avioral models. 8. -ork to eliminate ambiguit.
SYSTEM DE)ELOPMENT LIFECYCLE %#is concept #as ; stages=
1H
1. &. 0. 4. 8. 6. ;.
*ecognition of need sstem analsis sstem feasibilit stud sstem design code generation implementation post implementation
re"1n('("n "# nee/ In recognition of need wit#out a clear understanding in t#e sstem, an furt#er work done will lead to wastage of time and e/ort at later stages. ence various uestions must be posed identifing correct problem like. w#at is t#e actual problem cause of t#e problem if it is important to solve problems or not. %pes of benets e$pected after t#e problem is solved. %#e advantage of recognition of need in S"C 5Sstem "evelopment ife Ccle7 i.e. t#at it #elps in pinpointing t#e problem, setting proper sstem goals, determining t#e boundaries of project b taking into consideration t#e limitation of e$isting sstems. All t#e information of ab inventor is recorded manuall.
S,s'e$ #eas(2(l(', s'&/, %#e feasibilit stud proposes one or more conceptual solutions to t#e problem set for project. %#e conceptual solution gives an idea of w#at t#e new sstem will look like. !easibilit stud denes w#at will be done on computer.it is important to consult t#e users to see if t#e computeri:ed data recording function satises users objectives and can be tted into current sstem operation. %#e major
11
outputs of t#is p#ase are tec#nical feasibilit report, cost benet analsis report, operational feasibilit. It consists of t#e following= 1. statement of t#e problem &. Summar of t#e ndings and recommendations 0. "etails of ndings 4. *ecommendations and conclusions 8. %#ere are basicall t#ree tpes of feasibilit are addressed in t#e stud=) 1. %ec#nical feasibilit &. (conomic feasibilit 0. Ee#avioral feasibilit
Te!n(al #eas(2(l(', %ec#nical feasibilit ensures t#at t#e considered engineering concept does not violate t#e laws of p#sics. !or e$ample, a feasible device cannot deliver more energ or material t#an is put into t#e device.
Be!a3("ral #eas(2(l(', An estimate s#ould be made of #ow strong a reaction t#e user sta/ is likel to #ave towards t#e development of a computeri:ed sstem. It is common knowledge t#at t#e computer installations #ave somet#ing to do wit# turnover, transfers and c#anges in emploee job status.
E"n"$( #eas(2(l(', Analsis of a project3s costs and revenues in an e/ort to determine w#et#er or not it is logical and possible to complete.
S,s'e$ anal,s(s %#e proposed librar management sstem will enable faster information processing regarding various business processes #elping t#e sta/ to better serve t#eir customer needs in
1&
lesser time aimed at enric#ing t#e overall customer e$perience. Introduction t#is project is aimed at building a management information sstem using computer. It is not preliminar stud. It is a dept# stud of t#e end user information needs t#at produces functional reuirements t#at are used as t#e basis for t#e design of a new information sstem. It e$tracting t#e reuirements of t#e desired software product is t#e rst task in creating it. -#ile customers probabl believe, t#e know w#at t#e software is to do. It ma reuire skill and e$perience in software engineering to recogni:e incomplete, ambiguous or contradictor reuirements. Sstem involves detailed stud of=
a.
%#e information needs of t#e organi:ation and end user.
b.
%#e activities, resources and products of an present information sstem.
c. %#e information sstem capabilities reuired to meet our information needs.
S,s'e$ /es(1n "uring t#e design p#ase, we focus on t#e operation of t#e sstem. As in t#is p#ase we designed t#e arc#itecture and interface of website and decided and w#ere to store data and #ow I s#ould 2ow. -e decided to use ASP.+et based platform t#at provides users 2e$ible and e$tendable modules templates to support integration of web pages.
1. ogical design p#ase &. P#sical design p#ase
10
LOGICAL DESIGN PHASE* A data 2ow diagram s#ows t#e logical 2ow of t#e sstem and denes t#e boundaries of t#e sstem. !or a candidate stem it describes t#e input 5source7, out bases and procedure all in a format t#at meets t#e user reuirement.
PHYSICAL DESIGN* %#is produces t#e working sstem b dening t#e design specication t#at tells programmers e$actl w#at t#e candidate sstem must do. In turn t#e programmer writes t#e necessar programs or modif t#e software packages t#at access input from user, performs t#e necessar calculations, produces t#e reports on a #ard cop or displa it on t#e screen.
Fbjectives Successful completion of t#e design p#ase s#ould comprise •
%ransformation of t#e reuirements into detailed specications covering all aspects of t#e sstem.
•
Assessment and planning for securit risks.
•
Approval to progress to development p#ase.
G"als %#e purpose of t#e design p#ase is to transform t#e reuirements into complete and detailed sstem design specications. Fnce t#e design is approved, t#e development team begins t#e development p#ase. Sstem design can be viewed as t#e design of user interface data, process and sstem specication.
14
Sstem design
9ser interface design
"ata design
Sstem specification
Process design
C"/(n1 an/ Tes'(n1 -#en design is nis#ed, coding will t#en begin. %#is p#ase is t#e wa of creating new sstem, it involves coding of computer programs compilation and testing of program, link testing and integration of web pages. Dood software development organi:ations normall reuire t#eir programmers to ad#ere to some well)dened and standard stle of coding called coding standards. 'ost software development
18
organi:ations formulate t#eir own coding standards t#at suit t#em most and reuire t#eir engineers of an organi:ation to ad#ere to a standard stle of coding is t#e following. •
A coding standard gives a uniform appearance to t#e codes written di/erent engineers.
•
It en#ances code understanding.
•
It encourages goo programming practices.
Coding standards lists several rules to be followed during coding, suc# as t#e wa variables re to be named, t#e wa t#e code is to be named, t#e wa t#e code is to be laid out error return conventions, etc. Coding standards and guidelines=) Dood software development organi:ations usuall develop t#eir own coding standards and guidelines depending on w#at best suits t#eir organi:ation and t#e tpe of products t#e develop.
%#e following are t#e representative coding standards=) *ules for limiting t#e use of global= %#ese rules list w#at tpe f data can be declared global ad w#at cannot. Contents of t#e #eaders preceding codes for di/erent modules= %#e information contained in t#e #eaders of di/erent modules s#ould be standard for t#e organi:ation. %#e e$act format in w#ic# t#e #eader can be specied. %#e following are some standard #eader data= •
+ame of t#e module
•
"ate on w#ic# t#e module was created
16
•
Aut#or3s name
•
'odication #istor
•
Snopsis of t#e module
•
•
"i/erent functions supported along wit# t#eir input
Na$(n1 "n3en'("ns #"r 1l"2al 3ar(a2les4 l"al 3ar(a2les an/ "ns'an' (/en'(5ers = A possible naming convention can be t#at global variable names start wit# capital letter, local variable names are made of small letters and constant names are alwas capital letters.
Err"r re'&rn "n3en'("ns an/ e6e%'("n !an/l(n1 $e!an(s$s= %#e wa error conditions are reported b di/erent functions in a program are #andled s#ould be standard wit#in an organi:ation. !or e$ample, di/erent functions w#ile encountering an error condition s#ould eit#er return H or 1 constantl.
%#e following are some representative coding guidelines recommended b man software development organi:ations.
1;
D" n"' &se '!e "/(n1 s',le '!a' (s '"" le3er "r '"" /(+&l' '" &n/ers'an/= code s#ould be eas to understand . man ine$perienced engineers actuall take pride in writing crptic and incompre#ensible code. Clever coding can obscure meaning of t#e code and #amper understanding. It also makes maintenance di?cult.
A3"(/ "2s&re s(/e e7e's= %#e side e/ects of function call include modication of parameters passed b reference, modication of global variables and I
D" n"' &se an (/en'(5er #"r $&l'(%le %&r%"ses= Programmers often use t#e same identier to denote several temporar entities for e$ample, some programmers use a temporar loop variable for computing and storing nal result. %#e rationale t#at is usuall given b t#ese programmers for suc# multiple uses of variables is memor e?cienc, e.g. t#ree variables use up t#ree memor locations, w#ereas t#e same variable used in t#ree di/erent was uses just one memor location. owever, t#ere are several t#ings wrong wit# t#is approac# and #ence s#ould be avoided. Some of t#e problems caused b use of variables for multiple purposes as follows=
1>
•
•
(ac# variable s#ould be given a descriptive name indicating its purpose. %#is is not possible if an identier is used for multiple purposes. 9se of variable for multiple purposes can lead to confusion and make it di?cult for somebod tring to read and understand t#e code. 9se of variables for multiple purposes usuall makes future en#ancements more di?cult.
T!e "/e s!"&l/ 2e 8ell /"&$en'e/ = As rule of t#umb, t#ere must be at least one comment line on t#e average for ever t#ree source line.
T!e len1'! "# an, #&n'("n s!"&l/ n"' e6ee/ 9: s"&re l(nes= A function t#at is ver lengt# is usuall ver di?cult to understand as it probabl carries out man di/erent functions. !or t#e same reason, lengt# functions are likel to #ave disproportionatel larger number of bugs.
D" n"' &se 1" '" s'a'e$en's= 9se of go to statements makes s program unstructured and makes it ver di?cult to understand.
Tes'(n1
Similar to t#e sstem development lifeccle, testing also #as a lifeccle. As testing is a part of t#e S"C, some of t#e testing p#ases are combination of two di/erent S"C p#ases. %esting lifeccle #as t#ree di/erent p#ases3 vi:. test
1B
analsis p#ase, test planning< test designing p#ase, test e$ecution p#ase.
Tes' anal,s(s %!ase* In t#is p#ase, a tester needs get an understanding about t#e project.
Tes' Des(1n %!ase* In t#is p#ase, a tester needs to design t#e test cases based on t#e reuirements and use cases.
Tes's E6e&'("n %!ase = In t#is p#ase, a tester needs to e$ecute t#e test cease written b #im or #er or an ot#er resource and raise t#e defects, if an.
)ar("&s 'es'(n1 'e!n(;&es=)
Ae%'ane 'es'(n1 %esting t#e sstem t#e sstem wit# t#e intent of Conrming readiness3s of t#e product and customer acceptance.
A/!" 'es'(n1*< %esting wit#out a formal test plan or outside of a test plan. -it# some projects t#is tpe of testing is carried out as an adjunct to formal testing .if carried out b a skilled tester, it can often nd problems t#at are not caug#t in regular testing. Sometimes, if testing occurs ver late in t#e development ccle, t#is will be onl
&H
kind of testing t#at can be performed. Sometimes ad #oc testing is referred to as e$plorator testing.
Al%!a 'es'(n1=) %esting after code is mostl complete or contains most of t#e functionalit and prior to users being involved. Sometimes a select group of are involved. 'ore often t#is testing will be performed in #ouse or b an outside testing rm in close cooperation wit# t#e software engineering department.
A&'"$a'e/ 'es'(n1=) Software testing t#at utili:es a variet of tools to automate t#e testing process and w#en t#e importance of #aving a person manuall testing is diminis#ed. Automated testing still reuires a skilled ualit assurance professional wit# knowledge of t#e automation tool and software being tested to set up tests.
Be'a 'es'(n1=) %esting after t#e product code complete. Eetas are often widel disputed or even distributed to t#e public at large in #opes t#e will bu t#e nal product w#en it is released.
Bla= 2"6 'es'(n1 =) %esting software wit#out an knowledge of t#e inner workings, structure or language of t#e module being tested. Elack bo$ tests. As most ot#er kinds of tests, must be written from a denitive source document, suc# as specication or reuirements document.
C"n51&ra'("n 'es'(n1=)
&1
%esting of determine #ow well t#e product works wit# a broad range of #ardware
C"$%a'(2(l(', 'es'(n1=) %esting used to determine w#et#er ot#er sstem software components suc# as browsers, utilities and competing software will con2ict wit# software being tested.
F&n'("nal 'es'(n1=) %esting two or more modules toget#er wit# t#e intent of nding defects demonstrating t#at defects are not present, verifing t#at t#e module performs its intended functions as stated in specication and establis#ing condence t#at a program does w#at it is supposed to do.
In/e%en/en' 3er(5a'("n an/ 3al(/a'("n =) %#e process of e$ercising software wit# t#e intent of ensuring t#at t#e software sstem meets its reuirements and user e$pectations and doesn3t fall in an unacceptable manner.
Ins'alla'("n 'es'(n1=) %esting wit# t#e intent of determining if t#e product will install on a variet of platforms and #ow easil it installs.
In'e1ra'("n 'es'(n1=) %esting two or more modules or functions toget#er wit# t#e intent of nding interface defects between t#e modules or functions. %esting completed at as a part of unit or functional testing and sometimes becomes its own standalone test p#ase. Fn a larger level, integration testing can involve a putting toget#er of groups of modules and functions wit# t#e goal of completing and verifing t#at t#e sstem meets t#e sstem reuirements.5see sstem testing7.
L"a/ 'es'(n1=)
&&
%esting wit# t#e intent of determining #ow well t#e product #andles competition for sstem resources. %#e competition ma come in form of network tra?c, CP9 utili:ation or memor allocation.
Per#"r$ane 'es'(n1=) %esting wit# t#e intent of determining #ow uickl a product #andles a variet of events. Automated test tools geared specicall to test and ne tune performance are used oust often for t#is tpe of testing.
P(l"' 'es'(n1=) %esting t#at involves t#e users just before actual release to ensure t#at users become familiar wit# t#e release contents and ultimatel accept it.
Re1ress("n 'es'(n1=) %esting wit# t#e intent of determining if bug $es #ave been successful and #ave not created an new problems. Also, t#is tpe of testing is done to ensure t#at no degradation of baseline functionalit #as occurred.
Se&r(', 'es'(n1=) %esting of database and network software in order to keep compan data and resources secure from mistaken< accidental users, #ackers, and ot#er malevolent attackers.
S"#'8are 'es'(n1=) %#e process of e$ercising software wit# t#e intent of ensuring t#at software sstem meets its reuirements and users e$pectations and doesn3t fail in an unacceptable manner.
S'ress 'es'(n1=)
&0
%esting wit# t#e intent of determining #ow well a product performs w#en a load is placed on t#e sstem resources t#at nears t#en e$ceeds capacit.
S,s'e$ (n'e1ra'("n 'es'(n1=) %esting a specic #ardware
User ae%'ane 'es'(n1=)see acceptance testing
I$%le$en'a'("n ere, t#e project team actuall constructed and installed t#e website base on users3 feedback and reuirements. %#e ne$t step is to put all onto site nit and make t#e di/erent c#anges to meet t#e user reuirements.
It3s t#e reali:ation of an application. Fr e$ecution of a plan idea, model, design, specication, standard, algorit#m, or polic. Implementation is a stage w#ere t#eor is converted into practical. %#e implementation is vital step in ensuring t#e success of new sstems. (ven a well)designed sstem can fail if it is not properl implemented.
Post implementation and maintenance Fnce a sstem if full implemented and being operated and end users, t#e maintenance function begins. Sstems maintenance is
&4
monitoring, evaluating and modifing of operational information sstem to make desirable or necessar improvements.
THE MODEL USED IS WATERFALL MODEL Wa'er#all $"/el* is t#e simplest process modes, w#ic# states t#at t#e p#ases are organi:ed in a linear order. %#ere are various variation t#e waterfall models depending on t#e nature of activities and 2ow of control between t#em. Sometimes called t#e classic left ccle suggests a sstematic seuential approac# to software development t#at begins wit# customer specication of reuirements and progresses t#roug# planning modeling, construction and development in ongoing support of t#e completed software. *euirements
A+ASIS
"(SID+
&8
CF"I+D
testing
Acceptance
A/3an'a1es "# 8a'er#all $"/el* 1. It is simple model of software development w#ic# follow t#e seuence approac#. &. %#e large and comple$ task of building a software broken into smaller task. 0. Euggies and errors found in earl stages is c#apter in terms of mone e/orts and time to $ t#en t#e some buggies found later. 4. It also provides us wit# all t#e reuirement at an earl stage to modication in reuirement after t#e couc#ing are less. 8. -aterfall models emp#asis on making documents at ever stages of water models.
D(sa/3an'a1es "# 8a'er#all $"/el= 1. It is good for small projects. &. Clint ma not be aware of all t#e reuirements in t#e starting p#ase. (ac# p#ase must be completed before moving t#e ne$t p#ase.
&6
E
In software engineering, an entit relations#ip model 5()* model in s#ort7 is an abstract wa to describe a database. It usuall starts wit# a relational database, w#ic# stores t#e data in tables.
Some of t#e data in t#ese tables point to t#e data in ot#er tables for instance, our entr in t#e database could point to several entries for eac# of t#e p#one numbers t#at are ours.
&;
%#e (* model would sa t#at ou are an entit and eac# p#one number is an entit, and t#e relations#ip between ou and t#e p#one numbers is #as a p#one number.
"iagrams created to design t#ese entities and relations#ips are called entit relations#ip diagrams or (* diagrams. Smbols=) Attribute=)ovals are used to represent attributes.
(ntit=)bo$es are commonl used to represent entities.
*elations#ip=) diamonds are normal uses to represent relations#ip.
T!e en'(', rela'("ns!(% >ER? $"/el (* model forms t#e basis of an (* diagram.
&>
(*" represents t#e conceptual database as viewed b end user. (*"s depict t#e (* model t#ree main.
Components= • • •
(ntities Attributes *elations#ips
En'('(es • •
•
•
*efers to t#e entit set and not a single entit occurrence. Corresponds to a table and nor to row in t#e relational environment In bot# t#e C#en and Crow foot models an entit is represented b b a rectangle containing t#e entit name. (ntit name, noun, is usuall written in capital letters.
A''r(2&'es • •
• •
C#aracteristics of entities. In C#en model, attributes are represented b ovals and are connected to t#e entit rectangle wit# a line. (ac# oval contains t#e name of t#e attribute it resents. In t#e Crow !oot models, t#e attributes are simpl written in t#e attribute bo$ follow t#e entit rectangle.
&B
DRAW BACKS OF THE PRESENT SYSTEM 1. !ast report generation is not possible. &. %racing a book is di?cult. 0. Information about issue
E
TABLES USED ADMIN TABLE
0H
FEEDBACK TABLE
GENERATE FINES TABLE
01
GENERATE ORDER TABLE
ISSUE TABLE
PENDING BOOKS
0&
PURCHASE BOOKS TABLE
00
PURCHASE TABLE
RETURN BOOK TABLE
04
USER TABLE
NEW USER TABLE
08
CODING PART OF THE PROJECT ADMIN
USER
06
ISSUE
GENERATE ORDER
0;
PURCHASE
RETURN
0>
GENERATE FINES
PENDING BOOKS
0B
FEEDBACK
FRONT END OF THE PROJECT
4H
ADMIN
USER
ISSUE
41
GENERATE ORDER
PURCHASE
4&
RETURN
40
GENERATE FINES
PENDING BOOKS
