What is an excellent software architecture?

I know my question is too difficult to answer, but let me give you some background information.

Last year, as a software manager, I found a A new job, I think it can be done very well. I have extensive experience in many different programming fields, such as GUI, Web, RIA, web applications. I am a very good problem solver. Generally speaking, I know how Organize the code in a clean way. And I always work hard.

But almost a year later, I have to admit that my boss is very dissatisfied with my work. The most important reason is that he thinks mine The product software solution is not advanced enough.
I think I have carefully decomposed the system, and I chose the most popular platform for each component, and most of the code is robust and clean.

But my boss doesn’t think so. He really thinks we can do better. He wants not only good, but excellent. Something with almost the ultimate scalability looks very easy to expand, Some things have some great concepts and ideas.

This is a challenge I have never encountered. I don’t know how to show my boss whether the current system is good enough. I told him “We use xxx,yyy”, but he doesn’t know what they are. I showed him UML to explain what we did, but he is very interesting about C and skeptical of OO and UML.

Then Have you met some software architects who you feel are great, very good and easy to extend? I think I really need to look at some examples of what good software architecture means.

To be honest, I really doubt whether it is worth trying to build an architecture to prepare for some non-existent requirements, but I must make my boss happy to continue my work.

I suspect this is not a technical issue at all .I think your manager doesn’t really understand software architecture, but he may just have an understanding of popular knowledge.

Your job is to sell your architecture to your boss and manage him (Or their) expectations. If your boss is worried that your solution is not performance or scalability enough, then you probably have not fully grasped the relationship.

I don’t think you are doing anything. It’s completely correct to build something that might not happen. You can do it like crazy. You can’t expect everything.

I know my question is too difficult to answer, but Let me give you some background information.

Last year, I found a new job as a software manager, and I think I can do a good job. I have extensive experience in many different programming fields , Such as GUI, Web, RIA, web applications. I am a good problem solver. Generally speaking, I know how to organize code in a clean way. And I always work hard.

But almost a year later, I have to admit that my boss is very dissatisfied with my work. The most important reason is that he thinks that my product software solutions are not advanced enough.
I think I have carefully decomposed the system, and I The most popular platform is selected for each component, and most of the code is robust and clean.

But my boss doesn’t think so. He really thinks we can do better. He What I want is not only good, but excellent. Something with almost the ultimate scalability looks very easy to expand, and some things have some great concepts and ideas.

This is me Challenges that have never been encountered. I don’t know how to show my boss whether the current system is good enough. I told him “we use xxx, yyy”, but he doesn’t know what they are. I showed him UML to explain What we did, but he was very interesting about C and skeptical of OO and UML.

Then have you met some software architects who feel great, very good and easy to extend? ? I think I really need to look at some examples of what good software architecture means.

To be honest, I really doubt whether it is worth trying to build an architecture to prepare for some non-existent requirements, but I must make my boss happy to continue my work.

I suspect this is not a technical problem at all. I think your manager does not really understand the software architecture , But it may just be an understanding of popular knowledge.

Your job is to sell your structure to your boss and manage his (or their) expectations. If your boss is worried Your solution is not performance or scalability enough, then you probably haven’t fully grasped the relationship.

I think it is completely correct that you did not build for things that might not happen. .You can do it like crazy. You can’t expect everything.

Leave a Comment

Your email address will not be published.