U20CBP405 Software Engineering Laboratory

LIST OF EXERCISES:

SOFTWARE REQUIRED:
Open source Tools: Star UML / ARGO UML

Development of requirements specification, function-oriented design using SA/SD, object- oriented

design using UML, test case design, implementation using C++ and testing. Use of appropriate
CASE tools and other tools such as configuration management tools, program analysis tools in the
software life cycle

 Problem Analysis and Project Planning -Thorough study of the problem –Identify
Project scope, Objectives and Infrastructure
 Software Requirement Analysis –Describe the individual Phases/modules of the project
and Identify deliverables. Identify functional and non-functional requirements.
 Data Modeling –Use work products –data dictionary.

 Software Designing -Develop use case diagrams and activity diagrams, build and test class
diagrams, sequence diagrams and add interface to class diagrams.

 Develop the software project start-up, prototype model, using software engineering
methodology and object-oriented design using UML for at least two real time scenarios
 Prototype model –Develop the prototype of the product.

TOTAL: 30 PERIODS
Sample Experiments:

Academic domain
1. Course Registration System
2. Student marks analysing system
Railway domain
3. Online ticket reservation system
4. Platform assignment system for the trains in a railway station
Medicine domain
5. Expert system to prescribe the medicines for the given symptoms
6. Remote computer monitoring
Finance domain
2
7. ATM system
8. Stock maintenance
Human Resource management
9. Quiz System
10. E-mail Client system.

3
 INDEX

SL.NO NAME OF THE EXPERIMENT PAGE.NO

1 STUDY OF UML 5

2 LIBRARY MANAGEMENT SYSTEM 10

3 ONLINE TICKET RESERVATION SYSTEM 28

4 ONLINE COURSE REGISTRATION SYSYEM 37

5 ATM SYSTEM 48

6 PLATFORM ASSIGNMENT SYSTEM FOR TRAINS 60

7 EXPERT SYSTEM FOR MEDICAL SYMPTOMS 73

8. QUIZ STSTEM 82

9. STUDENT MARK ANALYSING SYSTEM 94

10. STOCK MAINTENANCE 104

11. EMAIL CLIENT SYSTEM 112

12. REMOTE COMPUTER MONITORING SYSTEM 121

4
EX.NO.1

STUDY OF UML
AIM:-
To study the basic concepts of Unified Modeling Language.

UML NOTATION
 Unified Modeling Language.
 Set of notations and conventions used to describe and model an application.
 Universal language for modeling systems.
 Standard notation for OO modeling systems.
 Does not specify methodology to develop an application.
UML DIAGRAMS
 Class Diagram
 Use Case Diagram
 Behavioral Diagram
 Interaction Diagram
 Sequence Diagram
 Collaboration Diagram
 State Chart Diagram
 Activity Diagram
 Implementation Diagram
 Component Diagram
 Deployment Diagram
CLASS DIAGRAM
 Shows the static structure of the model.
 Collection of static modeling elements such as classes and their relationships
connected as a graph.
 Provides visual representation of objects, relationships and their structures.

Class:-
 A class is a set of objects that share a common structure and common behavior.

5
  It is represented as:

<Class Name>
<Attributes>
<Operations>

Interface:-
 Specifies the externally-visible operations of a class and/or component.

Association:-
 Model properties of associations.
 The properties are stored in a class and linked to the association relationship.
 Example,

Bank Account Person

Generalization:-
 A generalize relationship is a relationship between a more general class or use case and a
more specific class or use case.
 Example,

Vehicle

Bus Truck Car

USE CASE DIAGRAM

 Set of use cases enclosed by system boundary, communication association between actors
and use cases, and generalization among use cases.
Actors:-
 External factors that interacts with the system from the user's perspective.

6
Use Cases:-
 Set of scenarios that describe how actor uses the system.
 Represented as,

Relationship:-
 Communication – communications with the use case normally.
 Uses – Shown by generalization arrow from the use cases.
 Extends – Used when one case does more than another that is similar to it.

BEHAVIOR DIAGRAM
INTERACTION DIAGRAM
 Diagrams that describes how group of objects are collaborated.

SEQUENCE DIAGRAM:
 Describes the behavior of the system through interaction between the system and
the environment in time sequence.
 Two dimensions:
 Vertical dimension – represents time.
 Horizontal dimension – represents objects.
 Life line – Object's existence during the interaction.

Object 1 Object 2

7
 COLLABORATION DIAGRAM:
 An interaction diagram that shows the order of messages that implement an operation or
a transaction.
 Collaboration diagrams show objects, their links, and their messages.

Object 1 Object 2
1. <Event>

Object:-
 An object has state, behavior, and identity.
 Objects interact through their links to other objects.
Link:-
 A link is an instance of an association, analogous to an object.
Message:-
 A message is the communication carried between two objects that trigger an event.

STATECHART DIAGRAM
 Models the dynamic behavior of individual classes or any other kind of object.
 Shows the sequences of states, events, and actions.

State:-
 Represents a condition or situation during the life of an object during which it satisfies some
condition or waits for some event.

<State>

Start State:-
 Shows the beginning of workflow.

End state::-
 Represents the final or terminal state.

8
ACTIVITY DIAGRAM
 Used for modeling the sequence of activities in a process
 Special case of a state machine in which most of the states are activities and most of the
transitions are implicitly triggered by completion of the actions in the source activities.
Activity:-
 Represents the performance of task or duty in a workflow.
<Activity>

Swim lanes:-
 Represents organizational units or roles within a business model.

IMPLEMENTATION DIAGRAM
 Shows the implementation phase of system development.
 Two types of implementation diagrams:
 Component diagram
 Deployment diagram

COMPONENT DIAGRAM
 Models the physical components in the design.
 A graph of the design’s components connected by dependency relationships.
 Includes concept of packages.
 Package is used to show how classes are grouped together.
DEPLOYMENT DIAGRAM
 Shows the configuration of runtime processing elements and software components.
 It is a graph of nodes connected by communication association.
 Nodes are the components that are connected to other components through dependencies.
 Used in conjunction with component diagrams to show the distribution of physical modules.

RESULT:- Thus the different conceptual models under UML have been studied

9
Ex.No: 2 LIBRARY MANAGEMENT SYSTEM

PROBLEM ANALYSIS

Problem Statement
Computerized Library Management system is used to monitor and control the transactions in a library.
It needs to maintain the record of new books and retrieve the details of books available in the library.
Should be able to perform basic operations in a library like adding new member, new books, and
updating new information, searching books and members and provide facility to borrow and
return books. The report generation facility should allow users to generate the list of
books borrowed by the members.

Analysis
Library Management System should allow the user to add new members and books. The system has
three categories of users: Administrator, Student and Faculty.

Administrator should be able to:

 Add new book details
 Modify book details
 Delete book
 Add new user details
 Modify user details
 Delete user
 Search for book and user details
 Lend/Return books
 Generate reports:
o Due list on daily basis
o Overdue list along with fine calculation
o Stock
o User information
o Overall issue or return of books
o Author/subject/Title

Student should be able to:

 Search for a book
 View the details of books borrowed by self

Faculty should be able to:

 Search for a book
 View the details of books borrowed by self

10
Feasibility study

Technical feasibility
The Library Management System (LMS) runs with a minimum system resources:
 Web server(Tomcat Apache )
 ARGO UML
 PHP
 HTML
Above said system resources are available as open source. Hence it is feasible to develop LMS
in this environment.

Operational feasibility
As the system has HTML based GUI no special skill set is required for working with the
system, hence it is operationally feasible.

Economic feasibility
As the LMS requires minimum system resources, hence it is economically feasible.

PROJECT PLANNING

1. Overview
Automation of Library Management System is to handle the entire activity of a library. The
system keeps track of all the information about the books and their complete details. The
system contains a database where all the information will be stored. The system is user-
friendly.

2. Goals and Scope

Goal : To automate the Library Information System with the following functional goals
1. Login
2. Adding Book/User Details.
3. Updating Book/User Details
4. Deleting Book/User Details
5. Generating Reports
6. Viewing/Searching for Details.

Scope : The system accepts the General Library Transactions of book issue, return and
renewals for the members. Different areas where we can use these applications are:

1. Any educational institutes can make use of it for providing information about
author, content of the available books.
2. The system would provide basic set of features to add/update members, add/update
books, and manage check in specifications for the systems based on the client's
statement of need.

11
3. Schedule
Work Breakdown Structure

Schedule and Milestones

Milestones Description Milestone Criteria Planned week

M0 Problem Analysis 1st week
Problem statement, Analysis,
Feasibility Study
M1 Project Planning 2nd week
Scope and concept described
M2 Requirement Analysis 2nd and 3rd week
Draft SRS, Design
Specification, Test Plan,
Requirement Analysis (Final)
M3 Study of UML Notations 3rd week
Architecture reviewed and
stable
M4 Modeling 4th week
Software Design, Data
Dictionary
M5 Implementation 5th week
Coding of functionality,
Debugging, System Test
Plan.

12
 Milestones Description Milestone Criteria Planned week
M6 Testing 6th week
Database & System
Integration, Acceptance
Testing
M7 Documentation 7th week
User Manual

Risk Management
Unexpected Holidays, Non availability of computer resources, Absence of Human Resource
are the identified risks for not meeting the deadlines. Additional efforts need to put in by the
human resources to complete the work within the deadline by the way of working after
working hours.

Delivery Plan

Ident. Deliverable Planned Date Receiver

D1 Analysis and Feasibility Report 1st week Client
D2 Project Plan 2nd week Client
D3 SRS 3rd week Client
D4 Design 4th week Client
D5 Test Plan 5th week Client
D6 Code 6th week Client
D7 Test Report 6th week Client

SOFTWARE REQUIREMENT ANALYSIS

Software Requirement Specification (SRS)

1. Introduction
Library Management system is used to monitor and control the transactions in a library. It
needs to maintain the record of new books and retrieve the details of books available in the
library. Should be able to perform basic operations in a library like adding new
member/ books, updating member/book information, searching for members/books and
provide facility to lend and return books. The report generation facility should allow
generating various reports.

Lending & returning books or viewing the available books at the Library is currently done
manually. This project is specifically designed for the use of librarians and library users. It is
especially useful for an educational institute where modifications in the content can be done
easily according to the requirements.

13
1.1 Purpose of the requirements document

The purpose of this document is to analyze and elaborate on the high-level needs and features
of the Library System. It focuses on the capabilities and facilities provided by a Library .The main
Objective of this document is to illustrate the requirements of Library Management System. This
document gives the detailed description of both functional and non-functional requirements
proposed by the clients.
This document defines and describes the operations, interfaces, performance, and quality
assurance requirements of the Library System. The document also describes the nonfunctional
requirements such as the user interfaces. It also describes the design constraints that are to be
considered when the system is to be designed, and other factors necessary to provide a complete
and comprehensive description of the requirements for the software.

1.2 Scope of the product

The Software Requirements Specification captures all the requirements in a single document.
The Library Management System that is to be developed provides the Administrator, Student
and Faculty members with books information, and many other facilities.

The system accepts the General Library Transactions of book issue, return and renewals for the
members. The system would provide basic set of features to add/update members, add/update
books, and manage check in specifications for the systems based on the client's statement of
need.

1.3 Definitions, acronyms and abbreviations

PHP- Hypertext Preprocessor
SQL- Structured Query Language
GUI- Graphical User Interface
LMS – Library Management System

1.4 References

(i) Roger s Pressman ,”Software Engineering -a practitioner's approach” 7th edition

(ii) Ian sommerville , “software engineering “ 9th edition

1.5. Overview of the remainder of the document

The SRS will provide a detailed description of the Library Management System. This document will
provide the outline of the requirements, overview of the characteristics and constraints of the system.

Section 2 of this document provides the General description such as Product perspective, Product
functions and the characteristics of the user’s of this product. Section 3 describes the Specific
requirements which cover the functional, non-functional and interface requirements. This is obviously

14
the most substantial part of the document but because of the wide variability in organizational practice,
it is not appropriate to define a standard structure for this section. The requirements may document
external interfaces, describe system functionality and performance, specify logical database
requirements, design constraints, emergent system properties and quality characteristics.

2. General description

2.1 Product perspective

The Library Management System is a package to be used by Libraries to improve the efficiency of
Administrator and Users. The system provides books catalog and information to members and helps
them decide on the books to lend from the library. The Librarian can keep the books catalog updated
all the time so that the members (students and the professors) get the updated information all the time.

2.2 Product functions

The Library Management System provides real time information about the books available in the
Library and the user information. The Product functions are more or less the same as described in the
product perspective. The functions of the system include the system providing different type of
services based on the type of users [Administrator/User].

1. Administrator should be able to Add new book/User details , Modify Book/user details, Delete
Book/user details, Search for book and user details, Lend/Return books and Generate various
reports such as
 Due list on daily basis
 Overdue list along with fine calculation
 Stock
 User information
 Overall issue or return of books
 Author/subject/Title

2. Student should be able to Search for a book and view the details of books borrowed by self
3. Faculty should be able to Search for a book and view the details of books borrowed by self

2.3 User characteristics

The users of the system are administrators, Student and Faculty members, the administrator who
maintain the system. The members are assumed to have basic knowledge of the computers . The
administrators of the system to have more knowledge of the internals of the system and is able to
rectify the small problems that may arise due to disk crashes, power failures and other catastrophes to
maintain the system. The proper user interface, user’s manual, online help and the guide to install and
maintain the system must be sufficient to educate the users on how to use the system without any
problems.

15
2.4 General constraints
 The information of all the users must be stored in a database that is accessible by the
Library Management System.
.
 The Library Management System is connected to the server computer and is running all
24 hours a day.

2.5 Assumptions and dependencies

 The users have sufficient knowledge of computers.
 The users know the English language, as the user interface will be provided in English
 The product can access the college student database
3. Specific requirements
3.1. Functional Requirements
This section describes in detail all the functional requirements.

(It shows what the system can do)

1. Login
2. Adding Book/User Details.
3. Updating Book/User Details
4. Deleting Book/User Details
5. Lend/Return book
6. Generating Reports
7. Viewing/Searching for Details.
3.2 Non- Functional Requirements
Usability
 The system is user friendly and self-explanatory.

Reliability
The system has to be very reliable due to the importance of data and the damages incorrect or
incomplete data can do.
Availability
The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The
system shall be operational 24 hours a day and 7 days a week.

Mean Time Between Failures (MTBF)

The system will be developed in such a way that it may fail once in a year.

Mean Time to Repair (MTTR)

Even if the system fails, the system will be recovered back up within an hour or less.

16
Accuracy
The accuracy of the system is limited by the accuracy of the speed at which the employees of the
library and users of the library use the system.
Maximum Bugs or Defect Rate
Not specified.
Access Reliability
The system shall provide 100% access reliability.

Performance
Response Time
The system shall respond to the member in not less than two seconds from the time of the request
submittal. The system shall be allowed to take more time when doing large processing jobs.

The requirements may document external interfaces, describe system functionality and performance,
specify logical database requirements, design constraints, emergent system properties and quality
characteristics.

3.3. Hardware and software requirements

3.3.1. Hardware Interfaces
 Processor: Pentium or Higher.
 RAM: 312MB or Higher.
3.3.2. Software Interfaces
Operating System: Unix, Linux, Mac, Windows etc..
Development tool: PHP : Hypertext Preprocessor
Data Base: MySQL
3.4 External Interfaces
User Interfaces
The user-interface of the system shall be designed as shown in the user-interface prototypes.
4. Appendices

5. Index

17
MODELING

Design model –UML diagrams

Use case diagramStep 1:start ARGO UML->Create-> Use Case

18
Activity Diagram for Lending of book

19
Sequence diagram for Lending of book

20
Collaboration diagram for Lending of book

21
Class Diagram

22
DATA DICTIONARY

Book Details

S.No Name Alias Name Where Supplementary Data

Used/How Data Type Limitations
Used
1 Book name Title Borrow, string Up to 20 char
Display
2 Book ID - Return, integer Up to 2 digits
Display
3 Author Borrow, string Up to 20 char
Name Display
4 Publisher Borrow, integer Up to 10 digits
Display
5 Price Borrow, integer Up to 16 digit
Display

User Details

S.No Name Alias Name Where Supplementary Data

Used/How Data Type Limitations
Used
1 User name - Membership, string Up to 20 char
Borrow,
Display
2 Dept name - Membership string Up to 2 digits
3 Address Membership string Up to 20 char

4 Email ID Membership string Up to 10 digits

5 Credit card Membership integer Up to 16 digit
no

23
 IMPLEMENTATION
Login use case:
lms.html
<html>
<head>
<title>
Library Management System
</title>
<body>
<form action="" value="post">
username:<input type="text"><br>
password:<input type="text"><br>
<input type="button" value="submit"><br>
</form>
</body>
</html>
lms.jsp
<%@ page language="java" import="java.sql.*"%>
<%@ page import="java.io.*"%>
<%@ page import="java.util.*"%>
<%@ page import="java.sql.connection"%>
<%@ page import="java.sql.drivermanager"%>
<%@ page import="java.sql.*"%>
<%@ page import="java.sql.SQLException"%>
<% string username,password;
string username="",password="";

24
username=request.getparameter("username");
password=request.getparameter("password");
Connection con=null;
try
{
Class.forName("com.mysql.jdbc.Driver");
con=DriverManager.getconnection("jdbc:mysql://localhost:3306/db1","root","root");
try
{
String sql="INSERT user VALUES(?,?)";
PreparedStatement prest=con.prepareStatement(sql);
prest.setString(1,username);
prest.setString(2,password);
int count=prest.executeUpdate();
con.close();
}
catch(SQLException s)
{
System.out.println("SQL statement is not executed!");
}
}
catch(Exception e){
e.printStackTrace();
}
%>

25
OUTPUT

TESTING
Test cases:

Name Requirement Description Input Expeted Actual

o/p o/p

Login Username & Used to verify if actor is User,name,password Valid Valid

password should the authorized person or msg msg
be entered not

Login Username & Used to verify if actor is User,name,password InValid InValid

password should the authorized person or msg msg
be entered not

Modify user details or Store the user details & Name,regno,email_id Valid Valid
user or book details book details (Or ) book name msg msg
books should be ,book_id ,price,
entered author_name

issue Check if the Used to issue books Book_id ,title of book Valid Valid
required no of msg msg
books are
available

26
issue Check the issue Used to issue books No of books issued Valid Valid
limit of faculty msg msg
or student

return Used to return Check whether the Book_id, Student_id or Valid Valid
the book before student or faculty return faculty_id msg msg
due data the book before due date
Book
return

return Used to return Check whether the Book_id, Student_id or Valid Valid
the book after student or faculty return faculty_id msg msg
due data the book after due date
Fine Fine
amount amount

search All info stored in View book details book name ,book_id, Valid Valid
database price, msg msg
author_name

Result: Thus the Library Management System has been studied and implemented successfully.

27
EX.NO:3
ONLINE TICKET RESERVATION SYSTEM

PROBLEM STATEMENT
The main purpose of online ticket booking system is to automate the booking and cancellation
process in order to help the customer to provide anytime and anyplace uninterrupted service.

UML USECASE DIAGRAM

28
CLASS DIAGRAM

COLLABORATION DIAGRAM

29
ACTIVITY DIAGRAM

30
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

31
Test cases:

Name Requirement Description Input Expeted Actual

o/p o/p

Login Username & Used to verify if actor User,name,password Valid Valid

password is the authorized person msg msg
should be or not
entered

Login Username & Used to verify if actor User,name,password inValid inValid

password is the authorized person msg msg
should be or not
entered

Reservation Store the Passengername,age,phone Name,age, gender Valid Valid

passenger no,address etc msg msg
details

Reservation Check if the Used to reserve tickets No of tickets to be Valid Valid

required no of booked msg msg
tickets are
available

Reservation Check if the Used to reserve tickets No of tickets to be Valid Valid

required train booked msg msg
is available

cancellation Used to cancel Check whether the Ticket no,no of tickets Valid Valid
the ticket passenger is able to to cancel msg msg
before data of cancel the tickets
journey Ticket
cancel

search All info stored View passenger details Name,age,address,phone Valid Valid
in database no msg msg

32
ONLINE TICKET RESERVATION SYSTEM

=================================

#include <iostream>
using namespace std;

main ()

{
int uname, choice, reserve, cancel;

int seat = 30, new_seat = 0;

int password;

cout<<"Enter the username: ";

cin>>uname;

cout<<"Enter the Password: ";

cin>>password;

cout<<"\n\n";

cout<<"\n\t
MENU ";

cout<<"\n\t 1. Availability ";

cout<<"\n\t 2. Reserve ";

cout<<"\n\t 3. Cancel ";

cout<<"\n\t 4. Exit ";

cout<<"\n\t ";

cout<<"\n\n";

label :

cout<<"Enter your choice: ";

cin>> choice;

33
 switch(choice)

case 1:

cout<<"Available Seats :"<<seat;

break;

case 2:

cout<<"No. of seats to reserve: ";

cin>>reserve;

if (reserve > seat)

cout<<"You don't have sufficient seats";

else

new_seat = seat - reserve;

cout<<"Current available seats: "<< new_seat;

}

break;

case 3:

cout<<"Seats to cancel: ";

cin>>cancel;

new_seat = new_seat + cancel;

cout<<"successfully cancelled";

break;

34
 case 4:

cout<<"Thank you for using our service\n\n";

break;

default :
return 0;

if(choice<4)

goto label;

else

return 0;

Output
======

root@smvec:~# c++ railwaysys.cpp

root@smvec:~#./a.out

Enter the username: 123

Enter the Password: 456

MENU

1. Availability
2. Reserve
3. Cancel
4. Exit

Enter your choice: 1

Available Seats :30

Enter your choice: 2

35
No. of seats to reserve: 5

Current available seats: 25

Enter your choice: 3

Seats to cancel: 5

successfully cancelled

Enter your choice: 1

Available Seats :30

Enter your choice: 4

Thank you for using our service

36
EX.NO.4

ONLINE COURSE REGISTERATION SYSTEM

PROBLEM STATEMENT

This project deals with course registration system. Online course registration is easier and more
efficient. Rather than holding a registration day in an auditorium with paper and forms and manual
filling. The online course registration system allows the students to browse a list of courses at an
educational institution and register for that. register, add or drop a course. All information about the
courses available in that registration form. All students able to view their registered courses anywhere
in the registration system. Admins are the only one who providing the permission to access the
details. Here students have the freedom to register, add or drop a course. All information about the
courses available in that registration form. All students able to view their registered courses anywhere
in the registration system. Admins are the only one who providing the permission to access the details

USECASE DIAGRAM

37
SEQUENCE DIAGRAM

COLLOBRATION DIAGRAM

38
ACTIVITY DIAGRAM

39
CLASS DIAGRAM

COMPONENT DIAGRAM

40
TEST CASES

Name Requirements Description Input Expected Actual

output
Output
Log in User name & Used to verify User name, Valid Valid
password is correct authorized message message
Password
person

Log in User name & Used to verify User name, Invalid Invalid
password is authorized message message
Password
incorrect person

Course Course name is Used to check Number of Valid Valid

the course courses message message
availability Correct availability

Course Course name is Used to check Number of Invalid Invalid

the course courses message message
availability incorrect availability

Payment Card number & Check the Card Valid Valid

branch code is balance number, message message
correct branch code,

amount

Payment Card number & Check the Card Invalid Invalid

branch code is balance number, message message
incorrect branch code,

amount

COURSE REGISTRATION SYSTEM

#include<iostream>

#include<string.h>

using namespace std;

class coursereg

41
{

public:

string name;

string dob;

float percentage;

string qualification;

int year,cmp;

int dif,i;

int cash;

int jcount,ncount,pcount;

string username,username1,password,tmppassword;

int ip;

void get_details();

void login();

void pamplet();

void enroll();

void show_details();

};

void coursereg::get_details()

jcount=10;

ncount=10;

pcount=10;

cout<<"\n----------------------Course Registeration-----------------\n";

cout<<"\nEnter your name : ";

cin>>name;

42
cout<<"\nEnter your dob : ";

cin>>dob;

cout<<"\nEnter qualification & percentage : ";

cin>>qualification>>percentage; cout<<"\

nEnter your username : "; cin>>username;

cout<<"\nEnter your password: ";

cin>>password;

cout<<"\n--------------------Registration Complete------------------\n";

cout<<"\n Press 1 to login 2 to exit : ";

cin>>ip;

switch(ip)

case 1: login();

break;

default : cout<<"\nEnter the correct choice";

void coursereg::login()

cout<<"\n---------------------login----------------------------------\n";

cout<<"\nEnter the username : ";

cin>>username1;

cout<<"\nEnter the password :

"; cin>>tmppassword;

i=0;

43
while(password[i]!='\0'||tmppassword[i]!='\0')

dif=(password[i]-tmppassword[i]);

if(dif!=0)

break;

i++;

if(dif==0)

cout<<"\nLogin Successful";

cout<<"\n 1.View pamplet";

cout<<"\n 2.exit"; cout<<"\

nEnter your choice : ";

cin>>ip;

switch(ip)

case 1: pamplet();

break;

default : cout<<"\nEnter the correct choice";

}}}

void coursereg::pamplet()

cout<<"\n1.Name: CoureJava"<<"|"<<"Duration: 3months Available seats : "<<jcount;

cout<<"\n2.Name: .NET"<<"|"<<"Duration: 3months Available seats "<<ncount;

cout<<"\n3.Name: PHP"<<"|"<<"Duration: 3months Available seats : "<<pcount<<"\n";

cout<<"\n Enter your choice : ";

44
enroll();

void coursereg::enroll(){

cin>>ip;

switch(ip){

case 1: {

jcount=jcount-1;

cout<<"\n-----------------------Student details------------------------\n";

cout<<"\nName : "<<name;

cout<<"\nDOB : "<<dob; cout<<"\

nCourse Enrolled : Java";

cout<<"\n--------------Seat Availablity Details-----------------------\n";

pamplet();

}break;

case 2: {

ncount=ncount-1;

cout<<"\n-----------------------Student details------------------------\n";

cout<<"\nName : "<<name;

cout<<"\nDOB : "<<dob;

cout<<"\nCourse Enrolled : .Net";

cout<<"\n--------------Seat Availablity Details-----------------------\n";

pamplet();

}break;

case 3: {

pcount=pcount-1;

cout<<"\n-----------------------Student details------------------------\n";

45
cout<<"\nName : "<<name;

cout<<"\nDOB : "<<dob; cout<<"\

nCourse Enrolled : .PHP";

cout<<"\n--------------Seat Availablity Details-----------------------\n";

pamplet();

}break;

default: cout<<"\nEnter the correct choice\n";

}}

int main(){

coursereg c;

c.get_details();

OUTPUT:

----------------------Course Registeration------------------

Enter your name : krishnakanth

Enter your dob : 18/05/1995

Enter qualification & percentage : 12th 94

Enter your username : krishnakanth

Enter your password: def123

--------------------Registration Complete-------------------

Press 1 to login 2 to exit : 1

---------------------login-----------------------------------

Enter the username : krishnakanth

Enter the password : def123

Login Successful

1.View pamplet

46
2.exit

Enter your choice : 1

1.Name: CoureJava|Duration: 3months Available seats : 10

2.Name: .NET|Duration: 3months Available seats 10

3.Name: PHP|Duration: 3months Available seats : 10

Enter your choice : 1

----------------------Student details-------------------------

Name : krishnakanth

DOB : 18/05/1995

Course Enrolled : Java

--------------Seat Availablity Details------------------------

1. Name: CoureJava|Duration: 3months Available seats :

9 2.Name: .NET|Duration: 3months Available seats 10

3.Name: PHP|Duration: 3months Available seats : 10

Enter your choice : 2

-----------------------Student details-------------------------

Name : krishnakanth

DOB : 18/05/1995Course Enrolled : .Net

47
Ex.NO:5
ATM SYSTEM

PROBLEMSTATEMENT
Customers holding a bank account require convenient transactions on-the-go. A user-friendly, fool-
proof automated system is required to facilitate this. This is implemented by developing a system that
validates a customer login with his/her personal Account Number and PIN and providing them with a
facility to carry out withdrawals, depositions , PIN Change and Balance Enquiries. The system will
also keep track of the transactions that are carried out and retrieve his/her updated account balance
whenever required.

SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

1.INTRODUCTION

1.1 Purpose

This document describes the software requirements and specification for an automated teller machine
(ATM) network. The document is intended for the customer and the developer (designers, testers, mai
ntainers).

1.2 Scope

The network enables customers to complete simple bank account services via automated
teller machines (ATMs) that may be located off premise and that need not be owned and operated b
y the customer’s bank. The ATM identifies a customer by a cash card and password. It collects info
rmation about a simple account transaction (e.g.,deposit, withdrawal,transfer, bill payment),commu
nicates the transaction information to the customer’s bank, and dispenses cash to the customer. The
banks provide their own software for their own computers

1.3 DEFINITIONS,ACRONYMS AND ABBREVATIONS

Account

A single account at a bank against which transactions can be applied. Accounts may be of various type
s with at least checking and savings. A customer can hold more than one account.

MaxDailyWD

The maximum amount of cash that a customer can withdraw from an account in a day

(from 00:00 AM to 23:59 PM) via ATMs.

PIN

48
It refers to Personal Identification Number. Used to identify and validate the login of an ATM user.

1.4 REFERENCES

1. www.google.com
2. www.scribd.com
3. Ali Bahrami –Object Oriented System Development.
4. Complete reference for visual basic-6.0

1.5 TECHNOLOGIES TO BE USED

1. Language to be used : Visual basic-6.0

2. Tools to be used : Agro UML

1.6 OVERVIEW

The first topic of the SRS provides information about the users and for what and
where they require this software It gives the external behavior of the system and design constraints .

The second topic of SRS describes the functionalities and design of the system. It
also provides the feasibility of the system and the assumptions on which the system is built.

The third topic of SRS describes the Operational and supplementary requirements for
building that system.

2. OVERALL DESCRIPTION

2.1 Product Perspective

An automated teller machine (ATM) is a computerized telecommunications device that provide

the customers of a financial institution with access to financial trnsactions in a public space without th
e need for a human clerk or bank teller. On most modern ATMs, the customer is identified by inserting
a plastic ATM card with a magnetic stripe or a plastic smartcard with a chip, that contains a unique
card number and some security information, such as an expiration date or CVC (CVV). Security is pro
vided by the customer entering a personal identification number (PIN).

2.2 Product functions

Using an ATM, customers can access their bank accounts in order to make cash withdrawals (or credit
card cash advances) and check their account balances.

The functions of the system are:

1. Login

2. Get Balance Information

49
 3. Withdraw Cash

4. Generate receipt

a)login

This is a use case used to verify the authentication of the user.In this the user gives his allotted
pin number as input ,the system then verifies whether the card number and pin number stored in data
base matches or not ,if it matches then it allows the user to use the system else it asks to enter the pin
number again.

b) balance inquiry

This use case is used to check the balance in the user account.After every transaction the balance
in the user’s account is updated by taking data consistency into consideration and the updated account
balance is displayed to the user.

c) withdrawal

This use case facilitates the user to withdraw money from his account.After the money is
withdrawn it is updated in the user’s account.

d) generate receipt

This use case is used to generate receipt for the transaction made by the user.

2.3. Assumptions and Dependencies

1. Hardware never fails

2. ATM casing is impenetrable

3. Limited number of transactions per day (sufficient paper for receipts)

4. Limited amount of money withdrawn per day (sufficient money )

3. SUPPORTING INFORMATION

ANALYSIS MODELS

1. Usecase diagram

2.Activity diagram

3.Sequence diagram

4.collaboration diagram

5.class diagram

50
 6.component diagram

7.deployment diagram

4. Non-Functional Requirements

 Reliability

 Maintainability

 Supportability

 Performance

Result:

 Thus the software requirement specification report for ATM system has been completed.

DATA DICTIONARY

51
USECASE DIAGRAM

52
ACTIVITY

53
CLASS DIAGRAM

COLLABORATION DIAGRAM

54
SEQUENCE DIAGRAM

55
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

56
TEST CASES

ATM SYSTEM
==========

#include <iostream>
using namespace std;
main ()
{
int card_number, choice, withdraw, deposit;
float amount = 3000.00, new_amount = 0;
int password;
cout<<"Enter the card number: ";
cin>>card_number;
cout<<"Enter the Password: ";
cin>>password;
cout<<"\n\n";
cout<<"\n\t MENU ";
cout<<"\n\t 1. Check Balance ";
cout<<"\n\t 2. Withdraw ";
cout<<"\n\t 3. Deposit ";
cout<<"\n\t 4. Exit ";
cout<<"\n\t ";
cout<<"\n\n";
label :
{
cout<<"\nEnter your choice: ";
cin>> choice;
switch(choice)
{
case 1:

57
 cout<<"Current balance on
your account: "<<amount;

break;

case 2:

cout<<"Enter the amount you want to withdraw: ";

cin>>withdraw;
if (withdraw > amount)
{

cout<<"You don't have sufficient balance";

}
else
{
new_amount = amount - withdraw;
cout<<"Current balance on
your account: "<< new_amount;

}
break;

case 3:
cout<<"Enter the amount you want to deposit: ";
cin>>deposit;
new_amount = new_amount + deposit;
cout<<"Current balance on
your account:"<< new_amount;
break;

case 4:
cout<<"Thank you for using our service\n\n";
break;
default : return 0;
}
}
if(choice<4)
goto label;
else
return 0;

58
}
Output
======

root@smvec:~# c++ atm1.cpp

root@smvec:~# ./a.out
Enter the card number: 111
Enter the Password: 333

MENU
1. Check Balance
2. Withdraw
3. Deposit
4. Exit
Enter your choice: 1
Current balance on your account: 3000
Enter your choice: 2
Enter the amount you want to withdraw: 500
Current balance on your account: 2500 Enter
your choice: 3
Enter the amount you want to deposit: 1000
Current balance on your account: 3500 Enter
your choice: 4
Thank you for using our service

59
EX.NO 6

PLATFORM ASSIGNMENT SYSTEM FOR THE TRAINS IN A RAILWAY STATION

PROBLEM STATEMENT

The station in which several trains might stop at the same platform at the same time.
Trains might enter and leave the station to both sides, but the arrival and departure times and
directions are fixed according to a give time table. The problem is to assign platforms to the trains
such that they can enter and leave the station in time without login blocked by any other train.

DATA DICTIONARY

NAME ALIAS NAME WHERE/HOW DATATYPE LIMITATION

USED
Admin - Authentication String Upto 10 character
Platform no - For assignment of Integer It should be 1 no
platform for trains and should not
start with 1 or 0
Train name Express name Verification of String Upto 5 characters
train details
Arrival time - Used to compare Integer It should be in the
with other trains format of railway
arrival time and to time.
assign the arrival
time.

60
USECASE DIAGRAM

61
ACTIVITY DIAGRAM

62
CLASS DIAGRAM

SEQUENCE DIAGRAM

63
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

64
DEPLOYMENT DIAGRAM

TEST CASES
NAME REQUIREMENT DESCRIPTION INPUT EXPECTED ACTUAL
OUTPUT OUTPUT

Login Admin name and Used to verify the Admin Authentication Valid
password should authorized name and verified. message.
be correct. person. password

Login Admin name and Used to verify the Admin Invalid Invalid
password should authorized name and message. message.
be incorrect. person. password

Platform Train specification Used to assign Train Platform Platform

assignment is valid platform for arrival/ assigned assigned
system trains depature
time

Platform Train specification Used to assign Train Platform not Platform

assignment is invalid platform for arrival/ assigned not
system trains depature assigned
time

Availability - To check Integer Return:

whether platform Yes-avaliable,
is available or No –not
not
65
 avaliable

PLATFORM ASSIGNMENT FOR TRAINS IN RAILWAY STATION

=================================================

#include<iostream>

using namespace std;

class plat

public:

string tname,username,username1,

password,tmppassword;

int pno;

int n,ip,i;

int dif;

string atime,dtime;

int tno;

void authentification_details();

void login();

void get_traindetails();

void platform_controller();

};

void plat::authentification_details()

cout<<"\nEnter your username : ";

cin>>username;

cout<<"\nEnter your password: ";

66
cin>>password;

cout<<"\n--Registration Complete- - -\n

cout<<"\n Press 1 to login ,2 to exit : ";

cin>>ip;

switch(ip)

case 1: login();

break;

default:

cout<<"\nexit\n";

void plat::login()

cout<<"\n--login-------\n";

cout<<"\nEnter the username : ";

cin>>username1; cout<<"\

nEnter the password : ";

cin>>tmppassword;

i=0;

while(password[i]!='\0'||tmppassword[i]!='\0')

dif=(password[i]-tmppassword[i]);

if(dif!=0)

cout<<"\n Invalid username";

67
break;

i++;

if(dif==0)

cout<<"\nLogin Successful";

void plat::get_traindetails()

int n=5;

cout<<"\n---Platform assignment

system in train details---";

cout<<"\n1.A Train";

cout<<"\n--Platform -1 details----";

cout<<"\nEnter the train-A ARRIVAL TIME:";

cin>>atime;

cout<<"Enter the Train-A DEPARTURE TIME:";

cin>>dtime;

cout<<"\n2.B Train";

cout<<"\n---------Platform 2 details-----------";

cout<<"\nEnter the train-B ARRIVAL TIME:";

cin>>atime;

cout<<"Enter the Train-B DEPARTURE TIME:";

cin>>dtime;

cout<<"\n3.C Train";

68
cout<<"\n--------Platform -3 details------------";

cout<<"\nEnter the train-C ARRIVAL TIME:";

cin>>atime;

cout<<"Enter the Train-C DEPARTURE TIME:";

cin>>dtime;

cout<<"\n4.D Train";

cout<<"\n---------Platform 4 details-----------";

cout<<"\nEnter the train-D ARRIVAL TIME:";

cin>>atime;

cout<<"Enter the Train-D DEPARTURE TIME:";

cin>>dtime;

cout<<"\n5.E Train";

cout<<"\n----------Platform -5 details----------";

cout<<"\nEnter the train-E ARRIVAL TIME:";

cin>>atime;

cout<<"Enter the Train-E DEPARTURE TIME:";

cin>>dtime;

cout<<"\nmaximum allocated platform is =\n"<<n;

void plat::platform_controller()

cout<<"\nENTER THE NEW TRAIN NUMBER:";

cin>>tno;

cout<<"\n---check availability for platform- - - -";

if(tno<=n)

cout<<"\n Available for platform";

69
else

cout<<"\n PLATFORM ARE NOT AVAILABLE\n";

int main()

int ch;

plat p;

p.authentification_details();

do

cout<<"\n1.Enter the train details";

cout<<"\n2.Assign platform";

cout<<"\nEnter the choice : ";

cin>>ch;

switch(ch)

case 1: p.get_traindetails();

break;

case 2: p.platform_controller();

break;

default:

cout<<"\n

Enter the correct choice:\n";

70
while(ch<=2);

OUTPUT

======

root@smvec:~/SE_lab# c++ plats.cpp

root@smvec:~/SE_lab# ./a.out

Enter your username : ram

Enter your password: ram

-Registration Complete

-----Press 1 to login ,

2 to exit : 1

login

Enter the username : ram

Enter the password : 123

1.Enter the train details

2.Assign platform

Enter the choice : 1

-Platform assignment system in train details----

1.A Train

----Platform -1 details----:

Enter the train-A ARRIVAL TIME:10

Enter the Train-A DEPARTURE

TIME:12

2.B Train

--Platform 2 details---:

Enter the train-B

ARRIVAL TIME:11
71
Enter the Train-B

DEPARTURE TIME:12

3.

C Train

-------Platform -3 details------------:

Enter the train-C ARRIVAL TIME:9

Enter the Train-C DEPARTURE

TIME:10 4.

D Train

---------Platform 4 details-----------:

Enter the train-D ARRIVAL TIME:8

Enter the Train-D DEPARTURE

TIME:10 5.

E Train

----------Platform -5 details----------:

Enter the train-E ARRIVAL TIME:8

Enter the Train-E DEPARTURE

TIME:1 maximum allocated platform is

1.

Enter the train details

2.

Assign platform

Enter the choice : 2

72
EX.NO 7:

EXPERT SYSTEM FOR PRESCRIBING THE MEDICINES

PROBLEM STATEMENT

This project is used to identify an ailment by its symptoms and return a result prescribing an
appropriate medicine corresponding to the disease. It is well known that developing countries are
facing lots of shortage of medical expertise. This expert system is a system that employs human
knowledge captured in computer to solve problems that ordinarily required by human.

DATA DICTIONARY

Patient details

73
USECASE DIAGRAM

74
ACTIVITY DIAGRAM

75
CLASS DIAGRAM

COLLABORATION DIAGRAM

76
SEQUENCE DIAGRAM

77
COMPONENT DIAGRAM

DEPLOYMENY DIAGRAM

78
TEST CASES

EXPERT SYSTEM FOR PRESCRIBING THE MEDICINES

#include<iostream>

using namespace std;

int password;

class medicalexpert

public:
string name,id,sex;

int age,dozage,option;

void entry()

cout<<"login the system";

cin>>id;

79
cout<<"\nenter the password";

cin>>password;

if(password==123)

{
cout<<"\nlogin successfull";
}
else
{
cout<<"\npassword is incorrect";
}
}
void symptoms()
{

cout<<"\nenter the symptoms nd diseases";

cout<<"\n1.fever-malaria"; cout<<"\

n2.headache-migrane"; cout<<"\

n3.stomachache-ulcer"; cout<<"\

n4.vomitting-thyphoid";

void prescription()
{
cout<<"\nprescribe the medicine";

cout<<"\nenter option";

cin>>option;

switch(option)

case 1:
cout<<"\nfound fever";
cout<<"\nmedicine-calpol";
break;
case 2:
cout<<"\nfound headache";

80
cout<<"\nmedicine-sinearest";
break;
case 3:
cout<<"\nfound stomachace";
cout<<"\nmedicine-buscopen";
break;
case 4:
cout<<"\nfound vomitting";
cout<<"\nmedicine-avomin";
break;
}
}
};

int main()
{
medicalexpert m;
m.entry();
if (password==123)
{
m.symptoms();
m.prescription();
}

OUTPUT
======
root@smvec:~/SE_lab# c++ ME.cpp
root@smvec:~/SE_lab# ./a.out
login the systemram
enter the password123
login successfull
enter the symptoms nd
diseases 1.fever-malaria
2.headache-migrane
3.stomachache-ulcer
4.vomitting-thyphoid
prescribe the medicine
enter option1
found fever
medicine-calpolroot@smvec:~/SE_lab#

81
EX.NO: 8

QUIZ SYSTEM

PROBLEM STATEMENT

The quiz system deals with the problem in evaluating the competency of the person taking the quiz
.Developing a quiz system includes both the user and the administrator is privileged to prepare the
quiz questions for the users based on the selected category. The users are allowed to take the quiz by
choosing the categories displayed. The competency of the user is evaluated at the end by displaying
the score obtained by the user in the quiz that he undertook. The quiz system can be used to evaluate
the competency of person taking quiz. It is used to recruit skilled employees.

DATA DICTIONARY

82
USECASE DIAGRAM

83
ACTIVITY DIAGRAM

84
CLASS DIAGRAM

SEQUENCE DIAGRAM

85
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

86
DEPLOYMENT DIAGRAM

/* QUIZ SYSTEM */

#include<iostream>
using namespace std;
main()
{
int x,y,z;
x=y=z=0;
char ch1[100],ch2,ch3,ch4,ch5,ch6,
ch7,ch8,ch9,ch10,ch11;
cout<<"Guest Enter Your Name\n";
cin>>ch1;
cout<<"WELCOME TO ONLINE QUIZ SYSTEM\n";
cout<<"Enter answer in form of a,b and c only.\n";
cout<<"What is called as THE HOLY LAND? \n";
cout<<"a.Jerusalem\n";

87
cout<<"b.mathura\n";
cout<<"c.mecca\n";
cin>>ch2;
if(ch2=='a')
{ x=x+1
0;
cout<<"Good Job.Your score is "<<x;
}
else
cout<<"sorry wrong answer.\n";
cout<<"\nWhat is called as THE ROOF OF THE WORLD?
\na.Nepal\nb.Rome\nc.Tibet\n";
cin>>ch2;
if(ch2=='c')
{ x=x+1
0;
cout<<"Good Job Your score is\n" <<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"\nWhat is called as THE LAND OF RISING SUN?
\na.Chicago\nb.Japan\nc.Tibet\n";
cin>>ch2;
if(ch2=='b')
{ x=x+1
0;
cout<<"Good Job Your score is \n"<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE GIFT OF NILE?
\na.Chicago\nb.Egypt\nc.Africa\n";
cin>>ch2;
if(ch2=='b')
{ x=x+1
0;
cout<<"Your score is\n" <<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE LAND OF MIDNIGHT SUN?
\na.norway\nb.japan\nc.australia\n";

88
cin>>ch2;
if(ch2=='a')
{ x=x+1
0;
cout<<"Your score is\n"<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE LAND OF THUNDERBOLT?
\na.Bhutan\nb.Canada\nc.Arab\n";
cin>>ch2;
if(ch2=='a')
{ x=x+1
0;
cout<<"Your score is\n"<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE WINDYCITY?
\na.Jerusalem\nb.Japan\nc.Chicago\n";
cin>>ch2;
if(ch2=='c')
{ x=x+1
0;
cout<<"Your score is\n"<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE LAND OF WHITEELEPHANTS?
\na.Bangladesh\nb.Thailand\nc.India\n";
cin>>ch2;
if(ch2=='b')
{ x=x+1
0;
cout<<"Your score is\n"<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE CITY OF SEVENHILLS?
\na.Rome\nb.Nilgiri Hills\nc.Tibet\n";

89
cin>>ch2;
if(ch2=='a')
{ x=x+1
0;
cout<<"Your score is\n "<<x;
}
else
cout<<"Sorry wrong answer\n";
cout<<"What is called as THE DARKCONTIENENT?
\na.Asia\nb.Australia\nc.Africa\n";
cin>>ch2;
if(ch2=='c')
{ x=x+1
0;
cout<<"our score is\n"<<x;
}
else
cout<<"Sorry wrong answer\n";
if(x==100)
cout<<"fantastic.your score is 100\n";
if(x==90)
cout<<"You are extremely intelligentYour Score is 90?\n";
if(x==80)
cout<<"You are intelligentYour Score is 80?\n";
if(50==x||x==70||x==60)
cout<<"You are averageYour Score is
"<<x<< "Better luck nexttime\n";
else if(x<=40)
cout<<"No use.. Not even 5 questions right\n";
}
/*

OUTPUT
======
i3205066@SMVEC:~$ c++ ooo.cpp
i3205066@SMVEC:~$ ./a.out Guest
Enter Your Name
nivedha

WELCOME TO ONLINE QUIZ SYSTEM

Enter answer in form of a,b and c only.

90
What is called as THE HOLY LAND?
a.Jerusalem
b.mathura
c.mecca

Good Job.
Your score is 10

What is called as THE ROOF OF THE

WORLD? a.Nepal
b.Rome
c.Tibet

Good Job
Your score is
20

What is called as THE LAND OF RISING SUN?

a.Chicago
b.Japan
c.Tibet

Good Job
Your score is
30

What is called as THE GIFT OF NILE?

a.Chicago
b.Egypt
c.Africa

91
Your score is
40
What is called as THE LAND OF MIDNIGHT SUN?
a.norway
b.japan
c.australia

Your score is
50

What is called as THE LAND OF THUNDERBOLT?

a.Bhutan
b.Canada c.Arab
c.Burma

Sorry wrong answer

What is called as THE WINDYCITY?

a.Jerusalem
b.Japan
c.Chicago

Your score is
60

What is called as THE LAND OF WHITEELEPHANTS?

a.Bangladesh
b.Thailand
c.India

92
Your score is
70

What is called as THE CITY OF SEVENHILLS?

a.Rome
b.Nilgiri Hills
c.Tibet

Your score is
80

What is called as THE DARKCONTIENENT?

a.Asia
b.Australia
c.Africa

your score is
90

You are extremely intelligent

Your Score is 90

i3205066@smvec~$ */

93
EX.NO.9

STUDENT MARK ANALYSIS SYSTEM

PROBLEM STATEMENT

This project deal with the student mark analysis system is used to calculate particular
student marks, total, average, grade and remarks. It also keep's a track of the student
marks in the semester there pass and fail percentage in each subject. Other than these it
also holds details of students like name, id, course enrolled subject offered under the
course, faculty regarding the course, address and other personal details. We can perform
add, update, delete, calculate the particular student mark. This also helps to automate
and increase data accuracy, make information management more secure, convenient
effective and accessible. It also maintains student attendance record.

DATA DICTIONARY

Student Mark Details

94
USECASE DIAGRAM

95
ACTIVITY DIAGRAM

96
CLASS DIAGRAM

SEQUENCE DIAGRAM

97
COLLABORATION DIAGRAM

COMPONENT DIAGRAM

98
DEPLOYMENT DIAGRAM

TEST CASES

STUDENT MARK ANALYSIS SYSTEM

#include<iostream>

#include<string>

using namespace std;

class student
99
{
string name;

int i;

int roll;

int m[6];

int total;

int avg;

char grade;

public:
void getdata();

void totalmar();

void avg1();

void grade1();

void display();

};

void student::getdata()
{
cout<<"Enter the name:";
cin>>name; cout<<"\nEnter
the roll:"; cin>>roll;
cout<<"\nEnter the marks:";
for(i=0;i<6;i++)
cin>>m[i];
}

void student::totalmar()
{
total=0;
for(i=0;i<6;i++)
total=total+m[i];
}

void student::avg1()
{
avg=total/6;
}

void student::grade1()
{
if(avg>90 ) grade='A';
else if(avg >80)
grade='B';
else if(avg>70)
grade='C'; else
if(avg>60)
grade='D'; else
if(avg>50)
grade='E'; else
grade='F';
}

void student :: display()

{
cout<<"name:"<<name<<"\n";
cout<<"rollno:"<<roll<<"\n";
cout<<"total:"<<total<<"\n";
cout<<"average:"<<avg<<"\n";
cout<<"grade:"<<grade<<"\n";
}

int main()
{
student s;
s.getdata();
s.totalmar();
s.avg1();

s.grade1();
s.display();
return 0;
}

OUTPUT:
Enter the Name:ALBIN
Enter the Roll:5001 Enter
the Marks:90
99
98
100
99
98

name:ALBIN
rollno:5001
total:584
average:97
grade:A
EX.NO :10

STOCK MAINTENANCE

PROBLEM STATEMENT:

Stock maintenance gives an idea about how the products are maintained in stores. Now a day’s people
should purchase things in store so the stores must be maintaining the product details and stock details.
The stock maintainace have the details about product code.no and all other information. By using all
this information people can easily purchase goods easily. Stock maintenance ensures that the shop has
sufficient stock of whatever products. This system analyze what goods are needed and what goods are
expired ones so it is easy to purchase goods.

DATA DICTIONARY

Product Details
SNO NAME ALIAS WHERE SUPPLEMENTARY DATA
NAME USED/HOW DATA TYPE PRESENT LIMITATION
USED VALUE
1. Product - Billing, string - Up to 20
name viewing, characters
product
details
2. Product - Viewing integer - Up to 5
number product character
details
3. cost - For billing integer - Up to 8
viewing character
product
details
4. quantity - Billing, integer - Up to 5
viewing character
product
details
Customer Details
SNO NAME ALIAS WHERE SUPPLEMENTARY DATA
NAME USED/HOW DATA PRESENT LIMITATION
USED
TYPE VALUE
1. Customer - Viewing the string - Up to 20
name customer characters
details
2. Customer - Viewing the integer - Up to 5
number customer character
details
3. address - Viewing the string - Up to 180
customer character
details
4. Phone - Viewing the integer - Up to 11
number customer character
details

USECASE DIAGRAM
ACTIVITY DIAGRAM
CLASS DIAGRAM

SEQUENCE DIAGRAM
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM
TEST CASES
NAME REQUIREMENT DESCRIPTION INPUT EXPECTED ACTUAL
OUTPUT OUTPUT
login User name and Used to verify if User name, Valid Valid
password should the actor is password message message
be entered authorized
person or not
login User name and Used to verify if User name, Not Valid Not Valid
password should the actor is password message message
be entered authorized
person or not
billing Check if the The availability Product Product Product
required product is number of name, available available
available particular quantity message message
product is
retrieved from
data base
billing Check if the The availability Product Not available Not
required product is number of name, message available
available particular quantity message
product is
retrieved from
data base
Product Product name, The availability Product Display Display
details product number, of product is name product product
quantity cost retrieved from details details
database
Product Product name, The availability Product Not available Not
details product number, of product is name message available
quantity cost retrieved from message
database
Customer Customer name, Customer details Customer Display Display
details address, phone is retrieved from name customer customer
number data base details details
Customer Customer name, Customer details Customer Not available Not
details address, phone is retrieved from name message available
number data base message
STOCK MAINTENANCE SYSTEM
========================

#include <iostream>
using namespace std;
main ()
{
int username, choice, sales, purchase;
float stock = 30, new_stock = 0;
int password;
cout<<"Enter the Username: ";
cin>>username;
cout<<"Enter the Password: ";
cin>>password; cout<<"\n\n";
cout<<"\n\t
MENU ";
cout<<"\n\t 1. Stock Available ";
cout<<"\n\t 2. Sales ";
cout<<"\n\t 3. Purchase ";
cout<<"\n\t 4. Exit ";
cout<<"\n\t ";
cout<<"\n\n";

label :

cout<<"\nEnter your choice: ";

cin>> choice;
switch(choice)
{
case 1:
cout<<"Current Stock Available: "<<stock;
break;
case 2:
cout<<"Enter the quantity you want to Sales: ";

cin>>sales;

if (sales > stock)

 {

cout<<"You don't have sufficient stock";

else if (sales < stock)

cout<<"Stock not available";

else
{

new_stock = stock - sales;

cout<<"Current Stock Available: "<< new_stock;

break;

case 3:

cout<<"Enter the quantity you want to purchase: ";

cin>>purchase;

new_stock = new_stock + purchase; cout<<"Current

Stock Available: "<< new_stock;

break;

case 4:

cout<<"Thank you for using our service\n\n";

break;

11
default : return 0;

if(choice<4)

goto label;

else return

0;

Output

======

root@smvec:~# c++ stock.cpp

root@smvec:~# ./a.out

Enter the Username: 123

Enter the Password: 123

MENU

1. Stock Available
2. Sales
3. Purchase
4.Exit

11
Enter your choice: 1 Current

Stock Available: 30 Enter

your choice: 2

Enter the quantity you want to Sales: 10

Current Stock Available: 20

Enter your choice: 3

Enter the quantity you want to purchase: 20 Current

Stock Available: 40

Enter your choice: 4

Thank you for using our system

11
EX.NO 11

EMAIL CLIENT SYSTEM

PROBLEM STATEMENT

Email client is a primarily a desktop application that enables users to receive and send emails directly
on their desktop. Typically email client requires an email address to set up and configured because
user can start using email service. These configuration and settings generally include email address,
port number, email aliases and other related preferences.

USECASE DIAGRAM

11
ACTIVITY DIAGRAM

CLASS DIAGRAM

11
SEQUENCE DIAGRAM

COLLABORATION DIAGRAM

11
COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

11
DATA DICTIONARY

EMAIL CLIENT SYSTEM

===================
composer.cpp
#include "composer.h"
void composer::edit()
begin
{
}
void composer::send()
begin
{
}
void composer::compose()
begin
{
}

composer.h
#ifndef composer_h
#define composer_h
class composer
{

11
public:
virtual void edit();
virtual void send(); virtual
void compose(); public:
String msg;
String text;
};
#endif //
composer_h

mail.cpp

#include "mail.h"
void mail::check mail()
begin
{
}
delete mail()
begin
{
}
element
mail.h

#ifndef mail_h
#define mail_h
class mail
{
public:
virtual
void check mail();
virtual
void delete mail();

11
public:
String read reply;
};
#endif

webserver.cpp
#include "webserver.h"
void webserver::control client()
begin
{
}
end
webserver.h
#ifndef webserver_h
#define webserver_h
class webserver
{
public:
virtual
void control client();
};

#endif // webserver_h

11
TEST CASES
EX.NO.12

REMOTE COMPUTER MONITORING

PROBLEM STATEMENT

This project deals with remote computer monitoring. Remote computer monitoring is the act of
monitoring a computer from a different location. A computer monitor is an output device that is used
as an electronic visual display for computer. It is used to design and collect information for remote
monitoring. It can control all your computers found in your office and remote branches. You can
control all activities made daily by personal with its easy and safe use. It is an easy program produced
for administrators of each size of team and team leader. It can also store old history from monitoring

DATA DICTIONARY

Server Details

S.No Name Alias Name Where Used Supplementary

How Used

Data
Datatype Limitation
1 client User name monitor string Upto 20
character
2 server - monitor string Upto 20
character
3 IP address - monitor double Upto 20
USECASE DIAGRAM
ACTIVITY DIAGRAM
CLASS DIAGRAM

SEQUENCE DIAGRAM
COLLABORATION DIAGRAM

COMPONENT DIAGRAM
DEPLOYMENT DIAGRAM