08-10-2016, 11:46 AM
[attachment=72729]
ABSTRACT
It is a web based project. This contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
In this admin and user have knowledge on web usage. In this particular user must interact with the admin for booking the movie tickets. Communication must be transparent. The scope of this project is to develop a Web Based Movie World Project. The main scope of the project is to provide movie tickets to the users through web. In this user and admin have knowledge on web usage. In this particular user must interact with this project to buy or online booking of tickets. Communication must be transparent. This software is a web application. Internet programming is mostly used in this project.
Users must use internet/intranet for reaching this system. When we look at computer programs, they include databases, collection of programs which are related to finding optimal paths with algorithms, graphical user interface for visual projection.
INTRODUCTION
1. INTRODUCTION TO THE PROJECT :
It is a web based project. This contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
In this both user and admin have knowledge on web usage. In this particular user must interact with this project to get the movie tickets. Communication must be transparent. The scope of this project is to develop a Web Based Move World Project. The main scope of the project is to provide movie ticket services to the user through web. In this both user and admin share knowledge on web usage. Communication must be transparent. This software is a web application. Internet programming is mostly used in this project.
Users must use internet/intranet for reaching this system. When we look at computer programs, they include databases, collection of programs which are related to finding optimal paths with algorithms, graphical user interface for visual projection.
1.2. PURPOSE OF THE PROJECT
This document contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
SYSTEM ANALYSIS
2.1. INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.
2.2. ANALYSIS MODEL
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
1. The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
2. A preliminary design is created for the new system.
3. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
4. A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning a designing the second prototype.
4. Constructing and testing the second prototype.
5. At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
6. The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
7. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
8. The final system is constructed, based on the refined prototype.
9. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.
2.3. STUDY OF THE SYSTEM
In the flexibility of uses the interface has been developed a graphics concepts in mind, associated through a browser interface. The GUI’s at the top level has been categorized as follows
1. Administrative User Interface Design
2. The Operational and Generic User Interface Design
The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The Interface helps the administration with all the transactional states like data insertion, data deletion, and data updating along with executive data search capabilities.
The operational and generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.
NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the following modules:
The modules involved are:
1. Administrator module
2. User module
1. Administrator module:
This module maintains the information related to all the online booking move tickets that exist within the Business domain. This module integrates itself to the tickets module and the user module to maintain the proper integration and consistency that can arise necessary from time to time.
The Administrator is the super user of the system. He is the responsible person to define a theaters and tickets and amount of the movie tickets. He is updated the information regarding the details of the movie tickets.
2. Manager module:
This module is using this project. User want to go movie for that user went to theater and stand on queue some times tickets will be not available and some time times tickets will be over when ever tickets will be over the user time will be wasted and he don’t have time to go another move. So to that persons use this project means they enquire weather the tickets will be available or not if available means we have to book or we have to buy that movie tickets. This is the main concept of this module.
2.4. HARDWARE & SOFTWARE SPECIFICATIONS
HARDWARE REQUIREMENTS:
1. PIV 2.8 GHz Processor and Above
2. RAM 512MB and Above
3. HDD 10 GB Hard Disk Space and Above
SOFTWARE REQUIREMENTS:
1. Servers: IIS
2. Operating System Server: - Microsoft Windows XP/2000 or Higher
3. Data Base Server: Microsoft SQL Server 2005/2008
4. Clients: Microsoft Internet Explorer (Client Browser)
5. Development Tools: Microsoft Visual Studio .Net 2008/2010
6. Documentation Tools: MS Office 2007/2010
7. Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007
8. User Interface: ASP.NET With AJAX
9. Code Behind: VC#.NET
2.5 PROBLEMS IN EXISTING STSTEM
The existing system is manual and the manual system works in the following way:
1. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application.
2. It also touches on the performance and quality requirements of the application and provides a solid definition.
3. Provides services online to everyone. It hardly matters whether you live in a metro or in a remotely located village. Users can connect through their internet.
4. It is time consuming.
It also lists the limitations, assumptions and dependencies of the application. Section 3.0, the specific requirements section, includes the developers’ technical view of the client's expectation of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
Till now most companies has adopted the above manual system that produces lot of problems and at the same time the following disadvantages are there with the above system.
The increasing complexity, producing the reports as desired is not possible, and protracted time-scales of modern systems design and development have made working to a standardized system both essential and mandatory.
2.6. PROPOSED SYSTEM
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.
1. Provides services online to everyone.
2. I hardly matters whether you live in metro or in a remotely located village.
3. User can connect through a internet.
It is not limited to a single system because it is aimed to develop for web based environment
4. User friendliness (Graphical User Interface) is provided in the application.
5. Provide Interactive interface through which a user can interact with different areas of application easily.
6. The system makes the overall task much easier and flexible.
7. It can be accessed over the Internet/Intranet facilities.
8. There is no risk of data management at any level while the project development is under process.
9. Report generation feature is provided using ASP.Net Data Control like Grid View/Data List/Repeater/Form View to generate different kinds of reports easily using this application which is essential requirement now a day in any company.
10. It provides high level of security using session based Authentication.
11. It provides role based authentication to the different users like Administrator, Manager, Agent and Customers.
1. Deploy the application on a single system and make is available on all the systems within the network, thereby reducing the maintenance cost of software.
2.7. INPUT AND OUTPUT
The major inputs and outputs and major functions of the system are follows:
Inputs:
1. Admin enter his user id and password for login.
2. User enters his user id and password for login.
3. Admin just see the user details and movie and ticket details
4. Doctor views the patient request.
5. Give the solutions to that request
Outputs:
1. Admin can have his own home page.
2. Doctor enter their own home page.
3. Patient enter their own home page
4. Patient see the doctor availability
5. Send complaints to the admin
CHAPTER-3
FEASIBILITY REPORT
Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
1. Technical Feasibility
2. Operation Feasibility
3. Economical Feasibility
3.1. Technical Feasibility :
technical issue usually raised during the feasibility stage of the investigation includes the following:
1. Does the necessary technology exist to do what is suggested?
2. Do the proposed equipments have the technical capacity to hold the data required to use the new system?
3. Will the proposed system provide adequate response to inquiries, regardless of the number or location of users?
4. Can the system be upgraded if developed?
5. Are there technical guarantees of accuracy, reliability, ease of access and data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at ABC Tech. Thus it provides an easy access to the users. The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at ABC Tech or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.
3.2. Operational Feasibility :
Proposed projects are beneficial only if they can be turned out into information system.
project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -
1. Is there sufficient support for the management from the users?
2. Will the system be used and work properly if it is being developed and implemented?
3. Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.
3.3. Economic Feasibility :
A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at ABC Tech, There is nominal expenditure and economical feasibility for certain.
CHAPTER-4
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION :
This document is the complete product requirement specification for the Enterprise security service System. This is the only document that contains all information regarding the requirements placed on the Enterprise security service by the administrator, catalogued in an unambiguous fashion. Unless otherwise stated, this document, and any future revisions of this document, supersedes all other requirements documents that exist for the Enterprise security service.
Purpose :
The purpose of this Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in Enterprise security service. All parts; design, coding and testing will be prepared with helping of SRS. The purpose of this document is to detail the requirements placed on the Enterprise security service System and serves as a contract between the customer and the developers as to what is to be expected of the Enterprise security service, and how the components of the system are to work with each other with external systems.
This document will be checked by group member’s supervisor and it will corrected by members if supervisor orders.
Scope :
The scope of this project is to develop a Web Based virtual medical home Project. The main scope of the project is to provide medical services to the patients through web. In this both customers, agents and managers have knowledge on web usage. In this manager’s, agents and user’s have knowledge on web usage. In this particular application agents must interact with the customers to recover from their problems. Communication must be transparent.
DEVELOPERS RESPONSIBILITIES OVERVIEW:
The developer is responsible for:
Developing the system, which meets solving all the requirements of the system?
1. Demonstrating the system and installing the system at client's location after the acceptance testing is successful.
2. Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
3. Conducting any user training that might be needed for using the system.
4. Maintaining the system for a period of one year after installation.
4.1FUNCTIONAL REQUIREMENTS :
The general description gives an executive overview and is very client-oriented. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application the specific requirements section, includes the developers’ technical view of the client's expectation of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
1. In this particular application customer must interact with the agent to join into new policies and to enquire about any new policies.
2. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives.
3. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
In this Manager and Agent and Customers have knowledge on web usage. In this particular application Agent must interact with the customer to recover from their problems. Communication must be transparent.
The normal user (i.e. unregistered user) should be able to view the catalog and contact information about voters of a particular region.
4.2. NON-FUNCTIONAL REQUIREMENTS :
The system should be web-based system. Users should use the system via internet. Each user should have a user account. The system should ask the username and password to users. It doesn’t permit to unregistered user to access for Enterprise security service. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation.
These are the mainly following:
1. Secure access of confidential data (user’s details). SSL (Secure Sockets Layer) can be used.
2. 24 X 7 availability
3. Better component design to get better performance at peak time
4. Flexible service based architecture will be highly desirable for future extension
Following are the some of requirements of our system
Performance :
They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule.
Security :
It provides more security by setting username and password.
Safety :
This application provides more safety to the users for accessing the databases and for performing the operations on the databases.
Interfaces:
It provides the interface for accessing the database and also allows the user to do the manipulations on the databases.
Reliability:
This entire project is depends on the SQL Server.
Accuracy:
Since the same table is created at different users account, the
Possibility of retrieving data wrongly increases. Also if the data is more,
Validations become difficult. This may result in loss of accuracy of data.
Ease of Use:
Ever user should be comfortable of working with computer and internet browsing. He must have basic knowledge of English.
Interoperability:
This provides the import and export facilities for sending one database to another database.
Maintainability:
The key to reducing need for maintenance, while working, if possible to do essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documentation.
3. Using more effective methods for designing, processing, login and communicating information with project team members.
4. Making better use of existing tools and techniques.
5. Managing system engineering process effectively.
Testability:
Testing is done in various ways such as testing the algorithm, programming code; sample data debugging is also one of following the above testing
4.3. PERFORMANCE REQUIREMENTS:
Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
1. The system should be able to interface with the existing system
2. The system should be accurate
1. The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
INTRODUCTION TO .NET FRAMEWORK :
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:
1. To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
2. To provide a code-execution environment that minimizes software deployment and versioning conflicts.
3. To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
4. To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
5. To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
6. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and Remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts.
For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code (similar to Microsoft® ActiveX® controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and secure isolated file storage.
FEATURES OF THE COMMON LANGUAGE RUN TIME :
The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application.
The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally featuring rich.
The runtime also enforces code robustness by implementing a strict type- and code-verification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers
Generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety.
In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications.
While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs.
The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance.
Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.
5.2 .NET FRAMEWORK CLASS LIBRARY:
The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is objecting oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services:
1. Console applications.
2. Scripted or hosted applications.
3. Windows GUI applications (Windows Forms).
4. ASP.NET applications.
5. XML Web services.
6. Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes.
CLIENT APPLICATION DEVELOPMENT :
Client applications are the closest to a traditional style of application in Windows-based programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products into a single, consistent development environment that drastically simplifies the development of client applications.
The Windows Forms classes contained in the .NET Framework are designed to be used for GUI development. You can easily create command windows, buttons, menus, toolbars, and other screen elements with the flexibility necessary to accommodate shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is one of many ways in which the .NET Framework integrates the developer interface, making coding simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer. This means that binary or natively executing code can access some of the resources on the user's system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user's system can now be safely deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page.
LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and JScripts.
5.3 C#.NET :
C#.NET .NET has many new and improved language features such as inheritance, interfaces, and overloading — that make it a powerful object-oriented programming language. As a C#.NET developer, you can now create multithreaded, scalable applications using explicit multithreading. Other new language features in C#.NET .NET include structured exception handling, custom attributes, and common language specification (CLS) compliance.
The CLS is a set of rules that standardizes such things as data types and how objects are exposed and interoperate. C#.NET .NET adds several features that take advantage of the CLS. Any CLS-compliant language can use the classes, objects, and components you create in C#.NET .NET. And you, as a C#.NET user, can access classes, components, and objects from other CLS-compliant programming languages without worrying about language-specific differences such as data types. CLS features used by C#.NET .NET programs include assemblies, namespaces, and attributes.
C#.NET .NET supports many new or improved object-oriented language features such inheritance, overloading, the Overrides keyword, interfaces, shared members, and constructors. Also included are structured exception handling, delegates, and several new data types.
.
INHERITANCE :
C#.NET .NET supports inheritance by allowing you to define classes that serve as the basis for derived classes. Derived classes inherit and can extend the properties and methods of the base class. They can also override inherited methods with new implementations. All classes created with C#.NET .NET are inheritable by default. Because the forms you design are really classes, you can use inheritance to define new forms based on existing ones.
EXCEPTION HANDLING :
C#.NET .NET supports structured exception handling, using an enhanced version of the Try...Catch...Finally syntax supported by other languages such as C++. Structured exception handling combines a modern control structure (similar to Select Case or While) with exceptions, protected blocks of code, and filters. Structured exception handling makes it easy to create and maintain programs with robust, comprehensive error handlers.
OVERLOADING :
Overloading is the ability to define properties, methods, or procedures that have the same name but use different data types. Overloaded procedures allow you to provide as many implementations as necessary to handle different kinds of data, while giving the appearance of a single, versatile procedure.
OVERRIDING PROPERTIES AND METHODS :
The Overrides keyword allows derived objects to override characteristics inherited from parent objects. Overridden members have the same arguments as the members inherited from the base class, but different implementations. A member's new implementation can call the original implementation in the parent class by preceding the member name with My Base.
CONSTRUCTORS AND DESTRUCTORS :
Constructors are procedures that control initialization of new instances of a class. Conversely, destructors are methods that free system resources when a class leaves scope or is set to nothing. C#.NET .NET supports constructors and destructors using the Sub New and Sub Finalize procedures. For details, see Object Lifetime: How Objects are Created and Destroyed.
DATA TYPES :
C#.NET .NET introduces three new data types. The Char data type is an unsigned 16-bit quantity used to store Unicode characters. It is equivalent to the .NET Framework System. Char data type. The Short data type, a signed 16-bit integer, was named Integer in earlier versions of C#.NET. The Decimal data type is a 96-bit signed integer scaled by a variable power of 10. In earlier versions of C#.NET, it was available only within a Variant.
INTERFACES :
Interfaces describe the properties and methods of classes, but unlike classes, do not provide implementations. The Interface statement allows you to declare interfaces, while the Implements statement lets you write code that puts the items described in the interface into practice.
DELEGATES :
Delegates — objects that can call the methods of objects on your behalf — are sometimes described as type-safe, object-oriented function pointers. You can use delegates to let procedures specify an event handler method that runs when an event occurs. You can also use delegates with multithreaded applications.
SHARED MEMBERS :
Shared members are properties, procedures, and fields that are shared by all instances of a class. Shared data members are useful when multiple objects need to use information that is common to all. Shared class methods can be used without first creating an object from a class.
REFERENCES :
References allow you to use objects defined in other assemblies. In C#.NET .NET, references point to assemblies instead of type libraries.
NAMESPACES :
Namespaces prevent naming conflicts by organizing classes, interfaces, and methods into hierarchies.
ASSEMBLIES :
Assemblies replace and extend the capabilities of type libraries by, describing all the required files for a particular component or application. An assembly can contain one or more namespaces.
ATTRIBUTES :
Attributes enable you to provide additional information about program elements. For example, you can use an attribute to specify which methods in a class should be exposed when the class is used as a XML Web service.
MULTITHREADING :
C#.NET .NET allows you to write applications that can perform multiple tasks independently. A task that has the potential of holding up other tasks can execute on a separate thread, a process known as multithreading. By causing complicated tasks to run on threads that are separate from your user interface, multithreading makes your applications more responsive to user input.
ADO.NET :
As you develop applications using ADO.NET, you will have different requirements for working with data. In some cases, you might simply want to display data on a form. In other cases, you might need to devise a way to share information with another company.
No matter what you do with data, there are certain fundamental concepts that you should understand about the data approach in ADO.NET. You might never need to know some of the details of data handling — for example, you might never need to directly edit an XML file containing data — but it is very useful to understand the data architecture in ADO.NET, what the major data components are, and how the pieces fit together.
This introduction presents a high-level overview of these most important concepts. The topic deliberately skips over many details — for example, there is much more to datasets than what is mentioned here — in favor of simply introducing you to ideas behind data integration in ADO.NET.
ADO.NET Does Not Depend on Continuously Live Connections In traditional client/server applications, components establish a connection to a database and keep it open while the application is running. For a variety of reasons, this approach is impractical in many applications.
Open database connections take up valuable system resources. In most cases, databases can maintain only a small number of concurrent connections. The overhead of maintaining these connections detracts from overall application performance.
Similarly, applications that require an open database connection are extremely difficult to scale up. An application that does not scale up well might perform acceptably with four users but will likely not do so with hundreds. ASP.NET Web applications in particular need to be easily scalable, because traffic to a Web site can go up by orders of magnitude in a very short period.
A model based on always-connected data can make it difficult and impractical to exchange data across application and organizational boundaries using a connected architecture. If two components need to share the same data, both have to be connected, and a way must be devised for the components to pass data back and forth.
For all these reasons, data access with ADO.NET is designed around an architecture that uses connections sparingly. Applications are connected to the database only long enough to fetch or update the data. Because the database is not holding on to connections that are largely idle, it can service many more users.
ABSTRACT
It is a web based project. This contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
In this admin and user have knowledge on web usage. In this particular user must interact with the admin for booking the movie tickets. Communication must be transparent. The scope of this project is to develop a Web Based Movie World Project. The main scope of the project is to provide movie tickets to the users through web. In this user and admin have knowledge on web usage. In this particular user must interact with this project to buy or online booking of tickets. Communication must be transparent. This software is a web application. Internet programming is mostly used in this project.
Users must use internet/intranet for reaching this system. When we look at computer programs, they include databases, collection of programs which are related to finding optimal paths with algorithms, graphical user interface for visual projection.
INTRODUCTION
1. INTRODUCTION TO THE PROJECT :
It is a web based project. This contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
In this both user and admin have knowledge on web usage. In this particular user must interact with this project to get the movie tickets. Communication must be transparent. The scope of this project is to develop a Web Based Move World Project. The main scope of the project is to provide movie ticket services to the user through web. In this both user and admin share knowledge on web usage. Communication must be transparent. This software is a web application. Internet programming is mostly used in this project.
Users must use internet/intranet for reaching this system. When we look at computer programs, they include databases, collection of programs which are related to finding optimal paths with algorithms, graphical user interface for visual projection.
1.2. PURPOSE OF THE PROJECT
This document contains a description for “Movie World” enhancement. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives. The SRS will serve as a guide for the client and the developers.
SYSTEM ANALYSIS
2.1. INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution.
2.2. ANALYSIS MODEL
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement. This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
As originally envisioned, the iterations were typically 6 months to 2 years long. Each phase starts with a design goal and ends with a client reviewing the progress thus far. Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
1. The new system requirements are defined in as much details as possible. This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
2. A preliminary design is created for the new system.
3. A first prototype of the new system is constructed from the preliminary design. This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
4. A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning a designing the second prototype.
4. Constructing and testing the second prototype.
5. At the customer option, the entire project can be aborted if the risk is deemed too great. Risk factors might involve development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
6. The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
7. The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
8. The final system is constructed, based on the refined prototype.
9. The final system is thoroughly evaluated and tested. Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.
2.3. STUDY OF THE SYSTEM
In the flexibility of uses the interface has been developed a graphics concepts in mind, associated through a browser interface. The GUI’s at the top level has been categorized as follows
1. Administrative User Interface Design
2. The Operational and Generic User Interface Design
The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The Interface helps the administration with all the transactional states like data insertion, data deletion, and data updating along with executive data search capabilities.
The operational and generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.
NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the following modules:
The modules involved are:
1. Administrator module
2. User module
1. Administrator module:
This module maintains the information related to all the online booking move tickets that exist within the Business domain. This module integrates itself to the tickets module and the user module to maintain the proper integration and consistency that can arise necessary from time to time.
The Administrator is the super user of the system. He is the responsible person to define a theaters and tickets and amount of the movie tickets. He is updated the information regarding the details of the movie tickets.
2. Manager module:
This module is using this project. User want to go movie for that user went to theater and stand on queue some times tickets will be not available and some time times tickets will be over when ever tickets will be over the user time will be wasted and he don’t have time to go another move. So to that persons use this project means they enquire weather the tickets will be available or not if available means we have to book or we have to buy that movie tickets. This is the main concept of this module.
2.4. HARDWARE & SOFTWARE SPECIFICATIONS
HARDWARE REQUIREMENTS:
1. PIV 2.8 GHz Processor and Above
2. RAM 512MB and Above
3. HDD 10 GB Hard Disk Space and Above
SOFTWARE REQUIREMENTS:
1. Servers: IIS
2. Operating System Server: - Microsoft Windows XP/2000 or Higher
3. Data Base Server: Microsoft SQL Server 2005/2008
4. Clients: Microsoft Internet Explorer (Client Browser)
5. Development Tools: Microsoft Visual Studio .Net 2008/2010
6. Documentation Tools: MS Office 2007/2010
7. Drawing Tools: IBM Rational Rose Enterprise, MS Office Visio 2007
8. User Interface: ASP.NET With AJAX
9. Code Behind: VC#.NET
2.5 PROBLEMS IN EXISTING STSTEM
The existing system is manual and the manual system works in the following way:
1. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application.
2. It also touches on the performance and quality requirements of the application and provides a solid definition.
3. Provides services online to everyone. It hardly matters whether you live in a metro or in a remotely located village. Users can connect through their internet.
4. It is time consuming.
It also lists the limitations, assumptions and dependencies of the application. Section 3.0, the specific requirements section, includes the developers’ technical view of the client's expectation of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
Till now most companies has adopted the above manual system that produces lot of problems and at the same time the following disadvantages are there with the above system.
The increasing complexity, producing the reports as desired is not possible, and protracted time-scales of modern systems design and development have made working to a standardized system both essential and mandatory.
2.6. PROPOSED SYSTEM
To overcome all the difficulties of the existing system the management has proposed automated the whole system and the development of the new automated system contains the following activities, which try to automate the entire process keeping in view of the database integration approach.
1. Provides services online to everyone.
2. I hardly matters whether you live in metro or in a remotely located village.
3. User can connect through a internet.
It is not limited to a single system because it is aimed to develop for web based environment
4. User friendliness (Graphical User Interface) is provided in the application.
5. Provide Interactive interface through which a user can interact with different areas of application easily.
6. The system makes the overall task much easier and flexible.
7. It can be accessed over the Internet/Intranet facilities.
8. There is no risk of data management at any level while the project development is under process.
9. Report generation feature is provided using ASP.Net Data Control like Grid View/Data List/Repeater/Form View to generate different kinds of reports easily using this application which is essential requirement now a day in any company.
10. It provides high level of security using session based Authentication.
11. It provides role based authentication to the different users like Administrator, Manager, Agent and Customers.
1. Deploy the application on a single system and make is available on all the systems within the network, thereby reducing the maintenance cost of software.
2.7. INPUT AND OUTPUT
The major inputs and outputs and major functions of the system are follows:
Inputs:
1. Admin enter his user id and password for login.
2. User enters his user id and password for login.
3. Admin just see the user details and movie and ticket details
4. Doctor views the patient request.
5. Give the solutions to that request
Outputs:
1. Admin can have his own home page.
2. Doctor enter their own home page.
3. Patient enter their own home page
4. Patient see the doctor availability
5. Send complaints to the admin
CHAPTER-3
FEASIBILITY REPORT
Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. The main objective of the feasibility study is to test the Technical, Operational and Economical feasibility for adding new modules and debugging old running system. All system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation:
1. Technical Feasibility
2. Operation Feasibility
3. Economical Feasibility
3.1. Technical Feasibility :
technical issue usually raised during the feasibility stage of the investigation includes the following:
1. Does the necessary technology exist to do what is suggested?
2. Do the proposed equipments have the technical capacity to hold the data required to use the new system?
3. Will the proposed system provide adequate response to inquiries, regardless of the number or location of users?
4. Can the system be upgraded if developed?
5. Are there technical guarantees of accuracy, reliability, ease of access and data security?
Earlier no system existed to cater to the needs of ‘Secure Infrastructure Implementation System’. The current system developed is technically feasible. It is a web based user interface for audit workflow at ABC Tech. Thus it provides an easy access to the users. The database’s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. Permission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard requirements for the development of this project are not many and are already available in-house at ABC Tech or are available as free as open source. The work for the project is done with the current equipment and existing software technology. Necessary bandwidth exists for providing a fast feedback to the users irrespective of the number of users using the system.
3.2. Operational Feasibility :
Proposed projects are beneficial only if they can be turned out into information system.
project are to be taken as an important part of the project implementation. Some of the important issues raised are to test the operational feasibility of a project includes the following: -
1. Is there sufficient support for the management from the users?
2. Will the system be used and work properly if it is being developed and implemented?
3. Will there be any resistance from the user that will undermine the possible application benefits?
This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the management issues and user requirements have been taken into consideration. So there is no question of resistance from the users that can undermine the possible application benefits.
The well-planned design would ensure the optimal utilization of the computer resources and would help in the improvement of performance status.
3.3. Economic Feasibility :
A system can be developed technically and that will be used if installed must still be a good investment for the organization. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. Financial benefits must equal or exceed the costs.
The system is economically feasible. It does not require any addition hardware or software. Since the interface for this system is developed using the existing resources and technologies available at ABC Tech, There is nominal expenditure and economical feasibility for certain.
CHAPTER-4
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION :
This document is the complete product requirement specification for the Enterprise security service System. This is the only document that contains all information regarding the requirements placed on the Enterprise security service by the administrator, catalogued in an unambiguous fashion. Unless otherwise stated, this document, and any future revisions of this document, supersedes all other requirements documents that exist for the Enterprise security service.
Purpose :
The purpose of this Software Requirement Specification (SRS) is to help the project. It is provided with some requirements which are used in Enterprise security service. All parts; design, coding and testing will be prepared with helping of SRS. The purpose of this document is to detail the requirements placed on the Enterprise security service System and serves as a contract between the customer and the developers as to what is to be expected of the Enterprise security service, and how the components of the system are to work with each other with external systems.
This document will be checked by group member’s supervisor and it will corrected by members if supervisor orders.
Scope :
The scope of this project is to develop a Web Based virtual medical home Project. The main scope of the project is to provide medical services to the patients through web. In this both customers, agents and managers have knowledge on web usage. In this manager’s, agents and user’s have knowledge on web usage. In this particular application agents must interact with the customers to recover from their problems. Communication must be transparent.
DEVELOPERS RESPONSIBILITIES OVERVIEW:
The developer is responsible for:
Developing the system, which meets solving all the requirements of the system?
1. Demonstrating the system and installing the system at client's location after the acceptance testing is successful.
2. Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.
3. Conducting any user training that might be needed for using the system.
4. Maintaining the system for a period of one year after installation.
4.1FUNCTIONAL REQUIREMENTS :
The general description gives an executive overview and is very client-oriented. It expounds on the functional and data requirements of the application. It also lists the limitations, assumptions and dependencies of the application the specific requirements section, includes the developers’ technical view of the client's expectation of the application. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
1. In this particular application customer must interact with the agent to join into new policies and to enquire about any new policies.
2. This document will contain the functional requirements of the project and how the developers will enhance the project to achieve all the objectives.
3. It also touches on the performance and quality requirements of the application and provides a solid definition of the interface.
In this Manager and Agent and Customers have knowledge on web usage. In this particular application Agent must interact with the customer to recover from their problems. Communication must be transparent.
The normal user (i.e. unregistered user) should be able to view the catalog and contact information about voters of a particular region.
4.2. NON-FUNCTIONAL REQUIREMENTS :
The system should be web-based system. Users should use the system via internet. Each user should have a user account. The system should ask the username and password to users. It doesn’t permit to unregistered user to access for Enterprise security service. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation.
These are the mainly following:
1. Secure access of confidential data (user’s details). SSL (Secure Sockets Layer) can be used.
2. 24 X 7 availability
3. Better component design to get better performance at peak time
4. Flexible service based architecture will be highly desirable for future extension
Following are the some of requirements of our system
Performance :
They understand the importance of timing, of getting there before the competition. A rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. Our track record is testimony to complex projects delivered within and evens before schedule.
Security :
It provides more security by setting username and password.
Safety :
This application provides more safety to the users for accessing the databases and for performing the operations on the databases.
Interfaces:
It provides the interface for accessing the database and also allows the user to do the manipulations on the databases.
Reliability:
This entire project is depends on the SQL Server.
Accuracy:
Since the same table is created at different users account, the
Possibility of retrieving data wrongly increases. Also if the data is more,
Validations become difficult. This may result in loss of accuracy of data.
Ease of Use:
Ever user should be comfortable of working with computer and internet browsing. He must have basic knowledge of English.
Interoperability:
This provides the import and export facilities for sending one database to another database.
Maintainability:
The key to reducing need for maintenance, while working, if possible to do essential tasks.
1. More accurately defining user requirement during system development.
2. Assembling better systems documentation.
3. Using more effective methods for designing, processing, login and communicating information with project team members.
4. Making better use of existing tools and techniques.
5. Managing system engineering process effectively.
Testability:
Testing is done in various ways such as testing the algorithm, programming code; sample data debugging is also one of following the above testing
4.3. PERFORMANCE REQUIREMENTS:
Performance is measured in terms of the output provided by the application.
Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.
The requirement specification for any system can be broadly stated as given below:
1. The system should be able to interface with the existing system
2. The system should be accurate
1. The system should be better than the existing system
The existing system is completely dependent on the user to perform all the duties.
INTRODUCTION TO .NET FRAMEWORK :
The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:
1. To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
2. To provide a code-execution environment that minimizes software deployment and versioning conflicts.
3. To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
4. To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
5. To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.
6. To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.
The .NET Framework has two main components: the common language runtime and the .NET Framework class library. The common language runtime is the foundation of the .NET Framework. You can think of the runtime as an agent that manages code at execution time, providing core services such as memory management, thread management, and Remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. Code that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .NET Framework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface (GUI) applications to applications based on the latest innovations provided by ASP.NET, such as Web Forms and XML Web services.
The .NET Framework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the execution of managed code, thereby creating a software environment that can exploit both managed and unmanaged features. The .NET Framework not only provides several runtime hosts, but also supports the development of third-party runtime hosts.
For example, ASP.NET hosts the runtime to provide a scalable, server-side environment for managed code. ASP.NET works directly with the runtime to enable Web Forms applications and XML Web services, both of which are discussed later in this topic.
Internet Explorer is an example of an unmanaged application that hosts the runtime (in the form of a MIME type extension). Using Internet Explorer to host the runtime enables you to embed managed components or Windows Forms controls in HTML documents. Hosting the runtime in this way makes managed mobile code (similar to Microsoft® ActiveX® controls) possible, but with significant improvements that only managed code can offer, such as semi-trusted execution and secure isolated file storage.
FEATURES OF THE COMMON LANGUAGE RUN TIME :
The common language runtime manages memory, thread execution, code execution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime.
With regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin (such as the Internet, enterprise network, or local computer). This means that a managed component might or might not be able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application.
The runtime enforces code access security. For example, users can trust that an executable embedded in a Web page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be exceptionally featuring rich.
The runtime also enforces code robustness by implementing a strict type- and code-verification infrastructure called the common type system (CTS). The CTS ensures that all managed code is self-describing. The various Microsoft and third-party language compilers
Generate managed code that conforms to the CTS. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety.
In addition, the managed environment of the runtime eliminates many common software issues. For example, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references.
The runtime also accelerates developer productivity. For example, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. Any compiler vendor who chooses to target the runtime can do so. Language compilers that target the .NET Framework make the features of the .NET Framework available to existing code written in that language, greatly easing the migration process for existing applications.
While the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary COM components and DLLs.
The runtime is designed to enhance performance. Although the common language runtime provides many standard runtime services, managed code is never interpreted. A feature called just-in-time (JIT) compiling enables all managed code to run in the native machine language of the system on which it is executing. Meanwhile, the memory manager removes the possibilities of fragmented memory and increases memory locality-of-reference to further increase performance.
Finally, the runtime can be hosted by high-performance, server-side applications, such as Microsoft® SQL Server™ and Internet Information Services (IIS). This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industry's best enterprise servers that support runtime hosting.
5.2 .NET FRAMEWORK CLASS LIBRARY:
The .NET Framework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is objecting oriented, providing types from which your own managed code can derive functionality. This not only makes the .NET Framework types easy to use, but also reduces the time associated with learning new features of the .NET Framework. In addition, third-party components can integrate seamlessly with classes in the .NET Framework.
For example, the .NET Framework collection classes implement a set of interfaces that you can use to develop your own collection classes. Your collection classes will blend seamlessly with the classes in the .NET Framework.
As you would expect from an object-oriented class library, the .NET Framework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of specialized development scenarios. For example, you can use the .NET Framework to develop the following types of applications and services:
1. Console applications.
2. Scripted or hosted applications.
3. Windows GUI applications (Windows Forms).
4. ASP.NET applications.
5. XML Web services.
6. Windows services.
For example, the Windows Forms classes are a comprehensive set of reusable types that vastly simplify Windows GUI development. If you write an ASP.NET Web Form application, you can use the Web Forms classes.
CLIENT APPLICATION DEVELOPMENT :
Client applications are the closest to a traditional style of application in Windows-based programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers.
Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.
In the past, developers created such applications using C/C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products into a single, consistent development environment that drastically simplifies the development of client applications.
The Windows Forms classes contained in the .NET Framework are designed to be used for GUI development. You can easily create command windows, buttons, menus, toolbars, and other screen elements with the flexibility necessary to accommodate shifting business needs.
For example, the .NET Framework provides simple properties to adjust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is one of many ways in which the .NET Framework integrates the developer interface, making coding simpler and more consistent.
Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user's computer. This means that binary or natively executing code can access some of the resources on the user's system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user's system can now be safely deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page.
LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#, Visual Basic, and JScripts.
5.3 C#.NET :
C#.NET .NET has many new and improved language features such as inheritance, interfaces, and overloading — that make it a powerful object-oriented programming language. As a C#.NET developer, you can now create multithreaded, scalable applications using explicit multithreading. Other new language features in C#.NET .NET include structured exception handling, custom attributes, and common language specification (CLS) compliance.
The CLS is a set of rules that standardizes such things as data types and how objects are exposed and interoperate. C#.NET .NET adds several features that take advantage of the CLS. Any CLS-compliant language can use the classes, objects, and components you create in C#.NET .NET. And you, as a C#.NET user, can access classes, components, and objects from other CLS-compliant programming languages without worrying about language-specific differences such as data types. CLS features used by C#.NET .NET programs include assemblies, namespaces, and attributes.
C#.NET .NET supports many new or improved object-oriented language features such inheritance, overloading, the Overrides keyword, interfaces, shared members, and constructors. Also included are structured exception handling, delegates, and several new data types.
.
INHERITANCE :
C#.NET .NET supports inheritance by allowing you to define classes that serve as the basis for derived classes. Derived classes inherit and can extend the properties and methods of the base class. They can also override inherited methods with new implementations. All classes created with C#.NET .NET are inheritable by default. Because the forms you design are really classes, you can use inheritance to define new forms based on existing ones.
EXCEPTION HANDLING :
C#.NET .NET supports structured exception handling, using an enhanced version of the Try...Catch...Finally syntax supported by other languages such as C++. Structured exception handling combines a modern control structure (similar to Select Case or While) with exceptions, protected blocks of code, and filters. Structured exception handling makes it easy to create and maintain programs with robust, comprehensive error handlers.
OVERLOADING :
Overloading is the ability to define properties, methods, or procedures that have the same name but use different data types. Overloaded procedures allow you to provide as many implementations as necessary to handle different kinds of data, while giving the appearance of a single, versatile procedure.
OVERRIDING PROPERTIES AND METHODS :
The Overrides keyword allows derived objects to override characteristics inherited from parent objects. Overridden members have the same arguments as the members inherited from the base class, but different implementations. A member's new implementation can call the original implementation in the parent class by preceding the member name with My Base.
CONSTRUCTORS AND DESTRUCTORS :
Constructors are procedures that control initialization of new instances of a class. Conversely, destructors are methods that free system resources when a class leaves scope or is set to nothing. C#.NET .NET supports constructors and destructors using the Sub New and Sub Finalize procedures. For details, see Object Lifetime: How Objects are Created and Destroyed.
DATA TYPES :
C#.NET .NET introduces three new data types. The Char data type is an unsigned 16-bit quantity used to store Unicode characters. It is equivalent to the .NET Framework System. Char data type. The Short data type, a signed 16-bit integer, was named Integer in earlier versions of C#.NET. The Decimal data type is a 96-bit signed integer scaled by a variable power of 10. In earlier versions of C#.NET, it was available only within a Variant.
INTERFACES :
Interfaces describe the properties and methods of classes, but unlike classes, do not provide implementations. The Interface statement allows you to declare interfaces, while the Implements statement lets you write code that puts the items described in the interface into practice.
DELEGATES :
Delegates — objects that can call the methods of objects on your behalf — are sometimes described as type-safe, object-oriented function pointers. You can use delegates to let procedures specify an event handler method that runs when an event occurs. You can also use delegates with multithreaded applications.
SHARED MEMBERS :
Shared members are properties, procedures, and fields that are shared by all instances of a class. Shared data members are useful when multiple objects need to use information that is common to all. Shared class methods can be used without first creating an object from a class.
REFERENCES :
References allow you to use objects defined in other assemblies. In C#.NET .NET, references point to assemblies instead of type libraries.
NAMESPACES :
Namespaces prevent naming conflicts by organizing classes, interfaces, and methods into hierarchies.
ASSEMBLIES :
Assemblies replace and extend the capabilities of type libraries by, describing all the required files for a particular component or application. An assembly can contain one or more namespaces.
ATTRIBUTES :
Attributes enable you to provide additional information about program elements. For example, you can use an attribute to specify which methods in a class should be exposed when the class is used as a XML Web service.
MULTITHREADING :
C#.NET .NET allows you to write applications that can perform multiple tasks independently. A task that has the potential of holding up other tasks can execute on a separate thread, a process known as multithreading. By causing complicated tasks to run on threads that are separate from your user interface, multithreading makes your applications more responsive to user input.
ADO.NET :
As you develop applications using ADO.NET, you will have different requirements for working with data. In some cases, you might simply want to display data on a form. In other cases, you might need to devise a way to share information with another company.
No matter what you do with data, there are certain fundamental concepts that you should understand about the data approach in ADO.NET. You might never need to know some of the details of data handling — for example, you might never need to directly edit an XML file containing data — but it is very useful to understand the data architecture in ADO.NET, what the major data components are, and how the pieces fit together.
This introduction presents a high-level overview of these most important concepts. The topic deliberately skips over many details — for example, there is much more to datasets than what is mentioned here — in favor of simply introducing you to ideas behind data integration in ADO.NET.
ADO.NET Does Not Depend on Continuously Live Connections In traditional client/server applications, components establish a connection to a database and keep it open while the application is running. For a variety of reasons, this approach is impractical in many applications.
Open database connections take up valuable system resources. In most cases, databases can maintain only a small number of concurrent connections. The overhead of maintaining these connections detracts from overall application performance.
Similarly, applications that require an open database connection are extremely difficult to scale up. An application that does not scale up well might perform acceptably with four users but will likely not do so with hundreds. ASP.NET Web applications in particular need to be easily scalable, because traffic to a Web site can go up by orders of magnitude in a very short period.
A model based on always-connected data can make it difficult and impractical to exchange data across application and organizational boundaries using a connected architecture. If two components need to share the same data, both have to be connected, and a way must be devised for the components to pass data back and forth.
For all these reasons, data access with ADO.NET is designed around an architecture that uses connections sparingly. Applications are connected to the database only long enough to fetch or update the data. Because the database is not holding on to connections that are largely idle, it can service many more users.