of 75
8/14/2019 Final Repor(Swapnil AMS)
1/75
Bansilal Ramnath Agarwal Charitable Trusts
Vishwakarma Institute Of Technology, Pune-37Department Of Computer Engineering
Project Synopsis
Group No : I-08
Group Members:
Roll
No
Name Class Contact No Email-ID
07 Swapnil Bhala B.E.-J 9850335176 [email protected]
39 Kailash Vetal B.E.-J 02026991665 [email protected]
40 Sagar Shintre B.E.-J 9970290528 [email protected]
Academic Year : 2008-09
Project Title : Application Monitoring System
Project Area : Computer Networks/ Real Time Systems
Sponsor Company : Cognizant Technology Solution India Pvt. Ltd
Company Address : Plot No. 26/27, Pune IT Park, MIDC, Hinjewadi, Pune,Maharashtra 411027
Internal Guide : Mr.J.B.Karande
Name of theExternal Guide : Mr.Sandeep BhaleContact No : 9822976583
Signature of Internal Guide
1
8/14/2019 Final Repor(Swapnil AMS)
2/75
Table of Contents
Project Synopsis 3
Feasibility Study Report 8
Project Plan 14
System Requirement Specification 18
Use Case Diagrams 25
Sequence Diagrams 30
State-Chart Diagrams 37
Activity Diagrams 40
System Design 42
2
8/14/2019 Final Repor(Swapnil AMS)
3/75
Vishwakarma Institute of Technology, Pune-37.
Application Monitoring System
Bansilal Ramnath Agarwal CharitableTrusts
09/24/2008
Approvals Signature Block
Project Responsibility Signature Date
Project Guide (Internal)
Project Guide (External)
Documentation Leader
3
8/14/2019 Final Repor(Swapnil AMS)
4/75
Department of Computer Engineering
Table of Contents
1. CONTEXT .............. .............. .............. ............... .............. .............. .............. .............. ........... ..6
2. PROBLEM ............. .............. .............. .............. .............. ............... .............. ............ ...... ...... ...7
3. SOLUTION .............. .............. ............... .............. .............. .............. .............. .............. ............... ...... ...... .....8
4. BENEFITS ............. .............. .............. .............. .............. ............... .............. .............. .............. .............. .......9
5. INTRODUCTION ............................................................................................................13
5.1 PURPOSE...................................................................................................................................................... 13
5.2 METHODOLOGY............................................................................................................................................. 145.3 REFERENCES................................................................................................................................................. 14
6. GENERAL INFORMATION ............ ............... .............. .............. .............. .............. ............. ...... ...... ......14
6.1 CURRENT SYSTEMSAND PROCESSES ...............................................................................................................14
6.2 SYSTEM OBJECTIVES...................................................................................................................................... 14
6.3 ISSUES......................................................................................................................................................... 16
6.4 ASSUMPTIONSAND CONSTRAINTS....................................................................................................................16
7. ALTERNATIVES .............. .............. .............. .............. ............... .............. .............. .............. .............. .......16
7.1 COMPARISONSOF ALTERNATIVES ....................................................................................................................16
8. RECOMMENDATIONS AND CONCLUSION ............. .............. .............. .............. ............. ..... ..... ......17
9. OVERVIEW .............. ............... .............. .............. .............. .............. ............... .......... ..... ..21
10. GOALS AND SCOPE ............. .............. ............... .............. .............. .............. .............. .....22
10.1 PROJECT GOALS.......................................................................................................................................... 2210.2 PROJECT SCOPE.........................................................................................................................................22
10.2.1 Included .......................................................................................................................................23
10.2.2 Excluded ......................................................................................................................................23
11. SCHEDULE AND MILESTONES ............. ............... .............. .............. .............. .............. .............. ......23
12. INTRODUCTION ..........................................................................................................28
12.1 PURPOSE.................................................................................................................................................... 28
12.2 SCOPE.......................................................................................................................................................28
12.3 DEFINITIONS, ACRONYMS, ANDABBREVIATIONS................................................................................................28
12.4 REFERENCES............................................................................................................................................... 29
12.5 OVERVIEW.................................................................................................................................................29
13. OVERALL DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....29
PROBLEM STATEMENT.........................................................................................................................................29
13.1 PRODUCT PERSPECTIVE................................................................................................................................30
PRODUCT POSITION STATEMENT............................................................................................................................ 30
13.1.1 System Interfaces ........................................................................................................................30
13.1.2 User Interfaces .......................................................................................................................... ..30
4
8/14/2019 Final Repor(Swapnil AMS)
5/75
13.1.3 Hardware Interfaces ....................................................................................................................31
13.2 PRODUCT FUNCTIONS................................................................................................................................... 31
13.3 ASSUMPTIONSAND DEPENDENCIES................................................................................................................. 31
14. SPECIFIC REQUIREMENTS .............. .............. .............. ............... .............. .............. .............. ........ ...31
14.1 FUNCTIONS................................................................................................................................................. 31
14.2 LOGICAL DATABASE REQUIREMENTS..............................................................................................................31
14.3 SOFTWARE SYSTEM ATTRIBUTES.................................................................................................................... 31
14.3.1 Reliability ....................................................................................................................................31
14.3.2 Security .................................................................................................................. .....................3214.3.3 Portability ....................................................................................................................................32
14.3.4 Efficiency ....................................................................................................................................32
15. USE CASE TEMPLATE .............. .............. .............. ............... .............. .............. .............. .............. ..... ..37
USE CASE # 1 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .39
USE CASE # 2 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .40
16. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....44
16.1 SCENARIO DESCRIPTION...............................................................................................................................44
17. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....44
18. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....46
18.1 SCENARIO DESCRIPTION...............................................................................................................................47
19. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....47
20. STATE CHART DIAGRAM OVERVIEW ............. .............. ............... .............. ......... ...... ......52
20.1 STATES DESCRIPTION..................................................................................................................................52
21. CLASS DIAGRAM DESCRIPTION ............. .............. .............. ............... .............. .............. ............. ...59
21.1 CRC TEMPLATE.........................................................................................................................................59
21.2 CRC CARDS OVERVIEW.............................................................................................................................. 61
Responsibility........................................................................................................................................61Collaborator..........................................................................................................................................62Domain Users (3-5 people)...................................................................................................................62
OO Design Analyst (1-2 people)...........................................................................................................62
Facilitator (1 person).............................................................................................................................63
Scribe (1-2 people)................................................................................................................................63
Observers (0-N people).........................................................................................................................63
The CRC Technique..............................................................................................................................64
Selecting a Scenario..............................................................................................................................64
Creating Initial CRC Card(s)................................................................................................................64Arranging the CRC Cards.....................................................................................................................65
The CRC Interview...............................................................................................................................65Finding Classes.....................................................................................................................................65
Finding Collaborators...........................................................................................................................6621.2.1 General Guidelines .................................................................................................................. ....67
21.2.2 Class Style Guidelines ................................................................................................................68
21.2.3 Interfaces .....................................................................................................................................70
21.2.4 Relationship Guidelines ................................................................................................ ...... ...... ..71
21.2.5 Inheritance Guidelines ................................................................................................................73
21.2.6 Aggregation and Composition Guidelines .................................................................... ...... ...... ..7321.3 CLASS DIAGRAM......................................................................................................................................... 75
5
8/14/2019 Final Repor(Swapnil AMS)
6/75
1.CONTEXT
In large, complicated systems, which depend on various applications for their
smooth functioning, application monitoring plays a vital role by helping to detect the
problems and act on them before they become critical. But unfortunately much
attention is not paid to develop the effective application monitoring system till now.
The available systems monitor clientside systems health rather than monitoring
applications which may lead to inaccurate results. Also these systems are heavy on
client side and have poor error reporting capabilities which creates need of the new
effective, efficient, light-weight Application monitoring system.
6
8/14/2019 Final Repor(Swapnil AMS)
7/75
In proposed application monitoring system applications are monitored constantly in
order to address any issue before it becomes a serious issue using Health Monitoring
system. Health monitoring is a simple arrangement in which a snapshot of system &
application parameters is compared with the standard benchmarks for finding health
of the system.
The monitoring process is continued to execute multiple number of times by
deciding the polling interval depending upon the criticality of the applications.
Depending upon the criticality of the applications, the monitoring can be performed
at frequent intervals as required. The process of deployment and working of the
application monitoring system can be shown as:
STEP 1: Application Monitoring Program is installed locally on a Client that has
applications that need to be monitored.
STEP 2: Application Monitoring Program starts one or more programs that admin
specify.
STEP 3: Configure your network monitoring tool* to monitor the appropriate TCP/IP
port where Application Monitoring System resides.
The project helps a great deal in resolving problems on the client side
thus reducing the load on the administrator. Precise error reporting & event logging
in the system will help administrator to great extend while diagnosis of the problem.
The monitoring of system for efficient utilization of resources increases performance
of applications at client side. In this way the project serves as an important
application for business firm and software industry.
2.PROBLEM
The system should find applications which are vital for business process and
decides performance of the business firm. This application must be embedded
directly into the monitoring system for monitoring values of crucial parameters.
The system should set benchmark for every client before monitoring. The system
must check the crucial parameter values of client side application for detecting its
health.
7
8/14/2019 Final Repor(Swapnil AMS)
8/75
Application monitoring system must generate event log data and alert report as
an output for the debugging of the error and automated or manual error correction.
The monitoring system requires few network resources as well as memory for
sending the parameters value to administrator.
3.SOLUTION
In order to enable the administrator to perform well and to enable the correction of
minor errors at the client-side, we will implement the Application Monitoring Wizard
which will takes care of the client side applications and reports to the administrator in
case of any discrepancy.
This project will mainly extends to the monitoring of system specific important
applications to check for the occurrence of errors through use of certain control
parameters and generate reports and alerts. The monitoring process will continue to
execute multiple numbers of times by deciding the polling interval depending upon
the criticality of the applications. Thus we will get a complete overview of the
performance of the various applications in our system after specific time intervals.
Depending upon the criticality of the applications, the monitoring will perform at
frequent intervals as require.
The project extends to the development of the wizard, which monitors the
embedded applications and generates reports and alert messages. Also a database
is maintained, which will has records of all the errors encountered till date.
8
8/14/2019 Final Repor(Swapnil AMS)
9/75
4.BENEFITS
Proactive Monitoring :
You can prevent failures in your applications even before your users notice them.
This proactive monitoring can be done by setting thresholds for application variables.
When thresholds are crossed, you can opt to get notified through standard
mechanisms.
Integrated Applications, Servers, and Systems Monitoring :
Applications Manager is an integrated solution that provides you insight into your
diverse applications. You do not have to rely on multiple monitoring tools for each of
your IT resource. Applications Manager provides a single view of your entire business
infrastructure.
An Affordable Solution :
With its low price and ease of deployment, Applications Manager enables a very
affordable alternative to manage complex applications and servers. Applications
Manager requires standard hardware, supports multiple operating systems, and can
be used without extensive training.
9
8/14/2019 Final Repor(Swapnil AMS)
10/75
Vishwakarma Institute of Technology, Pune-37.
Application monitoring systemBansilal Ramnath Agarwal Charitable
Trusts
10/ 11 /2008
Approvals Signature Block
Project Responsibility Signature Date
Project Guide (Internal)
Project Guide (External)
Documentation Leader
Department of Computer Engineering
10
8/14/2019 Final Repor(Swapnil AMS)
11/75
Table of Contents
1. CONTEXT .............. .............. .............. ............... .............. .............. .............. .............. ........... ..6
2. PROBLEM ............. .............. .............. .............. .............. ............... .............. ............ ...... ...... ...7
3. SOLUTION .............. .............. ............... .............. .............. .............. .............. .............. ............... ...... ...... .....8
4. BENEFITS ............. .............. .............. .............. .............. ............... .............. .............. .............. .............. .......9
5. INTRODUCTION ............................................................................................................13
5.1 PURPOSE...................................................................................................................................................... 135.2 METHODOLOGY............................................................................................................................................. 14
5.3 REFERENCES................................................................................................................................................. 14
6. GENERAL INFORMATION ............ ............... .............. .............. .............. .............. ............. ...... ...... ......14
6.1 CURRENT SYSTEMSAND PROCESSES ...............................................................................................................14
6.2 SYSTEM OBJECTIVES...................................................................................................................................... 146.3 ISSUES......................................................................................................................................................... 166.4 ASSUMPTIONSAND CONSTRAINTS....................................................................................................................16
7. ALTERNATIVES .............. .............. .............. .............. ............... .............. .............. .............. .............. .......16
7.1 COMPARISONSOF ALTERNATIVES ....................................................................................................................16
8. RECOMMENDATIONS AND CONCLUSION ............. .............. .............. .............. ............. ..... ..... ......17
9. OVERVIEW .............. ............... .............. .............. .............. .............. ............... .......... ..... ..21
10. GOALS AND SCOPE ............. .............. ............... .............. .............. .............. .............. .....22
10.1 PROJECT GOALS.......................................................................................................................................... 22
10.2 PROJECT SCOPE.........................................................................................................................................22
10.2.1 Included .......................................................................................................................................2310.2.2 Excluded ......................................................................................................................................23
11. SCHEDULE AND MILESTONES ............. ............... .............. .............. .............. .............. .............. ......23
12. INTRODUCTION ..........................................................................................................28
12.1 PURPOSE.................................................................................................................................................... 28
12.2 SCOPE.......................................................................................................................................................28
12.3 DEFINITIONS, ACRONYMS, ANDABBREVIATIONS................................................................................................28
12.4 REFERENCES............................................................................................................................................... 29
12.5 OVERVIEW.................................................................................................................................................29
13. OVERALL DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....29
PROBLEM STATEMENT.........................................................................................................................................29
13.1 PRODUCT PERSPECTIVE................................................................................................................................30PRODUCT POSITION STATEMENT............................................................................................................................ 30
13.1.1 System Interfaces ........................................................................................................................3013.1.2 User Interfaces .......................................................................................................................... ..30
13.1.3 Hardware Interfaces ....................................................................................................................31
13.2 PRODUCT FUNCTIONS................................................................................................................................... 31
13.3 ASSUMPTIONSAND DEPENDENCIES................................................................................................................. 31
14. SPECIFIC REQUIREMENTS .............. .............. .............. ............... .............. .............. .............. ........ ...31
14.1 FUNCTIONS................................................................................................................................................. 31
11
8/14/2019 Final Repor(Swapnil AMS)
12/75
14.2 LOGICAL DATABASE REQUIREMENTS..............................................................................................................31
14.3 SOFTWARE SYSTEM ATTRIBUTES.................................................................................................................... 31
14.3.1 Reliability ....................................................................................................................................3114.3.2 Security .................................................................................................................. .....................32
14.3.3 Portability ....................................................................................................................................32
14.3.4 Efficiency ....................................................................................................................................32
15. USE CASE TEMPLATE .............. .............. .............. ............... .............. .............. .............. .............. ..... ..37
USE CASE # 1 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .39
USE CASE # 2 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .40
16. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....44
16.1 SCENARIO DESCRIPTION...............................................................................................................................44
17. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....44
18. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....46
18.1 SCENARIO DESCRIPTION...............................................................................................................................47
19. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....47
20. STATE CHART DIAGRAM OVERVIEW ............. .............. ............... .............. ......... ...... ......52
20.1 STATES DESCRIPTION..................................................................................................................................52
21. CLASS DIAGRAM DESCRIPTION ............. .............. .............. ............... .............. .............. ............. ...59
21.1 CRC TEMPLATE.........................................................................................................................................59
21.2 CRC CARDS OVERVIEW.............................................................................................................................. 61
Responsibility........................................................................................................................................61
Collaborator..........................................................................................................................................62
Domain Users (3-5 people)...................................................................................................................62OO Design Analyst (1-2 people)...........................................................................................................62
Facilitator (1 person).............................................................................................................................63
Scribe (1-2 people)................................................................................................................................63
Observers (0-N people).........................................................................................................................63The CRC Technique..............................................................................................................................64
Selecting a Scenario..............................................................................................................................64
Creating Initial CRC Card(s)................................................................................................................64
Arranging the CRC Cards.....................................................................................................................65The CRC Interview...............................................................................................................................65
Finding Classes.....................................................................................................................................65
Finding Collaborators...........................................................................................................................66
21.2.1 General Guidelines .................................................................................................................. ....67
21.2.2 Class Style Guidelines ................................................................................................................68
21.2.3 Interfaces .....................................................................................................................................70
21.2.4 Relationship Guidelines ................................................................................................ ...... ...... ..71
21.2.5 Inheritance Guidelines ................................................................................................................7321.2.6 Aggregation and Composition Guidelines .................................................................... ...... ...... ..73
21.3 CLASS DIAGRAM......................................................................................................................................... 75
12
8/14/2019 Final Repor(Swapnil AMS)
13/75
5.INTRODUCTION
This document provides the purpose of the feasibility study, the background of the
proposed project, the methodology used for performing the study, and any reference
materials used in conducting the feasibility study.
In complicated systems used these days, there is lot of overhead on the
administrator of the system so as to keep track of the clients. This may lead to low
performance by the administrator and may also lead to low performance by the system.
So in order to enable the administrator to perform well and to enable the correction of
minor errors at the client-side, we implement the Application Monitoring Wizard which
takes care of the client side applications and reports to
the administrator in case of any discrepancy.
5.1PURPOSE
The purpose of feasibility study is to analyze the existing Application Monitoring
System and new features that can help to increase the accuracy. This document studies
whether the proposed system is realizable or not. Also, it includes whether the problem
13
8/14/2019 Final Repor(Swapnil AMS)
14/75
exists and solution to be implemented would be able to solve the problem or not. It is
also useful for deciding the constraints on the system and assumptions to be made while
implementing the solution.
The feasibility study takes into account the following factors:
Technology
Hardware Characteristics
Resources
5.2METHODOLOGY
Following techniques are used to understand the feasibility of the system to be
created.
Surveying:
This part of studying feasibility consists of exactly studying the proposed system by
collecting information through different sources like finding information about the similar
line products etc.
5.3REFERENCES
1.www.monitools.com
2.www.ibm.com
3.www.java.sun.com
4.IEEE paper on "Parameter passing for the JVM" by Gough, K. J,Computer Science
Conference, 2000, ACSC 2000, 23rd Australasian
5. "NetRexx Programming for the JVM" by Rick Hightower
6.GENERAL INFORMATION
6.1CURRENT SYSTEMSAND PROCESSES
Some currently implemented monitoring Application monitor one application only.
6.2SYSTEM OBJECTIVES
14
http://www.monitools.com/http://www.ibm.com/http://www.java.sun.com/http://www.ibm.com/http://www.java.sun.com/http://www.monitools.com/8/14/2019 Final Repor(Swapnil AMS)
15/75
General Description of Proposed System:
The aim of the project is to enable the constant monitoring of software
applications to check for the occurrence of errors through use of certain control
parameters and generate reports and alerts.
Major Performance objectives:
a. Whether the System will be automated?The generation of alerts and reports will be automated by the Client side
application. The user only needs to enter verification id to view this reports.
b. Functionalities:
Application Monitoring System provides safe way to monitor crucial Application. Itprovides the following functionalities:
1. Check the values of critical parameters of embedded application.2. Determine the health status of application.3. Determine and keep track of errors.
Processes and Operations Required
Process Method UsedFor
ImplementationRetrieve values of critical parameter MonitoringThread
Comparison of critical parameter StringCompare
Create report create reportSend report/alerts to Server SOCKET
System End ProductThe end product is an Application Monitoring Tool implemented using NetBeans
IDE 6.1 for client and server side(optional)
Cliento Install Application:
o Retrieve values of critical parameter
o Create Report
o Notification: It notifies server about values of parameter and health status.
15
8/14/2019 Final Repor(Swapnil AMS)
16/75
Servero View reports.
o Take proper step to increase performance.
6.3ISSUES
1. User may get frustrated by getting notifications.
6.4ASSUMPTIONSAND CONSTRAINTS
INSTALLATIONThe Application that our Application will monitor must install first.
INTERACTION WITH APPLICATION
To check values of critical parameters, we can make use of thread concept tomake it more effective. Also it makes use of URL from browser so Internet Explorercomes into picture.
FINANCIAL CONSIDERATIONS FOR DEVELOPMENT AND OPERATIONAL COSTSThe final product if revised with special services, they can increase the cost of the
system.
7.ALTERNATIVES
Software Alternatives
This category consists of all software alternatives and the effect it will have on theoverall proposed system.
1. Database Management Systems
Instead of using NetBeans, other software like eclipse may be used.
7.1COMPARISONSOFALTERNATIVES
Alternative Reliability Efficiency Integrity Flexibility Maintainability Reusability
Software Alternative(DBMS)
NetBeans High High High High High Medium
Eclipse Medium High High High Low High
16
8/14/2019 Final Repor(Swapnil AMS)
17/75
8.RECOMMENDATIONSAND CONCLUSION
In today's world, we see multiple complicated systems which have multiple clientsworking together in co-ordination. These clients have many applications installed whichform a part of the system. If any of these applications face any problem, it affects thesmooth working of the entire system. Thus to avoid the error occurring in the applicationsat the clients side, we use the application monitoring Wizard which will help solve theproblems before they reach a critical state.
Vishwakarma Institute of Technology, Pune-37.
Application monitoring system
Bansilal Ramnath Agarwal CharitableTrusts
10/ 11 /2008
17
8/14/2019 Final Repor(Swapnil AMS)
18/75
Approvals Signature Block
Project Responsibility Signature Date
Project Guide (Internal)
Project Guide (External)
Documentation Leader
Department of Computer Engineering
18
8/14/2019 Final Repor(Swapnil AMS)
19/75
Table of Contents
1. CONTEXT .............. .............. .............. ............... .............. .............. .............. .............. ........... ..6
2. PROBLEM ............. .............. .............. .............. .............. ............... .............. ............ ...... ...... ...7
3. SOLUTION .............. .............. ............... .............. .............. .............. .............. .............. ............... ...... ...... .....84. BENEFITS ............. .............. .............. .............. .............. ............... .............. .............. .............. .............. .......9
5. INTRODUCTION ............................................................................................................13
5.1 PURPOSE...................................................................................................................................................... 13
5.2 METHODOLOGY............................................................................................................................................. 145.3 REFERENCES................................................................................................................................................. 14
6. GENERAL INFORMATION ............ ............... .............. .............. .............. .............. ............. ...... ...... ......14
6.1 CURRENT SYSTEMSAND PROCESSES ...............................................................................................................14
6.2 SYSTEM OBJECTIVES...................................................................................................................................... 146.3 ISSUES......................................................................................................................................................... 16
6.4 ASSUMPTIONSAND CONSTRAINTS....................................................................................................................16
7. ALTERNATIVES .............. .............. .............. .............. ............... .............. .............. .............. .............. .......16
7.1 COMPARISONSOF ALTERNATIVES ....................................................................................................................16
8. RECOMMENDATIONS AND CONCLUSION ............. .............. .............. .............. ............. ..... ..... ......17
9. OVERVIEW .............. ............... .............. .............. .............. .............. ............... .......... ..... ..21
10. GOALS AND SCOPE ............. .............. ............... .............. .............. .............. .............. .....22
10.1 PROJECT GOALS.......................................................................................................................................... 22
10.2 PROJECT SCOPE.........................................................................................................................................22
10.2.1 Included .......................................................................................................................................23
10.2.2 Excluded ......................................................................................................................................23
11. SCHEDULE AND MILESTONES ............. ............... .............. .............. .............. .............. .............. ......23
12. INTRODUCTION ..........................................................................................................28
12.1 PURPOSE.................................................................................................................................................... 28
12.2 SCOPE.......................................................................................................................................................28
12.3 DEFINITIONS, ACRONYMS, ANDABBREVIATIONS................................................................................................28
12.4 REFERENCES............................................................................................................................................... 29
12.5 OVERVIEW.................................................................................................................................................29
13. OVERALL DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....29
PROBLEM STATEMENT.........................................................................................................................................29
13.1 PRODUCT PERSPECTIVE................................................................................................................................30
PRODUCT POSITION STATEMENT............................................................................................................................ 30
13.1.1 System Interfaces ........................................................................................................................30
13.1.2 User Interfaces .......................................................................................................................... ..3013.1.3 Hardware Interfaces ....................................................................................................................31
13.2 PRODUCT FUNCTIONS................................................................................................................................... 31
13.3 ASSUMPTIONSAND DEPENDENCIES................................................................................................................. 31
14. SPECIFIC REQUIREMENTS .............. .............. .............. ............... .............. .............. .............. ........ ...31
14.1 FUNCTIONS................................................................................................................................................. 31
14.2 LOGICAL DATABASE REQUIREMENTS..............................................................................................................31
14.3 SOFTWARE SYSTEM ATTRIBUTES.................................................................................................................... 31
19
8/14/2019 Final Repor(Swapnil AMS)
20/75
14.3.1 Reliability ....................................................................................................................................31
14.3.2 Security .................................................................................................................. .....................32
14.3.3 Portability ....................................................................................................................................3214.3.4 Efficiency ....................................................................................................................................32
15. USE CASE TEMPLATE .............. .............. .............. ............... .............. .............. .............. .............. ..... ..37
USE CASE # 1 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .39
USE CASE # 2 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .40
16. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....44
16.1 SCENARIO DESCRIPTION...............................................................................................................................44
17. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....44
18. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....46
18.1 SCENARIO DESCRIPTION...............................................................................................................................47
19. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....47
20. STATE CHART DIAGRAM OVERVIEW ............. .............. ............... .............. ......... ...... ......52
20.1 STATES DESCRIPTION..................................................................................................................................52
21. CLASS DIAGRAM DESCRIPTION ............. .............. .............. ............... .............. .............. ............. ...59
21.1 CRC TEMPLATE.........................................................................................................................................59
21.2 CRC CARDS OVERVIEW.............................................................................................................................. 61
Responsibility........................................................................................................................................61
Collaborator..........................................................................................................................................62
Domain Users (3-5 people)...................................................................................................................62
OO Design Analyst (1-2 people)...........................................................................................................62
Facilitator (1 person).............................................................................................................................63Scribe (1-2 people)................................................................................................................................63
Observers (0-N people).........................................................................................................................63
The CRC Technique..............................................................................................................................64
Selecting a Scenario..............................................................................................................................64Creating Initial CRC Card(s)................................................................................................................64
Arranging the CRC Cards.....................................................................................................................65
The CRC Interview...............................................................................................................................65
Finding Classes.....................................................................................................................................65Finding Collaborators...........................................................................................................................66
21.2.1 General Guidelines .................................................................................................................. ....67
21.2.2 Class Style Guidelines ................................................................................................................68
21.2.3 Interfaces .....................................................................................................................................70
21.2.4 Relationship Guidelines ................................................................................................ ...... ...... ..71
21.2.5 Inheritance Guidelines ................................................................................................................73
21.2.6 Aggregation and Composition Guidelines .................................................................... ...... ...... ..73
21.3 CLASS DIAGRAM......................................................................................................................................... 75
20
8/14/2019 Final Repor(Swapnil AMS)
21/75
9.OVERVIEW
The motivation for this project is the need to implement an Monitoring Tool
using Thread Concept which will help the users to recognize the errors in
working of crucial application.
The customer is any user who was dealing with Complex System
The project will deliver an executable program for monitoring of controlparameter for client side another executable for administrator side to view
reports and alerts.installation guide to help user to install the program and
user guide to solve the problems of the user.
The first fully functional version will be released around 31st
Feb,
2009.Future Versions and bug fixes would be released in the future.
21
8/14/2019 Final Repor(Swapnil AMS)
22/75
The organizations involved are Vishwakarma Institute of Technology (VIT),
Cognizant Technology Solution India Pvt. Ltd.
10.GOALS AND SCOPE
10.1PROJECT GOALS
Project Goal Priority Comment/Description/Reference
Functional Goals:
1 To design and implement a component for
embedding the user application into to system with
flexibility to select parameters, .
1 To design and implement component which will
maintain database of the monitored parameters
values
2 To design a component which report to
Administrator and provide statically data and
pictorial representation.
3 To develop interactive and user friendly interfaces.
Quality Goals: 2
To provide a system that gives more flexibility toAdministrator empower for monitoring particular
system.
To create a system with minimum resource
requirement at client-side
Constraints:
The system is not supposed to take any preventing
action when problem is detected.
10.2 PROJECT SCOPE
The proposed system will deliver report to Administrator about
performance of monitoring application.
22
8/14/2019 Final Repor(Swapnil AMS)
23/75
The proposed system will not deliver correction of error.
10.2.1Included
The project will deliver an executable program for Monitoring Application
like JVM, Tomcat, Websites and another executable for server to view
reports, installation guide to help user to install the program and user
guide to solve the problems of the user.
The receivers of this project would be Vishwakarma Institute of
Technology (VIT), Cognizant Technology Solution India Pvt. Ltd.
10.2.2Excluded
This project will exclude..
Training to end users.
11.SCHEDULEAND MILESTONES
Milestones Description Milestone Criteria Planned
Date
M0 Start Project Budget Release 25-09-2008
Understand the
requirements and define
project goals and scope.
Research on the domain to
clearly identify the
requirements. Project
synopsis and SRS deliveredM1 Start Planning 17-10-2008
Objectives and strategy
defined and feasibility
studied.
Implementation language,
standards and protocols to be
followed are decided.
23
8/14/2019 Final Repor(Swapnil AMS)
24/75
Milestones Description Milestone Criteria Planned
Date
M2 Start Execution 01-12-2008
Complete project plan
defined and reusable
modules identified.
User interface libraries
defined and project plan
reviewed.
M3 Confirm Execution 20-01-2009
First version completed All basic functionalities tested
and verified.
M4 Start Introduction 30-01-2009
First version of product
ready to be delivered.
Coding of new functionality
finished,
Draft documentation
M5 Release Product 31-03-2009
Final version completed
with enhancements.
Product system tested,
documentation reviewed
M6 Close Project 10-04-2009Vishwakarma Institute of Technology, Pune-37.
Application monitoring system
Bansilal Ramnath Agarwal CharitableTrusts
10/ 18 /2008
24
8/14/2019 Final Repor(Swapnil AMS)
25/75
Approvals Signature Block
Project Responsibility Signature Date
Project Guide (Internal)
Project Guide (External)
Documentation Leader
Department of Computer Engineering
25
8/14/2019 Final Repor(Swapnil AMS)
26/75
Table of Contents
1. CONTEXT .............. .............. .............. ............... .............. .............. .............. .............. ........... ..6
2. PROBLEM ............. .............. .............. .............. .............. ............... .............. ............ ...... ...... ...7
3. SOLUTION .............. .............. ............... .............. .............. .............. .............. .............. ............... ...... ...... .....8
4. BENEFITS ............. .............. .............. .............. .............. ............... .............. .............. .............. .............. .......9
5. INTRODUCTION ............................................................................................................13
5.1 PURPOSE...................................................................................................................................................... 13
5.2 METHODOLOGY............................................................................................................................................. 14
5.3 REFERENCES................................................................................................................................................. 14
6. GENERAL INFORMATION ............ ............... .............. .............. .............. .............. ............. ...... ...... ......14
6.1 CURRENT SYSTEMSAND PROCESSES ...............................................................................................................14
6.2 SYSTEM OBJECTIVES...................................................................................................................................... 14
6.3 ISSUES......................................................................................................................................................... 16
6.4 ASSUMPTIONSAND CONSTRAINTS....................................................................................................................16
7. ALTERNATIVES .............. .............. .............. .............. ............... .............. .............. .............. .............. .......16
7.1 COMPARISONSOF ALTERNATIVES ....................................................................................................................16
8. RECOMMENDATIONS AND CONCLUSION ............. .............. .............. .............. ............. ..... ..... ......17
9. OVERVIEW .............. ............... .............. .............. .............. .............. ............... .......... ..... ..21
10. GOALS AND SCOPE ............. .............. ............... .............. .............. .............. .............. .....22
10.1 PROJECT GOALS.......................................................................................................................................... 22
10.2 PROJECT SCOPE.........................................................................................................................................2210.2.1 Included .......................................................................................................................................23
10.2.2 Excluded ......................................................................................................................................23
11. SCHEDULE AND MILESTONES ............. ............... .............. .............. .............. .............. .............. ......2312. INTRODUCTION ..........................................................................................................28
12.1 PURPOSE.................................................................................................................................................... 28
12.2 SCOPE.......................................................................................................................................................28
12.3 DEFINITIONS, ACRONYMS, ANDABBREVIATIONS................................................................................................28
12.4 REFERENCES............................................................................................................................................... 29
12.5 OVERVIEW.................................................................................................................................................29
13. OVERALL DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....29
PROBLEM STATEMENT.........................................................................................................................................29
13.1 PRODUCT PERSPECTIVE................................................................................................................................30
PRODUCT POSITION STATEMENT............................................................................................................................ 30
13.1.1 System Interfaces ........................................................................................................................30
13.1.2 User Interfaces .......................................................................................................................... ..30
13.1.3 Hardware Interfaces ....................................................................................................................31
13.2 PRODUCT FUNCTIONS................................................................................................................................... 31
13.3 ASSUMPTIONSAND DEPENDENCIES................................................................................................................. 31
14. SPECIFIC REQUIREMENTS .............. .............. .............. ............... .............. .............. .............. ........ ...31
14.1 FUNCTIONS................................................................................................................................................. 31
14.2 LOGICAL DATABASE REQUIREMENTS..............................................................................................................31
14.3 SOFTWARE SYSTEM ATTRIBUTES.................................................................................................................... 31
26
8/14/2019 Final Repor(Swapnil AMS)
27/75
14.3.1 Reliability ....................................................................................................................................31
14.3.2 Security .................................................................................................................. .....................32
14.3.3 Portability ....................................................................................................................................3214.3.4 Efficiency ....................................................................................................................................32
15. USE CASE TEMPLATE .............. .............. .............. ............... .............. .............. .............. .............. ..... ..37
USE CASE # 1 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .39
USE CASE # 2 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .40
16. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....44
16.1 SCENARIO DESCRIPTION...............................................................................................................................44
17. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....44
18. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....46
18.1 SCENARIO DESCRIPTION...............................................................................................................................47
19. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....47
20. STATE CHART DIAGRAM OVERVIEW ............. .............. ............... .............. ......... ...... ......52
20.1 STATES DESCRIPTION..................................................................................................................................52
21. CLASS DIAGRAM DESCRIPTION ............. .............. .............. ............... .............. .............. ............. ...59
21.1 CRC TEMPLATE.........................................................................................................................................59
21.2 CRC CARDS OVERVIEW.............................................................................................................................. 61
Responsibility........................................................................................................................................61
Collaborator..........................................................................................................................................62
Domain Users (3-5 people)...................................................................................................................62
OO Design Analyst (1-2 people)...........................................................................................................62
Facilitator (1 person).............................................................................................................................63Scribe (1-2 people)................................................................................................................................63
Observers (0-N people).........................................................................................................................63
The CRC Technique..............................................................................................................................64
Selecting a Scenario..............................................................................................................................64Creating Initial CRC Card(s)................................................................................................................64
Arranging the CRC Cards.....................................................................................................................65
The CRC Interview...............................................................................................................................65
Finding Classes.....................................................................................................................................65Finding Collaborators...........................................................................................................................66
21.2.1 General Guidelines .................................................................................................................. ....67
21.2.2 Class Style Guidelines ................................................................................................................68
21.2.3 Interfaces .....................................................................................................................................70
21.2.4 Relationship Guidelines ................................................................................................ ...... ...... ..71
21.2.5 Inheritance Guidelines ................................................................................................................73
21.2.6 Aggregation and Composition Guidelines .................................................................... ...... ...... ..73
21.3 CLASS DIAGRAM......................................................................................................................................... 75
27
8/14/2019 Final Repor(Swapnil AMS)
28/75
12.INTRODUCTIONThis document is the Software Requirement Specification for Application
Monitoring System. This document details out the purpose of the system beingdeveloped, its overall description and its specific requirements.
12.1PURPOSE
The purpose of this document is to collect, analyze and define high-level needsand features of the Application Monitoring. It focuses on the capabilities needed by thestakeholders, and the target users, and why these needs exist. This document will alsointroduce all the functionalities that the system can perform and its effect on the usersand the stakeholders. The intended audiences for this SRS are system developers,system analysts.
12.2SCOPE
This project mainly extends to the monitoring of system specific importantapplications to check for the occurrence of errors through use of certain controlparameters and generate reports and alerts. The monitoring process is continued to
execute multiple number of times by deciding the polling interval depending upon thecriticality of the applications. Thus we get a complete overview of the performance of the
various applications in our system after specific time intervals. Depending upon thecriticality of the applications, the monitoring can be performed at frequent intervals asrequired.
The project extends to the development of the wizard, which monitors theembedded applications and generates reports and alert messages. Also a database ismaintained, which has records of all the errors encountered till date. Applications usedfor monitoring include:
JVM Tomcat server
12.3DEFINITIONS, ACRONYMS, ANDABBREVIATIONS
Term or Acronym Definition
AMS Application Monitoring System
JVM Java Virtual Machine
28
8/14/2019 Final Repor(Swapnil AMS)
29/75
12.4REFERENCES
1. www.ibm.com
2. www.java.sun.com
3. IEEE paper on "Parameter passing for the JVM" by Gough, K. J,
Computer Science Conference, 2000, ACSC 2000, 23rd Australasian
4. "NetRexx Programming for the JVM" by Rick Hightower
12.5OVERVIEW
The document is divided into three Sections.
Section 1 introduces you to the system as a whole, its capabilities and how it isdifferent from other tools. It describes the scope of the system being developed and the
references that were needed to give a shape to this system.
Section 2 describes you to the history for the project under consideration. Itcompares the existing system with the proposed system.
Section 3 Describes the Products Perspective, the various Interfaces of the system,its functions, user characteristics, constraints, assumptions and dependencies and alsodescribes external interfaces to the system, performance requirements, designconstraints, system attributes and system specific requirements.
13.OVERALL DESCRIPTION
In complicated systems used these days, there is lot of overhead on the
administrator of the system so as to keep track of the clients. This may lead to low
performance by the administrator and may also lead to low performance by the system.
So in order to enable the administrator to perform well and to enable the correction of
minor errors at the client-side, we implement the Application Monitoring Wizard which
takes care of the client side applications and reports to
the administrator in case of any discrepancy.
PROBLEM STATEMENT
The problem ofAffects (the stakeholders affected by the problem).
The impact of which is (what is the impact of the problem).A successful solution The constant monitoring of software
29
8/14/2019 Final Repor(Swapnil AMS)
30/75
would applications to check for the occurrence of errors through use of certain controlparameters and Generate reports and alertsbefore before it becomes a serious issue.
13.1PRODUCT PERSPECTIVE
PRODUCT POSITION STATEMENT
For System AnalystsWho Involved in analyzing or marinating the client server link.
The ApplicationMonitoringSystem
is a Monitoring
That Helps businesses to ensure high availability andperformance for their business applications.
Our product Monitor the performance of various com-
ponents of an application and helps
troubleshooting production issues quickly.
This helps reduce finger pointing and poor
quality of service to end users.
Additionally with our product identifying
root cause of performance issues becomes
quicker.
Also provides you with a business centricview to monitoring IT resources. This fur-
ther helps aligning your IT resources to
the needs of the business.
13.1.1System Interfaces
Our system interacts with the system in order to retrieve the values of required
parameters under consideration.
13.1.2User Interfaces
The wizard allows for user login. Once the user gets access to the software, he can start
monitoring of the applications depending upon his choice.
30
8/14/2019 Final Repor(Swapnil AMS)
31/75
13.1.3Hardware Interfaces
User side device will be desktop PC or a Laptop having internet connection.
13.2PRODUCT FUNCTIONS
Retrieve parameter from embedded application
Compare that value with benchmark
Send alert repot to administrator and update log file
13.3ASSUMPTIONSAND DEPENDENCIES
User is having windows environment 2000 or later.
He is having Internet Connection.
Monitoring Application already install
14.SPECIFIC REQUIREMENTS
14.1FUNCTIONS
The system will perform the following functions:
Retrieve value of critical parameter of monitoring application
Compare that value with benchmark
Write into Log File
Generate Report by analyzing the Log file.
14.2LOGICAL DATABASE REQUIREMENTS
The information that needs to be maintained by the system is mainly the
performance log
The system also needs to maintain authentication information.
Frequency of use is frequent
14.3SOFTWARE SYSTEM ATTRIBUTES
14.3.1Reliability
Threading Concept is the standard mechanisms for handling multiple task which areconsidered to be highly reliable. Our system also compares the above mechanismsunder different scenarios.
31
8/14/2019 Final Repor(Swapnil AMS)
32/75
14.3.2Security
Only valid users are allowed to access the system, proper authentication
mechanisms are used for the same.
Communication is one side
14.3.3Portability
The system is designed in such a way that it will have applicability over various
domains.
The client is portable to any Windows (NT) operating system.
14.3.4Efficiency
The efficiency of the system depends on the time that is needed to process the query.The efficiency of the system depends on the rate at which the requests are served by the
server.
ID Characteristic Rank1 Correctness 1
2 Efficiency 33 Reliability 2
4 Security 4
32
8/14/2019 Final Repor(Swapnil AMS)
33/75
Vishwakarma Institute of Technology, Pune-37.
Application monitoring system
Bansilal Ramnath Agarwal CharitableTrusts
10/18/2008
Approvals Signature Block
Project Responsibility Signature Date
Project Guide (Internal)
Project Guide (External)
Documentation Leader
33
8/14/2019 Final Repor(Swapnil AMS)
34/75
Department of Computer Engineering
34
8/14/2019 Final Repor(Swapnil AMS)
35/75
Table of Contents
1. CONTEXT .............. .............. .............. ............... .............. .............. .............. .............. ........... ..6
2. PROBLEM ............. .............. .............. .............. .............. ............... .............. ............ ...... ...... ...7
3. SOLUTION .............. .............. ............... .............. .............. .............. .............. .............. ............... ...... ...... .....8
4. BENEFITS ............. .............. .............. .............. .............. ............... .............. .............. .............. .............. .......9
5. INTRODUCTION ............................................................................................................13
5.1 PURPOSE...................................................................................................................................................... 13
5.2 METHODOLOGY............................................................................................................................................. 14
5.3 REFERENCES................................................................................................................................................. 14
6. GENERAL INFORMATION ............ ............... .............. .............. .............. .............. ............. ...... ...... ......14
6.1 CURRENT SYSTEMSAND PROCESSES ...............................................................................................................14
6.2 SYSTEM OBJECTIVES...................................................................................................................................... 14
6.3 ISSUES......................................................................................................................................................... 16
6.4 ASSUMPTIONSAND CONSTRAINTS....................................................................................................................16
7. ALTERNATIVES .............. .............. .............. .............. ............... .............. .............. .............. .............. .......16
7.1 COMPARISONSOF ALTERNATIVES ....................................................................................................................16
8. RECOMMENDATIONS AND CONCLUSION ............. .............. .............. .............. ............. ..... ..... ......17
9. OVERVIEW .............. ............... .............. .............. .............. .............. ............... .......... ..... ..21
10. GOALS AND SCOPE ............. .............. ............... .............. .............. .............. .............. .....22
10.1 PROJECT GOALS.......................................................................................................................................... 22
10.2 PROJECT SCOPE.........................................................................................................................................22
10.2.1 Included .......................................................................................................................................2310.2.2 Excluded ......................................................................................................................................23
11. SCHEDULE AND MILESTONES ............. ............... .............. .............. .............. .............. .............. ......23
12. INTRODUCTION ..........................................................................................................28
12.1 PURPOSE.................................................................................................................................................... 28
12.2 SCOPE.......................................................................................................................................................28
12.3 DEFINITIONS, ACRONYMS, ANDABBREVIATIONS................................................................................................28
12.4 REFERENCES............................................................................................................................................... 29
12.5 OVERVIEW.................................................................................................................................................29
13. OVERALL DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....29
PROBLEM STATEMENT.........................................................................................................................................29
13.1 PRODUCT PERSPECTIVE................................................................................................................................30
PRODUCT POSITION STATEMENT............................................................................................................................ 30
13.1.1 System Interfaces ........................................................................................................................30
13.1.2 User Interfaces .......................................................................................................................... ..30
13.1.3 Hardware Interfaces ....................................................................................................................31
13.2 PRODUCT FUNCTIONS................................................................................................................................... 3113.3 ASSUMPTIONSAND DEPENDENCIES................................................................................................................. 31
14. SPECIFIC REQUIREMENTS .............. .............. .............. ............... .............. .............. .............. ........ ...31
14.1 FUNCTIONS................................................................................................................................................. 31
14.2 LOGICAL DATABASE REQUIREMENTS..............................................................................................................31
35
8/14/2019 Final Repor(Swapnil AMS)
36/75
14.3 SOFTWARE SYSTEM ATTRIBUTES.................................................................................................................... 31
14.3.1 Reliability ....................................................................................................................................31
14.3.2 Security .................................................................................................................. .....................3214.3.3 Portability ....................................................................................................................................32
14.3.4 Efficiency ....................................................................................................................................32
15. USE CASE TEMPLATE .............. .............. .............. ............... .............. .............. .............. .............. ..... ..37
USE CASE # 1 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .39
USE CASE # 2 .............. .............. .............. ............... .............. .............. .............. .............. ............... ........ ..... .40
16. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....44
16.1 SCENARIO DESCRIPTION...............................................................................................................................44
17. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....44
18. SEQUENCE DIAGRAM OVERVIEW .............. .............. ............... .............. .............. ....... .....46
18.1 SCENARIO DESCRIPTION...............................................................................................................................47
19. MESSAGE DESCRIPTION ............. .............. .............. .............. .............. .............. ............... ....... ..... ....47
20. STATE CHART DIAGRAM OVERVIEW ............. .............. ............... .............. ......... ...... ......52
20.1 STATES DESCRIPTION..................................................................................................................................52
21. CLASS DIAGRAM DESCRIPTION ............. .............. .............. ............... .............. .............. ............. ...59
21.1 CRC TEMPLATE.........................................................................................................................................59
21.2 CRC CARDS OVERVIEW.............................................................................................................................. 61
Responsibility........................................................................................................................................61
Collaborator..........................................................................................................................................62
Domain Users (3-5 people)...................................................................................................................62
OO Design Analyst (1-2 people)...........................................................................................................62Facilitator (1 person).............................................................................................................................63
Scribe (1-2 people)................................................................................................................................63
Observers (0-N people).........................................................................................................................63
The CRC Technique..............................................................................................................................64Selecting a Scenario..............................................................................................................................64
Creating Initial CRC Card(s)................................................................................................................64
Arranging the CRC Cards.....................................................................................................................65
The CRC Interview...............................................................................................................................65Finding Classes.....................................................................................................................................65
Finding Collaborators...........................................................................................................................66
21.2.1 General Guidelines .................................................................................................................. ....67
21.2.2 Class Style Guidelines ................................................................................................................68
21.2.3 Interfaces .....................................................................................................................................70
21.2.4 Relationship Guidelines ..........................
