Software Design: I create software designs and reports to the highest standard. UML, use cases, requirements documentation and capture, and more are all covered if required.
Experience within CMMI.: I have experience working to CMMI level 3 and have a fair working knowledge of Prince2. Whichever heavyweight process is involved I can work within that framework and produce designs and documentation to your requirements.
Agile Design.: Using the latest agile techinques including agile modelling, I can easily work within an agile project to help create a design that works for you.
Organic growth: Whilst having huge monolithic designs sometimes pays off, in my experience designs that are allowed to grow organically tend to produce the best results. Thats why I fully support all types of agile development where the design is part of the development work, not just an activity that is done in response to a documented list of requirements.

Design is important. But... I feel that taking on board principles from the agile manifesto is more important. People & communication over process & tools, and responding to change over following a plan are two tennets that should be followed where designs are concerned. Past projects have made clear that responding to changing requirements is much more important than following the original plan. If we'd followed the origianl plan the customer would be sorely dissapointed. Changing things takes courage, but blindly following a design is worse. Only trivial projects can succeed with fixed designs.

Continuous communication is key in giving the customer the product they need.