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...

Risk Mitigations for Custom Applications

In many healthcare applications, often due to the cloistered nature of the use cases – e.g. it will only be accessed by users authorized in a particular facility, such as an operating room suite – the needs for Authentication and Authorization are minimized when the system is designed and implemented. This presents a risk as soon as you allow for the possibility of users with ill-intent or that otherwise want to operate outside their given roles. Custom applications need to consider these possibilities and implement the following measure to ensure the integrity of the system. 1. Authentication and Authorization Controls: Multi-Factor Authentication (MFA): Implement MFA for all user logins. This adds an extra layer of security beyond just a username and password. Role-Based Access Control (RBAC): Grant users access only to the data and functionalities they need for their specific role. This minimizes the potential for unauthorized access. Strong Password Policies: ...

You don't really know who you're talking to online...

The following is a story that I think highlights the assumptions that get you into trouble online... https://www.proofpoint.com/us/blog/threat-insight/i-knew-you-were-trouble-ta456-targets-defense-contractor-alluring-social-media This is particularly scary since we found so much utility in online connections during the pandemic and out of necessity, started trusting more online. Please note the timeline for this breach - it was a long, slow process, a key factor in many 'cons'. "Build trust" is a key first step, once someone has identified you as a party. You think...you're convinced you know who your talking to, but if you don't triangulate the identity with some non-online, ideally in-person information, you shouldn't trust. And even if you do get what seems like real-life confirmations of identity, you must look at questioning motives, needs, and keeping danger at arms-length. Online includes email, texting (sms), application chatbots, voice communicati...

Earnest Engineer

Search This Blog