Me Myself and I

Identifying the appropriate and necessary requirements that build up the functionalities within the user dashboard was a truly interactive and based on a contextual inquiry session that mimic-ed the system to be developed. Though the user dashboard wasn't considered a necessity at the beginning of the requirements gathering phase, it proved to aid in acting as an intermediary wall between the communication channel of a user and the Event Planning System Staff from the highest to the lowest hierarchy. A registered user is the beneficiary of such a feature. The dashboard will be instantly created for a registered user as soon as hes/ her account is created. A login validation function will ensure the integrity of the access to that particular user's dashboard. The idea to establish this connectivity resulted as the requirement, to keep the client to the website explore options while navigating within the website itself and not having the need to a...

For my 3rd year 1st semester at SLIIT, I've been allocated the task of developing an Event Planner for a client according to their requirements. Me and my team mates, have been gathering requirements from the client for 7 days and we've finalized the technological aspects of the system and started implementing the Interfaces. Language: PHP Framework : CodeIgniter Architecture : MVC Database : MySQL IDE : JetBrains PhpStorm CodeIgniter was chosen over Laravel as a result of its desirable feature of having a very small footprint. Also CodeIgniter's set-up and installation procedures seemed to be facile in comparison to that of Laravel's. CodeIgniter also proved to  effortlessly  induce a faster learning curve than that of other frameworks. But, this is merely my personal opinion. Though there are contradictions in the system development world regarding these two, such as, CodeIgniter being outdated and not using the CLI, considering the expendable t...