In this modern world everyting depends on technology. Without technology we can not do anything. Student Information is one of the important things of our School, Collage, & University life. Everybody purchases some thing. But our life is very busy. So we do not have enough time to total Information of a Student. So the Student Information system was developed. A Student Information System is one building where we can find everything that we need in our daily Student Information is a modern system. it is difficult to maintain by one person. A Team must manage this total system. But we use Student Information System to properly manage total system eithin short time and esasily. Using If we can properly manage Student Information System and any kind of report. We can generate any kind of report any time.
Problem in Student Information (By Manually):
A Student Information may have many problems. The can be categorized as follwas.
1) Its very difficult to find out any students Information’s in a short time.
2) More manpower needed to maintain files.
3) Not secure System.
5) Employee Honestly Problem.
To solve these problems an Student Information must use a Computerized Student Information System. Using this Student Information system one can properly manage Student Infomation and any kind of customized report. If they use an automation system they can prevent many kinds of corruption, which is very important for any kind of Student Information.
Criteria of Output:
- Accurate: Accuracy has been defined in the context of data reconciliation and related to one popular test, the maximum power measurement test. The definition is an extension of one used for measurements to estimators. We define the induced bias as the bias obtained in a stream after data reconciliation is performed in the presence of gross errors. We show that the smearing effect of data reconciliation renders induced biases that are smaller than the actual measurement biases. Finally, we show that loops initiate unlimited accuracy and we claim that these are nonetheless events with low probability so we anticipate working on a probabilistic-based definition of accuracy. Yet, evidence exists that the output of this software may vary accuracy and validity.
- Speedy: when we were coding this software, we focused upon the speed of the software. We used SQL and VB (High Level Language) but I tried to make simple in every instructions and we tried our best.
- Robust: Software is typically buggy (i.e., contains errors) and fragile, and thus not robust. This is in large part because programs are usually too big and too complicated for a single human mind to comprehend in their entirety, and thus it is difficult for their developers to be able to discover and eliminate all the errors, or to even be certain as to what extent of errors exist. This is especially true with regard to subtle errors that only make their presence known in unusual circumstances. Creating robust software is to write general code that can accommodate a wide range of situations and thereby avoid having to insert extra code into it just to handle special cases. This is because code added just to accommodate special cases is often buggier than other code, and stability problems can become particularly frequent and/or severe from the interactions among several such sections of code.
- Less Human Interaction: The system that functions properly requires less human interaction with software systems. Data entry at the mercy of human error can as well as reduces the overall efficiency of an Organization.
- Secure: This software is designed to operate at a level of security that is consistent with the potential harm that could result from the loss, inaccuracy, alteration, unavailability, or misuse of the data and resources that it uses, controls, and protects.
The Genesis of the project.
This project is completed by the platform of visual studio and SQL server as the backend and using the two tier application architecture.
In the 2 tier architecture approach we have only 2 layers. They are:
a). Presentation Layer (Client System)
b). Application Layer + Database Layer (Server System)
Minimum System Requirements:
Operating System : Windows XP Windows Vista, Windows 7
Processor : Pentium 4/AMD 450MHz or higher
RAM : 1GB or higher
HDD : 160GB.
Microsoft Visual Studio:
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is used to develop console and graphical user interface applications along with Windows Forms applications, web sites, web applications, and web services in both native code together with managed code for all platforms supported by Microsoft Windows, Windows Mobile, Windows CE, .NET Framework, .NET Compact Framework and Microsoft Silver light.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The integrated debugger works both as a source-level debugger and a machine-level debugger. Other built-in tools include a forms designer for building GUI applications, web designer, class designer, and database schema designer. It accepts plug-ins that enhance the functionality at almost every level—including adding support for source-control systems (like Subversion and Visual SourceSafe) and adding new toolsets like editors and visual designers for domain-specific languages or toolsets for other aspects of the software development lifecycle (like the Team Foundation Server client: Team Explorer).
Microsoft provides “Express” editions of its Visual Studio 2010 components Visual Basic, Visual C#, Visual C++, and Visual Web Developer at no cost. Visual Studio 2010, 2008 and 2005 Professional Editions, along with language-specific versions (Visual Basic, C++, C#, J#) of Visual Studio Express 2010 are available for free to students as downloads via Microsoft’s Dream Spark program.
Visual Studio does not support any programming language, solution or tool intrinsically, instead allows the plugging of functionality coded as a VS Package. When installed, the functionality is available as a Service. The IDE provides three services: SVs Solution, which provides the ability to enumerate projects and solutions; SVs UIShell, which provides windowing and UI functionality (including tabs, toolbars and tool windows); and SVs Shell, which deals with registration of VS Packages. In addition, the IDE is also responsible for coordinating and enabling communication between services. All editors, designers, project types and other tools are implemented as VS Packages. Visual Studio uses COM to access the VS Packages. The Visual Studio SDK also includes the Managed Package Framework (MPF), which is a set of managed wrappers around the COM-interfaces that allow the Packages to be written in any CLI compliant language. However, MPF does not provide all the functionality exposed by the Visual Studio COM interfaces. The services can then be consumed for creation of other packages, which add functionality to the Visual Studio IDE.
Support for programming languages is added by using a specific VS Package called a Language Service. A language service defines various interfaces which the VS Package implementation can implement to add support for various functionalities. Functionalities that can be added this way include syntax coloring, statement completion; brace matching, parameter information tooltips, member lists and error markers for background compilation. If the interface is implemented, the functionality will be available for the language. Language services are to be implemented on a per-language basis. The implementations can reuse code from the parser or the compiler for the language. Language services can be implemented either in native code or managed code. For native code, either the native COM interfaces or the Babel Framework (part of Visual Studio SDK) can be used. For managed code, the MPF includes wrappers for writing managed language services.
Visual Studio does not include any source control support built in but it defines two alternative ways for source control systems to integrate with the IDE. A Source Control VS Package can provide its own customized user interface. In contrast, a source control plug-in using the MSSCCI (Microsoft Source Code Control Interface) provides a set of functions that are used to implement various source control functionality, with a standard Visual Studio user interface. MSSCCI was first used to integrate Visual SourceSafe with Visual Studio 6.0 but was later opened up via the Visual Studio SDK. Visual Studio .NET 2002 used MSSCCI 1.1, and Visual Studio .NET 2003 used MSSCCI 1.2. Visual Studio 2005, 2008 and 2010 use MSSCCI Version 1.3, which adds support for rename and delete propagation as well as asynchronous opening.
Visual Studio supports running multiple instances of the environment (each with its own set of VS Packages). The instances use different registry hives (see MSDN’s definition of the term “registry hive” in the sense used here) to store their configuration state and are differentiated by their AppId (Application ID). The instances are launched by an AppId-specific .exe that selects the AppId, sets the root hive and launches the IDE. VS Packages registered for one AppId are integrated with other VS Packages for that AppId. The various product editions of Visual Studio are created using the different AppIds. The Visual Studio Express edition products are installed with their own AppIds, but the Standard, Professional and Team Suite products share the same AppId. Consequently, one can install the Express editions side-by-side with other editions, unlike the other editions which update the same installation. The professional edition includes a superset of the VS Packages in the standard edition and the team suite includes a superset of the VS Packages in both other editions. The AppId system is leveraged by the Visual Studio Shell in Visual Studio 2008
The Visual Studio code editor also supports setting bookmarks in code for quick navigation. Other navigational aids include collapsing code blocks and incremental search, in addition to normal text search and regex search. The code editor also includes a multi-item clipboard and a task list. The code editor supports code snippets, which are saved templates for repetitive code and can be inserted into code and customized for the project being worked on. A management tool for code snippets is built in as well. These tools are surfaced as floating windows which can be set to automatically hide when unused or docked to the side of the screen. The Visual Studio code editor also supports code refactoring including parameter reordering, variable and method renaming, interface extraction and encapsulation of class members inside properties, among others.
Visual Studio features background compilation (also called incremental compilation). As code is being written, Visual Studio compiles it in the background in order to provide feedback about syntax and compilation errors, which are flagged with a red wavy underline. Warnings are marked with a green underline. Background compilation does not generate executable code, since it requires a different compiler than the one used to generate executable code.Background compilation was initially introduced with Microsoft Visual Basic but has now been expanded for all included languages.
Main article: Microsoft Visual Studio Debugger
Visual Studio includes a debugger that works both as a source-level debugger and as a machine-level debugger. It works with both managed code as well as native code and can be used for debugging applications written in any language supported by Visual Studio. In addition, it can also attach to running processes and monitor and debug those processes. If source code for the running process is available, it displays the code as it is being run. If source code is not available, it can show the disassembly. The Visual Studio debugger can also create memory dumps as well as load them later for debugging. Multi-threaded programs are also supported. The debugger can be configured to be launched when an application running outside the Visual Studio environment crashes.
The debugger allows setting breakpoints (which allow execution to be stopped temporarily at a certain position) and watches (which monitor the values of variables as the execution progresses). Breakpoints can be conditional, meaning they get triggered when the condition is met. Code can be stepped over, i.e., run one line (of source code) at a time. It can either step into functions to debug inside it, or step over it, i.e., the execution of the function body isn’t available for manual inspection. The debugger supports Edit and Continue, i.e., it allows code to be edited as it is being debugged (32 bit only; not supported in 64 bit). When debugging, if the mouse pointer hovers over any variable, its current value is displayed in a tooltip (“data tooltips”), where it can also be modified if desired. During coding, the Visual Studio debugger lets certain functions be invoked manually from the
immediate tool window. The parameters to the method are supplied at the immediate window.
Visual Studio includes a host of visual designers to aid in the development of applications. These tools include:
Visual Studio Web Designer in code editor view
Visual Studio 2005 in Class Designer view:
Windows Forms Designer:
The Windows Forms designer is used to build GUI applications using Windows Forms. Layout can be controlled by housing the controls inside other containers or locking them to the side of the form. Controls that display data (like textbox, list box, grid view, etc.) can be bound to data sources like databases or queries. Data-bound controls can be created by dragging items from the Data Sources window onto a design surface. The UI is linked with code using an event-driven programming model. The designer generates either C# or VB.NET code for the application.
The WPF designer, codenamed Cider, was introduced with Visual Studio 2008. Like the Windows Forms designer it supports the drag and drop metaphor. It is used to author user interfaces targeting Windows Presentation Foundation. It supports all WPF functionality including data binding and automatic layout management. It generates XAML code for the UI. The generated XAML file is compatible with Microsoft Expression Design, the designer-oriented product. The XAML code is linked with code using a code-behind model.
The Class Designer is used to author and edit the classes (including its members and their access) using UML modeling. The Class Designer can generate C# and VB.NET code outlines for the classes and methods. It can also generate class diagrams from hand-written classes.
The data designer can be used to graphically edit database schemas, including typed tables, primary and foreign keys and constraints. It can also be used to design queries from the graphical view.
From Visual Studio 2008 onwards, the mapping designer is used by LINQ to SQL to design the mapping between database schemas and the classes that encapsulate the data. The new solution from ORM approach, ADO.NET Entity Framework, replaces and improves the old technology.
Visual Studio allows developers to write extensions for Visual Studio to extend its capabilities. These extensions “plug into” Visual Studio and extend its functionality. Extensions come in the form of macros, add-ins, and packages. Macros represent repeatable tasks and actions that developers can record programmatically for saving, replaying, and distributing. Macros, however, cannot implement new commands or create tool windows. They are written using Visual Basic and are not compiled. Add-Ins provide access to the Visual Studio object model and can interact with the IDE tools. Add-Ins can be used to implement new functionality and can add new tool windows. Add-Ins are plugged in to the IDE via COM and can be created in any COM-compliant languages. Packages are created using the Visual Studio SDK and provide the highest level of extensibility. They can create designers and other tools, as well as integrate other programming languages. The Visual Studio SDK provides unmanaged APIs as well as a managed API to accomplish these tasks. However, the managed API isn’t as comprehensive as the unmanaged one. Extensions are supported in the Standard (and higher) versions of Visual Studio 2005. Express Editions do not support hosting extensions.
Visual Studio 2008 introduced the Visual Studio Shell that allows for development of a customized version of the IDE. The Visual Studio Shell defines a set of VS Packages that provide the functionality required in any IDE. On top of that, other packages can be added to customize the installation. The Isolated mode of the shell creates a new AppId where the packages are installed. These are to be started with a different executable. It is aimed for development of custom development environments, either for a specific language or a specific scenario. The Integrated mode installs the packages into the AppId of the Professional/Standard/Team System editions, so that the tools integrate into these editions. The Visual Studio Shell is available as a free download.
After the release of Visual Studio 2008, Microsoft created the Visual Studio Gallery. It serves as the central location for posting information about extensions to Visual Studio. Community developers as well as commercial developers can upload information about their extensions to Visual Studio .NET 2002 through Visual Studio 2010. Users of the site can rate and review the extensions to help assess the quality of extensions being posted. RSS feeds to notify users on updates to the site and tagging features are also planned.
Visual Studio Team System:
Prior to Visual Studio 2010, Visual Studio Team System provided four role-specific editions are:
- Team Explorer (basic TFS client)
- Architecture Edition
- Database Edition
- Development Edition
- Test Edition
The combined functionality of the four Team System Editions is provided in a Team Suite Edition. The Database Edition, codenamed “Data Dude”, was initially released as a separate edition after Visual Studio 2005’s initial release. It is included with Visual Studio 2008 as a separate edition, but Microsoft did roll its functionality into the Premium Edition with Visual Studio 2010.
Visual Studio Test Professional is an edition which was introduced with Visual Studio 2010. Its focus is aimed at the dedicated tester role and includes support for the management of test environments, the ability to start and report on tests and to connect to Team Foundation Server. It does not include support for development or authoring of tests.
Visual Studio 2008:
Visual Studio 2008, and Visual Studio Team System 2008 codenamed Orcas (a reference to Orcas Island, also an island in Puget Sound, like Whidbey for the previous 2005 release), were released to MSDN subscribers on 19 November 2007 alongside .NET Framework 3.5. The source code for the Visual Studio 2008 IDE is available under a shared source license to some of Microsoft’s partners and ISVs. Microsoft released Service Pack 1 for Visual Studio 2008 on 11 August 2008. The internal version number of Visual Studio 2008 is version 9.0 while the file format version is 10.0. Visual Studio 2008 is the last version to support targeting Windows 2000 for C++ applications.
Visual Studio 2008 is focused on development of Windows Vista, 2007 Office system, and Web applications. For visual design, a new Windows Presentation Foundation visual designer and a new HTML/CSS editor influenced by Microsoft Expression Web are included. J# is not included. Visual Studio 2008 requires .NET 3.5 Framework and by default configures compiled assemblies to run on .NET Framework 3.5, but it also supports multi-targeting which lets the developers choose which version of the .NET Framework (out of 2.0, 3.0, 3.5, Silver light CoreCLR or .NET Compact Framework) the assembly runs on. Visual Studio 2008 also includes new code analysis tools, including the new Code Metrics tool (only in Team Edition and Team Suite Edition). For Visual C++, Visual Studio adds a new version of Microsoft Foundation Classes (MFC 9.0) that adds support for the visual styles and UI controls introduced with Windows Vista. For native and managed code interoperability, Visual C++ introduces the STL/CLR, which is a port of the C++ Standard Template Library (STL) containers and algorithms to managed code. STL/CLR defines STL-like containers, integrators and algorithms that work on C++/CLI managed objects.
The Visual Studio debugger includes features targeting easier debugging of multi-threaded applications. In debugging mode, in the Threads window, which lists all the threads, hovering over a thread will display the stack trace of that thread in tooltips. The threads can directly be named and flagged for easier identification from that window itself. In addition, in the code window, along with indicating the location of the currently executing instruction in the current thread, the currently executing instructions in other threads are also pointed out. The Visual Studio debugger supports integrated debugging of the .NET 3.5 Framework Base Class Library (BCL) which can dynamically download the BCL source code and debug symbols and allow stepping into the BCL source during debugging. As of 2010 a limited subset of the BCL source is available, with more library support planned for later.
Visual Studio Application Lifecycle Management:
Visual Studio Application Lifecycle Management is a collection of integrated software development tools developed by Microsoft. These tools include IDEs, source control, work items, collaboration, metrics, and reporting tools. Visual Studio Application Lifecycle Management consists of four products:
- Visual Studio, which provides an IDE (Integrated Development Environment) for development and client side interfaces for the other products.
- Visual Studio Test Professional, which provides an IDE for software testers to create and execute tests.
- Team Foundation Server, which provides Source Code collaboration and data storage.
- Visual Studio Lab Management, which provides a way for software testers to create and manage virtual environments.
Microsoft SQL Server:
Microsoft SQL Server is a relational database server product by Microsoft. Its primary query languages are T-SQL and ANSI SQL.
Prior to version 7.0 the code base for MS SQL Server was sold by Sybase SQL Server to Microsoft, and was Microsoft’s entry to the enterprise-level database market, competing against Oracle, IBM, and, later, Sybase. Microsoft, Sybase and Ashton-Tate originally teamed up to create and market the first version named SQL Server 1.0 for OS/2 (about 1989) which was essentially the same as Sybase SQL Server 3.0 on Unix, VMS, etc. Microsoft SQL Server 4.2 was shipped around 1992 (available bundled with IBM OS/2 version 1.3). Later Microsoft SQL Server 4.21 for Windows NT was released at the same time as Windows NT 3.1. Microsoft SQL Server v6.0 was the first version designed for NT, and did not include any direction from Sybase.
About the time Windows NT was released, Sybase and Microsoft parted ways and each pursued their own design and marketing schemes. Microsoft negotiated exclusive rights to all versions of SQL Server written for Microsoft operating systems. Later, Sybase changed the name of its product to Adaptive Server Enterprise to avoid confusion with Microsoft SQL Server. Until 1994, Microsoft’s SQL Server carried three Sybase copyright notices as an indication of its origin.
Since parting ways, several revisions have been done independently. SQL Server 7.0 was a rewrite from the legacy Sybase code. It was succeeded by SQL Server 2000, which was the first edition to be launched in a variant for the IA-64 architecture.
In the ten years since release of Microsoft’s previous SQL Server product (SQL Server 2000), advancements have been made in performance, the client IDE tools, and several complementary systems that are packaged with SQL Server 2005. These include: an ETL tool (SQL Server Integration Services or SSIS), a Reporting Server, an OLAP and data mining server (Analysis Services), and several messaging technologies, specifically Service Broker and Notification Services.
SQL Server 2005:
SQL Server 2005 (codename Yukon), released in October 2005, is the successor to SQL Server 2000. It included native support for managing XML data, in addition to relational data. For this purpose, it defined an
xml data type that could be used either as a data type in database columns or as literals in queries. XML columns can be associated with XSD schemas; XML data being stored is verified against the schema. XML is converted to an internal binary data type before being stored in the database. Specialized indexing methods were made available for XML data. XML data is queried using XQuery; Common Language Runtime (CLR) integration was a main feature with this edition, enabling one to write SQL code as Managed Code by the CLR. SQL Server 2005 added some extensions to the T-SQL language to allow embedding XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery, called XML DML that allows query-based modifications to XML data. SQL Server 2005 also allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests. When the data is accessed over web services, results are returned as XML.
For relational data, T-SQL has been augmented with error handling features (try/catch) and support for recursive queries with CTEs (Common Table Expressions). SQL Server 2005 has also been enhanced with new indexing algorithms, syntax and better error recovery systems. Data pages are check summed for better error resiliency, and optimistic concurrency support has been added for better performance. Permissions and access control have been made more granular and the query processor handles concurrent execution of queries in a more efficient way. Partitions on tables and indexes are supported natively, so scaling out a database onto a cluster is easier. SQL CLR was introduced with SQL Server 2005 to let it integrate with the .NET Framework.
SQL Server 2005 introduced “MARS” (Multiple Active Results Sets), a method of allowing usage of database connections for multiple purposes.
SQL Server 2005 introduced DMVs (Dynamic Management Views), which are specialized views and functions that return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance.
SQL Server 2005 introduced Database Mirroring, but it was not fully supported until the first Service Pack release (SP1). In the initial release (RTM) of SQL Server 2005, database mirroring was available, but unsupported. In order to implement database mirroring in the RTM version, you had to apply trace flag 1400 at startup. Database mirroring is a high availability option that provides redundancy and failover capabilities at the database level. Failover can be performed manually or can be configured for automatic failover. Automatic failover requires a witness partner and an operating mode of synchronous (also known as high-safety or full safety).
SQL Server Reporting Services is a report generation environment for data gathered from SQL Server databases. It is administered via a web interface. Reporting services features a web services interface to support the development of custom reporting applications. Reports are created as RDL files.
Reports can be designed using recent versions of Microsoft Visual Studio (Visual Studio.NET 2003, 2005, and 2008) with Business Intelligence Development Studio, installed or with the included Report Builder. Once created, RDL files can be rendered in a variety of formatsincluding Excel, PDF, CSV, XML, TIFF (and other image formats), and HTML Web Archive.
Originally introduced as a post-release add-on for SQL Server 2000, Notification Services was bundled as part of the Microsoft SQL Server platform for the first and only time with SQL Server 2005.with SQL Server 2005, SQL Server Notification Services is a mechanism for generating data-driven notifications, which are sent to Notification Services subscribers. A subscriber registers for a specific event or transaction (which is registered on the database server as a trigger); when the event occurs, Notification Services can use one of three methods to send a message to the subscriber informing about the occurrence of the event. These methods include SMTP, SOAP, or by writing to a file in the file system. Notification Services was discontinued by Microsoft with the release of SQL Server 2008 in August 2008, and is no longer an officially supported component of the SQL Server database platform.
SQL Server Integration Services is used to integrate data from different data sources. It is used for the ETL capabilities for SQL Server for data warehousing needs. Integration Services includes GUI tools to build data extraction workflows integration various functionality such as extracting data from various sources, querying data, transforming data including aggregating, duplication and merging data, and then loading the transformed data onto other sources, or sending e-mails detailing the status of the operation as defined by the user.
Full Text Search Service:
The SQL Server Full Text Search service architecture:
SQL Server Full Text Search service is a specialized indexing and querying service for unstructured text stored in SQL Server databases. The full text search index can be created on any column with character based text data. It allows for words to be searched for in the text columns. While it can be performed with the SQL
LIKE operator, using SQL Server Full Text Search service can be more efficient. Full Text Search (FTS) allows for inexact matching of the source string, indicated by a Rank value which can range from 0 to 1000 – a higher rank means a more accurate match. It also allows linguistic matching (“inflectional search”), i.e., linguistic variants of a word (such as a verb in a different tense) will also be a match for a given word (but with a lower rank than an exact match). Proximity searches are also supported, i.e., if the words searched for do not occur in the sequence they are specified in the query but are near each other, they are also considered a match. T-SQL exposes special operators that can be used to access the FTS capabilities.
The Full Text Search engine is divided into two processes – the Filter Daemon process (
msftefd.exe) and the Search process (
msftesql.exe). These processes interact with the SQL Server. The Search process includes the indexer (that creates the full text indexes) and the full text query processor. The indexer scans through text columns in the database. It can also index through binary columns, and use iFilters to extract meaningful text from the binary blob (for example, when a Microsoft Word document is stored as an unstructured binary file in a database). The iFilters are hosted by the Filter Daemon process. Once the text is extracted, the Filter Daemon process breaks it up into a sequence of words and hands it over to the indexer. The indexer filters out noise words, i.e., words like A, And etc., which occur frequently and are not useful for search. With the remaining words, an inverted index is created, associating each word with the columns they were found in. SQL Server itself includes a Gatherer component that monitors changes to tables and invokes the indexer in case of updates.
When a full text query is received by the SQL Server query processor, it is handed over to the FTS query processor in the Search process. The FTS query processor breaks up the query into the constituent words, filters out the noise words, and uses an inbuilt thesaurus to find out the linguistic variants for each word. The words are then queried against the inverted index and a rank of their accurateness is computed. The results are returned to the client via the SQL Server process.
Microsoft Visual Studio includes native support for data programming with Microsoft SQL Server. It can be used to write and debug code to be executed by SQL CLR. It also includes a data designer that can be used to graphically create, view or edit database schemas. Queries can be created either visually or using code. SSMS 2008 onwards, provides intelligence for SQL queries as well.
Crystal Reports is a business intelligence application used to design and generate reports from a wide range of data sources. Several other applications, including Microsoft Visual Studio, at one time bundled an OEM version of Crystal Reports as a general purpose reporting tool. Crystal Reports is a popular report writer, especially so when Microsoft bundled it with Visual Studio versions 2003 through 2008. Microsoft discontinued this practice and later released their own competitive reporting tool, SQL Server Reporting Services (SSRS). Crystal Reports for Visual Studio 2010 is still available as add-on software.
Crystal Reports allows users to graphically design data connection(s) and report layout. In the Database Expert, users can select and link tables from a wide variety of data sources, including Microsoft Excel spreadsheets, Oracle databases, Business Objects Enterprise business views, and local file system information. Fields from these tables can be placed on the report design surface, and can also be used in custom formulas, using either BASIC or Crystal’s own syntax, which are then placed on the design surface. Formulas can be evaluated at several phases during report generation as specified by the developer.
Both fields and formulae have a wide array of formatting options available, which can be applied absolutely or conditionally. The data can be grouped into bands, each of which can be split further and conditionally suppressed as needed. Crystal Reports also supports sub reports, graphing, and a limited amount of GIS functionality.
Supported data sources:
Accessible data sources include the following:
- Databases such as PostgreSQL, Sybase, IBM DB2, Ingres, Microsoft Access, Microsoft SQL Server, MySQL, Interbase and Oracle
- Spreadsheets such as Microsoft Excel
- Text files
- HTML XML files
- Groupware applications as Lotus Notes, Microsoft Exchange and Novell GroupWise
- SAP: BW, Info Sets, Tables, and Business Objects Universes
- Any other data source accessible through a web service, ODBC, JDBC or OLAP.
In software engineering, an Entity Relationship Model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called Entity Relationship Diagrams, ER Diagrams, or ERDs.
This article refers to the techniques proposed in Peter Chen’s 1976 paper. However, variants of the idea existed previously, and have been devised subsequently.
The table structures and descriptions are given below.
SQL Server Logins and Users:
Although the terms login and user are often used interchangeably, they are very different.
- A login is used for user authentication
- A database user account is used for database access and permissions validation.
|Column Name||Data type||Description|
|User Name||varchar (20)||Stores the user name|
The login form is used to log into the application. Here user name is used as the user login id and password is used for user password. If the user credential are valid a successfully login otherwise it gives an invalid user massage. Form design given in figure and the code is in Appendix.
The main form is used to insert, delete, update search data and to see reports. With this page we can insert student data, delete, and update. We also can get reports. We can search students information whenever we want.
In insert page we create four sections. There are personal information, family information, academic information and additional information. In personal information form we can insert student ID, name, date of birth, gender, date of admission, address and contact number.
Personal Information’s: In the personal information we can insert Students personal information’s.
Family Information: In family formation form, we can insert student’s family information’s.
Academic Information: In Academic Information form, we can insert all Academic Qualification’s of a Student.
Additional Information: In Additional information form, we can insert Additional information of a Student.
Delete Form: In the delete form we can delete wrong information’s or inappropriate information’s.
Detail & Update: In the Detail & Update form we can see the information’s detail and we can update information’s if needed.
Update Personal Information:
Search: In the search form we can search Students information’s whatever we want. There are two sections.
Report: In this form we can see reports whatever we want, such as Individual or all reports of students.
5.1 Future work:
The time we had was not enough for the full completion of the project work but we did our best to complete this project. Yet some lacking exists. We did not get enough time to implement many things which would be the additional advantage of the project.
Evolution of the Software: A student info system is a software application for education establishments to manage student data. Student information systems provide capabilities for entering student all over information. We can anytime, anywhere access to data. The act prompted an explosion of different users who needed student data are now made available to appropriate users. These systems vary in size, scope and capability, from packages that are implemented in relatively small organizations to cover student records.
- Easily import data from external sources
- Identify your best prospective students, how many applicants you have, and next steps to move each applicant through the process.
- Capture information needed for admissions, such as education history, activities, test scores, interview notes, and more
- Track detailed relationships of applicants and students to assist in the recruiting process
- Perform any type of demographic analysis (ethnicity, religion, gender, etc.)
- Communicate application status via letters, emails, or your website
- Standardize, simplify, and expedite the process with communication and checklist management features
- See where students stand on credits and requirements with degree tracking and audit functionality
- Perform institutional research with easy-to-use query and reporting tools
- Simplify the production of campus directories and specialized lists with easy-to-use query and reporting tools
Conclusion: In this project we tried to cover most of the important components of the Students Information System. In developing this project we used visual studio 2008 for design the interface and for the backend we used SQL server 2005 and we also used Crystal Report for viewing report. We tried to outmost to design our database free from data redundancy and enhance data consistency and make the application bug free. This software is designed to be modular to allow for future updates and advance requirements fulfillment. This project focused on real life student’s information system.