JAHANGIRABAD INSTITUTE OF TECHNOLOGY

Department of Computer science and engineering

Dr. A.P.J. Abdul Kalam Technical University, Lucknow

LAB MANUAL

Subject Code: KCS-551

Subject Name: SOFTWARE ENGINEERING

1
 INDEX
S. No List of Experiments Page No.
1 Figure 1.Use case diagram for Book Bank System 6
2 Figure2. Activity Diagram for Book Bank System[borrow book] 7
3 Figure3.Activity Diagram for Book Bank System[order book] 8
4 Figure4. Activity Diagram for Book Bank System[Return book] 9
5 Figure5.SequenceDiagramForBookIssue&Return 10
6 Figure6. Collaboration Diagram For Book Issue & Return 11
7 Figure7.Class Diagram For Book Bank System 12
8 Figure 8.StateChartDiagramforBookBankSystem 13
9 Figure9: Deployment Diagram for Book Bank System 13
10 Develop test cases for unit testing and integration testing 14

Develop test cases for various white box and black box
testing techniques

2
Problem Statement: A Book Bank lends books and magazines to member, who is registered in the system.
Also it handles the purchase of new titles for the Book Bank. Popular titles are brought into multiple copies. Old
books and magazines are removed when they are out or date or poor in condition. A member can reserve a book
or magazine that is not currently available in the book bank, so that when it is returned or purchased by the book
bank, that person is notified. The book bank can easily create, replace and delete information about the tiles,
members, loans and reservations from the system.
Preparation of Software Requirement Specification Document:
Users Characteristics:
Student: They are the people who desire to obtain the books and submit the information to the database.
Librarian: He has the certain privileges to add the books and to approval of the reservation of books.
System Modules:
Login: Secure registration of student and librarian by filling online registration form.
Book bank: Book bank contains all the books. New book added to the book bank with book no, title
name, author, edition, publisher name details to the database. Any book is deleted if damaged.Update of
the book information also done.
Operations: student and administrator perform their operations like add book, delete book, update information,
view book details are implemented in log in WebPages.
Non-functional requirements:
Privacy: privacy maintained for each and every user by providing user credentials user name and password.
Portability: installation on multiple platforms and execution of software.

Preparation of Software Configuration Management

Software Requirements:
Operating sytem:
windows7/10 Front end :
J2EE
Backend : MySQL Server
IDE used : StarUML

Hardware Requirements:
Processor: i3orhigher RAM : 4 GB
Hard Disk drive :
500GB

Study and usage of any Design phase CASE tool

CASE Tool: STARUML

How to Install Star UML on Windows10

Star UML is a UML (Unified Modeling Language) tool, introduce by MK Lab. It is an open-source modeling
tool that supports the UML framework for system and software modeling. Star UML is based on UML version
1.4, it provides 11 different types of diagram and it accepts UML2.0 notation. Version 2.0 was released for
beta testing under a property license.
Star UML is actively supporting the MDA (Model Driven Architecture). It approaches by supporting the UML
profile concept and allowing it to generate code for multiple languages. It also provides a number of bug fixes
and improved compatibility with the modern versions of the Windows Operating System.
3
Star UML is mostly used by the Agile and small development teams, professional persons and used by the
educational institutes

4
Diagram Types in Star UML

1. Use Case Diagram

2. Class Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. State chart Diagram
6. Component Diagram
7. Deployment Diagram
8. Composite Structure Diagram

Features of Star UML

It supports multi-platforms Mac OS, Windows, and Linux.

It involves UML2.x.standardcompliant.

Includes Entity-Relationship diagram (ERD), Data-flow diagram (DFD), and Flowchart diagram.
It creates multiple windows.

It has modern UX and dark and light themes.

Featured with retina(High-DPI) display

support. Includes model-driven development.

It has open APIs.

Supports various third-party

extensions. Asynchronous model

validation.

It can export to HTML docs.

Steps to Download and Install Star UML

Step 1: Go on the browser, type in the URL “StarUML”

Step2: Click on the very first search “Download StarUML”.
Step3: There will be 3 Operating Systems(OS) options, click on the option as per the devise OS.
Step4: Now, right-click on the downloaded file, select “Show in Folder” option.
Step5: Click on the open file, a popup window opens, click on the “Yes” button.
Step 6: Installation gets start. After installation popup opens to ask to buy a license. If you want to click on the
“Buy Now” button or else close that window. Star UML is ready to use.

5
Performing the Design by using any Design phase CASE tools CASE Tool: Star UML

6
Use Case Diagram:
The book bank use cases are:
book_issue
book_return
book_order
book_entry
searchbook_details

Actors Involved:
Student
Librarian
Vendor

Use case Name: SearchBook_Details

The librarian initiates this use case when any member returns or request the book and check in gif the book is
available.

Precondition: The librarian should enter all Book details.

Normal Flow: Build message for librarian whose arch the book.

Post Condition: Send message to respective member who reserved the book.

Use case Name: Book_Issue

Initiatedbylibrarianwhenanymemberwantstoborrowthedesiredbook.Ifthebookisavailable, the book is issued.

Precondition: Member should be valid member of library.

Normal Flow: Selected book will be issued to the member.

Alternative Flow: If book is not available then reserved book use case should be initiate.

Post Condition: Update the catalogue.

Use case Name: Book_Order

Initiated by librarian when the requested book is not available in the library at that moment. The book is
reserved for the future and issued to the person when it is available.

Precondition: Initiated only when book is not available.

Normal Flow: It reserved the book if requested.

Post Condition: Mention the entry in catalogue for reservation.

Use case Name: Book_Return

Invoked by the librarian when a member returns the book.

Precondition: Member should be valid member of library.

7
Normal Flow: Librarian enters book id and system checks for return date of the book.

Alternative Flow: System checks for return date and if it returned late fine message will be displayed.

Post Condition: Check the status of reservation.

Use case Name: Book_Entry

The purchase book use-case when new books invoke it or magazines are added to the library.

Precondition: Not available or more copies are required.

Normal Flow: Enter book id, author information, publication information, purchased date, prize and number of
copies.

Post Condition: Update the information in catalogue.

Figure 1.Use case diagram for Book Bank System

Activity Diagram:
Activity diagrams are graphical representations of work flows of step wise activities and actions with

8
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams can be used
to describe the business and operational step-by-step work flows of components in a system. An activity
diagram shows the overall flow of control. An activity is shown as an rounded box containing the name of the
operation. This activity diagram describes the behavior of the system.

Figure2. Activity Diagram for Book Bank System[borrow book]

9
Figure3.Activity Diagram for Book Bank System[order book]

10
 Figure4. Activity Diagram for Book Bank System[Return book]

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 systems end message to one
another.

11
Figure5.SequenceDiagramForBookIssue&Return

12
 Figure6. Collaboration Diagram For Book Issue & Return

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.
The ATM system class diagram consists of four classes:
Student
Book
Issue
Return
Vendor
Details

Student:
It consists of twelve attributes and three operations. The attributes are enroll no, name, DOB, father name,
address, dept name, batch and book limits. The operations of this class are add StInfo(), delete StInfo(), modify
StInfo().
13
Book:
It consists of ten attributes and four operations. This class is used to keep book information such as author, title,
vendor, price, etc

Issue:
It consists of eight attributes and two operations to maintain issue details such as, issue date, acc no of issued
book, name of the student who borrowed book.

Return:
It consists of eight attributes and two operations to maintain issue details such as, issue date, acc no of issued
book, name of the student who borrowed book.

Vendor:
The attributes of this class are name, dept , year , bcode no The operation is display students().

Detail:
The attributes of this class are book name, author, bcode no The operations are delete details().

Figure7.Class Diagram For Book Bank System

14
State Chart Diagram:
It consists of state, events and activities. State diagrams are a familiar technique to describe the behavior of
a system. They describe all of the possible states that a particular object can get into and how the object's
state changes as a result of events that reach the object.

Figure 8.StateChartDiagramforBookBankSystem

Deployment Diagram and Component Diagram:

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

Figure9: Deployment Diagram for Book Bank System

15
Develop test cases for unit testing and integration testing

Develop test cases for various white box and black box testing techniques.

16
17
16
19