Traditional requirements gathering tends to focus on the data inputs, business requirements and data outputs. Obviously, in order to have a system that functions correctly and reliably, these needs must be met. However, in traditional software development, the user interface is typically thought to be something that we can change as we learn about the… Read More Design From The User Perspective
Recently, I wrote about how software development processes do not fail, the people involved with the projects fail. The idea in that post was that the processes are rarely followed the way they are written. The parts that fail are the people adding scope without following the process, the people underestimating the complexity of a… Read More Defining Project Failure
I was recently looking at Google Analytics and the data for this blog. For whatever reason, I was only looking at a two day span in the recent past, and I was focused on search keywords. One search caught my attention because it was short and was not one of the typical searches in this… Read More Processes Do Not Fail, People Do
A few weeks ago I talked about what a software engineer may do for design tasks. Today, we are going to take a step in a slightly different direction and look at how projects are planned and what a software engineer may do during planning. If you are just starting out as a software engineer,… Read More Software Engineering Tasks: Planning
Continuing with my introduction to software development posts, I have listed some of my favorite computer science books. Many of these are fairly theory based, or were really important when they were released. Many software developers I know have huge libraries, but I wanted to focus on some that I refuse to give away. The… Read More My Favorite Programming And Computer Science Books
Regular Geek 