Oose lab notes

GALGOTIAS UNIVERSITY Greater Noida, Gautam Buddha

Nagar Uttar Pradesh, India

SCHOOL OF COMPUTING SCIENCES & ENGINEERING

M.Tech. (Software Engineering) Program

Title Sheet

CSE 563- Object Oriented Software Engineering Lab

L T P C : 0 0 4 2

Course Type : Program Core

Pre-Requisite CSE201

Semester Offered : Winter

Academic Year : 2012-13

Slot : Wed 9:15-10:55 PM, Thu 9:15-10:55 PM (Morning Session)

Class Room : Lab -A209

Faculty Details:

Name : Mr. Thirunavukkarasu K.

Designation : Assistant Professor-Grade III

Web Link

Moodle

https://sites.google.com/thirugalgotias

http://www.galgotia.activemoodle.com/course/view.php?id=341

School : School of Computing Sciences & Engineering

Cabin No : A-018

Intercom : 819

Open Hours : Monday 10 - 11 am, Tuesday 10 – 1 am

Is this Course offered to

more than one Batch? No

If yes, please indicate the

name(s) of other faculty who

is/are sharing this Course

-

https://sites.google.com/thirugalgotias

Galgotias University

COURSE ACTIVITIES

Official Time Table of the Course

Year: 2012-13

Semester: Winter

1 Name of the Faculty : Mr. Thirunavukkarasu K.

2 Subject/Course : Object Oriented Software Engineering Lab Course Code: CSE 563

3 Branch : M.Tech.(Software Engineering)

Time Table: (My Schedule)


COURSE SYLLABUS

Year: 2012-13

Semester: Winter




Course Topics: (Syllabus)

CSE 563 Object Oriented Software Engineering

Lab

L T P C 0 0 4 2

Version No. 1.0

Prerequisite Object Oriented Programming Language, Software Engineering

Objectives: This course provides platform for implementing and designing of software projects using various available object oriented techniques.

Expected Outcome: On completion of this course the student should be able to accomplish the following: Understand various tools and techniques used for designing and implementing software projects using object oriented tools and techniques.

List of Experiments

UML diagrams to be developed are:

1. Use Case Diagram.

2. Class Diagram.

3. Sequence Diagram.

4. Collaboration Diagram.

5. State Diagram

6. Activity Diagram.

7. Component Diagram

8. Deployment Diagram

Reference Book

1 Sommerville : Software Engineering, Pearson Education Publication, 7th ed.

2 R. S. Pressman: Software Engineering: A Practiioners Approach, 5th Edn.,

TMA, New Delhi.

3 J. F. Peters & W. Pedrycz– Software Engineering, John Wiley & Sons,Inc.

2000.

4 Object Oriented Software Engineering: A Use Case Driven Approach, By

Jacobso., Pearson.

5 Object-Oriented Software Engineering: Practical Software Development Using

UML and JAVA By Lethbridge, Tata McGraw Hill Publishers.

6 Object-Oriented Software Engineering: Using Uml, Patterns And Java, 2/E

By Bruegge, Pearson.

Mode of Evaluation Lab examination / viva voce examination

Recommended by the Board of Studies on:

Date of Approval by the Academic Council:

Signature of HOD Signature of Faculty

Thirunavukkarasu K.

Date: Date: 04-04-2013


COURSE OBJECTIVES

Year: 2012-13

Semester: Winter




Course Description:

This course is aimed at helping students build up an understanding of how to develop a

Object Oriented Software System from scratch by guiding them through the development

process and giving them the fundamental principles of system development using object

oriented features. The course will initiate students to the different software process models,

project management, software requirements engineering process, systems analysis and

design as a problem-solving activity, key elements of analysis and design, and the place of

the analysis and design phases within the object oriented system development life cycle.

Prerequisite:

No specific courses are needed.

Course Objectives:

The objectives of this course are to make the students to:

Study of an agile unified methodology and its application to object-oriented software

development. Topics include introduction to software engineering, review of object orientation,

basing software development on reusable technology, developing requirements and modeling,

design patterns, focusing on users and their tasks.

Course Learning Outcomes and relationship with Program Outcomes:

Accomplishments of the student after completing the course:

To identify, formulate, analyze, and solve problems, as well as identify the computing

requirements appropriate to their solutions.

To design, implement, and evaluate software-based systems, components, or programs of

varying complexity that meet desired needs, satisfy realistic constraints, and demonstrate

accepted design and development principles.

To design and conduct experiments appropriate to the discipline, as well as to analyze and

interpret data and communicate effectively with a range of audiences.

4. On completion of this subject / Course the student will :

S. No. Objectives Outcomes

1. To identify, formulate, analyze, and solve problems, as well as

identify the computing requirements appropriate to their solutions.

A,B,E

2.

To design, implement, and evaluate software-based systems,

components, or programs of varying complexity that meet desired

needs, satisfy realistic constraints, and demonstrate accepted design

and development principles.

C,D,F,G,J

3.

To design and conduct experiments appropriate to the discipline, as

well as to analyze and interpret data and communicate effectively

with a range of audiences.

G,I,K

Signature of Faculty

Date: 28-06-2013


COURSE OUTCOMES

Year: 2012-13

Semester: Winter

1 Name of the Faculty : Mr. Thirunavukkarasu K. 2 Subject/Course : Object Oriented Software Engineering Lab Course Code: CSE 563


4. The expected outcomes of the Course / Subject are:

S. No. General Categories of Outcomes Specific Outcomes of the Courses

A. An ability to apply knowledge of mathematics, science

and engineering

Understanding the basics of

software development issues and

applying them into the development

of more advanced software.

B. An ability to design and conduct experiments, as well as

to analyze and interpret data

Different software concepts can be

simulated in the form of a more

advanced software to impart

continuous development .

C. An ability to design a system, component, or process to

meet desired needs within realistic Constraints such as

economic, environmental, social, political, ethical heat

and safety, Manufacturability and sustainability

Further knowledge in this subject

can definitely fulfill the upcoming

demands in all the given areas.

D. An ability to function on multi-disciplinary teams At this computer age the knowledge

of the same provide the strong link

on multi-disciplinary discipline

E. An ability to identify, formulate, and solve engineering

problems

Through software engineering we

insist on constant development in all

aspect by properly analyzing the

previous development, and solve all

types of problem arising during the

cycle .

F. An understanding of professionals and ethical The stakeholder of the software

particularly the software engineer is

supposed to be well acquainted with

all the professionals and ethical

issues related to that particular area

G. An ability to communicate effectively During the Analysis phase

information gathering will play vital

role between system analyst and

customer through effective

communication and at design phase

we must take care of the naïve user

too.

H. The broad education necessary to understand the impact

of engineering solutions in a global, economic,

environmental, and social context

I. A recognition of the need for, and an ability to engage in

lifelong learning

Once a software is developed it

needs a lifelong development

J. A knowledge of contemporary issues Without the knowledge of

contemporary issues none of the

software can be close to the actual

problem

K. An Ability to use the techniques, skills and modern

engineering tools necessary for engineering practice.

Until unless the developer is not

sound enough on technical issues he

can guarantee the development of

the perfect software

5. Objectives – Outcome Relationship Matrix (Indicate the relationships by mark).

Outcomes

Objectives

A B C D E F G H I J K

1.

2.

3.

4.

5.

6.

Total No. of Instructional periods available for the course: -- Sessions

Signature of HOD Signature of Faculty

Thirunavukkarasu K.

Date: Date: 28-06-2013


ASSESMENT SCHEME

Year: 2012-13

Semester: Winter

1. Name of the Faculty : Mr. Thirunavukkarasu K. 2. Subject/Course : Object Oriented Software Engineering Lab Course Code: CSE 563

3. Branch : M.Tech.(Software Engineering)

4. Target

a) Percentage Pass : 100

b) Percentage I class : 100

2. Course Plan

Coverage of course by lectures, assignments and quizzes.

3. Method of Evaluation

3.1 Class Tests (CAT-I & CAT-II)

3.2 Assignments / Seminars / Tutorials

3.3 Mini projects

3.4 Quizzes 3.5 Term End Lab Examination

3.6 Others


QUIZ – SEE

Year: 2012-13

Semester: Winter

1. Which question no longer concerns the modern software engineer?

a. Why does computer hardware cost so much?

b. Why does software take a long time to finish?

c. Why does it cost so much to develop a piece of software?

d. Why can’t software errors be removed from products prior to delivery?

2. Today the increased power of the personal computer has brought about an abandonment of the practice of team development of software. a. True

b. False 3. Software is a product and can be manufactured using the same technologies used for other engineering artifacts. a. True

b. False 4. Software deteriorates rather than wears out because a. Software suffers from exposure to hostile environments

b. Defects are more likely to arise after software has been used often

c. Multiple change requests introduce errors in component interactions

d. Software spare parts become harder to order 5. Most software continues to be custom built because a. Component reuse is common in the software world.

b. Reusable components are too expensive to use.

c. Software is easier to build without using someone else's components.

d. Off-the-shelf software components are unavailable in many application domains. 6. The nature of software applications can be characterized by their information a. complexity

b. content

c. determinacy

d. both b and c 7. Modern software applications are so complex that it is hard to develop mutually exclusive category names. a. True

b. False 8. The so called "new economy" that gripped commerce and finance during the 1990s died and no longer influences decisions made by businesses and software engineers. a. True

b. False 9. The functionality of most computer systems does not need to be enhanced the lifetime of the system. a. True

b. False

10. Process models are described as agile because they a. eliminate the need for cumbersome documentation b. emphasize maneuverability and

adaptability

c. do not waste development time on planning activities d. make extensive use of prototype

creation


COURSE ACTIVITIES

Use Case Diagrams

Year: 2012-13

Semester: Winter




Library Management System:

Use Case Diagram

So following are uses cases of above diagram (Library Management System).

System Use Cases

Main Screen (UC1)

Scope Library Management System

Level User Goal

Goal in Context Present a main menu form which one can access the various functions

of the library management system.

Primary Actor User and Admin

Stakeholders User: Wants to get a specific book for certain period of time

Admin: Wants to keep the record of all books (issued or returned)

and also maintains the record.

Preconditions Run Library Management Software and entered password is correct.

Triggers A previous command completes successfully.

Success Guarantee The Library Management System waits for user input when main

menu is on the screen

Main Success Scenario:

1. Library Management System:

There are following seven options to chose from:

a. Students Membership Record (UC2)

b. Book Catalogue (UC3)

c. Reference books Catalogue (UC4)

d. Book Issued record (UC5)

e. Book returned record (UC6)

f. Fine records (UC7)

g. Reservation for books (UC8)


Waits for user input

Extensions:

1a. if the Password is incorrect than a message is printed on the screen and ask for another

attempt but after the third attempt, if the password is incorrect than the systems does not

ask for reenter the password but it quits to windows.

Students Membership Record (UC2)

Scope Library Management System

Level User Goal

Goal in Context Present a menu from which one can access the various functions

of the Student Membership Record.

Primary Actor Admin

Stakeholders Admin: Wants to enter and maintain the Student Membership

Record.

Preconditions None

Triggers Admin selects Student Membership record option from the

main menu.

Success Guarantee Library Management System Waits for user input

Main Success Scenario:

1. Admin: Selects the menu option to Enter in the Student Membership Record.

2. Library Management System: Presents a Menu for maintaining student Membership

record. That contains the following Four options to choose from.

a. Add Students Record (UC2-1)

b. Edit Students Record (UC2-2)

c. View Students Record (UC2-3)

d. Search for Student Record (UC2-4)


Waits for user input

Extensions:

2a. to enter in the option Add Student Record and Edit Student Record, the system waits

for the Password.

School of Computing Science & Engineering

Lab Manual - Version 1.0

Course Name : Object Oriented Software Engineering Lab

Course Code : CSE563

School : School of Computing Science and Engineering

Program : M.Tech. (SE) Batch : I

Year/Semester : Ist/ 2

nd Semester Session : Winter 2012-13

GALGOTIAS UNIVERSITY Plot No.2, Sector 17-A, Yamuna Expressway,

Greater Noida, Gautam Buddh Nagar, U.P., India

Prepared by:

Mr. Thirunavukkarasu K.

Assistant Professor-Grade III

School of Computing Science and Engineering,

Galgotias University,

Greater Noida.

Table of Contents

S.No. Name of the Experiment Date Page No.

1 Use case of Online Recruitment

System

06.02.2013

2 Class diagram of an ATM System 13.02.2013

3 Sequence Diagram of Geographical

Information System

21.02.2013

4 Collaboration Diagram of an

Online ATM System

28.02.2013

5 State Chart Diagram of a

Transaction Processing System

07.03.2013

6 Activity Diagram of a University

Admission System

04.04.2013

7 Component Diagram of a Online

Railway Reservation System

17.04.2013

8 Deployment Diagram of a Crime

File Management System

25.04.2013

School of Computing Science and Engineering Page | 1

INTRODUCTION

Introduction and Project Definition

Objectives Introduce the lab environment and tools used in the software Engineering lab

Discuss the Project & learn how to write project definition.

1. Outline Introduction to the lab plan and objectives.

Project definition.

2. Background The software engineer is a key person analyzing the business, identifying opportunities for

improvement, and designing information systems to implement these ideas. It is important to

understand and develop through practice the skills needed to successfully design and implement

new software systems.

2.1 Introduction In this lab you will practice the software development life cycle (project management,

requirements engineering, systems modelling, software design, prototyping, and testing) using

CASE tools within a team work environment. UML notation is covered in this lab as the

modelling language for analysis and design.

2.2 Tools Used in the Lab Software Engineering lab is one of the most challenging of all labs. Developing a

complete software application requires from each of you a good level of know-how of

various tools.

There are some tools which will be taught, but there are some which are assumed you

already know, if you don’t, then you learn should it individually.

Rational Rose: for UML diagrams (object oriented analysis and design)

2.3 Software Engineering Lab Objectives

Learn the software life cycle phases (project management, requirements engineering,

software design, prototyping and testing). Practice the software phases using a project.

Learn a number of CASE tools and use them in a project within a team work

environment.

Get familiar with UML (modelling language for analysis and design).


In late 1960‘s people were concentrating on Procedure Oriented Languages such as COBOL,

FORTRAN, PASCAL…etc. Later on they preferred Object Oriented Languages. In the middle

of 1970-80 three Scientists named as BOOCH, RUMBAUGH and JACOBSON found a new

language named as Unified Modeling Language. It encompasses the Designing of the

System/Program. It is a Defacto language.

What is UML?

It is a language. It is not simply a notation for drawing diagrams, but a complete language for

capturing knowledge (semantics) about a subject and expressing knowledge (syntax) regarding

the subject for the purpose of communication.

Applies to modeling and systems. Modeling involves a focus on understanding a subject

(system) and capturing and being able to communicate in this knowledge.

It is the result of unifying the information systems and technology industry‘s best engineering

practices (principals, techniques, methods and tools).

Used for both database and software modeling

Overview of the UML

The UML is a language for

- visualizing

- specifying

- constructing

- documenting

The artifacts of a software-intensive system

Visual modeling (visualizing)

A picture is worth a thousand words!

Uses standard graphical notations

- Semi-formal

- Captures Business Process from enterprise information systems to distributed

Web-based applications and even to hard real time embedded systems

Specifying

• building models that are: Precise, Unambiguous, Complete

• UML symbols are based on well-defined syntax and semantics.

• UML addresses the specification of all important analysis, design, and implementation

decisions.


Constructing

• Models are related to OO programming languages.

• Round-trip engineering requires tool and human intervention to avoid information loss

– Forward engineering — direct mapping of a UML model into code.

– Reverse engineering — reconstruction of a UML model from an implementation.

Documenting

– Architecture, Requirements, Tests, Activities (Project planning, Release management)

Conceptual Model of the UML

To understand the UML, you need to form a conceptual model of the language, and this requires

learning three major elements.

Elements:

1. Basic building blocks

2. Rules

3. Common Mechanisms

Basic Building Blocks of the UML

The vocabulary of the UML encompasses three kinds of building blocks:

• Things

• Relationships

• Diagrams

Things in the UML

• There are four kinds of things in the UML:

1. Structural — nouns of UML models.

2. Behavioral — dynamic (verbal) parts of UML models.

3. Grouping — organizational parts of UML models.

4. Annotational — explanatory parts of UML models.

Structural Things • These are the Nouns and Static parts of the model.

• These are representing conceptual or physical elements.

There are seven kinds of structural things:

1. Class

2. Interface

3. Collaboration

4. Use Case

5. Active Class

6. Component

7. Node


1. Class

It is a description of set of objects that share the same attributes, operations

Methods, relationships and semantics.

2. Interface

A collection of operations that specify a service (for a resource or an action) of a class or

component. It describes the externally visible behavior of that element

3. Collaboration

Define an interaction among two or more classes. – Define a society of roles and other elements.

– Provide cooperative behavior. – Capture structural and behavioral dimensions. – UML uses

pattern as a synonym (careful)


4. Use Case

– A sequence of actions that produce an observable result for a specific actor.

– A set of scenarios tied together by a common user goal.

– Provides a structure for behavioral things.

– Realized through a collaboration (usually realized by a set of actors and the system to be built).

5. Active Class

– Special class whose objects own one or more processes or threads.

– Can initiate control activity.

6. Component – Replaceable part of a system.

– Components can be packaged logically.

– Conforms to a set of interfaces.

– Provides the realization of an interface.

– Represents a physical module of code


7. Node

– Element that exists at run time.

– Represents a computational resource.

– Generally has memory and processing power.

Construct Description Syntax

class a description of a set of

objects that share the same

attributes, operations,

methods, relationships

and semantics.

interface a named set of operations

that characterize the

behavior of an element.

component a physical, replaceable part

of a system that packages

implementation and

provides the

realization of a set of

interfaces.

node a run-time physical object

that represents a

computational resource.

2. Behavioral Things

– These are Verbs of UML models.

– These are Dynamic parts of UML models: ―behavior over time and space

– Usually connected to structural things in UML.


There are two kinds of Behavioral Things:

1. Interaction

It is a behavior of a set of objects comprising of a set of messages exchanges within a particular

context to accomplish a specific purpose.

2. State Machine

It is a behavior that specifies the sequences of states an object or an interaction goes through

during its lifetime in response to events, together with its responses to those events.

3. Grouping Things

These are the organizational parts of the UML models.

There is only one primary kind of group thing:

1. Packages

- General purpose mechanism for organizing elements into groups.

- Purely conceptual, only exists at development time.

- Contains behavioral and structural things.

- Can be nested.

- Variations of packages are: Frameworks, models & subsystems.


4. Annotational Things

• These are Explanatory parts of UML models

• These are the Comments regarding other UML elements (usually called adornments in UML)

There is only one primary kind of Annotational thing:

1. Note

A note is simply a symbol for rendering constraints and comments attached to an element or

collection of elements. Is a best expressed in informal or formal text.

Relationships

There are four kinds of relationships:

1. Dependency

2. Association

3. Generalization

4. Realization

» These relationships tie things together.

» It is a semantic connection among elements.

» These relationships are the basic relational building blocks of the UML.

1. Dependency

It is a semantic relationship between two things in which a change to one thing (the

independent thing) may affect the semantics of the other thing (the dependent thing).

2. Association

It is a structural relationship that describes a set of links, a link being a connection among

objects.


3. Generalization

It is a specialization/generalization relationship in which objects of the specialized element (the

child) are more specific than the objects of the generalized element.

4. Realization

A semantic relationship between two elements, wherein one element guarantees to carry out

what is expected by the other element.


WEEK PLAN

WEEK LAB CONTENT TOOL

Week 1 Introduction

Week 2 Use Case Diagram Star Uml

Week 3 Class Diagram Star Uml

Week 4 Sequence Diagram Star Uml

Week 5 Collaboration

Diagram

Star Uml

Week 6 State Diagram Star Uml

Week 7 Activity Diagram Star Uml

Week 8 Component

Diagram

Star Uml

Week 9 Deployment

Diagram

Star Uml


3. CASE Tools STAR UML is used for this lab.

StarUML was an open source UML tool, licensed under a modified version of GNU GPL. After

being abandoned for some time, the project had a last revival to move from

Delphi to Java/Eclipse and then stopped again. However, the community is still active and many

topics are discussed on the forums.

The stated goal of the project was to replace larger, commercial applications such as Rational

Rose and Borland Together.

StarUML supports most of the diagram types specified in UML 2.0. It is currently

missing object, package, timing and interaction overview diagrams (though the first two can be

adequately modeled through the class diagram editor).

StarUML was written in Delphi, which is one of the reasons why it was abandoned for a long

time. A separate update called WhiteStarUML hopes to address some of the outstanding

problems.

http://en.wikipedia.org/wiki/Open_source

http://en.wikipedia.org/wiki/UML_tool

http://en.wikipedia.org/wiki/GNU_GPL

http://en.wikipedia.org/wiki/Java_(programming_language)

http://en.wikipedia.org/wiki/Eclipse_(software)

http://en.wikipedia.org/wiki/Internet_forum

http://en.wikipedia.org/wiki/Rational_Rose

http://en.wikipedia.org/wiki/Rational_Rose

http://en.wikipedia.org/wiki/Borland_Together

http://en.wikipedia.org/wiki/Unified_Modeling_Language

http://en.wikipedia.org/wiki/Object_diagram

http://en.wikipedia.org/wiki/Package_diagram

http://en.wikipedia.org/wiki/UML_Timing_Diagram

http://en.wikipedia.org/wiki/Interaction_overview_diagram

http://en.wikipedia.org/wiki/Class_diagram

http://en.wikipedia.org/w/index.php?title=WhiteStarUML&action=edit&redlink=1


USE CASE DIAGRAM

ONLINE RECRUITMENT SYSTEM

AIM Online Recruitment is aimed at developing a web-based and central recruitment

Process system for the HR Group for a company.

OBJECTIVE The objective of Online Recruitment System is to record the details various activities

of user.

OVERVIEW This project is aimed at developing a web-based recruitment Process system for the HR

Group for a company. Some features of this system will be creating vacancies, storing

application data, and Interview process initiation, Scheduling interviews, storing

Interview results for the applicant and finally Hiring of the applicant. Reports may be

required to be generated for the use of the HR group.

TOOL USED STAR UML

PRIMARY ACTORS 1. Administrator

2. Jobseekers

3. Company

STAKEHOLDERS 1. Administrator: Administrator has the full authority over the website. He can view

all the registered users and have the power to delete them. He can edit the web pages

and update them. He can view all the company details also.

2. Jobseeker: A jobseeker can register himself. After registration, he will be directed to

his homepage. Here he can update his profile, change password and see the

examination details and all.

3. Company: A company can register itself, conduct online examination, approve or

disapprove candidates attending examination and provides results about the selected

candidates.

USE CASES 1. Download CV’s from job portal

2. Shortlist CV’s

3. Do Screening of CV’s

4. Make Calls to Shortlisted CV Candidates

5. Schedule Interview

6. Get Feedback

7. Upload CV to job portals

8. Update CV

9. Appear for interview

10. Give feedback

11. Conduct examination for job seeker


ANALYSIS 1. PRESENT SYSTEM: - Presently recruitment is done manually. That is if a

company or organization needs employees they make an announcement through

newspaper. People who are eligible send application to the organization or company.

From these applications they are called for interviews or tests. After tests company has

to do short listing manually. From these shortlisted candidates, they are called for

interviews. After interview short listed candidates are employed. So it’s all a time

consuming procedure.

2. PROPOSED SYSTEM: - Online Recruitment is aimed at developing a web-based

and central recruitment Process system for the HR Group for a company. Some

features of this system will be creating vacancies, storing application data, and

Interview process initiation, Scheduling Interviews, Storing Interview results for the

applicant and finally hiring of the applicant. This project Online Recruitment System is

an online website in which jobseekers can register themselves and then attend the

exam. Based on the outcome of the exam the jobseekers will be shortlisted.

THEORY 1. ACTOR: - Actors represent anyone or anything that interact with the system. An

actor may

• Only input information to a system

• Only retrieve information from a system

• Both input and retrieve information to and from a system

2. USE CASE: - A use case can be defined as a sequence of transactions performed by

a system that yields a measurable result of values for a particular actor. Use cases

eventually map to the menu option. Use cases represent the functionality provided by

the system. Each individual functionality provided by a system is captured as a use

case. A use case thus represents a dialog between an actor and the system.


DIAGRAM OF CASE STUDY:-

CONCLUSION They are a central theme for the entire development process. They play a

role in a various stages of the development process as follows:

1. During requirements determination, they specify what the system

should do from the user’s point of view.

2. During analysis and design, the use cases are realized in a design model

.Use case realizations describe the interaction between various objects in

the design model.

3. During implementation, the design model becomes the implementation

specification.

EXERCISE

1. Make case study of Library Information System using Use Case Diagram.

2. Make case study of Adhaar Card System using Use Case Diagram.


CLASS DIAGRAM

ATM SYSTEM

AIM This describes the software requirements for an automated teller machine network

(ATM). It is intended for the designer developer and maintainer of the ATM by

class Diagram.

OBJECTIVE The objective of the ATM system is to provide automatic transactions to the user

and information regarding their accounts without going to the particular branch and

access it from anywhere.

OVERVIEW A single account in a bank against which transactions can be applied. Accounts may

be of various types with at least checking and savings. A customer can hold more

than one account. A station that allows customers to enter their own transactions

using cash cards as identification. The ATM interacts with the customer to gather

transaction information, send the transaction information to the central computer for

validation and processing, and dispenses cash to the customer. We assume that an

ATM need not operate independently of the network.

TOOL USED STAR UML

PRIMARY

ACTORS/CLASSES

1. Bank

2. ATM Info

3. Debit Card

4. Customer

5. Account

6. Current Account

7. ATM Transaction

8. Withdraw Transaction

9. Transfer Money

10. Change Pin

11. Check Balance

12. Saving Account

STAKEHOLDERS 1. Account: - A single account in a bank against which transactions can be applied.

Accounts may be of various types with at least checking and savings. A customer

can hold more than one account.

2. ATM: - A station that allows customers to enter their own transactions using cash

cards as identification. The ATM interacts with the customer to gather transaction

information, send the transaction information to the central computer for validation

and processing, and dispenses cash to the customer. We assume that an ATM need

not operate independently of the network.


3. Bank: - A financial institutions that holds accounts for customers and that issues

cash cards authorizing access to accounts over the ATM network.

4. Bank Computer: - The computer owned by a bank that interfaces with the ATM

network and the bank’s own cashier stations. A bank may actually have its own

internal network of computers to process accounts, but we are only concerned with

the one that interacts with the network.

5. Customer: - The holder of one or more accounts in a bank. A customer can

consist of one or more persons or corporations; the correspondence is not relevant to

this problem. The same person holding an account at a different bank is considered a

different customer.

6. Transaction: - A single integral request for operations on the accounts of a single

customer. We only specified that ATMs must dispense cash, but we should not

preclude the possibility of printing checks or accepting cash or checks. We may also

want to provide the flexibility to operate on accounts of different customers,

although it is not required yet. The different operations must balance properly.

DETAILS OF CLASS DIAGRAM

CLASS ATTRIBUTES OPERATIONS

Bank Bank Id: Char

Location: Char

Manages()

Debit Card Card No: Char

Ownrd By: Char

Access()

Customer Id: Char

Name: Char

Address

Account Type: Char

Owned By: Char

Branch Location: Char

Withdraw()

DepositCash()

Atm Info Location: Char Transaction()

Atm Transaction TransactionId: Char

Date: Date

Amount: Integer

Modify()

Current Account AccNo: Char

Balance: Float

Saving Account AccNo: Char

Balance: Float

Withdraw Transaction Amount: Integer WithdrawMoney()

Transfer Money Amount: Integer

AccNo: Char

TransferAmount()

Check Balance Query: Char QueryProcessing()

Change Pin OldPin: Integer ChangePin()


NewPin: Integer

ANALYSIS 1. PRESENT SYSTEM:- Presently most of people now also withdraw their cash and

transfer their cash by visiting in the Branch itself and takes lots of time and during the

rush hours the Queue in the banks are long and sources in the bank is less. So, it is very

time consuming procedure.

2. PROPOSED SYSTEM:- The ATM must be able to provide the following services to

the customer:

1. A customer must be able to make a cash withdrawal from any suitable account linked

to the card, in multiples of Rupees 100. Approval must be obtained from the bank before

cash is dispensed.

2. A customer must be able to make a deposit to any account linked to the card,

consisting of cash and/or checks in an envelope. The customer will enter the amount of

the deposit into the ATM, subject to manual verification when the envelope is removed

from the machine by an operator. Approval must be obtained from the bank before

physically accepting the envelope.

3. A customer must be able to make a transfer of money between any two accounts

linked to the card.

4. A customer must be able to make a balance inquiry of any account linked to the card.

THEORY Class Diagrams are perhaps the most commonly used Diagrams in modeling object-

oriented systems.

A Class Diagram

Shows a set of classes and interfaces, and their relationship. In an object-oriented system,

no class can stand in a complete isolation from all the other classes. Classes share various

types of relationship with other classes. In fact, a system isa collection of various

collaborating classes. It is through collaboration between various classes that a system

can achieve its final goal.

Contents of a Class Diagram

A class Diagram consists of some logically related classes and interfaces from some

aspects of a system, along with the relationship as well as collaborations between these

classes. The number of classes and interfaces in a non-trivial system is likely to be such

that a single Diagram showing all classes and interfaces, and all their relationship, may

not be practical. We, therefore, make a number of classes Diagrams, each Diagram

representing some specific aspects of a structural relationships and

collaborations between classes. A class may appear in multiple class Diagrams.


Representing classes in a Class Diagram

The complete UML notation for a class Diagram is a rectangle with three compartments.

The first compartment has an optional stereotype and the class name. The second

compartment can be used to show the attributes of a class, while the third compartment is

used for listing the responsibilities of operations of the class. Only the first compartment

is mandatory, the next compartments are optional, and often omitted. Including all

attributes and operations for a class Diagram may not only be unnecessary in most

contexts, but it may also clutter up the Diagram and make them difficult to use.UML also

allows you to render some selected attributes and operations in the respective

compartments


DIAGRAM OF CASE STUDY:-

CONCLUSION This system meets all of the assignment design criteria. It:

Ties multiple accounts to one ATM card and PIN combination

Allows a cardholder to have as many accounts as desired (more than one checking,

more than one credit card, more than one loan, etc.)

Includes all of the account types specified by the assignment – “checking, savings,

loan, mortgage, car or boat loan account and credit card account” – although we chose

to create “vehicle loan” as a loan account which encompasses car, boat, motorcycle,

etc.

Allows cardholders to make balance inquiries, deposits, withdrawals, account

payments, and transfer funds – all with the appropriate accounts displayed for

selection depending upon the type of transaction.


Limits the amount of a withdrawal from an account to $200 – with no limits placed on

fund transfers Limits the number of transactions per day to 10

Provides cardholder with the option of a receipt

EXERCISE

1. Make case study of Home Alarm System using Class Diagram.

2. Make case study of Adhaar Card System using Class Diagram.


SEQUENCE DIAGRAM

GEOGRAPHICAL INFORMATION SYSTEM

AIM To demonstrate that the proposed system is technically feasible and acceptable for the

potential users for medical patients.

OBJECTIVE The objective of Geographical information system is to locate all the hospitals for

medical patients.

OVERVIEW Recent developments in positioning systems and telecommunications have provided

the technology needed for the development of location aware medical applications. We

developed a system, named Emergency Location, which is based upon this technology

and uses a set of sensors that are attached to the patient's body, a micro-computing unit

which is responsible for processing the sensor readings and a central monitoring unit,

which coordinates the data flow.

TOOL USED STAR UML

PRIMARY ACTORS 1. Patient Manager

2. Sensor Manager

3. Network Manager

4. LBS Middleware CMU Service

5. GIS

6. Network Positioning

7. Medical Record Archive

STAKEHOLDERS 1. Patient Manager: Patient Manager has the authority over the website. He can view

all the patients’ record in the various hospitals.

2. Sensor Manager: Sensor Manager has authority to keep track of all the locations

regarding the project emergency location and provide details of the location.

3. Network Manager: Network Manager has authority to provide correct location and

check for the faults in the network.

4. LBS Middleware CMU Service: It is the service which provide the service to the

user from the server.

5. GIS: It is the Geographical Information System which is locating all geographical

information regarding the location i.e. its address, contact numbers etc.

6. Network Positioning: It is the GPS locator when user find request from user and

send request to server then again it send to user.


7. Medical Record Archive: It is the new medical records which is being updated in

the database.

USE CASES 1. Download CV’s from job portal

2. Shortlist CV’s

3. Do Screening of CV’s

4. Make Calls to Shortlisted CV Candidates

5. Schedule Interview

6. Get Feedback

7. Upload CV to job portals

8. Update CV

9. Appear for interview

10. Give feedback

11. Conduct examination for job seeker

ANALYSIS 1. PRESENT SYSTEM: - In the present system, patients have to search the medical

store and shops and hospitals by their own or by the internet in their homes in which

they have to find from large database.

2. PROPOSED SYSTEM:- This system provide the automatic search, parking areas

of hospitals, all the hospitals in the city particularly all registered medical shops and

specialty hospitals search by the type of disease patient have.

THEORY A sequence Diagram shows a pattern of interaction among objects, emphasizing the

sequencing of messages. A message is the mechanism by which an object to execute a

certain responsibility. Normally, we begin drawing a sequence Diagram by placing the

initiating actor at the left and subsequent classes or actors increasingly to the

right. Linking the participating objects or actors by line with an arrow shows a

message. The message line originates from the object or the actor who initiates the

message and arrow points to the object or the actor who is responsible for that message

to be executed. The message line should be labeled with a suitable description of the

message being passed. We can also specify the message. Interaction between actors

should not be shown in a sequence Diagram. Since actors are outside the system, any

interaction between them is also outside the system, and therefore should not be

modeled Sequence Diagram demonstrate the behavior of objects in a use case by

describing the objects and the message they loss. The Diagrams are read left to right

and descending.


DIAGRAM OF CASE STUDY

CONCLUSION This system will benefit project managers, site engineers and clients in the following

manner:

PROJECT MANAGER

• Up-to date information about the progress of work

• Helps in controlling big project sites

• Comes to know about the Cost incurred/Spent and the quantity of materials used on

site

• Reduces time for decision making as all information is in one system

NETWORK MANAGER

• Controlling the project site by knowing the progress of work

• Helps in easy decision making for procurement of funds or materials

• Helps in informing the contractors beforehand about the start of their work

• Helps in knowing how much more material is required

• Helps in reducing wastage of materials

• Helps in ordering the ideal quantity of materials thus by reducing over ordering of

materials


GIS

• Helps in knowing the exact status of the project

• Has a 3-D view of the progress of work thus knowing where large cost has been

incurred

EXERCISE

1. Make case study of Packers and Movers using Sequence Diagram.

2. Make case study of Road Traffic System using Sequence Diagram.


COLLABORATION DIAGRAM

ONLINE ATM SYSTEM

AIM This describes the collaborations or sharing the same goals between clients, bank

and customers.

OBJECTIVE The objective of the system is to know about the flow of the system and the

behavior of the ATM through different perspectives.

OVERVIEW A single account in a bank against which transactions can be applied. Accounts

may be of various types with at least checking and savings. A customer can hold

more than one account. A station that allows customers to enter their own

transactions using cash cards as identification. The ATM interacts with the

customer to gather transaction information, send the transaction information to the

central computer for validation and processing, and dispenses cash to the customer.

We assume that an ATM need not operate independently of the network.

TOOL USED STAR UML

PRIMARY ACTORS 1. Account

2. ATM Machine

3. Checking Account

4. Bank Client

STAKEHOLDERS 1. Account: - A single account in a bank against which transactions can be applied.

Accounts may be of various types with at least checking and savings. A customer

can hold more than one account.

2. ATM: - A station that allows customers to enter their own transactions using

cash cards as identification. The ATM interacts with the customer to gather

transaction information, send the transaction information to the central computer

for validation and processing, and dispenses cash to the customer. We assume that

an ATM need not operate independently of the network.

3. Bank: - A financial institutions that holds accounts for customers and that issues

cash cards authorizing access to accounts over the ATM network.

4. Clients: - Stakeholders which invest in the bank and made profit to bank and

bank revised their various schemes of their customers with the help of clients.


COLLABORATION DETAILS

Objects Message(Flow of Message) Description

ATM Machine Flow towards Bank Client

from ATM Machine

In this ATM flow is towards bank client

and Client request is processing for

taking cash Request Kind

Request Amount

Dispense Cash

Request Take Cash

Take Cash

Request Continuation

Print Receipt

Flow towards Account from

ATM machine

In this transaction is processing and they

getting synchronized with account of the

Account Holder Process Transaction

Bank Client Flow towards ATM Machine

from Bank Client

In this request from server comes back

and they ask to entering the amount from

the client. Enter Kind

Enter Amount

Terminate

Account Flow towards Account from

ATM Machine

Transaction is successful after verifying

with Account Holder’s account.

Transaction Successful

Flow towards Account from

Checking Account

In this synchronization is done

successfully.

Withdrawal Successful

Checking Account Flow towards Checking

Account from Account

In this it is checking that if there are

sufficient funds in account or not.

Withdraw from Checking

Account

ANALYSIS 1. PRESENT SYSTEM: - At present all work is done manually as we know very

well. Now, there are thousands of clients which want to invest in the bank but they

are not happy with their manual work. So, they are fear of taking risk or customer

want to access an account in bank but they are fed up of the long procedures.

2. PROPOSED SYSTEM:- The ATM must be able to provide the following

services to the customer:


1. A customer must be able to make a cash withdrawal from any suitable account

linked to the card, in multiples of Rupees 100. Approval must be obtained from the

bank before cash is dispensed.

2. A customer must be able to make a deposit to any account linked to the card,

consisting of cash and/or checks in an envelope. The customer will enter the

amount of the deposit into the ATM, subject to manual

Verification when the envelope is removed from the machine by an operator.

Approval must be obtained from the bank before physically accepting the envelope.

3. A customer must be able to make a transfer of money between any two accounts

linked to the card.

4. A customer must be able to make a balance inquiry of any account linked to the

card.

THEORY Collaboration is working with each other to do a task. It is a recursive process

where two or more people or organizations work together to realize shared goals,

this is more than the intersection of common goals seen in co-operative ventures,

but a deep, collective, determination to reach an identical objective for example, an

intriguing endeavor that is creative in nature by sharing knowledge, learning and

building consensus. Most collaboration requires leadership, although the form of

leadership can be social within a decentralized and egalitarian group. In particular,

teams that work collaboratively can obtain greater resources, recognition and

reward when facing competition for finite resources. Collaboration is also present

in opposing goals exhibiting the notion of adversarial collaboration, though this is

not a common case for using the word.



CONCLUSION This system meets all of the assignment design criteria. It:

Objects are responsible for small pieces of behaviour of all the system.

High-level functionality is achieved through object collaboration

Participating objects and links between objects.

Interactions (messages sent between objects).

Stereotypes provide a mechanism for distinguishing between different sorts of

object.

EXERCISE

1. Make case study of Library Information System using Collaboration Diagram.

2. Make case study of Security Alarm System using Collaboration Diagram.


STATE CHART DIAGRAM

TRANSACTION PROCESSING SYSTEM

AIM The aim of the study is to focus on what makes a transaction inclusive and how

important is this system

OBJECTIVE The objective is system to make transaction from any part of the world any buy

anything by customers will paid through their cards.

OVERVIEW A customer visits the online shopping portal. A customer may buy item or just visit the

page and logout. The customer can select a segment, then a category, and brand to get

the different products in the desired brand.

The customer can select the product for purchasing. The process can be repeated

for more items. Once the customer finishes selecting the product/s the cart can

be viewed, If the customer wants to edit the final cart it can be done here.

For final payment the customer has to login the portal, if the customer is visiting for the

1st time he must register with the site, else the customer must use the login page to

proceed.

Final cart is submitted for payment and card details and address (where shipment has to

be made) are be confirmed by the customer .Customer is confirmed with a shipment

Id and delivery of goods within 15 days.

TOOL USED STAR UML


2. Customer

STAKEHOLDERS 1. Portal

• Allows the customer to view the different categories and further to different products

within the brands.

• Allows the customer to shop online saying time and cost of customer.

The portal provides a bill and an shipment Id which can be used to track the delivery

status of the goods purchased by the customer.

2. Customer

• Customers when enter the site and view the various products in different category.

• Authentication of the customer is done for the payment of the shopping done

• Customer can browses through the products available in the shop can select some of

them and put into the shopping cart.

• Customer can anytime change the items in the cart either by adding new items or by

removing existing items. Customer proceeds towards the payment counter. Finalize


product list of items he finally wish to buy and make the final payment.

3. Administrator

• Updates the details of the different category ,segments etc

• Verifies the customer card details and records the details for shipment of goods.

STATES 1. Idle: - It is the initial state of the system.

2. Send order request:- In this we send the order through any online website

3. Select normal or special order:- According to cart we choose any types of special

product or schemes

4. Order confirmation: - In this we have to confirm the order to the company on

Online website.

5. Dispatch Order: - At last order is dispatched from the company and reached to the

customer on particular address.

ANALYSIS 1. PRESENT SYSTEM: - Presently all the shopping of any type of the product is

done by peoples by going into the shops and pay cash and they have to carry so much

of cash in hand. So, customers are fed up of going at distant places and also they lack

of varieties.

2. PROPOSED SYSTEM: - Transaction Processing System provides the online

payment gateways to pay for the products buy from anywhere. So, now cash in hand is

less and cards like ATM card, credit card, debit card and many more for transaction.

THEORY A state chart Diagram is a view of a state machine that models the changing behavior

of a state. State chart Diagrams show the various states that an object goes through, as

well as the events that cause a transition from one state to another.

State chart Diagram model elements

The common model elements that State chart Diagrams contain are:

1. States

2. Start and end states

3. Transitions

4. Entry, do, and exit actions


A state represents a condition during the life of an object during which it satisfies some

condition or waits for some event. Start and end states represent the beginning or

ending of a process. A state transition is a relationship between two states that

indicates when an object can move the focus of control on to another state once certain

conditions are met. In a state chart Diagram, a transition to self element is similar to a

state transition. However, it does not move the focus of control. A state transition

contains the same source and target state.



CONCLUSION Being able to buy any time, any place, anywhere, provides exciting opportunities not

only for normal customers but for the Group as a whole, and these benefits are likely to

increase over time.

For potential customers, the site enables them to browse before they shop, and to

research the product so they have more confidence in what they are buying. For normal,

the site offers greater exposure and increased sales. Like all the best arrangements, there

is something in it for all parties.

EXERCISE

1. Make case study of Postal Tracking System using State Chart Diagram.

2. Make case study of Air Ticket Reservation System using State Chart Diagram.


ACTIVITY DIAGRAM

UNIVERSITY ADMISSION SYSTEM

AIM University wants to computerize its admission process for higher education courses.

OBJECTIVE Basic objectives are to extend their reach to geographically scattered students,

reducing time in activities, centralized data handling and paperless admission with

reduced manpower. Cost cutting, operational efficiency, consist view of data and

integration with other institutions are other factors. Main challenges are effectively

sync internal and external operations in such a manner that job can be finished

within time limit and integration with different agencies on an agreed upon common

data format.

OVERVIEW The Department Committee draws up a time schedule for admission and also

decides on the criteria for section and sends its recommendation to the graduation

committee. Once this done, the following procedure is to be followed.

1. The university meets to finalize the draft advertisement, criteria for admission and

preparation of the merit list.

2. All application forms received by the Departments are listed in order of merit and

sent to the Admission Section. The Admission Section prepares merit list of students

other than University which after being approved by the departmental committee, is

sent back to the admission section along with the application forms for further

checking by a specific date.

3. The merit list is complied according to the criteria as decided by the committee

and the principles of reservation as University Rules.

4. After the checking of the forms by the admission committee, the committee is to

meet again to consider and finalize the merit list within a specific date. The prepared

merit list should be prominently displayed at least three days before the actual

admission.

5. The admission section is then to proceed with the admission through counseling

within the due date.

TOOL USED STAR UML


2. Student

3. University


STAKEHOLDERS 1. Administrator: Administrator has the full authority over the website. He can

view all the registered users and have the power to delete them. He can edit the web

pages and update them.

2. Student: Student can give their fee for particular course and enroll in that course.

3. University: It can conduct various examination for different courses and shortlist

according to their particular criteria.

ACTION STATE 1. Fill at Forms

2. Inspect Forms

3. Display student system

4. Input Applicant Information

5. Check the Application of the applicant

6. Search for applicant on system

7. Apply in University

8. Display list of point matchers

9. Create Student Record

10. Enroll in system

11. Calculate Enrolment Fee

12. Display Fee Summary

13. Pay Fee

14. Print Receipt

15. Process Payment

ANALYSIS 1. PRESENT SYSTEM: - The Current System is a browser which is not totally

computerized especially for university admission process. The system takes lots of

time in performing different activities, and there is no centralized data handling.

There is no integration in the current system upon common data format.

2. PROPOSED SYSTEM: - The Proposed system is a browser which is completely

related to internet browsing. The web enabled information management system

designed to automate the entire operations of a modern. This system allows multi-

divisional, multi-department system handling that includes various activities.

THEORY Activity Diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified

Modeling Language, activity Diagrams can be used to describe the business and

operational step-by-step workflows of components in a system. An activity Diagram

shows the overall flow of control.

http://en.wikipedia.org/wiki/Workflow




Activity Diagrams are constructed from a limited number of shapes, connected with

arrows. The most important shape types:

1. Rounded rectangles represent actions;

2. Diamonds represent decisions;

3. Bars represent the start (split) or end (join) of concurrent activities;

4. A black circle represents the start (initial state) of the workflow;

5. An encircled black circle represents the end (final state).

6. Arrows run from the start towards the end and represent the order in which

activities happen.



CONCLUSION They are a central theme for the entire development process. They play a

role in a various stages of the development process as follows:

1. During registration helps lot and save human effort.

2. No mistakes is done when criteria going on.

3. Every student get fair chance through it.

EXERCISE

1. Make case study of Library Information System using Activity Diagram.

2. Make case study of Tracking System using Activity Diagram.


COMPONENT DIAGRAM

ONLINE RAILWAY RESERVATION SYSTEM

AIM The main aim of this project is to give efficient software to reserve, cancel and review

the railway tickets through network in the name of “e-booking”.

OBJECTIVE The ultimate goal of this is to develop database software that enables enterprise user

to reserve the Train tickets, find and retrieve passenger information

OVERVIEW The Customers are required to register on the server for getting access to the database

and query result retrieval. Upon registration, each user has an account which is

essentially the ‘view level’ for the customer. The account contains comprehensive

information of the user entered during registration and permits the customer to get

access to his past reservations, enquire about travel fare and availability of seats, make

a fresh reservations, update his account details, etc.

The Railway Administrator is the second party in the transactions. The administrator

is required to login using a master password, once authenticated as an administrator,

one has access and right of modification to all the information stored in the database

at the server. This includes the account information of the customers, attributes and

statistics of stations, description of the train stoppages and physical description of

coaches, all

The reservations that have been made, etc. The railway administrator has the right to

modify any information stored at the server database.

TOOL USED STAR UML


2. Passenger

3. Management

STAKEHOLDERS 1. Administrator: Administrator has the full authority over the website. He can view

all the registered users and have the power to delete them. He can edit the web pages

and update them. He can view all the reservation details also.

2. Passengers: They perform various tasks as follows:-

1. RESERVE SEAT:-

A passenger should be able to reserve a seat in the train specified by him if available.

For this he has to fill a reservation form with the details about his journey. The clerk

checks for the availability of the seat in the train and if the seat is available then he

makes entries regarding train name, train number, date of journey, boarding station,

and destination. The passenger is the asked to pay the fair .After making payment the

passenger can collect the ticket from the clerk.


2. CANCEL RESERVATION:-

There may arise a case when the passenger wants to cancel his reservation .For this he

has to fill a cancellation form providing all the details about the ticket reserved by

him. The clerk then checks for the entries from the database and cancels the

reservation finally returning the ticket amount with some deduction.

3. UPDATE TRAIN INFORMATION & REPORT GENERATION: -

Only the Administrator has the right to make changes in train details (train name, train

no. etc.).The system should also be able to generate report when needed in the form of

reservation charts, train schedule charts etc.

4. LOGIN-:

Only the user with specified login id & password can get access to the system.

This provides security from unauthorized access.

5.VIEW RESERVATION STATUS & TRAIN SCHEDULE:-

All the users should be able to see the information about the reservation status & train

schedule, train name, train number etc.

COMPONENTS 1. Check availability

2. Modify form

3. Fill form

4. Cancel ticket

5. Book ticket

6. Passenger

7. Ticket

8. Refund

9. Access Database

PACKAGES 1. Reservation Class

2. Access System

ANALYSIS 1. PRESENT SYSTEM:- In old days passengers go to the counters and purchase

the tickets in the long queue which is very time consuming and also by standing long

there is no guarantee that you will get the ticket and all things manually operated by

the railways.

2. PROPOSED SYSTEM: - In Online Railway Reservation System, for booking the

tickets online the intended user has to enter details like username and password.

Once the username and passwords are verified then he is allowed to enter the main

system wherein he can select the destination, date and no of tickets.

For the purchase of the tickets he is asked for payment details (like credit card details


etc).

The user is also provided with a provision of canceling the reservation where in the

entire amount is credited back to his account.

The analysis part also comprises of the UML Diagrams that boost the program.

THEORY Components are wired together by using an assembly connector to connect the

required interface of one component with the provided interface of another

component. This illustrates the service consumer - service provider relationship

between the two components.

An assembly connector is a "connector between two components that defines that one

component provides the services that another component requires. An assembly

connector is a connector that is defined from a required interface or port to a provided

interface or port."

When using a component Diagram to show the internal structure of a component, the

provided and required interfaces of the encompassing component can delegate to the

corresponding interfaces of the contained components.

A delegation connector is a "connector that links the external contract of a component

(as specified by its ports) to the internal realization of that behavior by the

component’s parts."

The example above illustrates what a typical Insurance policy administration system

might look like. Each of the components depicted in the above Diagram may have

other component Diagrams illustrating their internal structure.

http://en.wikipedia.org/wiki/Interface_(computing)



CONCLUSION This project on ONLINE RAILWAY RESERVATION SYSTEM to simple process.

The details of the Train number, Train ticket are used to know about the Train. The

programs are coded in easier and structure manner so that any possible modification

can be done easily. The passenger details, Train details very easily, so that the

passengers reports are generated easily.

EXERCISE

1. Make case study of Criminal Case System using Component Diagram.

2. Make case study of Online Shopping System using Component Diagram.


DEPLOYMENT DIAGRAM

ONLINE CRIME FILE MANANGEMENT SYSTEM

AIM The aim of proposed system is to develop a system of improved facilities. The

proposed system can overcome all the limitations of the existing system. The system

provides proper security and reduces the manual work.

OBJECTIVE It is achieved by creating user-friendly screens for the data entry to handle large

volume of data. The goal of designing input is to make data entry easier and to be

free from errors. The data entry screen is designed in such a way that all the data

manipulates can be performed. It also provides record viewing facilities.

OVERVIEW The project titled as “Online Crime file Management “is a web based application.

This software provides facility for reporting online crimes, complaints, missing

persons, show most wanted person details mailing as well as chatting. Any Number of

clients can connect to the server. Each user first makes their login to sever to show

their availability.

The server can be any Web Server. An SMTP Server must be maintained for

temporary storage of emails and chat jar files for enable the chatting facilities. The

main modules in this project

TOOL USED STAR UML

PRIMARY ACTORS 1. Visitors

2. Registered Users

3. Administrator

STAKEHOLDERS The visitor module include:-

View Hot news: This module help the visitor to see the latest hot news which can

updated by the admin

The registered user module includes,

1. Add Complaint: This module help the user to report online complaints.

2. Add Crime report: This module help the user to report online crimes.

3. Add Missing person: This module help the user to report online missing persons details also we

have to add photos of missing person using heterogeneous database.

4. View Missing persons: This module help the user to view all the missing person

details.

5. View Most wanted persons: This module help the user to view all most

wanted persons which can be given by the administrator.

5. Edit Complaint: This module help the user to edit his complaint details.

6. Edit Account: This module help the user to update his or her profile.

7. View complaint status: This module allows us to view the status of all complaint


that you have posted earlier.

8. View crime status: This module allows us to view the status of the all crimes that

you have posted earlier.

9. Add and View feedback: This module helps the user to add and view feedbacks

10. Chat: This module help the user to chat with the administrator or with

other registered users

11. Mail: This module helps the user to send mail to the administrator.

The administrator module includes:-

1. View and reply user complaint: This module helps the admin to view and reply

users complaint details

2. View and reply user crimes: This module helps the admin to view and reply users

crimes details

3. New admin: This module used for add new admin

4. Add and delete latest hot news: This module helps the admin to add and delete

latest hot news.

5. View and delete users feedback: This module helps the a min to add and delete

users feedback

6. Add, delete and view most wanted persons: This module helps the a min to add, delete and

view most wanted person details

7. Add, delete and view missing persons: This module helps the a min to add, delete and view

missing person details

8. Add and view Criminal registration: This module helps the a min to add and

view criminal registrations

9. Add and view FIR: This module helps the a min to add and view Fir reports

10. Add and view history sheet: This module helps the a min to add and view history

reports

11. View and delete all complaint reply: This module helps the a min to view and

delete complaint reply.

12. Add and view prisoner report: This module helps the a min to add and prisoner reports

13. Change password: This module helps the a min to update his or her password

14. Chat: This module help the admin to chat with the administrator or with

other registered users

15. Mail: This module helps the user to send mail to the user.


NODES/SUB NODES NODES SUBNODES ARTIFACTS

Administrator

Complaints 1. View and reply user

complaint

2. View and reply user

crimes

User Works

1. Add and delete latest hot

news

2. Add and view FIR

User

Registered User 1. Add Crime report

2. Edit Complaint

3. Chat

Visitor 1. View Hot news

ANALYSIS 1. PRESENT SYSTEM: - In the existing system only we can see the details of

particular information about the police stations in our state, the existing system has

more workload for the authorized person, but in the case of Proposed System, the user

can registered in our site and send the crime report and complaint about a particular

city or person.

2. PROPOSED SYSTEM: - The aim of proposed system is to develop a system of

improved facilities. The proposed system can overcome all the limitations of the

existing system. The system provides proper security and reduces the manual work.

The existing system has several disadvantages and many more difficulties to work

well. The proposed system tries to eliminate or reduce these difficulties up to some

extent. The proposed system will help the user to reduce the workload and mental

conflict. The proposed system helps the user to work user friendly and he can easily

do his jobs without time lagging.

THEORY A deployment Diagram in the Unified Modeling Language models the

physical deployment of artifacts on nodes. To describe a web site, for example, a

deployment Diagram would show what hardware components ("nodes") exist (e.g., a

web server, an application server, and a database server), what software components

("artifacts") run on each node (e.g., web application, database), and how the different

pieces are connected (e.g. JDBC, REST, RMI).

The nodes appear as boxes, and the artifacts allocated to each node appear as

rectangles within the boxes. Nodes may have sub nodes, which appear as nested

boxes. A single node in a deployment Diagram may conceptually represent multiple

physical nodes, such as a cluster of database servers.

There are two types of Nodes.

1. Device Node

2. Execution Environment Node


http://en.wikipedia.org/wiki/Artifact_(UML)

http://en.wikipedia.org/wiki/Node_(UML)


Device nodes are physically computing resources with processing memory and

services to execute software, such as typical computer or mobile phones. An execution

environment node (EEN) is a software computing resource that runs within an outer

node and which itself provides a service to host and execute other executable software

elements.



CONCLUSION The project titled as Online Crime file Management´ is a web based

application. This software provides facility for reporting online crimes,

complaints, missing persons, show most wanted person details mailing as

well as chatting. This software is developed with scalability in mind.

Additional modules can be easily added when necessary. The software is

developed with modular approach. All modules in the system have been

tested with valid data and invalid data and everything work successfully.

Thus the system has fulfilled all the objectives identified and is able to

replace the existing system

EXERCISE

1. Make case study of University Enrollment System using Deployment Diagram.

2. Make case study of House Alarm System using Deployment Diagram.

Technology

Oose lab notes