VB Final Report

CHAPTER 1 OBJECTIVE
PAYROLL MANAGEMENT SYSTEM Page 1
CHAPTER 2 SOFTWARE REQUIREMENT SPECIFICATION 2.1. Introduction 2.1.1 Purpose 2.1.2 Scope 2.1.3 Definitions, Acronyms and Abbreviations 2.1.4 References 2.1.5 Overview 2.2. The Overall Description 2.2.1 Product Perspective 2.2.1.1 Features of TechSketch 2.2.1.2 User Interfaces 2.2.1.3 Hardware Interfaces 2.2.1.4 Software Interfaces 2.2.1.5 Communications Interfaces 2.2.1.6 Functional requirements 2.2.1.7 Non functional requirements 2.2.2 User Characteristics 2.2.3 Constraints 2.2.4 Assumptions and Dependencies 2.2.5 User Documentation
2.3. Specific Requirements 2.3.1 External Interfaces 2.3.2 Functions 2.3.3 Software attribute 2.3.4 Performance 2.3.5 Design Constraints 2.3.6 Software System Attributes 2.3.6.1 Maintainability 2.3.6.2 Availability 2.3.6.3 Correctness 2.3.7 Software System Attributes 2.3.7.1 System Feasibility 2.3.7.2 User friendliness 2.3.7.3 Consistency 2.3.7.4 Compatibility 2.3.7.5 Security 2.3.7.6 Reliability & Robustness 2.3.7.7 Performance 2.3.7.8 Extensibility 2.3.7.9 Flexibility 2.3.7.10 Maintainability 2.4. Document Approval
2.1INTRODUCTION: Visual Basic is a third-generation event-driven programming language and integrated development environment (IDE) from Microsoft for its COM programming model first released in 1991. Visual Basic is designed to be relatively easy to learn and use. Visual Basic was derived from BASIC and enables therapid application development (RAD) of graphical user interface (GUI) applications, access to databasesusing Data Access Objects, Remote Data Objects, or ActiveX Data Objects, and creation of ActiveXcontrols and objects. VBA is effectively the same language as Visual Basic but VBA-code is tied to Microsoft Office and can only run within that environment.The scripting language VBScript is a subset of Visual BasicA programmer can create an application using the components provided by the Visual Basic program itself. Programs written in Visual Basic can also use the Windows API, but doing so requires external function declarations. Though the program has received criticism for its perceived faults,[3] version 3 of Visual Basic was a runaway commercial success,[4] and many companies offered third party controls greatly extending its functionality. The final release was version 6 in 1998. Microsoft's extended support ended in March 2008 and the designated successor was Visual Basic .NET
Visual Basic is a third generation event-driven programming language. The Microsoft Corporation released Visual Basic in 1987. It was indeed the first visual development tool from Microsoft. Visual Basic was derived from BASIC and enables rapid application development of
graphical user interface applications, access to databases using DAO, RDO, or ADO, and creation of ActiveX controls and objects. The language not only allows Visual Basic programmers to create simple GUI applications, but also helps them develop quite complex applications. Visual Basic allows developers to target Windows, Web, and mobile devices. Programmers have undergone a major change in many years of programming various machines. For example what could be created in minutes with Visual Basic could take days in other languages such: as "C" or "Pascal". Visual Basic provides many interesting sets of tools to aid you in building exciting applications. Visual Basic provides these tools to make your life far more easier because all the real hard code is already written for you. With controls like these you can create many applications which use certain parts of windows. For example, one of the controls could be a button, which we have demonstrated in the "Hello World" program below. First create the control on the screen, then write the code which would be executed once the control button is pressed. With this sort of operation in mind, simple programs would take very little code. Why do it like the poor old "C" programmer who would have to write code to even display a window on the screen, when Visual Basic already has this part written for you. Even though people tend to say Visual Basic's compiler is far behind the compilers of Pascal and C, it has earned itself the status of a professional programming language, and has almost freed BASIC of the reputation of a children's language. Overall you would class Visual Basic as a Graphics User Interface(GUI). Because as you draw, you write for the program. This must always be remembered in any kind of creation of a Visual Basic program. All in all, VB is the preferred language of many future program mers. If you want to start programming Windows, and don't know how to start, give Visual Basic a shot. VISUAL BASIC is a high level programming language which was evolved from the earlier DOS version called BASIC. Visual Basic is an Object based Event Driven Programming Langugage.
However, it seems people only use Microsoft Visual Basic today, as it is a well developed programming language and supporting resources are available everywhere. VISUAL BASIC Program is made up of many subprograms, each has its own program codes, and each can be executed independently and at the same time each can be linked together in one way or another VISUAL BASIC ENVIRONMENT On start up, Visual Basic 6.0 will display the following dialog box as shown in figure. You can choose to either start a new project, open an existing project or select a list of recently opened programs. A project is a collection of files that make up your application. There are various types of applications we could create, however, we shall concentrate on creating Standard EXE programs VISUAL BASIC is a high level programming language which evolved from the earlier DOS version called BASIC.BASIC means Beginners' All-purpose Symbolic Instruct ion Code. It is a very easy programming language to learn. The code look a lot like English Language. Different software companies produced different versions of BASIC, such as Microsoft QBASIC, QUICKBASIC, GWBASIC ,IBM BASICA and so on. However, people prefer to use Microsoft Visual Basic today, as it is a well developed programming language and supporting resources are available everywhere. Now, there are many versions of VB exist in the market, the most popular one and still widely used by many VB programmers is none other than Visual Basic 6. We also have VB.net, VB2005 , VB2008 and the latest VB2010, which is a fully object oriented programming (OOP) language. It is more powerful than VB6 but looks more complicated to master.
VISUAL BASIC is a VISUAL and events driven Programming Language. These are the main divergence from the old BASIC. In BASIC, programming is done in a text-only environment and the program is executed sequentially. In VB, programming is done in a graphical environment. In the old BASIC, you have to write program code for each graphical object you wish to display it on screen, including its position and its color. However, In VB , you just need to drag and drop any graphical object anywhere on the form, and you can change its color any time using the properties windows. Project 'Thunder' was initiated in 1990.[citation needed] Visual Basic 1.0 (May 1991) was released for Windows at the Comdex/Windows World trade show in Atlanta, Georgia. Visual Basic 1.0 for DOS was released in September 1992. The language itself was not quite compatible with Visual Basic for Windows, as it was actually the next version of Microsoft's DOSbased BASIC compilers,QuickBASIC and BASIC Professional Development System. The interface used a Text user interface, usingextended ASCII characters to simulate the appearance of a GUI.
Visual Basic 2.0 was released in November 1992. The programming environment was easier to use, and its speed was improved. Notably, forms became instantiable objects, thus laying the foundational concepts of class modules as were later offered in VB4. Visual Basic 3.0 was released in the summer of 1993 and came in Standard and Professional versions. VB3 included version 1.1 of the Microsoft Jet Database Engine that could read and write Jet (or Access) 1.x databases. Visual Basic 4.0 (August 1995) was the first version that could create 32-bitas well as 16-bit Windows programs. It has three
Page 8
PAYROLL MANAGEMENT SYSTEM
editions; Standard, Professional, and Enterprise. It also introduced the ability to write non-GUI classes in Visual Basic. Incompatibilities between different releases of VB4 caused installation and operation problems. While previous versions of Visual Basic had used VBX controls, Visual Basic now used OLE controls (with files names ending in .OCX) instead. These were later to be named ActiveX controls. With version 5.0 (February 1997), Microsoft released Visual Basic exclusively for 32-bit versions of Windows. Programmers who preferred to write 16-bit programs were able to import programs written in Visual Basic 4.0 to Visual Basic 5.0, and Visual Basic 5.0 programs can easily be converted with Visual Basic 4.0. Visual Basic 5.0 also introduced the ability to create custom user controls, as well as the ability to compile to native Windows executable code, speeding up calculation-intensive code execution. A free, downloadable Control Creation Edition was also released for creation of ActiveX controls. It was also used as an introductory form of Visual Basic: a regular .exe project could be created and run in the IDE, but not compiled. Visual Basic 6.0 (Mid 1998) improved in a number of areas[9] including the ability to create web-based applications. VB6 has entered Microsoft's "non-supported phase" as of March 2008. Although the Visual Basic 6.0 development environment is no longer supported, the runtime is supported on Windows Vista, Windows Server 2008 and Windows 7.[10] Mainstream Support for Microsoft Visual Basic 6.0 ended on March 31, 2005. Extended support ended in March 2008. [11] In response, the Visual Basic user community expressed its grave concern and lobbied users to sign a petition to keep the product alive. [12] Microsoft has so far refused to change their position on the matter. [13] Ironically, around this time (2005), it was exposed that Microsoft's new anti-spyware offering, Microsoft AntiSpyware (part of theGIANT Company Software purchase), was coded in Visual Basic 6.0. [14] Its replacement, Windows Defender, was rewritten as C++ code
. 2.1.1 PURPOSE:
Visual Basic is not only a programming language, but also a complete graphical development environment. This environment allows users with little programming experience to quickly develop useful Microsoft Windows applications which have the ability to use OLE ( Object Linking and Embedding ) objects, such as an Excel spreadsheet. Visual Basic also has the ability to develop programs that can be used as a front end application to a database system, serving as the user interface which collects user input and displays formatted output in a more appealing and useful form than many SQL versions are capable of. Visual Basic's main selling point is the ease with which it allows the user to create nice looking, graphical programs with little coding by the programmer, unlike many other languages that may take hundreds of lines of programmer keyed code. As the programmer works in the graphical environment, much of the program code is automatically generated by the Visual Basic program.
2.1.2 SCOPE: This software could consider any code in any language, constrained with a comment language. This software could generate a flow chart or class diagram for the system, which could be further used for analysis of the system. Programming in Visual Basic is a combination of visually arranging components on a form, specifying attributes and actions of those components. Since the default
attributes and actions ought to be defined for the components, it is very simple to write a program without the help of a Visual Basic programmer. Forms can be created using drag and drop techniques. Visual Basic provides many interesting sets of tools to help you in building exciting and entertaining applications. It provides these tools to make your life easier, since the entire coding is already written for you. Moreover, it is a user friendly language which is very effective and efficient. A tool is used to place controls such as text boxes, buttons, etc on the form window. Default values will be provided when a control is created, but it can be changed by the Visual Basic programmer.
Visual Basic is not only a programming language, but it also has a complete graphical development environment. Visual Basic has the ability to develop programs that can be used as a front end application to a database system, and serving as the user interface which collects input from the user and displays formatted output in an attractive format. As the Visual Basic programmer works in the graphical environment, much of the program code is automatically generated by the Visual Basic program. The main object in Visual Basic is called a form. Once you create forms, you can change the properties using properties window. Finally, you
can add events to your controls. Events are responses to actions performed
2.1.4 REFERENCES: [IEEE] The applicable IEEE standards are published in IEEE Standards Collection, 2001 edition.
2.2. OVERALL DESCRIPTION: When you open a new project, you will start with a clear form that looks similar to this : 1.GUI Interface VB is a Graphical User Interface (GUI) language. This means that a VB program will always show something on the screen that the user can interact with (usually via mouse and keyboard) to get a job done. The first step in building the VB program is to get the GUI items on the screen. This is done via pull-down menus that list the available graphical objects. Every system is slightly different (Mac differs from Windows and VB4 Differs from VB6) but, generally speaking, left-clicking on an object allows you to describe attributes like size and position. Right clicking allows you to write code. For example, if the GUI item is a
switch, left-clicking would allow the programmer to say how big the switch was, how it was labeled and where on the screen it is positioned. Right-clicking on the switch would bring up a window that allows the programmer to write the code that describes what happens when the user clicks the switch. Modularization It is considered good programming practice to modularize your programs. Instead of thinking of a computer program as a single large collection of code, the good programmer writes code so that you never need to look at more code than fits on the screen (or page) at one time. If you program in modules like this, the program is easier to understand and easy to update. Updating will likely be done by someone else so it is import that the program be easy to understand. Small (page size) modules where it is clearly indicated what comes into the module and what goes out makes a program easy to understand. VB forces you to program in a modular fashion because each GUI item contains part of the code---the part that applies to that GUI item.
o
Object Orentation Object Oriented Programming (OOP) is a concept where the programmer thinks of the program in "objects" (however abstract the objects may be) that interact with each other. In OOP, all the code associated with that object is in one place. Once again, VB forces this good programming practice. The GUI items are the objects and all the code associated with the object are just a click away. This natural way of enforcing good programming practices---plus the ease of programming in BASIC---is exactly why VB has found so many devoted fans.
2.2.Product perspective
Using Visual Basic's tools, you can quickly translate an abstract idea into a program design which you can actually see on the screen. VB encourages you to experiment, revise, correct, and network your design until the project meets your requirements. Visual Basic Programmer use the language in different areas such as Education, Business, Accounting, Marketing and Sales. Visual Basic supports a number of common programming constructs and language elements. Once you understand the basics of the language, you can create powerful applications using Visual Basic. Visual Basic can create executables i.e. EXE files, ActiveX controls, but it is primarily used to develop Windows applications. It is also used to interface web database systems. This generation of Visual Basic continues the tradition of giving you a faster and easier way to create .NET framework-based applications. Visual Basic also fully integrates the .NET framework and the common language runtime, which provide language interoperability, garbage collection, enhanced security, and versioning support
2.2.1 Hardware interface 1. Operating System: Windows XP or Windows Vista 2. Processor: 1.5 GHz (XP), 2-GHz (Vista) 32-bit (x86) or better
3. Memory: 512 MB or more 4. Screen Resolution: 1024x768 pixels or higher
2.2.1.2 Software interface These requirements will be for an end user. 1. Visual basic 6.0 or higher 2. Sql srever 5.0 or higher
Advantages 1. The structure of the Basic programming language is very simple, particularly as to the executable code. 2. VB is not only a language but primarily an integrated, interactive development environment (IDE). 3. The VB-IDE has been highly optimized to support rapid application development (RAD). It is particularly easy to develop graphical user interfaces and to connect them to handler functions provided by the application. 4. The graphical user interface of the VB-IDE provides intuitively appealing views for the management of the program structure in the large and the various types of entities (classes, modules, procedures, forms, ). 5. VB provides a comprehensive interactive and contextsensitive online help system. 6. When editing program texts the IntelliSense technology informs you in a little popup window about the types of constructs that may be entered at the current cursor location. 7. VB is a component integration language which is attuned to Microsofts Component Object Model (COM). 8. COM components can be written in different languages and then inegrated using VB.
9. Interfaces of COM components can be easily called remotely via Distributed COM (DCOM), which makes it easy to construct distributed applications. 10. COM components can be embedded in / linked to your applications user interface and also in/to stored documents (Object Linking and Embedding OLE, Compound Documents). 11. There is a wealth of readily available COM components for many different purposes. 12. Visual Basic is built around the .NET environment used by all Microsoft Visual languages, so there is very little that cant be done in Visual Basic that can be done in other languages (such as C#). .
2.3.7 SOFTWARE SYSTEM ATTRIBUTES 2.3.7.1 Feasibility Analysis: A feasibility analysis involves a detailed assessment of the need value and the practicality of a proposed enterprise, such as system development. The process of designing and implementing record keeping systems has significant accountability and resource implications for an organization. Feasibility analysis will help you make informed and transparent decisions at crucial points during the development process as you determine whether it is operational, economically, technically realistic to proceed with a particular course of action. A feasibility analysis usually involves a thorough assessment of the financial (value), technical (practicality), and operational (need) aspects of a proposal. In Internet Management Solution projects, devices used are primarily
responsible for assessing the operational feasibility of the system, and information technology (IT) analysts are responsible for assessing technical feasibility. Both then work together to prepare a cost-benefit analysis of the proposed system to determine its economic feasibility.
2.3.7.1.1 Economic Feasibility:
Evolution of Visual Basic

March 6, 1988 Microsoft Buys Tripod Alan Cooper, the 'father' of Visual Basic, shows a drag-and-drop shell prototype called Tripod to Bill Gates. Microsoft negotiates to buy the concept, now code-named Ruby. The Tool includes a widget control box, the ability to add widgets dynamically, and a small language engine. March 20, 1991 Visual Basic 1.0 Debuts at Windows World Microsoft marries QuickBasic to Ruby shell app and gives it a new code name: Thunder. The result is the first tool that lets you create Windows apps quickly, easily, and visually. Features include a drag and drop control toolbox, codeless UI creation, and an eventoriented programming model. March 1992 Visual Basic 2.0 Toolkit (Rawhide) Released This toolkit integrated several third-party tools into a single package, putting controls in the hands of many VB developers for the first time. It provided instrumental in helping VB's third party market achieve critical mass.
September 1992 Visual Basic 1.0 for DOS is released. Figure this one out :) The language itself was not quite compatible with Visual Basic for Windows, as it was actually the next version of Microsoft's DOSbased BASIC compilers, QuickBASIC and BASIC Professional Development System. November 1992 Visual Basic 2 Debuts Adds ODBC Level 1 support, MDI forms, and object variables. First version to feature the Professional Edition. The programming environment was easier to use, and its speed was improved. June 1993 Visual Basic 3 Debuts Integrates the Access Engine (Jet), OLE Automation and reporting. It came in both Standard and Professional versions. Visual Basic 3 included version 1.1 of the Microsoft Jet DatabaseEngine that could read and write Jet (or Access) 1.x databases. October 1996 Visual Basic 4 Debuts Permits you to create your own add-ins. Also introduces classes and OCX's. Was the first version that could created 32 bit as well as 16-bit Windows programs. April 1997 Visual Basic 5 Debuts Incorporates compiler, WithEvents, and the ability to create ActiveX controls. A free, downloadable Control Creation Edition was also released for creation of ActiveX controls. It was also used as an introductory form of Visual Basic: a regular. exe project could be created and run in the IDE, but not compiled.
October 1998 Visual Basic 6 Debuts Introduces WebClasses, windowless controls, data designers, new reporting designers, and the ability to create data sources.
Visual Basic Version Summary.

The evolution of Visual Basic can be summarized by the following table: Version 1 (for Windows) March 20, 1991 Version 1 (for MS-DOS) September 1992 Version 2 November 1992 Version 3 June 1993 VBA (VB for Applications) 1993 Version 4 October 1996 (16- and 32-bit support) Version 5 April 1997 (no 16-bit support) Version 6 October 1998 (part of Visual Studio) Version 7 (.NET) February 2002 Version 7.1 (.NET 2003) April 2003 VBA .NET for Office 2003 October 2003 Version 8 (.NET 2.0, Visual Studio 2005) November 2005 Version 9 (.NET 3.5, Visual Studio 2008) released November 2007 Version 10 (Visual Studio 2010 and .NET Framework 4.0) in Pre-release as of October 31, 2008
Brief Historyof VisualBasic(1.0 to 6.0) Visual Basic 1.0 for Windows was released in May 1991 at a trade show in Atlanta, Georgia.
Visual Basic 2.0 was released in November 1992. The programming environment was easier to use, and its speed was improved. Notably, forms became core objects, thus laying the foundational concepts of class modules as were later offered in VB4. Visual Basic 3.0 was released in 1993 and came in Standard and Professional versions. VB3 included version 1.1 of the Microsoft Jet Database Engine that could read and write Jet (or Access) 1.x databases.
Visual Basic 4.0 was released in August 1995. It was the first version that could create 32-bit as well as 16-bit Windows programs. It also introduced the ability to write non-GUI classes in Visual Basic. While previous versions of Visual Basic had used VBX controls, Visual Basic now used OLE controls (with files names ending in .ocx) instead. These were later to be named ActiveX controls.
With version 5.0 release in February 1997, Microsoft released Visual Basic exclusively for 32-bit versions of Windows. Programmers who preferred to write 16-bit programs were able to import programs written in Visual Basic 4.0 to Visual Basic 5.0, and Visual Basic 5.0 programs could easily be converted with Visual Basic 4.0. Visual Basic 5.0 also introduced the ability to create custom user controls, as well as the ability to compile to native Windows executable code, speeding up calculation-intensive code execution. A free, downloadable Control Creation Edition was also released for creation of ActiveX controls.
Visual Basic 6.0 released in mid 1998 improved in a number of areas including the ability to create web-based applications. VB6 has been the most successful version in the history of Visual Basic, it has entered Microsoft's 'non-supported phase' as of March 2008. Although the development environment is no longer supported, the runtime is supported on Windows Vista, Windows Server 2008 and Windows 7. Mainstream Support for Microsoft VB 6.0 ended on March 31, 2005. Extended support ended in March 2008. In response, the Visual Basic user community expressed its grave concern and lobbied users to sign a petition to keep the product alive. Microsoft has so far refused to change their position on the matter. Visual Basic has gone through many changes over it lifetime. The latest incarnation, VB.Net, is evolving at an ever increasing price. 2.3.7.1.2 Operational/Social Feasibility:
Menu / Toolbar This is the only element of the IDE which is always visible. You use it to select which other IDE elements to view and to add forms or controls to your project.
Toolbox The toolbox is simply a library of controls which you can place on your application. Once you've placed all the controls you need onto your applications
forms, you can hide the toolbox to make room for working in the other elements of the IDE. Project Window This is simply a list of all the forms which make up your VB project. There are several kinds of forms.
Property Window Such things as pushbuttons, scrolling text boxes, pictures boxes and other features of most VB applications allow you to enter parameters which define how these controls work. In VB, these parameters are called properties. Some properties can be entered at design time within the IDE, while others must be entered with code while the program is running.
Forms You add these to your VB

application as they are needed. They are the windows which hold the various controls (buttons, text boxes, etc.) which make up your application.
Code Window Like it's name implies, this is where you type in the code that VB executes. Notice that the heading of the window indicates with which event the code is associated.
2.3.7.1.3
Tec hnic al
Feasibility: 3. Visual Basic 1.0 for Windows was first released on May 20, 1991 at the Windows World convention in Atlanta Georgia. In September 1992, Microsoft announced Microsoft Visual Basic for MS-DOS in Standard and Professional editions. Like Visual Basic for Windows, this version combined the ease of
graphical design with the power and versatility of traditional programming. Developers simply drew the user interface and attached code that responded to events. However, following the release of Windows 3.1 in March 1992 it became apparent that the DOS environment had come to the end of its useful life. The last version of MS-DOS, 6.22, was released in 1994. 4. VB version 2.0 for Windows (November 1992) was faster, more powerful and easier to use than version 1. VB 2 was also available in a freeware student release called the Primer edition. Visual Basic 3.0 (1993) added tools to access and control databases and Object Linking and Embedding (OLE) version 2. It came in Standard and Professional versions. 5. A superset of VB, called Visual Basic for Applications, was released as part of Microsoft Excel 5 and Microsoft Project 4 in 1993. It has since become the internal programming language of the Microsoft Office family of products, and is available for license by other software companies. 6. Visual Basic 4 was released in 1995 and supported the new Windows 95 family of 32-bit operating systems. The Professional Edition could also compile code to run on the older 16-bit Windows 3.x systems. Visual Basic Scripting Edition (VBScript) was also announced in 1995. VBScript is used to write embedded code for inclusion in web pages, although not all web browsers will run VBScript. 7. With the introduction of Visual Basic version 5 in early 1997, 16-bit systems were no longer supported. Between versions 4 and 5, significant changes were made in the user interface. Visual Basic 5 added, among other things, the ability to create true
executables and to create your own custom controls. It also supported Microsoft's Active-X technology. 8. Visual Basic 5 was available in Standard (Learning), Professional and Enterprise Editions. A free edition, called Control Creation Edition, could be downloaded from www.microsoft.com, and was included with many textbooks. Visual Basic 5 was also included as part of a package known as Visual Studio 97. 9. Visual Basic 6 (VB6) was introduced in 1998 and was included as part of a package known as Visual Studio 6.0. VB6 added new capabilities in the areas of data access, Internet features, controls, component creation, language features and wizards. To quote Microsoft's web site, Visual Basic 6.0 features provide graphical, integrated data access to any ODBC or OLE DB data source, and additional database-design tools for Oracle and Microsoft SQL Server-based databases. New Web development features bring the easy-to-use, component-based programming model of Visual Basic to the creation of HTMLand Dynamic HTML (DHTML)-based applications. Many organizations are still using this version today. 10. The newest version of Visual Basic, sometimes referred to as VB7 or Visual Basic .NET, was released in February 2002. This product will be part of Microsoft's .NET software initiative, designed to produce XML-based applications for the Microsoft Internet environment. A Microsoft Web article says, At first glance, it may appear to you that Visual Basic .NET is so radically different from what you know that you will have to learn it all over
again. For more information on Visual Basic .NET, see the article Upgrading from Visual Basic 6.0 on the Microsoft Web site.
2.3.7.2 User friendliness: This project will have user-friendly screens. The screens designed will have very simple functionality for retrieving/ adding/ updating the information.
2.3.7.3 Consistency: The consistency in the proposed system will provide high efficiency due to smaller learning curves and increased data integrity.
2.3.7.4 Compatibility: This project offers great compatibility, as it will be designed with proper methodology, new tools and technology.
1.3.7.5
Reliability & Robustness:

2. Like the BASIC programming language, Visual Basic was
designed to be easily learned and used by beginner

programmers. The language not only allows programmers to create simple GUI applications, but to also develop complex applications. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. 3. Although VB programs can be compiled into native code executables from version 5 onwards, they still require the presence of runtime libraries of approximately 1 MB in size. Runtime libraries are included by default in Windows 2000 and later, however for earlier versions of Windows, i.e. 95/98/NT, runtime libraries must be distributed together with the executable.
4. 5. 6. An empty form in Visual Basic 6. 7. Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be
inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted.
8. Visual Basic can create executables (EXE files), ActiveX
controls, or DLL files, but is primarily used to develop Windows applications and to interface database systems. Dialog boxes with less functionality can be used to provide pop-up capabilities. Controls provide the basic functionality of the application, while programmers can insert additional logic within the appropriate event handlers. For example, a dropdown combination box will automatically display its list and allow the user to select any element. An event handler is called when an item is selected, which can then execute additional code created by the programmer to perform some action based on which element was selected, such as populating a related list.
9. Alternatively, a Visual Basic component can have no user
interface, and instead provide ActiveX objects to other programs via Component Object Model(COM). This allows for server-side processing or an add-in module.
10. The
runtime recovers unused memory using reference counting which depends on variables passing out of scope or being set to "Nothing", resulting in the very common problem of memory leaks. There is a large library of utility objects, and the language provides basic object oriented support. Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table. String comparisons are case sensitive by default.
11. The Visual Basic compiler is shared with other Visual Studio languages (C, C++), but restrictions in the IDE do not allow the creation of some targets (Windows model DLLs) and threading models.
12. 12.3.7.5 2.3.7.6 Performance: The performance of this application will be high because of its optimized design and sound architecture. 2.3.7.7 Flexibility: This project has the flexibility of new languages when needed. It can be updated whenever required. 2.3.8.8 Maintainability: This software is maintainable as there will be user controls and optimized methodology used to build it.
2.4. DOCUMENT APPROVAL The following signatures are required for approval of this document.
Name Mr Ravi Govil Project Guide Professor (Department Computer science Engineering/I .T) Mr. Ravi Govil H.O.D (Department of I.T) of Application
Signature
Date
25/04/2013
25/04/2013
CHAPTER 3 TECHNOLOGICAL ASPECTS Like the BASIC programming language, Visual Basic was designed to be easily learned and used by beginner programmers. The language not only allows programmers to create simple GUI applications, but to also
develop complex applications. Programming in VB is a combination of visually arranging components or controls on a form, specifying attributes and actions of those components, and writing additional lines of code for more functionality. Since default attributes and actions are defined for the components, a simple program can be created without the programmer having to write many lines of code. Performance problems were experienced by earlier versions, but with faster computers and native code compilation this has become less of an issue. Although VB programs can be compiled into native code executables from version 5 onwards, they still require the presence of runtime libraries of approximately 1 MB in size. Runtime libraries are included by default in Windows 2000 and later, however for earlier versions of Windows, i.e. 95/98/NT, runtime libraries must be distributed together with the executable. Forms are created using drag-and-drop techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have attributes and event handlers associated with them. Default values are provided when the control is created, but may be changed by the programmer. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted. Visual Basic can create executables (EXE files), ActiveX controls, or DLL files, but is primarily used to develop Windows applications and to interface database systems. Dialog boxes with less functionality can be used to provide pop-up capabilities. Controls provide the basic functionality of the application, while programmers can insert additional logic within the appropriate event handlers. For example, a drop-down combination box will automatically display its list and allow the user to select any element. An event handler is called when an item is selected, which can then execute additional code created by the programmer to
perform some action based on which element was selected, such as populating a related list. Alternatively, a Visual Basic component can have no user interface, and instead provide ActiveX objects to other programs via Component Object Model(COM). This allows for server-side processing or an add-in module. The runtime recovers unused memory using reference counting which depends on variables passing out of scope or being set to "Nothing", resulting in the very common problem of memory leaks. There is a large library of utility objects, and the language provides basic object oriented support. Unlike many other programming languages, Visual Basic is generally not case sensitive, although it will transform keywords into a standard case configuration and force the case of variable names to conform to the case of the entry within the symbol table. String comparisons are case sensitive by default. The Visual Basic compiler is shared with other Visual Studio languages (C, C++), but restrictions in the IDE do not allow the creation of some targets (Windows model DLLs) and threading models. CHARACTERISTICS Visual Basic has the following traits which differ from C-derived languages:

Statements tend to be terminated with keywords such as "End If", instead of using "{}"s to group statements. Multiple variable assignment is not possible. A = B = C does not imply that the values of A, B and C are equal. The boolean result of "Is B = C?" is stored in A. The result stored in A would therefore be either false or true. Boolean constant True has numeric value 1.[5] This is because the Boolean data type is stored as a 16-bit signed integer. In this construct 1 evaluates to 16 binary 1s (the Boolean value True), and 0 as 16 0s (the Boolean value False). This is apparent when performing a Not operation on a 16 bit signed integer value 0 which will return the integer value 1, in other words True = Not False. This inherent functionality becomes especially useful when performing logical operations on the individual bits of an integer such
Page 32
asAnd, Or, Xor and Not.[6] This definition of True is also consistent with BASIC since the early 1970s Microsoft BASIC implementation and is also related to the characteristics of CPU instructions at the time. Logical and bitwise operators are unified. This is unlike some Cderived languages (such as Perl), which have separate logical and bitwise operators. This again is a traditional feature of BASIC. Variable array base. Arrays are declared by specifying the upper and lower bounds in a way similar to Pascal and Fortran. It is also possible to use the Option Base statement to set the default lower bound. Use of the Option Base statement can lead to confusion when reading Visual Basic code and is best avoided by always explicitly specifying the lower bound of the array. This lower bound is not limited to 0 or 1, because it can also be set by declaration. In this way, both the lower and upper bounds are programmable. In more subscript-limited languages, the lower bound of the array is not variable. This uncommon trait does exist in Visual Basic .NET but not in VBScript. OPTION BASE was introduced by ANSI, with the standard for ANSI Minimal BASIC in the late 1970s.
Relatively strong integration with the Windows operating system and the Component Object Model. The native types for strings and arrays are the dedicated COM types, BSTR and SAFEARRAY. Banker's rounding as the default behavior when converting real numbers to integers with the Round function.[7] ? Round(2.5, 0) gives 2, ? Round(3.5, 0) gives 4. Integers are automatically promoted to reals in expressions involving the normal division operator ( /) so that division of one integer by another produces the intuitively correct result. There is a specific integer divide operator (\) which does truncate. By default, if a variable has not been declared or if no type declaration character is specified, the variable is of type Variant. However this can be changed with Deftype statements such as DefInt, DefBool, DefVar, DefObj, DefStr. There are 12 Deftype statements in total offered by Visual Basic 6.0. The
Page 33
default type may be overridden for a specific declaration by using a special suffix character on the variable name ( # for Double, ! for Single, & for Long, % for Integer, $ for String, and @ for Currency) or using the key phrase As (type). VB can also be set in a mode that only explicitly declared variables can be used with the command Option Explicit. Visual Basic Version Information This document lists brief descriptions of current and older Microsoft development tools for the PC, along with notes and a brief list of features. While you may find older versions of development tools in many places, links to the old/used programming tools sales pages of EMS Professional Software, this page's sponsor, are provided for your convenience. EMS is not affiliated with Microsoft or any other vendor. All terms on this page are trademarks of Microsoft Corporation. Version information for other Microsoft products. Version information for other vendors' products. Visual Basic for DOS Visual Basic 1.0 for Windows Visual Basic 2.0 for Windows Visual Basic 3.0 for Windows Visual Basic 4.0 for Windows Visual Basic 5.0 for Windows Visual Basic 6.0 for Windows
Visual Basic 1.0 for DOS MS Part Numbers: VBDOS 1.0 Std., academic, 3.5": 046-351V100 VBDOS 1.0 Std., 10 license pack, academic, 3.5": 046-499V100 UPGRADE VISUAL BASIC 1.0(DUAL)RSLR: 046-099-100 VBDOS 1.0 Std., 3.5": 046-095V100 VBDOS 1.0 Prof., Upgrade, Academic, 3.5": 203-095-100 VBDOS 1.0 Prof., Upgrade, Direct, 3.5": 203-095-125 VB PRO 1.00 (DUAL) PC NFR: 203-599V100 VBDOS 1.0 Prof., 3.5": 203-095V100 VBDOS 1.0 Prof., 3.5"/5.25": 203-099V100
Visual Basic for DOS Standard
Visual Basic for DOS Professional - For the dual media package, the MS product number is 203-099V100. Includes seven 1.44MB and/or nine 1.2MB diskettes and the following printed materials: Manuals: Programmer's Guide, 658 pages, Document Number DB27591-0792, book rear bar code label: 27591 Reference, 510 pages, Document Number DB27592-0792, book rear bar code label: 27592 Professional Features, 365 pages, Document Number DB32480-0792, book rear bar code label: 32480
Visual Basic 1.0 for Windows MS Part numbers: Std. NFR: 046-550V100 Retail Dual media: 046-050V100 "WINDOWS VB PROTOOLKIT 1.00 (DUAL)": 203-050V100 Programmer's Guide manual, 456 pages, 0191 Part No. 12974 Three 3.5" 720K disks dated 5/10/1991 1:00AM, labeled Disk Assy 046051-004 (and 5 and 6) Visual Basic 1.0 for Windows Standard, Special upgrade Offer. 3.5" low density disks. MS Product number 046-051-060. To qualify for purchase, MS asked that you be a licensed user of Turbo Pascal, Borland C, C++ or Turbo C, Actor, or Smalltalk. System requirements: Windows 3.0 or later running in standard or enhanced mode. 80286 or higher processor. 1MB or memory (2 recommended), floppy and hard disk. CGA, EGA, VGA, 8514/A, Hercules or compatible video adapter, and mouse. Box spine marked 1191 Part No. 27776. Originally published with a $99 suggested retail price. Manuals: (and others?) Programmer's Guide, 0991 Part No. 26489 Language Reference, 0991 Part No. 26490
Visual Basic 1.0 for Windows Professional, Competitive Upgrade
Visual Basic with Professional Toolkit (VB 1.00 with both 3.5" and 5.25" media)

Visual Basic 2.0 for Windows MS Part numbers: Visual Basic 2.0 Standard, 3.5": 046-051V200 UPGRADE WIN VB PRO 2.0 (5.25) RSLR: 203-051-080 WINDOWS VB PRO 2.00 (5.25): 203-050V200 WINDOWS VB PRO 2.00 (3.5): 203-051V200 Visual Basic 2.0 Standard, Gateway 2000 Edition - Six 1.2MB diskettes.
Visual Basic 2.0 Standard, retail 3.5" package. MS part number 046051V200
Visual Basic 2.0 Professional, Special Upgrade - MS product number for 3.5" version: 203-051-080. No disk scan or enforcement, but license requires you to have a Visual Basic 1.0 for Windows, Borland C++, Borland Turbo C++ for Windows, Borland Turbo Pascal, or Borland Turbo Pascal for Windows. Contains eight 1.2MB diskettes plus the following printed materials: Professional Features, Bar code label 34892 Programmer's Guide, Bar code label 34887 Language Reference, Bar code label 34888 License card "UPGRADE WIN VB PRO 2.0 (5.25) RSLR" Registration card
Visual Basic 2.0 Professional - MS part number 203-051V200. White label on top of retail sleeve reads" WINDOWS VB PRO 2.00 (3.5)". Rear 0992 Part No. 36889. Includes the following printed materials: Professional Features, 34892 Programmer's Guide, 34887 Language Reference, 34888 Visual Basic 3.0 for Windows MS Part numbers: VB3 Std. Competitive Upgrade with "LRN" suffix, 3.5": 046-751-112 VB Std. 3.5", full retail: 046-051V300 also 046-751V300 (LRN additions?) WIN/VB 3.00 (1.44MB)AE SINGLE USR: 046-351V300 VB3 Pro., Academic, 3.5": 203-351V300 VB 3.00, 3.5", Learning Edition, 046-751V300 VB3 Pro, version upgrade, 3.5", 203-051-102 UPDATE WIN/VB PRO 3.00 (1.44MB)DIR, 203-051-300A (direct box, license agreement looks like international) VB3 Pro, 3.5", 203-051V300 VB3 Pro w Office DK, 3.5"/CD, Special Upgrade, 203-851-101 VB3 Pro w Office DK, 3.5"/CD, Not for Resale, 2035851V300 VB3 Pro w Office DK, 3.5"/CD, Academic, 203-351V300 VB3 Pro w Office DK, 3.5"/CD, full retail, 203-851V300 VB3 Pro w Office DK, CD/CD, full retail, 203-052V300 Visual Basic 3.0 Standard, version upgrade - No disk scan or enforcement. Requires Windows 3.0 or later, 2MB of available memory for design environment, one high density disk drive and a hard disk with 12MB available. EGA or higher resolution monitor. MS mouse or compatible pointing device. Includes three 1.44MB diskettes and the following printer materials: Component Objects and Companion Products for Visual Basic, Winter/Spring 1994, Part No. 55439 Support and Service for Microsoft Visual Basic brochure. 1292 Part no. 50510 CompuServe offer License agreement, 0294 Part No. 57117, inkjet marked "UPDATE WIN/VB 3.00(1.44MB) DIRECT"
Page 39
Diskette and Upgrade order form, 0394 Part No. 55566 Microsoft Support Network contact info card, 0993 Part No. 55277 Inside Visual Basic for Windows newsletter offer, 59476 Visual Basic Programmer's Journal magazine offer, Part #52753 Manuals: Programmer's Guide, 55959 -orProgrammer's Guide, 711 pages, Document Number DB51410-0493, rear bar code label 51410 Language Reference, 674 pages, Document Number DB51411-0493, rear bar code label 51411

Visual Basic 3.0 Standard competitive upgrade version - No disk scan or enforcement, but license requires you to have a "Microsoft language product, Borland language product, or other Windows based programming products." Requires Windows 3.0 or later, 2MB of available memory for design environment, one high density disk drive and a hard disk with 12MB available. EGA or higher resolution monitor. MS mouse or compatible pointing device.
Visual Basic 3.0 Standard - MS part number 046-051V300
Visual Basic 3.0 Std. Academic Edition
VB3 Standard "Propeller Head" packaging. Visual Basic 3.0 "LRN", I think this is a learning edition, but don't know what its relationship is to later academic licensing.
Visual Basic 3.0 Professional, version upgrade: You qualify for the upgrade if you own Visual Basic Programming System with Professional Toolkit (VB1 Pro), VB2 Pro, or Professional Toolkit for Visual Basic. Visual Basic 3.0 Professional with Office DK on 3.5" and CD. Special upgrade. MS product number 203-851-101. For users of Microsoft language products, Borland language products, other Windows-based programming products, Microsoft Access, Excel, or Office. Box spine rear bottom marked 0294 Part No. 55029 Visual Basic 3.0 Professional with Office DK on 3.5" and CD. "Not for Resale" package. Front of box has transparent sticker "PROMOTIONAL SAMPLE NOT FOR RESALE". White label on top of box says "WIN/VB3.0PRO(3.5/CD)NFR" with product number "2035851V300" Visual Basic 3.0 Professional 3.5" and Office DK, Academic Edition, MS Part number 203-351V300 Visual Basic 3.0 Professional - Nine 1.44MB diskettes with files dated 04/28/93 00:00. First diskette, labeled Disk Assy 203-051-025, gets written ID of first user in file vbsetup.ini. Includes the following manuals: Professional Features Book1, 51412 Professional Features Book2, 52324 Language Reference, 51411
Programmer's Office Developer's Kit, 55428

Guide,
55959
Visual Basic 3.0 Professional on CD-ROM, with SDK on CD-ROM. Full retail version has Microsoft product ID 203-052V300 on white label on top of box. Visual Basic 4.0 for Windows MS part numbers: 4.0, CD: 046-051V400 VB 4.0STD/WIN(CD): 046-056V400 4.0 Professional, Academic, 3.5": 203-356V400 4.0 Professional, Academic, CD: 203-???V400 VB PRN 4.0 WIN EN NA CD AE NA ONLY: 203-00044 4.0 Professional Easy Fulfillment Document Set: 203-055-045 4.0 Professional Upgrade, CD: 203-054-205, also 203-056-205 4.0 Professional w Office DK, Upgrade, CD: 203-851-101 4.0 Professional Competitive Upgrade, CD: 203-054-215, also 203-056215 4.0 Professional, CD: 203-054V400 also 203-056V400 VB 4.0PRO/WIN(CD)NFR: 203-556V400 4.0 Enterprise Upgrade, CD: 2034155-400 4.0 Enterprise, CD: 2031056V400 4.0 Enterprise, NFR, CD: 2031556U400 MASTERING VISUAL BASIC 4.00: 007-056-210 Visual Basic 4.0 Standard (buy it) VB 4.0STD/WIN(CD): 046-056V400 System requirements: 386DX or later processor. Windows 95 or NT 3.51 or later OS. 6MB of RAM (8 recommended) or 16MB for NT. 20-60MB disk space. Consists of the following: Retail box 0795 Part No. 65163. CD in jewel case with orange CD Key on rear insert 0895 Part No. 64510. Front insert 0895 Part No. 64514. CD face Version 4.0, Disc Assy. 046-056-006, 0296 Part No. 69913. License agreement 51880002.DOC, 0895 Part no. 61798. "VERSION 4.00, STANDARD EDITION, LICENSES: 1"
Page 43
Professional edition offer, 0895 Part No. 66889 Registration card, 0995 Part No. 67821 Manuals: Programmer's Guide, 857 pages, Document No. 58513-TR6, 58513 (I'm not sure about this next one. It was in the box we examined.) Teach yourself Visual Basic 4 for Windows 95, with 3.5" disk, ISBN 155828-399-4

Visual Basic 4.0 Professional version upgrade - MS part number for 3.5/CD w ODK 203-851-101. Box sleeve 0795 Part No. 65167. Top of box reads "UPDATE VB 4.0PRO/WIN(CD)PRO/PRO RSL". Will search your hard disk and/or floppy drive to confirm your eligibility. To be eligible, you must be a licensed user of Visual Basic Professional version 2.0 or 3.0. CD jewel case rear insert 0895 Part No. 66295. Jewel case font insert rear 0895 Part No. 66296. CD face reads Version 4.0, Disc Assy. 203-056-006, 0895 Part No.66147. Dates of directories in CD root are 8/24/95 3:31:48pm. Includes the following printed materials: Registration card, 0995 Part No. 67821 License card, printed "VERSION 4.00, PROFESSIONAL EDITION, LICENSES: 1", 0895 Part No. 61798 Microsoft Visual Basic 4.0 Roadmap, 66931 1.44 MB Disk Offer, 0695 Part No. 66302, Kit No. 203-054-045 Enterprise Edition info card, 0895 Part No. 66890 Developer Network offer, 66858 Visual Basic Programmer's Journal offer, 61882 Component Objects and Companion Products for Visual Basic catalog, Volume 5, Winter/Spring 1995, 60087 Manuals: Crystal Reports for Visual Basic User's Manual, 143 pages, Document No. DD58500-0795, 58500 Professional Features, Document No. DB58499-0795, 58499 Language Reference, 1064 pages, Document Number DB58514-0795, 58514 Programmer's Guide, 857 pages, Document No. 58513-TR6, 58513
VB 4 Pro Academic
Visual Basic 4.0 Professional competitive upgrade version - Software will scan your hard and floppy drives to ensure you own one of the following: a licensed user of one of the following products: Microsoft Visual Basic, Standard Edition, version 2.0, 3.0, or 4.0, Microsoft Visual C++ version 1. 5 or later, Microsoft Visual FoxPro version 3.0 or later, Microsoft FoxPro version 2. 6 for Windows, Microsoft FORTRAN Power Station version 4.0 or later, Microsoft Office Standard or Professional version 4. 0 or later, Microsoft Access version 2. 0 or later, Microsoft Excel version 5.0 or later, Borland Delphi, Borland dBASE for Windows, or Powersoft Power Builder 3 or 4. CD face is labeled Disc Assy.203-056-006, 0895 Part No.66147 Visual Basic 4.0 Professional, CD. MS Part number: 203-056V400
Visual Basic 4.0 Enterprise - MS product number 2031056V400. Includes the following materials: Registration card (part number unknown) License card, printed "VERSION 4.00, ENTERPRISE EDITION, LICENSES: 1", 0895 Part No. 61798 License card (probably for Visual SourceSafe 4.0), printed "VERSION 4.00, LICENSES: 1", 0195 Part No. 62720 Microsoft Visual Basic 4.0 Roadmap, 66931 Microsoft Visual SourceSafe 4.0 Quick Reference Card, 64666 Visual Basic Programmer's Journal offer, 61882 Component Objects and Companion Products for Visual Basic catalog, Volume 7, Winter 1996/1997, 93143 Inside Visual Basic for Windows magazine offer, 61884 CD jewel case rear insert, 0895 Part No. 64579, bar code 64579 CD jewel case front insert, 0895 Part No. 64577 CD face: Disc Assy. 2031056-010, 0296 Part No.69944 Manuals: Crystal Reports for Visual Basic User's Manual, 143 pages, Document No. DD58500-0795, 58500 Professional Features, Document No. DB58499-0795, 58499 Language Reference, 1064 pages, Document Number DB58514-0795, 58514 Programmer's Guide, 857 pages, Document No. 58513-TR6, 58513 Microsoft Visual SourceSafe User's Guide, 204 pages, Document No. D64664-0795, 64664 Building Client/Server Applications with Visual Basic, 275 pages, Document No. DD59950-0795, 59950 Visual Basic 5.0 for Windows MS Part numbers: Learning Edition: 046-00067 "VB STD 5.0 W32 EN NA CD LRN COM" Professional, AE: 203-00100 VB PRO 5.0 W32 EN NA CD COM: 203-00102 Enterprise, Upgrade, CD: 361-00088 Enterprise NFR: 361-00090 "VB ENT 5.0 W32 EN NA CD NFR COM" Enterprise International Academic: "VB ENTERPRISE 5.0 W32 EN INTL CD AE COM: 361-00170
Page 46
Buy it Learning Edition. 046-00067 "VB STD 5.0 W32 EN NA CD LRN COM" Retail box sleeve 1196 Part No. 94214. License agreement card is printed: VERSION 5.00, LEARNING EDITION, LICENSES: 1", 0197 Part No. 94186 Registration card assembly 0897 Part No. X03-41835 Rebate coupon 0297 Part No. 94216 Installation card, 93010 Visual Basic Programmer's Journal offer, Part No. 93144 Microsoft Office and Visual Basic for Applications Developer offer, PART # X03-22916 Component Objects and Companion Products for Visual Basic, Summer/Fall 1997, volume 8, Part No. X03-09311 License card, Part No. 98177 Mastering Visual Basic 5.0 offer, 1196 Part No. 93336 CD jewel case front insert 93009, rear insert 93008, with CD key CD, 1196 Part No. 93007 Learn visual Basic Now CD, Part No. 93006 Visual Basic 5.0 Professional competitive upgrade version - May search your disk for competitive software. License requires you to own one of the following: Visual Basic 3 or 4, Visual C++ 1.5 or later, Visual FoxPro 3.0 or later, Fortran PowerStation 4.0 or later, Office97 Developer Edition, Delphi, dBASE for Windows, PowerBuilder 3, 4 or 5, Oracle PowerObjects or Developer/2000, or Borland C++. Visual Basic 5.0 Enterprise Edition (buy it)
Page 47
The international academic version includes: Retail box sleeve, 1196 Part No. 93025 with product label "VB ENTERPRISE 5.0 W32 EN INTL CD AE COM: 361-00170" Media: VB 5 Enterprise CD in jewel case with key code. CD marked 1196 Part No. 93027. Front insert 93029. Rear insert 1196 Part No. 93028 SQL Server 6.5 Developer Edition CD paper window sleeve, 0796 Part No. 92636 Transaction Server Developer Edition in jewel case with key, CD marked 1296 Part No. 93159, Front insert is a multi-page booklet 1296 Part No. 93157. Rear insert 1296 part no. 93158 MSDN Library Special Edition, CD in jewel case marked 0197 Part No. 97449, front insert 0197 Part No. 97453, rear insert 0197 Part No. 97448 License agreement documents: End-User License Agreement, "VERSION 5.00, ENTERPRISE EDITION AE, LICENSES: 1", 0197 Part No. 94186 EULA for SQL Server 6.5 Developer Edition, marked "AE, LICENSES: 1", 0297 Part No. X03-09013 EUAL for Microsoft Database Tools, 0397 Part No. X03-17069 Addendum to server license for transaction Server 1.0, Developer Edition, 0297 Part No. X03-09070 License agreement for SourceSafe, labeled "VERSION 5.00 AE, LICENSES: 1", 0295 Part No. 62720 Printed manuals: Guide to Data Access Objects, Crystal Reports for Visual Basic: Document No. 93015 Component Tools Guide, Document No. 93014 Language Reference, 1064 pages, Document No. DB58514-0795 Visual Basic Guide to Building Client/Server, 366 pages, Document No. 93026 Visual Basic Programmer's Guide, 898 pages, Document No. 93011 Visual SourceSafe User's Guide, 247 pages, Document No. DB928890196 Other printed materials: Microsoft Transaction Server, Developer Edition feature card, 0197 Part No. 90300 SourceSafe 5.0 Quick Reference Card, bar code label 94752 Visual Database Tools Quick Reference Card, bar code label 92944
Page 48
Limited Warranties booklet, bar code label 61002 Registration card assembly, Part Number 94206, folding envelope 36100170 Mastering Visual Basic brochure, 1196 Part No. 93336

Visual Basic 6.0 for Windows (buy it) MS part numbers: US: VB PRO 6.0 WIN32 ENGLISH NA CD REFR: 203-00768 Visual Basic 6 Programming Starter Kit by McMillan: special limited version Academic: Enterprise - 361-00438, Professional (with NT 4.0 workstation) - 203-00506, Learning - 046-00392. Professional w SQL Dev. Ed.? 203-00769 Academic with W2K Readiness Kit: Professional - 203-00769 Upgrade: Enterprise -361-00441, Professional 203-00509 Full: Enterprise - 361-00422, Professional - 203-00490, Learning - 04600378 International: Upgrade: Professional, English - 203-00510, Spanish - 203-00532, Enterprise, Spanish 361-00446 Full: Enterprise, English - 361-00423, Spanish - 361-00437, Professional, English - 203-00491, Spanish - 203-00505, Standard/Learning, English - 046-00379 Visual Basic - synopsis Judson McClendon judmc123@bellsouth.net (remove numbers) Sun Valley Systems http://personal.bhm.bellsouth.net/~judmc When Microsoft and IBM split the blanket over OS/2, Microsoft dusted off the dinky old toy which was Windows 2.x, and did a serious rewrite as Windows 3.0. Microsoft needed development languages for Windows fast, because not everybody had enough hair on their chests to tackle Windows API development directly C. Working on two fronts, Microsoft released Visual Basic for DOS and Visual Basic for Windows. VB DOS provided not only a QuickBasic compatible platform, but a character based, interrupt driven platform similar to Windows programs, specifically VB Windows. VB DOS was never enhanced, because Microsoft was determined to abandon the DOS platform as soon as
Page 49
possible. VB DOS was only a hook to get QuickBasic programmers acclimated to the idea of Windows programming. With Windows 95, Microsoft released VB 4.0 whichsupported (in the professional version) both the older 16 bit Windows 3.x API, and the newer 32 bit Windows 95 API. The 16 bit option was dropped with VB 5.0. Visual Basic 6.0 is the latest version. Though enormously powerful, Visual Basic is also enormously more complex to learn and master than QuickBasic, QBasic or PDS. You can actually learn to do some easy stuff in VB quicker than you might with QBasic. But to really know VB takes a tremendous amount of effort and time
3.5 FLOW CHARTS A flowchart is a type of diagram that represents an algorithm or process, showing the steps as boxes of various kinds, and their order by
connecting these with arrows. This diagrammatic representation can give a step-by-step solution to a given problem. Process operations are represented in these boxes, and arrows connecting them represent flow of control. Data flows are not typically represented in a flowchart, in contrast with data flow diagrams; rather, they are implied by the sequencing of operations. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields. Flow charts are simple diagrams that map out a process so that it can easily be communicated to other people. To draw a flowchart, brainstorm the tasks and decisions made during a process, and write them down in order. Then map these out in flow chart format using appropriate symbols for the start and end of a process, for actions to be taken and for decisions to be made. Finally, challenge your flow chart to make sure that it's an accurate representation of the process, and that that it represents the most efficient way of doing the job. A flow chart can therefore be used to: 1. Define and analyze processes. 2. Build a step-by-step picture of the process for analysis, discussion, or Communication 3. Define, standardize or find areas for improvement in a process
3.5.1 OVERVIEW Flowcharts are used in designing and documenting complex processes. Like other types of diagram, they help visualize what is going on and thereby help the viewer to understand a process, and perhaps also find flaws, bottlenecks, and other less-obvious features within it. There are many different types of flowcharts, and each type has its own repertoire of boxes and notational conventions. The two most common types of boxes in a flowchart are: 1. A processing step, usually called activity, and denoted as a rectangular box 2. A decision, usually denoted as a diamond. A flowchart is described as "cross-functional" when the page is divided into different swim lanes describing the control of different organizational units. A symbol appearing in a particular "lane" is within the control of that organizational unit. This technique allows the author to locate the responsibility for performing an action or making a decision correctly, showing the responsibility of each organizational unit for different parts of a single process. Flowcharts depict certain aspects of processes and they are usually complemented by other types of diagram. For instance, Kaoru Ishikawa defined the flowchart as one of the seven basic tools of quality control, next to the histogram, Pareto chart, check sheet, control chart, cause-andeffect diagram, and the scatter diagram. Similarly, in UML, a standard concept-modeling notation used in software development, the activity
diagram, which is a type of flowchart, is just one of many different diagram types. Nassi-Shneiderman diagrams are an alternative notation for process flow. Common alternate names include: flowchart, process flow chart, functional flow chart, process map, process chart, functional process chart, business process model, process model, process flow diagram, work flow diagram, business flow diagram.
3.5.2 FLOWCHART SYMBOLS Different flow chart symbols have different meanings. The most common flow chart symbols are: 1. Terminator: An oval flow chart shape indicating the start or end of the process. 2. Process: A rectangular flow chart shape indicating a normal process flow step. 3. Decision: A diamond flow chart shape indication a branch in the process flow. 4. Connector: A small, labeled, circular flow chart shape used to indicate a jump in the process flow. 5. Data:
A parallelogram that indicates data input or output (I/O) for a process. 6. Document: Used to indicate a document or report 7. Junction Symbol: Generally represented with a black blob, showing where multiple control flows converge in a single exit flow. A junction symbol will have more than one arrow coming into it, but only one going out. In simple cases, one may simply have an arrow point to another arrow instead. These are useful to represent an iterative process (what in Computer Science is called a loop). A loop may, for example, consist of a connector where control first enters, processing steps, a conditional with one arrow exiting the loop, and one going back to the connector. For additional clarity, wherever two lines accidentally cross in the drawing, one of them may be drawn with a small semicircle over the other, showing that no junction is intended.
8. Labeled connectors:
Represented by an identifying label inside a circle. Labeled connectors are used in complex or multi-sheet diagrams to substitute for arrows. For each label, the "outflow"connector must always be unique, but there may be any number of "inflow" connectors. In this case, a junction in control flow is implied.
9. Concurrency Symbol: Represented by a double transverse line with any number of entry and exit arrows. These symbols are used whenever two or more control flows must operate simultaneously. The exit flows are activated concurrently when all of the entry flows have reached the concurrency symbol.
3.5.3 TYPES OF FLOWCHART Sterneckert (2003) suggested that flowcharts can be modelled from the perspective of different user groups (such as managers, system analysts and clerks) and that there are four general types: 1. Document flowcharts, showing controls over a document-flow through a system 2. Data flowcharts, showing controls over a data flows in a system 3. System flowcharts showing controls at a physical or resource level
3.6 CLASS DIAGRAM In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations(or)methods and the relationships between the classes. The class diagram is the main building block in object
oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. The classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed. In the class diagram these classes are represented with boxes which contain three parts:
A class with three sections: 1. The upper part holds the name of the class 2. The middle part contains the attributes of the class
3. The bottom part gives the methods or operations the class can take or undertake In the system design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the static relations between those objects. With detailed modeling, the classes of the conceptual design are often split into a number of subclasses. In order to further describe the behavior of systems, these class diagrams can be complemented by state diagram or UML state machine. Also instead of class diagrams Object role modeling can be used if you just want to model the classes and their relationships.
3.6.1 MEMBERS: UML provides mechanisms to represent class members, such as attributes and methods, and additional information about them. Visibility To specify the visibility of a class member (i.e., any attribute or method) there are the following notations that must be placed before the member's name:
+ -
Public Private
# ~ /
Protected Package Derived
underline Static
3.6.2 SCOPE: The UML specifies two types of scope for members: instance and classifier.[3] In the case of instance members, the scope is a specific instance. For attributes, it means that its value can vary between instances. For methods, it means that its invocation affects the instance state, in other words, affects the instance attributes. Otherwise, in the classifier member, the scope is the class. For attributes, it means that its value is equal for all instances. For methods, it means that its invocation does not affect the instance state. Classifier members are commonly recognized as "static" in many programming languages. To indicate that a member has the classifier scope, its name must be underlined. Otherwise, as default, the instance scope is considered.
3.6.3 RELATIONSHIPS
A relationship is a general term covering the specific types of logical connections found on class and objects diagrams. UML shows the following relationships: 3.6.4 Instance Level Relationships 3.6.4.1 External links A Link is the basic relationship among objects. It is represented as a line connecting two or more object boxes. It can be shown on an object diagram or class diagram. A link is an instance of an association. In other words, it creates a relationship between two classes. 3.6.4.2 Association
Class diagram example of association between two classes
An Association represents a family of links. Binary associations (with two ends) are normally represented as a line, with each end connected to a class box. Higher order associations can be drawn with more than two ends. In such cases, the ends are connected to a central diamond. An association can be named, and the ends of an association can be adorned with role names, ownership indicators, multiplicity, visibility, and other properties. There are five different types of association. BiPAYROLL MANAGEMENT SYSTEM Page 59
directional and uni-directional associations are the most common ones. For instance, a flight class is associated with a plane class bidirectionally. Associations can only be shown on class diagrams. Association represents the static relationship shared among the objects of two classes. Example: "department offers courses", is an association relation. 3.6.4.3 Aggregation
Class diagram showing Aggregation between two classes Aggregation is a variant of the "has a" or association relationship; aggregation is more specific than association. It is an association that represents a part-whole or part-of relationship. As a type of association, an aggregation can be named and have the same adornments that an association can. However, an aggregation may not involve more than two classes. Aggregation can occur when a class is a collection or container of other classes, but where the contained classes do not have a strong life cycle dependency on the containeressentially, if the container is destroyed, its contents are not.
In UML, it is graphically represented as a hollow diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
3.6.4.4 Composition
Class diagram showing Composition between two classes at top and Aggregation between two classes at bottom Composition is a stronger variant of the "owns a" or association relationship; composition is more specific than aggregation. Composition usually has a strong life cycle dependency between instances of the container class and instances of the contained class(es): If the container is destroyed, normally every instance that it contains is destroyed as well. Note that a part can (where allowed) be removed from a composite before the composite is deleted, and thus not be deleted as part of the composite. The UML graphical representation of a composition relationship is a filled diamond shape on the containing class end of the tree of lines that connect contained class(es) to the containing class.
3.6.5 Class Level Relationships 3.6.5.1 Generalization
Class diagram showing generalization between one superclass and two subclasses The Generalization relationship indicates that one of the two related classes (the subclass) is considered to be a specialized form of the other (the super type) and superclass is considered as 'Generalization' of subclass. In practice, this means that any instance of the subtype is also an instance of the superclass. An exemplary tree of generalizations of this form is found inbinomial nomenclature: human beings are a subclass of simian, which are a subclass of mammal, and so on. The relationship is most easily understood by the phrase 'an A is a B' (a human is a mammal, a mammal is an animal). The UML graphical representation of a Generalization is a
hollow triangle shape on the superclass end of the line (or tree of lines) that connects it to one or more subtypes. The generalization relationship is also known as the inheritance or "is a" relationship. The superclass in the generalization relationship is also
known
as
the "parent", superclass, base class, derived
class,
or base
type. class,
The subtype in the specialization relationship is also known as the "child", subclass, derived type, inheriting or inheriting type. Note that this relationship bears no resemblance to the biological parent/child relationship: the use of these terms is extremely common, but can be misleading. Generalization-Specialization relationship A is a type of B E. g. "an oak is a type of tree", "an automobile is a type of vehicle" Generalization can only be shown on class diagrams and on Use case diagrams.
3.6.5.2 Realization In UML modeling, a realization relationship is a relationship between two model elements, in which one model element (the client) realizes (implements or executes) the behavior that the other model element (the supplier) specifies. A realization is indicated by a dashed line with an unfilled arrowhead towards the supplier.
Realizations can only be shown on class or component diagrams. A realization is a relationship between classes, interfaces, components, and packages that connects a client element with a supplier element. A
realization relationship between classes and interfaces and between components and interfaces shows that the class realizes the operations offered by the interface. 3.6.5.3 General Relationship
Class diagram showing dependency between "Car" class and "Wheel" class
3.6.5.4 Dependency Dependency is a weaker form of relationship which indicates that one class depends on another because it uses it at some point of time. Dependency exists if a class is a parameter variable or local variable of a method of another class. 3.6.5.5 Multiplicity The association relationship indicates that (at least) one of the two related classes makes reference to the other. In contrast with the generalization relationship, this is most easily understood through the phrase 'A has a B' (a mother cat has kittens, kittens have a mother cat).
The UML representation of an association is a line with an optional arrowhead indicating the role of the object(s) in the relationship, and an optional notation at each end indicating the multiplicity of instances of that entity (the number of objects that participate in the association).
CHAPTER 4 SYSTEM DESIGN
Project File Formats

Microsoft Visual Basic utilizes and creates a number of files at both design and run time. Which files will be required by your project or application depends upon its scope and functionality.
Design-time and Miscellaneous Files

The following table lists all the design-time and miscellaneous other files that may be produced when you develop an application: Extension Description
.bas .cls .ctl .ctx .frm .frx .log .vbp
Basic module Class module User Control file User Control binary file Form file Binary form file Log file for load errors Visual Basic project file
Run-Time Files
When you compile your application, all the necessary design-time files are included in the run-time executable files. Run-time files are listed in the following table: Extension .dll .exe .ocx Description In-process ActiveX component Executable component file or ActiveX
ActiveX control
Software design focuses on distinct attributes of program: data structure, software architecture, interface representation, and procedural detail. According to requirement, the design is documented. The design process translates requirements into a representation of the software that can be assessed for quality before coding begins. The design must be translated into a machine-readable form, this is called code generation step. The design phase is the first step while moving from the problem domain to solution domain. The aim of this phase is to produce a model or a representation of the system, which is useful to have an overall look of the system without even developing the entire system. This model of the system is a plan for developing the system. There are three characteristics for the evaluation of a good design. 1. The design should implement all the requirements of the user, which are specified in the SRS and it must accommodate all the requirements that may not be specified by the Recruiter in the analysis phase. 2. The design should be readable and understandable for the people who involve in developing and testing the system. 3. The design should provide a complete picture of the system, addressing the data functional domains from the implementation perspective.
4.1 DESIGN METHODOLOGY: When solving a small problem, the entire problem can be tackled at once. The complexity of large problems and limitations of human minds do not allow large problems to be treated as huge monoliths. For software design, the goal is to divide the problem into manageably small phases that can be solved separately. However, the different phases cannot be entirely independent of each other, as they together form the system. The different phases have to co-operate and communicate in order to solve the larger problem.
CHAPTER 7 SCREEN SHOTS
Fig 7.1 Main Page
Administrator Screens
CHAPTER 10 CONCLUSION Visual Basic Enterprise Edition The Enterprise edition allows professionals to create robust distributed applications in a team setting. It includes all the features of the Professional edition, plus Back Office tools such as SQL Server, Microsoft Transaction Server, Internet Information Server, Visual SourceSafe, SNA Server, and more. Printed documentation provided with the Enterprise edition includes the Visual Studio Enterprise Features book plus Microsoft Developer Network CDs containing full online documentation. Visual Basic Professional Edition The Professional edition provides computer professionals with a fullfeatured set of tools for developing solutions for others. It includes all the features of the Learning edition, plus additional ActiveX controls, the Internet Information Server Application Designer, Integrated Data Tools and Data Environment, and the Dynamic HTML Page Designer. Documentation provided with the Professional edition includes the Visual Studio Professional Features book plus Microsoft Developer Network CDs containing full online documentation.
Visual Basic Learning Edition The Visual Basic Learning edition allows programmers to easily create powerful applications for Microsoft Windows and Windows NT. It includes all intrinsic controls, plus grid, tab, and data-bound controls. Documentation provided with this edition includes Learn VB Now (a multimedia CD-ROM title), plus Microsoft Developer Network CDs containing full online documentation. Integrated development environment IDEs typically present a single program in which all development is done. This program typically provides many features for authoring, modifying, compiling, deploying and debugging software. The aim is to abstract the configuration necessary to piece together command line utilities in a cohesive unit, which theoretically reduces the time to learn a language, and increases developer productivity. It is also thought that the tight integration of development tasks can further increase productivity. For example, code can be compiled while being written, providing instant feedback on syntax errors. While most modern IDEs are graphical. An IDE normally consists of:

a source code editor a compiler and/or an interpreter build automation tools a debugger
CHAPTER 11 FUTURE SCOPE A computer program is an organized list of instructions that, when executed, causes the computer to behave in a predetermined manner. Without programs, computers are useless.Therefore, programming means designing or creating a set of instructions to ask the computer to carry out certain jobs which normally are very much faster than human beings can do.
Event-Driven Programming
In an event-driven application, the code doesn't follow a predetermined path it executes different code sections in response to events. Events can be triggered by the user's actions, by messages from the system or other applications, or even from the application itself. The sequence of these events determines the sequence in which the code executes, thus the path through the application's code differs each time the program runs.
What is an Enterprise Application?

An enterprise application is a business application, obviously. As most people use the term, it is a big business application. In todays corporate environment, enterprise applications are complex, scalable, distributed, component-based, and mission-critical. They may be deployed on a variety of platforms across corporate networks, intranets, or the Internet. They are data-centric, userfriendly, and must meet stringent requirements for security, administration, and maintenance. In short, they are highly complex systems.

VB Final Report

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VB Final Report

Transféré par

Droits d'auteur :

Formats disponibles

CHAPTER 1 OBJECTIVE

PAYROLL MANAGEMENT SYSTEM Page 1

PAYROLL MANAGEMENT SYSTEM Page 2

PAYROLL MANAGEMENT SYSTEM Page 4

PAYROLL MANAGEMENT SYSTEM Page 6

PAYROLL MANAGEMENT SYSTEM Page 7

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM Page 11

3. Memory: 512 MB or more 4. Screen Resolution: 1024x768 pixels or higher

2.3.7.1.1 Economic Feasibility:

Evolution of Visual Basic

PAYROLL MANAGEMENT SYSTEM Page 17

PAYROLL MANAGEMENT SYSTEM Page 18

Visual Basic Version Summary.

Forms You add these to your VB

PAYROLL MANAGEMENT SYSTEM Page 24

Reliability & Robustness:

designed to be easily learned and used by beginner

PAYROLL MANAGEMENT SYSTEM Page 29

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM Page 34

Visual Basic for DOS Standard

PAYROLL MANAGEMENT SYSTEM Page 35

Visual Basic 1.0 for Windows Professional, Competitive Upgrade

PAYROLL MANAGEMENT SYSTEM Page 36

PAYROLL MANAGEMENT SYSTEM Page 37

PAYROLL MANAGEMENT SYSTEM Page 38

PAYROLL MANAGEMENT SYSTEM

Visual Basic 3.0 Standard - MS part number 046-051V300

PAYROLL MANAGEMENT SYSTEM Page 40

Visual Basic 3.0 Std. Academic Edition

PAYROLL MANAGEMENT SYSTEM Page 41

PAYROLL MANAGEMENT SYSTEM Page 42

Programmer's Office Developer's Kit, 55428

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM Page 44

PAYROLL MANAGEMENT SYSTEM Page 45

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM

PAYROLL MANAGEMENT SYSTEM Page 51

PAYROLL MANAGEMENT SYSTEM Page 55

PAYROLL MANAGEMENT SYSTEM Page 56

PAYROLL MANAGEMENT SYSTEM Page 57

Protected Package Derived

PAYROLL MANAGEMENT SYSTEM Page 58

Class diagram example of association between two classes

PAYROLL MANAGEMENT SYSTEM Page 60

PAYROLL MANAGEMENT SYSTEM Page 61

3.6.5 Class Level Relationships 3.6.5.1 Generalization

the "parent", superclass, base class, derived

PAYROLL MANAGEMENT SYSTEM Page 64

CHAPTER 4 SYSTEM DESIGN

Project File Formats

Design-time and Miscellaneous Files

PAYROLL MANAGEMENT SYSTEM Page 65

.bas .cls .ctl .ctx .frm .frx .log .vbp

PAYROLL MANAGEMENT SYSTEM Page 66

PAYROLL MANAGEMENT SYSTEM Page 67

PAYROLL MANAGEMENT SYSTEM Page 68

CHAPTER 7 SCREEN SHOTS