Site Loader

CHAPTER 1 – INTRODUCTION
1.1 ORGANIZATION PROFILE
Shankersinh Vaghela Bapu Institute of Technology (SVBIT) is situated in Gandhinagar in Gujarat state of India. Established in 2009 with the approval of AICTE and affiliated to Gujarat technological University (GTU), offering five courses in Bachelor of Engineering, with a total annual intake of 540. The college is located at Gandhinagar – Mansa road, on 7 km from Gandhinagar, in a sprawling 40 acre lush green campus. BGKV proudly launches second edition of “SPANDAN” a wall magazine, a unique identity of BGKV essential colleges, which gives platform to technical students to find out the ability hide from view in them.
SVBIT, with a view to provide opportunity to the aspirants, especially in Gujarat for their guidance in technical education and to make available consultancy and testing amenities to the industries/organizations situated in this area and to connect hands with Govt. of India in creation of industrial man authority. For the accomplishment of this noble task, the collage has been making consistent efforts with the help of innovative and dedicated faculty, technical and non-technical staff members and the students for the growth and progress. The collage provides an environment which is not only pollution free but is also immensely suited for the holistic growth and the expansion of the students.
1.2 PROJECT DETAIL
1.2.1 PROJECT DEFINITION
Periodic management system is the managing system of journals and magazines. It maintains the database of exporting and importing of journals and magazines. This management will easily manage the volumes of journals with their particular year.
1.2.2 PROJECT PROFILE
? This website be able to facilitate Librarian, Agent, Vendor, Admin as well as Supplier toward view that is exporting and importing of journals and magazines.
? This website can provide a platform for order the journals and manage the journals. They are complete info concerning about journals.
? The activities involved through this project are analysis of the project, designing of the project, coding, testing and deployment of project.
? Approximately 6-7 month is required to develop this website along with testing. After that it is ready to release in the PHP market . For being an PHP website development cost is negligible.

1.3 SCOPE OF THE PROJECT
PMS website is comprehensive PHP based website. Which is highly needed according to current digital technology generation. It will design for better interaction between Admin, Vendor, Supplier and Librarian.
This system is easy to understand and manage so incase changing of any Librarian , new Librarian will be able to whole system.
1.5 OBJECTIVE

1.6 TECHNOLOGY & LITERATURE REVIEW
TECHNOLOGY
? Wamp
? MySQL:
Server version: 5.1.53
? Apache:
Server version: 2.2.17
LITERATURE REVIEW

CHAPTER 2 – ABOUT THE SYSTEM
2.1 SOFTWARE REQUIREMENT SPECIFICATION
2.1.1 OVERALL DESCRIPTION
Describe the general factors that affect the product and its requirements. This section doesn’t state specific requirements.
PRODUCT PERSPECTIVE
In This system Regular journals will be generated in our application so though librarians can have a review of number of periods going on.
PRODUCT FEATURE
? Regular updates for journals
? Set of journals by year
? Manage the database
? Reminder to binder
USER CLASSES AND CHARACTERISTICS
This software is user friendly. Only general and basic computer knowledge mandatory to operate this software.
ADMIN
Admin will handle all the activity and can add new features to the system.
VENDOR
Vendor will get request from user for journals and will provide journals to them via supplier.
AGENT
Agent will get request from user for journals and will respond if they have journals available if not then they will contact to vendor for the specified journals and after that agent will provide it to user.
SUPPLIER
Supplier will supply journals to specified user by vendor and get payment from user.

OPERATING ENVIRONMENT
? Front End
? HTML
? CSS
? PHP
? Back End
? Apache
? MySQL
DESIGN AND IMPLEMENTATION CONSTRAINTS
Wamp
MySQL:
Server version: 5.1.53
Apache:
Server version: 2.2.17
ASSUMPTION AND DEPENDENCY
It is assumed that the user machine will contain proper operation system in order to run the system.
? Database is made of MYSQL, which provides strong protected database management.
? User must have an Internet Connection.
SYSTEM FEATURES
This section describes the functionality and modules with their description of our definition.
? All modules have different login id and password.
? website is available 24 hours.

EXTERNAL INTERFACE REQUIMENTS
USER INTERFACE
? User friendly website.
? WAMP or XAMP is required.
? Mysql is used for server side.
HARDWARE INTERFACE
There are no hardware interfaces to this software system. The only interfaces are through a mobile and computer.
SOFTWARE INTERFACE
As per our system, user will require WAMP/XAMP server and Notepad++.
COMMUNICATION INTERFACE
2.1.1 FUNCTION REQUIREMT
This subsection presents the indentified functional requirements for the subject PMS. Initially, general requirements the pertain to the whole system are given. Where possible, subsequent requirements have been demarcated on their relevance to the system, that is admin, librarian, vendor, agent, supplier.
ADMIN
Admin will handle all the activity and can add new features to the system.
LIBRARIAN
Librarian will request for journals to vendor or agent and will provide details of journals.
VENDOR
Vendor will get request from user for journals and will provide journals to them via supplier.
AGENT
Agent will get request from user for journals and will respond if they have journals available if not then they will contact to vendor for the specified journals and after that agent will provide it to user.
SUPPLIER
Supplier will supply journals to specified user by vendor and get payment from user.
2.1.2 NON-FUNCTION REQUIREMT
PERFORMANCE REQUIREMENTS
? It’s important to login into network for the network admin.
? The system is expected to have reasonable short time response.
SAFETY REQUIREMENTS
? Admin login
? Two way verification
SECURITY REQUIMENTS
? The main concern regarding security is that no unauthorized user should be able to access the page.
? For this system will generate id and password for the all modules for secured login.
SOFTWARE QUALITY ATTRIBUTES
? Consistent in performance
? Safe and Secure
? Robust
? Scalable
? Flexible
? User friendly
? Efficient
? Upgradable
? Available in the time
2.2 PROJECT PLANNING
? Project planning is an part of Project Management that focuses a lot on Project Integration. The project plan reflects the current status of all project activities and is used to monitor and control the project. The Project Planning tasks ensure that various elements of the Project are coordinated and therefore guide the project implementation. Project Planning helps in
? Facilitating communication
? Monitoring and measuring the project progress, and
? planning decisions
? The Project Planning Phases can be broadly classified as follows:
? Development of the Project Plan
? Execution of the Project Plan
? Testing of Project
? Final Deployment of Project

?

CHAPTER 3 – ANALYSIS
3.1 E-R DIAGRAM
An entity-relationship diagram (ERD) is a data modeling techniques that graphically illustrates an information system’s entities and the relationships between those entities.
The elements of an ERD are:
? Entities
? Relationships
? Attributes

Table 3(1) : Symbols for ER diagram

Figure 3(a) ER diagram

3.2 DATA FLOW DIAGRAM
A data flow diagram (DFD) shows the functional relationship of values computed by a system, including input values, and internal data stores. A data flow diagram is a graph showing flow of data values from their source in objects throughout process that change them to their destinations in other objects. A data flow doesn’t show control information, such as the time at which the process is executed or decision among the alternative data paths.
Level 0 :

Figure 3(b) DFD Level 0

Level 1 :

Figure 3(c) DFD Level 1

Level 2 :

Figure 3(d) DFD Level 2

Level 3 :

Figure 3(e) DFD Level 3
Level 4 :

Figure 3(f) DFD Level 4
Level 5:

Figure 3(g) DFD Level 5

3.3 CLASS DIAGRAM
A class diagram is nothing but the static structure diagram that describes the structure of a system with the help of the system’s classes, their attributes, method, and the relationships among the objects. Relationship between object can be one to many, many to one, one to one and many to many. Class diagram has another major two type of relationship, one is aggregation and another is composition. When we are showing aggregation relation between two entities that means they are not fully depended on each other. But when we give composition relation between two entities that means they are fully depended.

Figure 3(h) Class diagram

3.4 STATE DIAGRAM
A state diagram is a type of diagram used in computer science and correlated fields to explain the behavior of systems. State diagram require that the system described is collected of a reasonable abstention. Many forms of state diagrams exist, which differ slightly and have different semantics.

Figure 3(i) State diagram
3.5 USE CASE DIAGRAM
To introduce use case diagrams two things to remember are Actors and Use Cases. An actor is anyone or anything that must interact with the system, actors are not part of the system. In the UML, an actor is represented as a stickmen. A use case must deliver something of value to an actor. The collection of use cases for a system constitutes all the defined ways the system may be used. A use case diagram is a diagram that shows a set of use cases and actors and their relations. Use case diagrams are used to model the context and requirment of a system.

Figure 3(j) Librarian – Agent Use case diagram

Figure 3(k) Librarian – Vendor/Supplier Use case diagram

3.6 SEQUENCE DIAGRAM
A Sequence diagram is an interaction diagram that shows how processes work with one a different and in what order. It is a construct of a Message Sequence Chart. A sequence diagram shows object contacts arranged in time sequence. It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario.

Figure 3(l) Librarian Sequence diagram

Figure 3(l) Vendor Sequence diagram

Figure 3(m) Agent Sequence diagram

Figure 3(n) Admin Sequence diagram
3.7 ACTIVITY DIAGRAM
Activity diagrams are normally used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the details logic of business rule.

Figure 3(o) Librarian Activity diagram

Figure 3(p) Admin Activity diagram

Figure 3(q) Agent Activity diagram

Figure 3(r) Vendor Activity diagram

CHAPTER 4 – DESIGN
4.1 SYSTEM FLOW DIAGRAM
In our Librarian , vendor , agent or Admin can login with their id and password and then system check the database and identify the user type it is admin or other modules then login. If the admin is login it have different permission and other modules have different permission admin can manage and update all data user can update few data and view all data of PMS then finally admin and other modules can logout from this website.

Figure 4(a) System Flow diagram
4.2 DATA DICTIONARY
4.2.1 LIBRARIAN
Table 4(1) : Title

Table 4 (2) : Title Entry

Table 4(3) : New Request

Table 4(4) : Select for Approval

Table 4(5) : Approval Process

Table 4(6) : Re- Approval Process

Table 4(7) : Oder Process

Table 4(8) : Order Cancellation

Table 4(9) : Invoice Process

Table 4(10) : Payment Process

Table 4(11) : Refund Process

Table 4(12) : Non Received Issues

Table 4(13) : Check-in Details

Table 4(14) : Process Of Received Issues

Table 4(15) : Oder Process

Table 4(16) : Receiving

Table 4(17) : Binding – Invoice Process

Table 4(18) : Payment

Table 4(19) : Preparation Of Sets

Table 4(20) : Receiving

4.2.2 VENDOR
Table 4(21) : Login

Table 4(22) : Registration

Table 4(23) : Delivery

Table 4(24) : Frequency Master

Table 4(25) : Binding Type

Table 4(26) : Edition Master

4.2.3 ADMIN
Table 4(27) : Admin Login

4.2.4 AGENT
Table 4(28) : Agent

4.2.5 SUPPLIER
Table 4(29) : Supplier

4.3 RELATIONSHIP TABLE
Table 4 (30) : relationship table
SR No To Relation With
1 Librarian Logs In Login
2 Admin Logs In Login
3 Agent Logs In Login
4 Vendor Logs In Login
5 Supplier Logs In Login
6 Librarian View Info Journal
7 Librarian Request for journal Vendor
8 Librarian Request for journal Agent
9 Agent Provide Journal Librarian
10 Vendor Provide Journal Librarian
11 Vendor Provide Journal to Agent Librarian
12 Supplier Provide Journal to Librarian
4.4 USER INTERFACE
? As soon as librarian open the website main login screen will appear.
? Once librarian pass through login page there will be option like suggestion, subscription, payment, check-in, commercial binding etc.
? Then update information if they want to update.
? Then logout from website.

CHAPTER 5 – IMPLEMENTATION
5.1 IMPLEMENTATION ENVIRONMENT
It is deployed on PHP so the software is platform dependent. All the functions are developed in Wamp (MySQL: Server version: 5.1.53, Apache:Server version: 2.2.17).
Implementation Planning
? Implementation section needs precise designing and observance mechanism in order to make sure schedule and completeness.
? We’ll develop the website in numerous sub-phases in Implementation section.
Module Implementation
? This level of subsystem involves implementation of assorted modules of our project.
5.2 SECURITY FEATURE

CHAPTER 6 – CONCLUSION & FUTURE WORK
6.1 CONCLUSION

REFERENCES
1 Mr. Nitin Padriya – SVBIT
2 Ms. Gita Zala – Librarian SVBIT
3 MARC 21
4 ISO 2709 Standard
Websites
5https://patents.google.com/patent/US20040243920A1/en?q=journal&q=managment&q=system&oq=journal+managment+system
6 https://patentimages.storage.googleapis.com/f7/0e/9a/58d9c2e82d8cd5/JP2012003680A.pdf
7https://patents.google.com/patent/WO2013008327A1/en?q=journal&q=managment&q=system&oq=journal+managment+system&page=3
8https://patents.google.com/patent/US20140337562A1/en?q=journal&q=managment&q=system&oq=journal+managment+system&page=3
9https://patentimages.storage.googleapis.com/c3/bd/97/9e7fd51effc52f/US20060101085A1.pdf

Post Author: admin