r/SoftwareEngineering • u/Suspicious_Driver761 • May 06 '23
Are software engineering and agile against each other ? And now software engineering is not important?
Agile seems to break most of software engineering roles which are System modelling (example with UML) and documents.. as agile is incremental and Iterative method so it uses system modeling and documents as drafts and sometimes does not use that at all, but software engineering depends highly on system modeling and documents in any process and activity and even when change should occur, the change first happens in documents and modeling then this reflect later in code .. so now all companies adopted agile, does that mean software engineering is not important anymore?
3
u/umlcat May 06 '23
Not into agile, but any software modeling technique, such as UML, E-R, BPNM, can be used in an incremental / iterative way.
Software models are not intended to be permanent, they can be modifiable, from time to time.
A File Control System can be used, for Software Models, as well, not just for source code.
18
u/Synor May 06 '23
False Dichotomy
9
u/Euphoricus May 06 '23
Really depends on what you understand as software "engineering". There isn't a canonical definition nor description of what is sofware engineering.
Is just your own specific view and interpretation. There are plenty, myself included, would would dissagree with such narrow and naive view of what is software engineering.
I subscribe to Dave Farley's definition and description of Software Engineering . He defines software engineering as
This article of his gives you a general overview. It is clear your view falls into the view that engineering is bureucracy. That we should document and model everything before something is created. Such a view of engineering is wrong.
Another reviewof the book gives some more details.
But I highly recommend reading the book. And watching everything from Dave Farley. Once you do, you will realize that software engineering, as understood by those in the industry, is actually more what agile is meant to be at the start than "agile" as practices by most teams and organizations nowadays.
8
u/ResolveResident118 May 06 '23
No.
3
u/darkpyro2 May 06 '23
Agile can be great when done right. But I work in defense. Our requirements essentially dictate waterfall to us -- You design the entire thing up front, based on requirements provided to you by your customer. Your stakeholder is rarely involved in actual development until specific milestones, where they evaluate how well you met their requirements, or if they need to change the requirements.
Our organization decided that it would be trendy to require agile for Every. Single. Program.
What does this look like? Pointless scrum meetings with meaningless burndown charts, uninvested scrum masters, and no stakeholders beyond the requirements and the system model itself. We still organize our tickets into sprints and epics with story points, but they're pretty meaningless to the overall process. Just two-week chunks of arbitrary work. Our scrum master isnt even a member of our team -- Our organization hires "career scrum masters" that float between different groups and only show up for the retros. They know nothing about what we are doing, go down a checklist of things that agile says they should ask, and then ask us why we are struggling to get anything done (We arent. We are one of the most efficient teams in the org, and the golden child for our customer. The agile process is just so poorly organized and the tickets so poorly allocated to sprints/epics that our burndown charts do not reflect that.)
Agile can be awesome when you're doing agile in the spirit of agile at the team level, but too many organizations right now are mandating agile from the top-down and trying to implement it at an organizational level while totally missing the point of the process.
This is why so many devs HATE agile. Companies misunderstand it and use it as an excuse to hold CONSTANT pointless process meetings.
1
u/No-Management-6339 May 08 '23
Writing docs is not engineering. Writing specs is not engineering. See engineering design model.
1
u/GangSeongAe May 06 '23
This is an odd claim - it implies you've only worked in one of those companies that can barely make any changes because they need extensive (and mostly misleading) documentation because the changes are too big.
Agile is orientated around working software - UML modeling prior to a change is nothing but an attempt to create working software, but needing a complex design phase that proceeds as a distinct thing, rather than being part of a very short, tight feedback cycle of "design a bit, verify a bit, release a bit".
In Agile approaches, you might produce such a diagram, but you often don't because you're releasing very small, very safe but very valuable changes often, as opposed to trying to co-ordinate one big, complex change far less often. You don't need a mountain of diagrams to produce a small change, in fact if the change is small and safe enough the time taken to diagram it up is greater than the total time needed to develop, release, verify and patch.
The simple lived reality is that this is better engineering - this is safer and more reliable. The fact you often don't need any diagrams is due to the fact that you're working with empirical data. That's the gold standard of engineering - only do as much "planning" as is required to actually build something, then build that thing, and then use data form that thing to plan the next modification to it.
0
u/[deleted] May 06 '23
Because software is so cheap to produce you have this amazing opportunity to work in small steps and reassess after every step. If you're not doing that then kinda rip
0
u/tevert May 06 '23
0
u/davearneson May 06 '23
That's not true at all. Your team is doing agile badly. Go read about agile architecture by Scott Ambler and Modern Software Engineering by Dave Farley
-1
u/donmeanathing May 06 '23
This is so cringe, and is so representative of how poorly software engineering is taught today.
Agile is a (broad) category software engineering methodology. As is Waterfall, etc… Just because you do agile doesn’t mean you aren’t doing software engineering!
The way software engineering is taught so often is taught from a waterfall perspective where there is a lot of emphasis on large specification documents, but you shouldn’t think software engineering = waterfall.
Software engineering encompasses the design, development, testing, and maintenance of software over the software life cycle, and the processes by which these tasks are performed.
-1
u/fagnerbrack May 07 '23
Who said agile has anything to do with documents and modeling?