Ready.
copycat82/83 is in the field of computer science, with a claim to model distributed systems, but it is only a total lack of achievement - worse than trivial.
copycat82/83, itself, is uncurable. If its plagiarism, and immense faultfullness, were to be "heal"ed, nothing else would remain, out of it. This first-aid kit, instead, is a remedy for the readers - to avoid contagious ignorance.
Plagiarism means copying ("borrowing") from others, although being expected to deliver self-made (original) work. You may read further on the page Plagiarism. The page also briefly dicusses some relevant issues.
To earn a Ph.D., is the/a critical, turning-point - professionally. And the degree-granting juries must feel, if anything, the heavy responsibility when granting such a degree, and must concentrate on the objective facts, the tangible work, being already presented. Not on some sweet sensations, or diverted virtues like a misplaced-"benevolence" which is only a cruelty to many others. That not only introduces unfair-competition which can only cloud the accomplishments of the deserving recipients, but may probably leave generations of rather bright students and other employers, facing an incompetent service of teaching and/or research.
The philosophy-relevance of a Ph.D. may be the tools used by the philosophers, which a Ph.D. also must use, when producing the required original contribution to the field. Those tools involve thinking: Observing the facts, formulating of (new) ideas, comparing and contrasting, etc. The subject matter need not be something ordinarily considered "philosophical." As an example, Newton is/was called a philosopher, whereas today the physics-thinkers are most usually called physicists. You may read a discussion and some details on the page Ph.D..
An abstract specification is the art and science of telling only so much as needed. You can find examples, and some further information on the page (Abstract) Specification.
Petri nets is a visual, modeling and simulation tool. In its basic form,
it is only an explicit representation of the possible event sequences. Arrows show the
succession between the related events and conditions, and the token(s) may travel in the
directions pointed by the arrows. For more information, you may read the page
Petri nets (or, E-nets), and/or take it as
entertainment, and visit the page Learn-with-Fun: Petri Nets.
.
Event-modeling tells of a system in terms of what-event-may-happen-with-what-preconditions. The precondition may be a state of being. For example, when you are at the door of your house, the door-opening event may happen. The precondition may also be a time of clock. For example, when it is 17:00, some ring may bell.
When the event takes place, its effects may enable some other events to happen. For example, after you may turn the television on, you may start watching something on it. You can read the discussion on the page Modeling Events [and Data].
A (programming) method(ology) is some way of organizing the programming process. A method may sometimes come in the form of a set of principles, at other times, it may be some computer software or hardware that eases your programming, and makes harder in other ways. When you adapt to it, you are using its (implicit) method, even if you are reciting of no particular principle in your mind. You may read a bit more about this on the page (Programming) Method[ology].
A distributed system is any group communicating processes, each of which have their own CPU(s) to execute their own tasks. This may be within a multiple-CPU computer, as well as around the world. Of course, the capabilities and the problems may vary widely depending on the configuration. You may read some of the uses, and the usual difficulties with programming such systems on the page Distributed Systems.