4.

2 E-R DIAGRAMS
An entity relationship diagram is a graphical representation of an organizations data storage requirements. Entity relationship diagrams are abstractions of the real world which simplify the problem to be solved while retaining its essential features. Entities: 1. An entity is an object of concern used to represent the things in the real world. e.g., car, table, book etc. 2. An entity need not be a physical entity, it can also represents a concept in real world, e.g., project, loan etc. Attributes: An attribute is a property used to describe the specific feature of the entity. So to describe an entity entirely, a set of attributes is used. For example, a student entity may be described by the students name, age, address, etc. Relationships: A relationship can be defined as: A connection or set of associations, or A rule for communication among entities.

E-R Diagram: We can also express the overall logical structure of a database using ER model graphically with the help of an E-R Diagram. Features of E-R Diagram: The basic features of ER diagrams are sufficient to design many database situations. However, with more complex relations, it is required to move to enhanced features of ER models, the three such features are:

Generalization Specialization Aggregation

ER diagrams are composed of Rectangles representing entity sets. Ellipses representing attributes. Diamond representing relationship sets.

Let us define the symbols used in the ER diagram.

Entity

Relationship

Identifying Relationship

Weak Entity

Attribute

E-R Diagram for BPCS - Steganography

HiderNa me passwo rd

LoginId Retrieve rId Hider Se nd to LoadImag e

passwor d

public key Retriver

publick ey private key addfile

decri pt StegoIma ge

privatek ey viewd ata

imagety pe

imagesi ze

4.3 UML DIAGRAMS

A diagram is a graphical presentation of a set of elements, most often rendered as a connected graph. UML includes nine such diagrams. Unified Modeling Language (UML) is a probably the most widely known and used notation for object-oriented methods. The Unified Modeling Language (UML) is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct and document the artifacts. A Modeling Language is a language whose vocabulary and rules focus on the conceptual and the physical and the physical representation of a system. Modeling is the designing of the software applications before coding. It is an essential part of large software projects, and helpful to medium and even small projects as well. A model plays an analogous role in software development projects success can assure themselves that business functionality is complete and correct. Care should be taken that end-users needs are met. The underlying premise of UML is that no one diagram can capture the different elements of a system at different points of time in the software life cycle of a system. UML stands for Unied Modeling Language. "The Unified Modeling Language (UML) is a graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system. The UML offers a standard way to write a system's blueprints, i ncluding conceptual things such as business processes and system functions as well as concrete things such as programming language statements, database schemas, and reusable software components." UML is unique in that it has a standard data representation. This representation is called the Meta model. The meta-model is a description of UML in UML. It describes the objects, attributes, and relationships necessary to represent the concepts of UML within a software application. The UML notation is rich and full bodied. It is comprised of two major subdivisions. There is a notation for modeling the static elements of a design such as

classes, attributes, and relationships. There is also a notation for modeling the dynamic elements of a design such as objects, messages, and finite state machines. The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. 4.3.1 USE CASE DIAGRAM: A use case is a set of scenarios that describing an interaction between a user and a system. A use case diagram displays the relationship among actors and use cases. The two main components of a use case diagram are use cases and actors.

An actor is represents a user or another system that will interact with the system you are modeling. A use case is an external view of the system that represents some action the user might perform in order to complete a task.

Use case Diagram for User

Use case Diagram for Hider

Use case Diagram for Retriever

4.3.2 SEQUENCE DIAGRAM UML sequence diagrams are used to to represent or model the flow of messages, events and actions between the objects or components of a system. Time is represented in the vertical direction showing the sequence of interactions of the header elements, which are displayed horizontally at the top of the diagram. Sequence Diagrams are used primarily to design, document and validate the architecture, interfaces and logic of the system by describing the sequence of actions that need to be performed to complete a task or scenario. UML sequence diagrams are useful design tools because they provide a dynamic view of the system behavior which can be difficult to extract from static diagrams or specifications. Notations used in sequence diagram

Object life line

Send message

Return message

Sequence Diagram for Hider

Sequence Diagram for Retriever

4.3.3 CLASS DIAGRAM Class diagrams are widely used to describe the types of objects in a system and their relationships. Class diagrams model class structure and contents using design elements such as classes, packages and objects. Class diagrams describe three different perspectives when designing a system, conceptual, specification, and implementation. These perspectives become evident as the diagram is created and help solidify the design. Classes are composed of three things: a name, attributes, and operations. Below is an example of a class. Notations used in Class diagram

Class name Attribute name operations

Simple Class

Dependency relationship

Association relationship

Realization relationship

Class Diagram for BPCS Steganography

4.3.4 ACTIVITY DIAGRAM Activity diagrams describe the workflow behavior of a system. Activity diagrams are similar to state char diagrams because activities are the state of doing something. The diagrams describe the state of activities by showing the sequence of activities performed.

Activity diagrams can show activities that are conditional or parallel. Activity diagrams should be used in conjunction with other modeling techniques such as interaction diagrams and state char diagram The main reason to use activity diagrams is to model the workflow behind the system being designed. Activity Diagrams are also useful for: analyzing a use case by describing what actions need to take place and when they should occur Simple Activity diagrams consist of:

Initial node. Activity final node. Action node

Initial node

Represented by a fat black dot There can be only one initial (starting) node

Final node

A fat black dot inside a circle (bull's eye symbol) A circle with an x represents the end of a flow (not the whole activity)

Action node

Activity Diagram for Hider

Activity Diagram for Retriever

4.3.5 COMPONENT DIAGRAM A component diagram shows a set of component and their relationship graphically, a component diagram is a collection of vertices and arcs. A component diagram is just a special kind of diagram and shares the same common properties as do all other diagrams- a name and graphical components that are a projection into a model. Component diagrams commonly contain Components Interfaces Dependency, Generalization, association and realization relationships Like all other diagrams, component diagrams may contain notes and constraints. Component diagrams may also contain packages or subsystems, both of which are used to group elements of our model into large chunks. Notations used in Component diagram:

Component

Dependency

Association

Generalization

Component Diagram for BPCS-Steganography

4.3.6 DEPLOYMENT DIAGRAM

A deployment diagram shows the configuration of run time processing nodes and the components that live on them. Deployment diagrams are one of the diagrams used in modeling the physical aspects of an object oriented system. Graphically, a deployment diagram is a collection of vertices and arcs. A deployment diagram commonly contains Nodes, Dependency and Association relationship. Deployment diagrams may also contains components and also contains packages or subsystems, both of which are used to group elements of our model into large chunks. Deployment diagram is a special kind of class diagram which focuses on a systems nodes. Notations used in Deployment diagram:

Processor

Device

Association relationship Deployment diagram for Bpcs steganography