req-fn-app-feature-list

To create a feature inventory, define system functions as online screens and batch jobs with consistent IDs (F-O-NNN/F-B-NNN), structured metadata, and actor mapping. This standardizes granularity rules where one screen equals one online function and one job equals one batch function.

The standard ID format for system feature inventory lists uses F-O-NNN for online screen functions and F-B-NNN for batch job functions. This standardization ensures integrity checks and alignment with related downstream design documents.

Yes, you can use this feature list approach for requirements scoping, feature list review, and updating. It produces a complete inventory that correctly connects to downstream design artifacts such as processing lists, screen definitions, and transition diagrams.

To check feature inventory integrity, verify comprehensiveness, ID format constraints, actor-name consistency, and summary description formats. These checks ensure alignment with related design documents and validate online and batch function mapping.

Your feature inventory needs to separate online and batch functions to systematically capture all screens and jobs without omission. This separation enforces distinct granularity rules and ID formats, ensuring accurate scoping and downstream artifact preparation.