A conference in Malmö for software developers

Java Speakers

• Alef Arendsen
• Aslam Khan
• Ben Alex
• Bruce Snyder
• Dierk König
• Johan Haleby & Jan Kronquist
• Jonas Jacobi
• Joshua Marinacci
• Ken Gilmer
• Kirk Pepperdine
• Martijn Dashorst
• Mattias Arthursson
• Nikita Ivanov
• Olaf Heimburger
• Rickard Öberg

More with Aslam Khan

• Seminar - Designing for Modularity
• Seminar - Managing Diversity Challenges in Agile Teams
• Workshop - Bootstraping your SOA project

Aslam Khan, factor10, South Africa

Aslam Khan has eighteen years of professional experience covering software architecture and development using design patterns, agile methodologies and various static and dynamic programming languages. He works intimately by coaching software development teams to design and build sustainable, low maintenance enterprise applications by focusing on team agility, simplicity over complexity and by taking the fundamental position that design is more valuable than a technology.

He holds the philosophy that successful architectures and enterprise applications can be achieved if one immerses themselves completely in the business domain of the enterprise.  With a degree in Electronic Engineering, Aslam believes that software architects must be able to build what they draw and still finds room in every engagement to practice his craft of software development.  

Aslam is an architecture and design coach at factor10 (http://www.factor10.com) and looks after factor10 interests in South Africa.  He is a regular writer in various technical forums and speaker at local and international events and is a dzone.com editor for the Architecture zone (http://architects.dzone.com).  You can read his blog at http://aslamkhan.net.

Solving Domain Problems with Aspects

Aspect Oriented Programming (AOP) is a notoriously difficult topic which many do not grasp at the first attempt, or even after several attempts. Although AOP has its roots in fundamental object oriented patterns, part of the problem with the complexity in AOP is the terminology and language used. Another contributor is the examples of problems that are typically solved using Aspects. Commonly, aspects are used to solve difficult infrastructure problems within applications, such as caching, transaction management, authentication and authorization of objects, lazy loading, amongst others.
Comparatively, the use of aspects to solve domain specific problems is less frequent. It is certainly not a first choice technique because it is poorly understood and carries the perception of introducing complexity. However, by focusing on the simplicity of the patterns upon which AOP is founded, many domain specific problems can be solved elegantly and simply.
In this seminar, we will cover the following:
The basic set of object oriented patterns upon which AOP is founded
Thinking about aspects without being tied up with AOP terminology as a transitioning technique to moving to AOP
Examples of real world domain problems where aspects were used to solve the problems
From these examples, patterns are extracted which can be used as targets for AOP solutions
If code examples are needed, Java and the Spring Framework will be used, but the patterns and material covered will be applicable in other languages and frameworks.

Gold Partner