Close
Login to Your Account
Faadooengineers






F Polls
Loading...
Results 1 to 2 of 2

Thread: Notes for Artificial Intelligence

  1. #1
    Passionate FaaDoO Engineer prasanjeet roy's Avatar
    Join Date
    Jan 2011
    Posts
    286
    Blog Entries
    5

    Gender: : Male

    Branch: : Computer Science Engineering

    Send Private Message
    Send Friend Request

    Doc 32 Notes for Artificial Intelligence

    Do you know about artificial intelligence ? Read some important notes on artificial intelligence. Download doc file to know more about it.



    Attached Files for Direct Download
      File Name:
      File Size:
      607.0 KB
    * Click on the 'file icon' or 'file name' to start downloading
    Last edited by jaivinder; 14th January 2016 at 12:54 PM.

  2. #2
    Fuchcha FaaDoO Engineer
    Join Date
    Jun 2013
    Posts
    1

    Gender: : Male

    Branch: : Computer Science Engineering

    City : Lucknow*

    Send Private Message
    Send Friend Request

    Information Re: Notes for reports

    INRODUCTION
    Borrowing books, returning books or viewing the available books at the Library of the local University is currently done manually where in the student has to go to the Library and check the available books at the Library. Students check the list of books available and borrow the books if the book is a borrow book otherwise it is of waste for the student to come to the library to come to check for the books if the student doesn’t get the book. Then the librarian checks the student id and allows the member to check out the book and the librarian then updates the member database and also the books database. This takes at least one to two hours if the member is available at the near by place otherwise it may take more time.
    We have decided to investigate the use of an Online Library Management System. This system would be used by members who may be students or professors of that University to check the availability of the books and borrow the books, and by the librarian to update the databases. The purpose of this document is to analyze and elaborate on the high-level needs and features of the Online Library System. It focuses on the capabilities and facilities provided by a Library. The details of what all are the needs of the Online Library System and if it fulfils these needs are detailed in the use-case and supplementary specifications.
    1.1 Purpose

    The purpose of Software Requirements Specification (SRS) document is to describe the external behavior of the Online Library System. Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of the Online Library System. The document also describes the nonfunctional requirements such as the user interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system. Requirements described in this document are derived from the Vision Document prepared for the Online Library System.
    1.2 Scope

    The Software Requirements Specification captures all the requirements in a single document. The Online Library System that is to be developed provides the members of the Library and employees of the library with books information, online blocking of books and many other facilities. The Online Library System is supposed to have the following features.
    The product provides the members with online blocking of books capabilities and the Online Library System is up and running all day.
    The system provides logon facility to the users.
    The system provides the members with the option to check their account and/or change their options like password of the account whenever needed all through the day during the library hours.
    The system allows the members to block the books 24 hours a day and all the through the semester.
    The system lets the library staff to check which all members have blocked the books and whether they can borrow any more books or not.
    The system allows the Librarian to create the books catalog, add/delete books and maintain the books catalog.
    The system updates the billing system as and when the member borrows or returns a book.
    The book catalog is automated and the decision of offering the book based on the category of the book is automatically decided.
    We also have an order department, which manages to add or remove a book from the Library.

    The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criteria for the system is based in the level up to which the features described in this document are implemented in the system.
    1.3 Definitions, Acronyms and Abbreviations

    UHCL – University of Houston-Clearlake.
    Provided wherever necessary in the document.
    PIN – Personal Identification Number
    1.4 References

    The SRS document uses the following documents as references:
    1.4.1 UHCL Information Security Requirements: To provide security to the system based on the current security system currently used by UHCL.
    1.4.2 The Billing System: To provide the interface between the system being developed and the billing system currently in use by UHCL to update the member account due as and when they borrow and return the books.
    1.5 Overview

    The SRS will provide a detailed description of the Online Library System. This document will provide the outline of the requirements, overview of the characteristics and constraints of the system.
    1.5.1 Section 2: This section of the SRS will provide the general factors that affect the product and its requirements. It provides the background for those requirements. The items such as product perspective, product function, user characteristics, constraints, assumptions and dependencies and requirements subsets are described in this section.
    1.5.2 Section 3: This section of SRS contains all the software requirements mentioned in section 2 in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements.





    2. STATEMENT ABOUT THE PROBLEM


    The purpose of the LIBRARY MANAGEMENT SYSTEM is mainly to provide automation to the library. The categories of users provided are :
    LIBRARIAN: He can read or write the information about any member and can update, delete or create a membership plan.
    MEMBER: He can get a book issued.
    The Scope of the application is wide and can be used with any education institute and also can be used in offices with the necessary modifications done.
    With this application, the manual application is converted into automated online application. For example purposes, customized data is being used for this purpose. The user will not have the privilege to enter the data about the books.
    2.1 The three major components in the application are:
    -LOGIN
    -ISSUE/BORROW BOOK
    -BALANCE DUES
    2.2 The solutions provided by the system are:
    -better and efficient service provided
    -Faster retrieval of information
    -reduced workload of the library staff
    - All details of the book will be available on a click
    - Less paper work and document maintenance

    3. Why this particular topic chosen?

    The Computer Based Management is an asset for Library management system .Looking forward to a more efficient and streamlined processing system and better coordination between student and the librarian leading to desired results in terms of quality, service, profits, market, share and competitiveness.
    3.1. Multiple Share Information
    This website is share for the multiple information of the library and it provide doctors schedule so it more effective website.
    3.2. Flexible Information System
    The project of Library Management system is more and more flexible for other website .our website is give lot of information for different hospitals.













    4. Objective and Scope

    The purpose of this application is as follows:
    The software is for automation of library.
    Keeping a note of E-Journals, E-Mazines
    Online class tutorials.
    Operator can enter details related to a particular book.
    Operator will provide membership to members.
    Operator will enter details for new books.
    Admin can read and write information about any member.
    Admin will update, create, and delete the record of membership as per requirement and implementation plants.
    Scope


    The Software Requirements Specification captures all the requirements in a single document. The Online Library System that is to be developed provides the members of the Library and employees of the library with books information, online blocking of books and many other facilities. The Online Library System is supposed to have the following features.

    The product provides the members with online blocking of books capabilities and the Online Library System is up and running all day.
    The system provides logon facility to the users.
    The system provides the members with the option to check their account and/or change their options like password of the account whenever needed all through the day during the library hours.
    The system allows the members to block the books 24 hours a day and all the through the semester.
    The system lets the library staff to check which all members have blocked the books and whether they can borrow any more books or not.
    The system allows the Librarian to create the books catalog, add/delete books and maintain the books catalog.
    The system updates the billing system as and when the member borrows or returns a book.
    The book catalog is automated and the decision of offering the book based on the category of the book is automatically decided.
    We also have an order department, which manages to add or remove a book from the Library.

    The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criteria for the system is based in the level up to which the features described in this document are implemented in the system.












    5. Methodology


    Project is related to library management which provides reading services to its members. Any person can become a member of the library by filling a prescribed form. They can get the book issued, so that they can take home and return them. He can also avail the facility of online classes, e-Mazine, E-Journals and etc. This application is used to convert the manual application to the online application. Customized data will be used in this application. User does not have right to enter information about books.
    5.1 Data flow diagram

    Context Diagram


    ONLINE LIBRARY management system
    USER



    ADMIN


    5.2 Level 1 Data Flow Diagram







    5.3 Entity Relation Diagram


    5.4 SNAP SHOTS

    HOME PAGE












    Select Card To Indent




    Indent Page


    Video Tutorial



    Admin Page


    5.5 Module Description:
    Online membership.
    Keeps the track of issues and submission of books.
    Online Magazines.
    E-Videos Tutorials:
    E-Learning tools quickly and easily with these interactive video tutorials and demos. Step-by-step guidance for the world's leading authoring tools.
    E- Generals:
    An electronic library(colloquially referred to as a digital library) is a library in which collections are stored in electronic media formats (as opposed to print, microform, or other media) and accessible via computers.The electronic content may be stored locally, or accessed remotely via computer networks. An electronic library is a type of information retrieval system.

    5.1.1 Interface Requirements:-

    This section describes how the software interfaces with other software products or users for input or output.
    5.5.2 User Interfaces:-
    Describes how this product interfaces with the user.
    5.5.3 GUI
    Describes the graphical user interface if present. This section should include a set of screen dumps or mockups to illustrate user interface features.
    5.5.4 Description
    The user interface must be customizable by the administrator
    5.5.5 Criticality
    This issue is essential to the overall system. All the modules provided with the software must fit into this graphical user interface and accomplish to the standard defined.
    5.5.6 Technical issues
    An order to satisfy this requirement the design should be simple and all the different interfaces should follow a standard template. There will be the possibility of changing colors and images, plus switching between interfaces with the minimum impact for the users.
    5.5.7 Risks
    To reduce the circumstances under which this requirement might not able to be satisfied, all the designers must have been developed web sites previously and they must be aware of html restriction and cross browsers implementations before starting the designing. In order to reduce the probability of this occurrence the entire design team will be trained in basic html development and macromedia fireworks, this tool will be used instead of Photoshop.
    5.5.8 Dependencies with other requirements
    All user interfaces should be able to interact with the user management module and a part of the interface must be dedicated to the login/logout module
    5.6 Non Functional Requirements:-

    5.6.1 Software Requirements:-

    Database: SQL Server.
    Application: ASP (Active Server Pages)
    Web Server: IIS (Internet Information Services (IIS) is a powerful.
    Web server that provides a highly reliable, manageable, and scalable.
    Web application infrastructure.
    5.6.2 Communications Interfaces

    The Customer must connect to the Internet to access the Website:
    Dialup Modem of 52 kbps
    Broadband Internet
    Dialup or Broadband Connection with a Internet Provider.
    5.6.3 Performance Requirements

    The proposed system that we are going to develop will be used as the Chief Performance system within the different campuses of the university which interact with the university staff and students. Therefore, it is expected that the database would perform functionally all the requirements that arespecified by the university.
    5.6.4 Safety Requirements

    The database may get crashed at any certain time due to virus or operating system failure. Therefore, it is required to take the database backup.
    5.6.5 Security Requirements

    We are going to develop a secured database for the university. There are different categories of users namely teaching staff, administrator, library staff,studentsetc, Depending upon the category of user the access rights are decided .It means if the user is an administrator then he can be able to modify the data, delete, append etc. ,All other users other than library staff only have the rights to retrieve the information about database. Software Quality Attributes The Quality of the database is maintained in such a way so that it can be very user friendly to all the users of the database.
    5.6.6 Hardware Constraints

    The system requires a database in order to store persistent data. The database should have backup capabilities.
    5.6.7 Software Constraints

    The development of the system will be constrained by the availability of required software such as web servers, database and development tools. The availability of these tools will be governed by the University of Balart. The most recent versions of software d 5.6Design Constraints The system must be designed to allow web usability. That is, the system must be designed in such a way that will be easy to use and visible on most of the browsers.
    6. Hardware & Software


    Hardware Requirements:-

    Server Side:
    Operating System: Windows 7
    Processor: Pentium 3.0 GHz or higher
    RAM: 256 Mb or more
    Hard Drive: 10 GB or more
    Client side:

    Operating System: Windows 9x or above, MAC or UNIX.
    Processor: Pentium III or 2.0 GHz or higher.
    RAM: 256 Mb or more

    Software Requirements

    Front End: .Net.
    Back End : MS Access, Apache Tomcat server.


    7. Future Scope

    FUTURE SCOPE OF APPLICATION

    This application can be easily implemented under various situations. We can add new features as and when we require. Reusability is possible as and when require in this application. There is flexibility in all the modules.
    SOFTWARE SCOPE:
    This software is extendable in ways that its original developers may not expect.
    Extensibility: The following principles enhances extensibility like hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations.
    Reusability: Reusability is possible as and when require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.
    Understandability: A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method, which small and coherent helps to accomplish this.
    Cost-effectiveness: It is desirable to aim for a system with a minimum cost subject to the condition that it must satisfy the entire requirement. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.
    Last edited by jaivinder; 14th January 2016 at 06:20 PM.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •