AIRLINE BOOKING SYSTEM-MCA PROJECT

We are professional service providers for assistance in management studies:

PROJECT REPORTS / PROJECT SYNOPSIS for HR / Finance / Marketing /Operations for all students from all Indian and foreign universities.  We provide great quality Project Synopsis / Project Reports as per student requirements.

Best quality projects & assignments at less price. Mail your requirement at

stuffstudy5@gmail.com or

Call us at 9815333456.

   PROJECT

DONE BY

PROJECT MEMBERS

Table of Contents

INTRODUCTION  WHAT IS UML?....4

UML Provides Standard Notation and Semantics...............................................................................................4

UML Is Not a Method ...............................................................................................................................................4

UML 1.1 EXTENSIONS....................................................................................................................................................5

Stereotypes .................................................................................................................................................................4

Business Modeling Extensions...............................................................................................................................5

Object Constraint Language (OCL) .......................................................................................................................5

FURTHER EXTENSIONS..................................................................................................................................................6

Responsibility-Driven Analysis with CRC Cards.................................................................................................6

Relational Data Modeling ......................................................................................................................................6

AN OVERVIEW OF UML.................................................................................................................................................7

A Use Case Driven Tour...........................................................................................................................................7

Use Cases and Interaction Diagrams.....................................................................................................................7

Class and Implementation Diagrams .....................................................................................................................7

CRC Cards – An Informal UML Extension............................................................................................................7

State Diagrams ..........................................................................................................................................................7

Implementing the Design .........................................................................................................................................9

Testing Against Requirements ................................................................................................................................9

AN IN-DEPTH LOOK AT UML.....................................................................................................................................10

ORGANIZING YOUR SYSTEM WITH PACKAGES........................................................................................................

USE CASE MODELING..................................................................................................................................................

Capture and/or Verify Requirements...................................................................................................................11

Organization of Use Case Diagrams ....................................................................................................................11

A Use Case for Every Scenario ..............................................................................................................................11

Model Alternate Sequences Through "Extends" Relationship .......................................................................12

Eliminate Redundant Modeling Through "Uses" Relationship......................................................................12

Use Cases Aid in Testing System Against Requirements...................................................................................12

SEQUENCE DIAGRAMS................................................................................................................................................. COLLABORATION DIAGRAMS.....................................................................................................................................

ANALYSIS AND DESIGN WITH THE CLASS DIAGRAM............................................................................................. 1

Development of Class Diagram During Analysis...............................................................................................14

Design of System with Class Diagram..................................................................................................................15

MODELING CLASS BEHAVIOR WITH STATE DIAGRAM.......................................................................................... 17

ACTIVITY DIAGRAMS..................................................................................................................................................

Using Activity Diagrams to Model Use Cases ....................................................................................................18

Using Activity Diagrams to Model Classes.........................................................................................................18

MODELING SOFTWARE COMPONENTS.....................................................................................................................

MODELING DISTRIBUTION AND IMPLEMENTATION ............................................................................................. 20

RELATIONAL DATABASE DESIGN – A UML EXTENSION ...................................................................................... 2

USE OF A MODELING TOOL.......................................................................................................................................22

SUMMARY..............................................................................................................................................................23

REFERENCES

Introduction

This whitepaper introduces the Unified Modeling Language (UML), version 1.1. It reviews the diagrams that comprise UML, and offers a Use-Case-driven approach on how these diagrams are used to model systems. The paper also discusses UML's built-in extensibility mechanisms, which enable its notation and semantics to be extended. This paper also suggests extending UML by two non-built-in techniques: CRC cards for responsibility-driven analysis and entity relation diagrams for modeling of relational databases.

What Is UML?

The Unified Modeling Language prescribes a standard set of diagrams and notations for modeling objectoriented systems, and describes the underlying semantics of what these diagrams and symbols

Use Case diagram for modeling the business processes

Sequence diagram for modeling message passing between objects

Collaboration diagram for modeling object interactions

State diagram for modeling the behavior of objects in the system

Activity diagram for modeling the behavior of Use Cases, objects, or operations

Class diagram for modeling the static structure of classes in the system

Object diagram for modeling the static structure of objects in the system

Component diagram for modeling components

Deployment diagram for modeling distribution of the system.

Organizing Your System with Packages

One of the key tasks to modeling a large software system is to break it down into manageable areas first. Whether these areas are called domains, categories, or subsystems, the idea is the same: break the system into areas that have similar subject matter. UML introduces the notion of a package as the universal item to group elements, enabling modelers to

subdivide and categorize systems. Packages can be used on every level, from the highest level, where they are used to subdivide the system into domains, to the lowest level, where they are used to group individual Use Cases, classes, or components.

Figure 2 Organizing System Using Packages

Best quality projects & assignments at less price. Mail your requirement at

stuffstudy5@gmail.com or

Call us at 9815333456.