Ooad Record Finalmanual

7/29/2019 Ooad Record Finalmanual

1/74

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 aboutsoftware 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 attributedetermines 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 asystem. 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


2/74

6. STATE DIAGRAM:

State chart diagrams show the possible states of objects and the transitions thatcause 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.

2


3/74


4/74

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

total

percentage

grade

staff student

4


5/74

CLASS DIAGRAM :

staff memberint No.of sub

int marks

int total

float percentage

char grade

int regno

display()

getmarks()

findtotal()

findavg()

assigngrade()

studentschar name

int regno

int collcode

displayresult()

STATE CHART DIAGRAM :

Student detailsubmission

Filter

Process

Report

5


6/74

SEQUENCE DIAGRAM :

Staff Marks Find Totaland Avg

Assigngrade

Student

1: No of subjects

2: Read marks

3: Find total and avg

4: Find grade

5: Store

6: Store marks

COLLABORATION DIAGRAM :

Staff Marks Find Total andAvg

Student

1: No of subjects2: Read marks 3: Find total and avg

6: Store marks

Assigngrade

4: Find grade5: Store

6


7/74

Student Mark Analysis

Code Generation Template :

Staff.cpp

#include "Staff.h"

//##ModelId=4246E53402BBStaff::Display()

{}

//##ModelId=4246E53402BB

Staff::Getmarks(){}


Staff::Findtotal(){}


Staff::Findaverage(){}

//##ModelId=4246E53402BBStaff::Assigncode()

{}

Staff.h

#ifndef STAFF_H_HEADER_INCLUDED_BDB88738

#define STAFF_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class Staff

{ 9public:


Display();//##ModelId=4246E53402BB

Getmarks();


Findtotal();


Findaverage();

//##ModelId=4246E53402BBAssigncode();

private://##ModelId=4246E5290069

No of students;

//##ModelId=4246E5290069

7


8/74

Marks;

//##ModelId=4246E5290069

Total;

//##ModelId=4246E5290069

Percentage;

//##ModelId=4246E5290069Grade;

//##ModelId=4246E5290069Reg No;

};

#endif /* STAFF_H_HEADER_INCLUDED_BDB88738 */

Student.cpp

#include "Student.h"

//##ModelId=4246E53402BBStudent::Displayresult()

{}

Student.h

#ifndef STUDENT_H_HEADER_INCLUDED_BDB88738#define STUDENT_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class Student{

public:

//##ModelId=4246E53402BBDisplayresult();private:

//##ModelId=4246E5290069

Reg No;//##ModelId=4246E5290069

Name;

//##ModelId=4246E5290069College Code;

};

#endif /* STUDENT_H_HEADER_INCLUDED_BDB88738 */Result :

Thus the UML Diagrams for Students Mark Analysis was created.

8


9/74

Ex: 3 QUIZ APPLICATION

Date:

AIM:

To create a UML diagram of a Quiz application.

Requirement Analysis:

Hardware Requirements:

RAM : 256 MBProcessor : 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 2000Back end : Oracle , MS-Access

PROBLEM STATEMENT :

Quiz application has to be developed for verifying the answers and deciding the winnerbased 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. ObjectivesThe 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 andthe 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, whichwill 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.Participant3.Scorer

9


10/74

USE CASES:1.No. of teams

2.Team name

3.No. of participants4.Rules

5.Rounds

6.Questions and answers

7.Time8.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 nameNo.of participantsNo.of rounds

Rules

Questions

Answers

Marks

Interviewer Participant

Prize

Result

Scorer

10


11/74

CLASS DIAGRAM :

q u i z i n te r vi e w e r c h a r t ea m n a m e

i n t t im e

i n t ro u n d s

m a i n t a in t im e l im it ()

a s k q u e s t io n ()

q u i z p a r ti c i p a n t

a n a l y s e t h e q u e s t i o n s ( )g i v e a n s w e r ( )

q u i z s c o re r

ve r i f yanswers ( )g i ve resu l t ( )

ACTIVITY DIAGRAM :

Describe no.of teams,participants,roundsand teamname

Enterround

Askquestions

Getanswer

Checkanswer

Check end ofround

Declareresult

Awardprize

Assignmarks If correct

No

If yes

11


12/74

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:

Interviewer

Marks

WinnerRounds

Participant

6: If yes, announce winner

1: Ask question4: If not correct, ask next question

2: Answer the question

3: If answer is co rrect, provide mark

5: Check e nd of rounds

7: If no, ask next question

12


13/74

Quiz Application


Interviewer.cpp

#include "Interviewer.h"


Interviewer::maintaintimelimit()

{}

//##ModelId=4246E53B000B

Interviewer::Askquestion(){

}

Interviewer.h

#ifndef INTERVIEWER_H_HEADER_INCLUDED_BDB88738

#define INTERVIEWER_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class INTERVIEWER

{public:


maintaintimelimit();


Askquestion();private:

//##ModelId=4246E5290069

Teamname;

//##ModelId=4246E52C0386

Time;

//##ModelId=4246E52C0386

Round;

};#endif /* INTERVIEWER_H_HEADER_INCLUDED_BDB88738 */

Participant.cpp

#include "Participant.h"

//##ModelId=4246E53402BBParticipant::Analysethequestion()

{}

//##ModelId=4246E53B000BParticipant::Giveanswer()

{}

PARTICIPANT.h

13


14/74

#ifndef PARTICIPANT_H_HEADER_INCLUDED_BDB88738

#define PARTICIPANT_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class PARTICIPANT{ public:


Analysethequestion();


Giveanswer();

private:};

#endif /* PARTICIPANT_H_HEADER_INCLUDED_BDB88738 */

Scorer.cpp

#include "Scorer.h"

//##ModelId=4246E5

3402BBScorer::VerifytheAnswer()

{}//##ModelId=4246E53B000B

Scorer::Giveresult(){}

Scorer.h

#ifndef SCORER_H_HEADER_INCLUDED_BDB88738#define SCORER_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class SCORER

{

public://##ModelId=4246E53402BBVerifytheAnswer();

//##ModelId=4246E53B000BGiveresult();

private:

};

#endif /* SCORER_H_HEADER_INCLUDED_BDB88738 */

Result :

Thus the UML Diagrams for Quiz Application was created.

14


15/74

Ex: 4 ONLINE COURSE REGISTRATION SYSTEM

Date:

AIM:

To create a UML diagram of course registration system.



RAM : 256 MBProcessor : Intel Pentium IV

Hard disk : 40 GB


Case tools : Rational suites win runner, Emprix.Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML


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


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


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

15


16/74

ALGORITHM :

1. Start the application.

2. Create the required actors and use cases on the browser window.



ACTORS:

1. Student

2. System

USE CASE:

1. Register no.2. No.of course

3. Course code

4. Fees detail5. Confirmation

6. Certificate submission

7. Credit card transaction8. Course registered successfully

16


17/74

USE CASE DIAGRAM:

s y s t e m student

register no

no of course

cou rse code

fees detail

conf i rmat ion

cert i f ica te submission

cred i t card t ransact ion

course reg ister successfu l ly

17


18/74

CLASS DIAGRAM:

college DB

int no of course

int register no

int course code

int fees detail

int credit card transaction

display()

get detail()

check detail()

course confirmation()

stu

int register no

int course code

int fees detail

int credit card transaction

display()confirmation()

ACTIVITY DIAGRAM:

18


19/74

course

duration

no ofcourse

coursecode

register

sorry tryagain

fees detail

certificatesubmission

credit cardtransaction

confirmationmsg

course registeredsuccessfully

no

yes

SEQUENCE DIAGRAM:

19


20/74

system student

no of course

enter course code

course code entered

course duration

register

fees detail

credit card transaction

certificate submission

confirmation ms g

course registerd sucessfully

COLLABORATION DIAGRAM:

system student

1: no of course2: enter course code

4: course duration6: fees detail

9: confirmation msg10: course registerd sucessfully

3: course code entered5: register

7: credit card transaction8: certificate submission

20


21/74

Online Course Registration System


DBClass.cpp

#include "DB Class.h"//##ModelId=4246E53402BB

DB Class::Addrecord()

{

}//##ModelId=4246E53402BB

DB Class::Modifyrecord()

{}


DB Class::Displayrecord(){

}

//##ModelId=4246E53402BBDB 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:


Addrecord();//##ModelId=4246E53402BB

Modifyrecord();

//##ModelId=4246E53402BBDisplayrecord();

//##ModelId=4246E53402BBMiscellenous();

private:

//##ModelId=4246E5290069

Stud ID;

//##ModelId=4246E5290069

Stu Name;

//##ModelId=4246E5290069

Stu Address;

21


22/74

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


Student::Enterdetails()

{}


Student::Submitform(){}

Student.h

#ifndef STUDENT_H_HEADER_INCLUDED_BDB88738

#define STUDENT_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class Student

{

public:

//##ModelId=4246E53402BBEnterdetails();

//##ModelId=4246E53402BBSubmitform();


22


23/74

ID;

//##ModelId=4246E5290069

Name;

//##ModelId=4246E5290069

Address;

//##ModelId=4246E5290069Course;

//##ModelId=4246E5290069Marks;

//##ModelId=4246E5290069Dob;

};

#endif /* STUDENT_H_HEADER_INCLUDED_BDB88738 */

Regform.cpp

#include "Regform.h"//##ModelId=4246E53402BB

Regform::Openform(){

}

//##ModelId=4246E53402BBRegform::Checkeligibility()

{


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=4246E53402BBOpenform();

//##ModelId=4246E53402BBCheckeligibility();

23


24/74

//##ModelId=4246E53402BBRegister();

//##ModelId=4246E53402BBAssignID();

private:

//##ModelId=4246E5290069Iseligible;

//##ModelId=4246E5290069FormID;

};

#endif /* REG_FORM_H_HEADER_INCLUDED_BDB88738 */

Result:

Thus the UML Diagrams for Online Course Registration was created.

24


25/74

Ex No :5 ONLINE TICKET RESERVATION SYSTEM

Date:

Aim:

To prepare the document and develop Online ticket reservation software using

software engineering methodologies.



RAM : 256 MB

Processor : Intel Pentium IV

Hard disk : 40 GB


Case tools : Rational suites win runner, Emprix.

Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML


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 performlike 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

25


26/74

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 vacancyposition, 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 usershould 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 beintimated 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


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. ScopeThis Supplementary Specification applies to the Student Mark analysis System, whichwill be developed by the OOAD students. This Specification defines the non-functional


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

Actors

1.Passenger2.System DB

Use cases

1. Train info

2. Reserve ticket

3. Train Avail4. Cancel Ticket

ALGORITHM :





26


27/74

Usecase diagram:

Passenger

Enter the Web Site

Exit

Select the Destination

List of Trains

Select the Train

User Details

No of Seats

Ticket Status

Credit Card No

Confirmation

System

27


28/74

Class diagram:

DB

Train Name

Train No

Source

DestinationArrTime

DepTime

Class

Fare

Distance

Getcustomerdetails()

gettraveldetails()

confirmation()

reserveticket()

display()

Process()

Customer

Customer Name

DOB

Sex

Address

Phone

Givedet()

availability()

getconfirm()

reserve()

givecreditcardno()

getticket()

Computer

isavailableticketno

maintaindb()

updatedb()

reserveticket()

deliverticket()

28


29/74

Activity diagram:

Login Web

Site

Select the

Destination

Select the Train

No & No of Seats

Try Later

Create Custom er

Details

Credit Card

Number

Confirmation

Exit

Is AvailableNoYes

29


30/74

Sequence diagram:

Collaboration diagram:

30

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


31/74

Passenger System

DB

1:2:4:5:6:7:

3:10:

8:

9:

Component diagram:

31


32/74

Online ticket registration


DB.cpp

#include "DB.h"


DB::Getcurrentdetails()

{


DB::GetTraveldetails()

{}


DB::Confirmation(){

}

//##ModelId=4246E53402BBDB::Receiveticket()

{}

//##ModelId=4246E53402BBDB::Display()

{


DB::Process()

32

DB

Store &

Update

Computer


33/74

{

}

DB.h

#ifndef DB_H_HEADER_INCLUDED_BDB88738

#define DB_H_HEADER_INCLUDED_BDB88738//##ModelId=4246E52003A5

class DB

{

public://##ModelId=4246E53402BB

Getcurrentdetails();


Gettraveldetails();


Confirmation();


Reserveticket();

//##ModelId=4246E53402BBDisplay();

//##ModelId=4246E53402BBProcess();


Train Name;

//##ModelId=4246E5290069Train No;

//##ModelId=4246E5290069Source;

//##ModelId=4246E5290069Destination;

//##ModelId=4246E5290069

Arr time;

//##ModelId=4246E5290069

Dep time;

//##ModelId=4246E5290069

Class;

33


34/74

//##ModelId=4246E5290069

Fare;

//##ModelId=4246E5290069

Distance;};

#endif /* DB_H_HEADER_INCLUDED_BDB88738 */

Customer.cpp

#include "Customer.h"//##ModelId=4246E53402BB

Customer::Givedetails()

{}


Customer::Availability(){

}

//##ModelId=4246E53402BBCustomer::Getconfirm()

{}

//##ModelId=4246E53402BBCustomer::Reserve()

{


Customer::Givecreditcardinfo()

{}


Customer::Getticket(){}

Customer.h

#ifndef CUSTOMER_H_HEADER_INCLUDED_BDB88738

#define CUSTOMER_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class Customer

{

public:

//##ModelId=4246E53402BBGivedetails();

//##ModelId=4246E53402BBAvailability();

//##ModelId=4246E53402BBGetconfirm();

34


35/74

//##ModelId=4246E53402BBReserve();

//##ModelId=4246E53402BBGivecreditcardinfo();


Getticket();

private:

//##ModelId=4246E5290069Customer Name;

//##ModelId=4246E5290069DOB;

//##ModelId=4246E5290069Sex;

//##ModelId=4246E5290069

Add;

//##ModelId=4246E5290069

Phone;};

#endif /* CUSTOMER_H_HEADER_INCLUDED_BDB88738 */

System.cpp

#include "System.h"


System::Maintaindb(){

}


System::Updatedb()

{

}


System::Reserveticket(){

}


35


36/74

System::Deleiverticket()

{}

System.h

#ifndef SYSTEM_H_HEADER_INCLUDED_BDB88738#define SYSTEM_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class System

{public:


maintaindb();//##ModelId=4246E53402BB

Updatedb();


Reserveticket();


Deliverticket();private:

//##ModelId=4246E5290069Is Available;

//##ModelId=4246E5290069

Ticket No;};

#endif /* SYATEM_H_HEADER_INCLUDED_BDB88738 */

Result :

Thus the UML Diagrams for Online Ticket Reservation was created.

36


37/74

Ex No: 6 ATM SYSTEM

Date:

AIM :

To develop an ATM system using software engineering methodologies.

Problem Statement-

To 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 andPin 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.



RAM : 256 MB

Processor : Intel Pentium IVHard disk : 40 GB


Case tools : Rational suites win runner, Emprix.

Languages : C/C++/JDK1.3, JSDK, Internet explorer, UML


SPECIFICATIONS :

1. Objectives

The purpose of this document is to define requirements of the Student Mark analysissystem. This Supplementary Specification lists the requirements that are not readily

captured in the use cases of the use case model. The Supplementary Specifications andthe 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.

37


38/74

Actors

1.Passenger

2.System DB

Use cases

1.Train info2. Reserve ticket

3. Train Avail

4. Cancel Ticket

ALGORITHM :



3. Go to the new use case view and open a new package.4. Rename the new package with a new name.

Usecase diagram:

C l i en t

Inse r t C a rd

E n t e r P IN

T y p e o f T ra n s a c t i o n

R e m o ve t h e C a r d

E x i t

D e p o s i t A m o u n t

W it h dr aw A m o u n t

A d m in is t ra t o r

Inva l id P INA p p ro va l

T r a n s a c t i o n C o m p l t e d

38


39/74

Activity diagram:

insert card

enter pin no.

valid

displayinvalid

invalid

withdrawalamt

deposit amt

approval

transactioncompleted

check pin no.

check transaction type

withdrawal

deposit

39


40/74

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


.

40


41/74


42/74

ATM Application


ATM Card.cpp

#include "ATM Card.h"

//##ModelId=4246E53402BBATM Card::GetPIN()

{

}


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=4246E53402BBGetPIN();

//##ModelId=4246E53B000BGiveID();

private:

//##ModelId=4246E5290069Card No;

//##ModelId=4246E52C0386PIN ID;

};

#endif /* ATM_CARD_H_HEADER_INCLUDED_BDB88738 */

Customerdetails.cpp

#include "Customer details.h"


42


43/74

Customer details::GetCard()

{}

//##ModelId=4246E53B000BCustomer details::Changevalidity()

{

}


Customer details::ChangePIN()

{}

//##ModelId=4246E53B000BCustomer details::PINEntry()

{

}

Customerdetails.h

#ifndef CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738#define CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class Customer details

{


Get Card();

//##ModelId=4246E53B000BChange validity();

//##ModelId=4246E53B000BChange PIN();

//##ModelId=4246E53B000BPIN Entry();

private:

//##ModelId=4246E5290069Name;

//##ModelId=4246E52C0386Address;

//##ModelId=4246E52C0386Phone No;

43


44/74

//##ModelId=4246E52C0386PIN No;

//##ModelId=4246E52C0386Card ID;

};

#endif /* CUSTOMER_DETAILS_H_HEADER_INCLUDED_BDB88738 */

MainDB.cpp

#include "MainDB.h"


MainDB::Givebalance(){

}

//##ModelId=4246E53B000BMainDB::Checkwithdrawal()

{

}


MainDB::ApprovalorNot(){

}

//##ModelId=4246E53B000BMainDb::GiveAmountvalue()

{

}

MainDB.h

#ifndef MAINDB_H_HEADER_INCLUDED_BDB88738

#define MAINDB_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5class MainDB

{


Givebalance();


44


45/74

Checkwithdrawal();


ApprovalorNot();


GiveAmountvalue();


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=4246E53402BBCarddetails::Checkvalidity(){

}


Carddetails::Readinformation()

{}

Carddetails.h

#ifndef CARD_DETAILS_H_HEADER_INCLUDED_BDB88738

#define CARD_DETAILS_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class Carddetails

{public:

45


46/74


Checkvalidity();


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"


Reports::Checkmoneyavailability(){

}

//##ModelId=4246E53B000BReports::Readamount()

{

}


Reports::Countmoney(){

}

//##ModelId=4246E53B000BReports::Dispatchmoney()

{

}

Reports.h

#ifndef REPORTS_H_HEADER_INCLUDED_BDB88738

46


47/74

#define REPORTS_H_HEADER_INCLUDED_BDB88738

//##ModelId=4246E52003A5

class Reports

{public:


Checkmoneyavailability();


Readinamount();

//##ModelId=4246E53B000B Countmoney();

//##ModelId=4246E53B000BDispatchmoney();


Amount;

#endif /* REPORTS_H_HEADER_INCLUDED_BDB88738 */

Result :

Thus the UML Diagrams for ATM Application was created.

47


48/74

7. EMPLOYEE PAYROLL SYSTEM

Ex.No:7

Date :

AIM

To create a UML diagram of employee payroll.

REQUIREMENT ANALYSISHardware Requirements

RAM 256MB

Processor Intel Pentium IV

Hard disk 40 GB


Case tools : Rational suits win runner, Emprix

Languages : C / C++/JDK 1.6

Font end : VB, VC++, Developer 2000

Back end: :Oracle, MS Access.

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.

48


49/74

49


50/74

USECASE DIAGRAM:

e m p l o y e ea d m i n i s t r a t i

e m p l o y e i d

e m p l o y e n a m e

e m p l o y e f i e l d

b a s i c p a y

t r a v e l a l l o w e n c e

e x t r a a l l o a n c e

y e a r o f e x p e r i e n c e

t o t a l s a l e r r y

50


51/74

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

51


52/74

CLASS DIAGRAM:

employe

char employename

char employefield

int employe id

int basic pay

int travel alloance

int extra alloancefloat 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

52


53/74

enter the employeid number

enter the

name

enter thefield

if exp>3

show thecust id no

showcustname

show custname

show fieldname

totallsalery

totallsallery

exit

53


54/74

COLLABORATION DIAGRAME:

employe

e

dtabase

administr

ation

1: employe name

3: employe experience

4: employe field5: employe basic pay

8: employe detail

2: employe id

6: alloances

7: extra alloance+basic pay9: total salery

Result :

Thus the UML Diagram for Employee payroll system was created.

54


55/74

8. LIBRARY MANAGEMENT SYSTEM

Ex. No:

Date :

AIM

To create a UML diagram of library management system.

REQUIREMENT ANALYSIS

Hardware Requirements

RAM 256MB

Processor Intel Pentium IV

Hard disk 40 GB


Case tools : Rational suits win runner, Emprix

Languages : C / C++/JDK 1.6

Font end : VB, VC++, Developer 2000

Back end: : Oracle, MS Access.

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.

55


56/74

Use-case Diagram:

b o r r o w b o o k s

r et u rn b o o k s

i n t e r l i b r a r y l o a n

d o r e s e a r c h

re a d b o o k s , n e w s p a p e r

p u rc h a s e s u p p l i e s

m e m e b e r s

c h e c k l ib r a ry c a rd

56


57/74

Activity Diagram:

library card

enter thelibrary no

check the librarynumber

return book?

display the detailsof the student

borrowbooks

go to the counmterand return the book

doresearch

readbooks,newspaper

purchasesupplies

yes

no

yes

no

57


58/74

Sequence Diagram:

m e m b e r l i b r a r y s y s t e m s u p p l i e r c l e r k

e n t e r t h e n u m b e r

c h e c k t h e m e m b e r d e t a i l s

r e t u r n o r b o r r o w i n g t h e b o o k

g e t t i n g t h e b o o k o r t a k i n g t h e n e w s p a p e r

g i v i n g t o t h e s u p p l i e r

58


59/74

Collaboration Diagram

m em ber library s y stem

s upplier c lerk

1: enter the num ber

3: return or borrowing the book5: gett ing the book or tak ing the news paper2: chec k t he m em ber deta i

4: giving to the supplier

Result :

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

59


60/74

EX: 9 Report- Data Dictionary

Date:

Aim:

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. The dictionary also store the adjective of the

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

which has the same meaning. It is a user friendly application. The user can motivated by

60


61/74

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 thecharacteristics 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

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

database.

61


62/74

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

62


63/74

Use Case Diagram:

exit

synonyms or antonyms

comparision

is it verb or noun

mathmatical terms

display result

database admn

(from actor)

search for abbreviation

User

type input

Activity Diagram

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

63


64/74

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.

choosingalphabets

Correct

choose type ofinformation

list ofalphabets

list of words

Enter the wordstarting with

display the

words

select the

words

list ofsynonyms

list of antonym s

list of alphabets list of medicalwords

enter the wordwe want

list of alphabet

display the meaningand the causes

list of medicalwords

enter the wordwe want

select the word

display the meaningand the causes

NewA ct ivity s elec t the word

enter the wordyou want

display themeaning

English

Medical

Computer

search

search

search

choose alp

choose alp

enter the word verb or noun result

others Country withcapitals

Currencey us e

Proverbs

capital

currency

proverb

64


65/74

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



Private Sub Form_Load()



End Sub


meaning.Show

End Sub


Abbrevation.Show

End Sub


Quantity.Show

End Sub

65


66/74


tips.Show

End Sub


End

End SubFORM 3:

Option Explicit




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


Text1.Text = ""

Text2.Text = ""

End Sub


End

End Sub

66


67/74


menu.Show

End Sub



Set rs = db.OpenRecordset("select * from table1")End Sub

FORM 4:

Option Explicit




Dim s As String

rs.MoveFirst

While Not rs.EOF

If Text1 = rs("abv") Then


If s = vbOK Then

Text2.Text = rs("abrevation")

Exit Sub

End If

Else

rs.MoveNext

End If

Wend


End Sub


Text1.Text = ""

Text2.Text = ""

End Sub


End

67


68/74

End Sub


menu.Show

End Sub


Set db = OpenDatabase("c:\data.mdb")Set rs = db.OpenRecordset("select * from table1")

End Sub

FORM 5:

Option Explicit




Dim s As String

rs.MoveFirst

While Not rs.EOF

If Text1 = rs("scale") Then


If s = vbOK Then

Text2.Text = rs("eq-scale")

Exit Sub

End If

Else

rs.MoveNext

End If

Wend


End Sub


menu.Show

End Sub

68


69/74




End Sub

FORM 6:Option Explicit




End

End Sub




End Sub

FORM 7:

Option Explicit




rs.MoveFirst

While Not rs.EOF

Text1 = rs("tips")

rs.MoveNext

Wend

End Sub


End

End Sub


menu.Show

End Sub

69


70/74


rs.MoveLast

While Not rs.BOF

Text1 = rs("tips")

rs.MovePrevious

WendEnd Sub




rs.MoveFirst

Text1 = rs("tips")

End Sub

Result:

Thus the report data dictionary system has been designed and implemented successfully

70


71/74

EX: 10 Case Study - Expert System

Date:

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 medicineEfficiency of the medicine

Chemical contents of the medicinewhen 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/XPRational 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 diseasechemicalcontents() provide chemical contents of the medicine

71


72/74

These are the functions which run in the database of the system to provide the answers forthe required query.

Design Phase:

Use Case Model:

usersystem

medicine name

company

disease related

symptoms

price

medicine efficiency

medicine contents

Class Diagram:

Userchar medname

char compname

Systemchar disease

char symptoms

int efficiency

float price

char contents

disease()

symptoms()

efficiency()

price()

chemicalcontents()

72


73/74

Activity Diagram:

enter medicinename

enter companyname

if found

not found

Name ofdisease

contents

price

efficiency

symptoms

73


74/74

Sequence diagram:

user system

1: medicine name

2: companyname

3: Nameof diseaserelated

4: symptom

5: price

6: efficiency

7: contents


user system

1: medic ine nam e2: comp any name

3: Nam e o f d isease re la ted4: sym ptom

5: pr ice6: effici ency7: co ntents

Conclusion:

Th f b f ll i h b h d ll f d h i l

Date post:	03-Apr-2018
Category:	Documents
Upload:	mohammed-thariq
View:	236 times
Download:	0 times

Ooad Record Finalmanual

Documents