Ready.


copycat82 - Page-by-Page
Raw Dumps of My Precise Commentary

copycat82 is patchy, vague, and immensely faulty. I employ a variety of approaches to make this clear to everyone, and to let my further arguments stand on this base of my solid presentations - available as the case-study about copycat82/83


this section

It makes sense to match against copycat82, at its own patchiness - even if not with its vagueness, and faultiness. Therefore, this section publishes, page by page, raw dumps of my fact-filled commentary.


While Reading These Pages

If the content is not familiar, the reader should first read about the prior art, literature published in the decade before copycat82. This should suffice, because copycat82 plagiarizes, any way. It only renames a few, and cuts-and-pastes a few.

There is also a starter's kit at this site.


Refer by-page...

For those who have the copycat82-text available, this section may be especially valuable, not to get lost among copycat82's false claims, faultiness, self-contradictions, etc. I present evidence upon evidence, against each page of copycat82, as raw dumps - with links to other pages, and sections, at this site. Thereby, you can keep in touch with the other sections, at this site, whichever page you start at. i.e: What problems, in fact, exist at that page, and how it relates to copycat82's overall failure.

The page numbers that are clickable, are the already published (web) pages. If you are interested about a page that is not published, yet, you may ask for it.






Literature overview (intro, 1, and 2)

Tell and Forget: Introductory overview

The papers listed in the literature overview sections of copycat82, are only to be not cited later in copycat82. That implies, their relevance is supposed to be ending there. No compare-and-contrast, with whatever copycat82 itself claims to be its own - neither at the introductory sections, nor at the conclusion. Doing that, in fact, would reveal that copycat82 plagiarizes - as we discover it, ourselves, at this site.

Page-by-page: i, ii, iii, iv, v, vi, vii, viii, ix, x, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22.





Sections 3.1., and 3.2.

Graph(s) [and data]

Page-by-page: 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63.





Section 3.3

Sample representations

Page-by-page: 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96.





Section 4.

Unreflecting, Patch-by-Patch, Cut-And-Paste of the Software Engineering Literature

Page-by-page: 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119.





Section 5.

Vagueness:
Is it Analyzeable, without Further work?

Petri nets are analyzeable, verifiable - mostly, with the reachability test. The vagueness introduced by copycat82, loses that ability, though. The (implicit, unstated) assumption of of careless-extensibility, turns out to be FALSE. There are no proofs-of-correct-operation in copycat82, and now, when we arrive at the fifth section, we find out that, in fact faultiness is the canon, in copycat82. The "verifiability" is degenerate, because the differences from ordinary Petri nets, are not dealth with properly.

Page-by-page: 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139.





Section 6.

Welcome to the Funerals
  Introducing the "Example Application"s

The "example applications" both deadlock, at their first (outermost) figures. They keep being faulty, in other figures, too. I call some of the errors, of copycat82, the standard errors, because those examples themselves suffice to demonstrate the worthlessness, the unworkability, of copycat82. i.e: You do not even have to find any further method-breaking counter-examples. You find them presented in copycat82, itself - as if they were correct. No care to read, and reflect, even about its own examples? As such, how could that be even a high-school project - with such a massive faultiness? (Let alone, being a Ph.D. dissertation - with nothing new in it, any way.)

Not to mention the breaches of visual-presentation. e.g: Drawing multiple occurrences of the same element, within the same figure. As such, when you are shuffling pages, back and forth, to track the multiple figures, of an example, finding the element-X in figure-n "only" once, does not suffice. You have to exhaustively read every label in a figure, to make sure that there exists no other occurrence of that very same element. Not to mention the broken arcs.

Page-by-page: 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152.



Any Questions?: . . (Request Content . . . . . Correct Errors . . . . . Submit Case Study . . . . . Report Content Similarity.)

LastUpdated: June 10, 2004
Page-version: 1_0_2 (Links-update: July 17, 2004)
Written by: Ahmed Ferzen/Ferzan R Midyat-Zilan (or, Earth)
Copyright (c) [1994,] 2003, 2004 Ferzan Midyat. All rights reserved.