DYA|Software helps the architect to bridge between the various stakeholders and to direct the software realisation process at both the application and the enterprise level. DYA|Software helps the architect to think ahead and act effectively.

One of the challenges faced by architects is balancing the interests of the different stakeholders and simultaneously ensuring that the architecture offers solutions for the most important and complex demands. The architecture needs to comply with both functional and quality requirements and the organisation needs to be able to realise the system within its budget and existing plans.

A standard architectural framework, a standard architectural language and predefined architectural products do not of themselves guarantee a good architecture. Basically, they are merely frameworks for an average system and an average organisation. But just as the average person does not exist, there is no such thing as an average system or organisation. The one system utilises new technology, while the other is realised via a non-standard process. And a third system is required to support non-standard quality requirements.  A good architecture is geared towards the unique aspects of your system and its environment. DYA|Software can help to achieve that.

DYA|Software has the following core elements:

  • Working from what would the right architecture in your specific situation. This makes it clear which stakeholders, design choices and realisation tasks the architect needs to focus on. It also allows the architect to effectively utilise existing approaches. In addition, it forms the basis for assessments of the architecture.
  • The architecture reasoning model helps architects to make traceable and balanced  decisions and to bridge between business, technology and realisation process.
  • The incorporation of software architecture in the development and management process, such that the architect can manage and control the architecture.
  • The positioning of software architecture within enterprise architecture and its alignment with other architectures.
  • The embedding of applications’ common properties and the facilitation of their differences via a system family approach.