http://www.steptwo.com.au/papers/ext_implementingcms/index.html Beyond The Idea Thu, 09 Feb 2012 09:46:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.steptwo.com.au/papers/ext_implementingcms/index.html/comment-page-1#comment-1212 bradley shoebottom Tue, 08 Dec 2009 15:19:01 +0000 http://www.steptwo.com.au/?p=460#comment-1212 James I was writing our internal process for implementing a CMS and found tha tthis process and your deploying a CMS to mostly focus on procinples as opposed to actual "tasks". I developed this tentative list that might prove useful. It follows along the lines a typical software implementaiton: 1. Build hardware infrastructure 2. Instantiate CMS software 3. Obtain CMS software training for key users (administrator, power user) 4. Configure the software a. Security model b. Workflow c. Reporting d. Style sheets e. DTDs f. Folder structure g. Metadata Schema h. Versioning 5. Test the implementation for technical performance and scalability 6. Revise software configuration 7. Conduct usability test of key interfaces 8. Revise software interfaces James
I was writing our internal process for implementing a CMS and found tha tthis process and your deploying a CMS to mostly focus on procinples as opposed to actual “tasks”. I developed this tentative list that might prove useful. It follows along the lines a typical software implementaiton:
1. Build hardware infrastructure
2. Instantiate CMS software
3. Obtain CMS software training for key users (administrator, power user)
4. Configure the software
a. Security model
b. Workflow
c. Reporting
d. Style sheets
e. DTDs
f. Folder structure
g. Metadata Schema
h. Versioning
5. Test the implementation for technical performance and scalability
6. Revise software configuration
7. Conduct usability test of key interfaces
8. Revise software interfaces

]]>