Management of models

[livam]

Ideally, I would like to enable well-defined model management, which would include our organization's Architectural Review Board (ARB) and integrate security approvals into the model creation process. To ensure that our model management lifecycle process is consistent, accurate, and complete, models should represent both standard and nonstandard software and be linked to associated software contracts.

[frankeck]

Hi Livam,

have a similar topic. First, do you have an organization who is able to manage that? Then think about processes, Software Model creation or check shall in my view be part of Software Onboarding/Offboarding process.

So I have three basic use cases, bringing in a new software into the company, change an existing one, retire a software.

Depending on the kind of Software, you might have a Demand as a trigger or a project.

The basic stakeholders we consider are, without a specifc order here.

• Requestor, might come in via Demand (if you have SPM), might come in via a Service Request
• Architecture Board, to check if the Business capability is covered by an existing solution which might do the trick
• Licence Management, to create the Software Model, Discovery Map, Software Entitelment and so on
• Procurement, again depending on the setup a pure procurement or have additional task like negotiating, setup supplier and other related master data
• Data Security/Data privacy
• Legal for contractual topics
• Worker Council
• Future Product Owner, depending if it a small Desktop application or a full blown system

Are you using SAM already? Because Software Models are only a small part of the world.

Best regards,

Frank