Unit 20 Event Driven Programming Solutions-Btechnd

ProgrammeBTEC Higher National Diploma in Computing
Unit Number and TitleUnit 20 Event Driven Programming Solutions
QFC LevelLevel 4
Unit CodeH/601/0453

Unit 20 Event Driven Programming Solutions-Btechnd


AC1.1 Submit a report to the club president clearly explaining the principles, characteristics and features of event driven programming.

Principles of Event Driven Programming: Event-driven programming is a programming approach in which events decide the flow of program execution. For example when a user performs a mouse click, press a key on keyboard or interact with the system with any other input method.
An event-driven web application detect events as they occur and then call appropriate event-handling procedures to generate the results desired by the user.
The previous era of programming uses interrupt-driven programming to generate results on command-line environments such as DOS or embedded systems (where the application is implemented as firmware).
Event-driven programs can be written in any programming language, but Visual Basic is specifically designed to facilitate event-driven programming. It also provide an integrated development environment (IDE) {Visual Studio} which helps developers in writing code and provide variety of built-in objects and controls.
Characteristics of Event Driven Programming:

  • Best for Graphical User Interface: Event driven programming in best technique for GUI applications, because in GUI applications user interacts with the system using events (Mouse Click, Key Press etc.).
  • Event driven programming can also be used with procedural languages where all event handling can be defined as separate procedures.
  • Service Oriented: In event driven programming many of our event handlers are service oriented. Service oriented event handlers works as background services and serve users silently in the background.
  • Time Driven: In event driven programming we can define time driven event handler. Time driven event handler execute automatically after a specific time interval.

Features of Event Driven Programming:

  • Flexibility: Event driven programming is very flexible and a wide range of applications can be created using event driven programming.
  • Suitable for graphical interfaces: Event driven programming is very suitable for graphical interfaces because in GUI application user interact with the system via events.
  • Simplicity of programming: Event driven programming is very simple compare to traditional flow driven languages.
  • Ease of development: Event driven programming provide easy development environment for programmer because he/she only need to concentrate only on one event a time.

M3 Present and communicate appropriate finding in a standard technical format when submitting this report to the club president.
Report for club president:
After a thorough study of application requirements for “The Creative Computing Club”, we found that, we have to develop a GUI based application for the club. This application provide functionality for three kind of user.

  • Organizer: Organizer can perform administrative tasks.
  • Presenter: Presenter is an authorized member to give a presentations.
  • Audience: General viewer of a presentation. These provide score for each presentation held at the club.

To develop such application we have to select a programming paradigm which is best for current application. There are many programming styles for application development such as procedural programming, event driven programming and object oriented programming etc.
After deep study of each programming paradigm we decided that Event driven programming will be the perfect solution for the application. Event driven programming is suitable for such applications which performs actions based on user actions (events).
Since proposed application is a GUI application and it performs tasks according to the user actions. Event driven programming is best choice for the application.
To develop an event driven programming solution we have to define an event scheduler which receives all events and pass the control to event specific handler.

unit 20 image1

Technologies to be used for the application:

  1. Programming Approach : Event Driven Programming
  2. Programming Language : VB.NET
  3. To store application data : Microsoft SQL Database Server


AC2.1 Design an event driven programming solution based on the specification given by Creative Computing Club.

Proposed design of the application using event driven programming
Since we are developing an application for Creative Computing Club we prepared user interface design for our application.
Our design in visual studio is as follows:

Design of login screen:

unit 20 event driven

Presenter Details Form:
(Figure : Presenter Details Form)

  1. Schedule Presentation Form:
    (Figure : Schedule Presentation)
  2. Certificate Design:
    unit 20 image5
    (Figure : Certificate Design)
  3. View all Presenter Certificates:
    unit 20 image6
    (Figure : View All Presenter Certificates Form)

AC2.2 Identify the screen components and data file structures required to implement the design provided for the Creative Computing Club problem specification.

Visual Studio Screen Components:

1.Complete interface of visual studio

unit 20 image6
(Figure: Visual Studio Complete interface)
2.Solution Explorer: It provides functionality to manage all project files. It shows a tree structure which enables users to add, delete or rename files to their projects.
unit 20 image7
(Figure : Solution Explorer)
3.Editor Area: This is the main working area for the user. It provides two interfaces Design and Code.
In Design interface user can see application’s running time interface. He can add or adjust other components using mouse.
In Code interface application shows application code to the user.
unit 20 event driven programming
(Figure : Editor Area)
4.Toolbox: Toolbox area provides screen controls for the application. It is very useful with Design Interface of Editor Area. User can drag controls from here and add them directly to the application interface.

unit 20 event
(Figure: Toolbox)
5.Toolbar: It provides few useful shortcuts to work with visual studio, like opening new project, save project, run project, debug project etc.
unit 20 event driven
(Figure: Toolbar)

M2 Identify and apply strategies to find appropriate design solutions to your application. Include all design documentations listed in briefing note for Task2.
Strategies for designing the application (User Use Case & Application Flow diagrams)
During the study phase of the application we have found that there are three types of users in the application:

  1. Administrator
  2. Clerk (User)
  3. Presenter

Following diagram shows tasks of these users in the application.

unit 20 event image

(Figure: User Case Diagram for all users of the application)

After defining the tasks for each user we have designed the flow of application. This application flow describes how modules of our application work together to achieve a specific goal.

unit 20 event driven image

(Figure: Application Flow Diagram)

Take responsibility for managing and organizing all the activities in your project. Refer to briefing note for Task 2
Project Plan: After deep study of the application we have defined user roles and application flow between modules we are now assured that this application is feasible and we it fulfill all tasks as stated in assignment.
We have made a project plan, which defines various phases of our application development and estimated time for each phase.Order Now
Following figure represents our project plan:

unit 20 event image driven

(Figure: Project Plan)

Leave a Reply

Your email address will not be published.

1 Step 1