Software Engineering Lab Project
Software Engineering Lab Project
2-11
12-17
18-35
36-52
53-100
101-112
113-124
125-136
137-145
146-154
Software Requirement Specification Document
For
Prepared by
JUNAID SHAIK(23BCE8679)
In software engineering, a class diagram in the Unified Modelling Language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationship s among objects.
In the diagram, classes are represented with boxes that contain three compartments:
The top compartment contains the name of the class. It is printed in bold and centred, and
the first letter is capitalized.
The middle compartment co ntains the attributes of the class. They are left-aligned and the
first letter is lowercase.
The bottom compartment contains the operations the class can execute. They are also left -
aligned and the first letter is lowercase.
.PassportAutomationSystem : -
1.1. Attributes
. User:-
2.1. Attributes
2.2. Methods
AdminLogin
Attributes
o AdminLoginId
o AdminPassword
Methods
AdminAuthentication
Attributes
o PendingApplications
o Dispatched Passports
o ApplicationId
Methods
NewUser
Attributes
o String Name
o String DOB
o Char Gender
o String EmailId
o Long MobileNo.
Methods
RegisteredUser
Attributes
o String LoginId
o String Password
. Methods
A State chart diagram describes a state machine. State machine can be defined as a machine
which defines different states of an object and these states are controlled by external or internal
events.
Activity diagram explained in the next chapter, is a special kind of a State chart diagram. As State
chart diagram defines the states, it is used to model the lifetime of an object.
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modeling its process aspects. A DFD is often used as a preliminary step to create an overview
of the system without going into great detail, which can later be elaborated. DFDs can also be used
for the visualization of data processing (structured design).
A DFD shows what kind of information will be input to and output from the system, how the data will
advance through the system, and where the data will be stored. It does not show information about
the timing of process or information about whether processes will operate in sequence or in parallel
unlike a flowchart which also shows this information
4. USECASE DIAGRAM : -
To model a system, the most important a spect is to capture the dynamic behavior. Dynamic behavior
means the behavior of the system when it is running/operating.
Only static behavior is not sufficient to model a system rather dynamic behavior is more important
than static behavior. In UML, there are five diagrams available to model the dynamic nature and use
case diagram is one of them.
The internal and external agents are known as actors. Use case diagrams consists of actors, use cases
and their relationships.
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system.
Activity diagram is basically a flowchart to represent the flow from one activity to another activity.
The activity can be desc ribed as an operation of the system.
The control flow is drawn from one operation to another. This flow can be sequential, branched, or
concurrent.
For
BOOK BANK
Prepared by
Junaid Shaik(23BCE8679)
A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a partic ular goal. It is represented using
ellipse.
Actor is any external entity that makes use of the system being modeled. It is represented using stick
figure.
The actors in this use case diagram are member and database. The use cases are the activities
performed by actors.
The member will register himself in the book bank.
Database will verify the status of book and the books will be given.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is represented using a rectangle with three compartments. Top
compartment have the class name, middle compartments the attributes and the bottom
compartment with operations
1. Member details class : Attributes include name, father name, date of birth, address, phone
number, member id, college, degree, course, and semester. Operations are registration,
authentication, and year selection.
2. Administrator: Attributes include name, address, phone, and mail id. Operations are
authentication, verification, and issuing books.
3. Year: Attribute is year selection. Operations are 1st1st year, 2nd2nd year, 3rd3rd year,
and 4th4th year.
4. Issue for 1st1st year: Attributes include member code, member name, book code, book
name, and quantity. Operation is issue.
5. Issue for 2nd year: Attributes include member code, member name, book code, book name,
and quantity. Operation is issue.
6. Issue for 3rd year : Attributes include member code, member name, book code, book name,
and quantity. Operation is issue.
SEQUENCE DIAGRAM
A s equence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows
how processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. There are two dimensions.
He select the books given and the database will update the status of b ook.
The purpose of state chart diagram is to understand the algorithm involved in performing a
method. It is also called as state diagram. A state is represented as a round box, which may
contain one or more compartments. An initial state is represented as small
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
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 workflows 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 flow of stepwise activities performed in book bank management system.
A deployment diagram in the unified modeling language serves to model the physical deployment of
artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represen ted by 3-dimentional box.
Dependencies are represented by communication association.
The processor in this deployment diagram is the book bank which is the main part and which are the
some of the main activities performed in the system. And issue for firs t year, issue for second year
issue for third year and issue for fourth year are some activities performed in this system.
Software Requirement Specification Document
For
Prepared by
J YASHWANTH(23BCE9747)
1. User Characteristics
Student: Students register for exams by submitting their details to the database. They can view
available exams, register, make payments, and receive confirmation.
Administrator: The administrator (exam coordinator) has privileges to manage exams, approve
registrations, update schedules, and oversee the registration process.
2. System Modul es
Login & Authentication: Secure registration for students and administrators via an online form with
username and password credentials.
Exam Management: The system contains all available exams. New exams are added with details like
exam ID, subject, date , time, and eligibility criteria. Exams can be deleted if canceled, and updates
can be made to the exam details.
Operations: Students can register for exams, pay fees, and view their registration details.
Administrators can add, update, and remove exams, v erify student registrations, and manage
schedules.
Privacy: User data is secured with credentials (username and password) to ensure privacy.
Portability: The system should be installable on multiple platforms and support web -based access
for ease of use.
3. Preparation of Software Configuration Management
Software Requirements:
Hardware Requirements:
Processor:i3 or higher
RAM : 4 GB
Star UML is a UML ( Unified Modeling Language ) tool, introduce by MKLab. It is an open - source
modeling tool that supports the UML framework for system and software modeling. StarUML
is based on UML version 1.4, it provides 11 different types of diagram and it accepts UML 2.0
notation. Version 2.0 was released for beta testing under a property license.
StarUML is mostly used by the Agile and small development teams, professional persons and
used by the educational institutes
Diagram Types in StarUML
2.Sequence Diagram
3.Class Diagram
4.Collaboration Diagram
5.Statechart Diagram
6.Component Diagram
7.Deployment Diagram
Features of StarUML
3. Includes Entity- Relationship diagram (ERD), Data- flow diagram (DFD), and Flowchart
diagram.
Step 3: There will be 3 Operating Systems (OS) options, click on the option as per the devise
OS.
Step 4: Now, right - click on the downloaded file, select “Show in Folder” option.
Step 5: Click on the open file, a popup wind ow 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. StarUML is ready to use.
Use Cases:
1. Student Registration
2. Exam Enrollment
3. Payment Processing
Actors Involved:
6
1. Student
2. Admin
3. Payment Gateway
Normal Flow: The student enters details such as name, email, phone
generated.
Normal Flow: The student selects the exam, chooses the preferred
Alternative Flow: If the exam slot is full, the student will be asked to
7
Post Condition: The exam seat is reserved for the student.
Alternative Flow: If the payment fails, the system prompts the user to
retry.
confirmed.
payment process.
Normal Flow: The system generates the admit card with exam details.
Post Condition: The student can download the admit car d for
examination entry.
8
Use Case Name: View Exam Schedule
admin.
Normal Flow: The student logs in and views the available exam
schedule.
Post Condition: The student is informed about the exam date and time.
9
Activity Diagram:
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
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 workflows 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 behaviour of the system.
10
Sequence Diagram:
A sequence diagram represents the sequence and interact ions 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
classcontains.
It is also represented by the order in which things occur and how the objects in the system send
message to one another.
12
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 Online Exam Registration System consists of six main classes: Student, Exam, Registration,
Payment, Admin, and Notification. The Student class stores student details such as studentID, name,
DOB, email, contact number, department, course, year, and credentials, with operations like registering,
deleting, and updating student information. The Exam class manages exam- related details, including
examID, subject name, date, duration, total marks, eligibility criteria, and fee, along with operations to add,
update, delete, and view exams. The Registration class tracks exam enrollments, storing registrationID,
studentID, examID, registration date, and status, with operations for registering and canceling registrations.
The Payment class ensures secure fee transactions by handling paymentID, studentID, examID, amount,
payment date, and payment status, with functio ns for processing and verifying payments. The Admin class
allows administrators to manage students, exams, and registrations, storing adminID, name, email, contact
number, and credentials, with operations to manage student and exam records. Lastly, the Not ification class
manages communication, storing notificationID, studentID, message, and timestamp, with functions to send
and view notifications. This structured system ensures a smooth and secure exam registration process for
both students and administrato rs.
13
Figure 7. Class Diagram For Book Bank System
14
Deployment Diagram and Component Diagram
Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed.
15
State chart diagram
ER diagram
16
17
18
Software Requirement Specification Document
For
Prepared by
J YASHWANTH(23BCE9747)
1. User Characteristics
Store Manager: Responsible for overseeing stock levels, adding new items, updating inventory
details, generating reports, and managing supplier information.
Sales Staff: Can view stock availability, process sales transactions, and update stock quantities after
sales.
Administrator: Has full system privileges, including managing user roles, auditing stock records,
and setting access permissions.
2. System Modules
Login & Authentication: Secure access for different users (store managers, sales staff, and
administrators) wi th role -based permissions.
Stock Management: Allows users to add, update, and remove stock items with details like item ID,
name, quantity, supplier, and category.
Inventory Tracking: Monitors stock levels in real time, triggers low - stock alerts, and maint ains
stock movement history.
Sales & Purchase Management: Records incoming stock (purchases) and outgoing stock (sales),
linking them with invoices and suppliers.
Reporting & Analytics: Generates reports on stock levels, sales trends, purchase history, and
restocking needs for informed decision - making.
3. Non- Functional Requirements
Security & Privacy: User authentication ensures secure access, and sensitive inventory data is
protected with encryption.
Scalability: The system should support businesses of va rying sizes and handle large datasets
efficiently.
Portability: It should be accessible via web and mobile platforms for ease of use and remote
inventory management.
Would you like any modifications or additional details?
Software Requirements:
Hardware Requirements:
Processor:i3 or higher
RAM : 4 GB
Hard Disk drive: 500 GB
Star UML is a UML ( Unified Modeling Language ) tool, introduce by MKLab. It is an open - source
modeling tool that supports the UML framework for system and software modeling. StarUML
is based on UML version 1.4, it provides 11 different types of diagram and it accepts UML 2.0
notation. Version 2.0 was released for beta testing under a property license.
StarUML is mostly used by the Agile and sm all development teams, professional persons and
used by the educational institutes
2.Sequence Diagram
3.Class Diagram
4.Collaboration Diagram
5.Statechart Diagram
6.Component Diagram
7.Deployment Diagram
3. Includes Entity -Relationship diagram (ERD), Data - flow diagram (DFD), and Flowchart
diagram.
Step 3: There will be 3 Operating Systems (OS) options, click on the option as per the devise
OS.
Step 4: Now, right - click on the downloaded file, select “Show in Folder” option.
Step 5: 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. StarUML is ready to use.
Actors Involved:
reports.
6
Use Case Name: Add New Stock
privileges.
Normal Flow: The store manager enters stock details such as item
Normal Flow: The user selects a stock item and updates quantity or
details.
displayed.
Post Condition: The updated stock details are saved in the system.
7
Normal Flow: The sales staff selects the item, records the quantity
update stock.
generated.
Normal Flow: The manager selects a report type (e.g., low stock, sales
analysis.
admin.
Normal Flow: The student logs in and views the available exam
schedule.
8
Figure 1. Use case diagram for stock maintenance system
Activity Diagram:
Activity diagrams are graphical representations of workflows of stepwise activities and actions with
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 workflows 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 behaviour of the system.
9
Figure 2. Activity Diagram for stock maintenance system
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
classcontains.
It is also represented by the order in which things occur and how the objects in the system send
message to one another.
10
Figure 5. Sequence Diagram For online exam regestration
11
Collaboration Diagram
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 des cribes the structure and the relationships among objects.
The Online Exam Registration System consists of six main classes: Student, Exam, Registration,
Payment, Admin, and Notification . The Student class stores student details such as studentID, name,
DOB , email, contact number, department, course, year, and credentials, with operations like registering,
12
deleting, and updating student information. The Exam class manages exam -related details, including
examID, subject name, date, duration, total marks, elig ibility criteria, and fee, along with operations to add,
update, delete, and view exams. The Registration class tracks exam enrollments, storing registrationID,
studentID, examID, registration date, and status, with operations for registering and canceling registrations.
The Payment class ensures secure fee transactions by handling paymentID, studentID, examID, amount,
payment date, and payment status, with functions for processing and verifying payments. The Admin class
allows administrators to manage stud ents, exams, and registrations, storing adminID, name, email, contact
number, and credentials, with operations to manage student and exam records. Lastly, the Notification class
manages communication, storing notificationID, studentID, message, and timesta mp, with functions to send
and view notifications. This structured system ensures a smooth and secure exam registration process for
both students and administrators.
13
Deployment Diagram and Component Diagram
Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed.
14
State chart diagram
15
ER diagram
16
17
1
For
Prepared by
AIM:
To develop the problem statement for Online Course Reservation System.
PROBLEM STATEMENT:
Online Course Reservation System is meant for students who wish to apply for the course
through online in a college. At first the system will list the available courses in the college. Then
the student will check the available seats for the particular course in the college. If the interested
course is available then the student will login and directed to fill the application. The system will
check fo r the eligibility and if the student is eligible then they will directed for payment to reserve
the course. If the course is reserved, then an acknowledgement will be send to the student and also
to the registrar of the college.
2
Software Requirements
Specification
For
ONLINE COURSE
RESERVATION
Prepared by
Revision History
1.5. References
IEEE Software Requirement Specification Template
https://krazytech.com/projects/sample -software -requirements -specificationsrs
2.Overall Description
2.1. Product Perspective
The Online Course Reservation System will be useful for students so that they can reserve their interested course in a
college .This Online Course reservation system is a interface between ‘Students ’ and the ‘College’. This system is
developed to save energy and time of the student.
In the System, Students must register to reserve their interested course in a college. Then Students mu st enter the
details in the application form and the system checks for the eligibility of student. If the student is eligible he/she will
be allowed to pay for the course through E -Pay after payment both the student and registrar will be notified.
· Keepsecretforallofstudentprofiles.Eachdivisioncanseeonlynecessarydataof each
student foranalyzing.
· Internet connection to work on with thesystem.
4.System Feature
4 . 1System Feature1
Description andPriority
ReserveSeat :
· Sign In: The first needs to sign in to the system with the name andpassword he/she have
provided with. The system needs to check for validation of that name and password and then
only allow he/she to access thesystem.
· Check Availability: They must be allowed to see all available options for courses.And see
if the seat is available ornot.
· Reserve Position: Then if the position is available then it must be booked by the only and
should not be granted to any other again till it getsfree .
MaintainHistory :
· Course Information: The System shall generate reports on course about thefollowing
Information: Course ID, Course Name.
· The System will generate reports on seats availability about thefollowing information: Course ID,
Seat Number,Reserved or Unreserved.
Database:
· Mandatory Information: First Name, Last Name, Phone Number, ID, Address, Postal Code, City,
Country, name and Password.
· Course Type: Technical or Non-Technical, Instructor, InstructorDetails.
· Update Information: The registrar will allow Admini strator to update anyof the information.
· Course Related Information: Course ID, No. of Seats.
8
4.2. FunctionalRequirements
1. Login
2. View coursedetails
3. Reserve forcourse
4. Payfee
5. CheckStatus
ACTORS INVOLVED :
1. Student
2. Registrar
REQ - 1 : LOGIN
The User enters the name and password and chooses whether the user is Student or
Registrar.If entered details are valid, the user’s account becomes available. If it is
invalid, anappropriate message is displayed to the user .
REQ - 2 :VIEW COURSE DETAILS
In this use case, a student can search all the courses available to him and choose the
best course he wants. The student can view the course duration, faculty and
department ofthe courses he maychoose.
REQ - 3 :RESERVE FOR COURSE
When a student has successfully chosen a course, he can register to that course. Upon
registration, the student’s details are stored in the database .
REQ - 4 :PAY FEE
After registration to any course, the student may see the details of his current course. He
may wish to know details about fees and other information.
REQ - 5 :CHECK STATUS
· Login ID: Any who uses the system shall have a Login ID andPassword.
· Administrator ’ s Rights: Administrator shall be able to view and modify all information
inSystem.
· Reliability: The system keeps the data securely students who enrolled the courses.
10
REGISTRAR:
DATABA SE:
database is an electronic system that allows data to be easily accessed, manipulated and
updated. In other words, a database is used by an organization as a method of storing, managing
and retrieving information.
Server:
Date:
The purpose of use case diagram is to capture the dynamic aspect of a system. However, this
definition is too generic to describe the purpose, as other four diagrams (activity, sequence,
collaboration, and Statechart) also have the same purp ose.
System:
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.
Usecase:
Draw use cases using ovals. Label the ovals with verbs that represent the system's functions.
Actors:
Actors are the users of a system. When one system is the actor of another system, label the actor
system with the actor stereotype.
13
Relationships:
Illustrate relationships between an actor and a use case with a simple line. For relationships among
use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one
use case is needed by another in order to perform a task. An "extends" relationship indicates
alternative options under a certain use case.
14
Casual:
15
Success scenario:
The Student enters into the system ’s software and looks into the control panel, then he enters the
login ID and password. . If the password is valid then the system will display the next step.
Alternate scenario:
If the password entered by the Student is invalid, the system cannot be opened and can’t
perform any actions. So he must reenter the valid password. The system allows to enter the
valid passwo rd upto three attempts.
Fully Dressed:
Use case name Login
Goal To login successfully into the system.
Level Enter the login ID and password.
Primary actor Student.
Secondary / Suporting actor Admin
Stake holders Student plays the important role in the
system. He login to the system and and then
fill the application.
c
t
p
a
s
s
w
o
r
d
.
F
o
r
g
e
t
p
a
s
s
w
o
r
d
.
Extension Proper maintenance of the system is needed.
Unauthorised person cannot login to the
system.
Special requirements Security
is
importan
t.
Provide
more
authentic
ation.
The Student can enter the system and select the course to check the status of seat availability for
the course. If the seat is available for that course then the student will select the course else the
student will select the other available course.
Casual:
Success scena rio:
The student can enter the system and select the course to check the status of seat availability for
the course. If the seat is available for that course then the student will select the course.
Alternate scenario:
But at some situations, if the seat is not available then the student will select the other
available course.
Fully Dressed:
Main success scenario The student can enter the system and select the
course to check the status of seat availability for
the course. If the seat is available for that course
then the student will select the course.
18
Domain model:
Steps to create a domain model:
1. Find conceptual classes.
Category list:
1.Business transaction: Reservation.
2.Transaction item: Reservation line items.
3.Product or service Course.
Related to transaction:
NOUNS:
· Course
· Student
· Registrar
· Detail
· Username
· Password
· Acknowledgement
· Fees
· System
· Payment
· Details
21
Domain Model:
22
CLASS DIAGRAM:
Class diagram is a static diagram. It represents the static view of an application. Class diagram is
not only used for visualizing, describing, and documenting different aspects of a system but also
for constructing executable code of the software applicat ion.
Class diagram describes the attributes and operations of a class and also the constraints imposed
on the system. The class diagrams are widely used in the modeling of objectoriented systems
because they are the only UML diagrams, which can be mapped d irectly with object - oriented
languages.
Class diagram shows a collection of classes, interfaces, associations, collaborations, and
constraints. It is also known as a structural diagram.
Purpose of Class Diagrams:
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering.
Members:
UML provides mechanisms to represent class members, such as attributes and methods, and
additional information about them.
Visibility:
To specify the visibility of a class member (i.e. any attribute or method), these notations must be
placed before the member's name.
23
Derived property:
Is a property which value (or values) is produced or computed from other information, for
example, by using value of other properties.
Derived property is shown with its name preceded by a forward slash '/'.
Scope :
The UML specifies two types of scope for members: instance and classif ier, and the latter is
represented by underlined names.
Classifier members are commonly recognized as “static” in many programming languages.
The scope is the class itself.
o Attribute values are equal for all instances
o Method invocation does not affect the classifer ’ s state
Instance members are scoped to a specific instance.
o Attribute values may vary between instances
o Method invocation may affect the instance ’ s state (i.e. change instance ’ s attributes)
To indicate a classifier scope for a member, its name must be underlined. Otherwise, instance
scope is assumed by default.
Relationships:
24
Class Notation:
UML class is represented by the following figure. The diagram is divided into four parts.
The top section is used to name the class.
The second one is use d to show the attributes of the class.
The third section is used to describe the operations performed by the class.
The fourth section is optional to show any additional components
Classes are used to represent objects. Objects can be anything having properties and
responsibility.
Object Notation:
It is represented in the same way as the class. The only difference is the name which is underlined
as shown in the following figure.
25
Classes:
1. User
Username: String
Password: String
2. CourseDetails
Coursetype: String
Duration: Integer
3. Reservation
Name: String
Age: Integer
DOB: String
Marks:Integer
Parentdetail:String
4. Payment
26
Amount: Integer
ModeofPayment: String
5. NetBanking
userid: String
password: String
6. CardPayment
Cardnumber: Long
ExpiryDate: String
CVVnumber: Integer
7. Status
Name: String
Coursename: String
Paidamount: Integer
CLASS DIAGRAM:
28
Class diagram
29
SEQUENCE DIAGRAM:
A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order
in which these interactions take place. We can also use the terms event diagrams or event scenarios
to refer to a sequence diagram. Sequence diagrams describe how and in what order the objects in
a system function. These diagrams are widely used by businessmen and software developers to
document and understand requirements for new and existing systems.
1. Actors: An actor in a UML diagram represents a type of role where it interacts with the
system and its objects. It is important to note here that an actor is always outside the scope
of the system we aim to model using the UML diagram.
30
2. We use actors to depict various roles including human users and other external subjects.
We represent an actor in a UML diagram using a stick person notation. We can have
multiple actors in a sequence diagram. For example: Here the user in seat reserv ation
system is shown as an actor where it exists outside the system and is not a part of the
system.
UML for naming a lifeline follows the following format – Instance Name : Class Name
We display a lifeline in a rectangle called head with its name and type. The head is located
on top of a vertical dashed line (referred to as the stem) as shown above. If we want to model
an unnamed instance, we follow the same pattern except now the portion of lifeline ’s name
is left blank.
Difference between a lifeline and an actor: A lifeline always portrays an object internal to
the system whereas actors are used to de pict objects external to the system. The following is
an example of a sequence diagram:
32
the processing of the message. The caller continues only when it knows that the
receiver has processed the previous message i.e. it receives a reply message. A large
number of calls in object oriented programming are synchronous. We use a solid
arrow head to represent a synchronous message.
Delete Message: We use a Delete Message to delete an object. When an object is deallocated
memory or is destroyed within the system we use the Delete Message symbol. It destroys the
occurrence of the object in the system.It is represented by an arrow terminating x. For
example – In the scenario below when the order is received by the user, the object of order
class can be destroyed.
35
Self Message: Certain scenarios might arise where the object needs to send a message to
itself. Such messages are called Self Messages and are represented with a U shaped arrow.
For example – Consider a scenario where the device wants to access its webcam. Such a scenario
is represented using a self message.
Reply Message: Reply messages are used to show the message being sent from the re ceiver
to the sender. We represent a return/reply message using an open arrowhead with a dotted
line. The interaction moves forward only when a reply message is sent by the receiver.
36
For example – Consider the scenario where the device requests a photo from the user. Here
the message which shows the photo being sent is a reply message.
Found Message: A Found message is used to represent a scenario where an unknown source
sends the message. It is represented using an arrow directed towards a lifeline fro m an end
point. For example: Consider the scenario of a hardware failure.
37
It can be due to multiple reasons and we are not certain as to what caused the hardware
failure.
38
Lost Message: A Lost message is used to represent a scenario where the recipient is not
known to the system. It is represented using an arrow directed towards an end point from a
lifeline. For example: Consider a scenario where a warning is generated.
The warning might be generated for the user or other software/object that the lifeline is
interacting with. Since the destination is not known before hand, we use the Lost Message
symbol.
Guards: To model conditions we use guards in UML. They are used when we need to restrict the
flow of messages on the pretext of a condition being met. Guards play an important role in letting
software developers know the constraints attached to a system or a particular process.
For example: In order to be able to withdraw cash, having a balance greater than zero is a condition
that must be met as shown below.
Used to model and visualize the logic behind a sophisticated function, operation or
procedure.
They are also used to show details of UML use case diagrams.
Used to understand the detailed functionality of current o r future systems.
Visualize how messages and tasks move between objects or components in a system.
SEQUENCE DIAGRAM:
40
41
Flow of messages:
The student login to the system by entering a valid ID and password.
COLLABORATION DIAGRAM:
A collaboration diagram, also known as a communication diagram, is an illustration of the
relationships and interactions among software objects in the Unified Modeling Language ( UML).
These diagrams can be used to portray the dynamic behavior of a particular use cases and define
the role of each object.
Collaboration diagrams are created by first identifying the structural elements required to carry out
the functionality of an interaction. A model is then built using the relationships between those
elements. Several vendors offer software for creating and editing coll aboration diagrams.
A collaboration diagram resembles a flowchart that portrays the roles, functionality and behaviours
of individual objects as well as the overall operation of the system in real time. The four major
components of a collaboration diagram are:
1. Objects- Objects are shown as rectangles with naming labels inside. The naming label follows
the convention of object name: class name. If an object has a property or state that specifically
influences the collaboration, this should also be noted.
2. Actors- Actors are instances that invoke the interaction in the diagram. Each actor has a name
and a role, with one actor initiating the entire use case.
3. Links- Links connect objects with actors and are depicted us ing a solid line between two
elements. Each link is an instance where messages can be sent.
43
4. Messages- Messages between objects are shown as a labeled arrow placed near a link. These
messages are communications between objects that convey information about the activity and
can include the sequence number.
The most important objects are placed in the centre of the diagram, with all other participating
objects branching off. After all objects are placed, links and messages should be added in between.
COLLABORATION DIAGRAM:
45
ACTIVITY DIAGRAM: \
46
Activity diagram describe activities which involve concurrency and synchronization, which are a
variation of state diagrams that focuses on the flow of actions and events. They can be used for:
To model a human task (a business process, for instance).
To describe a system function that is represented by a use case.
ACTIVITY DIAGRAM:
processed by the filling the ap plication by entering the details and get validate by the
system.Then payment is done by the help of accountant.Then the acknowledgement send to the
student for the resevation of a course.
Key concepts:
State
A state is a condition during the life of an object during which it satisfies some condition,
performs some activity, or waits for some external event.
A state machine diagram is a graph consisting of:
The final state of a state machine diagram is shown as concentric circles. An open loop
state machine represents an object that may terminate before the system terminates, while
a closed loop state machine diagram does not have a final state; if it is the case, then the
Conclusion:
The Online course Reservation system can help to save the time of the students. The
system is designed to reduce the time , also improve the efficiency of maintaining the course.
It provides flexible and powerful reports regarding the course available in the list.it provides
the status to get the details of their enrolled course. It also helps to overcome some problems
faced by the students in real timecourse reservation .
Software Requirement Specification Document
For
E -TICKETING SYSTEM
Prepared by
T SAI VIVEK REDDY(23BCE8725)
PROBLEM STATEMENT
S.NO CONTENTS
1 INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 References
1.6 Overview
2 OVERALL DESCRIPTION
2.1 Functionality
2.2 Usability
2.3 Performance
2.4 Reliability
1. INTRODUCTION
Purpose
The applicant should login to the database for reserving the ticket.
In the specification use define about the system requirements that are part from
the
functionality of the system. It tells the usability, reliability defined in the
use case
specification.
References
Technology To Be Used
Tools Be Used
2. OVERALL DESCRIPTION
Functionality
Usability
The User interface makes the Credit Card Processing System to be effi-
cient.
Performance
It is of the capacities about which it can perform function for many us-
ers
at the same times efficiently that are without any error occurrence.
Reliability
The system should be able to process the user for their corresponding re-
quest.
UML DIAGRAMS
Sno UML DIAGRAMS
The actors in this use case diagram are applicant, and E -ticketing Data-
base. The use
cases are the activities performed by actors. The actors in this use case dia-
gram are
login,filling details,selecting flight,book ticket,search,cancel ticket.
CLASS DIAGRAM
DOCUMENTATION
SEQUENCE DIAGRAM
DOCUMENTATION
DOCUMENTATION
ACTIVITY DIAGRAM
DOCUMENTATION
RESULT
Thus the project to develop E -Ticketing system using Umbrello Tool
and to
implement using Visual Basic is done successfully.
Software Requirement Specification Document
For
Prepared by
M.ASISH REDDY(23BCE8660)
AIM
To develop a project software personnel management system using the rational rose
software and to implement the software in java
PROBLEM STATEMENT
The CEO must enter the name and password to login the form and select the particular
employee to view the details about that employee and maintaining the employee details
personally. This process of software personnel management system are descri bed sequentially
through following steps, The CEO login to the software personnel management system .He/she
search for the list of employees. Then select the particular employee. Then view the details of
that employee. After displaying the employees detail then logout.
UML DIAGRAMS
The use case diagram in the software personnel management system illustrates the
sequence of sequencing and describing an interaction between a CEO and a system.
CEO - login to the software personnel management system and maintaining the employee
details.
DATABASE - Maintainance the list of employee details and check whether the CEO has given
the valid name and password.
LOGIN - This use case gives as entry to the CEO and the database.
LIST OF EMPLOYEE- This will create the situation for the CEO to select particular
employee from the available list.
EMPLOYEE DETAILS - The CEO can able to view the details of the employee using this
usecase.
VERFICATION - Database check name and password is valid or invalid.
MAINTAIN PERSONNELDETAILS - The CEO maintain the employee details in the details.
LOGOUT - The CEO can be logout the software personal management system.
USECASE DIAGRAM
CLASS DIAGRAM
CEO - The CEO has to login the form by specifying the name and password of him.
DATABASE - The database checks whether the CEO has given the name and password
Accordingly. if not the error message will be displayed.
AVAILABILE EMPLOYEE - The database is connects to the list of available employees and
the CEO. if wants then select the employee from it.
CLASS DIAGRAM
CEO
DATABASE
name : string
name : string
login()
joballocation() login()
regularAttedance() storeDetails()
verification() logout()
logout()
EMPLOYEE
name : string
login()
qua;lification()
experience()
logout()
SEQUENCE DIAGRAM
The CEO must enter his name and password to login the software personnel management
system. The verification process is undergone by the database .If the details are correct he can
enter to the system otherwise error is displayed. After login the details of the particular employee
is viewed by the CEO. Finally he is logged out from the system.
SEQUENCE DIAGRAM
login
COLLABORATION DIAGRAM
It is same as the sequence diagram that involves the object of the project with the only
differences that we give the sequence no to the each process. The CEO must enter his name and
password to login the software personnel management system. The verification process is
undergone by the database .If the details are correct he can enter to the system otherwise error is
displayed. After login the detail of the particular employee is viewed by the CEO. Finally he is
logged out from the system.
COLLABORATION DIAGRAM
6: login
8: view employee details
9: verification
10: logout
ceo dba
1: login
2: name and address
3: qualification
4: experiance
5: logout
employe
e
STATE CHART DIAGRAM
The various states are the login, listsof employees, selects a employee, display the
information about the employee, logout.The state chart diagram describes the behavior of the
system. The main purpose of the system is to maintain an employee details personally. For that
the CEO Log in to the software personnel management system. He/she s elects a particular
employee from the list of available employee. The CEO has to view the details of the particular
employee by clicking the respective button.The CEO views the details then finally he is logout
from the system.
The CEO Log in to the software personnel management system. He/she selects a
particular employee from the list of available employee. The CEO can view the details of the
particular employee by clicking the respective button. After viewing the details he is logout from
the s ystem.
ACTIVITY DIAGRAM
In this diagram there link between the actors is present in the SPMS that could be shown
in diagrammatically way in the component diagram. Each every actor is having a directional link
to process further details present in the system.
COMPONENT DIAGRAM
software personal
management system
emplo DBA
yee ceo
DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the software personnel management system
which is the main part and the devices are the CEO login, viewing the details of the employee
are some of the main activities performed in the system.
DEPLOYMENT DIAGRAM
RESULT
Thus the UML diagrams are drawn for software personnel management system and the
java code was generated successfully by using Rational Rose software.
Software Requirement Specification Document
For
Prepared by
M.ASISH REDDY(23BCE8660)
PROBLEM STATEMENT:
The system allows users to apply for a credit card, manage transactions, and make payments.
The process includes:
UML DIAGRAMS:
1. Us e Case Diagram
2. Class Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. State Chart Diagram
6. Activity Diagram
7. Component Diagram
8. Deployment Diagram
USECASE DIAGRAM
Customer: Registers, logs in, applies for a credit card, views transactions, makes payments.
Admin: Reviews and approves applications, manages credit card details.
Database: Stores and verifies customer details.
Use Cases
login
Allot
Pay
Signup
Usecase diagram for Credit Card Processing System
CLASS DIAGRAM
Classes
verify authentication
Allot card
User login
Verify authenticate
Get card
Check due
check due
pay due
user logout
Admin logout
2: verify authentication
5: verify authentication
4: user login
8: check due
9: pay due
10: user logout
User Database
6: get card
1: admin login
3: allot card
7: check due
11: admin logout
Admin
States
Allot card
Check due
Make
payment
update
balance
Logout
Main components:
Custome NewCom
r ponent2
Bank
Shows the system’s physical structure, including hardware and software deployment.
Nodes:
Credit Card
processing system
Custom Bank
er
For
E-BOOK MANAGEMENT
Prepared by
L THARUN(23BCE8698)
AIM
To develop a project for an E -Book Management System using
UML diagrams and to implement the software in an appropriate
programming language.
PROBLEM STATEMENT
The system allows users to manage, organize, and access e -
books efficiently. Users can register, log in, upload, download,
and categorize e -books. The system will include an
administrative module for managing users and content.
UML DIAGRAMS
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
CLASS DIAGRAM
The main classes involved in the system:
User: Handles user authentication and actions.
Admin : Manages users and e -books.
E -Book: Stores book details such as title, author, and file
location.
SEQUENCE DIAGRAM
Describes the interaction between users, administrators, and
the system when managing e -books.
COLLABORATION DIAGRAM
Similar to the sequence diagram but focuses on object
interactions with sequence numbers.
STATE CHART DIAGRAM
Depicts various states such as login, boo k selection, reading,
and logout.
ACTIVITY DIAGRAM
Illustrates the flow of activities from login to e -book
management and logout.
COMPONENT DIAGRAM
Shows the relationship between different components of the
system.
DEPLOYMENT DIAGRAM
Illustrates the system ’s physical deployment, including servers,
users, and data storage.
RESULT
The UML diagrams are designed for the E -Book Management
System, and the implementation will be carried out using the
chosen technology stack.
Software Requirement Specification Document
For
RECRUITMENT SYSTEM
Prepared by
L THARUN(23BCE8698)
AIM
To develop a project for a Recruitment System using UML diagrams and to implement the software in
an appropriate programming language.
PROBLEM STATEMENT
The system allows companies to post job openings, and applicants to register, apply for jobs, and
track their application status. The system will include an administrative module for managing job
postings and user applications.
UML DIAGRAMS
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
Activity Diagram
Component Diagram
Deployment Diagram
The Use Case Diagram illustrates the interactions between job seekers, recruiters, and the system.
Actors:
Job Seeker : Registers, logs in, searches for jobs, applies, and tracks applications.
Recruiter : Posts job openings, reviews applications, and manages recruitment processes.
Use Cases:
User Registration – Job seekers and recruiters register w ith the system.
CLASS DIAGRAM
Job Posting : Stores job details such as title, description, and requirements.
SEQUENCE DIAGRAM
Describes the interaction between job seekers, recruiters, and the system when applying for jobs.
COLLABORATION DIAGRAM
Similar to the sequence diagram but focuses on object interactions with sequence numbers.
Depicts various states such as job posting, application submission, interview s cheduling, and hiring.
ACTIVITY DIAGRAM
DEPLOYMENT DIAGRAM
Illustrates the system ’ s physical deployment, including servers, users, and data storage.
RESULT
The UML diagrams are designed for the Recruitment System, and the implementation will be carried
out using the chosen technology stack.