CIRDLES: Linking Task

Spring 2020

I am beginning my last semester of college with a Topsoil task! 

The goal inside Plot Configuration is to link a data column with its uncertainty column.

When you import a file from Topsoil we are making the assumption that it will be formatted to have a data column then followed by an uncertainty column.

1. The user will select X or Y for the data column

2. If there is an uncertainty column after the data, the column value with be automatically generated 

For example, if the user selects X for the data, then Bar X. 

3. The uncertainty value will stay as follows even if the user physically rearranges the columns (a feature of JavaFX)

4. If an uncertainty column is read in with no data column prior to it, the column itself is useless. This will alert the user that an orphaned uncertainty is meaningless and the file will need to be formatted.

5. Disable java dragging because there is no way to disable the column header > get the node that is in the table header node and intercept any click and drag> then cancel it

6. Remove the 'set' and 'set all' buttons

7. There is only 1 dropdown menu that contains X, Y, and Rho

8. When X is selected map it to X uncertainty and Y uncertainty

The changes that are made will work for the project on line!

This will be implemented in the following steps.

a. change all of the hash maps to linked hash map

b. edit comments in (Squid3Parser.java) specifically inline 87

c. make Classic X and Classic Y (Variable.Java)

d. reference the column by giving the column; if you are going to have to say (1) or (2)(datacolumn.java)

e. look at FX Data Column line 55 and 56

f. update the wiki

Next Steps:

Goal: Make the linking visually known for the user.

a. outline a dark line showing that 2 columns may go together

b. set rho to 0 in calculations if they want a circle and then their data still looks the same

c. create a fake column called RHO OF all 0's

d. The changes that are made will work for the project online! desktop

The changes that are made will work for the project online!

The next task is to fix up Topsoil's help section of the CIRDLES.org website and then integrate these links into the desktop and web app when applicable.

HW23: Chapter 22

Ex 22.6

Q: Fixed-price contracts, where the contractor bids a fixed price to complete system development, may be used to move project risk from client to contractor. If anything goes wrong, the contractor has to pay. Suggest how the use of such contracts may increase the likelihood that product risks will arise.

A: If the contractor is interested in a fixed price contract, they might not be extremely invested in the project. This gives me the feeling that they are more interested in getting the job done within a certain time frame at all costs as they would not be benefitting by gaining extra cash if they spent more time on it. I think it would increase the likelihood of a product arising. My next question would be, "how is the quality of this product?" If they are trying to push out this product within a certain time frame and plans do not go as scheduled, for the sake of the contractor losing money, would they be willing to sacrifice doing a little bit of extra testing because they do not have time? I think this ties in the ethics of the individual software engineering that may be working on the project. The questions I'm asking are dependent on the standards the developer holds themselves to.

HW27: Chapter 25

Ex 25.10

Q: Describe 5 factors that engineers should take into account doing the process of building a release of a large software system.

A:

When thinking about this answer I used the release of a phone as an example to think about.

1. Bug Fixes- fix prior software and or hardware version's problems

2. Marketing- publicity for the large software system

3. Compatability- make sure the new software is compatible with previous hardware and potential current hardware

4. Documentation- electronic and paper documentation

5. Testing and Inspections- doing both of these tasks thoroughly to prevent potential bugs or problems for the end customer/ user