The Gist of 2 Huge Structural Flaws in Computer Science (Software)
Recommend Documents
The Gist of 2 Huge Structural Flaws in Computer Science (Software). The software researchers committed two structural mistakes. The first kind of mistake was: ...
The Gist of Two Huge Mistakes in Computer Science (Software). The software researchers committed two mistakes. The first kind of mistake was: Relying on ...
The organization of cases provides a means for accessing individual cases when ..... Let Stb be the similarity between the new case and old case b and Solb.
Of course, many computer science programs now include software methodology and engineering as part of their curriculum, and some have adopted curricula ...
The interviewees were also allowed access to the interview questions before the actual interview. We also did ... interpretation was that the managers were in a better position to estimate ...... Thousand Oaks, CA: SAGE Publications. [9] Taipale ...
Abstract—Experimentation in software engineering supports the ad- vancement
of the field ... We describe a variety of experiments in the framework and discuss.
Abstraction is recognized as a key concept in Computer Science and Software .... however, always come naturally, and requires some degree of awareness.
3. We will come back to user and system requirements. Functional requirements.
• Statements of services the system should provide, how the system.
We can't just throw few dozens of programmers to start programming without any
detailed plans. Design is ... The output of the architectural design process is.
excerpts in this section are all taken from the code these students wrote for that ... The class excerpt below illustrates the use of inspectors in specifying method.
bear this notice and the full citation on the first page. To copy otherwise ..... Design patterns can be considered an integral part of most computer ...... CS1014/information/JavaKid8x11.pdf. [7] Gosling J. ...... teams in the field with the head qu
solutions, and questions related to data privacy issues in software engineering. ...
question of software engineering is how can a data owner protect private ...
University of Virginia. Department of Computer Science. Charlottesville, VA 22904-4740 USA. Tel: +1 804 982 2206 [email protected]. William G. Griswold.
Climate Change: Science and Software. Steve M. Easterbrook, University of Toronto ..... of consciousness program at the University of California, Santa Cruz.Missing:
Key Words: free software, open source software, software ethics, ethical uses of software ..... At best, she could appeal to the conscience of her fellow scientists and ..... The Mass Media as Discursive Network: Building on the Implications.
Software development relies on the use of models that ... In model-driven development the developer ..... removeCon f licts(Pairs,(qa,qb)) removes any pair.
Example: A team of 6 six students use Extreme Programming techniques to ...... metrics that could be used across all languages (some notably PHP are not ...
in the aspects of implementation method, memory organization, memory consistency model, cache coherence protocol, and application programming interface.
Jul 31, 2003 - School of Computer Science and Software Engineering. Monash University. Bachelor of Computer Science Honours (1608), Clayton Campus.
tinct from, software aging, is the system slow down caused by .... failure to apply this principle. q. Man textbooks on software mention this tech-. 1 nique , but they ...
2 systems. Moreover, content providers supply content such as data, music and game ..... and lists who are its collaborators (partners) in the software ecosystem.
of software engineering, software faults, and malicious attacks .... monitor the status of software at runtime. ... metrics used (i.e., CPU time, heap memory, etc.).
1 What nonsense! I can easily imagine ... get old, software aging can, and will occur in all successful products, ... In other words, nobody understands the modified product. Software that has .... The experi- enced programmer realises that this is j
Oct 22, 2015 - b Department of Academic Surgery, The Royal Marsden NHS Foundation Trust, Fulham Road, London SW3 6JJ, United Kingdom.
The Gist of 2 Huge Structural Flaws in Computer Science (Software)
The Gist of 2 Huge Structural Flaws in Computer Science (Software). The software researchers committed two structural mistakes. The first kind of mistake was: ...
The Gist of 2 Huge Structural Flaws in Computer Science (Software)
The software researchers committed two structural mistakes. The first kind of mistake was: Relying on unproven and undocumented beliefs for nearly past 50 years by concluding the beliefs to be self-evident facts. Hence BoK (Body of Knowledge) for the discipline of Computer Science contain many flawed facts (i.e. wrong beliefs that are considered self-evident facts). Any fact, concept or observation derived by relying on such flawed fact most likely be flawed (i.e. infected with the corruption). Since many of the newer concepts or facts added to the BoK by relying on already exiting earlier facts or concepts, corruption spreads across BoK over time as more & more new facts, concepts and observations are added to the BoK (e.g. to expand and grow the BoK).
The second mistake is: Considering and insisting that computer science is a sub-domain of mathematics, instead of treating computer science as an independent discipline for creating and expanding Body of Knowledge (or BoK) for addressing any kind of problems and/or issues related to software. Mathematics alone can’t provide knowledge foundation absolutely essential for addressing many problems and issues that must be addresses by software. Mathematics is just one tool for gaining certain kind of knowledge, but not the only tool for gaining all kinds of knowledge.
Mathematics can provide certain kind of knowledge or perspective, but can’t provide certain other kinds of knowledge for gaining comprehensive perspective. For addressing certain problems, we need more than one kind of knowledge and perspectives. That is the reason other scientific or engineering disciplines are using multiple tools for gaining necessary knowledge for respective subject (or domain).
Likewise, to address each of the problems that must be solved in the domain of software, computer science must use any and every proven tool for providing necessary knowledge foundation. No one can argue science is not a proven tool for gaining certain kind of knowledge. Refusing to use science (i.e. proven scientific processes and methods) for acquiring knowledge for software is a huge mistake.
If Google for "What is Science", one would see 3 descriptions. First sentence describes science as a tool to gain knowledge. Another two describes science as a body of knowledge for a particular subject (or discipline). Both are right depending on the context. Computer science is a body of knowledge for software. Computer science can and must use scientific processes as a tool for gaining necessary knowledge.
If I am right, it would open a huge uncharted territory that can be explored for decades by thousands of researchers of computer science (to expand the theoretical and knowledge foundations) and software engineering (to make new and useful inventions by relying on the expanded theoretical and knowledge foundations). The 1st mistake might be a manifestation of 2nd mistake. Mathematicians used axiom instead of discovering facts such as nature and properties of things like components.
