Essential Communication Between End-Users For Learning Proficiency

Title of the Project: Essential Communication Between End-Users For Learning Proficiency Project Architecture : N-Tire Architecture SDLC Methodologies: Waterfall model/Spiral model
Course: Roll No: Name of the Pupil: Technology And Language: Internal Guide: E-Mail ID: Mobile No (Pupil):

MS.Net 3.5 With Visual C#.net

Abstract of the Project:

Introduction:
Essential Communication between End-Users for Learning Proficiency is a Web based application. Developing a Essential Communication between End-users for learning proficiency system to promote a greater count of Pupils to do too much into the field of Education. It integrates the benefits of a physical classroom with the convenience of a no-physical-bar virtual learning environment, minus the commuting risk and expenses.

Functional Requirements:
The educational methodology utilized for the concept of the Virtual Classroom (a classroom in an electronic space) reflects asynchronous group communications and collaborative approaches to education and training. The Pupil is an active part of a learning group but proceeds to learn and understand on an individual basis independent of the speed of other learners in the group.

Number of Pupils appearing the exam. It is a major task to provide the exams for training consultative. Employees view the results. Overall the aggregate the Pupils performance The Virtual Classroom is a teaching and learning environment located within a computer-mediated communication system To support a collaborative learning process.

The objectives of a Virtual Classroom are to improve access to advanced educational experiences by allowing Pupils and instructors to participate in remote learning communities using personal computers at home or at work. To support a collaborative learning process. By collaborative learning is meant a learning process that emphasizes group or cooperative efforts among Tutor and Pupils, active participation and

interaction on the part of both Pupils and instructors, and new knowledge that emerges from an active dialog among those who are sharing ideas and information.

Non-Functional Requirements:
24 X 7 availability Better component design to get better performance at peak time Flexible service based architecture will be highly desirable for future extension

Existing System:
Let us consider the existing system is manual and the manual system works in the following way: It integrates the benefits of a physical classroom with the convenience of a no-physical-bar virtual learning. It integrates the benefits of a physical classroom with the convenience of a no-physical-bar virtual learning environment, minus the commuting hazards and expenses. It will usher in the immense flexibility and sophistication in the existing learning platform structures, with the perfect blend of synchronous and asynchronous interaction.

It will usher in the immense flexibility and sophistication in the existing learning platform structures, with the perfect blend of synchronous and asynchronous interaction. Lack of data security. Data inconsistency. It requires lot of resources. It takes lot of time to getting records and doing manipulations

Till now most companies has adopted the above manual system that produces lot of problems and at the same time the following disadvantages are there with the above system. The increasing complexity, producing the reports as desired is not possible and protracted time-scales of modern systems in now days.

Proposed System:
To develop the new system all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.

These online exams conduct to Pupils for testing the Pupils knowledge. A manual hand written bill is provided to the corporate or individual as a proof of it. The luggage is then loaded. User friendliness (Graphical User Interface) is provided in the application. Provide Interactive interface through which a user can interact with different areas of application easily.

It can be accessed over the Internet/Intranet facilities.

It doesnt contain data inconsistency. No need for taking lot of resources.

Modules:
The modules of the system are as following:

Director Module Tutor Module Pupil Module

Director Module: Director is treated as a super user in this system. He can have all the privileges to do anything in this system. Director can prepare course curriculum, along with course content by the help of the faculties. He can collect the course videos and stored into in the centralized database. Tutor: Faculties can take lectures, uploads assignments, announcements, evaluate answer sheets and also upload lectures, and other discussions in various formats as in the form of videos and power point presentations. Pupil: Pupils can choose courses, attend lectures, take exams, and view their attendance records, progress reports as per their convenience through this system only. One Pupil can register multiple courses. Take their classes on the schedule time or later their convenience. By using the system interface Pupil learn the courses properly and attend the exams as an online mode. Results will be announced through online only.

Users of the System:

This system should be designed to support the following users: Director Tutor Pupil Normal users

Environment:
Servers: IIS Operating System Server: - Microsoft Windows XP/2000 or Higher Data Base Server: Microsoft SQL Server 2005/2008 Clients: Microsoft Internet Explorer (Client Browser)

Development Tools: Microsoft Visual Studio .Net 2008/2010 Documentation Tools: MS Office 2007/2010 Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007 User Interface: ASP.NET With AJAX Code Behind: C#.NET

Requirements: Hardware Requirements:

Number 1 Description PC With Minimum 20 GB Hard-Disk And 1GB RAM

Software Requirements:
Number 1 2. 3. 4. Description Windows XP/2000 Or Higher With MS-Office 2007/2010 MS-SQL Server 2005/2008 Ms-Visual Studio .Net 2008/2010 MS-Internet Explorer

Milestones:
No. Milestone Name Requirements Specification Milestone Description Remarks

Technology Familiarization

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. Understanding of the technology needed to implement the project.

Attempt should be made to add some more relevant functionality other than those that are listed in this document.

Database Creation

A database of at least 10 entries of users with at least 1 should application Director.

High-level Detailed Design

and

Development of Front End Functionalities.

Listing down all possible scenarios and then coming up with flow-charts or pseudo code to handle the scenario. Implementation of the main screen giving the login, screen that follows the login giving various options, screens for each

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

of the options 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. The system should be thoroughly tested by running all the test cases written for the system (from milestone 5). Issues found during the previous milestone are fixed and the system is ready for the final review.

can be updated as and when new scenarios come to mind.

Integration Testing

Final Review

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

The following steps will be helpful to start of 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.