CLIENT SERVER BASED LIVE MEETING

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. 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. EXISTING SYSTEM:

Ø  The existing system is manual system. Needs to be converted into automated system. Risk of mismanagement of data. Less Security. No proper coordination between different Applications and Users. Fewer Users - Friendly. Accuracy not guaranteed. Not in reach of distant users. Communication between users through phone or manually.

Ø  The existing system users are using third party public mail services for communication. Using public domains are not supposed for employee communication.

Ø  Anonymous user can be allowed like these public domains.  It is critical to share their information like this environment. Some organizations are using manual system. In the manual system the data can be stored and transferred in the form of disk drives or paper.

Ø  Semi automated systems are connected through LAN but they are using data in local systems like Ms-Access or MS-Excel etc. In local data base there is no Option for data security and data integrity.

8. PROPOSED SYSTEM:

Ø  The development of the new system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.

Ø  User friendliness is provided in the application with various controls. The system makes the overall project management much easier and flexible. There is no risk of data mismanagement at any level while the project development is under process. It provides high level of security with different level of authentication. Users from any part of the world can make use of the system. New system will process accurate results. New system will be much better in performance as compared to existing one.

Ø  The proposed system is having frequent interaction between administrator and the project members by using email and chat modules.

9. MODULES:

·         Online Chat Module

·         Member registration Module

·         Sending and Receiving mails

·         Integrated Security Module:

·         Admin Module

10. 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.

·   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.

11. 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

12. 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

13. 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.

14.  Milestones:

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

15.  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.