The boundary for an Internet/Intranet application is defined in a similar way for traditional applications. For traditional applications the boundary is not drawn just around the user interface or a group of screens but around the entire application. Frequently, Internet/Intranet applications are just extensions to current and existing applications. There is a tendency to create a "new" application for the Internet/Intranet extension, but this approach is incorrect.
The boundaries for client/server applications need to be drawn around both the client and server. The reason is that neither the client nor server supports a users (or sophisticated) view. That is, one alone does not represent a total application. As mentioned early, any complete application needs both data at rest (server) and data in motion (client).