what are programming and examples, Assignments of Programming Languages

Download what are programming and examples and more Assignments Programming Languages in PDF only on Docsity!

PROGRAMMING

Assignment

Abdullah I A Rock

Employee form.

Login Form

What is debugging? Debugging is the process of identifying and correcting errors in a computer program's code. Debugging a program entail starting with the wrong piece of code, isolating the sources of any problems, and then fixing them. A debugger is a program that runs another program (say, your own code), allowing you to control the code while it's running, and to check certain elements when things go wrong. How a Debugger Operates. There are several things you may want to do or know when running error-prone software:  When a critical error occurs, what statement or expression was the program executing?  What line of program contains the call to that function in case a fatal error occurs while executing it?  What are the values of the program's variables (including parameters) at a given point in the program's execution?  What happens when an expression is evaluated at some point in the program?  What is the actual sequence of the instructions executed in the program? These functions require the ability to examine program data, get a list of currently running jobs, set breakpoints where program execution is suspended to allow inspection of its data, and cycle through program data to see what is really going on. Debugging Feature.  Breakpoints: A breakpoint is the first thing that comes to mind when you think of debugging. It does exactly what its name implies - it indicates a point in the code where execution will stop (and no, it won't break the code).  Run, Step Over/Into/Out: A step gets you to the next job, Step takes you to the next job, Step takes you out of the current job.  Check the call stack.  Put the variables' names and contents into the local/global scoop.  Hover over a variable to view its contents.  Examine or modify the changed contents.  View the object's structure. Almost all debuggers work at the symbolic or source code level to provide more information about the operation of the original code. In essence, they give the impression that you're executing Java statements in your source code rather than the machine code they're compiled into. When debugging code, it's common to need to look at several things at once: running code, device registers in the microcontroller, specific memory locations, and breakpoints. As a result, you will want to display multiple windows in a graphical user interface format. Figure 1 depicts a screenshot of the annotated debugger to highlight some of the available features.

Figure 1

Figure 1: The Eclipse IDE debugger screen with multiple windows and its

functions.

remaining uppercase letters. For example, when calculating the total daily rental cost, we will use the variable as the total cost. When naming a function, the first letter of each word in the name of the function must be capitalized. In the middle of the word, make the first letter of each syllable randomly capitalize. For example, the monthRemDays.  Use of comments: Comments are used when writing application code. Writing comments allows others to understand the code better.  Each line contains one statement: Each line can contain one statement. It makes it easier for others to develop code.  Indentation: Proper indentation is crucial to increase the readability of the code. Programmers must use whitespace correctly to make their code readable. The following are some spacing conventions: o After the comma, there must be a space between two functions' arguments. o Each overlapping block must be indented and spaced properly. o An appropriate indent must be present at the beginning and end of each program block. o All parentheses must start with a newline, and the code following the end of the parentheses must start with a newline.  Avoid hard-to-understand markup: Code must be easy to understand. Maintenance and debugging are difficult and costly due to the complex code.  Avoid using an identifier for more than one purpose: you should give each variable a descriptive and meaningful name indicating why it is used. This is not possible if the identifier is being used for multiple purposes, which can confuse the reader. Furthermore, it also makes future improvements more difficult.  The code should be well documented: the code should be commented properly so that it can be easily understood. Adding comments to statements improves code readability.  Function length should be kept to a minimum: long functions are difficult to understand. As a result, jobs need to be small enough to handle small tasks, and larger tasks need to be broken down into smaller jobs to handle small tasks.  Avoid using GOTO statements: GOTO statements make the program disorganized, which reduces program understanding and makes debugging difficult. Camel Case example.

What is SDLC? The Software Development Life Cycle (SDLC) refers to the process of planning, developing, testing, and deploying software. The SDLC clearly explains the various tasks that need to be completed at each stage of the software development process. SDLC is divided into several stages, including planning, requirements, design, development, testing, deployment, and maintenance. Waterfall model, spiral model, V-shaped model, iterative model, big bang model, and graceful model are some of the models of SDLC. Each phase of software development is easily evaluated, allowing programmers to work concurrently using SDLC phases. This is a procedure to be followed, not a technique. There are several stages in the software life cycle which are explained below:  requirements stage  analysis stage  design stage  development stage  testing phase  Publication and maintenance phase

Update.

Clear.

After

Before

2) Analyze phase. After the requirement’s gathering phase is completed, the requirements need to be analyzed and approved by the client/s. This is achieved using the Software Requirements Specification (SRS), which contains all the requirements that were compiled and developed during the "requirements collection" phase. Project managers, business analysts, and consultants are mainly responsible for this stage. 3) Design Phase. After completion of the analysis phase, the need arises to develop a more accurate, robust, efficient, and cost-effective architecture for the product to be developed. During this stage, multiple designs are usually proposed, and the best one is chosen based on various criteria such as robustness, durability, timeliness, cost-effectiveness, and many more! The various design architectures are usually documented in a Design Document Specification (DDS). Employee Login form.

5) Testing Phase. After the development phase is completed, the developed program is tested. Developed software is sent to a testing team, who thoroughly tests the software and looks for defects.

Employee Code.

If a defect is detected, the testing team documents it and sends it back to the development team for correction. This role is undertaken by the Company's software testers and quality analysts. The testing team must make sure that every component of the software is error- free and working correctly.

Save Button

6) Deployment in the Market and Maintenance. After the testing phase is completed, the first version of the software is deployed and delivered to the customer for use. When a customer begins to use the developed software, there is the potential for bugs not caught during the testing phase to be fixed, such as when a large group of end-users begin using the software; There is a possibility that some boundary cases will be missed. There is also the possibility to update the program with newer versions as well as the latest patches and security technologies. Finally, there is room for improvement in the program by integrating new features into the existing program. 7) Implementation phase: The SDLC implementation phase is the process of configuring software for specific use conditions as well as training customers on product use. After the system is tested and approved by the company, this phase begins. A program is installed at that time to support the intended business functions. The performance of the system is compared to the objectives that were set during the planning phase. Reksoft provides a full range of software implementation services for customers, from software installation, adaptation, modification, and advancement to device integration, commissioning, and user training.

Jar File

Example of debugging.

 Fundamental Concepts Eclipse has excellent debugging support. Visualizes implementation step by step and helps us find bugs. We will use the sample Perfect Square Counter program to demonstrate the debugging features of Eclipse. This program counts the total number of perfect squares and even perfect squares that are less than a certain number:  Debug Mode First, your Java program needs to be run in debug mode within Eclipse. There are two ways to get this done:

 Code-Flow Controls Now that the debugger has stopped at the specified breakpoints, we can continue execution. Suppose the debugger is presently present as shown in the screenshot below, on line 16:

 Debug Perspective: When we run the program in debug mode, Eclipse will prompt us to specify the debug perspective. A debug perspective is a set of views that help us visualize and interact with the debugger. Here are some of the most informative views on this: o debug view - This displays the various threads and call stack traces. o Show variables - This displays the values of the variables at any given point. If we want to see static variables, we must say so explicitly. o Breakpoints - This displays the various breakpoints and control points (which we will see below). o The Debug Shell enables us to write and test custom code while debugging (example covered later).