Fyi, I put together a concept diagram as a guide to follow as I setup the 
user interface elements: BAM Support for SDLC Processes and Artefacts  
<https://docs.google.com/drawings/d/1GE1DXLSZVn1l9hxFWMWRWTdCYsIJdJaP007s4f08TjM/edit?usp=sharing>



On Monday, November 14, 2022 at 12:52:10 AM UTC-4 Charlie Veniot wrote:

> Follow-up to https://youtu.be/74pUOtpSnww
>
> Just in case you geek out on things related to software development 
> process or project/task management in general...
>
> I'm just in the process of laying out BAM's "SDLC" Tools (SDLC = Software 
> Development Life Cycle 
> <https://en.wikipedia.org/wiki/Software_development_process>), starting 
> out with the basics:
>
>    - Idea Manager
>    - Requirement Manager
>    - Change Request Manager
>    - Issue Manager
>    - Task Manager
>
> Imagine you're working on a complex software development project (for some 
> freakish reason, it is in BASIC).
>
> 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.
>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/12892b27-2ad4-4e0a-81b6-3ac5514ab3ecn%40googlegroups.com.

Reply via email to