Prepare for your exams
Get points
Guidelines and tips
Sell on Docsity
Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips

Sell on Docsity

Docsity AI

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents

20 Points

For each uploaded document

Answer questions

5 Points

For each given answer (max 1 per day)

All the ways to get free points

Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

assignment 2 programming M pass, Schemes and Mind Maps of System Programming

FPT University (FPTU)System Programming

good luck everyone this assignment will be M

Typology: Schemes and Mind Maps

2022/2023

Uploaded on 09/06/2023

quoc-anh-tran-1 🇻🇳

(1)

19 documents

1 / 53

This page cannot be seen from the preview

Don't miss anything!

ASSIGNMENT 2 FRONT SHEET

Qualification

BTEC Level 5 HND Diploma in Computing

Unit number and title

Unit 1: Programming

Submission date

Date Received 1st submission

Re-submission Date

Date Received 2nd submission

Student Name

TRAN QUOC ANH

Student ID

BH01310

Class

SE206.06

Assessor name

NGO THI MAI LOAN

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

QUANH

Grading grid

Discover Schemes and Mind Maps of System Programming FPT University (FPTU)

Partial preview of the text

Download assignment 2 programming M pass and more Schemes and Mind Maps System Programming 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 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name TRAN QUOC ANH Student ID BH

Class SE206.06 Assessor name NGO THI MAI LOAN

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 QUANH

Grading grid

P2 P3 P4 P5 M2 M3 M4 D2 D3 D

Table of Figures

I. INTRODUCTION
- A. SCENARIO
- B. REPORT
II. BODY......................................................................................................................................................................................................
- and the relationship between them...................................................................................................................................................... A. Give explanations of what procedural, object-oriented and event-driven paradigms are. Their characteristics
  - 1. Procedural paradigm
  - 1. Object-oriented paradigm
  - 1. Event-driven paradigm
  - 1. The relationship between them
- B. Write a program that implements an algorithm using an IDE.
  - 1. User request list
  - 1. Your application could solve the problem
  - 1. Result screenshot......................................................................................................................................................................
- C. Explain the debugging process and explain the debugging facilities available in the IDE.
  - 1. Explain the debugging process
  - implementation 2. Explain the debugging facilities available in the IDE and Evidence that I have used debugging during the
  - 1. The process debug of my program
- D. Outline the coding standard you have used in your code.................................................................................................
- E. Analyze the common features that a developer has access to in an IDE.....................................................................
  - 1. They offer a central interface with all the tools a developer needs
  - 1. The Benefits of Using IDEs..................................................................................................................................................
  - 1. Multi-Language IDE
- F. Use the IDE to manage the development process of the program.................................................................................
  - 1 Why choose IDE to manage the development process of the program.
  - 1. State cons and pros
  - 1. Evidence of how the IDE was used to manage the development of your code
- G. Evaluate how the debugging process can be used to help develop more secure, robust applications.
III. CONCLUTION
IV. References
Figure 1:Introduction
Figure 2:Procedural programming
Figure 3:Object-oriented programming
Figure 4: Encapsulation
Figure 5:Event-driven paradigm..................................................................................................................................
Figure 6: Login
Figure 7:Exiting the program
Figure 8:Logging in information
Figure 9: login in information is correct......................................................................................................................
Figure 10:Logging in correct information
Figure 11:Student
Figure 12:Find Student Menu......................................................................................................................................
Figure 13:Entering student information
Figure 14: Fix student information
Figure 15:Delete student..............................................................................................................................................
Figure 16: Exit the program
Figure 20:Color coding of the syntax in my program
Figure 21:A translator in my program
Figure 22:Code highlighting in my program
Figure 23:Breakpoints in my program
Figure 24: Step over in my program............................................................................................................................
Figure 25: Step into in my program
Figure 26:Run to cursor in my program
Figure 27: My code need debug
Figure 28:Put a breakpoint
Figure 29:The program run until the line has put breakpoint button
Figure 30:Use to Step Over
Figure 31:My debugger finished
Figure 32: Coding standard
Figure 33: Coding standard
Figure 34: Coding standard
Figure 35: Code for login
Figure 36:Check ID and Password
Figure 37: code of ID and password list for login
Figure 38:Code for close or exit the form
Figure 39: Add student information
Figure 40: Edit student information
Figure 41: Delete student.............................................................................................................................................
Figure 42: Data grid view student
Figure 43: Find student by information
Figure 44:Code editor in my program
Figure 45:Compiler in my program
Figure 46:Debug in my program

I. INTRODUCTION

A. SCENARIO

My application for a trainee position with a software development business was accepted, and I was

contacted for an interview. I've been given the presentation to show off my aptitude for problem-solving

and fundamental programming abilities. Now I'm given a more difficult task: to construct an application

that completely functions, is secure, was produced using an IDE, and complies with coding standards for a

specific business problem.

B. REPORT

I will discuss a suitable problem with my mentor and list the user requirements before designing,

implementing (coding) and testing a solution. I will create a report that should include:

Introduction to your program (list of requirements and screenshots of the program).

Explain some of the programming paradigms. Evaluate why and how your program uses these (or some of)

paradigms.

Figure 1 :Introduction

Explain the common features of an IDE should have and evidence of how the IDE was used to manage the

development of your code.

An evaluation of developing applications using an IDE versus developing an application without using an

IDE.

An explanation and evaluation of the debugging process in the IDE used and how it helped with

development.

An explanation and evaluation of coding standards used in your program and the benefits to organizations

of using them.

II. BODY

A. Give explanations of what procedural, object-oriented and

event-driven paradigms are. Their characteristics and the

relationship between them.

1. Procedural paradigm

a) What is procedural programming?

A programming paradigm known as procedural programming is based on the notion that programs are

collections of instructions that must be carried out. They put a lot of emphasis on dividing programs into

named, function-like collections of instructions called procedures. A procedure can access and change

global data variables as well as local data that is not available from outside the process's scope.

b) The characteristics of object-oriented paradigm

Encapsulation:

Information and an object's internal processing capabilities can be hidden thanks to encapsulation. Other

objects must go through public methods supplied by that object in order to change the state of the object and

modify the data inside.

Code and data within an object may be private or public to that object, or both. Private data or code may not

be available by a component of the program that exists outside the object as private code is only known to

Figure 3 :Object-oriented programming

Figure 4 : Encapsulation

and accessible by another portion of the object. Even if it is declared within an object, when the code and

data are public, other parts of your application may access them.

Inheritance: This is the process by which a class can be derived from a base class with all features of base

class and some of its own. This increases code reusability.

Child classes don't need to be redefined because they inherit all the parent class's members. Subclasses can

add new components or expand those that were inherited.

Polymorphism: The ability to treat different objects the same way is known as polymorphism. One of the

main advantages of inheritance is this. Based on the derived type of the base reference, we may choose the

appropriate call at runtime. We refer to this as late binding.

Abstraction: Abstraction eliminates the unnecessary complexity of the object and focuses only on what is

essential and important.

Abstract classes: The abstract keyword in C# enables the declaration of abstract classes and functions.

An abstract class cannot be created as an instance. Any non-abstract derived class must override any abstract

members, which have a signature but no function body. Inheritance is the main purpose of abstract classes.

Abstract member functions, properties, and indexers are possible. A class must also be abstract if it has one

or more abstract members. No static members may be abstract.

Sealed classes: The opposite of abstract classes are sealed classes. Sealed classes cannot be inherited, but

abstract classes may and are improved in the derived class. An instance of a sealed class can be generated.

To stop additional refinement through inheritance, a sealed class is employed.

Interface: A derived class must implement a set of related functions known as an interface. An interface's

members are implicitly public and impersonal. Similar to abstract classes, interfaces are. Both types cannot

be created as instances; first, both must be inherited. Despite the fact that there are certain distinctions, such

as the following.

An Abstract class can contain some implementations, but an interface can't.
An Interface can only inherit other interfaces, but abstract classes can inherit from other classes and

interfaces.

An Abstract class can contain constructors and destructors, but an interface can't.
An Abstract class contains fields, but interfaces don't.

Time Driven: Time driven is a paradigm in event driven programming that describes a piece of code that

executes in response to a time trigger. This code can run once an hour, once a day, once a week, or once a

month, making it a pre-set job. Windows Update is one example of a time-driven application in which the

user may specify when to update or when to check for and download updates.

Event handlers: A kind of method or function that executes a certain action when a particular event is

triggered. An event handler may, for instance, be a button that, upon user click, displays a message and,

upon subsequent user click, hides the message.

Trigger functions in event-driven: There are functions in programming that determine what code should

be executed when a certain event happens and which event handler should be utilized for the event.

Events include mouse, keyboard, and user interface; in order for them to occur, a user must interact with

an item in the program, such as clicking a button with a mouse or choosing a button with the keyboard,

among other things.

Event-driven programming is straightforward and easier to program than other types of programming since

it is extremely visible. For instance, you can create a button by just selecting it, placing it on a form, and

writing a code for it. Because event-driven programming allows users to stop the code while it is running,

it is also simple for users to add pre-written code scripts into an already-existing application. which make

event-driven programming development simple.

4. The relationship between them

Due to the rapid advancement of technology, sophisticated programs are becoming more and more

prevalent nowadays. Regular programmers coordinate between two or three programming models to

streamline these programs' algorithms. Additional examples of how they could be.

Numerous programs have hundreds of thousands of lines of code and can get quite huge. Older

programming languages, like COBOL, were able to handle this complexity by allowing the creation of

paragraphs or by moving some code to external programs that could be called from a main, central, or

controlling program that assigned values to the variables that would be used as parameters by the called

program. On terminating, the called program would hand back control to the caller program and might or

might not return some values as directed. When one program calls another with or without arguments and

with or without receiving a return value, calling can be nested.

The procedural paradigm considers the processes needed to solve a problem, providing solutions,

determining processes and data streams.

Event handlers are just a convenient way for event driven programming to maintain a lot of code on hand

and ready to utilize as needed. If this code is not necessary, it just exists on the periphery without interfering

with or clogging up other programs. The program is now composed of a number of smaller programs, each

of which is connected to a specific event related to a command button, drop-down menu, text box, etc. The

controlling application merely keeps track of various events and executes the code within the event handler

designated for that event (for example, a form in Visual Basic).

Event programming model creates actions when encountering events for both procedural programming

and programming object.

Programmers can handle the complexity of large programs and construct increasingly complicated

programs because to the mutually reinforcing nature of the three models. Three models each rely on its own

benefits and drawbacks to prevent the disturbance of the others, assisting programmers in effectively

finishing their task.

B. Write a program that implements an algorithm using an IDE.

1. User request list

Have login function for software
Add Student.
Update student information.
Delete student.
Looking for students.
Show list of students. 2. Your application could solve the problem
There must be a form to perform the login function.
Create a list of student information.
Add student information.
Edit student information.
Delete student.
Search for student names by personal information.

Figure 7 :Exiting the program

When logging in information

When the user logs in the password will be covered by dots. And the textboxes and buttons are arranged in

order so that the user can use the tab button on the keyboard instead of themouse. Support for faster login.

Figure 8 :Logging in information

When logging in the information is incorrect

When the user logs in incorrectly or lacks the ID or password, the program will display amessage Asking

the user to re-enter them.

Figure 9 : login in information is correct

When logging in correct information

After successful login, enter the program and perform the next functions.

Figure 11 :Student

On the “Find Student” menu is the same just different for choose bottom for find.

assignment 2 programming M pass, Schemes and Mind Maps of System Programming

Related documents

Partial preview of the text

Download assignment 2 programming M pass and more Schemes and Mind Maps System Programming 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 Date Received 1st submission

Re-submission Date Date Received 2nd submission

Student Name TRAN QUOC ANH Student ID BH

Class SE206.06 Assessor name NGO THI MAI LOAN

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 QUANH

Grading grid

P2 P3 P4 P5 M2 M3 M4 D2 D3 D

Table of Contents

Table of Figures

I. INTRODUCTION

A. SCENARIO

My application for a trainee position with a software development business was accepted, and I was

contacted for an interview. I've been given the presentation to show off my aptitude for problem-solving

and fundamental programming abilities. Now I'm given a more difficult task: to construct an application

that completely functions, is secure, was produced using an IDE, and complies with coding standards for a

specific business problem.

B. REPORT

I will discuss a suitable problem with my mentor and list the user requirements before designing,

implementing (coding) and testing a solution. I will create a report that should include:

Introduction to your program (list of requirements and screenshots of the program).

Explain some of the programming paradigms. Evaluate why and how your program uses these (or some of)

paradigms.

Figure 1 :Introduction

Explain the common features of an IDE should have and evidence of how the IDE was used to manage the

development of your code.

An evaluation of developing applications using an IDE versus developing an application without using an

IDE.

An explanation and evaluation of the debugging process in the IDE used and how it helped with

development.

An explanation and evaluation of coding standards used in your program and the benefits to organizations

of using them.

II. BODY

A. Give explanations of what procedural, object-oriented and

event-driven paradigms are. Their characteristics and the

relationship between them.

a) What is procedural programming?

A programming paradigm known as procedural programming is based on the notion that programs are

collections of instructions that must be carried out. They put a lot of emphasis on dividing programs into

named, function-like collections of instructions called procedures. A procedure can access and change

global data variables as well as local data that is not available from outside the process's scope.

b) The characteristics of object-oriented paradigm

Encapsulation:

Information and an object's internal processing capabilities can be hidden thanks to encapsulation. Other

objects must go through public methods supplied by that object in order to change the state of the object and

modify the data inside.

Code and data within an object may be private or public to that object, or both. Private data or code may not

be available by a component of the program that exists outside the object as private code is only known to

Figure 3 :Object-oriented programming

Figure 4 : Encapsulation

and accessible by another portion of the object. Even if it is declared within an object, when the code and

data are public, other parts of your application may access them.

Inheritance: This is the process by which a class can be derived from a base class with all features of base

class and some of its own. This increases code reusability.

Child classes don't need to be redefined because they inherit all the parent class's members. Subclasses can

add new components or expand those that were inherited.

Polymorphism: The ability to treat different objects the same way is known as polymorphism. One of the

main advantages of inheritance is this. Based on the derived type of the base reference, we may choose the

appropriate call at runtime. We refer to this as late binding.

Abstraction: Abstraction eliminates the unnecessary complexity of the object and focuses only on what is

essential and important.

An abstract class cannot be created as an instance. Any non-abstract derived class must override any abstract

members, which have a signature but no function body. Inheritance is the main purpose of abstract classes.

Abstract member functions, properties, and indexers are possible. A class must also be abstract if it has one

or more abstract members. No static members may be abstract.

abstract classes may and are improved in the derived class. An instance of a sealed class can be generated.

To stop additional refinement through inheritance, a sealed class is employed.

members are implicitly public and impersonal. Similar to abstract classes, interfaces are. Both types cannot

be created as instances; first, both must be inherited. Despite the fact that there are certain distinctions, such

as the following.

interfaces.