270 likes | 761 Views
Visual Basic 6.0. Designing an Application in VB 6.0. Objectives in this lesson. Define a Procedure Oriented application and show examples – (procedur.exe) Define an OOED (Object Oriented/Event Driven) Application and show an example Steps to Creating an OOED Application
E N D
Visual Basic 6.0 Designing an Application in VB 6.0
Objectives in this lesson • Define a Procedure Oriented application and show examples – (procedur.exe) • Define an OOED (Object Oriented/Event Driven) Application and show an example • Steps to Creating an OOED Application • Steps to Planning an OOED Application • Design Tips for the Application • Exercise: • Create a TOE chart of the Skate Away Sales Order Form • Sketch the Interface (in the back of the sheet)
Procedure Oriented Application • Applications where the emphasis is on how to accomplish a task. • Programmer must instruct the computer every step of the way, from start to finish. • Requires that the program think in a step-by-step, top to bottom approach. • Limitations: • User has very little control over the data entered • Sample apps: procedur.exe (under tut02 folder)
OOED – Object Oriented Event Driven Application • Emphasis is on the objects and events included in the user interface • Goal is to give the user as much control over the application as possible. • Does not require that the programmer work in a step by step, top to bottom approach. • Sample apps: OOED.exe (on the TUT02 folder)
Steps to create an OOED application • Plan the application • Build the user interface • Write the code for the application • Test and debug the application • Assemble the documentation
Steps to planning an OOED application • Identify the tasks, objects and events using a TOE chart (Task, Objects, Events)\ • The programmer creates objects and events for all the tasks needed and names them. • The programmers sketches the application using one of these methods: • Writing pseudocodes • Flowcharts
Design tips for an OOED application • Information should flow vertically or horizontally, with the most important information at the top left. • Commands buttons should be grouped together, along the bottom of the screen or lower right corner. • Use no more than six command buttons • Use meaning and short captions (one to three words) in buttons • Label each control. Align labels to the left , short, and one line only.
Exercise: Sketch the Skate Away Application • Using the sales order handout, do the following • Write a TOE chart (decide how many controls to use and name them. • Sketch the user interface in the back of the page.