CMS-K and K-Screens

In lights of the software engineering course, we had to develop a content management system for one of our customers at CISCPA. The system is being used to manage the monitor dynamic contents across the whole building and works with various API's to deliver bus and mensa plans for the current day.

Setting up the webserver

1. Install MAMP as webserver (http://downloads4.mamp.info/MAMP-PRO-WINDOWS/releases/3.3.1/MAMP_MAMP_PRO_3.3.1.exe)
2. Set python environment path in your system ('C:\MAMP\bin\python\bin' if using MAMPs python)
3. Download pip (https://bootstrap.pypa.io/get-pip.py) and install it (python get-pip.py) (already installed if you're using Python 2 >=2.7.9 or Python 3 >=3.4)
4. Go to '\python\Scripts' and run 'pip install beautifulsoup4 python_dateutil urllib flask'
5. Install nodeJS (https://nodejs.org/dist/v6.11.1/node-v6.11.1-x64.msi)
6. Install grunt-cli (npm install -g grunt-cli)
7. Type "npm install" to download the dependencies
8. Type "grunt run" to trigger the build process
9. Set the newly created www-folder as root directory for your webserver
10. Set the WSGIPythonPath in the httpd.conf of your server to ".../www/php"
11. Enter localhost on Google Chrome

Remarks: nodeJS is only needed to create the www-folder. Once built you only need that one to upload to your Apache server.

Technology Stack

• [jQuery]
• [Bootstrap]
• [Grunt]
• [PHP]
• [MySQL]
• [Python]

Timeline

Time	Date	Implementation	Important Deliverables
Iteration 2, week 1	9 June	- Refined User Interface (template) - Setting up the Database
week 2	16 June	- Selecting/Deleting resources from Database
week 3	23 June	- Integrating all monitors into our system such that we can change their screening
week 4	30 June	- Implemented the functionality to change monitors during configuration page - Filter monitor according to their Location	- GUI Paper prototypes for all use cases including exceptional scenarios - UML Class and Sequence diagramms for all use cases - A working prototype implementing most of the must-have requirements
Iteration 3, week 1	7 July	- Implementing Timer Functionality - Log-in screen
week 2	14 July	- Plug & Play
week 3	21 July	- Implemented Labels - Debugging
week 4	28 July	- Debugging - Release	- Final Working Prototype presented to Client - Final every document - Implementation of all must-haves and (if time permits) may-haves

Authors

• Jonas Mohr - Completed work
• Esha chatterjee - Completed work
• Ba Thinh Tran - Completed work
• Marc Schubhan - Completed work

See also the list of contributors who participated in this project.