-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
Managing the development of software is a complex task – at least if the team grows above a few people or there is a demand for control patterns that is above informal working. You will need to be clear on your boundaries to teams or people with other accountabilities and on your general guidelines for
In my view, IT Architecture is important in order to ensure that: This can only happen if the IT Architect masters numerous disciplines: Ph.D.s and lifelong studies can be spent on all the abstract sides of information management, enterprise architecture and solution design, but so far all this has led to no silver bullets and
In my work I tend to include concept maps – which can be a bit of an elastic or confusing term. But in essence we capture the concepts that describes the domain that we intend to manage – and articulate the concepts relation to each other. So in a business context it will be the
I recently worked for a global freight forwarding company where I was involved in a project regarding data management. At some point I bumped into this model: The information here is really overwhelming – but in my opinion a fully zoomed out diagrams as this is essential if we want to be precise and aligned
We often use the term business logic or business rules when we want to talk about what we should understand when we build a business IT system or just when we try to set the documentation level of an IT system. But most of the examples that I can find in the open space are
The V-model provides a structured approach for managing the development of features and modules within both new and existing IT systems. It offers a visual representation that reveals the level of effort required to progress from conceptualization to implementation. While not delving into all the intricacies of the V-model, it presents the essential conceptual leap
sunevang 