|
| Home | Website Design | WordPress Blogs | eCommerce | Programming | Hosting | Portfolio | Resources | Site Map | Blog | Contact Us |
|
Home >> Library & Articles >> Database Application Development Basics
Library & ArticlesDatabase Application Development BasicsThis is a very simplified explanation of the key elements of database application development. It is intended to provide a quick summary of concepts to individuals who are new to the process. Database Application Development Tools In today's market, database applications are constructed using one or more database application tools. There are two distinct parts to these applications that perform very different functions:
Many of the development applications come with a built-in or native database engine. Some of them are designed to use whatever database engine is preferred or to use multiple database formats. The more sophisticated applications are designed to use ODBC and other means to connect to other proprietary database engines. Click here for a more detailed explanation of databases and ODBC.
Database Development During development, the programmers will design and program a set of database tables or files to store the desired information. Relationships between the different tables or files will be established along with rules to ensure that the data entered is valid. The result is a proprietary database design. Once the tables or files have been created, the user interfaces are designed. This includes the graphical interface that end-users use to add, change and view the information stored in the database files. This interface is often referred to as a GUI - Graphical User Interface. Most of the interface design is accomplished by using the database development application's built-in functions, which allows the designer to drag and drop elements such as buttons, labels, text entry boxes, pull-down menus, etc. onto forms. Most of the source code that produces the bare-bones interface is automatically generated by the development application. With the bare-bones interface in place, any source code required to manipulate, validate and organize, display or calculate the data is written and added to the user interface. Click here to see a sample user interface that has custom data entry fields, menu and toolbars. Most database application designs also include designing specific reports that can be viewed or printed. The design of the interface and reports, and the accompanying source code written for the interface is proprietary.
Compiled Proprietary Application During the development phase, the source code and interface design editing functions are exposed, which means they can be accessed and manipulated by the programmers working on the application. When the design and programming process is complete, the application is compiled into its final form. In a compiled application, the source code and design functions for the user interface and the database tables or files are not accessible to the end-users.
Some compiled applications require the installation of specific database programs or report writing software to function. This depends on how the application was designed. Off-the-shelf software applications (which are compiled) do not require additional programs to function. Applications are compiled to:
Customization of Compiled Proprietary Application Some compiled applications are designed to allow further customization of the source code and database design by the end-user. There are various ways that this is accomplished:
Individuals and small companies will generally start off with ready-to-go compiled applications and organize their business practices around its functionality. This is a fast, inexpensive solution. Larger companies generally have more dollars to spend. Early on, they will typically pay for customization by the company that sold them the application. This is less expensive than purchasing a source code license. Some will purchase the developer kit and customize the application themselves. Very often, as a company grows, so does the need for more extensive customization. The company may decide that the best course of action is to purchase the source code, if it is available for licensing. The type of licensing available is an important factor in this decision. This may serve as an interim solution, but it does have the drawback that the customized version still depends on continuing to pay for licensing of the original compiled application. For companies that expect rapid expansion or diversification, the preferred route is to create their own proprietary application. The advantage is that there are no licensing fees to pay and the application may be changed at will to meet the needs of their changing business conditions. |
| ||||||||||||||||||||