INTRUDER DETECTION SYSTEM OVER ABNORMAL INTERNET SEQUENCE DESIGN

Batch No:2 Batch Name: INTRUDERS

NAME

EMAIL

REGISTERNUMBER

P.SHAMILI K.V.V.HARIKA K.V.G.S.MADHURI P.SWAMI

[email protected] [email protected] [email protected] [email protected]

08KD1A0538 08KD1A0527 09KD5A0501 08KD1A0536

GUIDE :A.RAMARAO DATE:09/01/2012

Introduction: To analyse the design, UML language is used.Unified Modelling Language allows the software engineer to express an analysis model using the modelling notation that is governed by a set of syntactic, semantic and pragmatic rules.

A UML system is represented using five different views that describes the system in a different perspective. Each view is defined by a set of diagrams as follows-

User model view: 1. This view represents the system from the users perspective. 2. The analysis representation describes a usage scenario from the end-users

perspective. y Structural model view: 1. In this model, the data and functionality are arrived from inside the system. 2. This view models the static structures. y Behavioural model view: 1. Behavioural model view specify system activity in careful detail, to foresee problems or conflicts before they arise. y Implementation model view: 1. This view deals with how a system will be realized in terms of its physical instantiation, including physical code snippets (source, binary or executable), data, documents etc. y Environmental model view: This view describes the configuration of the system and the relationships between information components, mapping all of the contextual conditions that may impact system function.

UML is specifically constructed through two different domains, which are as follows UML analyses the models, which mainly focuses on user model and structural model views of the system.

 UML designs the models, which mainly focuses on behavioural modelling and its implementation.

Use case Diagram: A use case diagram shows a set of use cases and actors and their relationships. Use case diagrams address the static use case view of a system. These diagrams are especially important in organizing and modelling the behaviour of a system. Use case diagram for Administrator: Here the actor is the administrator , who have rights to add the user , delete the user , modify and update the user details.

Use case diagram for User: Here the actor is user who can register in the website ,perform the operations such as buy, sell and visit .

Use case diagram for packet sequence: In this, the different packets are captured and checked. The domain of the packet is also checked.

Class Diagram: A class diagram shows a set of classes, interfaces, and collaborations and their relationships. These diagrams are the most common diagram found in modelling object-oriented systems. Class diagrams address the static design view of a system. Class diagrams that include active classes address the static process view of a system.

Class diagram for packet sequence:

Sequence Diagram: A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages. The events are performed one after the other. The life line of the object has started and closed when the event is begin after completion the time span of that one closed.

actor register

LOGIN

BUY

SELL

VISIT

buy

sell

visit

logout

Activity Diagram: Activity diagrams describe the workflow behaviour of a system. Activity diagrams are similar to state 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 Diagram for user:

Activity Diagram for Admin:

E-R model:
extn virusName userName firstName lastName userName 1 isValid n Users Approved By 1 Administrator 1 email password organizes n 1 Patterns has 1 Products VirusExtns n organizes passw ord

patternString

productImage

productID

Screen Shots:

2.HOME

3 ABOUT US

4 LOGIN

5 REGiSTRATION

10

11