All of this has very little to do with CAN. The only CAN terms here is CAN-ID and DLC, the latter meaning the data size in bytes (from 0 to 8).
The rest of the terms define something on a higher level than the CAN protocol itself, namely the carried data. CAN allows you to send any data you please over 0 to 8 bytes per package. It does not define or care what that data is.
Therefore it is not quite clear what you are trying to do here. Your tool seems strange and specialized, making assumptions about the higher level protocol used.
Explanation of the various technical terms:
Start Bit & Bit Length
"Start bit" is not applicable to CAN systems. Start bits are used in UART and similar protocols. Someone is using the wrong term, or this refers to some secret bit in the data. Bit length probably refers to the length of one particular data item in the protocol sent, such as 16 bits.
Little Endian vs Big Endian
This refers to the byte order of integer data, for integers that are larger than 1 byte. Wikipedia can give you the full story. Basically, in the 1980s the Intel camp preached Little Endian (ls byte at ls address) and the Motorola camp preached Big Endian (ms byte as ls address).
This can only refer to the data carried by the CAN package. the CAN low-level protocol itself has no endianess. (Other than in the CRC-15, which fixed Big Endian, you can't change it.)
Sign bit available, Two's Complement, Sign Bit
These all mean the same thing. These must refer to the data. Supposedly they are asking if signed numbers apply, and if so, what is the format. Apparently the option is two's complement (most common) or signed magnitude. If you don't know what two's complement is, then Wikipedia & study.
To sum it up, you can't do a thing with what you have. You must have a proper specification of what the higher level protocol is supposed to be and what format it has. Nobody on the Internet can tell you what data a particular non-standard protocol somewhere is sending out. The CAN standard does not specify this.
You show some table with 5 data bytes and say that DLC is 8 bytes. That doesn't make any sense. Supposedly you are to read a 16 bit data byte in Big Endian, two's complement format from byte 2 and 3.