Conclusion

In this chapter, we started the process of building a sample application that will make use of our CSLA .NET Framework. It's a simple project-tracking application that maintains a list of projects and a list of resources, and allows the resources to be assigned to the projects.

To design the application, we used an object-oriented analysis technique that involved creating use cases that described the various ways in which the users need to interact with the system. From those use cases, we created and refined a list of potential business objects.

That object list was then used to create a preliminary class diagram that showed the classes, their key data fields, and their relationships. Based on the diagram, our understanding of the business domain, and our use cases, we were able to refine the design until we arrived at a final class diagram that described the business classes that will comprise our application.

We then went through the business classes and determined the appropriate CSLA .NET base classes from which each should inherit. The editable business objects inherit from BusinessBase , and the collections of editable child objects inherit from BusinessCollectionBase . The lists of read-only data inherit from ReadOnlyCollectionBase , and our list of simple name -value data inherits from NameValueList .

We also walked through the process of creating a simple relational database to store the data for our application. In most applications, the database already exists, but in this case we had the luxury of creating a database from scratch. Even so, it's interesting to note the differences between our object model and the relational model, thus highlighting the fact that a good object-oriented model and a good relational model are almost never the same.

In Chapter 7, we'll implement the business objects that we designed in this chapter. Then, in Chapter 8, we'll build a Windows Forms UI based on those objects. In Chapter 9, we'll build a Web Forms UI, and in Chapter 10 we'll build a web-services interface that reuses the exact same objects. Finally, in Chapter 11, we'll look at some options for reporting against our business objects.



Expert C# Business Objects
Expert C# 2008 Business Objects
ISBN: 1430210192
EAN: 2147483647
Year: 2006
Pages: 111

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net