Let me know if this isn't an appropriate place, but I feel developers are the ones I should ask.
I am trying to ask my software developers at work for the following functionality in our system:
- I have a set of attributes describing cooking method type of a product. There can be up to 10 methods, and each needs to be their own individual attribute, but I don't want all 10 blank attributes showing if I only have 2 methods.
- I'd like for JUST the next blank one to be visible and the other attributes to be hidden until they are needed.
EXAMPLE
- It starts with 3 blank lines
- Method 1 – ________
- Method 2 – ________
- Method 3 – ________
- I fill out 2 of them
- Method 1 – Bake
- Method 2 – Pan Fry
- Method 3 – ________
- I add a 3rd method, and so a 4th blank field appears
- Method 1 – Bake
- Method 2 – Pan Fry
- Method 3 – Deep Fry
- Method 4 – ________
I realize I could just send them all this, and I probably will in the more formal writing of requirements, but I'm trying to talk about this on calls and I am hoping there is a phrase I can use to describe this type of listing. Any ideas?
submitted by /u/Alternative_Exit_537
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/rJMzcQW