Skip to main content

Lifecycle management - Securing "IST" and "SOLL" states in Bluedolphin object repository

Completed
Fred van der Meulen
  • What is your wish?
    Visually the “plateau” element can be used in worksets to make a distinction between IST and SOLL but this has no affect on the state of objects and relationships in the repository.

    Since architecture is about supporting our ability to continuously change we should be able to secure+filter the lifecycle state of objects and relationships in time, i.e. when checking the repository or when making new worksets or reports (based on a given date range)
     
  • What is the problem you encounter?
    We cannot store a past, current and future state (i.e. information architecture) in bluedolphin
     
  • Why do you want this wish?
    See bullet 1 - Now Bluedolphin can only store/work with a single lifecycle state in the repository - making modelling transitions quite hard.

    Our added value as architecture practitioners is to give our organizations insight / support the design and realization of changes in time (on processes, organisational, information/application, infrastructure). 
     
  • Do you have a workaround? And if so, what is it?
    Bluedolphin advises “misusing” their business unit functionality to create separate repositories - making lifecycle mgmt quite complex
     
  • How big is the problem on a scale from 1 to 5?
    4 - we can only store IST models in Bluedolphin now and no lifecycle mgmt is possible
9

Comments

4 comments

Date Votes
  • Official comment
    Nisha Haridas
    Edited

    Dear Fred van der Meulen ,

    ⁠ Finally, the wait is over – the first iteration of the Object Life Cycle is officially out! 

    Please note, this is just the beginning, with many more iterations to come as we continue enhancing its capabilities.

    For details on what is included in this initial iteration, be sure to check out the release notes.

     And stay tuned – there is more on the way!

  • Nisha Haridas
    Edited

    Dear Fred van der Meulen   ,

    Noted, your suggestion has been added to our backlog for future consideration given other planned priorities. Feel free to reach out if you have further questions. Have a nice day!

    0
  • Roeland Loggen

    Very major and important feature.

     

    Also see: As is(baseline) / To be(scenario's) separation in repository. – BlueDolphin (valueblue.nl)

    (2022!)

    Reaction then: This is definitely on our roadmap and a high priority. More on this subject in the coming year. 

     

    1
  • Fred van der Meulen

    Thanks for this comment. Missed that one - these requests can be merged!

    @Valueblue Koen van der Veldt could you please give us an update! 

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post