WCM Web Content Management

1
WCM Web Content Management

• John Stamm
• Greg Salter
• Jason Brisch

2
Overview

• Project Summary
• Input Methods
• Database Systems
• Server Technologies
• Dynamic Content Generation Methods

3
Project Summary

• Stakeholders
• Kent Peterson
• Department Heads
• Current System
• Email Messages
• Other Direct Modifications

4
Problem with Current System

• Concurrency
• Up to date information
• Consistency
• Inconsistent information
• Inconsistent formatting
• Timeliness
• E-mails take time
• Messages get lost
• Kent takes care of videos

5
Content Management System

• Features
• Allows multiple updates
• Revert to previous versions
• Updates can be confirmed
• Constraints
• Little HTML experience by end users
• No knowledge of system
• Security

6
Input Technologies

• Constraints
• Users prior knowledge
• Compatibility
• Ease of programming
• Price

7
Technologies

• Plain Text
• Microsoft Word
• Microsoft Access
• Web Forms

8
Database Systems

• Constraints
• Fits in existing MSOE framework
• Price
• Team familiarity
• Ease of programming

9
Technologies

• Oracle
• Microsoft Access
• SQL Server
• MySQL
• PostgreSQL

10
Server Technologies

• Constraints
• Fits in existing MSOE framework
• Price
• Reliability
• Flexibility
• Extensibility
• Security

11
Technologies

• IIS
• Tomcat
• Apache

12
Dynamic Content Generation

• Constraints
• Fits within MSOE framework
• Price
• Robustness
• Team familiarity
• Future maintainability

13
Technologies

• JSP
• ASP
• PHP

14
Conclusion

• Chosen technologies
• Web forms
• PostgreSQL
• Apache
• PHP
• Implementation plans
• Develop database
• Output
• Edit/Admin interface