Abstract: A role based graphical user interface (UI) is used for receiving user input for entry/editing relating to projects/tasks using a limited display device. Functional components are grouped into logical hubs that may be displayed within the user interface. The groupings of the components are based on a role of a user (e.g. project manager, project participant, contractor, . . . ). For example, for one or more users, the role based graphical UI may group the following components together: expense entry and approval; time entry and approval; notification messages; collaboration of information (e.g. documents, project information, and the like); reporting; and settings. After selecting one of the components from the role based UI, a user may use a displayed component for interacting with the functionality (e.g. entering an expense, time entry, . . . ). The UI is configured to allow navigation between the different functions included within the logical hubs.

Abstract: A layered architecture for a web service is provided with a data tier, object representation, data transformation, and a service tier. Scalability is achieved by relying on relatively high degree of decoupling, lightweight data interaction, and reducing overhead of transaction demands. Custom web services can be built on top and leverage the capabilities of the flexible framework including lightweight transaction support, event-based business logic extensibility, and efficient data contract binding.

Abstract: A layered architecture for a web service is provided with a data tier, object representation, data transformation, and a service tier. Scalability is achieved by relying on relatively high degree of decoupling, lightweight data interaction, and reducing overhead of transaction demands. Custom web services can be built on top and leverage the capabilities of the flexible framework including lightweight transaction support, event-based business logic extensibility, and efficient data contract binding.