Posts Tagged ‘Protection of Intellectual Property’

How I Protect My Proprietary Data

August 27, 2017

The original purpose of my blog was to provide me an easy
means of reporting my activity on my personally funded
research and development activities on error-free software
development methods.

My research and development activities produces a large
quantity of proprietary data. How do I protect this data?
Simple! I do not publish it on my blog or any other web-sites.

The purpose of “reporting my activity” involves establishing
the date at which a particular task was accomplished. The
task is sufficiently identified to enable me to identify
the associated proprietary data and daily log which is
stored on my machines, flash drives, and DVD’s.

Also, please let me remind you that when your machine is
not connected to the internet, hackers cannot access your
machine.

Advertisements

How I Protect My Proprietary Data

March 25, 2017

The original purpose of my blog was to provide me an easy
means of reporting my activity on my personally funded
research and development activities on error-free software
development methods.

My research and development activities produces a large
quantity of proprietary data. How do I protect this data?
Simple! I do not publish it on my blog or any other web-sites.

The purpose of “reporting my activity” involves establishing
the date at which a particular task was accomplished. The
task is sufficiently identified to enable me to identify
the associated proprietary data and daily log which is
stored on my machines, flash drives, and DVD’s.

Also, please let me remind you that when your machine is
not connected to the internet, hackers cannot access your
machine.

Development of Basic Text Write/Certification Utility Libraries

August 9, 2013

The effort associated with the development, upgrading and testing the
basic output software parts library will be documented here. If there
is anyone who desires to assist me in this development process, please
contact me by e-mail.

The affected software parts and their functional description are listed
below. The purpose of this library is to be able to write or certify
one or more text files. These parts are similar to object oriented
subroutines. The parts that have been completely tested are noted.

_BASIC_OUT_CONSTRUCT: Initializes the library for a write or
certification function.

_BASIC_OUT_DESTROY:   Completes the operation by eliminating the
specific setup. COMPLETELY TESTED.

_BASIC_OUT_BEGIN_SETUP: Begins a setup procedure by which the files to
be processed are specified. COMPLETELY TESTED.

_BASIC_OUT_ADD_FILE: Add a file to the process list.

_BASIC_OUT_END_SETUP: Completes the setup procedure. COMPLETELY TESTED.

_BASIC_OUT_GET_WRITE_NO: Utility: Search the output file list for the
the specified file. COMPLETELY TESTED.

_BASIC_OUT_GET_READ_NO: Utility: Search the input file list for the the
specified file. COMPLETELY TESTED.

_BASIC_OUT_ALIAS_FORMAT: Utility: Check for duplicate file
specification.

_BASIC_OUT_FILES_BEGIN: Begin the processing of files. COMPLETELY
TESTED.

_BASIC_OUT_FILES_END: Ends the processing of files.

_BASIC_OUT_TEXT: Processes a text segment in a specified file.

_BASIC_OUT_CHAR: Processes a special character in a specified file.

_BASIC_OUT_END_LINE: Processes a CRLF in a specified file.

_BASIC_OUT_READ_SEGMENT: Utility — Reads a text segment or special
character.

_BASIC_OUT_BASIC_READ: Utility — Basic Read for text segment, special
character, or CRLF.

_BASIC_OUT_FILE_LINE_END: Utility — Find the next CRLF in the file.

_BASIC_OUT_ERROR_INITIAL: Utility — Initial Error Management System
file.

_BASIC_OUT_ERROR_RECORD: Utility — Record Error

_BASIC_OUT_ERROR_END_FILE: Utility — Record Unexpected End of File

_BASIC_OUT_ERROR_READ_OK: Utility — Permission to read a line

_BASIC_OUT_GET_NO_ERRORS: Return the number of error entries.

_BASIC_OUT_GET_ERROR_TYPE: Return the error type associated  with a
error number.

TITLE: Development of Basic Text Write/Certification Utility Libraries
_BASIC_OUT_GET_ERROR_LINE_NO: Return the line number associated with a
error number.

_BASIC_OUT_GET_ERROR_PREP_NO: Return the preparation number associated
with a error number.

_BASIC_OUT_TEST_NO_ERRORS: Verify the number of error entries.

_BASIC_OUT_TEST_ERROR_TYPE: Verify the error type associated with a
error number.

_BASIC_OUT_TEST_ERROR_LINE_NO: Verify the line number associated with a
error number.

_BASIC_OUT_TEST_ERROR_PREP_NO: Verify the preparation number associated
with a error number.

_BASIC_OUT_WRITE_REPORT: UTILITY — Record a certification error.
COMPLETELY TESTED.

_BASIC_OUT_VERIFY_ALIAS: UTILITY — Verify Postal Alias .

THURSDAY: 2013/08/08

STATUS: The detection of unexpected or missing end-of-files has been
successfully tested.

DETAIL: The end-of-file testing is not complete.  An attempt to read
the two blank lines the complete the file must detected as an error
when the lines actually been read contain text or special characters.

RESULTS: This library has been sufficiently tested to render it usable
in various applications.

NEXT TASK: The end-of-file testing will continue.

Open Source Software Development Tool: Upgrade Progress

June 30, 2013

It is planned to upgrade the Programmable Software Development
Environment to include the capability of reading the paste-in text
files where the each paragraph is one very long line.  You may need to
download the latest version of the Programmable Software Development
Environment to fully understand my reports.

The ability to read the paste-in text file is needed to certify that
the file has not been changed, was developed using the agree-upon
standard libraries, or has not been illegally copied.

SUNDAY: 2013/06/30

STATUS: The development/modifications of the software parts associated
with basic output library continues.  I briefly reexamined the need to
add a read segment command to find the next CRLF.

DETAIL: To properly perform the desired certification function, we must
read and compare all of the lines in the subject file.  We cannot
error-out when we find the first discrepancy.  In as much as many
segments will be read before the CRLF, we must be able to find the CRLF
command in a line with a reported discrepancy.

RESULTS: I was able to prepare a general-purpose read-segment utility
capable of finding the next CRLF. There is no current need to develop
an additional command.

NEXT TASK: I will continue to develop/modify the software parts
associated with basic output library. When completed, I will use the
testing of this library as a means of testing the new Programmable
Software Development Environment version.

Open Source Software Development Tool: Upgrade Progress

December 21, 2012

It is planned to upgrade the Programmable Software Development Environment to include the capability of reading the paste-in text files where the each paragraph is one very long line.

Currently, the Programmable Software Development Environment has the capability of reading a standard ASCII text file where the TAB character is replaced with a suitable number of blanks. Each line of the text file cannot be longer than 256 characters. On the other hand, the Programmable Software Development Environment has the capability of writing a paste-in text file where each paragraph is one very long line. This capability includes the ability to include special characters such the TAB.

The ability to read the paste-in text file is needed to certify that the file has not been changed, was developed using the agree-upon standard libraries, or has not been illegally copied.

THURSDAY: The new utility routine for precfile.cpp for completing a string of characters read from a “paste-in” file has been prepared. The next step will be to continue the required integration efforts.

Development of Utility Libraries

December 21, 2012

The activity associated with development of utility software parts libraries will be presented here.

CERTIFICATION FRIDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library has been prepared and is ready for check out / formal test. The check-out / formal test of this library is the next task.

CERTIFICATION SUNDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library check out / formal test has begun. The output file creation software parts have been functionally checked out. The functional check-out of certification software parts is the next task.

CERTIFICATION MONDAY ACTIVITY: The certification process involves reading the subject file and comparing it on a line-by-line basis to what is expected. The associated software parts library check out / formal test has begun. The functional check-out of certification software parts has been completed for certifiable files. The next step is to update and test the report handling software parts.

CERTIFICATION THURSDAY ACTIVITY: Portability problems between Linux and Windows environment were discovered and solved.  Specifically, the Programmable Software Development Environment, when reading the text file, handles the end of file differently.  The next step is to update and test the report handling software parts.