We are leaders in the commercial application of Object Oriented analysis and design and Component Based Development techniques. We use iterative and incremental working patterns to manage risk and optimise realisation of business benefits.

Communication

The essence of formal business modelling and system specification techniques is communication. We will show you how to use models to create a shared understanding between business users, analysts, designers, coders and testers. The beauty of the models is that they are accessible at each stage to the appropriate people that have a stake in the creation of the system. The models provide a basis for testing the completeness and correctness of the system design before it is committed to code. This has a dramatic impact on the quality of the end result.

Using the UML

We base our process around the Unified Modeling Language, UML, but we do not aspire to be UML purists. UML is a broad-based industry standard that can be used to describe a wide range of types of computing systems. In our use of UML we apply the Pareto Principle . the 80/20 rule . we use an optimal subset of the UML notation in a systematic way dependent on the type of project to get the best balance between the benefits achieved and the time and effort expended.

Stay practical

This does not mean we cut corners. It just means that we are focussed on the purpose and value of each modelling activity and concentrate our efforts on the most profitable ones.

Focus on delivery - don't get distracted

Our experience tells us that when organisations take on UML, often in tandem with one of the heavyweight proprietary development processes, they get bogged down or flounder under the weight of new things they have to learn. Taking on a new process in the pressured environment of a live project causes a great deal of tension. Typically teams are faced with four problems at once; understanding the new modelling concepts and techniques, planning and estimating with the new development process, mastering new software tools (such as the CASE tool) and last but not least the problem of identifying and defining business problem. There may be lots of documentation describing the modelling techniques, the new process and the tools but not enough time to read and assimilate it all.

How we can help

When adopting a new development process, teams need a combination of formal training, to get everyone aligned on how they will be working, and hands-on mentoring support from people who have been through the process before. Only with experience can a practitioner distinguish whether they are struggling because they don't understand the business or because they are not applying the technique correctly. Without this support teams will often give up and revert to what they know, or at the very least they will create their own non-standard interpretations of the process.

Karona have many year's practical experience of using UML and iterative and incremental lifecycles in a variety of industry sectors. We can bring that confidence into a project team and help them get off on the right foot.

We will typically get involved with project definition, project planning, business analysis and modelling, requirements analysis, system specification, system design, test specification and test planning, and logical architecture definition. We can also assist with the definition and specification of technical architecture and technical frameworks.

We have long experience with most of the major CASE tools and development toolsets.

Our process is not confined to green field development. Most projects nowadays have a strong element of integration with existing systems and / or package implementation. Because our process has a simple framework with clear purpose, we can flex it to a variety of project models.