SOFTWARE ENGINEERING LAB

Roll No. Student Name Class / Section Email Id

18881A05K8 DHARMARAJULA AJAY CSE-D ajaydr16@gmail.com
18881A05L8 KARRA VASHIST REDDY CSE-D varunkarra4@gmail.com
19885A0519 MANGA SANJAYKANTH CSE-D sanjaykanth4646@gmail.com
19885A0523 VASKUL MAHESH JAIN CSE-D maheshjain3636@gmail.com

Case Study

“E-BOOK MANAGEMENT “
Structural and Behavioral Diagrams
Description:

EBook process is well organized online buying and selling of books. This system is well developed in
various resources, for example Amazon site deals more about e-booking concept. This process has
various issues in the basics of maintenance of database and updating in sites, and virus problem in pdf
books, so we have many issues in this process. The process of e-books is fully based on online, and the
process for this mainly interaction between buyer and seller, buyer who enter the site for purchase of
book will use search engine for book to purchase, the search engine will mainly focused on the database
process, it used to search book for the buyer who mentioned the book name, author name, edition,
publication details in the site, so that the search engine will show many books. There will be a payment
option and option for pdf file or hardcopy delivery to home, the user should decide whether he want
which one. Whether he choice hardcopy means, full detail address, driving license no, and then he
should login with his username and password, and then payment through atm debit or credit card
applicable.

(II) SOFTWARE RESOURCE SPECIFICATION:

1.0 INTRODUCTION
E-Book is the interface between the students and Librarian. It aims at improving the efficiency in
the Issue of books or magazines and reduces the complexities involved in it to the maximum
possible extent. 1.1 PURPOSE If the entire process of 'Issue of Books or Magazines' is done in a
manual manner then it would take several months for the books or magazines to reach the
applicant. Considering the fact that the number of students for Book Bank is increasing every year,
an Automated System becomes essential to meet the demand. So this system uses several
programming and database techniques to elucidate the work involved in this process. The system
has been carefully verified and validated in order to satisfy it.

1.2 SCOPE
Page 1 of 10
The System provides an online interface to the user where they can fill in their personal details and
submit the necessary documents (may be by scanning). The authority concerned with the issue of books
can use this system to reduce his workload.

1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

 E-book manager

Refers to the super user who is the Central Authority who has been vested with the privilege to manage
the entire system.

 User

One who wishes to obtain the Books or Magazines.

 Visitor

One who visits to obtain Books or Magazines.

 Administrator

One who manages and maintain Books or Magazines

USER CHARACTERISTICS

User: They are the people who desire to obtain the books and submit the information to the database.
Visitor: They are the person who visits the E-book system

Administrator: He has the certain privileges to add the books and to approval of the reservation of
books.

Page 2 of 10
Class Diagram:

The class diagram, also referred to as object modeling is the main static analysis diagram. The main task
of object modeling is to graphically show what each object will do in the problem domain. The problem
domain describes the structure and the relationships among objects.

List of Classes:

The E-book Management system class diagram consists of five classes:

1. Login

2. Registered User

3. Administrator

4. Book

5. Visitor

6. download

7. Logout

Relationships used:

1) Login: Login to the system

2) Registered User: It consists of six attributes and four operations. The attributes are user id, name,
password, email id, phone no, security question. The operations of this class are download(),
login(),search(),register().

3) Administrator: It consists of four attributes and two operations. The attributes are name, password,
email id, admin id. The operations of this class are update(), record()

4) Book: It consists of four attributes and two operations. The attributes are book id, book name, author,
and price. The operations of this class are update(), add().

5) Visitor: It consists of two attributes and two operations. The attributes are user name, email id. The
operations of this class are search book(), read book().

6) Download: It consists of two attributes and two operations. The attributes are user id, book id, date,
and amount. The operations of this class are search download ().

7) Logout: Logout from the system.

Page 3 of 10
Class Diagram:

Page 4 of 10
Use Case Diagram:

List of Use Cases:

The E-book use cases in our system are:

1. Login

2. Register

3. Search book

4. Download

5. Payment

6. Publisher

7. Update

Relationships:

1. Add: a student record. Each student should have following attributes.

-> Student id

->Name

->Address

->Phone no

2. Update: The record would be selected using the student id. The updates can be made on full
items only.
->name
->address
->phone no
3. Add to book item: Each book should have following attribute
->call no
->title
->ISBN
->Author name

Page 5 of 10
 4. Query the book database: The product shall let librarian query tools books detail information by
their ISBN number (or) author (or) title. The search result would produce a list of books, which
match the search parameters.
5. Check out a book: Librarians and member of the library can check out can be initialized from a
previous search operation where user has selected a set of books.
6. Check in a book: Librarians and member of the library can check in a book using its call no.

Use Case Diagram:

Page 6 of 10
Sequence Diagram:

 A sequence diagram represents the sequence and interactions of a given USE-CASE or scenario.
Sequence diagrams can capture most of the information about the system. Most object to
object interactions and operations are considered events and events include signals, inputs,
decisions, interrupts, transitions and actions to or from users or external devices. An event also
is considered to be any action by an object that sends information

 The event line represents a message sent from one object to another, in which the “form”
object is requesting an operation be performed by the “to” object. The “to” object performs the
operation using a method that the class contains.

 It is also represented by the order in which things occur and how the objects in the system
send message to one another.

 The two sequence diagram and two collaboration diagram one for Registered user and
another for visitor are given below

1.Sequence Diagram For Registered User.

Page 7 of 10
Activity Diagram:

The activity diagram shows the activity of the process here first login is done when the user is valid then
the welcome page appears .Here fork is used where two transaction line may be got search book and
online reading .search book can be used to search book and online reading can allow user to learn
online and when any of these two process is selected a join is used where download occurs, in this
download of book is done then finally cost of book is paid online:

Page 8 of 10
DEPLOYMENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed.

Page 9 of 10
STATE CHART DIAGRAM:

The diagrams show first login to the system and view the books and search for required book is done
and then required book is downloaded and amount paid in online .Finally logout from the system.

Page 10 of 10
Page 11 of 10