The Unified Modeling Language (UML) defines the industry standard notation and semantics for properly applying that notation for software built using object-oriented (OO) or component-based technology. In fact it is difficult to find modeling books or tools that do not use the UML these days. The UML provides a common and consistent notation with which to describe OO and component software systems, decreasing the learning curve for developers because they only need to learn the one modeling language (in theory at least). The UML is clearly a step in the right direction, we are no longer fighting the “notation wars” of the mid-1990s, it isn’t perfect. In this article I argue that the UML as it stands today is not sufficient for the development of business software and that the vision of Executable UML is a little (okay, a lot) ahead of its time. Perhaps we should define the modeling languages which we use via open source, not via committee.Be Realistic About the UML: It's Simply Not Sufficient
Showing posts with label SharePointobject model. Show all posts
Showing posts with label SharePointobject model. Show all posts
Saturday, 28 February 2009
Be Realistic About the UML: It's Simply Not Sufficient
Labels:
model Object,
OO,
SharePointobject model,
UML


Tuesday, 3 February 2009
Understanding the Administrative Object Model of Windows SharePoint Services 3.0
Understanding the Administrative Object Model of Windows SharePoint Services 3.0
The SharePoint .NET object model. Just to review. SPWebApplication is the Web Application sitting at either a host heater or a port. It is an IIS web site. SPContentDatabase is the SQL Server Database assigned to a Web Application. Web Applicaitons contain one or more sites SPSite, and SPSite contains one or more SPWeb which are pages.
Quoting Microsoft
Some characteristics of the SPWeb class are as follows:
-
An SPWeb object can be a child of another SPWeb object or of an SPSite object. If it is the child of an SPSite object, it is the top-level Web site in its site collection.
-
An SPWeb object has a Webs property that returns a collection of other SPWeb objects; specifically, the immediate child subsites under it.
-
The class has a very rich set of members for programmatic administration and customization of the Web site.
A hierarchy of Web sites always has exactly one top-level Web site. This site is the child of an SPSite object. You can learn more about the top-level Web site in the section Windows SharePoint Services Site Collections later in this article.
Blogged with the Flock Browser
Labels:
SharePointobject model


Subscribe to:
Posts (Atom)