Our CSLA 4.0 Implementation - Update #1

During the first third of 2013 I learned a lot about CSLA. Most importantly, during that time I realized how much is there to know about this framework.

1. It is not just an ORM tool. It is a framework for developing Business objects based on an Object Oriented Analysis and Design approach (i.e. object-oriented application vs data-driven application).
2. It has a learning curve, but it is worth the investment in it.
3. It follows 4 "simple" steps:

• Rely on the Use Case (or User Story) to understand and identify the entities and behavior that the Use Case requires
• Identify the required object attributes and CSLA stereotypes for the entities identified
• Identify other auxiliary classes that are needed to accomplish the use case (i.e. other classes required to implement Software Patterns)
• Determine if there are opportunities for behavioral reuse

4. It will be easier to learn if you already know / understand:

• WPF or SilverLight
• Model View View-Model presentation pattern
• C# language (although you can still use VB.NET)
• .NET framework
• n-tier architecture
• Windows Communication Foundation

5. Requires a lot of reading. If you are drawn to new learning and understanding new software development approaches, this part is the "fun part".
6. Install the demos, read, read, and read some more.

During the year, my hope is to narrate an account of our experience in learning and implementing CSLA 4.0 fully.