ICRA and ISBPRDVLMO

These two acronyms are the framework in which I organize and categorize the lifecycle of changes to work products in a system.

ICRA (pronounced "Ick-rah")
I = Identification (what work products are called, how they are identified, what classification method or standard they use)
C = Control (how access and changes to work products are managed, access controls, change mechanisms, guard rails)
R = Report (details on activities around changes to work products, who made them, when, etc.)
A = Audit (the trail of access and changes to work products)


ISBPRDVLMO (pronounced "Is Beeper Dove Elmo").  It represents the end to end lifecycle of components for product lines.
I = Identification (application identification codes, what things are called, who's leading it, the team, etc)
S = Source (source work products, where they are stored, how updated, access controls, etc)
B = Build (transform from source to packages/images)
P = Package/Publish (how product is packaged during or perhaps separately from build process, and how they are published to repositories)
R = Release (how components are released)
D = Deploy/Delivered (how components are deployed/delivered)
V = Verify (how components are verified once deployed/delivered)
L = Log (how component logs are logged, managed, set up, handled, archived, aggregated, analyzed, etc.)
M = Monitor (how components are monitored, managed, set up, handled, archived, notifications, etc.)
O = Operate (how the application is administered, operated, by who, docs, procedures, escalations, etc.)