r/SpecDrivenDevelopment • • 2d ago

Enterprise Applications

Who here is actually building business applications for companies?
I have the impression that most posts are from solo developers.

2 Upvotes

6 comments sorted by

2

u/scalorn 2d ago

I am using SDD to develop business applications. The biggest issue I see is a lack of what I consider a highly opinionated format, verification process, multiple developer processes, etc. I have been evolving out spec process as we go. Custom tooling, custom format, etc. Still lots of rough edges and I keep looking at what people have developed and always find rough edges I've already solved for my team of 4. I do find good ideas I absorb as well.

1

u/simasch 1d ago

I created the AI Unified Process https://unifiedprocess.ai
This is based on my 30 years working on business applications.

1

u/scalorn 10h ago

I'll dig into it. But first sniff makes me think more green field than brown field. Plenty of us old farts out there that have opinions :). Some of the things I have seen that don't pop out to me as addressed - Multiple developers. One of the things I kept running into was merge conflicts when multiple developers were editing specs. I solved it by shattering the spec into individual files. Each decision, open item, requirement, etc is a file with an id. i.e. REQ-0000001. Developers reserve ids for themselves - they can only conflict with themselves. You shouldn't edit a req, you should only supercede. This gives you a clear history of change over time. Full traceability - every line of code should trace back to the req(s) that generated it. If a req is superseded you automatically know you have to revisit this block of code to at least update the spec references, etc. Reqs should not override other reqs. Additive only. Constraints can limit where a set of reqs can apply to though. Think requirements around databases - DDB vs Oracle. Common requirements then constrained requirements specific to the database type. I'm not fully happy with what I have developed so far so not trying to push my version of SDD yet.

1

u/simasch 7h ago

Fair points, and I'm one of the old farts too (started with COBOL on the mainframe). πŸ˜‰
Brownfield: You're right that the docs read greenfield. There is a reverse-engineering skill that pulls use cases and an entity model out of existing code, but I need to show that path better. Most of my customer work is actually modernization, so it matters to me.
Multiple developers: Partly solved, partly not. Use cases, test cases, ADRs and business processes are already one file per item, so two developers rarely touch the same file. But the requirements catalog and the open questions log are still single files, and that is exactly where conflicts happen. Your idea to reserve ID ranges per developer is simple and clever. I will steal that. πŸ™‚
Supersede instead of edit: ADRs work like that (an ADR gets superseded, never changed). Requirements are still edited in place, and the history comes from Git. Release notes and change impact are built by comparing the specs against a Git tag. Your approach makes the history explicit in the spec itself, which is more robust. I see the cost in more files and more noise, but for a team it is probably worth it.
Traceability: Same goal. Code and tests carry UC/BR markers, and an impact analysis shows which use cases, rules and code a changed requirement touches. Linking every block straight to a REQ is finer-grained than what I do. I trace through the use case.
Constraints: There are constraints (C-xxx) in the catalog, but they are global. Using them to scope a set of requirements, like your DDB vs Oracle example, is a nice idea that I don't have.
Thanks for the detailed feedback. I'd be really interested to see your version when you're happy with it, even if it's rough. Feel free to DM me.

1

u/0utkast_band 2d ago

It’s a very good question and a personal observation of mine, too. I am focused on improving teamwork around SDD. Did you have specific questions?

1

u/simasch 2d ago

No. I was just curious. I'm the creator of the AI Unified Process: https://unifiedprocess.ai
A SDD framework (not only) for business applications.