11-14-2022, 04:43 AM
Just in case you geek out on this kind of stuff or are otherwise interested/curious...
SDLC = Software Development Life Cycle
I'm just in the process of laying out BAM's "SDLC" Tools, starting out with the basics:
Imagine you're working on a complex QB64PE project.
You have an idea, you add it to BAM via the Idea Manager.
That Idea may eventually get deleted/dropped, or may transition into being a new Requirement, or transition into being a Change Request to a previously fulfilled Requirement (a requirement can be a defined need to solve a defined problem, might be a feature, might be a constraint).
If it is a new requirement, eventually that requirement transitions into being a task. When that task gets completed, it transitions to being a fulfilled requirement AND a completed task.
If a Change Request, that change request is linked to some previously fulfilled requirement, and eventually the change request transitions into being a task. When done, that task transitions to being a completed task AND an implemented change request.
An issue (problem/bug/whatever), that issue might be related to a previously fulfilled requirement, and eventually the issue transitions into being a task (AND an issue in the process of being resolved). Or the issue transitions into being a new requirement, and the new requirement eventually transitions into also is a task (AND an issue being resolved).
Something like that.
Just piecing together "flow" to have an idea how to build the "managers" of all this info, and the "editors" for all of this info.
SDLC = Software Development Life Cycle
I'm just in the process of laying out BAM's "SDLC" Tools, starting out with the basics:
- Idea Manager
- Requirement Manager
- Change Request Manager
- Issue Manager
- Task Manager
Imagine you're working on a complex QB64PE project.
You have an idea, you add it to BAM via the Idea Manager.
That Idea may eventually get deleted/dropped, or may transition into being a new Requirement, or transition into being a Change Request to a previously fulfilled Requirement (a requirement can be a defined need to solve a defined problem, might be a feature, might be a constraint).
If it is a new requirement, eventually that requirement transitions into being a task. When that task gets completed, it transitions to being a fulfilled requirement AND a completed task.
If a Change Request, that change request is linked to some previously fulfilled requirement, and eventually the change request transitions into being a task. When done, that task transitions to being a completed task AND an implemented change request.
An issue (problem/bug/whatever), that issue might be related to a previously fulfilled requirement, and eventually the issue transitions into being a task (AND an issue in the process of being resolved). Or the issue transitions into being a new requirement, and the new requirement eventually transitions into also is a task (AND an issue being resolved).
Something like that.
Just piecing together "flow" to have an idea how to build the "managers" of all this info, and the "editors" for all of this info.