This document provides a software requirements specification for a Web Library Management System (WLMS). It outlines the purpose, scope, definitions, and overview of the system. It describes the overall functions for administrators and normal users. It specifies both functional and non-functional requirements. It provides illustrations of interfaces and usage scenarios, including screenshots. It also describes the data models and attributes for stored items like members, books, and DVDs. The goal is to provide guidelines for developers to design and build the WLMS application.
This document outlines the requirements for a new project at the Shreem Institute of Professional Development. It includes an introduction describing the organization's goals and objectives for the project, the project scope and what functionality will and will not be included. It also discusses assumptions, constraints, risks, and an overview of the current and proposed business processes. The document is intended to define what needs to be developed and guide the project team in building the requested features.
This document provides a summary of Sivareddy's professional experience working as an SAP HANA Consultant. He has over 4 years of experience designing, developing, and implementing SAP HANA solutions with a strong knowledge of BODS and BOBI. Some of his technical skills include SAP HANA, data replication methods like SLT and BODS, and reporting tools like SAP BOBI. He has worked on several projects for clients like Winn-Dixie Supermarkets, Nationwide Insurance, Trinity Health, and Brother International, where he developed attribute views, analytic views, calculation views, decision tables, and reports in SAP HANA and BOBI.
This document is a functional specification for a project with the purpose of describing the functions and scope. It includes sections for an introduction, scope overview, and a list of functions. The introduction defines the purpose and references other documents. The scope overview describes the project and lists any constraints or assumptions. The list of functions section defines each function with a description, process flow, and field details.
PC Solutions for your home, your work, and your life
The document outlines the business requirements and technical design for a new website. It details functional requirements around user access levels, the landing page layout, search functionality, and social networking features. It also covers advertising integration, data collection, and product/category pages. The technical design section describes the overall system architecture and security approach.
This document provides a template for a Business Requirements Document (BRD) to define requirements for a new Widget Interactive Naming System (WINS) project. The summary includes:
- WINS will create a central repository to house widget name records and links across the enterprise to avoid duplication and reduce development time.
- The current process where each team creates widgets independently will be replaced by a new process where WINS validates widget names and updates are tracked.
- Requirements are categorized by priority and functionality, including general requirements for the repository, security, reporting, and usability, as well as non-functional requirements for performance, availability and more.
This document provides guidance on defining and implementing Business Application Programming Interfaces (BAPIs) in SAP systems. It describes what BAPIs are, how they are defined in the Business Object Repository (BOR) and implemented as function modules. Frequently used generic BAPIs for reading, creating, and updating data are listed. The steps for defining a BAPI scenario, determining the relevant business objects, and defining the BAPI interface and functionality are also outlined.
The document provides an overview of a software requirements specification for a Personal Medical Record (PMR) mobile application designed for the Motorola Droid phone. The PMR app will allow users to store, access, and comment on their medical records from their phone. Medical records will be stored on a central database and the app will download the latest records from the server. The document outlines the purpose, scope, definitions, organization, description of key functions and user characteristics, constraints, assumptions, and specific requirements of the PMR app.
The document describes a library management system project created by a group of students. It includes an acknowledgement section thanking those who provided guidance. The introduction provides an overview of the project, which uses HTML, PHP, CSS and JavaScript to develop a software system for basic library operations like adding members and books, and searching. It has four main modules: data insertion, data extraction, report generation, and search. The document also covers feasibility analysis, system requirements, existing manual system problems, proposed automated system advantages, technologies used, and a basic cost estimation.
This document outlines the requirements for a new project at the Shreem Institute of Professional Development. It includes an introduction describing the organization's goals and objectives for the project, the project scope and what functionality will and will not be included. It also discusses assumptions, constraints, risks, and an overview of the current and proposed business processes. The document is intended to define what needs to be developed and guide the project team in building the requested features.
This document provides a summary of Sivareddy's professional experience working as an SAP HANA Consultant. He has over 4 years of experience designing, developing, and implementing SAP HANA solutions with a strong knowledge of BODS and BOBI. Some of his technical skills include SAP HANA, data replication methods like SLT and BODS, and reporting tools like SAP BOBI. He has worked on several projects for clients like Winn-Dixie Supermarkets, Nationwide Insurance, Trinity Health, and Brother International, where he developed attribute views, analytic views, calculation views, decision tables, and reports in SAP HANA and BOBI.
This document is a functional specification for a project with the purpose of describing the functions and scope. It includes sections for an introduction, scope overview, and a list of functions. The introduction defines the purpose and references other documents. The scope overview describes the project and lists any constraints or assumptions. The list of functions section defines each function with a description, process flow, and field details.
PC Solutions for your home, your work, and your life
The document outlines the business requirements and technical design for a new website. It details functional requirements around user access levels, the landing page layout, search functionality, and social networking features. It also covers advertising integration, data collection, and product/category pages. The technical design section describes the overall system architecture and security approach.
This document provides a template for a Business Requirements Document (BRD) to define requirements for a new Widget Interactive Naming System (WINS) project. The summary includes:
- WINS will create a central repository to house widget name records and links across the enterprise to avoid duplication and reduce development time.
- The current process where each team creates widgets independently will be replaced by a new process where WINS validates widget names and updates are tracked.
- Requirements are categorized by priority and functionality, including general requirements for the repository, security, reporting, and usability, as well as non-functional requirements for performance, availability and more.
This document provides guidance on defining and implementing Business Application Programming Interfaces (BAPIs) in SAP systems. It describes what BAPIs are, how they are defined in the Business Object Repository (BOR) and implemented as function modules. Frequently used generic BAPIs for reading, creating, and updating data are listed. The steps for defining a BAPI scenario, determining the relevant business objects, and defining the BAPI interface and functionality are also outlined.
The document provides an overview of a software requirements specification for a Personal Medical Record (PMR) mobile application designed for the Motorola Droid phone. The PMR app will allow users to store, access, and comment on their medical records from their phone. Medical records will be stored on a central database and the app will download the latest records from the server. The document outlines the purpose, scope, definitions, organization, description of key functions and user characteristics, constraints, assumptions, and specific requirements of the PMR app.
The document describes a library management system project created by a group of students. It includes an acknowledgement section thanking those who provided guidance. The introduction provides an overview of the project, which uses HTML, PHP, CSS and JavaScript to develop a software system for basic library operations like adding members and books, and searching. It has four main modules: data insertion, data extraction, report generation, and search. The document also covers feasibility analysis, system requirements, existing manual system problems, proposed automated system advantages, technologies used, and a basic cost estimation.
Parnab Nandy SAP BW Consultant Resume Parnab Nandy
Parnab Nandy has over 2.7 years of experience working as a BW Consultant at Maventic Innovative Solutions Pvt. Ltd. He has experience developing and supporting SAP BW 7.4/7.5 on HANA, BW 4/HANA, and SAP BO 4.1. Some of his responsibilities include designing and developing SAP BW and BO reports according to business needs, data modeling, extraction, loading, and scheduling in BW, and building and designing dashboards and reports in SAP Analytics Cloud and WEBI. He has worked on several projects involving ECC integration with BW On HANA, developing BW reports, data flows, and WEB
SRS for smart health care system,srs for health system,health management doc...AnilkumarSingh129
SRS(it stands for software requirement specification)which is usualy used in the software engineering field for present the view of software for the client.Basically it will devloped by the programer in the it field.In IT field SRS is very importent part of the software.
This document outlines the aims, objectives, literature review, methods, system design, and challenges of developing a library management system. The project aims to create a user-friendly interface that provides fast access to the database with less errors and quick transactions. The literature review discusses previous research on user criteria for library services and descriptions of library management systems. The system design section covers input, output, database design, and a dataflow diagram. Developing the system for a small college library poses challenges around limited storage capacity and restrictions for a small number of users.
Technical Overview of CDS View – SAP HANA Part IAshish Saxena
SAP HANA has introduced new paradigms to SAP ABAP application programming. Before SAP HANA, development paradigm in SAP was based on DATA-to-Code where intensive calculation was done at the application layer and database utilization was minimized. New programming paradigm in SAP HANA is Code-to-Data, where the intensive calculation is done at the database layer and less programming at application layer.
This library management system is a web application developed in ASP.NET 2.0 using C# and SQL Server 2005. It allows librarians to perform operations like issuing books, returning books, adding members, and searching for books. The application code is organized into folders for pages, themes, code files and the database. It uses tables like USERS, SUBJECTS, MEMBERS, TITLES, ISSUES and RETURNS to manage member, book and transaction data.
Documento que explica como realizar la integración entre SAP (BW- HANA) y PowerBI para maximizar el potencial de análisis de los datos económicos y financieros de las compañías
Condition changes with mekp mekr and meklarmindajack
The document discusses condition changes in purchasing transactions. It provides details on three transactions - MEKP, MEKR, and MEKLE - used to change conditions for info records, contracts, and scheduling agreements respectively. The transactions select conditions using selection criteria and make changes using functionality in module pool SAPFM06K. Changes can be made to a single date or a period of time, which impacts how validity periods are handled. Common problems arise from data inconsistencies like overlapping validity periods. The document also covers currency conversions, condition tables, and notes on issues customers have encountered.
Taller permisos de archivos y directorios ubuntuJose Diaz Silva
El documento explica cómo administrar permisos de archivos y directorios en Ubuntu usando el comando chmod. Chmod permite asignar permisos de lectura, escritura y ejecución al propietario, grupo u otros usuarios usando números del 0 al 7 o letras. El documento también incluye una actividad práctica para crear directorios y archivos, modificar sus permisos de forma recursiva y probar la ejecución de archivos.
The document contains 14 questions related to SAP ABAP development topics including: client numbers used for projects, reducing report execution time, handling error records from background jobs, deciding between method calls and sessions for BDC programs, differences between reports and scripts, differences between scripts and smart forms, what enhancements are, what user-exits are, what BADIs are, differences between user-exits and BADIs, differences between user-exits and customer-exits, obtaining functional specifications, writing technical specifications, and writing unit test plans.
This document contains a profile summary for Sivareddy, an SAP HANA consultant with over 4 years of experience in HANA modeling, development, implementation, and reporting using BODS and BOBI. He has worked on several projects involving data extraction and analytics for clients such as Winn-Dixie Supermarkets, Nationwide Insurance, Trinity Health, and Brother International Corporation. His skills include HANA development, data modeling, ETL, reporting with BOBI, and experience with Oracle and SQL Server databases.
This document describes how to create a user-defined field in CO line item reports by programming an ABAP exit. It involves extending the output structure to include the new field, programming the exit to fill the field with data from other tables, and maintaining the view V_TKALV to provide metadata for the report on the new field. An example is provided of adding a "Cost Center Manager" field to actual cost line item reports by retrieving the manager from the CSKS table.
The document provides a software requirements specification for an online university admission system. It includes sections on introduction, overall description, system requirements and analysis, and supplementary requirements. The introduction provides an overview of the current admission process and purpose of automating it. The overall description outlines the system scope, user classes and features. The requirements section specifies functionality for the user interface, student and admission views, and system requirements. The specification concludes with supplementary and non-functional requirements.
This document provides an alphabetical overview of all SAP ABAP keywords and commands. It lists keywords such as ADD, CALL FUNCTION, CASE, CHECK, CLASS and more. For each keyword, it provides the syntax and a short description of its usage in 1-3 sentences. The document appears to be an exhaustive reference list for all ABAP language elements.
Shivansh Bhatnagar is an SAP ABAP professional with over 3.7 years of experience developing and supporting SAP R/3 systems. He has experience in various industries including manufacturing, chemicals, and coatings. Some of his responsibilities have included requirements analysis, technical specification design, coding, testing, and performance tuning. He has knowledge of various SAP modules including SD, FI, MM, and PP.
This training package provides over 25-80 hours of video training covering Adobe Forms development in SAP. It covers topics like the Adobe Forms interface, developing form objects, form design with properties, conditions, tables and subforms. It also demonstrates integrating Adobe Forms with Web Dynpro ABAP and using offline forms to insert data into databases. The training videos are in MP4 format and provide lifelong access so students can learn at their own pace.
Power BI es un servicio de inteligencia empresarial de Microsoft que permite a las empresas consolidar, analizar, visualizar y compartir sus datos de forma interactiva. Fue lanzado en 2011 y consta de varias aplicaciones como Power BI Desktop, el servicio Power BI y aplicaciones móviles. Power BI Desktop permite a los usuarios conectarse a datos, transformarlos y crear informes visuales de forma gratuita.
Final sds of academic a webpage based android applicationpreeta sinha
This document provides the design details of an Android application called Academic for a university. It includes sections on architectural design, data structure design, user interface design, and testing. The architectural design section describes the overall software architecture and work breakdown for administrators, students, heads of department, and staff. It also includes entity relationship diagrams, context diagrams, and data flow diagrams. The document outlines the various data tables that will be needed. It describes that the user interface will include screens for login, home page, and other functions. It discusses that unit, integration, and acceptance testing will be used to test the application.
SAP HANA is an in-memory database platform that can be deployed on-premise or in the cloud. When deployed on-premise, SAP HANA combines software and hardware components optimized by SAP and its partners. In the cloud, SAP HANA is offered through managed services on infrastructure like SAP HANA One. To take advantage of SAP HANA's high-speed processing, developers can use Open SQL, core data services, and ABAP managed database procedures.
This document provides a software requirements specification for a library management system. It includes sections that describe the purpose, conventions, intended users, project scope, and references for the system. The overall description outlines the product perspective, features, user classes, operating environment, and assumptions. System features include the database for storage and functional requirements. Non-functional requirements cover the user interface, hardware, software, communications, performance, safety, security, and design constraints. The appendices define terms, include any models, and list open issues.
This document provides a summary of requirements for a Library Management System. It includes 3 sections:
1. Introduction - Defines the purpose, scope and intended audience of the system which is to manage library processes like book borrowing online.
2. Overall Description - Outlines key product functions for administrators and users, the operating environment, user characteristics and design constraints.
3. External Interfaces - Specifies the user interface requirements including login, search and categories. Hardware and software interfaces are also listed.
The document provides a high-level overview of the essential functions, behaviors and non-functional requirements for the library management software.
Parnab Nandy SAP BW Consultant Resume Parnab Nandy
Parnab Nandy has over 2.7 years of experience working as a BW Consultant at Maventic Innovative Solutions Pvt. Ltd. He has experience developing and supporting SAP BW 7.4/7.5 on HANA, BW 4/HANA, and SAP BO 4.1. Some of his responsibilities include designing and developing SAP BW and BO reports according to business needs, data modeling, extraction, loading, and scheduling in BW, and building and designing dashboards and reports in SAP Analytics Cloud and WEBI. He has worked on several projects involving ECC integration with BW On HANA, developing BW reports, data flows, and WEB
SRS for smart health care system,srs for health system,health management doc...AnilkumarSingh129
SRS(it stands for software requirement specification)which is usualy used in the software engineering field for present the view of software for the client.Basically it will devloped by the programer in the it field.In IT field SRS is very importent part of the software.
This document outlines the aims, objectives, literature review, methods, system design, and challenges of developing a library management system. The project aims to create a user-friendly interface that provides fast access to the database with less errors and quick transactions. The literature review discusses previous research on user criteria for library services and descriptions of library management systems. The system design section covers input, output, database design, and a dataflow diagram. Developing the system for a small college library poses challenges around limited storage capacity and restrictions for a small number of users.
Technical Overview of CDS View – SAP HANA Part IAshish Saxena
SAP HANA has introduced new paradigms to SAP ABAP application programming. Before SAP HANA, development paradigm in SAP was based on DATA-to-Code where intensive calculation was done at the application layer and database utilization was minimized. New programming paradigm in SAP HANA is Code-to-Data, where the intensive calculation is done at the database layer and less programming at application layer.
This library management system is a web application developed in ASP.NET 2.0 using C# and SQL Server 2005. It allows librarians to perform operations like issuing books, returning books, adding members, and searching for books. The application code is organized into folders for pages, themes, code files and the database. It uses tables like USERS, SUBJECTS, MEMBERS, TITLES, ISSUES and RETURNS to manage member, book and transaction data.
Documento que explica como realizar la integración entre SAP (BW- HANA) y PowerBI para maximizar el potencial de análisis de los datos económicos y financieros de las compañías
Condition changes with mekp mekr and meklarmindajack
The document discusses condition changes in purchasing transactions. It provides details on three transactions - MEKP, MEKR, and MEKLE - used to change conditions for info records, contracts, and scheduling agreements respectively. The transactions select conditions using selection criteria and make changes using functionality in module pool SAPFM06K. Changes can be made to a single date or a period of time, which impacts how validity periods are handled. Common problems arise from data inconsistencies like overlapping validity periods. The document also covers currency conversions, condition tables, and notes on issues customers have encountered.
Taller permisos de archivos y directorios ubuntuJose Diaz Silva
El documento explica cómo administrar permisos de archivos y directorios en Ubuntu usando el comando chmod. Chmod permite asignar permisos de lectura, escritura y ejecución al propietario, grupo u otros usuarios usando números del 0 al 7 o letras. El documento también incluye una actividad práctica para crear directorios y archivos, modificar sus permisos de forma recursiva y probar la ejecución de archivos.
The document contains 14 questions related to SAP ABAP development topics including: client numbers used for projects, reducing report execution time, handling error records from background jobs, deciding between method calls and sessions for BDC programs, differences between reports and scripts, differences between scripts and smart forms, what enhancements are, what user-exits are, what BADIs are, differences between user-exits and BADIs, differences between user-exits and customer-exits, obtaining functional specifications, writing technical specifications, and writing unit test plans.
This document contains a profile summary for Sivareddy, an SAP HANA consultant with over 4 years of experience in HANA modeling, development, implementation, and reporting using BODS and BOBI. He has worked on several projects involving data extraction and analytics for clients such as Winn-Dixie Supermarkets, Nationwide Insurance, Trinity Health, and Brother International Corporation. His skills include HANA development, data modeling, ETL, reporting with BOBI, and experience with Oracle and SQL Server databases.
This document describes how to create a user-defined field in CO line item reports by programming an ABAP exit. It involves extending the output structure to include the new field, programming the exit to fill the field with data from other tables, and maintaining the view V_TKALV to provide metadata for the report on the new field. An example is provided of adding a "Cost Center Manager" field to actual cost line item reports by retrieving the manager from the CSKS table.
The document provides a software requirements specification for an online university admission system. It includes sections on introduction, overall description, system requirements and analysis, and supplementary requirements. The introduction provides an overview of the current admission process and purpose of automating it. The overall description outlines the system scope, user classes and features. The requirements section specifies functionality for the user interface, student and admission views, and system requirements. The specification concludes with supplementary and non-functional requirements.
This document provides an alphabetical overview of all SAP ABAP keywords and commands. It lists keywords such as ADD, CALL FUNCTION, CASE, CHECK, CLASS and more. For each keyword, it provides the syntax and a short description of its usage in 1-3 sentences. The document appears to be an exhaustive reference list for all ABAP language elements.
Shivansh Bhatnagar is an SAP ABAP professional with over 3.7 years of experience developing and supporting SAP R/3 systems. He has experience in various industries including manufacturing, chemicals, and coatings. Some of his responsibilities have included requirements analysis, technical specification design, coding, testing, and performance tuning. He has knowledge of various SAP modules including SD, FI, MM, and PP.
This training package provides over 25-80 hours of video training covering Adobe Forms development in SAP. It covers topics like the Adobe Forms interface, developing form objects, form design with properties, conditions, tables and subforms. It also demonstrates integrating Adobe Forms with Web Dynpro ABAP and using offline forms to insert data into databases. The training videos are in MP4 format and provide lifelong access so students can learn at their own pace.
Power BI es un servicio de inteligencia empresarial de Microsoft que permite a las empresas consolidar, analizar, visualizar y compartir sus datos de forma interactiva. Fue lanzado en 2011 y consta de varias aplicaciones como Power BI Desktop, el servicio Power BI y aplicaciones móviles. Power BI Desktop permite a los usuarios conectarse a datos, transformarlos y crear informes visuales de forma gratuita.
Final sds of academic a webpage based android applicationpreeta sinha
This document provides the design details of an Android application called Academic for a university. It includes sections on architectural design, data structure design, user interface design, and testing. The architectural design section describes the overall software architecture and work breakdown for administrators, students, heads of department, and staff. It also includes entity relationship diagrams, context diagrams, and data flow diagrams. The document outlines the various data tables that will be needed. It describes that the user interface will include screens for login, home page, and other functions. It discusses that unit, integration, and acceptance testing will be used to test the application.
SAP HANA is an in-memory database platform that can be deployed on-premise or in the cloud. When deployed on-premise, SAP HANA combines software and hardware components optimized by SAP and its partners. In the cloud, SAP HANA is offered through managed services on infrastructure like SAP HANA One. To take advantage of SAP HANA's high-speed processing, developers can use Open SQL, core data services, and ABAP managed database procedures.
This document provides a software requirements specification for a library management system. It includes sections that describe the purpose, conventions, intended users, project scope, and references for the system. The overall description outlines the product perspective, features, user classes, operating environment, and assumptions. System features include the database for storage and functional requirements. Non-functional requirements cover the user interface, hardware, software, communications, performance, safety, security, and design constraints. The appendices define terms, include any models, and list open issues.
This document provides a summary of requirements for a Library Management System. It includes 3 sections:
1. Introduction - Defines the purpose, scope and intended audience of the system which is to manage library processes like book borrowing online.
2. Overall Description - Outlines key product functions for administrators and users, the operating environment, user characteristics and design constraints.
3. External Interfaces - Specifies the user interface requirements including login, search and categories. Hardware and software interfaces are also listed.
The document provides a high-level overview of the essential functions, behaviors and non-functional requirements for the library management software.
Software requirements specification of Library Management SystemSoumili Sen
The document provides requirements for a Library Management System. It includes 3 or less sentences:
The Library Management System aims to computerize library processes like book borrowing and maintain member and book details in a database. It will allow librarians and members to search for books, view member accounts, and generate reports. The system needs to be secure, fast, and compatible with common browsers and operating systems.
Library mangement system project srs documentation.docjimmykhan
The document describes a library management system created in Java. It has four main modules: inserting data into the database, extracting data from the database, generating reports on borrowed and available books, and a search facility. The proposed system automates library processes like adding members and books, searching, borrowing and returning books. This makes transactions faster and reduces errors compared to the manual existing system. The system was implemented using Java, MS Access for the database, and designed to run on Windows operating systems. Testing was done to check functionality and ensure all requirements were met.
This document provides a software requirements specification (SRS) for a library management system. It describes the existing manual system, proposed automated system, system requirements, and key system features. The proposed system will automate library operations like adding books and members, searching, borrowing and returning books, and generating reports. It aims to make transactions faster and reduce errors compared to the existing manual process. The SRS outlines user interface designs, database tables, and an implementation plan for training users and transitioning to the new system.
System requirement specification report(srs) T/TN/Gomarankadawala Maha vidyal...Ravindu Sandeepa
System requirement specification report
On
LIBRARY MANAGEMENT
SYSTEM
Done by
Information Communication Technology (NVQ Level 5)
District Vocational Training Center, VTA Srilanka
2016 Batch
,
www.gmvclc.sch.lk
The document outlines requirements for a bed and breakfast management system according to IEEE standards. It includes sections on introduction, overall description, and specific requirements. The introduction defines the purpose and scope of the software, which will be called the Bed and Breakfast Management System. It will include functional requirements like searching for vacancies and non-functional requirements like acting as an independent calendar. The overall description breaks down the key functions and constraints. Specific requirements include external interface requirements, classes/objects in the system, and state transition diagrams.
Online auction system is web based application, in which the seller can sell the goods by sitting in his own house ,so the main advantage of this application is that there is no more system compatibility requirement problem. The main advantage of the online auction system is that the user can have the better choices for their investment and also it is time saving , and through this system user can invest in their own selected firm.
Wants to view the record of all students
Pre-Conditions The records of students are already added in the database.
Post-Conditions The record of all students is presented in tabular form.
Main Success Scenario 1. Admin selects the menu option to view record of all students.
2. LMS presents the record of all students in tabular form.
Alternative Flows: None
Technology Online web access is supported.
Special Requirements In case of high latency the response time may exceed up to 1 minute.
The System can support Urdu English and French language.
Open Issues If the site
This document provides a software requirements specification for a social networking website. It contains 3 milestones that outline the purpose, functions, and design of the social networking site. Milestone 1 introduces the document and defines the product scope. Milestone 2 describes the product perspective, functions, operating environment, and interface requirements. It includes flow diagrams and interface designs. Milestone 3 covers the design phase, work distribution, and planning chart for the social networking website project. The document was prepared by 5 individuals and provides a requirements specification for developing a social media site.
SRS for student database management systemSuman Saurabh
This document is a software requirements specification for a student management portal being developed for LNMIIT. It outlines the purpose, scope, functions, users and operating environment of the system. The key functions are to maintain student records and grades, allow students to view their information, and give medical officers and coaches access to relevant health and sports data of students. It will be a web-based system built using Java, PHP and MySQL that can be accessed by around 20 staff, 1 administrator and 150 students concurrently.
This document provides a project report for developing a Hospital Management System. It includes requirements for key functions like patient registration, assigning patient IDs, generating reports on patient and bed information, and updating patient records in the database. The system is intended to automate manual paper-based processes currently used by the hospital. It will utilize web-based and MySQL database technologies with a Windows development environment.
The document discusses requirements analysis, which involves understanding customer needs and expectations for a proposed system. Requirements analysis is necessary to ensure projects align with business goals and specifications. The requirements analysis process includes identifying system boundaries, customers, eliciting requirements through stakeholder interviews, analyzing requirements, documenting requirements in a specification, and managing evolving requirements. An effective software requirements specification establishes agreement between customers and developers on system functionality.
This document provides an overview of a college management system software project created by a group of students. The objective is to develop a graphical user interface based software that is platform independent, user friendly, and can manage all aspects of a college. It aims to overcome issues with existing college management software like platform dependency, data redundancy, slow execution, and security threats. The proposed software would include modules for accounts, academics, training and placement, exams, library, laboratories, hostels, cafeterias, transportation, and culture. It would use a relational database to reduce data redundancy and Java for platform independence. The document describes the requirements and provides an entity relationship diagram and data flow diagram of the system.
The document outlines specifications for a bank management system that allows customers to create and manage bank accounts. It includes sections on team members, aims, problem description, requirements, module descriptions, entity relationship diagrams, outputs, conclusions, and screenshots. The system provides customers access to create accounts, deposit/withdraw funds, and view reports. It was developed to meet banking needs and allow additional functionality beyond conventional systems.
The document provides information about a library management system project for an education institute. It discusses the need to automate the library's processes to make it more efficient. Some key points include:
- The existing manual system has limitations like time consumption, difficulty in searching and maintaining records.
- The new system aims to address these issues and make operations like book searching, issuing and returning faster and easier for students and staff.
- It will also facilitate generating various reports and calculating late fees for overdue books.
The document describes a proposed online library management system. It includes sections on methodology, scope, requirements, design diagrams, screenshots and future scope. The key points are:
1. The proposed system will manage book and member records, transactions, and generate reports to provide an efficient service for librarians and members.
2. The system will allow librarians to add, issue, and return books and update member information. Members can check book availability and status.
3. Entity relationship, use case, sequence, and activity diagrams were designed to model the system's functions and interactions between librarians and members.
This document is the administrator's guide for Citrix XenServer 5.6 Feature Pack 1. It provides information on managing users and authentication using Active Directory, configuring resource pools and high availability, managing storage repositories and virtual disk images, and using Role Based Access Control (RBAC) to manage access permissions. The guide contains information on XenServer concepts like hosts, pools, virtual block devices (VBDs), and virtual disk data formats (VHD and LUN-based). It also describes features like storage management, host power on configuration, and auditing.
This document provides an overview of the Paladin network security system, including descriptions of the Paladin server, client workstations, and admin console. It discusses system requirements, installation instructions for the Paladin server and running it with SQL or MSDE databases. It also outlines how to configure system settings like email/proxy servers and port settings. The document describes how to set up policies for clients by configuring scan schedules, item actions, preventions, and alerts. It explains how to manage clients and detected spyware items.
This document provides an overview of BizTalk and discusses its key components and features. It covers topics like why BizTalk is useful, how its messaging engine works using publish/subscribe, developing the BizTalk environment, and includes examples of using various adapters like FTP and file. The document is organized into chapters that cover messaging basics and schemas, maps, and pipelines.
TortoiseSVN is a Windows client for Subversion version control. It provides features for importing and exporting files to a repository, checking out working copies, committing changes, updating working copies, and viewing project history. The document discusses TortoiseSVN's installation, basic version control concepts, repository creation and management, daily use features like committing and updating, and resolving conflicts. It is intended as a user guide for getting started with and using TortoiseSVN for source control management.
This document provides an overview of ALBPM Studio 6.0, including information on migrating projects from previous versions, the main components of the process designer like projects, processes, activities and transitions, and configuration options. It covers the user interface, preferences, project structure, process instances, variables, and audit event generation.
The document provides an overview of configuring and managing Red Hat clusters. It discusses setting up hardware, installing cluster software, and using various configuration tools like Conga, system-config-cluster, and command line tools. Conga is a comprehensive GUI for installing, configuring, and managing clusters and storage. system-config-cluster is also a GUI for configuring and managing clusters. Command line tools provide an alternative to the graphical tools.
This document provides instructions for configuring and managing Red Hat Cluster for Red Hat Enterprise Linux 5. It discusses setting up hardware and installing the Red Hat Cluster software. It then describes using the Conga and system-config-cluster tools to configure clusters, including defining global properties, cluster members, failover domains, resources, and services. It also covers starting, stopping, and managing clusters and troubleshooting problems.
This document is a C++ Programming HOW-TO guide that provides information on various topics related to C++ programming. It begins with an introduction comparing C++ and Java. It then discusses the different string class varieties in C++, downloading string classes, and how to use the string class including operators and functions. Further sections cover the string.h file, renaming the string class, the file class, deleting functions, pointers issues, memory allocation functions, debugging files, Java-like APIs, IDE tools, online textbooks, coding standards, online documentation, memory tools, related URLs, scripting languages, templates, the STL, threads, utilities, other document formats, copyright information, and an appendix with a string program example
This document introduces building a cookbook application in Ruby on Rails. It discusses configuring the database to use SQLite and generating a recipes interface using scaffolding. Scaffolding automatically generates the database migration file, model, views, and controller to quickly develop the interface. The chapter also covers testing the application and how Rails provides these features through its conventions and components.
Verio Web Hosting Virtual Server Handbookwebhostingguy
This document provides an introduction to Blue Reef's Virtual Server system. It discusses how virtual servers work and their advantages over do-it-yourself or traditional ISP hosting. The document also covers getting started with the virtual server, including understanding email configurations, registering domains, administering servers remotely, and the directory structure. It provides overviews of the iManager and iRoot tools for managing virtual servers and sections on maintenance tasks like managing quotas, loads, users, and troubleshooting issues.
Verio Web Hosting Virtual Server Handbookwebhostingguy
The document is a user guide for Blue Reef's Virtual Server System. It introduces the Virtual Server System as an alternative to owning a dedicated server. The Virtual Server System allows customers to have their own virtual servers hosted on Blue Reef's equipment to gain the benefits of a dedicated server at a lower cost than maintaining their own physical server. It provides an overview of the core virtual server services including web, FTP, email, and the Virtual Server Administrator interface for remotely managing virtual servers.
This document provides an overview of the configuration and advanced operation capabilities of the OMNI 6000/3000 flow computer firmware revisions 22.74 and 26.74. It describes how to configure physical inputs and outputs, meter stations, meter runs, temperature, pressure, density, products, batches, and other parameters using the keypad in program mode. It also covers user-programmable functions including Boolean flags, variables, and display screens. Finally, it details the flow equations and algorithms used to calculate flow rates and properties for liquid hydrocarbons in US customary and SI metric units.
The document provides instructions for creating a new Seam project using the New Seam Project wizard, which allows selecting project facets like JPA to add functionality, configuring Java build settings and web module settings, and adding JSF capabilities to the project. It also describes facets for things like the Seam component model and configuration options available in the wizard for customizing the new project setup.
This document provides an overview of the Exim mail transfer agent (MTA). It describes how Exim receives and delivers mail, the building and installation process, configuration options, and transports. Key components include routers for processing addresses, transports for delivery, and the use of regular expressions, lookups, and lists.
• Displays the name of the user assigned as the primary provider for the case.
• If no primary provider has been assigned, this will be blank.
Case Type:
• Displays the type of case (FAP, FINS, Clinical, etc.)
Status:
• Displays the status of the case (Open, Closed, etc.)
Date Opened:
• Displays the date the case was opened.
Action Items
Users with case assignment and/or form approval rights will see an Action Items section. This
section displays a list of tasks that require the user’s attention, such as:
- Forms awaiting approval/denial
- Case transfers awaiting approval
This document provides an overview and tutorial for building an ASP.NET MVC Music Store application. It begins by creating a new ASP.NET MVC 3 project and adding prerequisite software. Controllers and views are then added to implement basic pages for the home, store index, and individual albums. The tutorial progresses to adding data access with Entity Framework Code First, validation, authorization, a shopping cart, registration/checkout, and final styling. Each section builds upon the previous to create a full-featured e-commerce music store application using ASP.NET MVC patterns and practices.
This document provides a tutorial for building an ASP.NET MVC Music Store application. It begins by creating a new ASP.NET MVC 3 project and adding a HomeController to handle the home page. Next, a StoreController is added to manage store browsing functionality, including listing music genres, browsing albums in a genre, and viewing album details. The tutorial then covers data access using Entity Framework Code First, adding validation, membership, a shopping cart, registration and checkout functionality. It concludes by implementing additional site features like navigation, layout updates, and displaying top selling albums on the home page.
This document provides an overview and tutorial for building an ASP.NET MVC Music Store application. It begins by creating a new ASP.NET MVC 3 project and adding prerequisite software. Controllers and views are then added to implement basic pages for the home, store index, and individual albums. The tutorial progresses to adding data access with Entity Framework Code First, validation, authorization, shopping cart functionality, registration/checkout, and final design updates. Each section builds upon the previous work to create a full-featured e-commerce music store application using ASP.NET MVC patterns and practices.
This document provides an overview and tutorial for building an ASP.NET MVC Music Store application. It begins by creating a new ASP.NET MVC 3 project and adding prerequisite software. Controllers and views are then added to implement basic pages for the home, store index, and individual albums. The tutorial progresses to adding data access with Entity Framework Code First, validation, authorization, a shopping cart, registration/checkout, and final styling. Each section builds upon the previous to create a full-featured e-commerce music store application using ASP.NET MVC patterns and practices.
This document provides an overview and introduction to the Data Services Management Console: Administrator Guide. It welcomes the reader to Data Services XI Release 3 and lists the documentation set. It describes how to access the documentation on Windows and UNIX systems as well as from the Business Objects website. Finally, it provides Business Objects' information resources for customer support, consulting, training, and submitting documentation feedback.
Low power architecture of logic gates using adiabatic techniquesnooriasukmaningtyas
The growing significance of portable systems to limit power consumption in ultra-large-scale-integration chips of very high density, has recently led to rapid and inventive progresses in low-power design. The most effective technique is adiabatic logic circuit design in energy-efficient hardware. This paper presents two adiabatic approaches for the design of low power circuits, modified positive feedback adiabatic logic (modified PFAL) and the other is direct current diode based positive feedback adiabatic logic (DC-DB PFAL). Logic gates are the preliminary components in any digital circuit design. By improving the performance of basic gates, one can improvise the whole system performance. In this paper proposed circuit design of the low power architecture of OR/NOR, AND/NAND, and XOR/XNOR gates are presented using the said approaches and their results are analyzed for powerdissipation, delay, power-delay-product and rise time and compared with the other adiabatic techniques along with the conventional complementary metal oxide semiconductor (CMOS) designs reported in the literature. It has been found that the designs with DC-DB PFAL technique outperform with the percentage improvement of 65% for NOR gate and 7% for NAND gate and 34% for XNOR gate over the modified PFAL techniques at 10 MHz respectively.
Using recycled concrete aggregates (RCA) for pavements is crucial to achieving sustainability. Implementing RCA for new pavement can minimize carbon footprint, conserve natural resources, reduce harmful emissions, and lower life cycle costs. Compared to natural aggregate (NA), RCA pavement has fewer comprehensive studies and sustainability assessments.
KuberTENes Birthday Bash Guadalajara - K8sGPT first impressionsVictor Morales
K8sGPT is a tool that analyzes and diagnoses Kubernetes clusters. This presentation was used to share the requirements and dependencies to deploy K8sGPT in a local environment.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
CHINA’S GEO-ECONOMIC OUTREACH IN CENTRAL ASIAN COUNTRIES AND FUTURE PROSPECTjpsjournal1
The rivalry between prominent international actors for dominance over Central Asia's hydrocarbon
reserves and the ancient silk trade route, along with China's diplomatic endeavours in the area, has been
referred to as the "New Great Game." This research centres on the power struggle, considering
geopolitical, geostrategic, and geoeconomic variables. Topics including trade, political hegemony, oil
politics, and conventional and nontraditional security are all explored and explained by the researcher.
Using Mackinder's Heartland, Spykman Rimland, and Hegemonic Stability theories, examines China's role
in Central Asia. This study adheres to the empirical epistemological method and has taken care of
objectivity. This study analyze primary and secondary research documents critically to elaborate role of
china’s geo economic outreach in central Asian countries and its future prospect. China is thriving in trade,
pipeline politics, and winning states, according to this study, thanks to important instruments like the
Shanghai Cooperation Organisation and the Belt and Road Economic Initiative. According to this study,
China is seeing significant success in commerce, pipeline politics, and gaining influence on other
governments. This success may be attributed to the effective utilisation of key tools such as the Shanghai
Cooperation Organisation and the Belt and Road Economic Initiative.
Understanding Inductive Bias in Machine LearningSUTEJAS
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
A review on techniques and modelling methodologies used for checking electrom...nooriasukmaningtyas
The proper function of the integrated circuit (IC) in an inhibiting electromagnetic environment has always been a serious concern throughout the decades of revolution in the world of electronics, from disjunct devices to today’s integrated circuit technology, where billions of transistors are combined on a single chip. The automotive industry and smart vehicles in particular, are confronting design issues such as being prone to electromagnetic interference (EMI). Electronic control devices calculate incorrect outputs because of EMI and sensors give misleading values which can prove fatal in case of automotives. In this paper, the authors have non exhaustively tried to review research work concerned with the investigation of EMI in ICs and prediction of this EMI using various modelling methodologies and measurement setups.
2. Software Requirements Specification for WLMS Page ii
Table of Contents
Table of Contents.......................................................................................................................... ii
Revision History..........................................................................................................................iiii
Table of Contents......................................................................................................................... ii
Table of Contents.......................................................................................................................... v
1. Introduction..............................................................................................................................1
1.1 Purpose........................................................................................................................................... 1
1.2 Scope.............................................................................................................................................. 1
1.3 Intended Audience Definitions, acronyms and abbreviations......................................................... 1
1.3.1 Audience Definitions ..................................................................................................................... 1
1.3.2 Acronyms and abbrevaitions.......................................................................................................... 1
1.4 References...................................................................................................................................... 2
1.5 Overview........................................................................................................................................ 2
2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................ 2
2.2 Product Functions .......................................................................................................................... 2
2.2.1 Administrators................................................................................................................................ 2
2.2.2 Normal Users ( library members) ................................................................................................. 3
2.3 Operating Environment.................................................................................................................. 3
2.4 User Characteristics ....................................................................................................................... 3
2.5 Design and Implementation Constraints........................................................................................ 3
2.6 Assumptions and Dependencies .................................................................................................... 3
3. Specific Requirements .............................................................................................................4
3.1 Functional Requirements ............................................................................................................... 4
3.1.1 Librarian......................................................................................................................................... 4
3.1.2 Normal User................................................................................................................................... 5
3.1.3 Common Functions........................................................................................................................ 5
3.2 Non-Functional Requirements....................................................................................................... 6
3.2.1 Error Handling ............................................................................................................................... 6
3.2.2 Performance Requirements............................................................................................................ 6
3.2.3 Safety Requirements ...................................................................................................................... 6
3.2.4 Security Requirements................................................................................................................... 6
4. Interfaces and Possible Scenarios...........................................................................................7
4.1 Login Interface................................................................................................................................. 7
4.2 Registration Interface....................................................................................................................... 8
4.3 Personal Data Editing .................................................................................................................... 10
4.4 Search............................................................................................................................................. 11
4.5 Advanced Search ........................................................................................................................... 11
4.6 Book View..................................................................................................................................... 12
4.7 DVD View..................................................................................................................................... 12
4.8 Categories View............................................................................................................................. 13
4.9 Librarian’s Control Panel............................................................................................................... 13
4.10 Activating a User Account............................................................................................................. 14
4.11 Adding a Book............................................................................................................................... 15
4.12 Library Manager Control Panel ..................................................................................................... 15
4.13 Adding a Librarian......................................................................................................................... 16
5. Stored Items............................................................................................................................17
5.1 Member........................................................................................................................................... 17
5.2 Librarian.......................................................................................................................................... 18
5.3 Library Items................................................................................................................................... 18
5.4 Books, DVDs, Magazines and Journals ......................................................................................... 19
3. Software Requirements Specification for WLMS Page iii
Revision History
Name Date Reason For Changes Version
CE_ONB 8-3-2011 Upgrading the report to SRS 2.0
CE_ONB 15-3-2011 Upgrading the report to SRS 2.1
4. Software Requirements Specification for WLMS Page iv
LIST OF TABLES
Table 1 Attributes Saved About Member .......................................................17
Table 2 Attributes Saved About Librarians ....................................................18
Table 3 Attributes Saved About Library Items...............................................18
Table 4 Attributes Saved About Books...........................................................19
Table 5 Attributes Saved About DVD's..........................................................19
Table 6 Attributes Saved About Magazine.....................................................19
5. Software Requirements Specification for WLMS Page v
LIST OF FIGURES
Figure 1 Main menu ...........................................................................................7
Figure 2 Login error message.............................................................................7
Figure 3 Retrieve password form .......................................................................7
Figure 4 User registration form..........................................................................8
Figure 5 Server-Side Validation.........................................................................8
Figure 6 Client-Side Validation .........................................................................9
Figure 7 Personal data editing interface...........................................................10
Figure 8 Search interface..................................................................................11
Figure 9 Advaned search interface...................................................................11
Figure 10 View book interface...........................................................................12
Figure 11 DVD view interface...........................................................................12
Figure 12 Categories view..................................................................................13
Figure 13 Librarian’s control panel....................................................................14
Figure 14 Activating a user account interface....................................................14
Figure 15 Adding a book interface.....................................................................15
Figure 16 Library Manager Control Panel .........................................................15
Figure 17 Adding a Librarian interface...............................................................16
6. Software Requirements Specification for WLMS Page 1
1. Introduction
1.1 Purpose
The purpose of this document is to describe the Web Library Management System (WLMS)
product with the release number 0.1. This document contains the functional and non-functional
requirements of the project. This document contains the guidelines for website developers system
engineers and designers to start working the project.
1.2 Scope
WLMS product is basically updating the manual library system into a internet-based
application so that the users can know the details of their accounts, availability of books and
remaining time for borrowing.
The project is specifically designed for the use of librarians and library users. The product will work
as a complete user interface for library management process and library usage from ordinary users.
WLMS can be used by any existing or new library to manage its books and book borrowing,
insertion and monitoring .
WLMS can work as a powerful library management system for big libraries, and can provide a free
easy-to-use system for rising libraries.
1.3 Audience Definitions, Acronyms and Abbreviations
1.3.1 Audience Definitions
The intended readers of this document are the developers of the site, testers, library owners
and managers and coordinators.
Any suggested changes on the requirements listed on this document should be included in
the last version of it so it can be a reference to developing and validating teams.
1.3.2 Acronyms and Abbreviations
Acronym Meaning
WLMS Web Library Management System
MS SQL Microsoft Structured Query Language
ASP Active Server Pages
ISBN International Standard Book Number
DVD Digital Video Disc
IEEE Institute of Electrical and Electronics Engineers
7. Software Requirements Specification for WLMS Page 2
1.4 References
IEEE 830-1998 standard for writing SRS document.
I. Sommerville, Software Engineering, 8th
ed. England: Addison-Wesley, 2007.
1.5 Overview
Section 2 defines the general functions of WLMS, operating environment and user
constraints along with our assumptions.
Section 3 specifies functional and nonfunctional requirements; all of them are described to a
level of detail sufficient for designers to design a system.
Section 4 illustrates interfaces and its possible scenarios along with some screenshots to
make a general idea about the interfaces.
Section 5 specifies all stored information that we are concerned about for every entity in the
website .
2. Overall Description
2.1 Product Perspective
WLMS is a replacement for the ordinary library management systems which depend on
paper work for recording book and users’ information.
WLMS will provide an advanced book search mechanism and will make it easy to borrow,
insert and index a book in the library.
2.2 Product Functions
2.2.1 Administrators
Admin should be able to insert, modify and delete books.
Can accept or reject a new user according to the library policy or payment methods.
Increase the period for borrowing a book for specific type or group of users.
Can get the information (status report) of any member who has borrowed a book.
Add and edit book categories and arrange books by categories.
Add and edit authors and publishers information.
Can send lateness warnings to people who have exceeded deadline date.
Can record books returned by users.
8. Software Requirements Specification for WLMS Page 3
2.2.2 Normal Users (Library Members)
The member should be provided with the updated information about the books catalog.
Members are given a provision to check their account’s information and change it.
Members have the ability to search through books by subject, title, authors or any
information related to the book.
Can extend the period of borrowing books according to the library policy.
The customer may suggest a book to be brought to the library book collection.
2.3 Operating Environment
The WLMS is a website and shall operate in all famous browsers, for a model we are taking
Microsoft Internet Explorer versions 7.0, 8.0 and 9.0, with Flash Player 9 and JavaScript.
2.4 User Characteristics
Users of the website are members, librarians and the administrators who maintain the
website. Members and librarians are assumed to have basic knowledge of computers and Internet
browsing. Administrators of the system should have more knowledge of internal modules of the
system and are able to rectify small problems that may arise due to disk crashes, power failures and
other catastrophes. Friendly user interface, online help and user guide must be sufficient to educate
the users on how to use this product without any problems or difficulties.
2.5 Design and Implementation Constraints
The information of all users, books and libraries must be stored in a database that is
accessible by the website.
MS SQL Server will be used as SQL engine and database.
The Online Library System is running 24 hours a day.
Users may access WLMS from any computer that has Internet browsing capabilities and an
Internet connection.
Users must have their correct usernames and passwords to enter into their online accounts
and do actions.
2.6 Assumptions and Dependencies
The product needs the following third party products.
Microsoft SQL server to store the database.
ASP.net to develop the Product.
9. Software Requirements Specification for WLMS Page 4
The success of this system depends on
Existence of an Internet service to all people in Gaza Strip.
Are librarians and users comfortable with computers and have enough conation to work with
the product?
Website interface must be friendly and easy-to-use.
The search mechanism should be simple and fast.
3. Specific Requirements
3.1 Functional Requirements
3.1.1 Librarian
Prerequisite (admin signed in) for all requirements below
Requirement ID R1.01.01
Title insert book
Description This action is done to add new book to library book collection.
Priority 2
Requirement ID R1.01.02
Title delete / modify book
Description this event is to delete an existing book or modify its information.
Priority 2
Requirement ID R1.01.03
Title Validate user account
Description when a new member sign up then he should wait for acceptance by
Administrator according to library policies (e.g. fees required).
Priority 1
Requirement ID R1.01.04
Title delete member
Description Admin can delete a member due to some specific rules.
Priority 2
Requirement ID R1.01.05
Title modify member rank
Description Admin can extend the borrowing time or number of book borrowed
simultaneity to a user.
Priority 2
10. Software Requirements Specification for WLMS Page 5
Requirement ID R1.01.06
Title return book
Description Admin should confirm the return of books borrowed by users.
Priority 1
3.1.2 Normal User
Requirement ID R1.02.01
Title register
Description when new user enters WLMS for the first time then he has to register
Priority 3
Requirement ID R1.02.02
Title extending borrowing deadline.
Description member can extend the borrowing time to some limit decided by Admin
Priority 2
Requirement ID R1.02.03
Title reset password
Description when a member forgets his password he can claim it back via e-mail.
Priority 1
Requirement ID R1.02.04
Title edit personal information
Description if some user changes for example his mobile number, he can modify it.
Priority 2
Requirement ID R1.02.05
Title reset password
Description when a member forgets his password he can claim it back via e-mail.
Priority 1
3.1.3 Common Functions
Requirement ID R1.03.01
Title login
Description both Admin and members must be logged in before they modify any
information
Priority 1
Requirement ID R1.03.02
Title search for book
Description when user or admin wants to search on some book by name, author or
subject etc.
Priority 1
11. Software Requirements Specification for WLMS Page 6
3.2 Non-functional Requirements
3.2.1 Error handling
WLMS product shall handle expected and non-expected errors in ways that prevent loss in
information and long downtime period.
3.2.2 Performance Requirements
The system shall accommodate high number of books and users without any fault.
Responses to view information shall take no longer than 5 seconds to appear on the screen.
3.2.3 Safety Requirements
System use shall not cause any harm to human users.
3.2.4 Security Requirements
System will use secured database
Normal users can just read information but they cannot edit or modify anything except their
personal and some other information.
System will have different types of users and every user has access constraints.
12. Software Requirements Specification for WLMS Page 7
4. Interfaces and Possible Scenarios
4.1 Login Interface
In case the user is not registered yet, he can enter the registration form after clicking on
""تسجيم link as shown in Figure 4.
Figure 1: Main menu
We can see " تسجيمدخول " pannel in the main page in
Figure 1 which asks the user to type his username and password
then click "."دخول If the user entered either his username or
password incorrectly then an error message shown in Figure 2
will be shown.
Figure 3: Retrieve password form
Another possible scenario that an already-registered
Member has forgotten his password then he can click on " فقدت
كهمةانمرور " and this will lead him to password recovery page
shown in Figure 3 so he can enter his e-mail and the password
will be sent instantly to him via e-mail.
Figure 2: Login error message
13. Software Requirements Specification for WLMS Page 8
4.2 Registration Interface
When the button ""تسجيم is clicked, the server will check if the username or email is already taken
and alert the user as shown in Figure 5
If the user who is trying to register is already a member with the same username he can click
on "هنا اضغط " to move to login page.
Figure 4: User registration form
After the guest reads " وضوابط "شروط
and agrees it he can continue with
registration operation by entering his
name, password, e-mail, address, mobile,
telephone and personal photo.
When the user finishes entering the
required fields, he should click ""تسجيم to
be a member of the library.
Users will be warned about any
mistakes on data format or any other
constrains by validation notes and error
messages. Figures below show some of
these mistakes with their correction
examples.
Figure 5: Server-Side Validation
14. Software Requirements Specification for WLMS Page 9
There are some errors that will be shown instantly to users and do not require the server
response after ""تسجيم is clicked. Figure 6 shows these errors.
Validation fields are used to check if passwords entered are identical and it is also used to
check if the e-mails are identical.
The Registration form also checks for the entered mobile and telephone and view an
example to help the user to enter date in the correct form.
Figure 6: Client-Side Validation
15. Software Requirements Specification for WLMS Page 10
4.3 Personal Data Editing
If any member wants to change his personal information he can enter his profile by
clicking on his name at the top right of the main page and he will be directed to page shown
in Figure 7.
Member should enter his old password to verify that he owns the current account then he
can edit his personal information.
The form is similar to the registration form since same validation was used here. After the
member edits his information he should click ""حفظ otherwise his changes will be discarded. In case
the user does not want to continue editing his information, he can click on " إنغاء " button to abort the
page.
Figure 7: Personal data editing interface
16. Software Requirements Specification for WLMS Page 11
4.4 Search
4.5 Advanced Search
In advanced search user can perform search operation in more specific criteria, as shown in
Figure 9, user can search by “انموضوع”“ ,فّانمؤن”“ ,انعنوان” and/or other criteria. And he can select
search in “انكتب”“ ,انمجالت”“ ,انصحف”, and/or “األقراصانمدمجة” .
The user can roughly select the language of his search contents and how to display the
results by two options which are sorting the results and number of results per page.
Finally he can specify the date of the contents he wants to find by determining start and end dates.
Figure 8: Search interface
Figure 8 shows the search
form.
In the form member or
librarian can enter the type of media
he is looking for and the title he is
interested in them he can click on
"بحث ". User can also use advanced
search for more options.
17. Software Requirements Specification for WLMS Page 12
4.6 Book View
When a Liberian or a member wants to view some book from search results or
directly vie some link, the page on Figure 10 shall be shown to him.
As shown in Figure 9, a lot of useful information about the book will be displayed so the
user can decide whether this book can be helpful to him or not. This information includes the
publication year, publisher, edition, and number of pages, ISBN, table of contents, cover photo and
description, from that page the Liberian can edit or delete the book and an active member can
borrow it if there is enough number of copies.
4.7 DVD View
Simple information will be shown about the DVDs including its length, type, and available
copies. See Figure 11.
Figure 10: View book interface
Figure11 : DVD view interface
18. Software Requirements Specification for WLMS Page 13
4.8 Categories view
Figure 12 shows the books categories view with ability to Liberian to add/edit or delete a
category from the list; the same view for DVDs, journals and magazines.
4.9 Librarian’s Control Panel
This control panel will allow librarians to add, confirm, or remove users; add, edit, or
remove a medium. And manage lending options. See Figure 13.
Figure 12 : Categories view
19. Software Requirements Specification for WLMS Page 14
4.10 Activating a User Account
A librarian must activate the new user account before user can borrow.
Librarian can check user info and edit them as will, before he activates the account. See
Figure 14.
Figure 13 : Librarian’s control panel
Figure 14 : Activating a user account interface
20. Software Requirements Specification for WLMS Page 15
4.11 Adding A book
Librarian can add a book using form shown in Figure 15, all required fields are validated
automatically, and results the error messages shown in red.
4.12 Library Manager Control Panel
This control panel will allow Library manager to add, edit, view, or remove librarians; as an
addition to all what librarian can do. See Figure 16.
Figure 16: Library Manager Control Panel
Figure 15: Adding a book interface
21. Software Requirements Specification for WLMS Page 16
4.13 Adding a Librarian:
Library manager can add employees using form shown in figure 17, all required fields are validated
automatically, and results the error messages shown in red.
Figure17: Adding a Librarian interface
22. Software Requirements Specification for WLMS Page 17
5. Stored Items
In this section we will list all stored information about every entity in WLMS system.
5.1 Member
All important data related to the user will be stored in a database. Table 1 shows this data
with its constraints.
Item Type Constraints / notes
Name String
Maximum 40 char , should include first name, middle
name and last name.
ID Number This is a unique ID in the database.
Email String
Should be valid e-mail address with the formula
xx@yy.zz
Telephone String
Should not contain any letters and should be in full
form with detailed prefix. For example 00790-08-
2884665.
Address String
Accurate address containing city, street and house
number.
Birth date Date Under the formula : 19-08-1989.
Rank Number
As the rank goes higher as the user get more
privileges. By rank librarians can divide members
into groups with different proprieties.
Mobile String
Should not contain any letters and should be in full
form with detailed prefix. For example 00790-599-
852840.
Date registered Date Under the formula : 19-08-1989.
Membership status String
Include : {OK, Suspended, Expired, Waiting for
validation}
Borrowed books String The list of borrowed books and DVDs.
Late warnings Number
How many times this member was warned about
lateness?
User name String Registered username.
Password String Password.
Maximum books Number
Maximum number of books that can be borrowed
together.
Personal photo Photo Personal photo of the member.
Table 1: Attributes saved about member
23. Software Requirements Specification for WLMS Page 18
5.2 Librarian
Table 2 below illustrate the main attributes stored about librarians.
Item Type Constraints / notes
Name String
Maximum 40 char , should include first name,
middle name and last name.
ID Number This is a unique ID in the database.
Email String
Should be valid e-mail address with the formula
xx@yy.zz
Telephone String
Should not contain any letters and should be in full
form with detailed prefix. For example 00790-08-
2884665.
Address String
Accurate address containing city, street and house
number.
Birth date Date Under the formula : 19-08-1989.
Mobile String
Should not contain any letters and should be in full
form with detailed prefix. For example 00790-599-
852840.
Date hired Date Under the formula : 19-08-1989.
Hours of work number
Indicates how many hours this librarian works per
week.
Salary money Salary per month for a librarian.
User name String Registered username.
Password String Password.
Personal photo Photo Personal photo of the member.
ID String The identity number of the librarian.
Table 2: Attributes saved about librarians
5.3 Library Items
Table 3 includes common attributes that will be stored for every library item (book, DVD
etc.)
Item Type Constraints / notes
Type String book, magazine, lecture, notes, DVD.
Title String Title of the item in clear words.
Language
2 chars
First two letters of the book language for example :
AR, EN.
Table 3: Attributes saved about library Items
24. Software Requirements Specification for WLMS Page 19
5.4 Books, DVDs and Magazines
Table 4 below clarifies the major properties that will be stored for every book in WLMS.
Item Type Constraints / notes
ISBN String A unique numeric commercial book identifier.
Authors String Names of authors.
Edition Number No letters are allowed.
Publisher String Publisher name.
Cover page photo Photo Must be clear and colored.
Field String Entertainment, science etc.
Number of copies Number Copies available for the same book.
Year Date Date in this format 1999.
Number of pages Number No letters are allowed.
Status String Available, lost, damaged.
Chapters names String Main chapter names.
Table 4: Attributes saved about books
Table 5 illustrates the attributes saved about DVD's
Item Type Constraints / notes
Duration Time Minuets.
Number of copies Number Copies available for the same DVD.
Content type String Indicates type of files burned on this disk.
Type String CD / DVD / Blue Ray
Table 5: Attributes saved about DVD's
Table 6 illustrates the attributes saved about Magazine
Item Type Constraints / notes
Website String URL to the main webpage of the magazine.
Number of copies Number Copies available.
Date Date Date for this magazine.
Table 6: Attributes saved about Magazine