Working Up

by Dwayne Phillips A review of one of the fundamentals of systems engineering. We create and manage budgets of key technical performance measures. System engineers work with technical budgets. Examples: size weight power attenuation memory use RAM memory use disk time to complete an operation We are building a smartphone. We are told to keep […]

[Read more →]

by Dwayne Phillips Someone who had a big influence on my life has passed away. “The Mote in God’s Eye.” Star Wars was in theaters, and everyone was enthralled. The science fiction community tried to fit in with Luke, Han, and the rest, often in vain. Every science fiction commentator had their own list of, […]

[Read more →]

by Dwayne Phillips This paraphrase from Through the Looking Class continues to reign in systems development. The title of this post is a famous paraphrase from the classic Through the Looking Glass. I live it most days. The conversation goes something like this: Me: The system won’t do such-and-such. Builder: Of course not. It wasn’t […]

[Read more →]

by Dwayne Phillips Another fundamental question in systems engineering. Like the rest of the questions, ask with caution. Ever ask the titular question at work? Ever ask it out loud and expect an answer? Perhaps you are a systems engineer. Perhaps your workplace needs a systems engineer. The question seeks to find the reason behind […]

[Read more →]

by Dwayne Phillips There is a fundamental question to ask in analyzing and engineering systems. Why don’t we use it more often? A: We put this into the system. B: And then what happens? A: Well, now the system can do this great function for the users. B: And then what happens? A: For one […]

[Read more →]

by Dwayne Phillips Agile development is not an excuse for knowing what you did, why you did it, and how you did it. You’re doing agile development. You hold a meeting to start a sprint (different methods use different names for this). You sprint! You meet again at the end of the sprint. What did […]

[Read more →]

by Dwayne Phillips What is systems engineering? One answer is, “you can do it with only a pencil and piece of paper.” I have been plagued with the question, “What is systems engineering?” for too long. As a job seeker, a common job opening is Systems Engineer. A quick reading of the job description shows […]

[Read more →]

by Dwayne Phillips One function of systems engineering is to open the black boxes, look at the entire system, and apply some wisdom. We often build systems by connecting existing systems and subsystems. These existing pieces are black boxes, i.e., we don’t know or don’t care to know what is inside them and how they […]

[Read more →]

by Dwayne Phillips Sometimes we have to update the technology even when old technology still does the job. Requirements are real. We work to meet requirements in systems. Once the requirements are met, that is it. But what about the people? Many years ago, I worked with a system that used old technology. It was […]

[Read more →]

by Dwayne Phillips Systems are commonly built by connecting smaller systems. This requires that the systems are connect-able, and that requires a defined interface. Most of the time, we build systems by connecting large boxes together in a system diagram. There are exceptions, and another post will discuss some of those. Still, connect the boxes […]

[Read more →]