Escolar Documentos
Profissional Documentos
Cultura Documentos
1. Sanjyot Agureddy (0910880001) 2. Amol Khedkar (0910880007) 3. Bilal Sayyed (0910880015) Students of Third Year Diploma in Computer Engineering Have Successfully Completed The Project On
Acknowledgement
We are very glad to bring this report on Cloud based Fault Management System in the sense and for getting chance to express our grateful acknowledgement
Firstly, we thank to our Project Guide Mr Amol Sawant and Project Coordinator Ms Rupali Davalgaonka maam of Computer Department for the advice, constructive suggestion. They were very encouraging and guiding us throughout the entire project work.
Secondly, we would thank to our Head of Department of Computer Emginnering Prof. Sonali M. Antad, for providing valuable time, space, facilities for carrying out our project.
We are also thankful of all the staff members of our Computer Department and all those who have directly or indirectly helped in the completion of the Project.
Abstract
Today Fault Management System is a key part in Network Management Architecture consists of functions such as detect, isolate, determine the cause and correct the malfunctions in network. Fault Management System helps in increasing network availability, reduce network downtime and restore network failure quickly. In this project once error is reported, first step is to detect the fault and make a report of it. Based on this report we will isolate the fault i.e. to find the exact location of the fault and to determine the cause of the fault. Once isolated the fault need to be corrected and appropriate action need to be taken and report is sent to administrator. The administrator will maintain error logs and keep track of the person who works on the fault. Finally the entire application is deployed on cloud.
Index
Table of content: Chapter no. Name of Topic
Introduction 1.1 Background
Page no.
7 8 9 10 11 12 14 15 16 17 18 19 21 22 23 24 25 26 27 29 30
01
1.2 Need of Project 1.3 Problem Statement 1.4 Scope 1.5 Objective Requirement Analysis 2.1 Information Gathering 2.2 Hardware Requirements 2.3 Software Requirements 2.4 Functional Requirements 2.5 Non-Functional Requirements Design 3.1 Design Diagrams
3.2 Operator Use case Diagram
02
03
3.4 Analyzer Use case Diagram 3.5 Technician Use case Diagram
3.6 Class Diagram
Page no.
32 33 34 35 36 38 39 40 41 42 44 46 47
04
4.2 Module 2 4.3 Module 3 4.4 Module 4 First Page Login Form
05
06 07
Chapter -1
Introduction
Today Fault management System is a key part in a Network Management Architecture consists of Functions such as Detect, Isolate, determine the cause and correct the malfunction in network.
Fault management System helps in increasing Network availability, reduce network downtime and restore network failure quickly
Cloud computing allows consumers and businesses to use applications without installation and access their personal files at any computer with internet access.
Cloud computing is a technology that uses the internet and central remote servers to maintain data and applications
1.1 Background
The reason behind taking this project is that, today there is no Centralized Management System and we intend to make such a centralized Fault Management System.
So here, by using Java, Advance Java and Adobe Flex Builder we design a Centralized Fault Management System which will be deployed on cloud.
For all those Companies that require to maintain a record of their faults
This system will be deployed in cloud like Amazon Web Service which will help in reducing the overhead cost and maintenance.
There is no automatic system that will perform any of the functioning on its own
Entire project is deployed on the Cloud which is dependent on the Internet without which the project is non-functional
10
1.4 Scope
The Scope of the project is the vendor need not maintain their own fault management system.
They can use centralized fault management system which would help them reducing overall cost.
11
1.5 Objective
Design is the first step in moving from problem domain to solution domain. Design is essentially the bridge between requirements specification and the final solution.
The goal of design process is to produce a model or representation of a system can be used later to build that system. The produced model is called the Design of the System. It is a plan for a solution of the system.
The objective of design phase is to: Create User Interface Create Application Create and launch instance Deploy the instance on Amazon Web Service
12
Chapter -2
13
Requirement Analysis
14
At the beginning who studied what is a Fault Management Systems? How does it work? What all working and processing is needed? What different recording and unique properties are used? What is Cloud? How many of the companies use Cloud computing and for what purpose they use?
(For all that download the information from the internet and some from the companies who use fault management system)
15
: : :
Internet Connectivity
16
17
System
Creating Database and storing all the faults information.
18
The project should be deployed on Amazon Web Service supporting Java framework.
Unit testing, System testing will be done for integrity check and reliability check.
Once the project is deployed it runs around the clock from any remote client using internet.
19
Chapter -3
20
Design
Creating Application
J2ee
Database
21
Use case diagrams to organize and model the behaviour of the system Class diagrams to represent the static design view of the system Sequence diagrams to show the time-ordering of the messages
22
23
Views Faults Employee Registration Allocate Work Fault Manager View Progress Checks isolation report Checks Escalation Report
24
Views Assigned Work Analyze Work Allocate Work To Technician Fault Analyzer View Progress Views report Escalates Report
25
Submits Report
26
27
28
29
30
Chapter -4
31
Modules
32
Module 1
The first module is designed to provide authentication to individuals who wish to get connected.
The registration details are stored in the database and whenever the user logs in, the user credentials are retrieved to check whether the user is an authorized user or not.
33
Module 2
In this module the error is reported by the customer and a ticket is generated for the fault.
Manager views the faults, escalates the faults to available analyser or technicians.
He maintains error log and keep track of the problem and person who is working on it.
34
Module 3
In this module Analyzer and Technicians solve the problems allocated by the manager depending on the location from where the error encountered and generate reports after rectifying them.
35
Module 4
In this module administrator maintains error log and keep track of the problem and person who is working on it.
And finally we will deploy entire application in Amazon Elastic Compute Cloud (EC2) of Amazon Web Service
36
Chapter -5
37
38
Manager Login
Employee Login
39
40
41
42
Chapter -6
43
Future Scope
The Scope of the project is the vendor need not maintain their own fault management system.
They can use centralized fault management system which would help them reducing overall cost.
In this project we will overcome the above drawbacks by creating a centralized fault management system. This system will be deployed in cloud like Amazon Web Service which will help in reducing the overhead cost and maintenance.
44
Chapter -7
45
Conclusion
Service Developers want the Service Providers to ensure or provide the capability to dynamically allocate and manage resources in response to changing demand patterns.
It is now possible to provide dynamic visibility and control of services management to meet the rapidly growing demand for Amazon Web Service.
46
Bibliography
The applicable IEEE standards as published in IEEE standards collection, for the preparation of SRS. www.google.com/cloud-computing www.wikipedia.com
47