Chapter 5. Block diagram specification of the proposed Bibliographical Database Management System. 5.1 Preamble. 5.2 BDMS Design.

Transcription

1 Chapter 5 Block diagram specification of the proposed Bibliographical Database Management System 5.1 Preamble. Database functionality is necessary for a large category application which not only confines with in traditional commercial application such as pay roll system or personnel record management but also for modern library. Such applications are difficult to implement because these require a powerful data model for storing a large quantity of information and a powerful operational model to compute the complex operations required by the application. In this chapter, the required data element and data flow of proposed BDMS are designed for library 5.2 BDMS Design. Systematically approach adopted to understand the problems in designing the database application. The basis for a database specifies the problem that is to be solved the ability of resources that can be used in the solution or some likely approaches to the solutions. To formulate the blueprint of more convenient BDMS model, it can be broken to split steps. ^ Determine what functions or facial appearance the library would like to streamline. The first indispensable is to congregate a full understanding of the real needs of the user of a new automated system and determine what function the library would like to automate. Try to identify those repetitive tasks which now occupy of a large amount of man hours. So, priority has to be given for routine works ^ Decide which capabilities are required to support each specific function. Develop a written checklist of specific functions that are essential and those which are desirable. In addition to issue/return, user database creation and reservation what other functions are needed? What sort of reports must be generated by the system. Does

2 the library should use the existing student or patron ID number of the Institute? Whether financial accounts conform to certain bookkeeping standards? How does management and clients want to search the database? > Determine how much data need to be stored: In this step decision has to be taken about the number of titles, volumes, clients, order placed, notices sent, number of vendor etc. In addition books, materials like non-print materials, un-catalogued items, equipments kits, software etc also have to be considered Identify the basis for the Database Requirement. A library automation package has to fulfill the functions of acquisition, cataloguing, serial control, circulation control, information processing and service, documentation, information retrieval and processing. Effective Library automation software should be able to mechanize all of the works in library/information center. Thus it helps the library staff to find more time for the vital functions of the information collection,organization and services. The requirements assessed for the central library NT Kharagpur as a result of an involved survey visiting each section as well as listening to comments of the staff concerned lead to the following points. *** Determination of those functions or features the library would like to be automate. * Listing of essential and desirable functions. * Identify what the library absolutely must have vs. what would be nice to have System Design.,n the process of implementation of Bibliographical Database the various tables are Prepared to handle different function of the database. These tables are describe in proceeding chapter seven. System interaction diagrams are prepared to show the interaction between different subsystem and subtasks of a subsystem. Similarly data flow diagrams (DFDs) are drawn to represent the input data to the system, various Processing carried out on the data and the output data generated by the system.

3 Skeleton of System: Figure 5.1- Integrated Library Information System

4 Compilation o f Bibliographic database o f die Document Figure 5.3- System Interaction Diagram for the Technical processing. Figure 5.4- Circulation. Figure 5.5-Current Journal.

5 Data Flow Diagram Figure 5.6- BDMS.

6

7 Figure Serial Control. A conceptual data m odel fo r a lib ra ry U su rs U s e r_id 1 U s g r j a m e U s e r a J d j e ss E m a i l i d A n d o th e r details B o o k s Out on L o a n serjd 4MemoOssued date^of^retu Tii amount^of^ine Books Title Ssast-alJcss. O th er details o f the books >o- A u th or MjisjLs&Six System control param eter 4Ex~ae-gB irn Msmbat- a$semck Group W orking _ days Hefedax_ ai«a^et Notices Cancellation/jtsgg aent Reasons Fine categorr

8 5.3 Reference. 1 BERNSTEIN, P. A., HADZILACOS, V., AND GOODMAN, N. Concurrency Control and Recovery in Database Systems. Addison Wesley Publishing Company, BRODIE, M., AND RIDJANOVIC, D. On the design and specification of database transactions. In On Conceptual Modeling, Perspectives from Artificial Intelligence, Databases, and Programming Languages, M. Brodic, J. Mylopou- los, and J Schmidt, Eds. Springer Verlag, New York, 1994, pp DATE, C.J. and SELLIS, T. Introduction fo Database Systems. Advances in Object oriented Database system. Springer-Verlag Berlin Heidelberg, ELMASRI, R., and NAVATHE, S.B., Fundamentals of Database System. Addison-Wesley Publishing Co GEPPERT, A., GATZIU, S., DITTRICH, K.R., FRISTCHI, H. and VADUVA, A. Architecture and Implementation of an active Object Oriented database Management System. SAMOS, Technical Report 95.29, Institut fur lnformatic,universat Zurich, Switzerland, KAPPEL, G., RAUSCH-SCHOTT, S., RETSCHITZEGGER, W., and SAKKINEN, M. Multi-Parent Subtransactins Covering the Transactional Needs of Composite Events. In Proc. o f International Workshop on Advanced Transaction Models and Architectures(ATMA-96).E.Bertino, S. Jjodia, and L.Kerschberg.Eds. August 1996., pp KIM, W BALLOU, N., CHOU, H GARZA, J., A N D WOELK, D. Integrating an object oriented programming system with a database system.. In Proceed' g the Conference on Object Oriented Programming Systems, Languages and Applications 1998, pp MIYAZAKI, N. Selection propagation in deductive databases. Data an knowledge Engineering 5, 4., 1990, pp » MOSS, J. E. B. Semantics for transactions in shared object wortds. In Database Pmgmwming Languages, F. Bancilhon and P.Bunel ^ *" Press Frontier Series. Addison Wesley Publishing Co., 199, PP

9 -10. MUECK, T. and POLASCHEK M. Index Data Structures in Object oriented Database. Kluwer Academic Publisher, NGUYEN, G.1AND RIEU1 D. Schema evolution in object oriented database systems. Data and knowledge Engineering 4,1 (1989), NILSSON, N. J. Principles of Artificial Intelligence. Tioga Pub., OHORI, A. Orderings and types in databases. In Advances in Database Programming Languages, F. Bancilhon and P. Buncman, Eds., ACM Press, Frontier Series. Addison Wesley Publishing Co., 1990, pp OZSU, M.T. Transaction Models and Transaction management In Object oriented Database Management System. Sprinter-Verlag., NATO ASI Series F PUJARI, Dr. ARUN KUMAR. Database Management System. ISTE; Learning Materials Centre. New Delhi, RAMAKRISHNAN, R and GEHRKE, J Database Management System. 2nd Edition, McGraw-Hill International Edition, SILBERSCATZ, A., KORTH, H.F. and SUDERSHAN, S. Database System Concepts. McGraw Hill.lnc STEFIK, M., AND BOBROW, D.. Object oriented programming: Themes and variations. The A l Magazine ULLMAN, J. D. Principles of Database and knowledge-base Systems, vol. II. Computer Science Press, VIG, RENU and WALIA, EKTA. Fundamentals of Database Management System. ISTE; Learning Materials Centre. New Delhi, ZDONIK, S., and MAIER, D. Readings in Object oriented Database system. Morgan Kaufmann Publisher, 1990.

10 Chapter 6 E R Model of Library In-House Operations Acquisition, Circulation 6.1 Preamble. The entity Relationship model has existed for more than 20 years ago since the original description of Chan3,4. However E R modeling was never standardized. In an effort to standardized this, a graphical modeling tool called E-R diagram, based on E-R model had been proposed. In this diagram visual symbol are used to indicate each kind of constraints of the E-R model. In other words, the model can be carried out with the help of pictorial representation of entities, attributes and relationship. In this chapter the concepts involved in complex E R modeling for BDMS is considered. The E R model includes semantic concepts other than entities relationship and attributes to study a complete picture mapping of data with E R model for BDMS 13'14' E R Model. The basic entity-relationship model as originally proposed by Chen7, provides two modeling primitives (i.e. entities and relationships) for representing database. The E- R data model vies the real world as a set of basic objects (entities) and relationships among these objects. Formally, the basic entity-relationship schema is denoted as a set S={D, A, E, R\ where D is the database domain, A is the set of attributes, E is the set of entity sets and R is the set of relationship sets. An entity may be concrete (a user, or a book) or abstract (holiday or a concept)9,10,12,14 which is an object that exists and is distinguishable from other objects. For instance ABHAY KUMAR RASTOGI, ID is an entity, and he could be uniquely identified as one particular student of ndian Institute of Technology, Kharagpur. This entity-relationship diagram depicts the major concepts and relationships needed for managing BDMS for captunng the necessary attributes and relationships.

11 RELATIONSHIP MODEL D iagram Symbol JVleaning Entity Relationship E N G L I S H e q u i v a l e n t N o u n V e rb d Attribute of: Entity Relationship Figure E R Diagram Symbol. Adj ective Adverb Figure 6.2- E R Diagram for library In-House Operations Circulation.

12 Fig E-R Diagram for Circulation Fig E R Diagram for item, reserve, borrower Figure E R Diagram for library In-house operations of Acquisition.

13 6.3 Reference: 1. AGRAWAL, R., and GEHANI, N.H. Ode (Object oriented Environment): The Language and the Data Model. In Proceeding of the ACM SIGMOD International Conference on Management of Data. June 2002, pp BRANT, D and MIRANKER.D. Index Support and Rule Activation. In Proceeding of the ACM SIGMOD International Conference on Management of Data. May pp CHEN, P. The entity-relationship model: Towards a unified view or data. ACM Transactions on Database Systems 1, 1 (March 1976), CHEN, P., Ed. Entity-Relationship Approach: The Use of the ER Concept in knowledge Representation. North Holland, Amsterdam, CODD, E. A relational model for large shared data banks. Communications of the ACM 19,6 (June 1970), pp DELCAMBRE L. and ETHERDGE, J. The Relational Production Language: A Production language of Relational Databases. In Expert Database System- Proceeding o f Second International Conference. Benjamin/Cummings, pp HULL, R., AND YAP, C. The format model: A theory of database organization. Journal of Association of Computing Machinery: Jl, 3 (July 1994). 8. KENT, W. Limitations of record-oriented information models. ACM Transactions on Database Systems 4,1(March 1999), KING, R., AND McLEOD, D. A unified model and methodology for conceptual database design. 1n On Conceptual Modeling, Perspectives from Artificial Intelligence, Databases, and Programming Languages, M. Brodie, J. Mylopoulos, and J. Schmidt, Eds. S p r i n g e r Verlag, New York, 1994, pp KUPER, G AND VARDI, M. The logical data model. In Proceedings of A CM.SIGACT News- SIGMOD Symposium on Principles of Database Systems (ACM, New York, 2004), pp

14 11. ROUSSOPOLULOS, N. View Indexing in Relational Databases. ACM Transaction on Database Management System. Vol. 7 June 1982 pp SCHREIER, U PIRAHESH, H., AGRAWAL, R. and MOHON, C. Alert: An Architecture for Transforming a Passive DBMS into an Active DBMS. In Proceedings o f Seventeenth International Conference of Very Large Database. Barcelona, September 1991, pp SHIPMAN, D. The functional data model and the data language DAPLEX. ACM Transactions on Database Systems 6, 1 (March 1981), STONEBRAKER, M. S. et. al. A Rules System for a Relational Database Management System. In Proceedings of Second International Conference on Database. June TSICIIRITZIS, D AND LOCIIOVSKY, F. Data Models. Prentice-Hall, Engle wood Cliffs, New Jersey, 2002.