Ex: 1 STUDY OF UML
Date:
AIM:
General study of UML
Description:
The heart of object oriented problem solving is the construction of a model.
The model abstracts the essential details of the underlying problem.
Several modeling roots are wrapped under UML.
What is UML?
UML (Uniform Modeling Language) has emerged as the software blueprint language for analysts, designers and programmers alike. It provides common vocabulary to talk about software design.
UML is applicable to object oriented problem solving. The underlying level of object oriented problem solving is the construction of a model.
Model:
It is an abstraction of the underlying problem.
Model consists of objects that interact by sending each other message.
Every object has attributes and they can do operations. The value of an object attribute determines the state.
Classes are blueprints for objects.
There are 8 kinds of modeling diagrams:
1. USE CASE DIAGRAM:
A Use case is a set of scenario that describes an interaction between user and a system. A Use case diagram displays the relationship among Actors and Use cases.
There are two main components of Use case diagrams are:
· Use cases Functions
· Actors-User
2. SEQUENCE DIAGRAM:
It describes the behavior of a system by viewing the interaction between the system and its environment.
Sequence diagram has two dimensions:
· Vertical dimension represents the life time.
· Horizontal dimension represents the object.
3. CLASS DIAGRAM:
It represents the class name, attributes and list of methods which are going to use the software development process.
4. ACTIVITY DIAGRAM:
Activity diagrams focus on the flow of activities involved in a single process and the dependencies of the activity on them.
5. COLLABORATION DIAGRAM:
Collaboration diagrams are also interaction diagrams. They focus on object roles instead of the time that messages are sent.
6. STATE DIAGRAM:
State chart diagrams show the possible states of objects and the transitions that cause a change in state.
7. COMPONENT DIAGRAM:
A component is a code module. Component diagrams are a physical analog of class diagrams.
8. DEPLOYMENT DIAGRAM:
Deployment diagrams show the physical configuration of software and hardware.
Ex : 2 STUDENT MARK ANALYZING SYSTEM
Date :
AIM:
To implement the Student Mark Analyzing System using Rational Rose Software.
Requirement Analysis:
Hardware Requirements:
RAM : 256 MB
Processor : Intel Pentium IV
Hard disk : 40 GB
Software Requirements:
Case tools : Rational suites win runner, Emprix.
Languages : C/C++/JDK1.3, JSDK, Internet Explorer, UML
Front end : VB, VC++, Developer 2000
Back end : Oracle, MS-Access
PROBLEM STATEMENT:
Student marks analyzing system has to be developed for analyzing the marks obtained by the students who scored in Semester Examination
The System should provide the following functionalities:
1. The student enters the input form and the details are stored in the database.
2. The total and percentage of each student should be calculated and graded.
3. The total, percentage and grade are displayed.
SPECIFICATIONS :
1. Objectives
The purpose of this document is to define requirements of the Student Mark analysis system. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
2. Scope
This Supplementary Specification applies to the Student Mark analysis System, which will be developed by the OOAD students. This Specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability, as well as functional requirements. That is common across a number of use cases.
ACTORS:
- Staff
- Student
USE CASES:
- Number of Subjects.
- Marks.
- Total.
- Percentage.
- Grade.
ALGORITHM :
1. Start the application.
2. Create the required actors and use cases on the browser window.
3. Go to the new use case view and open a new package.
4. Rename the new package with a new name.
USE CASE DIAGRAM :
CLASS DIAGRAM :
STATE CHART DIAGRAM :
SEQUENCE DIAGRAM :
COLLABORATION DIAGRAM :
Student Mark Analysis
Code Generation Template :
Staff.cpp
#include "Staff.h"
//##ModelId=4246E53402BB
Staff::Display()
{}
//##ModelId=4246E53402BB
Staff::Getmarks()
{}
//##ModelId=4246E53402BB
Staff::Findtotal()
{}
//##ModelId=4246E53402BB
Staff::Findaverage()
{}
//##ModelId=4246E53402BB
Staff::Assigncode()
{}
Staff.h
#ifndef STAFF_H_HEADER_INCLUDED_BDB88738
#define STAFF_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class Staff
{ 9
public:
//##ModelId=4246E53402BB
Display();
//##ModelId=4246E53402BB
Getmarks();
//##ModelId=4246E53402BB
Findtotal();
//##ModelId=4246E53402BB
Findaverage();
//##ModelId=4246E53402BB
Assigncode();
private:
//##ModelId=4246E5290069
No of students;
//##ModelId=4246E5290069
Marks;
//##ModelId=4246E5290069
Total;
//##ModelId=4246E5290069
Percentage;
//##ModelId=4246E5290069
Grade;
//##ModelId=4246E5290069
Reg No;
};
#endif /* STAFF_H_HEADER_INCLUDED_BDB88738 */
Student.cpp
#include "Student.h"
//##ModelId=4246E53402BB
Student::Displayresult()
{
}
Student.h
#ifndef STUDENT_H_HEADER_INCLUDED_BDB88738
#define STUDENT_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class Student
{
public:
//##ModelId=4246E53402BB
Displayresult();
private:
//##ModelId=4246E5290069
Reg No;
//##ModelId=4246E5290069
Name;
//##ModelId=4246E5290069
College Code;
};
#endif /* STUDENT_H_HEADER_INCLUDED_BDB88738 */
Result :
Thus the UML Diagrams for Students Mark Analysis was created.
Ex: 3 QUIZ APPLICATION
Date:
AIM:
To create a UML diagram of a Quiz application.
Requirement Analysis:
Hardware Requirements:
RAM : 256 MB
Processor : Intel Pentium IV
Hard disk : 40 GB
Software Requirements:
Case tools : Rational suites win runner, Emprix.
Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML
Front end : VB, VC++, Developer 2000
Back end : Oracle , MS-Access
PROBLEM STATEMENT :
Quiz application has to be developed for verifying the answers and deciding the winner based on the score.
The System should provide the following functionalities:
1. The participants are divided into a no. of teams.
2. The interviewer asks questions based on the rules, verifies the answers and gives the marks.
3. Based on the marks, the winners get prizes.
SPECIFICATIONS :
1. Objectives
The purpose of this document is to define requirements of the Student Mark analysis system. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
2. Scope
This Supplementary Specification applies to the Student Mark analysis System, which will be developed by the OOAD students. This Specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability, as well as functional requirements. That is common across a number of use cases.
ACTORS:
1.Interviewer
2.Participant
3.Scorer
USE CASES:
1.No. of teams
2.Team name
3.No. of participants
4.Rules
5.Rounds
6.Questions and answers
7.Time
8.Marks
9.Results
10.Prize
ALGORITHM :
1.Start the application.
2.Create the required actors and use cases on the browser window.
3.Go to the new use case view and open a new package.
4.Rename the new package with a new name.
USE CASE DIAGRAM :
CLASS DIAGRAM :
ACTIVITY DIAGRAM :
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
Quiz Application
Code Generation Template :
Interviewer.cpp
#include "Interviewer.h"
//##ModelId=4246E53402BB
Interviewer::maintaintimelimit()
{
}
//##ModelId=4246E53B000B
Interviewer::Askquestion()
{
}
Interviewer.h
#ifndef INTERVIEWER_H_HEADER_INCLUDED_BDB88738
#define INTERVIEWER_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class INTERVIEWER
{
public:
//##ModelId=4246E53402BB
maintaintimelimit();
//##ModelId=4246E53B000B
Askquestion();
private:
//##ModelId=4246E5290069
Teamname;
//##ModelId=4246E52C0386
Time;
//##ModelId=4246E52C0386
Round;
};
#endif /* INTERVIEWER_H_HEADER_INCLUDED_BDB88738 */
Participant.cpp
#include "Participant.h"
//##ModelId=4246E53402BB
Participant::Analysethequestion()
{}
//##ModelId=4246E53B000B
Participant::Giveanswer()
{}
PARTICIPANT.h
#ifndef PARTICIPANT_H_HEADER_INCLUDED_BDB88738
#define PARTICIPANT_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class PARTICIPANT
{ public:
//##ModelId=4246E53402BB
Analysethequestion();
//##ModelId=4246E53B000B
Giveanswer();
private:
};
#endif /* PARTICIPANT_H_HEADER_INCLUDED_BDB88738 */
Scorer.cpp
#include "Scorer.h"
//##ModelId=4246E53402BB
Scorer::VerifytheAnswer()
{}
//##ModelId=4246E53B000B
Scorer::Giveresult()
{}
Scorer.h
#ifndef SCORER_H_HEADER_INCLUDED_BDB88738
#define SCORER_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class SCORER
{
public:
//##ModelId=4246E53402BB
VerifytheAnswer();
//##ModelId=4246E53B000B
Giveresult();
private:
};
#endif /* SCORER_H_HEADER_INCLUDED_BDB88738 */
Result :
Thus the UML Diagrams for Quiz Application was created.
Ex: 4 ONLINE COURSE REGISTRATION SYSTEM
Date:
AIM:
To create a UML diagram of course registration system.
Requirement Analysis:
Hardware Requirements:
RAM : 256 MB
Processor : Intel Pentium IV
Hard disk : 40 GB
Software Requirements:
Case tools : Rational suites win runner, Emprix.
Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML
Front end : VB, VC++, Developer 2000
Back end : Oracle , MS-Access
PROBLEM STATEMENT :
Online course registration system has to be developed for admissions to a new course.
The System should provide the following functionalities:
1. The student enters the login id, course and subject in the registration form.
2. Using the details the staff starts the registration.
3. The database maintains staff and student profiles.
4. The registrar updates the grade and closes the registration.
SPECIFICATIONS :
1. Objectives
The purpose of this document is to define requirements of the Student Mark analysis system. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
2. Scope
This Supplementary Specification applies to the Student Mark analysis System, which will be developed by the OOAD students. This Specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability, as well as functional requirements. That is common across a number of use cases.
ALGORITHM :
1. Start the application.
2. Create the required actors and use cases on the browser window.
3. Go to the new use case view and open a new package.
4. Rename the new package with a new name.
ACTORS:
1. Student
2. System
USE CASE:
1. Register no.
2. No.of course
3. Course code
4. Fees detail
5. Confirmation
6. Certificate submission
7. Credit card transaction
8. Course registered successfully
USE CASE DIAGRAM:
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
SEQUENCE DIAGRAM:
COLLABORATION DIAGRAM:
Online Course Registration System
Code Generation Template :
DBClass.cpp
#include "DB Class.h"
//##ModelId=4246E53402BB
DB Class::Addrecord()
{
}
//##ModelId=4246E53402BB
DB Class::Modifyrecord()
{
}
//##ModelId=4246E53402BB
DB Class::Displayrecord()
{
}
//##ModelId=4246E53402BB
DB Class::Miscellenous()
{
}
DB Class.h
#ifndef DB_CLASS_H_HEADER_INCLUDED_BDB88738
#define DB_CLASS_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class DB Class
{
public:
//##ModelId=4246E53402BB
Addrecord();
//##ModelId=4246E53402BB
Modifyrecord();
//##ModelId=4246E53402BB
Displayrecord();
//##ModelId=4246E53402BB
Miscellenous();
private:
//##ModelId=4246E5290069
Stud ID;
//##ModelId=4246E5290069
Stu Name;
//##ModelId=4246E5290069
Stu Address;
//##ModelId=4246E5290069
Stu Course;
//##ModelId=4246E5290069
Stu Marks;
//##ModelId=4246E5290069
Stu extraactivities;
//##ModelId=4246E5290069
Courseavailable;
//##ModelId=4246E5290069
feestructure;
//##ModelId=4246E5290069
duration;
//##ModelId=4246E5290069
Dob;
};
#endif /* DB_CLASS_H_HEADER_INCLUDED_BDB88738 */
Student.cpp
#include "Student.h"
//##ModelId=4246E53402BB
Student::Enterdetails()
{
}
//##ModelId=4246E53402BB
Student::Submitform()
{
}
Student.h
#ifndef STUDENT_H_HEADER_INCLUDED_BDB88738
#define STUDENT_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class Student
{
public:
//##ModelId=4246E53402BB
Enterdetails();
//##ModelId=4246E53402BB
Submitform();
private:
//##ModelId=4246E5290069
ID;
//##ModelId=4246E5290069
Name;
//##ModelId=4246E5290069
Address;
//##ModelId=4246E5290069
Course;
//##ModelId=4246E5290069 Marks;
//##ModelId=4246E5290069
Dob;
};
#endif /* STUDENT_H_HEADER_INCLUDED_BDB88738 */
Regform.cpp
#include "Regform.h"
//##ModelId=4246E53402BB
Regform::Openform()
{
}
//##ModelId=4246E53402BB
Regform::Checkeligibility()
{
}
//##ModelId=4246E53402BB
Regform::Register()
{
}
//##ModelId=4246E53402BB
Regform::AssignID()
{
}
Regform.h
#ifndef REG_FORM_H_HEADER_INCLUDED_BDB88738
#define REG_FORM_H_HEADER_INCLUDED_BDB88738
//##ModelId=4246E52003A5
class Regform
{
public:
//##ModelId=4246E53402BB
Openform();
//##ModelId=4246E53402BB
Checkeligibility();
//##ModelId=4246E53402BB
Register();
//##ModelId=4246E53402BB
AssignID();
private:
//##ModelId=4246E5290069
Iseligible;
//##ModelId=4246E5290069
FormID;
};
#endif /* REG_FORM_H_HEADER_INCLUDED_BDB88738 */
Result:
Thus the UML Diagrams for Online Course Registration was created.
Ex No :5 ONLINE TICKET RESERVATION SYSTEM
Date:
Aim:
To prepare the document and develop Online ticket reservation software using software engineering methodologies.
Requirement Analysis:
Hardware Requirements:
RAM : 256 MB
Processor : Intel Pentium IV
Hard disk : 40 GB
Software Requirements:
Case tools : Rational suites win runner, Emprix.
Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML
Front end : VB, VC++, Developer 2000
Back end : Oracle , MS-Access
Problem statement
System is designed for the online reservation of railway tickets for travel between any destinations that is a part of the network formed for enabling this activity. This system is intended to be provided to the Indian railway which is the largest railway system in Asia. This system enables the Advance booking in any class, against general and ladies quota, on payment of fare in full for adults and children, a maximum of six berths/seats at a time, for journey between any two stations served by a train.
It also provides details about
1. Accommodation available for a train/date combination
2. Current status of reservation position
3. Time table
4. Train fares
5. Train available between a pair of stations
The user of this system should first register for any interaction with the system. Once registered, he/she will be provided with a username and password for the user to log in. After logging in the user should select the kind of activity he would like to perform like booking a ticket, canceling a ticket, look out for help and so on.
If he selects the booking the ticket option, then he/she should select the to and from stations. After this step the user should select a particular train that runs between the specified stations from a list of trains that is provided by the system. Once a particular train is selected, the user should specify the class of travel and date of journey. Then he can view the vacancy position in that train for that date. Depending upon the vacancy position, the user can proceed to book his tickets. For reserving the ticket, the user should fill up the reservation form with the details like name, age, sex, class of travel, train number, train name, preferred seats/berths and others. After filling up this form, the user should submit this for reservation.
Then the mode of payment is selected and the user fills up the corresponding details. Once these processes are over, the system automatically reserves the ticket for the user and it deliver by post. The ticket number and PNR number details would be intimated to the user for future reference. Thus the Online Train Ticket has been booked.
SPECIFICATIONS :
1. Objectives
The purpose of this document is to define requirements of the Student Mark analysis system. This Supplementary Specification lists the requirements that are not readily captured in the use cases of the use case model. The Supplementary Specifications and the use-case model together capture a complete set of requirements on the system.
2. Scope
This Supplementary Specification applies to the Student Mark analysis System, which will be developed by the OOAD students. This Specification defines the non-functional requirements of the system; such as reliability, usability, performance, and supportability, as well as functional requirements. That is common across a number of use cases.
Actors
1.Passenger
2.System DB
Use cases
1. Train info
2. Reserve ticket
3. Train Avail
4. Cancel Ticket
ALGORITHM :
1. Start the application.
2. Create the required actors and use cases on the browser window.
3. Go to the new use case view and open a new package.
4. Rename the new package with a new name.
Usecase diagram:
Class diagram:
Activity diagram:
Sequence diagram: