60780174 49594067-cs1403-case-tools-lab-manual

CS1403 CASE TOOLS LAB 0 0 3 100
1. Prepare the following documents for two or three of the experiments listed below and
develop the software engineering methodology.
1. Program Analysis and Project Planning.
Thorough study of the problem – Identify project scope, Objectives, Infrastructure.
3. Software requirement Analysis
Describe the individual Phases / Modules of the project, Identify deliverables.
4. Data Modeling
Use work products – Data dictionary, Use diagrams and activity diagrams, build and test lass
diagrams, Sequence diagrams and add interface to class diagrams.
5. Software Development and Debugging
6. Software Testing
Prepare test plan, perform validation testing, Coverage analysis, memory leaks, develop test
case hierarchy, Site check and Site monitor.
SUGGESTED LIST OF APPLICATIONS
1. Student Marks Analyzing System
2. Quiz System
3. Online Ticket Reservation System
4. Payroll System
5. Course Registration System
6. Expert Systems
7. ATM Systems
8. Stock Maintenance
9. Real-Time Scheduler
10. Remote Procedure Call Implementation

RATIONAL ROSE
A process is a set of partially orders steps intended to search a goal, in software
engineering the goal is to build a software product or to enhance an existing one, in process
engineering. The goal is to develop or enhance a process. In RUP (Rational Unified Process)
there are organized into set of disciplines to further define the work flows and work process
elements.
Expressed in terms of business modeling, the software development process is a business
process the RUP is a general business protocol for Object Oriented Software Engineering
Process sharing a common structure, common process architecture. It provides a disciplined
approach to assigning tasks and responsibilities. Within a development organization in its goal
and to ensure the production of high quality software that meets the needs of its end user
within a predictable schedule and budget.
The RUP captures many of the best practices in modern software development in a form
that can be tolerable for a wide range of product.
When a software system is developed from scratch development is the process of creating
a system from requirement. But once the system has taken from any further development is
the process of confirming this system, to the new modified requirements. This applies
throughout the system lifecycle.
NEW OF CHANGED CHANGED
SYSTEM
The Software engineering process is the
process of developing a System from the requirement
either new or changes (Evolution Cycle).
Rational Rose helps companies overcome the e-software paradox by unifying the
communities that develop software with a common visual language that accelerates the
creation of flexible application with rousts, resilient architectures.
RATIONAL ROSE SOFTWARE:
ANALYSIS AND DESIGN:
The application’s method recommends the use of static and dynamic views of a logical
model and a physical model to capture the in-process products of object oriented analysis and
design. Using the notations, the application enables you to create and refine these views
within an overall model representing your problem domain and software system.
This overall model contains Classes, Use Cases, Objects, Packages, Operations, Components
Packages, Components, Processors, Devices and the relationship between them. A model also
contains diagrams and specification, which provides a means of visualizing and manipulating
the models elements and their model properties.
It is software developed by Rational Corporation. It contains the information interface and
the tools to create a visual model. In rose there are different views. A view is a perspective of
a model. The FIVE different views called Architectural views are:
SOFTWARE
ENGINEERING PROCESS

1. USE CASE VIEW:
• Contains the use case model, flow of events and supplementary
documentations.
• It is contract between customer and developer
• It is essential for Analysis, Design the test activities
• It also contains activity diagrams
• It contains the use case diagrams
• It includes the threads and the processes that found the System Concurrency it
is the heart if the other views that represent the required behaviors of the
System.
2. LOGICAL VIEW:
• It supports the functional requirements of the System
• It includes the use case realizations, Class diagrams, Interaction diagrams, State
Chart diagrams, and Activity diagrams
3. PROCESS VIEW:
• It address the Performance, Scalability and throughout the System
• It is not necessary for Single Processing Environment
4. COMPONENT VIEW:
• The Component view addresses the case of development management of
Software assets, reuse, subcontracting, and shelf components.
• Describes the organization of static software like Course call data file
components.
5. DEPLOYMENT VIEW:
• It addresses the view like Deployment, Installation and Performance.
• The Deployment is used for Distributed Systems only.

EX. NO: 1
STUDENT MARK ANALYSIS SYSTEM
AIM:
To analyze and design a Student Mark Analysis System using UML (Unified Modeling
Language) diagram.
PROJECT SCOPE:
The main scope of this project is to get the students marks and update it whenever
necessary and then to display it for the Students and Faculties.
OBJECTIVE:
The main objective of designing and implementing this project is to enable the students and
the faculties to see the marks easily.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS:
• Processor: PENTIUM IV
• Capacity: 256MB of RAM
SOFTWARE REQUIREMENTS:
• Rational Rose Software
PROBLEM STATEMENT:
Student Mark Analysis system is used for the Students and the faculty to have an easy
access for viewing the marks. It also makes the work simpler.
Here in this the students can only view the marks if their Username and the Password are
correct. They do not have the permission to change or update the marks. It is only the faculty
who can update and view the students mark. It is also the duty of the faculty to distribute the
report cards, the duty of the administrator, is to generate the report card and he/she can view
the report cards. But the administrator cannot update cards. All these processes are done
efficiently and easily in this Student Mark Analysis System.
ABSTRACT:
This project “Student Mark Analysis” deals with the complete details of academic details of
the Student. It comprises of the student Roll no, Name, Marks Obtained, Total, Average,
Attendance Percent etc. It can be accessed by the teacher or the faculty who alone can
change or update the marks of the students, it is also duty of the faculty to distribute the
records maintain the records, the duty of the administrator is to generate the report cards to
the faculty members. The faculty will calculate the total marks and them based on the
percentage obtained by the student he/she will be awarded the grades. Here the role of the
student is to just view the marks entered by the faculty of the teacher, this project is
constructed with modularity which helps in the easy understanding of the project and
instances access of the student’s data.
MODULAR DESCRIPTION:

GENERATE REPORT CARDS:
This module allows the faulty to generate the report cards that are going to contain the
Student’s academic details.
UPDATE GRADES:
This module allows the faculty to update grades and then to update the marks of the
students whenever the semester of the examination results are released.
SAVE GRADES:
Save Grades is used to save the grade that has been allotted to Students.
LOAD GRADES:
The Load Grades allows us to load the updated grade to the Report card.
VIEW GRADES:
This module allows the faculties as well as the Students to view the Grades, Marks, Total
and the Average Marks obtained by the Student. This is the only module that can be accessed
by the Student when the User name and the Password Matches.
Class Diagram:
G e n e ra te R e p o rt c a rd
roll n o : in t
n a m e : s trin g
a d d re s s : s tring
m a rk s : in t
tota l()
a vg()
g e n e ra te ()
R e c o rd G ra d es
m a rk s : in t
roll n o : in t
c h e c k ()
p rin t()
tota l()
a vg()
U p d a te G ra de s
roll n o : in t
u p d a te m a rk : in t
u p d a te ()
V iew G ra des
g e t p w d
u s e r n am e : s trin g
c h e c k ()
vie w ()
Component View:
Student Mark Analysis System
Use-Case Diagram:

Save Grades
Load Grades
Distributed Report Card
Recard Grades
Upgrade Grades
Generate Report Card
Teacher
Administrator Student
Log on
View grades
Collaboration Diagram:
Admin Teacher Student
2: Req. for report card
4: Provide the detail
3: Ask for student detail
5: provide report card
1: Req. for report card
6: Distribute report card
Sequence Diagram:

Admin Teacher Student
Req. for report card
Req. for report card
Ask for student detail
Provide the detail
provide report card
Distribute report card

Activity Diagram:
Distribution Of Report Card:
STUD REQ FOR
REPORT CARD
TEACHER COLECTS
REPORT FROM ADMIN
DISTRIBUTE
TO STUDENT
Update Report:
Log on
Select student
Update mark

Generate Report:
Enter roll no
Enter name
Enter address
Enter marks
Enter total
Enter the
Average
Enter the
grades

Load Report:
SELECT THE
STUDENT
DISPLAY THE
GRADE
STOP
Save Report:
GET THE
DETAILS
SAVE THE
GRADE
sTP

Record Details of Report:
Get average
if Avg<50
if AVG<60
no
if avg<=75
no
if avg>75
no
failYES
c gradeYES
b gradeyes
a gradeyes
STOp
no
Deployment Diagram:
STUDENT
MARK LIST
STUDENT 1
STUDENT 2
STUDENT 3
STUDENT 4
STUDENT
NAME

EX. NO: 2
ONLINE QUIZ MANAGEMENT SYSTEM
AIM:
To design and develop the Quiz Management System for organizing efficient quiz Programs
and to produce the results using the Rational Rose Software.
PROJECT SCOPE:
The quiz management system is developed after the completion of all necessary. UML
Components diagram which offers higher reliability and efficiency in handling the development
system. The development system plays a vital role irrespective of the field of work because it
has its own importance as it provides complete solution for organizing the quiz programs and
to produce the results.
OBJECTIVE:
The main objective behind developing this system is to handle, the most important system
which has its roots in almost all the companies and firms with ease and necessary. All these
constraints are considered and the system is developed to cater to the needs of the program
organization comments.
The developing process of this system has to take care of certain important stages with a
strong view that it deals with the most important instances of the world, the intelligence.
Hence lots of efforts are taken to ensure that the administration that is the participants enjoys
all the benefits of the system. These enhancements and all other aspects are handled and it is
tailored in such a way that it meets the needs of the administrator.
REGISTRATION:
Using this module the participants can register their details to participate in the Quiz
program. Details such as Name, Age, and Qualification etc. are collected from the participants.
Each user will be given a separate password after registering their forms.
DISPLAY THE ANSWER:
This field is used by the administrator to display the answer and questions. After getting
the answers from the users for the question displayed. The administrator will display the next
question.
UPDATION:
This module is used to modify or update the score after verifying the answers furnished by
the users. The scores are updated based on the positive and negative points given by the
users.
EVALUATION:
This module is used to verify or check the answers furnished by the users. The scores are
updated based on the positive and negative points given by the users. After evaluation, the
scores are updated by administrator.

ANNOUNCEMENT:
This module is used to announce the result of quiz program. Once result is announced,
prizes will be distributed to the winner.
WINNER LIST:
This is a unique module which is used to display the list of winner at the end of the
competition. The winners will be honored by issuing certificate and prizes.
Class Diagram:
Program Executive
char name
int marks
int time
int rank
Accept()
verify certificat()
Candidate
<<void>> cha name
<<void>> int age
<<void>> char qualification
<<void>> resume()
<<void>> field()
Component Diagram:
Quiz System

Use-Case Diagram:
Participant
Register
Display Question
Answer Questions
Display The score
Data Base
Winner List
Co ordinator
Candidate Program
Execution
Quiz
master
2: Display the question
4: Evaluation of score
8: Announce the result3: Verify
5: Select the field
6: Answer the ques
1: Accept the Req from 7: Update the score

Sequence Diagram:
Candidate Program
Execution
Quiz master
Select the field
Answer the ques
Accept the Req from
Verify
Display the question
Evaluation of score
Update the score
Announce the result

Activity Diagram:
Announcement of result:
Get the ans
from database
Announce the
result
Display of questions:
Accept the field
Display the
ques
Invalid field
Get the ans
Store the ans
Store the field

Evaluation Of Results:
Accept the ans
Verify the ans
Update the
score
Update Result:
accept the ans
Check the ans
Positive point
Negative point
Update the
point
Close the point

Deployment Diagram:
candidate
online quiz
system
co-ordinato
r
database/
admin

EX. NO: 3
ONLINE RESERVATION SYSTEM
AIM:
To design and develop the Reservation System for manipulating the reservation details of a
person using Rational Rose Software.
PROJECT SCOPE:
The Online Reservation System is develop after the completion of all necessary UML
Component diagrams, which offers higher reliability and efficiency in handling the developed
System. The developed System plays a vital role irrespective of the field of Online Reservation
because it has its own importance as it provides complete solution in processing and managing
the reservation details of an individual.
OBJECTIVE:
The main objective behind developing this system is to handle, the most important System
which has its rot in almost all the banks and firms with ease and accuracy this system
requesting almost.
The developing process of this system has to take care of certain important stages with the
strong view that deals with the most important instances of the world, the currency. Hence
lots of efforts are taken to ensure that the administrator i.e the individuals enjoys all the
benefits of this System. This System must be flexible in such a way that it allows ensure
enhancement or modification i.e. the entry of new reservation detail and the removal of
already existing details these enhancements and all other aspects are handled and it is
tailored in such a way that it meets the need of the administrator.
INFRASTRUCTURE:
HARDWARE REQUIREMENTS:
• Processor: Pentium IV
• Capacity: 256MB of RAM
SOFTWARE REQUIREMENTS:
• Rational Rose Software
AVAILABILITY:
This module contains details about the number of sears available for reservation, total
number of seats available for reservation, total no. of seats occupied etc.
ENQUIRY:
This module contain details about the enquiry made by the users, this module
administrators search the ticket by getting the details from the user and produce the results to
the user.
RESERVATION:
Using this module the user can reserve the tickets he need, in this module the
administrator get the no. of credit card, checks the money and finally issue the ticket.

MODIFY:
This module contains details about the modification of the ticket reserved. The user
modifies the ticket that has been reserved already.
CONFIRMATION:
Using this module the user can check whether the ticket reserved by him is confirmed or
not. The ticket is not yet reserved the user sends the requests to the administrator.
CANCELLATION:
This module is used to cancel the tickets reserved by the users. The administrator cancels
the ticket by getting the ticket number from the user.
Class Diagram:
Cancel
<<int>> ticket
Cancel Operation()
Modify
<<int>> date
<<int>> passenger
Change the date()
int passenger()
Reservation
<<int>> dae
<<char>> place
<<int>> cardno
date of journey()
checksthe place()
check credit cardno()
Enquiry
<<int>> ticket
<<char>> passing
<<int>> cardno
status of card()
passenger details()
Website
Char : Web
Search webpage()
Component View:
Online
reservation
Use-case Diagram:

passenger
Enter the website
enquiry
reservation
modify
cancel
system
passenger
System
Login
Enquiry
verify
Modify
Cancel
7: Verify
1: Enter id and password
3: Status of the train ticket
6: Credit card4: Avail ticket
5: Enter The detail
8: Issue of ticket
9: Modify journey date
10: Cancel
2: Login
Sequence Diagram:

passenger System Login Enquiry verify Modify Cancel
Enter id and password
Login
Status of the train ticket
Avail ticket
Enter The detail
Credit card
Verify
Issue of ticket
Modify journey date
Cancel

Activity Diagram:
Activity:
Display the
ticket
Enter the
website
Specify source
and destination
Choose train
Specify user
details
Seat avail
Specify card
details
Conform ticket
Valid card
Next train

Cancellation:
Enter THE
WEBSITE
ENTER THE
TICKET NO
ENTER TRAIN
NO
if amt refundable
Enter CARD
details
Refund amount
CONFIRM

Modify:
enter the
website
Specify sourc
and desti
Enter train no
Enter ticket no
Valid ticket
Enter modified souce and
destination
Enter new train
no
Confirm tick
disp the ticket
yes
no

Deployment Diagram:
passenger
online reservation
system
system

EX. NO: 4
PAYROLL PROCESSING SYSTEM
AIM:
To design and develop the payroll processing system for manipulating the pay details of the
employees using Rational Rose Software.
PROJECT SCOPE:
The Payroll Processing System is developed after the completion of all the necessary UML
component diagrams, which offers higher reliability and efficiency in handling the developed
System. The developed System plays a vital role irrespective of the field of work because it
has its own importance as it provides complete solution in manipulating and managing the pay
details of the employees.
OBJECTIVE:
The main objective behind developing this System is to handle, the most important System
which has its root in almost all the companies and firms, with ease and accuracy. This System
requires utmost care because there should not be any errors in manipulating as well as
managing the pay details of the employees of a concern. All these constraints are considered
and the System is developed to cater to the needs of the employer.
The developing process of this System has to take care of certain important stages with the
strong view that it deals with the most important instance of the world, the currency. Hence
lots of efforts are taken to ensure that the administrator i.e. the employer enjoys all the
benefits of this System. This System must be flexible in such a way that it allows future
enhancement of modification i.e. the entry of new employee detail and the removal of an
already existing employee detail etc. these enhancements and all other aspects are handled
and it is tailored in such a way that it meets the needs of the administrator.
ABSTRACT:
The analysis phase proves to be the most crucial phase in the development process of a
System as it has its own impact on all other phases. It can result in re-analysis or performance
of the developed System, if the analysis done in the beginning does not turn out to be efficient.
Likewise our ‘Payroll Processing System’ analysis phase is crucial because any single mistake
made may result in heavy loss. Hence, the analysis phase was considered seriously and the
design this System was developed in such a way that it provides complete Solution to all the
activities of the employer.
The designing process is a tedious job when it comes to such a system which has its won
risk if it is done poorly. The designing of the flow of data i.e. the logical flow is very crucial as
this System involves quiet more number of activities and module. Each of the module and the
activity has its own importance and the integration of all such important modules is one such a
tough task which need complete guidance and advises from the expertise people who really
possess a bit of experience in this field. It is one of the important tasks that it depicts the
future importance of this System.
This System has mainly only one actor who performs or is in charge of all activities involved
in this System and that one actor is administrator.
ADMINISTRATOR:

The administrator deals with all the activities of this System. The basic crux of the System
has been designed in such a way that it proves to be reliable and recoverable if it happens to
meet any kind of System error, Logical error and System failures. If any such happens, the
System should not fail lest it would result in improper and wrong manipulation of the pay
details which may cost more to the administrator. At the same time this system must also
flexible when it comes to real time application. Here the flexibility refers to the amount of
ease that this System delivers to the administrator in carrying out his own tasks and activities
through this System. The overall performance of this System is judged in such a way that all
the activities are explored and developed with great amount of interest to ensure the
effectiveness of the System. Thus, the entire process of this System is treated with utmost
care and efforts to make sure that the developed System is errorless and reliable.
This System has potentially four main modules and three modules arises from a module
and therefore totally constituting seven modules and they are,
CALCULATE PRINT PAYROLL:
This module is mainly focused with the pay details of the employees alone. The main task
of this module is to compute the pay details of the concerned employee and printing it. This
module needs to access the payroll databases to retrieve the pay details of the particular staff.
MODIFY PAYROLL AMOUNT:
This module adheres to modification made to the amount which is to be mentioned in the
payroll of various employees. This modification does may be done periodically. Hence this
module needs constant updation and this facility is taken care of.
MANAGE TAX SALES:
This module takes care of the frequent changes that are made by the government and its
impact are readily absorbed by the System as it is designed in such a way to adapt to future
changes. This particular module also needs frequent updation has its own impact on the entire
structure of this System.
MAINTAIN EMPLOYEE DETAILS:
This module is responsible for maintaining the employee details of the concern (i.e.
personal information) for effective manipulation of the pay details of that particular employee.
This module needs utmost care and this is one of the most important modules of this entire
System as its failure could have a great impact on the entire System.
EDIT EMPLOYEE DETAILS:
This module is used to edit employee’s personal details as the name implies. This
particular field needs proper data feed and maintenance because if any edition is not updated
properly then it may result in a poor result.
ADD EMPLOYEE DETAILS:
This module caters to the needs of the administrator in adding new employee’s entrance to
that particular concern in a flexible and efficient manner. This module needs to be updated
only whenever a new entry comes into role lest this module task is to ensure in any list of the
concern correspond to the similar data if not it indicates that there is an error.
REMOVE EMPLOYEE DETAILS:

This module makes sure that whenever any employer resigns or quits or is fixed the
employee database is updated approximately. This is the prime task of this module. The
updation is made in such a way that it is reflected in almost all the departments of the concern
to make sure that the updation has resulted in a universal issues(throughout the concern).
Class Diagram:
Maintain Employee
details
emp-name : char
Emp-id : int
dept_design : char
pay detail : int
Maintain date()
Maintain salary()
Add employee details
new_appointment : char
dept-transfer : char
branch-transfer : char
add_emp detail()
Manage tax rate
basic-pay : int
tax amount()
Calculate &print payroll
emp det : char
working hrs : int
ot-hrs : int
Leave taken : int
Add-ot()
add/remove amt()
gross salary()
Remove employee
details
Retirement : char
transfer : int
death : int
Remove emp-det()
Edit employee details
ind details : char
dept-details : char
branch det : char
Update DB()
Modify Payroll amt
emp-dept : char
promotin : char
demotion : char
suspension : char
inc/dec basic pay()
dec suspension amt()
gross salary()
Component View:
Payroll Processing

Use-case Diagram:
Add employee payroll
Edit employee within payroll
Remove from payroll
Calculate & print payroll
Modify payroll amount
Manage tax rates
Maintain employee details
Payroll Operator
Employee Payroll
details
2: Verify employee details
3: Maintain Employee details
4: Create employee details
9: Edit details in DB
11: Verify payroll calculate
1: Accept employee details
5: Calculate payroll details
6: Manage tax rates
7: Print pay details
8: Add /Rem Employee
10: Modify &print payroll details
12: Issue salary

Sequence Diagram:
Employee Payroll details
Accept employee details
Verify employee details
Maintain Employee details
Create employee details
Calculate payroll details
Manage tax rates
Print pay details
Add /Rem Employee
Edit details in DB
Modify &print payroll details
Verify payroll calculate
Issue salary

Activity Diagram:
Add Employee:
New
Appointment
Dept Transfer
Branch transfer
No new
Appointment
Add details of new
employee to DB
Edit Employee:
Update the edited
employee details
Update individual
employee details
Update dept wise
employee details
Maintain employee
records within DB

Maintain Employee:
Employee Id_no
Basic Pay
Employee name
Employee Dept
&designation
Allowances
Personel
Details Rebates &
Concession
Gross Salary
Manage Tax:
Emp Details
No tax
tax=10% of
annual income
tax=20% of
income
Basic Pay
<5000
Basic Pay
>5000
Yes
Basic Pay
>10000
Yes
Calculate tax
amount
Enter the
details in payroll
Enter the DB
Yes

Modify Pay Roll:
employee
details
Increment basic
pay
Decrement pay
Calculate amount for
suspended days
Reduce amount
from payroll
Call gross
salary
Promotion Yes
demotion Yes
No
SuspensionYes
No
No

Print pay Roll:
Employee
details
Working days
Overtime Hrs
Leave taken
No
Calculate the
gross salary
Print gross
salary
Calculate the
amount for hrs
Yes
Add amount to
net salary
Calculate amount to
nature of leave
Add/Sub amount to
nature of leave
Yes
No

Remove Employee Details:
Employee
Details
Update transfer
details in DB
No removed of
details
Remove details
from DB
Service
retirement
Voluntary
retirement
NO
Natural/Accident
al death
No
Yes
Yes
Yes
No
Yes

EX. NO: 5
COURSE REGISTRATION SYSTEM
AIM:
To design and develop the Course Registration System to enquire and to register the
courses available using UML diagrams in the Rational Rose Software.
PROJECT SCOPE:
The main scope of the project is to develop a Course Registration System, to enquire the
available courses using enquiry model and then register the required course using registration
model, if the candidate want to cancel the course using cancellation model, if the candidate
wants to modify or change the course, a modification model has been developed.
ABSTRACT:
The most important phase in developing software for a customer is the analysis phase. As
it is said that most strong and tail buildings. The analysis phase proves to be the foundation
for the Software development process. In our topic, the Course Registration System is
concerned with the process of choosing and joining the course in educational institutions.
The “Course Registration System” should be more flexible for the Students (end users).
Our topic is constrained to the admission process of educational institutions. There are
primarily two main actors involved in this Course Registration System they are:
STUDENTS AND ADMINISTRATOR:
It is highly a tedious job to analyze the major modules involved in the System, since this
particular System deals with educational institution (i.e., academics) the analysis and
development of this System must be dealt with utmost care because if anything goes wrong
the students are going to be the ultimate sufferers. This System is designed in such a way
that it is completely flexible in providing two way conversations between the students and the
administrator. Each and every activities have been seriously considered and they have been
implemented, keeping in mind the future enhancements of this System and utmost car has
been taken to solve almost all the special cases which arises due to any Special situation in the
System.
This Course Registration System provides complete flexibility to the Students to choose the
courses according to their desire and it also provides room for modification and cancellation of
nay information or process. It also allows the administrator to a greater extent to intimate and
process the information provided by the student in an effective manner which makes this
System further more effective.
ENQUIRY:
What are the courses available will be given in the enquiry. The candidate can view the
available courses.
ELIGIBLE CRITERIA:
This module describes about the eligibility criteria for each course in the institutions. If the
candidate are eligible with the prescribed marks and percentage then they may pass to the
next section of course registration otherwise their applications are rejected.
REGISTRATION:

In Registration model, the candidate can register the courses by giving his/her details.
CANCELLATION:
In Cancellation model, if the Candidate doesn’t want to join in the Course which has been
previously registered, he/she can cancel registration.
MODIFICATION:
In modification model, the candidate can modify his course. If the candidate wants to
change the course, he can change using this model.
ADMISSION:
In admission model, the candidate can confirm the course and apply for it by paying the
fees.
Class Diagram:
Course Enquiry
Name : String
Address : String
Pno : int
reg()
Enquiry()
Admission
Confirm : boolean
Name : Sting
Age : int
Sex : String
Address : String
Caste : String
Confirm()
Fill_App()
Eval_App()
Cancellation
Continuation : boolean
Reason : String
Confirm : boolean
Cancel()
Certi()
Modification
Name : String
Age : int
Address : String
Phno : int
modify()
fee pay()
Component View:
Course Registration

Use-Case Diagram:
Student
enquiry
Addmission
Modify
CAncellation
Admin
Student
Enquiry
Addmissio
n
Modificatio
n
Validate
Request
Admin
5: Evaluate the application
10: Validate request
13: Validate request
1: Enquiry
2: Reply for register 3: getting the application
7: Fee payment
4: submit the application
9: Request for modification
12: request for cancellation
6: Intimate for fee payment
8: Addmission confirmed
11: Request modification performed
14: Requetsted cancel performed

Sequence Diagram:
AddmissionStudent Modification Validate Request Admin
getting the application
submit the application
Evaluate the application
Intimate for fee payment
Fee payment
Addmission confirmed
Request for modification
Validate request
Request modification performed
request for cancellation
Validate request
Requetsted cancel performed
Enquiry
Enquiry
Reply for register

Activity Diagram:
Admission:
Course Confirm
Application form
Evaluation of
appli form
Rejected
Addmission
Fees Payment
Addmission
Cancelled
Addmission
confirmed
If eligible
If on date
No
Yes
No
Yes

Cancellation:
If stud is unwilling to
continue the course
Reason for
cancel
Yes
Cancel Confirm
Retreivel of
certificates
If accepted by
mgmtYes
no
no

Enquiry:
register
Enquiry college
inform structure
Enquire lab
facilities
placement
facilities
Course details
Fees Structure

Modification:
If modify reg
Cahnge of
personel detail
Change of
course
Fee Payment
Course
Confirmed
If confirmation
If seat available
IF fee structure
changed
Yes
No
Yes
No
Yes
No

EX. NO: 6
ATM SYSTEM
AIM:
To analyze and design an Automated Teller Machine System using UML diagrams in the
Rational Rose Software.
PROJECT SCOPE:
The main scope of the project is to perform the transaction and to update own account
balance using an ATM Machine System.
OBJECTIVE:
The main objective of designing and implementing an ATM System enable the customer to
have easier transaction of money at anytime without standing or waiting in queue.
ABSTRACT:
ATM stands for Automated Teller Machine. It is nothing but immediate aspect of getting
money by using simple word. User can simply insert ATM card into the ATM Machine and
follow the simple instructions provided by the machine to get the required amount from his/her
own account. To protect their account form other users to access, password is provided which
is called a pin number and is provided uniquely for each user. ATM Machine acts as an
excellent technical development which provides for these users who require money anytime
they require various models have been used here are:
• Password Derived
• Re-enter Password
• Account number
• Deposit
• Withdrawal
• Balance
• Exit
MODULAR DESCRIPTION;
VERIFICATION OF ATM CARD:
For the verification of ATM card by the System, the users will enter the Secret code. The
pin number or the code number is verified with the database of the customers. If the code is
exactly matched with the database of the customer, then the transaction can be performed. If
the code doesn’t match with the database of the customer, then the user is urged again to re-
enter the pin number of the access card is continued further.
TRANSACTION:
In this module, the necessary transaction to be performed by the user is displayed as an
option by the System. The transaction options are Withdrawal, Deposit, Balance, Enquiry, Mini
Statement, and Pin Change. The Users can withdraw the amount from their account. The user
can also deposit the amount in their account either by cash/cheque.
WITHDRAWAL:

In this module, the user can withdraw the required amount from the ATM Machine by
inserting his/her card and providing the correct pin number if the pin number does not match
with the database then it reject the card. The withdrawal amount should be minimum then the
current amount in his/her account.
DEPOSIT:
In this module, the user can deposit the amount in his/her account in the form of
cash/cheque provided and the amount gets transaction to his/her account.
BALANCE:
In this module, the user can check his/her Balance provided with the correct pin number if
the pin number is wrong then again the ATM machine rejects the card.
MINI STATEMENT:
In this module, the user can get a printed statement of his/her account details in the form of
hard copy it can be the details of the last 15 days transaction or the entire transaction
according to the users wish.
PIN CHANGE:
In this module, the user can change the pin number according to his/her wish provided the
pin number should be a 4 digit number if the provided pin number matches with the already
existing pin number then the ATM machine requests for a different pin number and if the
entered pin number is unique then it accepts and from that moment your pin number changes.
DISPLAY THE RECEIPT:
In this module, after the transaction process is performed by the user, the System displays
the balance amount available in the account and the amount withdrawn by the user through
receipt. The receipt will be provided at the end of the transaction process.

Class Diagram:
acct.info
acc.no
name
transac()
Money
Owner
Transaction() Message
Sender
Receiver
Intimation()
Balance
Amount
Calculation()
Log
User
Verify()
Status
Income
Check()
Cash
Dispenser
Acc no
Transac()
Envelope
acceptor
User name
acc.no
Address
Transation()
Atm
acc no
name
transac()
custom,
console
name
venue
acc.no
submit detail()
Receipt
name
acknow()
operator panel
card no
pan no
Secured enquiry()
Receipt print
cheque no
date
transac()
card reader
card no
acc no
validity check()
session 1
user detail
submit_detail()
withdraw
name
transac()
card
pan no
acc no
transac()
deposit
acc no
card n o
transac()
enquriy
acc no
cheque no
transaction()
transaction 1
acc no
card no
validity()
Component View:
ATM
System
Use-case Diagram:

user
admin
Session
Banking
Rejectpin
Mini statement
balance enquiry with draw
Deposit
pin change
Transaction

saving acc
Customer
atm
admin
current acc
recript
print
1: insert card
3: pass word
7: cash
11: saving
15: amount
19: current
23: amount
27: amount
31: recreipt
35: req.pin change
38: enter curr pin
41: enter the new pin
46: no
2: enter pin
6: cash withdraw
14: enter the amt
18: continue
22: enter the amt
26: enter the amt
30: continue
34: continue
44: pin changed
45: continue
47: take the card
4: red pass
8: request
10: current
36: req
39: req
42: req
5: verified
9: saving
37: proceed
40: proceed
43: proceed
12: requset
16: req transaction
13: verified
17: transaaction process
20: request transaction
21: transaction process
25: transaction process
29: transaction processed
32: request recreipt
33: reciept processed

Sequence Diagram:
Customer atm admin savingacc current acc recript print
insert card
enter pin
pass word
red pass
verified
cashwithdraw
cash
request
saving
current
saving
requset
verified
amount
enter theamt
req transaction
transaaction process
continue
current
request transaction
transaction process
enter theamt
amount
request transaction
transaction process

req transaction
transaaction process
continue
current
request transaction
transaction process
enter the amt
amount
request transaction
transaction process
enter the amt
amount
request transaction
transaction processed
continue
recreipt
request recreipt
reciept processed
continue
req.pin change
req
proceed
enter curr pin
req

Activity Diagram:
Cash Withdraw:
Current session
Banking
Enter pin
is pin valid pin invalid
cash withdraw
current acc
enter the amt
saving acc
enter the
amount
transaction
colect cash
tranasction
process
collect cash
no
yes

Balance Enquiry:
Atm Machine
Enter Pin
Pin Checking Invalid pin
Balance
Enquiry
Saving account Current Account
Bal checking
Print Balance
Check Balance
Print balance

Deposit:
customer
session
Baking
Enter the pin
pin is invalidis pin vaild
deposit
enter amt
transac
amt depocited
no

Mini Statement:
banking
enter the pin
invalid pinis pin valid
mini statement
saving account
last 15days
transac detail
current account
print the detail
no
yes

Pin change:
BANKING
enter pin
invalid pins
invalid code
pin change
new pin
Reenter the pin
pin changed
yes
no

EX. NO: 7
STOCK MAINTENANCE
AIM:
To design and develop the Stock Maintenance System for processing the Stock details of an
industry or organization using Rational Rose Software.
PROJECT SCOPE:
The Stock Maintenance System is developed after the component of the entire necessary
UML Component diagram, which offers higher reliability and efficiency in handling. The
developed System plays a vital role irrespective of the field of work because it has own
importance as it provides complete solution in protecting and managing the stock details of an
Industry.
OBJECTIVE:
The main objective behind developing the system is to handle the most important System
which has its root in almost all the companies and firms, with ease and accuracy. This System
requires utmost care because there should not be any errors in processing as well as
managing the Stock details of the industry of a Concern. All these constraints are considered
the system is developed to cater to the needs of the industry.
The developing process of this System has to take care of certain important stages with the
strong view that it deals with the most important instance of the world, the currency. Hence
lots of efforts are taken to ensure that the administrator i.e., the employer enjoys all the
benefits of this System. It must flexible in such a way that it allows future enhancement (or)
modification i.e., these enhancement and all other aspects are handled and it is tailored in
such a way that it meets the need of the administrator.
STOCK REPORT:
Stock Report will contain all the detail about the stocks purchased quality of stocks and cost
details of the stocks.
UPDATE REPORT:
Update Report will contain detail about the recent modification of the stock database.
Updating the performed whenever a new stock is purchased (or) when a stock is delivered.
DELIVERY REPORT:
Delivery report will contain detail about the Stocks delivered to the Customer. It also
contains detail about the profit and lose encountered during the self of stocks.
PHONE ORDER:
Phone Order will contain detail about the stocks ordered through Phone. This will be under
the control of telephone operator.
WALK IN SALE:
Walk in Sale will contain details about the stocks ordered in person; this will be under the
control of sales clerk.

Class diagram:
Phone Order
ordered Item : String
Quality item : Integer
Available : String
Price : integer
order()
check list()
display()
Walk in sale
Order Item : String
Avail item : String
Quality : Int
price : int
Check Item()
Display()
Purchase_details
cust_name : String
puchase : string
Date of purchase : integer
Amount paid : integer
Pay bill : int
get cust_name()
get per_item()
get date()
get amount()
Delivery report
item name : String
Quantity : integer
report : String
get name()
get date()
get report()
Update report
Solid item : string
Avail item : string
Quality : int
Price : int
get sold item()
get avail item()
get quality()
get price()
Stock Report
avail item : string
item name : string
price : int
check item()
display()
Component View:
Stock
maintanance

Deployment Diagram:
customer
atm system
receipt
current
saving
admin
transaction
pin change

Use Case Diagram:
telephone
operator
sales clerk
stock details
phone order work in sale
maintainer
purchase details
update stock report
sale

stock
keeper
no.of item
purchase
order
damage
report
update
report
maintain
report
1: no. of item
2: purchase order
3: maintain damage report
4: maintain update report
5: maintain stock report

Sequence Diagram:
stock keeper no.of item purchase order damage report update report maintain report
no. of item
purchase order
maintain damage report
maintain update report
maintain stock report

Activity Diagram:
Phone Order:
customer name
name of
available item
quality of the
available item
items
purchased
date of
purchase
amount paid

Purchase Details:
name of the
item purchased
quanitity of the
item
purchase date
and report
Sale:
customer na
list of items
solds
date of sales
amount rec
eived
pay bills

Stock Details:
name of the
available item
entry of required
items
quantity of the
item
price of the item
new item arrived
yes
no

Update:
item present
number of items
bought
number of item
sold
sold to stock
list
reduce from
stock list
load details and
save
Walk-In-Sale:
item present
number of items
bought
number of item
sold
sold to stock
list
reduce from
stock list
load details and
save

Deployment Diagram:
no.of items
stock maintenance
stock keeper
purchase
order
maintain report
damage report
damage report

60780174 49594067-cs1403-case-tools-lab-manual

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à 60780174 49594067-cs1403-case-tools-lab-manual

Similaire à 60780174 49594067-cs1403-case-tools-lab-manual (20)

Dernier

Dernier (20)

60780174 49594067-cs1403-case-tools-lab-manual