Computer Programming Techniques - Assignment Example

Computer Programming Techniques Task 3 3 Introduction The section produces a complete documentation that includes a user interface. The program documentation is used as a user manual in showing the input data needed and their range, types, and display of source code name. The user interface also displays the output data choice and output data that is user friendly. Input data required To come up with proper and authentic results, the user needs to connect a series R=100, L=10mH, and C=10 microF to a sinusoidal Alternative Power supply of precisely 100V/45 degrees. Connecting a proper circuit will help in coming up with better results since the parameters and variable will be of use in calculating current of the circuit. Therefore, the inputs needed to achieve its objective are R, L, and C. To run the program, the user will be required to input R as 100, L as 10 and C as 10. The input should be strictly numerical. When text input is used, the program will display an error and therefore no compilation and running will take place. The calculations will be the function of the frequency hence the frequency limits and interval need to be maintained. Frequency will range from 100 to 2000HZ at an interval of 100HZ. Output Depending on the output designed for production, a specified formula will be incorporated to suit the desire of the user. The set of output that the program is designed to produce include; the inductive reactance, capacitive reactance, complex impedance, Z amplitude, Z phase, and current. The needed quantities will be produced as frequency functions as specified in the specifications. For manual purpose, the complex reactance, Z Amplitude, and Z phase are highly dependent on the results in inductive reactance and capacitive reactance. Therefore, the user has to be discreet on the data he uses as input; it has to be within the set range. The table below shows the variables used in the program Quantity Formula Inductive reactance (XL) Capacitive reactance (XC) Complex Impedance (Z) Z Amplitude Z phase (argument) Current (I) The input and output for the program can be designed as shown below. The diagram shows step by step operation of the program: The program is intended to calculate the circuit current in the forms of Cartesian and polar. In addition, the calculations are based as functions of frequency. The current is computed from the division of the supply voltage (V) and the complex impendence (Z). 3.2 Introduction The section produces a technical document. The document provides a clear outline to the users of the program on technical problems solved, variables, and constants that they will deal with. Technical Problem The calculations in electrical engineering to use resistance, Voltages, and current normally use real numbers. These numbers are not only used by users when handling sinusoidal vectors and sources. The program introduces complex numbers to enable complex equations to be worked out with figures that are roots of imaginary numbers. Variables and Constants The variables used in programming include the inductive reactance, capacitive, complex impedance, Z amplitude, Z phase, and Z phase. To distinguish the real and the imaginary number, the j operator has been used on the formula to determine the complex impedance. The j operator is used before the difference between the inductive and capacitive reactance to signify the operation of an imaginary number. Therefore, complex impedance has two distinct but related sections; real number and imaginary number. From the variables, R signifies the real number, while the difference between the inductive reactance and capacitive reactance is an imaginary number. When the complete impedance square root is determined, the imaginary number’s vector will rotate by 180. The complete impedance is represented mathematically by using a cosine rule called the Cartesian form and the rectangular form. From the variable formula, Resistance is the active component, j is defined as the square root of -1, while the difference between the inductive reactance and capacitive reactance are the reactive component. The division of complex impedance is difficult to perform as it needs using the conjugate function in converting the denominator to a real figure. Hence, the polar form is used in carrying out the operation. The Z amplitude and Z phase uses the polar form. The variables are written in terms of angle and magnitude. In polar, the length L and the angle shows the complex impedance rather than a point. In this form the conjugate of the complex impendance has similar modulus, this signifies the angle that varies. The program therefore, harmonizes the two forms to come up with the current of the circuit. Task 4 Programming can be a complicated activity. No programmer can write a perfect code for the application. The errors of programming caries, the techniques that are used in locating and addressing them need to be calibrated to suit. A syntax error can be defined as errors arising due to missing parenthesis, colon, and semicolon. Basically syntax is the way users construct sentences by abiding to rules and principles. For instance in C++, a syntax error would arise to command “int X= five”; the function would not compile since it does not abide with the language syntax and does not make any use to the compiler. The error will occur when the program code is unable to observe the grammatical guidelines of a programming language. The following code in the program demonstrates the right statement: Input_R=“100”; The following amended program has a syntax error: Input_R=Martha;” The opening set of quote for the value of the variable is missing. Conversely, semantic error is an error arising due to logic. It arises from wrong logical statements and entails interpretations and meanings that are derived from understanding and sentences of the message. Basically, semantic errors are logical errors, as syntax is code error. Semantic error would compile but still contain logical errors. For example, Cons tint i=10; the program will compile and run without showing any errors, but the result will produce inaccurate results. Therefore, the semantic errors happen when the code has logical errors and mistakes. From the program, the following code demonstrates coming up with an array, to access the element Var frequency= [“100”, “200”, “300”]; document. Write (frequency [0]); The amended version has semantic error: Var frequency= [“100”, “200”, “300”]; Consequently, in C. “printf ()” printf () is a syntax error because the command is mistyped. 2+2 is taken to be a semantic error since it is logically incorrect. document. Write (frequency [3]); The code is in a position to cause the application program to crash. 4.2 Introduction The goal of testing a program is to make sure that the program works as it has been specified. A program test entails function testing within the program. The procedures include creating test plans, creating test data, carrying out test according to the program’s test plan, and report and review the outcomes of the test. Some of the features that need testing during the process include the functional needs, and regression tests. Documents needed The following documents offer information needed in creating the system test plan and is recommended to be read before beginning the phase. FRAM, change requests, Database Design Report, High Level Design Framework, Problem Repost Analysis Report, and Appropriate third party interface specifications. Program Test Design Steps The following are the guidelines recommends when carrying out the designing program tests: Design the test cases to make sure that all the specification identifies in the analysis are documented in a single or multiple test cases. To reduce the test cases number, the test cases are designed to find out the various related requirements. Every logical test case should perform test related functions. The test cases should be arranged in the order reduces the effort needed for setting up tests. Program Testing Steps The guidelines for program testing include: Review the entire requirement and design the papers. Attend the reviews of the system presented by the Analysis and Development Team. Maintain and create a detailed project plan Define the required regression tests Create Program Test Plan After creating and conducting System tests, quality record is carried out. Quality Record The following program testing documents are recorded as permanents Test Results Test Plans Status Report Integration and Program Test Report Client Access Memo 4.3 The programmers are cavalier on the quality of the program they write. We banged out some of the codes, run through it and conducted tests and analysis, is one of the method of detecting errors. The modern engineering practice to detect the error includes an effort towards testing and software quality assurance. There are two preventions to deliver the software from errors. The first step is to prevent introducing the error in the first place. Secondly, is to identify the bug lurking found in the code, flag them out, and crash the error. The first technique is superior. A bigger part of the program arises from conducting a proper work of defining the specifications for the program that is designed. Testing will focus on detecting the errors that creep in the program despite the efforts to keep them out. Additionally, other methods to detect an error in a program include; when one uses if an error with the program occurs, the mistake message will be #include #include int main (void) {           . . .           of stream fout;           . . .           fout. Open("my File");           assert (! fout. Fail( ));                         fout. Close( );           assert (! fout. Fail( )):           . . .  } Most errors occur because a mistake was made in coding, for instance when a programmer forgets to assign a certain value to a variable before using it. When the program is run and the mistake is found, the application will stop and the dialog box will be shown on the window of the code editor. The dialog box has the error description and the troubleshooting tips that outline the cause. The troubleshooting tips can be clicked to show the help topics for details. The program needs to be fixed before continuation of the program. To find the error the programmer needs to inspect the code. For instance, when an error occurred due to wrong value with the variable, intellisense can be used to see the variable value. Reference Magnuson, Robert A.. PDOC: program documentation system. Rev. 06/17/83. ed. Bethesda, Md.: Data Management Branch, Division of Computer Research and Technology, National Institutes of Health, 1983. Print. Read More