How difficult is the engineering

Difficulty in software engineering

Difficulty in software engineering
Hello dear forum,

Question:
I don't fully understand why software technology is difficult and what influence software technology has on the development process (effects)

My understanding:
As far as I understand, the software engineering discipline is responsible for software management, software quality management and software development. Then there are different procedural models that bring advantages and disadvantages to the development process, but I think the question should be understood again in a generalized way. For example, I know why it is difficult to develop software, but I don't fully understand what specific influences software technology has on the development process. I hope someone can help me with examples. Sometimes I find simple questions more difficult than specific questions.
Re: Difficulty in software engineering
Based on how you ask the question, one can conclude that you have no idea about software engineering and / or software development -> Shouldn't be an insult!

In general, it's like being on a construction site.

Architect -> Software Engineer -> Plans the house / software
Mason -> Programmer -> Builds the house / software exactly according to plan

And why it is always said that one (software engineer) is much more demanding than the other is because it is so.

The planning describes, at least theoretically, the entire software and ensures quality, description of all tasks, the complete program and the solution of all problems.

With good software engineering, the programming step is theoretically only the transfer of all constructs, considerations and solutions in the form of source code of the respective language, without having to look for solutions or encounter problems.

I am only following the guesswork here, if you really had to know that, so it would be necessary for you to know, then you would know too!

I hope I could help!



Edited 1 time. Last on 05/02/2020 17:55.
Re: Difficulty in software engineering
By Stefan309 I know, for example, why it is difficult to develop software, but I don't fully understand what specific influences software technology has on the development process.
It differs from area to area. E.g. database programming. I myself come from the SAP area. We pretended. gladly in SQL, although HANA is better. Theoretically yes, but in practice the hardware usually slows down the theoretical advantage.
Re: Difficulty in software engineering
By yvonne87 Based on how you ask the question, one can conclude that you have no idea about software engineering and / or software development -> Shouldn't be an insult!

In general, it's like being on a construction site.

Architect -> Software Engineer -> Plans the house / software
Mason -> Programmer -> Builds the house / software exactly according to plan
With a little software - Klitschee that could get there. At a corporation you forgot the structural engineers, those who tell the architects whether their construction will hold up at all. So the mathematicians who develop the algorithm. Of course, that doesn't exist in small clichés.
Quiet (unreg.)  📅 02.05.2020 18:19:40
Re: Difficulty in software engineering
By yvonne87Based on how you ask the question, one can conclude that you have no idea about software engineering and / or software development -> Shouldn't be an insult!

In general, it's like being on a construction site.

Architect -> Software Engineer -> Plans the house / software
Mason -> Programmer -> Builds the house / software exactly according to plan

And why it is always said that one (software engineer) is much more demanding than the other is because it is so.
On the basis of your answer one could assume the same thing to you.

What you say is technically not wrong, but it does not reflect the reality in which such a separation does not actually exist. The companies that can afford a separate software architect often do nothing more than model at a very high altitude. Tasks are usually not broken down and modeled in such a way that a developer actually only has to program and no longer solve problems and no longer have to make decisions. As a rule, companies only have software developers, and neither programmers nor architects, and they all do what belongs to software development.
Re: Difficulty in software engineering
By yvonne87 Architect -> Software Engineer -> Plans the house / software
Mason -> Programmer -> Builds the house / software exactly according to plan
The concept was tried in the 90s, it has nothing to do with modern software development. Code monkeys or pure programmers who implement requirements (e.g. UML diagrams) according to precise instructions are almost nonexistent today or only in old-fashioned large corporations that do not manage to get a software right.

Especially in non-technology corporations, e.g. the automotive industry, people still try to produce (not develop) software, which of course doesn't work. That is why SWE is often implemented by external service providers.
Re: Difficulty in software engineering
I think my, as written, rough description still applies quite well.

Personally, when I do a little software engineering in my private life, I proceed quite simply and not completely. So logically no requirement specification or flowchart etc. for me.

Use cases
Class diagram
Petri Netz (I just like more than a graphic chart)

Usually enough for me.
Re: Difficulty in software engineering
By I3enjaminWith a little software - Klitschee that could get there. At a corporation you forgot the structural engineers, those who tell the architects whether their construction will hold up at all. So the mathematicians who develop the algorithm. Of course, that doesn't exist in small clichés.
Mathematicians are only technical experts and cannot be compared with structural engineers. The evidence that software works correctly is ensured by means of (random) tests or completely ignored. Depending on the application, you don't need a mathematician, but an aircraft instructor, electrical engineer, biologist or kindergarten teacher.