Online Learning Portal

Online Learning Portal (Project Report)

SUBMITTED BY : Amit Raghav

ENROLMENT NO. : 520757439 UNDER THE GUIDANCE OF :

SIKKIM MANIPAL UNIVERSITY

INDEX

The Project Report Contains the Following Details 1. Introduction ………………………………………………………………. 2. Objectives

……………………………………………………………….

3. Feasibility Study …...……………………………………………………... • Technical Feasibility • Economical Feasibility • Operational Feasibility 4. System Analysis ………………………………………………………….. 5. Software Engineering Paradigm………………………………………….. 6. Software Requirement Specifications ……………………………………. 7. Project Planning…...……………………………………………………… 8. Introduction of ASP.NET…………………………………………………. 9. Introduction of Sql Server………………………………………………..

10.Gantt chart……...…………………………………………………………. 11.E-R Diagram……………………………………………………………… 12.Context free diagram ……………………………………………………... 13.Data Flow Diagram …………………………………………..................... 14.Data Base Table Used ……………………………………………………. 15.Screenshot………………………………………………………………… 16.Testing…………………………………………………………………….. 17.Implementation…………………………………………………………… 18.Maintenance ……………………………………………………………… 19.Coding…………………………………………………………………….. 20.Future application of the project …………………………………………. 21.Bibliography ……………………………………………………………… 22. Web References .…………………………………………………………

INTRODUCTION

Problem Defination Basic problem in manual system integration of two head of admin viz and user. Lot of time was wasted in paper work for above blocks of. Why This..? The scope of logics and integration of different modules were the main source of inspiration to work on this particular problem.

“ONLINE LEARNING PORTAL” is the process of the managing and controlling the activities of a school. It includes maintaining and managing the records of students & teachers available in the school. It also maintains the list of events, articles, announcement held in the school. It has been designed to make available information as and when required. Also, it is highly beneficial to both administrator as well as students and teachers involved in the school.

OBJECTIVE OF THE PROJECT The main objectives of using Relational Database Management System are as follows: -

1.

CONTROL REDUNDANCY : The System

should identify existence of common data and avoid duplicate recording relationships of pointers should be used to locate data which are used many times selective redundancy

is

sometimes

allowed

to

improve

performance or far better reliability.

2.

DATA INTEGRITY

:

Consistency of data

values and relationships must be preserved in order to achieve this the system must ensure validity of data by using

good

editing,

synchronize

updating

and

propagating changes to other related data element it also involves maintaining audit trails to enable recovery if errors are deleted.

3.

DATA SECURITY : This is concerned with

protecting access to data protection is needed at many levels for access, modification, deletion or display access restriction may be for individual data items or group of items.

4.

DATABASE PERFORMANCE : The system

should be able to provide timely information as required. The cost of storing and retrieving the data should be commensurate with the value of information provided.

5.

MANAGEMENT

CONTROL

:

As

the

dependence of an organization on a data base increases positive management controls should be exercised over addition, deletion, changes and disposition of data must be protected to start legal accounting and auditing requirements.

Main Objectives are :

Provide an innovative, cost efficient and effective recruitment system.



Increase the quality and quantity of applicants applying for vacancies.



Offer immediate cost savings on recruitment with substantial long term saving over a prolong period.



Dramatically reduce paper work and administrative work.



Streamline the recruitment process and reduce the corporate overall recruitment cycle.

FEASIBILITY STUDY A feasibility study is carried out to select the best system that meets performance requirements. Feasibility is the determination of whether or not a project is worth doing. The process followed in making this determination is called a feasibility study. This type of study determines if a project can and should be taken. Since the feasibility study may lead to the commitment of large resources, it becomes necessary that it should be conducted competently and that no fundamental errors of judgment are made. Depending on the results of the initial investigation, the survey is expanded to a more detailed feasibility study. Feasibility study is a test of system proposal according to its workability, impact on the organization, ability to

meet user needs, and effective use of

resources. The objective of the feasibility study is not to solve the problem but to acquire a sense of its scope . During the study, the problem definition is crystallized and aspects of the problem to be included in the system are determined. Consequently, costs and benefits are described with greater accuracy at this stage. It consists of the following:

1. Statement of the problem: A carefully worded statement of the problem that led to analysis. 2. Summary of finding and recommendations: A list of the major findings and recommendations of the study. It is ideal for the user who requires quick access to the results of

the analysis

of

the

system under study. Conclusion are stated , followed by a list of the recommendation and a justification for them . 3. Details of findings : An outline of the methods and

procedures

under-taken by the existing system, followed by coverage of the objectives and procedures of the candidate system. Included are also discussions of output reports, file structures, and costs and benefits of the candidate system. 4. Recommendations

and

conclusions: Specific

recommendations

regarding the candidate system, including personnel assignments, costs, project schedules, and target dates. Three key considerations are involved in the feasibility analysis these are 1.

Economic Feasibility

2.

Technical Feasibility

3.

Behavioral Feasibility

Economic Feasibility:

Economic analysis is the most frequently used method for evaluating the effectiveness of a system. More commonly known as cost/ benefit analysis, the procedure is to determine the benefits and savings that are expected from a system and compare them with cost. Earlier in Compu Craft the work has been done manually which takes lot of time as well as man power which is more economical. Now the same work is computerized which is more effective and efficient, less time consuming, reduces man power which in turn proves to be less economical. Technical Feasibility: Technical Feasibility centers around the existing computer system (hardware/ software) and also it can support the modification. In manual processing there are more chance of errors are there, creating lot of complications, less technical or logical. Through proposed system we can set this process in a very systematic pattern, which is more technical, full proof, authentic, safe and reliable. Behavior Feasibility: Our proposed system works to minimize the human errors, take less time, easy interaction with user, bug free. This project/software is further expanded by connecting various interrelated departments and by installing an extension part of this software.

•

System level goals and requirements.

•

Cost estimation for development process and

work product. •

Solution strategy development.

•

Outlines of the several solutions strategies.

•

Recommendation of solutions strategy.

•

Feasibility and study of each strategy.

•

List of priorities for management.

System Level Goals •

Data security.

•

The application should be error free.

•

Data integrity should be maintained.

•

Certain data control methods should be tracked.

•

Easy understanding of the working of the

Institution. Cost estimation for development process and work Cost driver factors of the project depends upon the product attributes, computer and the project. The effort adjustment factor id calculated depending upon these attributes. •

Solution strategy development.

•

Outline of several solution strategy.

•

Feasibility and studies of each strategy.

•

Recommendation of a solution strategy.

•

List of priorities for product characteristics.

ANALYSIS

System Analysis The analysis model must achieve three primary objectives:1.

To describe the requirements of the customer.

2.

To establish a basis for the creation of a software

design. 3.

To define a set of requirements that can be

validated once software is built. An Overview to system analysis The system analysis phase is considered to be one of the most important phases in the system development life cycle. It is immensely important that the software developer make through study of the existing system. Thorough study of the system is made and need i.e. features that are critical to system success and users wants (i.e. features that would be good but not essential) are brought out. The study will enable the developer to know the intricacies of the existing system. Requirement analysis is done in order to understand the problem which the S/W system is to solve e.g., the problem could be automating the existing manual system or developing a completely new automated system or a combination of the two. For large systems having a large number of features and the need to perform many different tasks, understanding the requirement of the system is a major task. The emphasis in requirement analysis is on identifying what is needed from the system, and not how the system achieves its goal.

The main objective behind any business organization is to maximize its profit besides maintaining quality and strategic norms.

This can be

achieved by improving the efficiency of the system by providing more facilities using automation, by adopting faster data access, proper communication. Since Computer Craft

is an educational institute, whereas its main

objective behind automation is not only to maximize profit but also to take care of students’ interest by providing coaching of latest courses benefiting students, in turn the country. The most important objective behind automation is to minimize Paper Work. Paper Work/Registers are replaced by a Centralized Data Bank, which is well equipped to store / provide information as and when required. Data Bank also helps speed up the communication between various depts. / outside agencies, as there is no need of making request against different departments for a specific data and to wait for it for a long period. This also improves the efficiency as it saves time and human resources. By making the manual system computerized, we can ensure complete utilization of our existing resources. Automation helps in generating the reports / information in a consistent way, which saves time and labour if done manually. NEED OF COMPUTERIZATION

In the area of information technology, it is need of hour to have a fast information processing system capable of providing processed data at right time and to right person which appropriately justified by the following limitation of manual system: •

Delay in information search and retrieval

•

Problem in updation of current information and maintaining proper

backup of information •

Possible damage of paper carrying the information thereby chance

of loosing valuable information. •

Much time required in giving correct information

•

Less reliability and maintainability of data

•

Secrecy of information may not be maintained due to visible facts

on paper. IMPORTANCE OF COMPUTERIZATION After computerization of the system, it will be helpful for giving correct information in a short period of time. This will provide: •

Easy storage and retrieval of data

•

Giving correct information with less effort and high accuracy

•

Secrecy and less chance of change of loss of data

•

Easy data updating facility

•

Data integrity and inconsistency Requirement Collection and Analysis

Most information regarding identification of user group and application areas, the operating environment, the processing requirements have been obtained during the system analysis phase through on-site observations and interviews. Preliminary Investigation:

The first step in the system development lifecycle is the preliminary investigation to determine the feasibility of the system .when the request is made; the first step is the preliminary investigation begins. This activity has three parts:1) Request clarification :- The client is a marketing based company . The tele-marketing persons contact to their client via telephone and confirm the appointment. They send these details to their head. Head after that allots that project to their Marketing Executives. They have to keep the record of their client, their payment details, share of each tele-marketing person for every confirm appointment and confirm order. Different Modules In Computerised System Module 1: Admin Password Module In this module, Admin enters a password and the software checks its validity. If the password is valid then he is allowed to enter, otherwise “Invalid User/Password” message is displayed.

Module 2: Student Password Module In this module, User enters a password and the software checks its validity. If the password is valid then he is allowed to enter, otherwise “Invalid User/Password” message is displayed. Different data access rights are assigned to different users. Module 3: New Student Module In this module, whenever a new Student is required to be added the corresponding forms are opened and the information of the new student will be entered into the database. His unique ID and Password is created so that he can use that ID and password to add discussion forum or use course material Module 3: New Teacher Module In this module, whenever a new Teacher is required to be added the corresponding forms are opened and the information of the new student will be entered into the database. His unique ID and Password is created so that he can use that ID and password to add discussion forum or use course material. Module 4: Activate Discussion Topic Module. In this module the Discussion Topic is activated by the administrator, so that he can use that ID and password to make orders through his computer allotted in his room. Until the administrator activate the Discussion Topic will not able to see to the guest/teachers/students.

Module 5: Add Announcement Module In this module, admin adds new announcement (related to studies) to be viewed on websites by all users/guests. Module 6: Add Album Module In this module, admin adds new albums to be viewed on websites by all users/guests. Module 7: Add Article Module In this module, admin adds new article to be viewed on websites by all users/guests. Module 8: Add Image Module In this module, admin adds new images in the specific albums to be viewed on websites by all users/guests. Module 9: Add Events Module In this module, admin adds new events to be viewed on websites by all users/guests. Module 10: Add Course Material Module In this module, admin adds new course material to be viewed / downloaded on websites by all teachers/students.

Module 11: Edit Announcement Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 12: Edit Events Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 13: Edit Articles Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 14: Edit Album Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.

Module 15: Edit Image Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 16: Edit Student Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 17: Edit Teacher Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.

SOFTWARE ENGINEERING PARADIGM APPLIED

Software Engineering Paradigm The basic objective of software engineering is to: develop methods and procedures for software development that can scale up for large systems and that can be used to consistently produce high quality software at low cost and with a small cycle time. That is, the key objectives are consistency, low cost, high quality, small cycle time, and scalability. The basic approach that software engineering takes is to separate the development process from the software. The premise is that the development process controls the quality, scalability, consistency, and productivity. Hence to satisfy the objectives, one must focus on the development process. Design of proper development process and their control is the primary goal of the software engineering. It is this focus on the process that distinguishes it from most other computing disciplines. Most other computing disciplines focus on some type of the product-algorithms, operating systems, databases etc. while software engineering focuses on the process for producing products.

To better manage the development process and to achieve consistency, it is essential that the software development be done in phases.

Different Phases Of The Development Process: 1) Requirement Analysis: Requirement analysis is done in order to understand the problem the software system is to solve. The problem could be automating an existing manual process, developing a new automated system, or a combination of the two. The emphasis in requirements analysis is on identifying what is needed from the system, not how the system will achieve its goals. There are atleast two parties involved in the software development-a client and a developer. The developer has to develop the system to satisfy the client’s needs. The developer does not understand the client’s problem domain, and the client does not understand the issues involved in the software systems. This causes a communication gap, which has to be adequately bridged during requirements analysis. 2) Software Design: The purpose of the design phase is to plan a solution of the problem specified by the requirements documents. This phase is the first step in moving from the problem domain to the solution domain. Starting with what is needed, design takes us toward how to satisfy the needs. The design of a system is perhaps the most critical factor affecting the quality of the software. It has a major impact on the later phases, particularly testing and maintenance.

The design activity is divided into two phases: System Design and Detailed Design. In system design the focus is on identifying the modules, whereas during detailed design the focus is on designing the logic for each of the modules. 3) Coding: The goal of the coding phase is to translate the design of the system into code in a given programming language. Hence during coding, the focus should be on developing programs that are easy to read and understand, and not simply on developing programs that are easy to write. 4) Testing: Testing is the major quality control measure used during software development. Its basic function is to detect errors in the software. Testing not only uncover errors introduced during coding, but also errors introduced during the previous phases. Thus, the goal of the testing is to uncover requirement, design and coding errors in the programs. Therefore, different levels of testing are used. Testing is an extremely critical and time consuming activity. It requires proper planning of the overall testing process. The output of the testing phase is the test report and the error report. Test report contains the set of test cases and the result of executing the code with these test cases. The error report describes the errors encountered and the action taken to remove the errors.

5) Operation & maintenance phase Software maintenance is a task that every development group has to face, when the software is delivered to the customer ‘s site, installedand is operational. Software maintenance isa very broad activity that includes error correction, enhancement of capabilities, deletion of obsolete capabilities and optimization.

SOFTWARE

REQUIREMENT

SPECIFICATION

Software Requirement Specifications If a document that completely describes what the proposed software should do without describing how the software will do it, The basic goal of requirements specific to produce the requirements, which describes the complete external behavior of the proposed software. However, producing the report is said to be done. The basic limitation is that the user’s need keep on changing as the environment in which system was to function changes with time. This happens more in complex application where all the needs may not be known to any set of people during the requirement phase. Types of error in this specifications can clearly be avoided or at least considerably, by properly performing the requirement phase. As many times a developer or administrator does not know what a user and the supplier on what the software product will do. This is the only document which tells the time agreement and procedure of complete project as well as what a user wants. There are some steps which are considered in the SOFTWARE REQUIREMENT SPECIFICATION such as •

Introduction Description

•

Information Description

•

Function Description

•

Behavioral Description

•

Validation checks and criteria

•

Bibliography

•

Appendix

INTRODUCTION The introduction states the goals and objectives of the software describing it in the context of the computer -based system. Actually the introduction may be nothing more than the software people of the planning document.

INFORMATION Online Recruitment System is to replace manual operations of recruitment of an IT company. As recruitment is a round the year activity involving thousands of candidates a need has been felt to automate the entire operations. Applications are collected in a prescribed format and checked for eligibility. All the eligible candidates are sent an automated message (just like Admit Card) for the selection test. The results are compiled and presented to management to decide on cut-offs for interview. Based on the selection criteria decided by the management, the qualified candidates are called for the interview. FUNCTIONAL DESCRIPTION The project also provides the facility to contact the registered user easily without any admin interaction. If you find an existing entry meeting your requirement, then you can contact the concerned party directly.

If there is no entry, which meets your requirement, you can register your details on the site, so that others can find you. The project improves the efficiency and effectiveness of the whole system. BEHAVIORAL DESCRIPTION IT Examine the operations of the software as a consequence of external events and internally generated control characteristics. Here the Admin checks the classified entered by the registered users. Admin is the only person who can activate or deactivate the classified entered by the registered users.

PROJECT PLANNING I was assigned the duty for developing a computerized system known as “Property Classified”. Working in team reinstates the team for some common guidelines and standard to be followed by all the team members across all team. For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things:  Topic Understanding.  Modular Break –Up Of The System.  Processor Logic For Each Module.

 Database Requirements.

Topic Understanding: It is vital that the field of application as introduced in the project may be totally a new field. I carefully went through the project to identify the requirements of the project. Modular Break –Up Of The System:  Identify The Various Modules In The System.  List Them In The Right Hierarchy.  Identify Their Priority Of Development.

Description Of The Modules: Module 1: Admin Password Module In this module, Admin enters a password and the software checks its validity. If the password is valid then he is allowed to enter, otherwise “Invalid User/Password” message is displayed.

Module 2: Student Password Module In this module, User enters a password and the software checks its validity. If the password is valid then he is allowed to enter, otherwise “Invalid User/Password” message is displayed. Different data access rights are assigned to different users. Module 3: New Student Module In this module, whenever a new Student is required to be added the corresponding forms are opened and the information of the new student will be entered into the database. His unique ID and Password is created so that he can use that ID and password to add discussion forum or use course material Module 3: New Teacher Module In this module, whenever a new Teacher is required to be added the corresponding forms are opened and the information of the new student will be entered into the database. His unique ID and Password is created so that he can use that ID and password to add discussion forum or use course material. Module 4: Activate Discussion Topic Module. In this module the Discussion Topic is activated by the administrator, so that he can use that ID and password to make orders through his computer allotted in his room. Until the administrator

activate

the

Discussion

Topic

will

not

able

to

see

to

the

guest/teachers/students. Module 5: Add Announcement Module

In this module, admin adds new announcement (related to studies) to be viewed on websites by all users/guests. Module 6: Add Album Module In this module, admin adds new albums to be viewed on websites by all users/guests.

Module 7: Add Article Module In this module, admin adds new article to be viewed on websites by all users/guests. Module 8: Add Image Module In this module, admin adds new images in the specific albums to be viewed on websites by all users/guests. Module 9: Add Events Module In this module, admin adds new events to be viewed on websites by all users/guests. Module 10: Add Course Material Module In this module, admin adds new course material to be viewed / downloaded on websites by all teachers/students. Module 11: Edit Announcement Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 12: Edit Events Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the

data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 13: Edit Articles Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 14: Edit Album Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 15: Edit Image Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.

Module 16: Edit Student Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. Module 17: Edit Teacher Module In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry.

Database Requirements:  Identify The Various Tables Required.  Fields For These Tables.  The Various Key Fields (for example Primary key and Foreign key).  Identify The Various Constraints like Not Null, Unique etc. The Database here used is Ms-SQL. The database tables are shown in DATABASE DESIGN. The list of tables are:List of Tables: • • • • • • • • • • • • • • • •

Album Announcement Article Event Image Login Material Poll Ppt Research Story Student Teacher Topic Views Vote

Software/Compilers Required To Develop This System: Operating System

:

Windows XP / 2000

Front-End Tool

:

ASP.NET 2005/2008

Back-End

:

Ms – Sql Server 2000/2005

Hardware Required To Develop This System: Processor: Any Pentium IV or Equivalent Machine RAM: 512 MB HDD: 80 GB FDD: 1.44 MB CD-ROM: 52X 17 inches Color Monitor 104 Keys Keyboards

Printer: DeskJet 670 C INTRODUCTION OF ASP.NET ASP.NET is not just a simple upgrade or the latest version of ASP. ASP.NET

combines

unprecedented

developer

productivity

with

performance, reliability, and deployment. ASP.NET redesigns the whole process. It's still easy to grasp for new comers but it provides many new ways of managing projects. Below are the features of ASP.NET.

ASP.NET Features

Easy Programming Model ASP.NET makes building real world Web applications dramatically easier. ASP.NET

server

controls

enable

an

HTML-like style of declarative programming that let you build great pages with far less code than with classic ASP. Displaying data, validating user input, and uploading files are all amazingly easy. Best of all, ASP.NET pages work in all browsers including Netscape, Opera, AOL, and Internet Explorer. Flexible Language Options ASP.NET lets you leverage your current programming language skills. Unlike classic ASP, which supports only interpreted VBScript and JScript, ASP.NET now supports more than 25 .NET languages (built-in support for VB.NET, C#, and JScript.NET), giving you unprecedented flexibility in your choice of language.

Great Tool Support You can harness the full power of ASP.NET using any text editor, even Notepad. But Visual Studio .NET adds the productivity of Visual Basicstyle development to the Web. Now you can visually design ASP.NET Web Forms using familiar drag-drop-doubleclick techniques, and enjoy fullfledged code support including statement completion and color-coding. VS.NET also provides integrated support for debugging and deploying ASP.NET Web applications. The Enterprise versions of Visual Studio .NET deliver life-cycle features to help organizations plan, analyze, design, build, test, and coordinate teams that develop ASP.NET Web applications. These include UML class modeling, database modeling (conceptual, logical, and physical models), testing tools (functional, performance and scalability), and enterprise frameworks and templates, all available within the integrated Visual Studio .NET environment.

Rich Class Framework Application features that used to be hard to implement, or required a 3rdparty component, can now be added in just a few lines of code using the .NET Framework. The .NET Framework offers over 4500 classes that encapsulate rich functionality like XML, data access, file upload, regular expressions, image generation, performance monitoring and logging, transactions, message queuing, SMTP mail, and much more. With Improved Performance and Scalability ASP.NET lets you use serve more users with the same hardware.

Compiled execution ASP.NET is much faster than classic ASP, while preserving the "just hit save" update model of ASP. However, no explicit compile step is required. ASP.NET will automatically detect any changes, dynamically compile the files if needed, and store the compiled results to reuse for subsequent requests. Dynamic compilation ensures that your application is always up to date, and compiled execution makes it fast. Most applications migrated from classic ASP see a 3x to 5x increase in pages served.

Rich output caching ASP.NET output caching can dramatically improve the performance and scalability of your application. When output caching is enabled on a page, ASP.NET executes the page just once, and saves the result in memory in addition to sending it to the user. When another user requests the same page, ASP.NET serves the cached result from memory without re-executing the page. Output caching is configurable, and can be used to cache individual regions or an entire page. Output caching can dramatically improve the performance of data-driven pages by eliminating the need to query the database on every request.

Web-Farm Session State ASP.NET session state lets you share session data user-specific state values across all machines in your Web farm. Now a user can hit different servers in the Web farm over multiple requests and still have full access to her

session. And since business components created with the .NET Framework are free-threaded, you no longer need to worry about thread affinity.

Enhanced Reliability ASP.NET ensures that your application is always available to your users.

Memory Leak, DeadLock and Crash Protection ASP.NET automatically detects and recovers from errors like deadlocks and memory leaks to ensure your application is always available to your users. For example, say that your application has a small memory leak, and that after a week the leak has tied up a significant percentage of your server's virtual memory. ASP.NET will detect this condition, automatically start up another copy of the ASP.NET worker process, and direct all new requests to the new process. Once the old process has finished processing its pending requests,

it

is

gracefully

released. Automatically,

disposed

without

and

the

administrator

leaked

memory

intervention

or

is any

interruption of service, ASP.NET has recovered from the error.

Easy Deployment ASP.NET takes the pain out of deploying server applications. "No touch" application deployment. ASP.NET dramatically simplifies installation of your application. With ASP.NET, you can deploy an entire application as easily as an HTML page, just copy it to the server. No need to run regsvr32 to register any components, and configuration settings are stored in an XML file within the application.

Dynamic update of running application ASP.NET now lets you update compiled components without restarting the web server. In the past with classic COM components, the developer would have to restart the web server each time he deployed an update. With ASP.NET,

you

simply

copy

the

component

over

the

existing

DLL, ASP.NET will automatically detect the change and start using the new code.

Easy Migration Path You don't have to migrate your existing applications to start using ASP.NET. ASP.NET runs on IIS side-by-side with classic ASP on Windows 2000 and Windows XP platforms. Your existing ASP applications continue to be processed by ASP.DLL, while new ASP.NET pages are processed by the new ASP.NET engine. You can migrate application by application, or single pages. And ASP.NET even lets you continue to use your existing classic COM business components.

XML Web Services XML Web services allow applications to communicate and share data over the

Internet,

regardless

of

operating

system

or

programming

language. ASP.NET makes exposing and calling XML Web Services simple. Any class can be converted into an XML Web Service with just a few lines of code, and can be called by any SOAP client. Likewise, ASP.NET makes it incredibly easy to call XML Web Services from your

application. No knowledge of networking, XML, or SOAP is required. Mobile Web Device Support ASP.NET Mobile Controls let you easily target cell phones, PDAs and over 80 mobile Web devices. You write your application just once, and the mobile controls automatically generate WAP/WML, HTML, or iMode as required by the requesting device.

INTRODUCTION OF SQL SERVER

Microsoft SQL Server is a Relational Database Management System (RDBMS) designed to run on platforms ranging from laptops to large multiprocessor servers. SQL Server is commonly used as the backend system for websites and corporate CRMs and can support thousands of concurrent users. SQL Server comes with a number of tools to help you with your database administration and programming tasks. SQL Server is much more robust and scalable than a desktop database management system such as Microsoft Access. Anyone who has ever tried using Access as a backend to a website will probably be familiar with the errors that were generated when too many users tried to access the database! Although SQL Server can also be run as a desktop database system, it is most commonly used as a server database system.

Server Database Systems Server based database systems are designed to run on a central server, so that multiple users can access the same data simultaneously. The users normally access the database through an application.

For example, a website could store all its content in a database. Whenever a visitor views an article, they are retrieving data from the database. As you know, websites aren't normally limited to just one user. So, at any given

moment, a website could be serving up hundreds, or even thousands of articles to its website visitors. At the same time, other users could be updating their personal profile in the members' area, or subscribing to a newsletter, or anything else that website users do.

Generally, it's the application that provides the functionality to these visitors. It is the database that stores the data and makes it available. Having said that, SQL Server does include some useful features that can assist the application in providing its functionality.

DESIGN Gantt chart E-R diagram Data Flow Diagram (DFD) DataBase Design

GANTT CHART

Gantt Chart Gantt Chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by coloring each milestone when completed. The project will start in the month of August and end after 4 months at the end of April.

Analysis Feasibility Analysis Design Development Implementation

DATABASE DESIGN

Maintenance

Introduction to data dictionary: Data dictionaries are an integral component of structured analysis, since data flow diagrams by themselves do not fully describe the subject of the investigation. The data flow diagrams provide the additional details about the project/system.

Data Dictionary (Definition):

A data dictionary is a catalog- a repository- of the elements in a system. These elements center on the data and the way they are structured to meet user requirements and organization needs. A data dictionary consists of a list of all the elements composing the data flowing through a system. The major elements are data flows, data stores, and processes. The data dictionary stores details and descriptions of these elements.

Describing Data Elements: Each entry in the data dictionary consists of a set of details describing the data used or produced in the system. Each item is identified by a data name, description, alias, and length and has specific values that are permissible for it in the system being studied.

List of Tables: Table Structure •

• • • • • • • • • • • • • • •

Album Announcement Article Event Image Login Material Poll Ppt Research Story Student Teacher Topic Views Vote

Table 1: Album

Field Name

Data Type

al_id

Number

al_name al_dttm

Nvarchar Nvarchar

Table 2: Announcement

Field Name

Data Type

Ann_id

Number

Ann_head Ann_dttm Ann_des

Nvarchar Nvarchar Nvarchar

Table 3: Article

Field Name

Data Type

Art_id

Number

Art_head Art_dttm Art_des

Nvarchar Nvarchar Nvarchar

Table 4: Event

Field Name

Data Type

Ev_id

Number

Ev_head Ev_dttm Ev_des

Nvarchar Nvarchar Nvarchar

Table 5: Image

Field Name

Data Type

Img_id

Number

img_name img_alname img_orgname

Nvarchar Nvarchar Nvarchar

Table 6: login

Field Name

Data Type

U_name

Nvarchar

U_pass U_type

Nvarchar Nvarchar

Table 7: Material

Field Name

Data Type

Mat_id

Number

mat_orgname Mat_subject mat_des Mat_dttm

Nvarchar Nvarchar Nvarchar Nvarchar

Mat_fname

Nvarchar

Table 8: Poll

Field Name

Data Type

Pol_id

Number

pol_ques pol_dttm

Nvarchar Nvarchar

Table 9: PPT

Field Name

Data Type

Ppt_id

Number

ppt_fname ppt_des Ppt_orgname Ppt_dttm

Nvarchar Nvarchar Nvarchar Nvarchar

Table 10: Image

Field Name

Data Type

Res_id

Number

Res_name Res_des Res_link1 Res_link2 Res_link3 Res_link4

Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar

Table 11: Story

Field Name

Data Type

story_id

Number

story_head story _dttm story _des

Nvarchar Nvarchar Nvarchar

Table 12: Student

Field Name

Data Type

St_id

Number

st_name st_fname st_add st_cno st_qual st_pass st_dttm

Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar

Table 13: Teacher

Field Name

Data Type

t_id

Number

t_name t_fname t_add t_cno t_qual t_pass t_dttm

Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar

Table 14: Topic

Field Name

Data Type

Top_id

Number

Top_des Top_subbyid Top_dttm Top_act Top_subbyname Top_subbytype

Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar Nvarchar

Table 15: Views

Field Name

Data Type

views_id

Number

views _des views _topid views _dttm Views_subby

Nvarchar Nvarchar Nvarchar Nvarchar

Table 16: Vote

Field Name

Data Type

Vote_id

Number

Vote_decision Vote_polid Vote_dttm

Nvarchar Nvarchar Nvarchar

E-R DIAGRAM Online Learning Portal

New user

Admin User uname

H as nam e

address

Admin Creates new

upass

Teacher/Student

mobil e

utype

homephon e Top_des

Top_subby

Top_id creates new

Top_ac t No

Activa te Yes

Add views

Check s

Discussion Topic

Discussion Topic

Top_dttm

DATA FLOW DIAGRAM (DFD) Definition of Analysis and Design:

Analysis and design refers to the process of examining a business situation with the intent of improving it through better procedures and methods. Overview of Analysis and Design:

System development can generally be thought of as having two major components - analysis and design. Introduction of User: The term user is widely used in the system analysis and design. The term end-user is widely used by the analysts to refer to people who are not professional information systems specialists but who can use computers to perform their Jobs. We can group end-user into four categories. Hands-on Users actually interact with the system. They feed in data or receive output, perhaps using a terminal. Indirect Users benefit from the results or reports produced by these systems but do not directly interact with the hardware or software. These users may be managers of business functions using the system.

End-Users are not alike. Some are intermittent users. The end-user can also be a competitor, not an employee of the firm. User managers have management responsibilities for application systems.

Definition of System: In the broad sense, a system is simply a set of components that interact to accomplish some purpose. Systems are all around us. As computers are used more and more by persons who are not computer professionals , the face of systems development is taking on an additional dimension. Users themselves are undertaking development of some of the systems they use , as the executive in the vignette emphasized. These different situations are represented by three distinct approaches to the development of computer information systems:  Systems Development Life Cycle.  Structured Analysis Development Method.  Systems Prototype Method. Systems Development Life Cycle:

Systems development, a process consisting of two major steps of systems analysis and design, starts when management or sometimes

systems development personnel realize that a particular business system needs improvement. SDLC is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. Different parts of the project can be in various phases at the same time, with some components undergoing analysis while others advanced stages. SDLC consists of following activities:

 Preliminary investigation.  Determination of system requirements.  Design of system.  Development of software.  System testing.  Implementation and evaluation.

Two main steps of development are:

 Analysis  Design

ANALYSIS:

Objectives: System analysis is conducted with the following objectives in mind:

 Identify the user’s need.  Evaluate the system concept for feasibility.  Perform economic and technical analysis.  Allocate functions to hardware, software, people, database, and other system elements.  Establish cost and schedule constraints.  Create a system definition that forms the foundation for all subsequent engineering work. Both hardware and software expertise are required to successfully attain the objectives listed above.

DFD (Data Flow Diagram) DFD (Data Flow Diagram)

DFD shows the entire system under Investigation.

Student Registration

User

Student

Student Detail TEacher

Teacher Registration

Login Details

Teacher details

Login Details

User

Online Learning Portal Activate / Deactivate

Discussion Topic activate/deactivate Listing Discussion Topic Activate/Delete Listing

Activate/Delete Discussion Topic

CODE EFFICIENCY

CODE EFFICIENCY For Code efficiency, the following conditions must be fulfilled: 1) Option Explicit: All variables must be declared with proper data type. Option Explicit keyword must be used, it forces each variable or expression in an application to be defined with a specific data type through the use of the Dim, Private, Public, Redim or Static keywords. If Option Explicit is not used, undefined variables are automatically defined as Variant. Variant data type must be avoided because it takes 16 bytes of memory. 2) Early Binding Vs Late Binding: Early binding is faster than Late Binding because the application doesn’t have to interrogate the object at runtime to determine the objects properties and methods. In Late Binding the objects are defined as objects. Late biding is slower than Early Binding because the application must interrogate the object to determine its properties and methods. 3) Reclaiming Space: Reclaim space from strings by setting a string variable to the empty string (“”) space can also be reclaim from object by setting an object variable to Nothing. It frees the space associated with the object if it is the last reference to the object. It also has the advantage of reducing the amount of cleanup work needed when the program terminates.

4)Control Array: Complex forms needs more memory. The more controls put on a form, the more memory it will require when it becomes loaded in to memory. Therefore, reducing the number of controls reduces the memory requirements. For this a control array must be used. A control array counts as only one name. Control arrays consumes fewer resources than the equivalent number of independent controls. 5)Reducing Memory Requirement: By using Dynamic Arrays we can reduce memory requirements by trimming the array to just the elements we need. Use the Redim Statement to change the dimensions of the array. Erase statement can be used to free the memory associated with the dynamic array. Use fewer graphics. Graphic images consumes memory. The more graphics we have, the more memory we are going to use. Destroy forms when we finished with them. If we are finished with a form we can use the unload statement to remove the form from memory. This will free some memory resources. To free all of the form resources we must set forms object name to nothing. (Set Form1= Nothing).

In an effort to maintain computational efficiency and to allow the eventual adaptation of the algorithm to face tracking applications, intense optimization of the code has been performed. Although further development is in progress, the algorithm is currently fast and compact enough to run interactively on most generic platforms. First, the sequential hierarchical search which proceeds from large scales to small scales. This allows a rapid convergence if the face is dominant in the image. Furthermore, the algorithm does not always flow through the complete loop. It stops as soon as one of the modules reports a failure and loops back to an earlier stage. For example, we do not search for a mouth if no eyes are found. In this case, no time is wasted in the mouth module. Additionally, we utilized special programming techniques to reduce the runtime. For instance, wave propagation is used to generate the symmetry maps. This provides a computational efficiency that makes the symmetry operator a practical tool. The 3D normalization algorithm is also extremely efficient and uses look-up tables and minimal calculations for increased speed. The execution times are measure on an SGI Indy machine which has a rating equivalent to that of a 1996 home personal computer. The efficiency of the code allows a face to be found in an image in less than 1 second if it is the dominant structure. However, we loop through all objects in the scene in an attempt to find all possible faces. Thus, the algorithm's loop is traversed multiple times even though a face could have been detected in an earlier iteration of the loop.

SCREENSHOT

HOME Page

Login Page

Course Page

Discussion Page

Admin Inbox Open Mail

Course open

Announcement Page

Adedtech Page

Adeditimage Page

AdeditannPage

Adedimage Page

Adedevent Page

User Change Password

Stories Page

Student Report Page

School news Page

Logout Page

TESTING It should be clear in mind that the philosophy behind testing is to find errors. Test cases are devised with this purpose in mind. A test case is a set of data that the system will process as normal input. However, the data are created with the express intent of determining whether the system will process them correctly. For example, test cases for inventory handling should include situations in which the quantifies to be withdrawn from inventory exceed, equal and are less than the actual quantities on hand. Each test case is designed with the intent of finding errors in the way the system will process it. There are two general strategies for testing software: Code testing and Specification testing. In code testing, the analyst develops that cases to execute every instructions and path in a program. Under specification testing, the analyst examines the program specifications and then writes test data to determine how the program operates under specific conditions. Regardless of which strategy the analyst follows, there are preferred practices to ensure that the testing is useful. The levels of tests and types of test data, combined with testing libraries, are important aspects of the actual test process.

Levels of Testing Systems are not designed as entire systems nor are they tested as single systems. The analyst must perform both unit and system testing.

Unit Testing: In unit testing the analyst tests the programs making up a system. For this reason, unit testing is sometimes called program testing. Unit testing gives stress on the modules independently of one another, to find errors. This helps the tester in detecting errors in coding and logic that are contained within that module alone. The errors resulting from the interaction between modules are initially avoided. For example, a hotel information system consists of modules to handle reservations; guest checking and checkout; restaurant, room service and miscellaneous charges; convention activities; and accounts receivable billing. For each, it provides the ability to enter, modify or retrieve data and respond to different types of inquiries or print reports. The test cases needed for unit testing should exercise each condition and option. Unit testing can be performed from the bottom up, starting with smallest and lowest-level modules and proceeding one at a time. For each module in bottom-up testing a short program is used to execute the module and provides the needed data, so that the module is asked to perform the way it will when embedded within the larger system. System Testing: The important and essential part of the system development phase, after designing and developing the software is system testing. We cannot say that every program or system design is perfect and because of lack of communication between the user and the designer, some error is there in the software development. The number and nature of errors in a newly designed system depend on some usual factors like communication between the user

and the designer; the programmer's ability to generate a code that reflects exactly the systems specifications and the time frame for the design. Theoretically, a newly designed system should have all the parts or subsystems are in working order, but in reality, each sub-system works independently. This is the time to gather all the subsystem into one pool and test the whole system to determine whether it meets the user requirements. This is the last change to detect and correct errors before the system is installed for user acceptance testing. The purpose of system testing is to consider all the likely variations to which it will be subjected and then push the system to its limits. Testing is an important function to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully activated. Another reason for system testing is its utility as a user-oriented vehicle before implementation. System testing consists of the following five steps: 1) Program testing 2) String testing 3) System testing 4) System documentation 5) User acceptance testing

Program Testing: A program represents the logical elements of a system. For a program to run satisfactorily, it must compile and test data correctly and tie in properly with other programs. it is the responsibility of a programmer to have an error free program. At the time of testing the system, there exists two types of errors that should be checked. These errors are syntax and logic. A syntax error is a program statement that violates one or more rules of the language in which it is written. An improperly defined field dimension or omitted key words are common syntax errors. These errors are shown through error messages generated by the computer. A logic error, on the other hand, deals with incorrect data fields out of range items, and invalid combinations. Since the logical errors are not detected by compiler, the programmer must examine the output carefully to detect them. When a program is tested, the actual output is compared with the expected output. When there is a discrepancy, the sequence of the instructions, must be traced to determine the problem. The process is facilitated by breaking the program down into self-contained portions, each of which can be checked at certain key points. String Testing: Programs are invariably related to one another and interact in a total system. Each program is tested to see whether it conforms to related programs in the system. Each part of the system is tested against the entire module with both test and live data before the whole system is ready to be tested.

System Testing: System testing is designed to uncover weaknesses that were not found in earlier tests. This includes forced system failure and validation of total system as it will be implemented by its user in the operational environment. Under this testing, generally we take low volumes of transactions based on live data. This volume is increased until the maximum level for each transaction type is reached. The total system is also tested for recovery and fallback after various major failures to ensure that no data are lost during the emergency. All this is done with the old system still in operation. When we see that the proposed system is successful in the test, the old system is discontinued. System Documentation: All design and test documentation should be well prepared and kept in the library for future reference. The library is the central location for maintenance of the new system. User Acceptance Testing: An acceptance test has the objective of selling the user on the validity and reliability of the system. It verifies that the system's procedures operate to system specifications and that the integrity of important data is maintained. Performance of an acceptance test is actually the user's show. User motivation is very important for the successful performance of the system. After that a comprehensive test report is prepared. This report shows the system's tolerance, performance range, error rate and accuracy.

Special Systems Tests: There are other six tests which fall under special category. They are described below: Peak Load Test: It determines whether the system will handle the volume of activities that occur when the system is at the peak of its processing demand. For example, test the system by activating all terminals at the same time. Storage Testing: It determines the capacity of the system to store transaction data on a disk or in other files. For example, verify documentation statements that the system will store 10,000 records of 400 bytes length on a single flexible disk. Performance Time Testing: it determines the length of time system used by the system to process transaction data. This test is conducted prior to implementation to determine how long it takes to get a response to an inquiry, make a backup copy of a file, or send a transmission and get a response. Recovery Testing: This testing determines the ability of user to recover data or re-start system after failure. For example, load backup copy of data and resume processing without data or integrity loss. Procedure Testing: It determines the clarity of documentation on operation and use of system by having users do exactly what manuals request. For

example, powering down system at the end of week or responding to paperout light on printer. Human Factors Testing: It determines how users will use the system when processing data or preparing reports.

IMPLEMENTATION Hardware Requirement Software Requirement

Hardware Requirement Hardware is the term given to machinery itself and to various individual pieces of equipment. It refers to the physical devices of a computer system. Thus the input, storage, processing control and output devices are hardware.

Minimum Hardware Requirement Of Client Side: Processor

:

Any Pentium IV or Equivalent Machine

RAM

:

256 MB

HDD

:

40 GB

FDD

:

1.44 MB

CD-ROM

:

52X

15 inches Color Monitor 104 Keys Keyboards Printer

:

DeskJet 670 C

Software Requirement Software means a collection of program where the objective is to enhance the capabilities of the hardware machine.

Minimum Software Requirement Of Client Side: Operating System

:

Windows 9x/NT/2000/XP

Database

:

MS – SQL SERVER 2000/2005

MAINTENANCE

MAINTENANCE Once the software is delivered and developed, it enters the maintenance phase. After implementation systems need maintenance. Beyond monkey testing during Software development some errors may not appear. During its usage by the end-user with actual data certain errors may disclose. Therefore some residual errors or bugs remain in the system that must be removed as they are discovered. Many of these surfaces only after the system have been in operation sometimes for a long time. These errors once discovered need to be removed on an urgent basis for the smooth running of the

system,

leading

to

the

software

getting

changed.

Though Maintenance is not a part of software development, it is an extremely important activity in the life of a software product. Maintenance involves understanding the existing software (code and related documents), understanding the effects of change, making the changes-to both the code and documents-testing the new parts and retesting the old part. For successful and smooth running of the system, maintenance is the prominent part of the project. Any error, which hinders the functioning of any part of the project, may lead to bad impression of the developer. There are majorly two types of errors: Compilation error and Runtime errors.

Compilation errors are errors during coding and are to be taken care by the developer during development process. Runtime errors are those which occurs during running of the program. Whenever there is an occurrence of error an ‘Error Window’ opens in the middle of the screen displaying the type of error, Error Number and the Nearest Possible reason as to why the error has occurred. With the occurrence of this Error Window the operator (End-user) should note the type of error, the error number and the description of the error and should immediately report to the concerned Developer or Administrator. Now comes the role of the Maintenance Personals. After knowing the entire details from the end-user like where or at which screen does this error occurred or what type of data was feeded by the user or the point of malfunctioning. Considering this error as the main reason for the malfunctioning the programmer now re-examines all the possible factors, which act behind the particular screen where error has occurred. After debugging the required error the programmer itself tests the same screen or process with dummy data. Only after getting completely satisfied with problem rectification the programmer compiles and runs the program.

CODING

Home Page Home.aspx var whichlink=0 var whichimage=0 var blenddelay=(ie)? document.images.slide.filters[0].duration*1000 : 0 function slideit(){ if (!document.images) return if (ie) document.images.slide.filters[0].apply() document.images.slide.src=imageholder[whichimage].src if (ie) document.images.slide.filters[0].play() whichlink=whichimage whichimage=(whichimage 0) { Label1.Visible Table1.Visible } else { Label1.Visible Table1.Visible } dr.Close(); c.con.Close();

= false; = true;

= true; = false;

} if (Request.QueryString["sub"] == "m") { Table3.Visible = true; Label3.Visible = true; c.con.Open(); string str = "select * from material where mat_subject='Maths'";

SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); int i = 0; int a = 1; while (dr.Read()) { TableRow R = TableCell c1 TableCell c2 TableCell c3 TableCell c4

HyperLink(); dr["mat_id"];

new TableRow(); = new TableCell(); = new TableCell(); = new TableCell(); = new TableCell();

c1.Text = a.ToString(); System.Web.UI.WebControls.HyperLink h1 = new h1.NavigateUrl = "courseopen.aspx?mid=" + h1.Text = dr["mat_orgname"].ToString(); c3.Controls.Add(h1); c2.Text = dr["mat_des"].ToString(); c4.Text = dr["mat_dttm"].ToString(); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign

= = = =

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center;

Table3.Rows.Add(R); i = i + 1; a = a + 1; } if (i > 0) { Label3.Visible Table3.Visible } else { Label3.Visible Table3.Visible } dr.Close(); c.con.Close();

= false; = true;

= true; = false;

} if (Request.QueryString["sub"] == "p") { Table4.Visible = true; Label4.Visible = true; c.con.Open(); string str = "select * from material where mat_subject='Physics'";

SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); int i = 0; int a = 1; while (dr.Read()) { TableRow R = new TableRow(); TableCell c1 = new TableCell(); TableCell c2 = new TableCell(); TableCell c3 = new TableCell(); TableCell c4 = new TableCell(); c1.Text = a.ToString(); System.Web.UI.WebControls.HyperLink h1 = new HyperLink(); dr["mat_id"];

h1.NavigateUrl = "courseopen.aspx?mid=" + h1.Text = dr["mat_orgname"].ToString(); c3.Controls.Add(h1); c2.Text = dr["mat_des"].ToString(); c4.Text = dr["mat_dttm"].ToString(); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign

= = = =

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center;

Table4.Rows.Add(R); i = i + 1; a = a + 1;

} if (i > 0) { Label4.Visible Table4.Visible } else { Label4.Visible Table4.Visible } dr.Close(); c.con.Close();

= false; = true;

= true; = false;

} if (Request.QueryString["sub"] == "eng") { Table2.Visible = true; Label2.Visible = true; c.con.Open(); string str = "select * from material where mat_subject='English'"; SqlCommand cmd = new SqlCommand(str, c.con);

SqlDataReader dr = cmd.ExecuteReader(); int i = 0; int a = 1; while (dr.Read()) { TableRow R = new TableRow(); TableCell c1 = new TableCell(); TableCell c2 = new TableCell(); TableCell c3 = new TableCell(); TableCell c4 = new TableCell(); c1.Text = a.ToString(); System.Web.UI.WebControls.HyperLink h1 = new

HyperLink();

h1.NavigateUrl = "courseopen.aspx?mid=" +

dr["mat_id"];

h1.Text = dr["mat_orgname"].ToString(); c3.Controls.Add(h1); c2.Text = dr["mat_des"].ToString(); c4.Text = dr["mat_dttm"].ToString(); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign

= = = =

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center;

Table2.Rows.Add(R); i = i + 1; a = a + 1;

} } }

} if (i > 0) { Label2.Visible Table2.Visible } else { Label2.Visible Table2.Visible } dr.Close(); c.con.Close();

}

}

Adsendmail.aspx

= false; = true;

= true; = false;



Adsendmail.aspx.cs using using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class adsendmail : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["aid"] == null) { Response.Redirect("index.aspx?q=n"); } if (Request.QueryString["us_id"] != "") { int i; string[] quid = Request.QueryString["us_id"].Split(','); for (i = 0; i < quid.Length - 1; i++) ; int val = Convert.ToInt32(quid[i]); for (i = 0; i < quid.Length; i++)

{

Session["quid"] = quid[i].ToString(); c.con.Open(); string str = "select * from usr where u_id=" + quid[i]; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { lbl_ID.Text = dr["u_id"].ToString(); lbl_name.Text = dr["u_name"].ToString(); lbl_pwd.Text = dr["u_pwd"].ToString(); } dr.Close(); c.con.Close(); c.con.Open(); string str2 = "select * from usr_mail order by m_id"; SqlCommand cmd2 = new SqlCommand(str2, c.con); SqlDataReader dr2 = cmd2.ExecuteReader(); int i1 = 0; while (dr2.Read()) { int a = 0; a = Convert.ToInt32(dr2["m_id"].ToString()); ViewState["mid"] = a.ToString(); i1 = i1 + 1; } if (i1 > 0) { int a = Convert.ToInt32(ViewState["mid"].ToString()); a = a + 1; ViewState ["id"] = a.ToString(); } else ViewState ["id"] = "10201"; c.con.Close(); c.con.Open(); string body = "Hi " + lbl_name.Text + ",\r\nYou are selected for the written test.\r\n Your login details are : \r\n\r\n ID:- " + lbl_ID.Text + "\r\nPassword: " + lbl_pwd.Text + "\r\nBest Of Luck.\r\n \r\nThanks & Regards, \r\nAdmin"; string abc = "insert into usr_mail(m_id,m_usrid,m_sendby,m_dttm,m_sub,m_body) values(" + ViewState["id"].ToString() + ",'" + quid[i] + "','Admin','" + System.DateTime.Now.ToString() + "','Admit Card Details','" + body + "')"; SqlCommand cmd1 = new SqlCommand(abc, c.con); cmd1.ExecuteNonQuery(); if (i == 0) Label1.Text += quid[i]; else Label1.Text += "," + quid[i]; //i = i + 1; c.con.Close(); } }

}

Response.Redirect("adsearch.aspx?com=" + Label1.Text);

}

Front master body { valign="top"; margin:0px; } //specify interval between slide (in mili seconds) var slidespeed=3000 //specify images var slideimages=new Array("images/1.JPG","images/2.JPG","images/3.JPG") //specify corresponding links var slidelinks=new Array("#","#","#") var newwindow=1 //open links in new window? 1=yes, 0=no var imageholder=new Array() var ie=document.all for (i=0;i

:: ONLINE RECRUITMENT SYSTEM :: ONLINE RECRUITMENT SYSTEM >> Home >> Login >> New User >> Online Test >> Report !!....Online Recruitment System....!! !!....Best Viewed in 1024x768....!!

Front master.cs using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class front : System.Web.UI.MasterPage { protected void Page_Load(object sender, EventArgs e) { }

}

Logout.aspx

Logout.aspx.cs using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class logout : System.Web.UI.Page {

}

protected void Page_Load(object sender, EventArgs e) { Session["aid"] = null; Session["uid"] = null; Session["stud"] = null; Response.Redirect("home.aspx"); }

Newusr.aspx >>  New User    

     

 

TabIndex="6">

  0) { int a = Convert.ToInt32(ViewState["sid"].ToString()); a = a + 1; txt_cid.Text = a.ToString(); } else txt_cid.Text = "200901"; c.con.Close();

} protected void Button1_Click(object sender, EventArgs e) { if (ddl_dte.Text == "----Date----") { Label9.Visible = true; Label9.Text = "!!..Select user's DOB Date ..!!"; } else { if (ddl_mon.Text == "----Month----") { Label9.Visible = true; Label9.Text = "!!..Select user's DOB Month..!!"; } else { if (ddl_dobyr.Text == "----Year----") { Label9.Visible = true; Label9.Text = "!!..Select user's DOB Year..!!"; } else { if (ddl_degree.Text == "----Select----") { Label9.Visible = true; Label9.Text = "!!..Select user course/degree..!!"; } else { if (ddl_pass.Text == "----Select----") { Label9.Visible = true; Label9.Text = "!!..Select user year pass..!!"; } else { if (ddl_exp.Text == "----Select----") { Label9.Visible = true; Label9.Text = "!!..Select user experience..!!"; } else {

try { string dob = ddl_dte.Text + "/" +

ddl_mon.Text + "/" + ddl_dobyr.Text;

c.con.Open(); string str = "insert into usr(u_id,u_pwd,u_name,u_dob,u_add,u_fname,u_degree,u_marks,u_yrpass,u_p ostapp,u_exp,u_sel,u_dttm,u_ccno) values(" + txt_cid.Text + ",'" + txt_pass.Text + "','" + txt_cname.Text + "','" + dob + "','" + txt_cadd.Text + "','" + txt_fname.Text + "','" + ddl_degree.Text + "','" + txt_marks.Text + "','" + ddl_pass.Text + "','" + txt_postapp.Text + "','" + ddl_exp.Text + "','n','" + System.DateTime.Now.ToString() + "','" + txt_ccno.Text + "')"; SqlCommand cmd = new SqlCommand(str, c.con); cmd.ExecuteNonQuery(); c.con.Close(); log(); Label9.Visible = true; Label9.Text = "!!..Hi.."+txt_cname .Text +", Your Account is successfully created..!!"; txt_cid.Text = ""; txt_marks.Text = ""; txt_postapp.Text = ""; txt_cadd.Text = ""; txt_ccno.Text = ""; txt_cname.Text = ""; txt_fname.Text = ""; txt_pass.Text = ""; Button1.Enabled = false; } catch (Exception ex) { Label9.Visible = true; Label9.Text = ex.Message; } } } } } } } } public void log() { //string type = "s"; c.con.Open(); string str = "insert into login (uname,upass,utype) values('" + txt_cid.Text + "','" + txt_pass.Text + "','u')"; SqlCommand cmd = new SqlCommand(str, c.con); cmd.ExecuteNonQuery(); c.con.Close(); } }

adedevent.aspx Add New Event| Edit Event >>  Edit Event Details

adedevent.aspx.cs using System;

using using using using using using using using using using

System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class adedevent : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } if (!Page.IsPostBack) { insert(); } } public void insert() { c.con.Open(); string str = "select * from event order by ev_id"; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr1 = cmd.ExecuteReader(); int i = 0; while (dr1.Read()) { TableRow R = new TableRow(); TableCell c1 = new TableCell(); TableCell c2 = new TableCell(); TableCell c3 = new TableCell(); TableCell c4 = new TableCell(); TableCell c5 = new TableCell(); TableCell c6 = new TableCell(); c1.Text c2.Text c3.Text c4.Text

= = = =

dr1["ev_id"].ToString(); dr1["ev_head"].ToString(); dr1["ev_des"].ToString(); dr1["ev_dttm"].ToString();

System.Web.UI.WebControls.HyperLink h1 = new HyperLink(); System.Web.UI.WebControls.HyperLink h2 = new HyperLink(); h1.NavigateUrl = "adeditevent.aspx?e_id=" + dr1["ev_id"]; h1.Text = "Edit"; h2.Text = "Delete"; h2.Attributes.Add("onclick", "return confirm('Are You sure you want to delete?');"); h2.NavigateUrl = "addelevent.aspx?e_id=" + dr1["ev_id"];

c5.Controls.Add(h1); c6.Controls.Add(h2); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); R.Cells.Add(c5); R.Cells.Add(c6); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign c5.HorizontalAlign c6.HorizontalAlign

= = = = = =

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center; HorizontalAlign.Center;

Table3.Rows.Add(R); i = i + 1;

}

} c.con.Close();

}

adedevent.aspx Add/Edit Album | Add Image | Edit Image Details >>  Edit Image Details



adedevent.aspx.cs using using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class adedevent : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } if (!Page.IsPostBack) { insert(); } } public void insert()

{

c.con.Open(); string str = "select * from event order by ev_id"; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr1 = cmd.ExecuteReader(); int i = 0; while (dr1.Read()) { TableRow R = new TableRow(); TableCell c1 = new TableCell(); TableCell c2 = new TableCell(); TableCell c3 = new TableCell(); TableCell c4 = new TableCell(); TableCell c5 = new TableCell(); TableCell c6 = new TableCell(); c1.Text c2.Text c3.Text c4.Text

= = = =

dr1["ev_id"].ToString(); dr1["ev_head"].ToString(); dr1["ev_des"].ToString(); dr1["ev_dttm"].ToString();

System.Web.UI.WebControls.HyperLink h1 = new HyperLink(); System.Web.UI.WebControls.HyperLink h2 = new HyperLink(); h1.NavigateUrl = "adeditevent.aspx?e_id=" + dr1["ev_id"]; h1.Text = "Edit"; h2.Text = "Delete"; h2.Attributes.Add("onclick", "return confirm('Are You sure you want to delete?');"); h2.NavigateUrl = "addelevent.aspx?e_id=" + dr1["ev_id"]; c5.Controls.Add(h1); c6.Controls.Add(h2); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); R.Cells.Add(c5); R.Cells.Add(c6); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign c5.HorizontalAlign c6.HorizontalAlign Table3.Rows.Add(R); i = i + 1;

= = = = = =

} c.con.Close(); }

}

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center; HorizontalAlign.Center;

adedevent.aspx >>  Edit Announcement Details Back       * Mandatory Fields                  

adedevent.aspx.cs using System; using System.Data; using System.Configuration; using System.Collections; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Web.UI.HtmlControls; using System.Data.SqlClient; public partial class adeditann : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); }

if (!Page.IsPostBack) { if (Request.QueryString["annid"] != null) { Label9.Visible = true; Label9.Text = "Announcement Details of ID " + Request.QueryString["annid"].ToString() + " is successfully updated"; Button1.Enabled = false; } else { Button1.Enabled = true; Label9.Visible = false; insert(); } } } public void insert() { c.con.Open(); ViewState["vs"] = Request.QueryString["anid"].ToString(); string str = "select * from announcement where ann_id=" + ViewState["vs"].ToString() + ""; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { txt_cid.Text = dr["ann_id"].ToString(); txt_des.Text = dr["ann_des"].ToString(); txt_head.Text = dr["ann_head"].ToString(); } dr.Close(); c.con.Close(); } protected void Button1_Click(object sender, EventArgs e) { try { string dttm = System.DateTime.Now.ToString(); c.con.Open(); string str1 = "update announcement set ann_head='" + txt_head.Text + "',ann_des='" + txt_des.Text + "', ann_dttm='" + dttm + "' where ann_id=" + ViewState["vs"].ToString() + ""; SqlCommand cmd1 = new SqlCommand(str1, c.con); cmd1.ExecuteNonQuery(); c.con.Close(); Response.Redirect("adeditann.aspx?annid=" + ViewState["vs"].ToString()); } catch (Exception ex) { Label9.Visible = true; Label9.Text = ex.Message; } } protected void txt_head_TextChanged(object sender, EventArgs e) {

} }

Uhome.aspx Hi , Welcome to your home page..!!

Uhome.aspx.cs using using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class uhome : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } else { c.con.Open(); string str = "select * from usr where u_id=" + Session["uid"]; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { Session["uname"] = dr["u_name"].ToString(); } dr.Close();

c.con.Close(); string mail = Session["uname"].ToString(); Label1.Text = Convert.ToString(mail).ToUpperInvariant(); }

}

}

adedimage.aspx >>  Edit Image Details Back    

          * Mandatory Fields

adedimage.aspx.cs using using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls; System.Data.SqlClient;

public partial class adedimage : System.Web.UI.Page { Connct c = new Connct(); protected void Page_Load(object sender, EventArgs e) { if (Session["uid"] == null) { Response.Redirect("login.aspx?log=n"); } if (!Page.IsPostBack) { filldll(); insert(); } } public void filldll() { c.con.Open(); string str = "select * from album order by al_name"; SqlDataAdapter ad = new SqlDataAdapter(str, c.con); DataSet ds = new DataSet(); ad.Fill(ds, "album"); DropDownList1.DataSource = ds; DropDownList1.DataTextField = "al_name"; DropDownList1.DataValueField = "al_id"; DropDownList1.DataBind(); c.con.Close(); } public void insert() { c.con.Open(); string str = "select * from image,album where al_id=img_alname order by img_id"; SqlCommand cmd = new SqlCommand(str, c.con); SqlDataReader dr1 = cmd.ExecuteReader(); int i = 0; while (dr1.Read()) { TableRow R = new TableRow(); TableCell c1 = new TableCell();

TableCell TableCell TableCell TableCell TableCell

c2 c3 c4 c5 c6

= = = = =

new new new new new

TableCell(); TableCell(); TableCell(); TableCell(); TableCell();

c1.Text = dr1["img_id"].ToString(); c2.Text = dr1["img_name"].ToString(); DropDownList1.SelectedValue = dr1["img_alname"].ToString(); c3.Text = DropDownList1.SelectedItem.Text; System.Web.UI.WebControls.Image i1 = new Image(); i1.ImageUrl = "~/Attach/" + dr1["img_orgname"].ToString(); i1.Height = 100; i1.Width = 150; c4.Controls.Add(i1); System.Web.UI.WebControls.HyperLink h1 = new HyperLink(); System.Web.UI.WebControls.HyperLink h2 = new HyperLink(); h1.NavigateUrl = "adeditimage.aspx?imgid=" + dr1["img_id"]; h1.Text = "Edit"; h2.Text = "Delete"; h2.Attributes.Add("onclick", "return confirm('Are You sure you want to delete?');"); h2.NavigateUrl = "addelimage.aspx?imgid=" + dr1["img_id"]; c5.Controls.Add(h1); c6.Controls.Add(h2); R.Cells.Add(c1); R.Cells.Add(c2); R.Cells.Add(c3); R.Cells.Add(c4); R.Cells.Add(c5); R.Cells.Add(c6); c1.HorizontalAlign c2.HorizontalAlign c3.HorizontalAlign c4.HorizontalAlign c5.HorizontalAlign c6.HorizontalAlign

= = = = = =

HorizontalAlign.Center; HorizontalAlign.Left; HorizontalAlign.Left; HorizontalAlign.Center; HorizontalAlign.Center; HorizontalAlign.Center;

Table3.Rows.Add(R); i = i + 1;

}

} c.con.Close();

}

Admin master

body { valign="top"; margin:0px; } Untitled Page ~~ ADMIN SECTION ~~ >> Home >> Add Article Details >> Add Announcement Details >> Add Event Details >>

Add Student Details >> Add Teacher Details >> Add Album/Image >> Add Research Link >> Add Success Stories >> Add Poll Questions >> Add Course Details >> Activate/Deactivate Discussion Topic >> Add Result Powerpoint Slides >> Logout !!....Online Learning Portal....!!

!!....Best Viewed in 1024x768....!!

Admin master.aspx.cs using using using using using using using using using using

System; System.Data; System.Configuration; System.Collections; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Web.UI.HtmlControls;

public partial class Admin : System.Web.UI.MasterPage { protected void Page_Load(object sender, EventArgs e) { } }

Web.config Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config -->

The section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace.

-->

value="false"/>





FUTURE APPLICATION OF THE PROJECT

The future of the Project looks more promising. The main advantage of the project is that it provides different types of registered users to be interviewed by the administrator. Admin can interact with the selected users through phone only. Now this site is free, after few months, registered users has to pay monthly for better and good services. In future, we can have the search engine that can provide the result on the basis of different criteria to search. We can also have one more module of implementing this project on web.

BIBLIOGRAPHY WEB REFRENCES

BIBLIOGRAPHY

 ASP.NET

UNLEASHED……………………………….Stephen

Walther.  Inside Ms-SQL Server ……..……………………………..Kalen

Delaney

Web References http://opensmpp.logica.com/introhtml/menu.htm www.devshock.com www.msdn.com http://www.asp.net/ http://msdn.microsoft.com/netframework/windowsforms/ www.sas.com www.bonrix.net