ITS+Requirements

toc

?What C3HUU ITS Requirements?
? What are the IT Services requirements of the people who are our key C3HUU "stakeholders" ? A key core principle to successfully apply IT Services is to insure that the stakeholders in the service have their needs, their "requirements" met. The best way to insure that is true is to constantly work to capture them. This wiki page is a part of that process, perhaps a way to gather in plain language what is requested on the C3H Change Request page.

So here is a list of key stakeholders and either a list of their current perceived requirements or a reference to another online web page with more details:
 * ~ Stakeholder ||~ Key Requirements ||~ Last Updated ||
 * Minister || See Minister ITS Requirements for details || 2008-08-15 ||
 * Director of RE || * PC upgrade, currently on Backup PC due to XP system problems || 2008-08-15 ||
 * Office Manager || * Better integrated calendar system perhaps a Church Management System (ChMS). See Church Calendar Search || 2008-08-15 ||
 * Membership Coordinator || * More usable Church Management System for tracking volunteers and groups || 2008-08-15 ||
 * Financial Assistant || * Better integrated, or at least cross-functional ChMS and Finance system (Quickbooks) || 2008-08-15 ||
 * Committee or Standing Group chair/lead || * Option to lead online group (Yahoogroup or Googlegroup) [COMPLETE!]
 * Option to "own" Wiki web page for group [COMPLETE!]
 * Sturdy Church owned PC display projector || 2008-11-15 ||
 * Member || * Web "portal" to allow tracking of contributions, making donations || 2008-08-15 ||

Security Requirements
Members exchange information with C3HUU staff and special committees and expect that information to remain confidential. C3HUU staff and ITS volunteers work to insure that there is secure storage of information collected.

One area that has received increased scrutiny is PC access. At present the PCs are administered independently, which is an archaic model and prone to problems. The ITS group proposes that there be enhanced security by adding:


 * 1) Windows Domain - use the Domain Controller function of the QNAP TS409 NAS to setup a Windows Domain for all staff and those non-staff with legitimate need for access to C3HUU PC resources
 * 2) Secure access with an additional layer, enforcing use of non-trivial passwords. To do so, research alternative technologies for keeping passwords for staff:
 * biometric security, fingerprint readers are the most common
 * Eikon Privacy manager: mouse like USB extension or USB "key". Reported to be best of breed, good software, updates cost $15, but worth it
 * Transcend JetFlash 220 - OK, portable USB key, software is finicky to install. Turns workstation into single user workstation as it disables the quick switch Windows software used to allow multiple sessions.
 * Lenovo ThinkFinger: OK, but just went out of distribution, though still supported
 * Roboforms password vault: excellent vault function, not integrated with above biometric devices