The journey begins with the view of the destination such as business functionality, technical resources and people skills.
Many services are outsourced to the partners’ computing nodes adding the significant latency to the core transactions, while the infrastructure is often outdated and needs optimisation. The necessary skills are not always available making the technology choices more difficult.
Understanding the business objectives and being clear in the architecture views is fundamental in defining the enterprise strategy. The technology choice and the applications transformation are based on that foundation.
Business always needs efficiency and innovations quickly, and the scope is defined as
What, How and When, and later Who
With the issues clarified and the goals appeared tangible, it is the right time to go into the technical and crucial details to do the proper technical planning.
Reviewing the whole scope helps to understand the architecture much better, as well as to evaluate the best fit middleware technology.
Architecture is emerging from the conceptual model of the business requirements and technology evolution. The change needs planning as much as new, and so the architecture of change begins the modernisation journey.
The assessment of the service platform provides the understanding of the systems and it’ interrelationships that is one of the definitions of the architecture. It is crucial to leverage on the good understanding of the service platform capabilities to understand the past and the future of the enterprise.
Usually the software is built on the service platforms and not just written in some programming language. Now days these service platforms are evolved to seamlessly integrate reducing the work-around created in the earlier days. The business applications are mapped to the robust domains on the service platforms. Cross-domain integration is supported by the media of the web services, mostly microservices, documents transfers and shared memory.
It is great to visualise the architecture, but the architectural language makes collaborations with the customers better. Using the modelling tools helps is essential for the architectural literacy.
The architecture process is based on the business domain understanding, and expertise in the service platforms installation, administration and configuration.
The consulting purpose is to take the customers from the architecture development to the software development.
- Solution architecture and it’ implementation detailed design
- Integration nodes and business application components design
- Architectural modeling with ARIS and IBM Rational
- ARIS and Rational tools setup and configuration
- Mentoring customer on ARIS and Rational modelling tools and processes
- Models transformation between the modeling tools from different vendors