Client Server Based Live Meeting

Development of a feature-rich web based Employees Communication System

1. Title of the project: Live Meeting

2. Domain: Software Industry
3. Sub Domain: Management
4. Project Architecture: N-Tire Architecture
5. SDLC methodologies: Waterfall model
6. Abstract of the project:
This project is mainly developed for the communication of Employees of
organization located at different locations. The project entitled “Live Meeting” set of
platform for the project leaders and administrator to send messages to keep constant
interaction with the programmers.

In the proposed system is the administrator can sit at his system and
communicate with the project leaders, programmers and can also maintain the login time,
logout time. He can chat about the project going on with both the programmers and project
leaders. This project also maintains offline messages. The administrator sees the IP address
of the system of project leader/programmer he is interested and chat with the people .The
project leader gives the instant report about the project to the administrator.

Through this Communication System, Whenever user logs-in into the system
then login time is recorded in the administrator’s system automatically. The administrator
can scan the present online system IP Address and send the messages to single
programmer ,set of programmers, project leader or Set of project leaders or all the
employees where he/ she is present.
This project makes the most of the tedious and mundane deskwork to minimize.
This facilitates the user to concentrate more on the project and less on the managing of
these tasks.

The software is fully integrated with CRM (Customer Relationship Management) as

well as CMS (Content Management System) solution and developed in a manner that is
easily manageable, time saving and relieving one from manual works.

The proposed system maintains…

 Frequent interaction between the administrator and the project
leaders/programmers.
 Automatically recording the login time/logout time of the user.
 Maintaining on line and offline Messages and Message View
 Employee Hierarchical

7. Functional components of the project:

 MESSAGE SENDING: In the large organization there are a set of programmers,
Project leader and Administrator. These programmers are spread through out the
organization into various groups. Project Leaders are in need to constantly interact
with the programmer’s in-groups spread over organization. It is difficult to go and pass
the message to each and ever programmer in personal
 CHATTING: When a person wants directly to communicate with the colleague, he/she
can use this service. If a person is in online that person can communicate with the
other person through the system located at different location.
 VIEW MESSAGES: This project consists of both online/offline messages. if the user is
online he can directly interact with the other user. If the user is in offline he can view
the message when he logins for the next time.
1
  EMPLOYEE HIERACHIAL: This project maintains hierarchy for the employees.

ADMINISTRATOR

PROJECT LEADER

PROGRAMMERS
 LOGIN DATE/TIME: When the user logins the system, the login time is automatically
recorded.
 LOGOUT DATE/TIME: When the user logouts the system, the logout time is
automatically recorded.
These Login and Logout time are monitored by the administrators/project leaders
depending upon the hierarchy.

8. Keywords:
 Generic Technology Keywords: Databases, User Interface, Programming
 Specific Technology Keywords: ASP.Net, C#.Net, MS SQL Server
 Project Type Keywords: Analysis, Design, Implementation, Testing
 SDLC Keywords: Presentation, Business, Data Access Layers
9. Environment:
 Servers:
a. Operating System Server: - Microsoft Windows 2000 or Higher
b. Data Base Server: Microsoft SQL Server 2000/2005
 Clients: Microsoft Internet Explorer,
 Tools: Microsoft Visual Studio .Net
 User Interface: ASP.NET with AJAX
 Code Behind: VC#.NET
10. Requirements:
 Hardware requirements:

Number Description
1 PC with 2 GB hard-disk
and 256 MB RAM

 Software requirements:

Number Description
1 Windows 2000/ XP/ or
Higher with MS-office

2. MS-SQL server2000/2005

3. Ms-Visual Studio .Net 2005

4. Ms-Internet Explorer

 Manpower requirements:
3 to 4 Developers can complete this in 3-4 months.
2
9. Milestones:
No. Milestone Milestone Description Remarks
Name

1 Requirements Complete specification of the Attempt should be made to add

Specification system including defining
hierarchies constitutes this
milestone. A document detailing
the same should be written and
a presentation on that be made.
2 Technology Understanding of the technology
familiarization needed to implement the project.
3 Database A database of at least 10 entries
creation of users with at least 1 should
application admin.
4 High-level and Listing down all possible
Detailed scenarios and then coming up
Design with flow-charts or pseudo code
to handle the scenario.
5 Development Implementation of the main
of front end screen giving the login, screen
functionalities. that follows the login giving
various options, screens for each
of the options
6 Integrating the The front-end developed in the
front-end with earlier milestone will now be able
the database to update the database. Other
features should be functional at
this stage. In short, the system
should be ready for integration
testing.
7 Integration The system should be thoroughly
Testing tested by running all the test
cases written for the system
(from milestone 5).
8 Final Review Issues found during the previous
milestone are fixed and the
system is ready for the final
review.
some more relevant functionality
other than those that are listed in
this document.
The presentation should be from
the point of view of being able to
apply it to the project, rather than
from a theoretical perspective.
It is important to finalize on the
database at this stage itself so that
development and testing can
proceed with the actual database
itself.
The scenarios should map to the
requirement specification
During this milestone period, it
would be a good idea for the team
to start working on a test-plan for
the entire system. This test-plan
can be updated as and when new
scenarios come to mind.
Another 2 weeks should be there
to handle any issues found during
testing of the system. After that,
the final demo can be arranged.
During the final review of the
project, it should be checked that
all the requirements specified
during milestone number 1 are
fulfilled

10. The following steps will be helpful to start off the project:
 Study and be comfortable with technologies such as: ASP.Net with C#, and SQL Server.
 Gather some knowledge of product hierarchies and maintenance before starting the
design.
 Create a user database with different access levels.
 Start with creating the login screen.
 Create menus for navigation and group the functionalities as sub menus.
 Create the help-pages of the application in the form of FAQ. This will helps user.