Difference betwen computer science & software engineering

From Dr. Dobbs: Software Engineering ≠ Computer Science

The author puts forward the thesis:

Software engineering will never be a rigorous discipline with proven
results, because it involves human activity.

He makes a good case. There are numerous formal methods that are being used to eat away at the fringes of the unprovable in software engineering through formal processes - but it usually requires defining the problem without a human element.

Indeed, look at some of the highly regarded practices for engineering today - with phrases such as "code smells", "team cohesion" - are we really expecting formal proofs?

At this point in the analysis, I'm shaking my head since I don't want to understand why a degree in Computer Science (like I have) might have been a waste... but looking at the diagram and reading through to the end, he makes the relationship between the two clear and makes the world (as I see it) whole again.

This is from the point of view of someone who gained a B.S. in C.S. from a school with a heavy emphasis on engineering disciplines, rather than pure science or mathematics. This was after a senior year transfer from a prior C.S. program at a school geared towards pure science and math. I understood as I entered my senior year that I simply wouldn't be employable except as a mathematician. I have been grateful for the opportunity to see the engineering side of world academically.

Comments

Unit Testing - What to Test

This I wrote to answer a question that came up when we were discussing our software process and I was training developers on how to unit test. It seems a simple enough question, but I kept pondering it and delving deeper until I realized I needed to write this monograph. What unit tests should we write? How do we know what to test? Ideally, unit tests should cover every path through the code. It should be your chance to see every path through your code works as expected and as needed. If you are practicing Test Driven Development then it's implied everything gets a test. In the real world, you might not be allowed to test everything - for instance, if the testing suite ends up taking a week to run, then the world will have changed by the time it finishes and the test results will be obsolete. Unit testing at it's basic is testing an object, a method - the smallest unit of your code that it can test independently. It should test the inputs "goes into" an...

Healthcare and Health Informatics Glossary

Here is a glossary of terms useful in Healthcare and Health Informatics ACO (Accountable Care Organization) MEDICARE’s outcomes-based contracting approach Arden Syntax an approach to specifying medical knowledge and clinical decision support rules in a form that is independent of any EHR and thus sharable across hospitals ARRA (American Recovery and Reconstruction Act) the Obama administration’s 2009 economic stimulus bill Blue Button an ASCII text based standard for heath information sharing first introduced by the Veteran’s Administration to facilitate access to records stored in VistA by their patients. The newer Blue Button + format provides both human and machine readable formats. CCD (Continuity of Care Document) an XML-based patient summary based on the CDA architecture CCOW (Clinical Context Object Workshop) an HL7 standard for synchronizing and coordinating applications to automatically follow the patient, user (and other) contexts to allow the clinical u...

It's all broken...

So, Scott Hanselman struck a chord again: Everything's broken and nobody's upset . The worst part is I can see that I'm part of the problem on both sides . I've excused many problems with software - shrugging as I restart the software or reboot. I save my anger for those occasions where I fell I've lost serious work and substantial time. Other than that I accept problems, glitches, crashes as "the cost of doing business". I believe it's actually because I've amused myself and earned a living creating software, that I am able to accept what's often pitiable quality. I've spent time working on systems that are not much more than breadboards with wires cascading from it, where getting something, anything to work was a huge accomplishment. But that was then and this is now. No way would I put up with a car that suffers from numerous small problems as today's software can. And putting these two thoughts together, it's now frightening ...

Earnest Engineer

Search This Blog