Project Components Should have Sub Components
Project Components are main features of an application. They often have sub components. (Sub features). The current flat list approach means that sub features (normally nested) must be included into soemthing of a mile-high list of components. - Nesting sub components makes for easier sorting and reporting.
EXAMPLE: Let's say this aplication that does video editing. This might be a small subset of all the feaures.
COMPONENTS:
- Audio
--- Audio Format support
---- Requires another sub test matrix WAV, AIFF, MP3, Oog. 8-24bit, 22-96khz etc..
--- Cue point marker support
--- ID3 Tag Support
--- Effects (Fade-in/Out, Crossfade)
--- Beat detection for video effects or markers
- Video
--- Fire support (matrix for file & compression types)
--- Playback & Scrubbing
--- Effects (Fade, disolve, crossfade etc)
- Images
--- Image Formats Supportted
--- Alpha Channel issues
--- Image effects (fade in/out, disolve, zoom etc..)
- Text
--- Placement & Editing on screem
--- Alpha Channel & Masking
--- Formitting (Kerning, Size, Scale, Stretch etc)
--- External file support (reading in TXT or other files)
- Export (muxing)
--- Another list of filetypes and compression types that could get confused with editing & import types
Customer support service by UserEcho