Dear Wiki user, You have subscribed to a wiki page or wiki category on "James Wiki" for change notification.
The "JamesUserTypes" page has been changed by SimonFunnell. The comment on this change is: First draft. http://wiki.apache.org/james/JamesUserTypes -------------------------------------------------- New page: = JamesUserTypes = James has, and accounts for, many types of users. The list below describes the role, knowledge and responsibilties.of each. ---- === Client === ==== Role ==== Clients use JamesTools to access JamesServices for the purpose sending, receiving, sorting, storing, viewing and collecting mail. ==== Knowledge ==== Clients have a summary knowledge of mail concepts with no specific knowledge of James. ==== Responsibilities ==== Clients are responsible for enjoying secure, reliable mail services. ---- === Administrator === ==== Role ==== Administrators use JamesTools to manage the throughput of JamesServices by implementing sophisticated mail infrastructures to meet the diverse needs of organisations and businesses. ==== Knowledge ==== Administrators have domain scope knowledge encompassing advanced mail concepts, management tool usage and specific organisation needs . ==== Responsibilities ==== Administrators are responsible for providing [[javascript:void(0);/*1259025065736*/|JamesServices]] to different Client types including * Managing client accounts, addresses and usage policy. * Combining matchers, mailets, sieve filters and Organisation objects into organisation/business services. ---- === Deployer === ==== Role ==== Deployers use JamesTools to manage the scope and lifecycle of a James instance. ==== Knowledge ==== Deployers have knowledge of operating systems (runtime environments), their supporting infrastructure (network/databases/filesystems/etc) and a general overview of the James server ==== Responsibilities ==== Deployers are responsible for making JamesServices available to Administrators. * Installing, integrating and updating the server package/components. * Starting, stopping and monitoring a James instance. ---- === Developer === ==== Role ==== Developers enhance James by providing configurable components that can be combined with each other, and other orgainsation components, to create highly sophisticated organisation services. ==== Knowledge ==== Developers have knowledge of the James application development framework and the general needs of business. ==== Responsibilities ==== Developers are responsible for providing Administrators and Deployers with the necessary tools and mechanisms for accessible and intuitive use of James features. ---- === Engineer === ==== Role ==== Engineers provide the core components that make James instances easy to manage and keep them running under heavy load 24/7. ==== Knowledge ==== Engineers have an understanding of the technical issues surrounding software/hardware engineering.. ==== Responsibilities ==== Engineers are responsible for abstracting machine level problems from Developers by creating frameworks to assist them in solving real world problems without the need to account for machine level constructs. ---- === Architect === ==== Role ==== Architects provide the guiding design principles ensuring James is a dynamic, robust, highly efficient server that is setting standards, not just meeting them. ==== Knowledge ==== Architects have knowledge pertaining to philosophically universal concepts and the art of applying of design patterns. ==== Responsibilities ==== Architects are responsible for defining the scope, integration strategies and extensibility mechanisms of the James server. ----
