INTRODUCTION

This Website THE WORLD KNOWLEDGE focuses on the following :---

It includes the latest news about:-1. SPORTS 2. CURRENT AFFAIRS 3. CARS AND BIKES 4. NRI PUNJABIS NEWS 5. COMPLETE ENTERTAINMENT NEWS 6. SCIENCE & TECHNOLOGY NEWS 7. HEALTH 8. PUNJAB 9. FUTURE TECH. AND MANY MORE...

ABOUT THE HCL CDC

A pioneer in IT industry and a leader for 31 years, HCL has been on the forefront of most of the innovations in Information Technology. With strengths in hardware, software and networking. technologies, HCL has emerged as a global leader in IT space. As the fountainhead of the most significant pursuit of human mind, HCL believes; only a leader can transform you into a leader. HCL CDC is an initiative that enables individuals to benefit from HCL expertise in the space and become Industry ready IT professionals. To enhance its market reach and strength, HCL has tied-up with global technology leaders, viz. Microsoft, Oracle, Cisco, Red Hat and Thomson Parametric. These alliances will help students Learn the contemporary technologies through different modes of learning. HCL career program equips you to meet emerging industry challenges with finesse and ease. Opportunities to grow with HCL are limitless, catapulting you to high level controlling positions In mega corporate. With top HCL professionals as your trainers, customized career programs, hands on experience.

State of art infrastructure and world class training program your career graph is bound to follow a steep rise.We offer the most modern computing facilities

loaded with the latest operating systems and Software packages. The classrooms are equipped with complete audio-visual tools & accessories. We have highly qualified, professional experienced faculty giving per personal attention to Students. The courses are highly customized and industry specific. We offer a bustling, vibrant And convenient environment to the student community of the institute. The infrastructure we Provide is truly world class. The courses are highly customized & industry specific.

OBJECTIVES
This Website THE WORLD KNOWLEDGE intended to provide

o o o

Automated solution to Latest Knowledge. This System provides some innovative features.

o A complete immense solution for Latest News And Videos.

It is extremely User friendly The user can keep track of every latest news Even if the user has no previous track record of operating a database There are different users for this system as per the requirements and they User Benefits & Solutions Get Right information in shortest time. Paperless database hence paperless office.

system even then he can easily operate it. can access only those fields which they need to know.

SYSTEM ANALYSIS
System Analysis by definition is a process of systematic investigation for the purpose of gathering data, interpreting the facts, diagnosing the problem and using this information to either build a completely new system or to recommend the improvements to the existing system. A satisfactory system analysis involves the process of examining a business situation with the intent of improving it through better methods and procedures. In its core sense, the analysis phase defines the requirements of the system and the problems which user is trying to solve irrespective of how the requirements would be accomplished There are 2 methods to perform System Requirement Analysis:

Structured Analysis

Structured Analysis is an analysis method that provides a basis for developing a model of software to be developed. The objective of structured analysis is to

identify the customer requirements and establish a basis to create a software model. The components of a Structured Analysis are Data Dictionary Entity Relationship Diagram Data Flow Diagram Process Specification Control Specification

Object Oriented Analysis It refers to a detailed study of the various objects involved in a system and the relationship of these objects with each other. While performing an object oriented analysis, the focus of the system analyst is on the availability of the objects that are relevant to software development. First and foremost we have to identify the need for development of such a System.

IDENTIFICATION OF NEED

HCL CDC, one of the leading career development centers in the past had a manual based data keeping system. This had several drawbacks, the major ones being listed below: 1) All the details of the student were being entered on paper manually which was an extremely cumbersome as well as time consuming process. 2) Further it was inefficient as stacks of storage were required to maintain these records. 3) There was growing negative student feedback since the record retrieval information was slow and the records occasionally tended to get lost which further led to inconvenience to the students. Keeping all these drawbacks in mind, there was a need felt for having an automated data Management System in place which could address all the above issues and provide viable solutions.

PRELIMINARY INVESTIGATION
The basic purpose behind Preliminary Investigation is to first clarify, understand and evaluate the Project Request. Preliminary Investigation basically refers to the collection of information that guides the organizer of an organization to evaluate the merits and demerits of the project request and make an informed judgment about the feasibility of the proposed system. This sort of investigation provides us with a through picture of the kind of software and hardware requirements which are most feasible for the system, plus the environment in which the entire project has to be installed and made operational. 1) Reviewing the Documents provided by the Organization They were quite effective in guiding us towards visualizing the features that were needed to be put together in the system and the required output which had to be generated once the system became functional. These specifications provided to us by the organization showed how the new system should look like; it helped us in understanding the basic structure of the application which we were supposed to develop. 2) On site Observation: Another technique utilized by us to gain information about the project was to visit the client site where the system had to be installed. Here a detailed system study was carried out, checking the existing system to replicate it with our system. On observing the existing system which the client was using helped us a lot in taking a decision regarding the feasibility of putting a SQL which could be made compatible with their other running systems. 3) Conducting Interviews: This method of investigation conducted by us involved questioning the concerned personnel to get the users (client) view about the system and the features they desired it to have. Some of the Questions put forward by our team were: a) The amount of data needed to be stored. 9

b) The issue of our application with existing system was widely discussed. c) Various standards and norm as of coding the application were looked. d) The level of access given to the customer would depend on his department.

10

FEASIBILITY STUDY
A feasibility study determines whether the proposed solution is feasible based on the priorities of the requirements of the organization. A feasibility study culminates in a feasibility report that recommends a solution. It helps you to evaluate the cost-effectiveness of a proposed system. The feasibility study is carried out to test if the proposed system is worth being implemented. Given unlimited resources and infinite time, all projects are feasible. After performing a Preliminary Investigation, gathering and interpreting data and details concerning the project, a Feasibility Check is done which involves a series of steps to check the Technical, Financial and Operational feasibilities. During this phase, various solutions to the existing problems were examined. For each of these solutions the Cost and Benefits were the major criteria to be examined before deciding on any of the proposed systems. These Solutions would provide coverage of the following: a) Specification of information to be made available by the system. b) A clear cut description of what tasks will be done manually and what needs to be handled by the automated system. c) Specifications of new computing equipment needed. A system that passes the feasibility tests is considered a feasible system. Let us see some feasible tests in my project.

11

TECHNICAL FEASIBILITY
It is related to the software and equipment specified in the design for implementing a new system. Technical feasibility is a study of function, performance and constraints that may affect the ability to achieve an acceptable system. During technical analysis, the analyst evaluates the technical merits of the system, at the same time collecting additional information about performance, reliability, maintainability and productivity. Technical feasibility is frequently the most difficult areas to assess. The main technical issue raised during feasibility is the existence of necessary technology and whether the proposed equipment has the capacity to hold required data. The technical guarantee of accuracy, reliability, ease and data were also investigated. Assessing System Performance: It involves ensuring that the system responds to user queries and is efficient, reliable, accurate and easy to use. Since we have the excellent network setup which is supported and excellent configuration of Pcs with 80 GB hard disk and 512 MB RAM, it satisfies the performance requirement. After the conducting the technical analysis we found that our project fulfills all the technical pre-requisites, the network environments if necessary are also adaptable according to the project.

12

ECONOMIC FEASIBILITY
This feasibility has great importance as it can outweigh other feasibilities because costs affect organization decisions. The concept of Economic Feasibility deals with the fact that a system that can be developed and will be used on installation must be profitable for the Organization. The cost to conduct a full system investigation, the cost of hardware and software, the benefits in the form of reduced expenditure are all discussed during the economic feasibility. Return on Investment i. ii. iii. iv. There will be revenue in terms of more Student Registrations. There will be cost reduction in terms of maintaining huge amounts of There will be tracking of the Students from a centralized database. User satisfaction will lead to more upgrades and reduce the downgrades. Cost of No Change The cost will be in terms of utilization of resources leading to the cost to the company. Since our cost of project is our efforts, which is obviously less than the long-term gain for the company, the project should be made.

paper records, stationary, humans.

13

COST- BENEFIT ANALYSIS

A cost-benefit analysis is necessary to determine economic feasibility. The primary objective of the cost benefit analysis is to find out whether it is economically worthwhile to invest in the project. If the returns on the investment are good, then the project is considered economically worthwhile. Cost benefit analysis is performed by first listing all the costs associated with the project cost which consists of both direct costs and indirect costs. Direct costs are those incurred by buying software, hiring people, cost of consumable items, rent for accommodation etc. Indirect costs include those involving time spent by user in discussing problems with system analysts , gathering data about problem etc. OPERATIONAL FEASIBILITY Operation feasibility is a measure of how people feel about the system. Operational Feasibility criteria measure the urgency of the problem or the acceptability of a solution. Operational Feasibility is dependent upon determining human resources for the project. It refers to projecting whether the system will operate and be used once it is installed. 1.If the ultimate users are comfortable with the present system and they see no problem with its continuance, then resistance to its operation will be zero. Behaviorally also the proposed system is feasible. A particular application may be technically and but may fail to produce the forecasted benefits, because the company is not able to get it to work. For the system, it is not necessary that the user must be a computer expert, but any computer operator given a little bit of knowledge and training can easily operate. Our Project is operationally feasible since there is no need for special training of staff member and whatever little instructing on this system is required can be done so quite easily and quickly as it is essentially.

14

SOFTWARE/HARDWARE SPECIFICATION
Tools/Platform Languages to be used The project will be built using a Multimedia Machine with the following configuration: Hardware Requirements Component RAM Processor Hard Space Software Requirements Software Type Operating system Front End Back End Platform: The operating system that will be used as a platform to build up the project is Windows XP, although it can run very well on other versions of Windows too. Language: ASP.Net will be used to implement the functionality of the project. ASP.Net will be used to create the Front End of the Application. And SQL server will be used to create the Back End of the application. Database: 15 Recommended Windows XP(or higher ASP.NET SQL server Drive Disk Recommended 512MB or higher Pentium III, 70 MHz or higher 40 GB or higher

Microsoft SQL Server is comprehensive, integrated data management and analysis software that enables organizations to reliably manage mission-critical information and confidently run todays increasingly complex business applications. SQL Server allows companies to gain greater insight from their business information and achieve faster results for a competitive advantage.

TECHNOLOGY USED
Front End: - ASP.Net ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of 16

the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. ASP.NET is the next generation ASP, but it's not an upgraded version of ASP.ASP.NET is an entirely new technology for server-side scripting. It was written from the ground up and is not backward compatible with classic ASP. ASP.NET is a Microsoft Technology. ASP stands for Active Server Pages .ASP.NET is a program that runs inside IIS .IIS (Internet Information Services) is Microsoft's Internet server .IIS comes as a free component with Windows servers .IIS is also a part of Windows 2000 and XP Professional. ASP.NET has better language support, a large set of new controls and XML based components, and better user authentication.ASP.NET provides increased performance by running compiled code An ASP.NET page has the extension .aspx. If a browser requests an ASP.NET page, the server processes any executable code in the page, before the result is sent back to the browser. ASP.NET encourages the programmer to develop applications using an eventdriven GUI model, rather than in conventional web-scripting environments like ASP and PHP. The framework attempts to combine existing technologies such as JavaScript with internal components like "View State" to bring persistent (inter-request) state to the inherently stateless web environment. Compiled code means applications run faster with more design-time errors trapped at the development stage.

ASP.NET Framework 3.5

ASP.NET Framework 3.5 has been launched recently ( on 19 November , 2007) as an improvement to the previous version 3.0 .The main features which distinguish this version from the prior versions are many such as New data 17

controls (List View, Data Pager) ,ASP.NET AJAX included as part of the framework ,Support for HTTP pipelining and syndication feeds, WCF Support for RSS, JSON, POX and Partial Trust etc.This version has all the features of the prior versions and supports them completely. Features of ASP.NET 3.5 ASP.NET AJAX: With ASP.NET AJAX, developers can quickly create pages with sophisticated, responsive user interfaces and more efficient client-server communication by simply adding a few server controls to their pages. New List View and Data Pager Controls : The new List View control gives you unprecedented flexibility in how you display your data, by allowing you to have complete control over the HTML markup generated. List Views template approach to representing data is designed to easily work with CSS styles, which come in handy with the new Visual Studio 2008 designer view. In addition, you can use the Data Pager control to handle all the work of allowing your users to page through large numbers of records. LINQ: With the addition of Language Integrated Query (LINQ) in .NET Framework 3.5, the process of building SQL queries using error-prone string manipulation is a thing of the past. LINQ makes your relational data queries a first-class language construct in C# and Visual Basic, complete with compiler and Intelligence support. WCF Support for RSS, JSON, POX and Partial Trust: With .NET Framework 3.5, Windows Communication Foundation (WCF) now supports building Web services that can be exposed using any number of the Internet standard protocols, such as SOAP, RSS, JSON, POX and more. Whether you are building an AJAX application that uses JSON, providing syndication of your data via RSS, or building a standard SOAP Web service, WCF makes it easy to create your endpoints, and now, with .NET Framework 3.5, supports building

18

Web services in partial-trust situations like a typical shared-hosting environment. JavaScript Debugging and Intelligence: The Intelligence give standard

JavaScript keyword support and it will automatically infer variable types and provide method, property and event support from any number of included script files. Similarly, the JavaScript debugging support now allows for the deep Watch and Locals support in JavaScript that you are accustomed to having in other languages in Visual Studio. And despite the dynamic nature of a lot of JavaScript, you will always be able to visualize and step into the JavaScript code, no matter where it is generated from.Multi-targeting Support: Through a simple drop-down, you can decide if you want a project to target .NET Framework 2.0, 3.0 or 3.5. The builds, the Intelligence, the toolbox, etc. will all adjust to the feature set of the specific version of the .NET Framework which you choose providing multi targeting support.

HTML
HTML is a language for describing web pages. It stands for Hyper Text Markup Language and uses markup tags. HTML tags: HTML tags are keywords surrounded by angle brackets like <html> .They normally come in pairs like <b> and </b> .The first tag in a pair is

19

the start tag, the second tag is the end tag . Start and end tags are also called opening tags and closing tags. HTML Documents: HTML documents describe web pages. They contain HTML tags and plain text and are also called web pages. The purpose of a web browser (like Internet Explorer or Firefox) is to read HTML documents and display them as web pages. The browser does not display the HTML HTML Headings:- HTML headings are defined with the <h1> to <h6> tags

JavaScript
JavaScript is used in millions of Web pages to improve the design, validate forms, detect browsers, create cookies, and much more. JavaScript is the most popular scripting language on the internet, and works in all major browsers, such as Internet Explorer, Firefox and Opera. JavaScript was designed to add interactivity to HTML pages. It is a scripting language and it is a lightweight 20

programming language. It is usually embedded directly into HTML pages. Everyone can use JavaScript without purchasing a license. What can a JavaScript Do? JavaScript gives HTML designers a programming tool - HTML authors are normally not programmers, but JavaScript is a scripting language with a very simple syntax! Almost anyone can put small "snippets" of code into their HTML pages. JavaScript can put dynamic text into an HTML page - A JavaScript statement like this: document. Write ("<h1>" + name + "</h1>") can write a variable text into an HTML page. JavaScript can react to events - A JavaScript can be set to execute when something happens, like when a page has finished loading or when a user clicks on an HTML element.JavaScript can read and write HTML elements - A JavaScript can read and change the content of an HTML element.JavaScript can be used to validate data - A JavaScript can be used to validate form data before it is submitted to a server. This saves the server from extra processing. JavaScript can be used to detect the visitor's browser - A JavaScript can be used to detect the visitor's browser, and - depending on the browser - load another page specifically designed for that browser.

Back End- SQL Server:

Microsoft SQL Server is comprehensive, integrated data management and analysis software that enables organizations to reliably manage mission-critical information and confidently run todays increasingly complex business applications. SQL Server allows companies to gain greater insight from their 21

business information and achieve faster results for a competitive advantage. SQL Server is an industry leading database system designed for mission critical data storage and retrieval. The RDBMS is responsible for accurately storing data and efficiently retrieving that data in response to user queries. Its Popularity is owned to a number of factors like its ability to support dozens to thousands of simultaneous users, its ability to handle high transaction rates and its ability to access databases that ranges in size from several hundred megabytes to many gigabytes.

Features of SQL Server:

Security Management: SQL Server provides a controlled to data to users

by providing a combination of privileges.

Backup and Recovery: SQL Server provides sophisticated security backup

and recovery routines.

Open connectivity: SQL Server provides open connectivity to and from

other vendors software such as Microsoft.

Various Front-End S/W: Also SQL Server database can be accessed by

various front-end softwares such as Visual Basic, C.

Space Management: In SQL Server one can flexibly allocate disk spaces

for data storage and can control them subsequently.

Others:

o SQL Server is designed with special feature of data warehousing. o (OLTP) systems are usually concerned with entering and retrieving missioncritical data from day-to-day operations. 22

o Availability, reliability, and performance are extremely important for these systems. delivers o Significant enhancements in these areas, along with improvements in scalability, serviceability, o Import/export support is provided for domain indexes. Indexes (including domain indexes) are exported by exporting the index definitions, namely the DELETE INDEX statements. o Because domain index data stored in database objects, such as tables, is exported, there is a fast rebuild of domain indexes at import time.

23

DATABASE SNAPSHOTS:-----------

24

25

26

27

28

29

30

31

32

33

34

35

36

37

SOFTWARE REQUIREMENTS SPECIFICATIONS

A key feature in the development of any software is analysis of the requirements that must be satisfied by software. A thorough understanding of these requirements is essential for the successful development and implementation of software. The software requirement specification is produced at the culmination of the analysis task. The function and performance allocated to software as part of system engineering are refined by establishing a complete information description, a detailed functional and behavioral description, an indication of performance requirements and design constraints, appropriate validation criteria. The Software Requirements Specifications basically states the goals and objectives of the software. It provides a detailed description of the functionality that software must perform. 38

HCL Total Organizer system deals with the processing of Students details. In our HCL Total Organizer system we have a number of screens/ forms through which we enter the data and store it in respective tables residing in the database. Projects Software Requirements: The system should demand only valid users (Users present in the user The client requires the Auto generation concept to be used in all the For the users logging into the system , performing updates, inserts, A new entry should be automatically created in the Master Table which

master database) who can gain entry into the System. master forms. deletions , gives the administrator visibility to all the users handling the system.

39

Project Category

Development of Project : This project is being developed on E-Mail Server. The first three phases(Feasibility Study, Requirement Gathering and Analysis) have been successfully completed and fourth (Design) is in progress. The details of the phases which have been completed are as follows : Feasibility Study : The feasibility study is used to determine if the project

should get the go-ahead. If the project is to proceed, the feasibility study will produce a project plan and budget estimates for the future stages of development. Therefore in our project we visited the concerned organization and made a rough overview of the time , cost , resources and technology which would be required to develop it and found that the project is feasible. Requirement Gathering : The requirement gathering phase aims at

collection of all requirements i.e. data which would be required in the development of the project.The data collection was done by visiting the organization frequently , holding meetings with the clients and collecting the pamphlets, brochures, snaps and other documents which contained essential and significant information about the school.

40

Analysis : Once a client starts discussing his requirements, the analyzers

will get into it and then perform the preliminary requirement analysis. The analysis would cover all the aspects especially on how the web site is going to join the existing system. Then, all the present hardware, software, people and data would be considered during the time of analysis .The analyzers would also do complete cost-benefit analysis and come up with a realistic plan. In this phase the output was the work plan, team requirements , hardware-software requirements , supporting documents and approval from the school to develop its project Design: Design focuses on high level design like, what programs are

needed and how are they going to interact, low-level design (how the individual programs are going to work), interface design (what are the interfaces going to look like) and data design (what data will be required). During these phases, the software's overall structure is defined. In this phase we have made DFD and E-R Diagram of our project and also designed the home page of our website . In addition to it three other forms have been designed and other are still in design process.

41

DFD For the Project

42

SYSTEM DESIGN PHASE

Design is an activity of translating the specifications generated in the software requirements analysis into specific design. The design involves designing a system that satisfies customer requirements. In order to transform requirements into a working system, we must satisfy both the customer and the system builders on development team. The customer understands what the system is to do. At the same time, the system builders must understand how the system is to work. For this reason, system design is really a two-part process. First, we produce a system specification that tells the customer exactly what the system will do. This specification is sometimes called a conceptual system design. This mirrors the two parts of requirement description. The conceptual design concentrates on the function of the system, while the technical design describes the form the system will take.

43

CONCEPTUAL DESIGN:
The conceptual design tells the customer what the system will do. The system is described in terms of its boundary, entities, attributes, and relationships. In the conceptual designing phase we have considered the following questions: Where will the data come from? What will happen to it in the system? What will the system look like to user? What choices will user be offered? What will the reports and screen look like?

Moreover, the system is described in language that the customer can understand, rather than in computer jargon and technical terms. For example, the customers of the system have been told that a menu on display screen will give users access to the system functions. The system description may even list acceptable user responses and the actions that may result. However, the customer is not told how the data are stored in the system or what kind of database management system is used for data manipulation. At the time of conceptual design, we have written in the clients language, which does not contain technicalities. It describes the functions of the systems and incorporates all requirements in adequate details.

44

TECHNICAL DESIGN:
The technical design explains the system to those hardware and software experts who will implement it. The design describes the hardware configuration, the software needs, the communication interfaces, the input and output of the system and anything else that translates the requirements into a solution to the customers problem. The design description is a technical picture of the system specification. Thus we include the following items in the technical design: The System Architecture: A description of the major hardware The System Software Structure: The hierarchy and function of the The data structure and flow through the system. components and their functions. software components.

45

DESIGN APPROACH:
Modular approach has been taken into consideration. A design is the determination of the modules and inters modular interfaces that satisfy a specified set of requirements. A design module is a functional entity with a well-defined set of inputs and outputs. Therefore, each module can be viewed as a component of the whole system, just as each room is a component of a house. A module is well defined if all the inputs to the module are essential to the function of the module and all outputs are produced by some action of the module. Thus if one input will be left out, the module will not perform its full function. There are no unnecessary inputs; every input is used in generating the output. Finally, the module is well defined only when each output is a result of the functioning of the module and when no input becomes an output without having the transformed in some way by the module. Modularity: Modularity is a characteristic of good system design. High level modules give us the opportunity to view the problem as whole and hide details that may distract us. By being able to reach down to a lower level for more detail when we want to, modularity provides the flexibility , trace the flow of data through the system, and target the pockets of complexity. These all are interrelated with each other and also self sufficient among themselves and help in running the system in an efficient and complete manner. Level of Abstraction: Abstraction an information hiding allows us to examine the way in which modules are related to one another in the overall design the degree to which the modules are independent of one another is a measure of how good the system design is. Independence is desirable for two reasons. First it is easier to understand how a module works if its function is not tied to others. It is much easier to modify a module if it is independent of others. Often a change in requirements or in a design decision means that certain modules must be modified. Each change affects data or function or both. If the 46

modules depend heavily on each other, a change to one module may mean changes module that are affected by the change. Coupling: Coupling is a measure of how modules depend on each other. Two modules are highly coupled if there is a great deal of dependence between them. Loosely couple modules have no interconnection at all. Coupling depends on several things The references made from one module to another. The amount of data passed from one module to another. The amount of control one module has over the other. The degree of complexity in the interface between one module and

another. Thus, coupling really represents a range of dependence, from complete dependence to complete independence. We want to minimize the dependence among modules for several reasons. First, if an element is affected by a system action, we always want to know which module causes an effect at a given time. Second, modularity helps in tracking the cause of the system errors. If an error occurs during the performance of particular function, independence of modules allows us to isolate the defective module more easily. Cohesion: Cohesion refers to the internal glue with which a module is constructed. The more cohesive a module, the more related are the internal parts of the module to each other and to the functionality of the module. In other words, a module is cohesive if all elements of the module are directed towards and essential for performing the same function. For example the various triggers written for the Subscription entry form are performing the functionality of the module like querying the old data, saving the new data, updating records etc. So its a highly cohesive system. Scope of control and effect: Finally we want to be sure that the modules in our design do not affect other modules over which they have the control. The modules controlled by the given module are collectively referred to as the

47

scope of effect. No module should be in scope of effect if it not in scope control. Thus in order to make the system easier to construct, test, correct, and maintain our goals had been: Low coupling of modules High cohesive modules Scope of effect of a module limited to its scope of control

It was decided to store data in different tables in SQL Server. The tables were normalized and various modules identified so as to store data properly create designed reports and on screen queries were written. A menu driven (user friendly) package has been designed containing understandable and presentable menus. Table structures are enclosed. Input and output details were made which are enclosed herewith.

The specifications in our design include User interface Design screens and their description Entity Relationship Diagrams

48

CODING

The coding step of the development phase translates the software design into a programming language that can be executed by a computer. CODING EFFICIENCY Efficiency means

How cryptic the coding is. Avoiding dead-code Remove unnecessary code and redundant processing Spend time documenting . Spend adequate time analyzing business requirements, process flows, Quality assurance is key: plan and execute a good test plan and testing

data-structures and data-model.

methodology.

49

A good way to see which code is more efficient is to compile is the code and generate the assembler code. See which one produces the most lines of code (LOC). The one with the least LOC is the one that is more efficient and will most probably run faster. Counting the number of lines of code tells you nothing. Many times the compiler will do optimizations that are intended to improve performance (speed) at the expense of space. How code efficiency is achieved in the project? We have made use of general procedures which we have used across a number of forms. The code written for the auto generation procedure is very efficient.

VERIFICATION & VALIDATION

Validation refers to the process of using software in a live environment using real data. The process of validation refers to a set of activities that ensure that the software that has been built is matching to customer requirement. Validation is successful when software functions in a manner that can be reasonably expected by the customer. Suitable validation checks have been put wherever need was felt so as to avoid wrong data input. Coding has been done so as to avoid wrong entries in the tables. For example Numeric characters are not allowed in the Students name. Various modules have different process logic, which involves sorting of data on different attributes and selection of required attribute depending upon conditions have been decided. Most of these are SQL queries.

50

Two types of V & V Verification: This checks if we are building the product right (i.e. does it meet the requirements specification?) Validation: This determines if we are building the right product? (i.e. does the requirement specification describe what the customer wants?) The various kinds of validations performed in our system are as follows: 1) Date Validation: The validation on date data type has been specified to be of the format DD/MM/YY. Any other format is unacceptable. 2) Amount Validation: There is a validation on amount that is entered in rupees in the following format. 00,000,000.00 E.g. 15,65,789.00 3) From Date to Date: The From Date always has to be less than the To Date, e.g. From 1 Nov, 2003 to 4 Nov, 2003 is correct and it cannot be other way round. 4) Number Field Validation: The field specified with Number as then their data-type will not accept Character or any other data type. 5) User Authentication: When a user logs on to the system to access data from the database, the password needs to be checked for user authentication. 6) Password change Validation: Only authorized users are allowed to change the password and the process requires asking the old password before changing it to the new one.

51

TESTING (TESTING TECHNIQUES AND TESTING STRATEGIES)

All software intended for public consumption should receive some level of testing. Without testing, you have no assurance that software will behave as expected. The results in public environment can be truly embarrassing. Testing is a critical element of software quality assurance and represents the ultimate review of specification, designing, and coding. Testing is done throughout the system development at various stages. If this is not done, then the poorly tested system can fail after installation. Testing is a very important part of SDLC and takes approximately 50%of the time. The first step in testing is developing a test plan based on the product requirements. The test plan is usually a formal document that ensures that the product meets the following standards: Is thoroughly Tested- Untested code adds an unknown element to the Meets product requirements- To meet customer needs, the product must Does not contain defects- Features must work within established quality product and increases the risk of product failure . provide the features and behavior described in the product specification. standards and those standards should be clearly stated within the test plan.

52

Testing Techniques
Black box Testing: aims to test a given programs behavior against its specification or component without making any reference to the internal structures of the program or the algorithms used. Therefore the source code is not needed, and so even purchased modules can be tested. We study the system by examining its inputs and related outputs. The key is to devise inputs that have a higher likelihood of causing outputs that reveal the presence of defects. We use experience and knowledge of the domain to identify such test cases. Failing this a systematic approach may be necessary. Equivalence partitioning is where the input to a program falls into a number of classes. e.g. positive numbers vs. negative numbers. Programs normally behave the same way for each member of a class. Partitions exist for both input and output. Partitions may be discrete or overlap. Invalid data (i.e. outside the normal partitions) is one for which partitions should be tested. Test cases are chosen to exercise each portion. Also test boundary cases (atypical, extreme, zero) should be considered since these frequently show up defects. For completeness, test all combinations of partitions. Black box testing is rarely exhaustive (because one doesn't test every value in an equivalence partition) and sometimes fails to reveal corruption defects caused by weird combination of inputs. Black box testing should not be used to try and reveal corruption defects caused, Example, by assigning a pointer to point to an object of the wrong type. Static inspection (or using a better programming language) is preferred.

53

White box Testing: was used as an important primary testing approach. Code is tested using code scripts, drivers, stubs, etc. which are employed to directly interface with it and drive the code. The tester can analyze the code and use the knowledge about the structure of a component to derive test data. This testing is based on the knowledge of structure of component (e.g. by looking at source code). The advantage is that structure of code can be used to find out how many test cases needed to be performed. Knowledge of the algorithm (examination of the code) can be used to identify the equivalence partitions. Path testing is where the tester aims to exercise every independent execution path through the component. All conditional statements tested for both true and false cases. If a unit has n control statements, there will be up to 2n possible paths through it. This demonstrates that it is much easier to test small program units than large ones. Flow graphs are a pictorial representation of the paths of control through a program (ignoring assignments, procedure calls and I/O statements). We use a flow graph to design test cases that execute each path. Static tools may be used to make this easier in programs that have a complex branching structure. Dynamic program analyzers instrument a program with additional code. Typically this will count how many times each statement is executed. At end, print out report showing which statements have and have not been executed. Possible methods: Usual method is to ensure that every line of code is executed at least once. Test capabilities rather than components (e.g. concentrate on tests for data loss over ones for screen layout). Test old in preference to new (users less affected by failure of new capabilities). Test typical cases rather than boundary ones (ensure normal operation works properly). Debugging:- Debugging is a cycle of detection, location, repair and test. Debugging is a hypothesis testing process. When a bug is detected, the tester must form a hypothesis about the cause and location of the bug. Further 54

examination of the execution of the program (possible including many returns of it) will usually take place to confirm the hypothesis. If the hypothesis is demonstrated to be incorrect, a new hypothesis must be formed. Debugging tools that show the state of the program are useful for this, but inserting print statements is often the only approach. Experienced debuggers use their knowledge of common and/or obscure bugs to facilitate the hypothesis testing process. After fixing a bug, the system must be reset to ensure that the fix has worked and that no other bugs have been introduced. In principle, all tests should be performed again but this is often too expensive to do. Testing Done in our System The best testing is to test each subsystem separately as we have done in our project. It is best to test a system during the implementation stage in form of small sub steps rather than large chunks. We have tested each module separately i.e. have completed unit testing first and system testing was done after combining /linking all different Modules with different menus and thorough testing was done. Once each lowest level unit has been tested, units are combined with related units and retested in combination. These proceeds hierarchically bottom-up until the entire system is tested as a whole. Hence we have used the Top Up approach for testing our system. Typical levels of testing in our system: Unit -procedure, function, method Module -package, abstract data type Sub-system - collection of related modules, method-message paths Acceptance Testing - whole system with real data (involve customer, user, etc) Beta Testing is acceptance testing with a single client. It is conducted at the developers site by a customer. The software is used in a natural setting with the developer looking over the shoulder of the user and recording errors and usage problems. Conducted in a controlled environment. Usually comes in after the completion of basic design of the program. The project guide who looks over the program or other knowledgeable officials may make 55

suggestions and give ideas to the designer for further improvement. They also report any minor or major problems and help in locating them and may further suggest ideas to get rid of them. Naturally a number of bugs are expected after the completion of a program and are most likely to be known to the developers only after the alpha testing. Involves distributing the system to potential customers to use and provide feedback. It is conducted at one or more customer sites by the end-user of the software. Unlike alpha testing, the developer is generally not present. Therefore, the beta test is a live application of the software in an environment that cannot be controlled by the developer. The customer records all problems (real or imagined) that are encountered during beta testing and reports these to the developer at regular intervals. As a result of problems reported during beta test, software engineers make modifications and then prepare for release of the software product to the entire customer base. In, this project, this exposes system to situations and errors that might not be anticipated by us.

56

EVALUATION
We have following approaches for the evaluation 1) Benchmarking- Comparing the performance of hardware and software. 2) Experience of other users- Vendors generally gives a list of users who are satisfied with their work. But it is advisable to seek the opinion independently. 3) Report of independent research organizationsMany research organizations undertake project of evaluating the proprietary software offered by various software agencies. They publish the report at regular interval. The prospective buyer of a software package can have faith in their evaluation. In our case we have evaluated our System and found that the hardware and software are in absolute sync with each other. Their performance has been found to be up to the mark. We also compared our software with HCL Total Organizer systems on other platforms and found that we were offering a much better system at a lesser price and on a more sophisticated and user friendly technology. Plus we offered complete maintenance and support for a certain period of time.

57

IMPLEMENTATION Implementation includes all those activities that take place to convert from old system to the new one. The new system may be completely new. Successful Implementation may not guarantee improvement in the organization using the new system, improper installation will prevent it. Implementation uses the design document to produce code. Demonstration that the program satisfies its specifications validates the code. Typically, sample runs of the program demonstrating the behavior for expected data values and boundary values are required. It may take several iterations of the model to produce a working program. As programs get more complicated, testing and debugging alone may not be enough to produce reliable code. Instead, we have to write programs in a manner that will help insure that errors are caught or avoided. Top-down implementation: Top down implementation begins with the user invoked module and works toward the modules that do not call any other modules. The implementation may proceed depth-first or breadth-first. Bottom- Up implementation: Implementation begins with modules that do not call any other modules and work toward the main program. Test harness is used to test individual modules. The main module constitutes the final test harness.

58

Stubs: Stub programming is the implementation analogue of top-down and stepwise refinement. It supports incremental program development by allowing for error and improvement. A stub program is a stripped-down, skeleton version of a final program. It doesn't implement details of the algorithm or fulfill all the job requirements. However, it does contain rough versions of all subprograms and their parameter lists. Furthermore, it can be compiled and run. Extensive use of procedures and parameter are the difference between stub programs and prototypes. Quick and dirty prototypes should be improved and rewritten. A stub program helps demonstrates that a program's structure is plausible. Its procedures and functions are unsophisticated versions of their final forms, but they allow limited use of the entire program. In particular, it may work for a limited data set. Often the high-level procedures are ready to call lower-level code, even if the more detailed subprograms haven't even been written. Our System was implemented at the client site in the following manner: 1) First of all we did a thorough system check on the clients machine in terms of hardware and software to ensure that there was enough space to load and run our application with ease. 2) Then we installed SQL Server Since the software was present on other systems and running properly, there wasnt much trouble in obtaining and installation. 3) Then came the process of Database Creation at the server site which involved the generation this procedure is also known as Database. 4) To establish contact with the server as per their requirement and each request should be implemented. This task actually is fairly crucial depending on the number of users trying to access the server at same time so a load test needs to be performed. 5) Finally came the job of training the users which meant that the clients were given instructions regarding the working of the system which included teaching

59

them the When the user was fully trained, he or she was asked to run the system independently and enter different sorts of data to test the system to its limits. 6) Our system not only met the user requirements but to certain extent exceeded in achieving much more then what was actually needed.

MAINTAINENCE

The maintenance starts after the final software product is delivered to the client. The maintenance phase identifies and implements the change associated with the correction of errors that may arise after the customer has started using the developed software. This also maintains the change associated with changes in the software environment and customer requirements. Once the system is a live one, Maintenance phase is important. Service after sale is a must and users/ clients must be helped after the system is implemented. If he/she faces any problem in using the system, one or two trained persons from

60

developers side can be deputed at the clients site, so as to avoid any problem and if any problem occurs immediate solution may be provided. The maintenance provided with our system after installation is as follows: First of all there was a Classification of Maintenance Plan which meant that the people involved in providing the after support were divided

SECURITY FEATURES
Authentication is the process of identifying users. Authorization is the process of granting access to users based on identity. Together, authentication and authorization provide the means to keep your application secure from intruders. The kind of security measures used in our System is as follows: User Authentication Only the Valid users, who are present in the pre defined list of Users stored in User Master Table, are granted permissions to enter the System. Any user apart from Record of User is denied access. User Authorization A privilege is a right to execute a particular type of SQL statement or to access Another users object. Some examples of privileges include the right to Connect to the database (create a session) Create a table Select rows from another users table Execute another users stored procedure

Privileges are granted to users so that they can accomplish tasks required for their jobs. A privilege should be granted only to a user who absolutely requires it to accomplish necessary task. Excessive granting can compromise security. A privilege can be granted in 2 ways: a) Grant privileges to users explicitly.

61

b) Grant privileges to a role (a named group of privileges), and then grant the role to one or more users. Because roles allow for easier and better management of privileges, you should normally grant privileges to roles and not to specific users. There are two distinct categories of privileges: System privileges Schema object privileges A system privilege is the right to perform a particular action, or to perform an action on any schema objects of a particular type. For example, the privileges to create table spaces and to delete the rows of any table in a database are system privileges. There are over 60 distinct system privileges. You can grant or revoke system privileges to users and roles. Only users who have been granted a specific system privilege with the ADMIN OPTION or users with the system privileges GRANT ANY PRIVILEGE or GRANT ANY OBJECT PRIVILEGE can grant or revoke system privileges to other users. We grant system privileges only to administrative personnel and application developers. End users normally do not require the associated capabilities. Schema Object Privileges A schema object privilege is a privilege or right to perform a particular action on a specific schema object: Table View Sequence Procedure Function Package

System Privileges

A user automatically has all object privileges for schema objects contained in his or

62

Her schema. A user can grant any object privilege on any schema object he or she Owns to any other user or role. Reduced privilege administration Rather than granting the same set of privileges explicitly to several users, you can grant the privileges for a group of related users to a role, and then only the role needs to be granted to each member of the group. Dynamic privilege management If the privileges of a group must change, only the privileges of the role need to be modified. The security domains of all users granted the groups role automatically reflect the changes made to the role. Any user granted a can grant or revoke that role to or From other users or roles of the database. This option allows administrative powers For roles on a selective basis. CREATE ROLE ADMIN_CONTROL; GRANT ADMIN_CONTROL TO ADMINISTRATOR; Table Level Security Schema object privileges for tables allow table security at the level of Data Manipulation Language and Data Definition Language operations. Data Manipulation Language Operations We can grant privileges to use the various DML statements like DELETE, INSERT, SELECT, and UPDATE to perform operations on a table or view. We grant these privileges only to users and roles that need to query or manipulate a tables data. With selective INSERT, a privileged user can insert a row with values for the Selected columns. All other columns receive NULL or the columns default value. With selective UPDATE, a user can update only specific column values of a row.

63

COST ESTIMATION
The cost estimation depends upon the following: Project complexity Project size Degree of structural uncertainty Human, technical, environmental, political can affect the ultimate cost of Delay estimation until late in the project. Base estimates on similar projects that have already been completed. Use relatively simple decomposition techniques to generate project cost Use one or more empirical models for software cost and effort estimation.

software and effort applied to develop it.

and effort estimates. Project complexity, project size and the degree of structural uncertainty all affect the reliability of estimates. For complex, custom systems, a large cost estimation error can make the difference between profit and loss. A model is based on experience and takes the form: D = f (Vi) Where d is one of a number of estimated values (e.g. effort, cost, project duration) and (Vi) are selected independent parameters (e.g. estimated LOC (Line of Code) or FP (Functional parameters)) New Hardware & Software: 64

Intel Pentium IV Processor Windows 2000 (Professional) SQL Server (Single User with 15 Licenses) DIFFERENT PHASES OF PROPOSED SOFTWARE DEVELOPMENT 1. 2. 3. 4. 5. 6. 7. 8. 9. System Study SRS (System Requirement Study) Documents and approval Advance Amount (50% of development charges + full cost of the Starting Of development (Interface Design and Approval) Development Presentation of New System User training. Implementation. Support.

software)

2nd partial development charges (Rest 50%).

10. Support for the futuristic changes. Price Quotation The process will start after the system study and with an advance amount of 50% from the corporate as advance. The rest in at the time of implementation. The project will approximately require 8 man months (8 person for 1 The development cost for this proposed software will be month) to be completed. Rs 11,500 (per man month) * 8 (man months) = Rs 92,000/Cost of original software (SQL Server) Rs 58,000 (approx.), (Developer 6i) Rs 18,000 (approx.) excluding 4% LST. Total: Rs 1, 68,000 (Excluding LST on Software)

**The above mentioned price includes free onsite maintenance for 3 months 65

starting from the day of final implementation and visit charges (that will be made while training and implementation of the project) as well as importing of the external / raw data from different data sources to the master database. *** Annual Maintenance of software (AMC) can be undertaken only after getting the consent from the concerned corporate / organization with proper documents only. ****AMC stands for Annual Maintenance Contract.

66

PERT / GANTT CHART

In order to ensure the success of a project, it is necessary for the team members involved in the project development and the customers to have a clear vision of the project goals and objectives. Once we have estimated of the effort and time requirement for the different phases a schedule for the project can be prepared. This schedule will then be used later for monitoring the progress of the project. Establishing a project vision offers the following advantages Clarification of Project goals Prioritizing of processes Integration with other products Basis for future planning Two general techniques of scheduling are Program evaluation and review technique (PERT) charts and Gantt charts The Gantt chart: is perhaps the simplest form of formal project management. Gantt chart (developed by Henry, L .Gantt) is a project control technique that can be used for several purposes, including scheduling and resource planning. It is a bar chart with each bar representing an activity. The bars are drawn against a time line. The length of each bar is proportional to the length of the time planned for the activity. It is used almost exclusively for scheduling purposes and therefore controls only the time dimension of projects. It helps in scheduling the activities of the project but not in identifying them. It is best for resource scheduling. It shows the tasks and their duration clearly, however do not show the intertasks dependencies plainly. A Gantt chart helps in scheduling the activities identified in the work break down structure. During the scheduling activity and also during implementation of the project, new activities may be identified that were not 67

envisioned during the initial planning. The manager must then go back and revise the break down structure and schedule to deal with these new activities. The Gantt chart in the figure is actually an enhanced version of standard Gantt charts. The white part of the bar shows the length of time each task is estimated to take. The black part shows the actual time, that is, the latest time by which a task is finished. Gantt charts can take different forms depending on their intended use. For resource scheduling. When a Bar chart is used as a project control method , milestones or check points usually are placed at the completion of each task (they may also placed within task). They indicate the completion of particular task and the project are on schedule; when a checkpoint is reached, the task just completed and the entire project are reviewed and evaluated. Reviewers ask where resources allocated have been properly utilized and indication of which task must be completed before others are begun and project costs must be accumulated and evaluated using other methods. Gantt chart uses a calendars oriented chart for representing the project schedule. Each activity is represented as a bar in the calendar starting from the starting date of the activity and ending at the ending date for that activity. The start & end of each activity become milestones for the project. The main drawback of the Gantt chart is that it doesnt depict the dependent relations among the different activities. Hence the effort of slippage in one activity on other activities or on the overall project schedule cannot be determined. However, it is conceptually simple & easy to understand, and is heavily used. It is sufficient for small & mediumsized projects.

68

The Gantt chart for my project made in the year 2009 is as follows: -

Stands for Planned Duration Stands for Actual Duration

69

FUTURE SCOPE OF THE PROJECT

1) Enhancement of our proposed system would be in terms of connectivity with the rest of the departments so that information is made available throughout the organization which leads to efficiency and speeding up of a number of processes. E.g. Finance dept. connected directly with main Database so that they could get information regarding fee. 2) Centralized Database in the main server could establish connections with each and every zonal head office via satellite communication. This would involve the concept of VSAT installed at each and every station communicating through WAN. 3) Online student register facility could be brought on to the Internet so as to automate the Subscription process to an large extend.

70

SNAPSHOTS OF THE PROJECT

71

HOME PAGE:-----------

72

73

INTERNET TECHNOLOGY:---

74

DESIGNERS PROFILE:----

75

FUTURE TECHNOLOGY PAGE:--

76

LOG IN PAGE:--77

78

USERS PROFILE:---

79

ADMINISTRATOR PAGE:--

80

COMPOSE MAIL PAGE:---

81

LOG IN PAGE:---

82

PICTURE UPLOAD PAGE:---

83

UPLOAD NEWS PAGE:---

BIBLIOGRAPHY 84

SQL Server Handbook by Ivan Bayross SQL Server Complete Reference from Oracle Press Microsoft MCTS Exam 70-526 VB.Net Black Book VB.Net Complete reference Google

85