× Limited Time Offer ! FLAT 20-40% off - Grab Deal Before Its Gone. Order Now
Connect With Us
Order Now

MITS4002 Object-Oriented Software Development Report Sample

You will be marked based on your submitted zipped file on Moodle. You are most welcome to check your file with your lab tutor before your submission. No excuse will be accepted due to file corruption, absence from lecture or lab classes where details of lab requirements may be given. Please make sure that you attend Lecture EVERY WEEK as low attendance may result in academic penalty or failure of this unit.

This assessment item relates to the unit learning outcomes as in the unit descriptors.

This checks your understanding about object-oriented software development.

This assessment covers the following LOs.

LO1 Demonstrate understanding of classes, constructors, objects, data types and instantiation; Convert data types using wrapper methods and objects.

LO2 Independently analyse customer requirements and design object-oriented programs using scope, inheritance, and other design techniques; Create classes and objects that access variables and modifier keywords. Develop methods using parameters and return values.

LO3 Demonstrate adaptability in building control and loop structures in an object-oriented environment; Demonstrate use of user defined data structures and array manipulation.

Tank Circuit Program

Print your Student Name and Student Number.

1. Calculate the Capacitor with the input E, permittivity, A, cross-sectional area, d, separated distance.

2. Calculate the resonant frequency, f, of a tank circuit with the above C and input L.

C = EA and f= 1
d 2π√LC

Typical

Area = 5mm2 values: E =8.85×10−12F/m. (hardcode)


L = 1 μH Separated distances ~ 1mm (or less)

Round the Resonant frequency to two decimal places.

Here is a sample run:

Sample 1:

John Smith JS00001

Enter Capacitor Area (mm^2): 5

Enter Capacitor separated distance (mm): 0.5

Enter Inductance of the inductor (uH): 1

John Smith’s LC Tank Circuit Resonate Frequency: 16.92 MHz

Questions:

1. Did you store temporary values? Where and why?

2. How did you deal with errors? (Refer to the code/code snippet in your answer)

3. If the value E, permittivity was changed regularly, how would you change your code?

Submit the following items:

1. Submit this Word document with the following:

a. Copy of your code (screenshot – includes comments in your code)

b. Screenshot of the output of your code (3 times with expected values, 2 times with non-expected values – such as a zero as an input)

c. Your written response to the questions (Q1-3)

Solution

For Assignment Help

Screenshot of the Code as required:


 

Output 1:

Output 2:



Output 3:



Output 4:



Output 5:


 

Questions and Answers:

1. Did you store temporary values? Where and why?

Temporary values are utilised in the provided Java code to store the computed capacitance (C) and resonant frequency (f). C and f are these ad hoc values. This is why they are employed:

The computed capacitance, which is an intermediate outcome obtained from user inputs and a formula (C = EA/d), is stored in the variable C.

The computed resonant frequency is another intermediate result obtained from user inputs and the formula (f = 1 / (2 * * sqrt(L * C)) and is stored in the variable f.

The storage of intermediate results for further processing and the user-friendly presentation of final results depend on these temporary variables (Chimanga et al., 2021).

2. How did you deal with errors? (Refer to the code/code snippet in your answer)

Error handling in the code is simple, and it is assumed that the user will input accurate numerical numbers. The code doesn't do much in the way of validation or error management. The user is implicitly expected to provide accurate values for the inputs (capacitor area, separation distance, and inductance), albeit this is not stated explicitly.

You can add extra validation tests to make sure the input values fall within acceptable ranges and are of the right data types in order to improve error handling and robustness. For instance, you can verify that the values are non-negative and fall within the acceptable ranges for this particular application.

3. If the value E, permittivity was changed regularly, how would you change your code?
 
You can adjust the code to accept this number as an input from the user if the permittivity (E) value is prone to frequent changes. The code currently has a hardcoded value for E:

We can request the user to enter the permittivity value at runtime, exactly like other input values, rather than hardcoding this number. Here's an illustration of how we may change the code to accomplish that:

This update allows for flexibility when E needs to be modified frequently because the user can now input the permittivity value each time the programme is run (Saleh et al., 2021).

References:

Fill the form to continue reading

Download Samples PDF

Related Sample

Assignment Services