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. 1

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 Date :

STUDENT MARK ANALYZING SYSTEM

AIM: To implement the Student Mark Analyzing System using Rational Rose Software. Requirement Analysis: Hardware Requirements: RAM : Processor : Hard disk : 256 MB Intel Pentium IV 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 nonfunctional 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. Staff 2. Student USE CASES: 1. Number of Subjects. 2. Marks. 3

3. Total. 4. Percentage. 5. 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 :

no of subjects

marks

staff

total

student

percentage

grade

CLASS DIAGRAM : staff member

int No.of sub int marks int total float percentage char grade int regno display() getmarks() findtotal() findavg() assigngrade()

students
char name int regno int collcode displayresult()

STATE CHART DIAGRAM :

Student detail submission

Filter

Process

Report

SEQUENCE DIAGRAM :
Staff Marks Find Total and Avg Assign grade Student

1: No of subjects

2: Read marks 3: Find total and avg 4: Find grade 5: Store

6: Store marks

COLLABORATION DIAGRAM :

1: No of subjects 2: Read marks Staff Marks

3: Find total and avg

Find Total and Avg

Assign grade

5: Store

6: Store marks 4: Find grade Student

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 { public: //##ModelId=4246E53402BB Display(); //##ModelId=4246E53402BB Getmarks(); //##ModelId=4246E53402BB Findtotal(); //##ModelId=4246E53402BB Findaverage(); //##ModelId=4246E53402BB Assigncode(); private: //##ModelId=4246E5290069 No of students; //##ModelId=4246E5290069 7

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 Date:

QUIZ APPLICATION

AIM: To create a UML diagram of a Quiz application. Requirement Analysis: Hardware Requirements: RAM Processor Hard disk : : : 256 MB Intel Pentium IV 40 GB

Software Requirements: Case tools Languages Front end Back end : : : : Rational suites win runner, Emprix. C/C++/JDK1.3, JSDK, Internet explorer, UML VB, VC++, Developer 2000 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 9

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 :

No.of teams Team name No.of participantsNo.of rounds Prize Rules

Interviewer

Questions

Participant

Result

Answers Scorer Marks

10

CLASS DIAGRAM :

quiz interviewer
char teamname int time int rounds maintaintimelimit() ask question()

quiz participant
analysethequestions() giveanswer()

quiz scorer
verifyanswers() giveresult()

ACTIVITY DIAGRAM :

Describe no.of teams,participants,rounds and team name

Enter round No Ask questions

Get answer Check answer

Assign marks

If correct

Check end of round If yes Declare result

Award prize

11

SEQUENCE DIAGRAM:
Interviewer Marks Rounds Winner

Participant

1: Ask question 2: Answer the question 3: If answer is correct, provide mark 4: If not correct, ask next question 5: Check end of rounds 6: If yes, announce winner

7: If no, ask next question

COLLABORATION DIAGRAM:

12

3: If answer is correct, provide mark Marks Interview er Particip ant

5: Check end of rounds 7: If no, ask next question

1: Ask question 4: If not correct, ask next question 2: Answer the question 6: If yes, announce winner

Rounds

Winner

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(); 13

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=4246E5 3402BB Scorer::VerifytheAnswer() {} //##ModelId=4246E53B000B Scorer::Giveresult() {} Scorer.h #ifndef SCORER_H_HEADER_INCLUDED_BDB88738 #define SCORER_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 14

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.

15

Ex: 4 Date:

ONLINE COURSE REGISTRATION SYSTEM

AIM: To create a UML diagram of course registration system. Requirement Analysis: Hardware Requirements: RAM Processor Hard disk : : : 256 MB Intel Pentium IV 40 GB

Software Requirements: Case tools Languages Front end Back end : : : : Rational suites win runner, Emprix. C/C++/JDK1.3, JSDK, Internet explorer, UML VB, VC++, Developer 2000 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

16

supportability, as well as functional requirements. That is common across a number of use cases.

17

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. 2. 3. 4. 5. 6. 7. 8. Register no. No.of course Course code Fees detail Confirmation Certificate submission Credit card transaction Course registered successfully

18

USE CASE DIAGRAM:

register no

no of course

course code

fees detail

system confirmation

student

certificate submission

credit card transaction

course register successfully

19

CLASS DIAGRAM:
college DB no of course register no course code fees detail credit card transaction stu register no course code fees detail credit card transaction

int int int int int

int int int int

display() get detail() check detail() course confirmation()

display() confirmation()

ACTIVITY DIAGRAM:

20

no of course course code register

yes no sorry try again course duration

fees detail

certificate submission

credit card transaction

confirmation msg

course registered successfully

SEQUENCE DIAGRAM: 21

system

student

no of course

enter course code

course code entered

course duration

register

fees detail

credit card transaction

certificate submission

confirmation msg

course registerd sucessfully

COLLABORATION DIAGRAM:
1: no of course 2: enter course code 4: course duration 6: fees detail 9: confirmation msg 10: course registerd sucessfully system 3: course code entered 5: register 7: credit card transaction 8: certificate submission student

22

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; 23

//##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: 24

//##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 25

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.

26

Ex No :5 Date: Aim:

ONLINE TICKET RESERVATION SYSTEM

To prepare the document and develop Online ticket reservation software using software engineering methodologies. Requirement Analysis: Hardware Requirements: RAM Processor Hard disk : : : 256 MB Intel Pentium IV 40 GB

Software Requirements: Case tools Languages Front end Back end : : : : Rational suites win runner, Emprix. C/C++/JDK1.3, JSDK, Internet explorer, UML VB, VC++, Developer 2000 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 27

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.

28

Usecase diagram:

Enter the Web Site

Select the Destination

List of Trains System Passenger Select the Train

User Details Exit

No of Seats

Ticket Status

Credit Card No

Confirmation

29

Class diagram:

DB Train Name Train No Source Destination ArrTime DepTime Class Fare Distance Getcustomerdetails() gettraveldetails() confirmation() reserveticket() display() Process()

Customer Customer Name DOB Sex Address Phone Givedet() availability() getconfirm() reserve() givecreditcardno() getticket()

Computer isavailable ticketno maintaindb() updatedb() reserveticket() deliverticket()

30

Activity diagram:

Login Web Site Select the Destination

Select the Train No & No of Seats

Yes Is Available

No

Try Later Create Customer Details

Credit Card Number

Confirmation

Exit

31

Sequence diagram:

Passenger

System

DB

1. Login Web Site

2. Select the Destination 3. List of Trains

4. Give User Details

5. Give Train No & No...

6. Credit Card No

7. Give Status 8. Reserve Ticket

9.Confirmation 10. Issue Ticket

Collaboration diagram:

32

1: 2: 4: 5: 6: 7: Passenger 3: 10: 9: 8: System

DB

Component diagram:

33

DB

Store & Update

Computer

Online ticket registration Code Generation Template : DB.cpp #include "DB.h" //##ModelId=4246E53402BB DB::Getcurrentdetails() { } //##ModelId=4246E53402BB DB::GetTraveldetails() { } //##ModelId=4246E53402BB DB::Confirmation() { } //##ModelId=4246E53402BB DB::Receiveticket() { } //##ModelId=4246E53402BB DB::Display() { } //##ModelId=4246E53402BB DB::Process() 34

{ } DB.h #ifndef DB_H_HEADER_INCLUDED_BDB88738 #define DB_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class DB { public: //##ModelId=4246E53402BB Getcurrentdetails(); //##ModelId=4246E53402BB Gettraveldetails(); //##ModelId=4246E53402BB Confirmation(); //##ModelId=4246E53402BB Reserveticket(); //##ModelId=4246E53402BB Display(); //##ModelId=4246E53402BB Process(); private: //##ModelId=4246E5290069 Train Name; //##ModelId=4246E5290069 Train No; //##ModelId=4246E5290069 Source; //##ModelId=4246E5290069 Destination; //##ModelId=4246E5290069 Arr time; //##ModelId=4246E5290069 Dep time; //##ModelId=4246E5290069 Class; 35

//##ModelId=4246E5290069 Fare; //##ModelId=4246E5290069 Distance; }; #endif /* DB_H_HEADER_INCLUDED_BDB88738 */ Customer.cpp #include "Customer.h" //##ModelId=4246E53402BB Customer::Givedetails() { } //##ModelId=4246E53402BB Customer::Availability() { } //##ModelId=4246E53402BB Customer::Getconfirm() { } //##ModelId=4246E53402BB Customer::Reserve() { } //##ModelId=4246E53402BB Customer::Givecreditcardinfo() { } //##ModelId=4246E53402BB Customer::Getticket() { } Customer.h #ifndef CUSTOMER_H_HEADER_INCLUDED_BDB88738 #define CUSTOMER_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class Customer { public: //##ModelId=4246E53402BB Givedetails(); //##ModelId=4246E53402BB Availability(); //##ModelId=4246E53402BB 36

Getconfirm(); //##ModelId=4246E53402BB Reserve(); //##ModelId=4246E53402BB Givecreditcardinfo(); //##ModelId=4246E53402BB Getticket(); private: //##ModelId=4246E5290069 Customer Name; //##ModelId=4246E5290069 DOB; //##ModelId=4246E5290069 Sex; //##ModelId=4246E5290069 Add; //##ModelId=4246E5290069 Phone; }; #endif /* CUSTOMER_H_HEADER_INCLUDED_BDB88738 */ System.cpp #include "System.h" //##ModelId=4246E53402BB System::Maintaindb() { } //##ModelId=4246E53402BB System::Updatedb() { } //##ModelId=4246E53402BB System::Reserveticket() { } 37

//##ModelId=4246E53402BB System::Deleiverticket() { } System.h #ifndef SYSTEM_H_HEADER_INCLUDED_BDB88738 #define SYSTEM_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class System { public: //##ModelId=4246E53402BB maintaindb(); //##ModelId=4246E53402BB Updatedb(); //##ModelId=4246E53402BB Reserveticket(); //##ModelId=4246E53402BB Deliverticket(); private: //##ModelId=4246E5290069 Is Available; //##ModelId=4246E5290069 Ticket No; }; #endif /* SYATEM_H_HEADER_INCLUDED_BDB88738 */ Result : Thus the UML Diagrams for Online Ticket Reservation was created.

38

Ex No: 6 Date: AIM :

ATM SYSTEM

To develop an ATM system using software engineering methodologies. Problem StatementTo develop an ATM System for HDFC Bank The system developed should contain the following features: 1. The Customer has to login into the system using Credit Card or Debit Card number and Pin Number. The system should check for validation. 2. The System queries the customer for the type of account either Savings Account or Current Account. After getting the type of account, the system shows the amount left. 3. The System then queries the customer for the required amount. The user enters the amount and gets the money. Requirement Analysis: Hardware Requirements: RAM Processor Hard disk : : : 256 MB Intel Pentium IV 40 GB

Software Requirements: Case tools Languages Front end Back end : : : : Rational suites win runner, Emprix. C/C++/JDK1.3, JSDK, Internet explorer, UML VB, VC++, Developer 2000 Oracle , MS-Access

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. 39

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:

Insert Card Enter PIN Invalid PIN Approval

Deposit Amount Type of Transaction Client Administrator

Withdraw Amount Remove the Card Transaction Complted Exit

40

Activity diagram:

insert card display invalid enter pin no. invalid valid

check pin no.

check transaction type withdrawal withdrawal amt approval

deposit

deposit amt

transaction completed

41

Sequence diagram:
Client ATM Administrator Bank

1. Insert Card

2. Enter PIN No 3. Send PIN No 4. Verify PIN No

5. Validate Message

6. Get Transaction Type

7. Get Amount 8. Send Amount 9. Update Account

10. Success 11. Transaction Completed

Collaboration diagram: .

42

1: 2: 6: 7: Client 11: 10: 3: 8:

ATM

5:

Administra tor

4: 9:

Bank

Component Diagram :

ATM Server

Update

Front Panel

43

ATM Application Code Generation Template : ATM Card.cpp #include "ATM Card.h" //##ModelId=4246E53402BB ATM Card::GetPIN() { } //##ModelId=4246E53B000B ATM Card::GiveID() { } ATM Card.h #ifndef ATM_CARD_H_HEADER_INCLUDED_BDB88738 #define ATM_CARD_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class ATM Card { public: //##ModelId=4246E53402BB GetPIN(); //##ModelId=4246E53B000B GiveID(); private: //##ModelId=4246E5290069 Card No; //##ModelId=4246E52C0386 PIN ID; }; #endif /* ATM_CARD_H_HEADER_INCLUDED_BDB88738 */ Customerdetails.cpp #include "Customer details.h" //##ModelId=4246E53402BB 44

Customer details::GetCard() { } //##ModelId=4246E53B000B Customer details::Changevalidity() { } //##ModelId=4246E53B000B Customer details::ChangePIN() { } //##ModelId=4246E53B000B Customer details::PINEntry() { } Customerdetails.h #ifndef CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738 #define CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class Customer details { public: //##ModelId=4246E53402BB Get Card(); //##ModelId=4246E53B000B Change validity(); //##ModelId=4246E53B000B Change PIN(); //##ModelId=4246E53B000B PIN Entry(); private: //##ModelId=4246E5290069 Name; //##ModelId=4246E52C0386 Address; //##ModelId=4246E52C0386 Phone No; 45

//##ModelId=4246E52C0386 PIN No; //##ModelId=4246E52C0386 Card ID; }; #endif /* CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738 */ MainDB.cpp #include "MainDB.h" //##ModelId=4246E53402BB MainDB::Givebalance() { } //##ModelId=4246E53B000B MainDB::Checkwithdrawal() { } //##ModelId=4246E53B000B MainDB::ApprovalorNot() { } //##ModelId=4246E53B000B MainDb::GiveAmountvalue() { } MainDB.h #ifndef MAINDB_H_HEADER_INCLUDED_BDB88738 #define MAINDB_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class MainDB { public: //##ModelId=4246E53402BB Givebalance(); //##ModelId=4246E53B000B 46

Checkwithdrawal(); //##ModelId=4246E53B000B ApprovalorNot(); //##ModelId=4246E53B000B GiveAmountvalue(); private: //##ModelId=4246E5290069 Customer details; //##ModelId=4246E52C0386 Card details; //##ModelId=4246E52C0386 Transaction details; //##ModelId=4246E52C0386 Balance Amount; };

#endif /* MAINDB_DETAILS_H_HEADER_INCLUDED_BDB88738 */ Carddetails.cpp #include "Carddetails.h" //##ModelId=4246E53402BB Carddetails::Checkvalidity() { } //##ModelId=4246E53B000B Carddetails::Readinformation() { } Carddetails.h #ifndef CARD_DETAILS_H_HEADER_INCLUDED_BDB88738 #define CARD_DETAILS_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class Carddetails { public: 47

//##ModelId=4246E53402BB Checkvalidity(); //##ModelId=4246E53B000B Readinformation(); private: //##ModelId=4246E5290069 Name; //##ModelId=4246E52C0386 Card ID; //##ModelId=4246E52C0386 Account No; };

#endif /* CARD_DETAILS_DETAILS_H_HEADER_INCLUDED_BDB88738 */ Reports.cpp #include "Reports.h" //##ModelId=4246E53402BB Reports::Checkmoneyavailability() { } //##ModelId=4246E53B000B Reports::Readamount() { } //##ModelId=4246E53B000B Reports::Countmoney() { } //##ModelId=4246E53B000B Reports::Dispatchmoney() { } Reports.h #ifndef REPORTS_H_HEADER_INCLUDED_BDB88738 48

#define REPORTS_H_HEADER_INCLUDED_BDB88738 //##ModelId=4246E52003A5 class Reports { public: //##ModelId=4246E53402BB Checkmoneyavailability(); //##ModelId=4246E53B000B Readinamount(); //##ModelId=4246E53B000B //##ModelId=4246E53B000B Dispatchmoney(); private: //##ModelId=4246E5290069 Amount; #endif /* REPORTS_H_HEADER_INCLUDED_BDB88738 */ Countmoney();

Result : Thus the UML Diagrams for ATM Application was created.

49

7. EMPLOYEE PAYROLL SYSTEM Ex.No:7 Date : AIM To create a UML diagram of employee payroll. REQUIREMENT ANALYSIS Hardware Requirements RAM Processor Hard disk Case tools Languages Font end Back end: ACTORS: 1) EMPLOYEE 2) ABMINISTRATION USECASES: 1) Employee id 2) Employee name 3) Employee field 4) Basic pay 5) Travel allowance 6) Extra allowance 7) Year of experience 8) Total salary ALGORITHM: 1) Start the application. 2) Create the required actors and use case 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. 256MB Intel Pentium IV 40 GB : Rational suits win runner, Emprix : C / C++/JDK 1.6 : VB, VC++, Developer 2000 :Oracle, MS Access.

Software Requirements:

50

51

USECASE DIAGRAM:

employe field employe id

basic pay

employee

travel allowence

administration

extra alloance

employe name year of experience

total salerry

52

SEQUENCIAL DIAGRAM:

employee

dtabase

administration

employe name employe id

employe experience

employe field

employe basic pay

alloances extra alloance+basic pay

employe detail

total salery

53

CLASS DIAGRAM:
employe char employename char employefield int employe id int basic pay int travel alloance int extra alloance float total salery int yearexpirience calculatealloance() calexperirnce() total sal()

adminstration int employe id char employename char employen field int year of joining salery() allowance()

ACTIVITY DIAGRAME

54

enter the employe id number

enter the name

enter the field

if exp>3

show the cust id no

show custname

show cust name

show field name

totall salery exit

totall sallery

55

COLLABORATION DIAGRAME:

1: employe name 3: employe experience 4: employe field 5: employe basic pay employe e dtabase

8: employe detail 7: extra alloance+basic pay 9: total salery 2: employe id 6: alloances

administr ation
Result : Thus the UML Diagram for Employee payroll system was created.

56

8. LIBRARY MANAGEMENT SYSTEM Ex. No: Date : AIM To create a UML diagram of library management system. REQUIREMENT ANALYSIS Hardware Requirements RAM Processor Hard disk Case tools Languages Font end Back end: ACTORS: 1) MEMBERS 2) CIRCULATION CLERK 3) SUPPLIER USECASES: 1) Borrow books 2) Return books 3) Interlibrary loans 4) Do research 5) Reading books, newspapers 7) Check library cards 8) Purchase supplies. ALGORITHM: 1) Start the application. 2) Create the required actors and use case 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. 57 256MB Intel Pentium IV 40 GB : Rational suits win runner, Emprix : C / C++/JDK 1.6 : VB, VC++, Developer 2000 : Oracle, MS Access.

Software Requirements:

Use-case Diagram:

borrow books

check library card

return books

interlibrary loan memebers

do research

read books,newspaper

purchase supplies

58

Activity Diagram:

library card

display the details of the student

enter the library no no check the library number

yes

return book? yes

no

borrow books

go to the counmter and return the book

do research

readbooks, newspaper

purchase supplies

59

Sequence Diagram:
member enter the number check the member details librarysystem clerk supplier

return or borrowing the book giving to the supplier

getting the book or taking the news paper

60

Collaboration Diagram
1: enter the number member librarysys tem

3: return or borrowing the book 5: getting the book or taking 2: check the the news member paper details

supplier

clerk

4: giving to the supplier

Result : Thus the UML Diagrams for Library management system application was created.

61

EX: 9 Date: Aim:

Report- Data Dictionary

To find the meanings for words in the dictionary Problem Statement: A dictionary is a tool for finding meanings for words. Here we have implemented a data dictionary that provides you an interactive way for finding the meaning of words, also the expansions for the abbreviations, also provides some tips like proverbs. If the exact meaning is not available, we can view the alternate words with the similar meanings. We can find the meanings for as many words we want. This application helps to know information about the medical, computer and other terms. If user doesnt know the exact spelling of the word, then he can give the starting letter of word and choose the word from the list of items. SOFTWARE REQUIREMENT SPECIFICATION Introduction Purpose The main purpose of this document is to produce the software requirement specification for the project titled as DICTIONARY CREATION . This document gives note about the problem which is handled in this application, software which is used for this application, needs of the user and also about the other facilities. Glossary Dictionary can be defined as the book which contains collection of words with their corresponding meaning. particular word. Overview The main objective of this project is to guide the user in their document preparation. That is the user can easily know the synonym or antonym of the particular word by referring this dictionary. This also guide or help the user to identify the words 62 The dictionary also store the adjective of the

which has the same meaning. It is a user friendly application. The user can motivated by this project. That is the user can easily prepare the documents with the help of this application. This application some additional features includes information about the medical terms , computer terms , and other information like wonders of the world , nations with capital etc. GENERAL DESCRIPTION In this we discuss about the function of the project and also about the characteristics of the user. Function of the project is to produce the synonyms or antonyms of the particular word which is given by the user. If possible list the words which has the same meaning as that of the users word. User characteristics To utilize the any application the user must posses some capabilities. Likewise, the user must have the following capabilities to use this project. The user must have some computer knowledge. That is about computer, how it is used etc., He/She must know how to use this particular application . Otherwise the user cant utilize the advantage of this application. This may fulfilled by providing helping window or any other ways. The user must also able to type the word with correct spelling, to get the meaning or antonyms of the word. SPECIFIC REQUIREMENTS In this we discuss about the functional requirements and external interface requirements and performance requirements. Functional Requirements: In functional requirements we discuss about the functions which are used and also about the uses of those functions. The functions used in this application are get_synonyms, get_antonyms , get_information, get_other etc., The function get_synonyms is used to retrieve the meaning of the given word or selected word from the list. Searching concept is used to retrieve the meaning from the database. The function get_antonyms is used to retrieve the antonym of the given word

63

or selected word from the list. Searching concept is used to retrieve the meaning from the database.

The function get_information is used to know about the particular term used in the medical or computer field. First enter the term which to be need to know then call the search function which found the correct information for the specified term if it is available and display it. Otherwise display the message no data found. The function get_other is used to retrieve the information like wonders of the world , nations with their capitals and countries with their languages etc. The search function is used to search for the correct information. USECASES: Give the input Search for meaning List the words with specified starting letter Search for any abbreviation Information about any medical, computer or other terms Search for any measurable quantity Search for any useful tips Compare the word with the Database Display the result ACTOR: User

64

Use Case Diagram:

type input

synonyms or antonyms

comparision User

database admn is it verb or noun

(from actor)

search for abbreviation

mathmatical terms

display result

exit

Activity Diagram 65

An activity diagram is a special case of a state machine in which the states are activities representing the performance of operation and the transition are triggered by the completion of the operations. The purpose of an activity diagram is to provide a view of flow and what is going on inside a use case or among several classes.

choose type of information

English

list of alphabets Correct

choosing alphabets search Enter the word starting with

list of words

select the words

list of synonyms

display the words select the word

list of antonyms

Medical list of alphabets

choose alp list of medical words search enter the word we want

display the meaning and the causes

Computer list of alphabet

choose alp NewActivity select the word

search enter the word you want enter the word verb or noun result display the meaning

others

capital currency

Country with capitals Currencey use

proverb

Proverbs

66

IMPLEMENTATION FORM 1: Option Explicit Public db As Database Public rs As Recordset Private Sub Form Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub Private Sub Command1_Click() menu.Show End Sub FORM 2: Option Explicit Public db As Database Public rs As Recordset Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub Private Sub Command1_Click() meaning.Show End Sub Private Sub Command2_Click() Abbrevation.Show End Sub Private Sub Command3_Click() 67

Quantity.Show End Sub Private Sub Command4_Click() tips.Show End Sub Private Sub Command5_Click() End End Sub FORM 3: Option Explicit Public db As Database Public rs As Recordset Private Sub Command1_Click() Dim s As String rs.MoveFirst While Not rs.EOF If Text1 = rs("word") Then s = MsgBox("MATCH IS FOUND", vbOKCancel, "CHECK") If s = vbOK Then Text2.Text = rs("meaning") Exit Sub End If Else rs.MoveNext End If Wend MsgBox ("MATCH IS NOT FOUND") End Sub Private Sub Command2_Click() Text1.Text = "" Text2.Text = "" End Sub Private Sub Command3_Click() 68

End End Sub Private Sub Command4_Click() menu.Show End Sub Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub FORM 4: Option Explicit Public db As Database Public rs As Recordset Private Sub Command1_Click() Dim s As String rs.MoveFirst While Not rs.EOF If Text1 = rs("abv") Then s = MsgBox("MATCH IS FOUND", vbOKCancel, "CHECK") If s = vbOK Then Text2.Text = rs("abrevation") Exit Sub End If Else rs.MoveNext End If Wend MsgBox ("MATCH IS NOT FOUND") End Sub Private Sub Command2_Click() Text1.Text = "" Text2.Text = "" End Sub 69

Private Sub Command3_Click() End End Sub Private Sub Command4_Click() menu.Show End Sub Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub FORM 5: Option Explicit Public db As Database Public rs As Recordset Private Sub Command1_Click() Dim s As String rs.MoveFirst While Not rs.EOF If Text1 = rs("scale") Then s = MsgBox("MATCH IS FOUND", vbOKCancel, "CHECK") If s = vbOK Then Text2.Text = rs("eq-scale") Exit Sub End If Else rs.MoveNext End If Wend MsgBox ("MATCH IS NOT FOUND") End Sub Private Sub Command3_Click() 70

menu.Show End Sub Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub FORM 6: Option Explicit Public db As Database Public rs As Recordset Private Sub Command1_Click() End End Sub Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") End Sub FORM 7: Option Explicit Public db As Database Public rs As Recordset Private Sub Command1_Click() rs.MoveFirst While Not rs.EOF Text1 = rs("tips") rs.MoveNext Wend End Sub Private Sub Command2_Click() End End Sub Private Sub Command3_Click() 71

menu.Show End Sub Private Sub Command4_Click() rs.MoveLast While Not rs.BOF Text1 = rs("tips") rs.MovePrevious Wend End Sub Private Sub Form_Load() Set db = OpenDatabase("c:\data.mdb") Set rs = db.OpenRecordset("select * from table1") rs.MoveFirst Text1 = rs("tips") End Sub Result: Thus the report data dictionary system has been designed and implemented successfully

72

EX: 10 Date:

Case Study - Expert System Abstract Problem Definition Requirement Analysis Functional Analysis Design Phase Code Generation Conclusion Future Usage

Abstract: Creating of a expert system which provides The name of the disease Symptoms of the disease Price of the medicine Efficiency of the medicine Chemical contents of the medicine when the name of the medicine is inputted in the system. Problem Definition: To create an expert system which provides the information about the medicine when the name of it is inputted to the system. Requirements Analysis: Hardware: 1mb memory Pentium 133+, 24 MB RAM Please use 32 bits (65536 colors) of screen color depth or higher. Software: Windows 95/98/Me/NT/2000/XP Rational Rose Enterprise Edition Functional Requirements Analysis: The functions required to provide the required informations are diseaserelated() - must check provide the names of the disease cured by this medicine. symptoms() must provide the symptoms of each diseases related to the medicine. price() provide price of the medicine efficiency() provide efficiency of the medicine to cure the disease chemicalcontents() provide chemical contents of the medicine 73

These are the functions which run in the database of the system to provide the answers for the required query. Design Phase: Use Case Model:

medicine name

disease related

symptoms

user

price

system

medicine efficiency company medicine contents

Class Diagram: System

char disease char symptoms int efficiency float price char contents disease() symptoms() efficiency() price() chemicalcontents()

User
char medname char compname

74

Activity Diagram:

enter medicine name enter company name

if found Name of disease

symptoms

price

not found

efficiency

contents

75

Sequence diagram:
user 1: medicine name system

2: company name

3: Name of disease related

4: symptom 5: price 6: efficiency 7: contents

Collaboration diagram:

1: medicine name 2: company name user 3: Name of disease related 4: symptom 5: price 6: efficiency 7: contents
Conclusion: Therefore by following the above method a well formed pharmaceutical experts system can be made. Future usage: The medicines found later can be made available to the system by updating the database of the system. 76

system