Working Up

by Dwayne Phillips If a system designed to last a few months last 12 years, is that a success or a failure? A recent story hailed the success of the NASA Mars rover. The rover was “designed” to last a few months, but is still going after 12 years. Wow! What a great design and […]

[Read more →]

by Dwayne Phillips I review a requirements-management scheme that indicates no requirements management. I once worked in an organization that built systems. Everyone worked very hard and very long hours. There was one problem: We never delivered a single system Why not? The problem was with managing requirements. Each month we held a requirements meeting. […]

[Read more →]

by Dwayne Phillips Many projects make no sense. They are driven by two unspoken yet paramount requirements. I have seen many projects that were driven by two unspoken but paramount requirements: The project must cost a certain amount of money—no more and no less You have to look like you are trying to do something […]

[Read more →]

by Dwayne Phillips A great idea is merely a requirement; it is not a design. The thinker of the great idea is important, but so is everyone else involved in the endeavor. Allow me to start with a blunt statement: Steve Jobs did not design the iMac, the iPod, the iPhone, and nothing else that […]

[Read more →]

by Dwayne Phillips When you consider it, systems engineers do something that everyone already does. Right? Systems Engineers do a simple task: they ensure that all customer requirements are built, tested, and delivered. They keep lists and tables and all sorts of things that trace all work back to every customer requirement. So why do […]

[Read more →]

by Dwayne Phillips Should we send our customers to a veterinarian, i.e., someone who is accustomed to working with beings that cannot speak? First, a story: My granddad was a stubborn man. My granddad was ill and went to a doctor, an MD. My granddad was paying the MD a lot of money, so he […]

[Read more →]

by Dwayne Phillips Programming languages are relevant but not critical to software engineers, but recruiters at job fairs love this question. For the record, I list my languages. I have been going to job fairs recently trying to find a job. People claim they are looking for systems engineers, software engineers, and software systems engineers. […]

[Read more →]

by Dwayne Phillips Systems are built to satisfy the requirements of the user. Sometimes, engineers want to add things, i.e., they desire to add things. Such are “desire-ments,” and they can kill projects. I walked into an existing project. Well, I  wasn’t in the middle of the project, but I was to work with a […]

[Read more →]

by Dwayne Phillips How specific should a system specification be? How many resources should the spec consume? I propose a measure to help answer these questions – the Return on Specification Investment. A few years ago, I was reviewing a specification for a system that someone in the office had written. I came to one […]

[Read more →]

by Dwayne Phillips The Technology Imperative states that if a new technology exists, we need it. Logic and business school lessons don’t matter. It happened again this week. I was visiting someone at their office in another building. The man I was visiting was slouched over in his chair with a face that asked, “Why […]

[Read more →]