Download Assignment 2-1618, Grade Pass and more Assignments Information Technology in PDF only on Docsity!
ASSIGNMENT 2 FRONT SHEET
Qualification BTEC Level 5 HND Diploma in Computing
Unit number and title Unit 1: Programming
Submission date 24/12/2022 Date Received 1st submission
Re-submission Date Date Received 2nd submission
Student Name Trần Văn Tưởng Student ID GCH
Class GCH1107 Assessor name Phạm Danh Tuyên
Student declaration
I certify that the assignment submission is entirely my own work and I fully understand the consequences of plagiarism. I understand that
making a false declaration is a form of malpractice.
Student’s signature Tưởng
Grading grid
P2 P3 P4 P5 M2 M3 M4 D2 D3 D
Summative Feedback: Resubmission Feedback:
Grade: Assessor Signature: Date:
Lecturer Signature:
2.4^ 2.2^ 2.
- I. Introduction to your program
- Introduce the Overview/ Context of the problem
- List out application’s requirements
- II. Explain programming paradigms
- Explain what is Procedural Programming with source code and illustrations
- 1.1. Definition...................................................................................................................................................
- 1.2. Characteristics
- Explain what is Object-Oriented Programming with source code and illustrations
- 2.1. Definition
- 2.2. Characteristics
- Event-Driven paradigm....................................................................................................................................
- Conclude which paradigms will be used to develop the application with explanation
- III. IDE features
- Introduce what is IDE
- Introduce features of IDE with illustrations
- development. 3. An explanation and evaluation of the debugging process in the IDE used and how it helped with
- Evidences that you have used debugging during the implementation...........................................................
- IDE. 5. An evaluation of developing applications using an IDE versus developing an application without using an
- IV. Design and Implementation
- Flowchart of the application
- Source code and screenshots of the final application with explanation
- Explain and evaluate coding standards used in the program
- Explain the benefits of using coding standards
- References
- Figure 1:Procedural programming
- Figure 2:Source code procedural programming............................................................................................................
- Figure 3:Object-Oriented Programming........................................................................................................................
- Figure 4:Source code Object-Oriented Programming
- Figure 5:Class anf Object
- Figure 6: Inheritance
- Figure 7:Encapsulation
- Figure 8:Abstraction
- Figure 9:Polymorphisms
- Figure 10:Event-Driven paradim
- Figure 11:Example event
- Figure 12:Text editor
- Figure 13:Visual studio's Debugger
- Figure 14:Compiler
- Figure 15:Code completion
- Figure 16:Programming language support
- Figure 17:Integration and plugins
- Figure 18:What is debug..............................................................................................................................................
- Figure 19:Create breakpoint
- Figure 20:Press Debug and press Toggle Breakpoint (F9):
- Figure 21:Press Debug and press Start Debugging (F5)
- Figure 22:Stop Debugging
- Figure 23:Create break point.......................................................................................................................................
- Figure 24:Waring system
- Figure 25:Flowchart add
- Figure 26:Flowchart Edit..............................................................................................................................................
- Figure 27:Flowchart Delete
- Figure 28:Flowchart Search
- Figure 29:Flowchart Cancel
- Figure 30:Code result
- Figure 31:Form
- Figure 32:Check Data...................................................................................................................................................
- Figure 33:Class
- Figure 34cell click
- Figure 35:Function add................................................................................................................................................
- Figure 36:idroom missing import warning
- Figure 37:Name missing import warning
- Figure 38:Type missing import warning
- Figure 39:Location missing import warnimg
- Figure 40:Status missing import warning
- Figure 41:Function Cancel
- Figure 42:warning system
- Figure 43:function delete
- Figure 44:warning system
- Figure 45:after deleting
- Figure 46:function edit
- Figure 47:after editting................................................................................................................................................
- Figure 48:Function setToDefault
- Figure 49:Function Search
- Figure 50:to name
- Example: Figure 2 :Source code procedural programming
1.2. Characteristics
The essential characteristics of Procedural programming are listed below
- A big program is decomposed into smaller, more manageable processes or functions. This
minimizes code duplication, making the code more readable and maintainable.
- Global variables allow different functions to exchange date. Because functions are entirely
separated, we must declare data in the higher scope if we wish to share it.
- Global data can be changed by functions. Because global data is passed from function to function,
global data in function chains may be changed throughout the transformation.
- Methodology from the top down. As previously said, procedural programming employs a top-down
approach, with workflow moving from top to bottom.
2. Explain what is Object-Oriented Programming with source code
and illustrations
2.1. Definition
Object-oriented programming, or OOP, is an approach to problem-solving where all computations are
carried out using objects. An object is a component of a program that knows how to perform certain
actions and how to interact with other elements of the program. Objects are the basic units of object-
oriented programming. A simple example of an object would be a person. Logically, you would expect
a person to have a name. This would be considered a property of the person. You would also expect a
person to be able to do something, such as walking. This would be considered a method of the person.
Figure 3 :Object-Oriented Programming
Figure 5 :Class anf Object 2.2.2. Inheritance
- This attribute allows an object to inherit properties from another object via inheritance. This allows
objects to share or expand existing properties without having to rewrite them. However, not all object-
oriented languages share this feature.
Figure 6 : Inheritance
2.2.3. Encapsulation
- The process or method of combining code and the data it manipulates into a single entity is known as
encapsulation. Encapsulation protects the altered date from tampering and misuse from the outside
world. Java classes and objects can help with this.
Figure 7 :Encapsulation 2.2.4. Abstraction
- Abstraction is a movement that allows you to extract the most important information from a piece of
information. Abstraction facilitates the easy incorporation of real-world items into OOP software
programs (Object Oriented Programming). Abstractions simplify understanding of real-world objects
by removing superfluous characteristics.
Figure 8 :Abstraction
Figure 10 :Event-Driven paradim
Example:
Figure 11 :Example event 3.1. Characteristics
- Service-Oriented : The benefit of service-focused programming, which is used to create
programs for services, is that it does not cause the computer to slow down. The service-
oriented model uses a small amount of the computer's control power, and services are
frequently run in the background of the operating system.
- Time-Driven : In motivated event programming, time is a paradigm. Time-motivated code
differs from period-triggered code in that it operates at a specific time, which could be once an
hour, once a week, or once a month. This is an example of a time-driven revision in which the
user can select when to revise or when to verify and download the revision.
- Trigger Functions : Trigger functions in event-driven coding are functions that determine what
code to run when a specific event occurs. When an event occurs, programmers use these
functions to determine which event handler to use for the function.
- Events : This software requires events to be triggered by the mouse, computer keyboard, and
user interface. This implies that the user must interact with some aspect of the software, such
as clicking a mouse button, selecting a button with the computer keyboard, and so on.
- The Simplicity of Programming and Ease of Decelopment : Event-driven programming is simple
and much easier to develop than other types of programming because it is so appealing. You
could, for example, select a button and drag it onto a form before creating a code for it. Using
event-driven development, the user can also easily insert a pre-written code script into an
existing application. It enables the user to halt code execution in the middle of it. As a result,
growing with event-driven programming is simple.
4. Conclude which paradigms will be used to develop the application with
explanation
In my program i use procedural programming, object-oriented programming and event-driven paradigms.
I use procedural programming to check condition when user enters information. This makes the code
simpler and easier to understand. And about object-oriented I created class room to reuse the code and
reduce the code line.
I also used event-driven programming to design the overview of my application. I use use some useful
functions like buttons, labels, text boxes... to create a friendly interface that makes my application easier
to use.
III. IDE features
1. Introduce what is IDE
An IDE or integrated development environment is a software application that combines, in one place, all
the tools needed for a software development project. On a more basic level, IDEs provide interfaces for
users to write code, organize text groups, and automate programming redundancies. But instead of a bare-
bones code editor, IDEs combine the functionality of multiple programming processes into one.
Compiler : Compilers are components that convert programming languages into machine-readable formats
such as binary code. The machine code is examined for accuracy. The code is then parsed and optimized
by the compiler to improve performance.
Figure 14 :Compiler
Code completion : Code completion features help programmers by identifying and inserting common code
components intelligently. These features save developers time when writing code and reduce the
possibility of typos and bugs.
Figure 15 :Code completion
Programming language support : IDEs are typically limited to a single programming language, though some
do support multiple languages. As a result, the first step is to determine which languages you will be coding
in and then narrow down your prospective IDE list accordingly. Ruby, Python, and Java IDE tools are
examples.
Figure 16 :Programming language support
Integrations and plugins : It comes as no surprise that integrations must be considered when evaluating
IDEs, given the name integrated development environment. Because your IDE serves as your development
portal, integrating all of your development tools will improve development workflows and productivity.
Poor integration can cause a slew of problems and headaches.
Figure 17 :Integration and plugins
find other errors around the error and to ensure that no collateral damage is introduced into the
fix.
4. Prove the Analysis : After you've finished analyzing the original bug, you should check the
application for any additional errors. Using a test framework, create automated tests for these
areas in this step.
5. Cover Lateral Damage : You must now create or collect all unit tests for the code that will be
modified. These unit tests should all pass if you run them now.
6. Fix & Validate : The final stage is to fix all errors and run all test scripts to ensure that they all pass.
c. Debug in Visual Studio IDE
First, in order to run Debug in Visual Studio IDE, we need to create a breakpoint by putting the pointer in
a position Which we need to create break point or select Debug on the toolbar and select the function
(F9). Then Press F5 Toggle Breakpoint (Debug > Start Debugging) or the Start Debugging button Start
Debugging in the Debug Toolbar. When fixing bugs, Debug run to the breakpoint and the debugging
process will end
First, in order to run Debug in Visual Studio IDE, we need to create a breakpoint by putting the pointer in a position Which we need to create break point or select Debug on the toolbar and select the function (F9). Then Press F Toggle Breakpoint (Debug > Start Debugging) or the Start Debugging button Start Debugging in the Debug Toolbar. When fixing bugs, Debug run to the breakpoint and the debugging process will end Figure 19 :Create breakpoint
Figure 20 :Press Debug and press Toggle Breakpoint (F9): Figure 21 :Press Debug and press Start Debugging (F5)
There are 3 basic functions to use:
Step into (F11) (Debug > Step Into is the Step Into command and advances the app execution one
statement at a time. When you start the app with F11, the debugger breaks on the first statement that
gets executed.
Step Over(F10): Run passes through each function in the code, but does not stop inside each method
Step out (Shift +F11) means that if you have stepped in a function and now you want to skip seeing how
the rest of the function is going to execute, you step out and the function returns. Then, you go back to
the next line, that is the line right after the function call.
After debugging, if you want to exit this function, select Stop Debugging (Shift + F5) on the toolbar or select
Debug on the toolbar and select Stop Debugging
