The Development of Drupal 8 and Its Potential Stake Holders

feature-top

The speed of innovation is driven by advances in technology, and the fact that the time needed to develop and deliver new products can be shorten, is also driven by advances in technology. In today’s article a project of choice to develop an application that can be used to develop websites, such as a content management system (CMS), is going to be discussed.

In this case the content management system of choice is Drupal, an open-source content management framework, that is used to manage large websites such as www.nih.gov.

A wide range of web applications can also be developed, using Drupal, which uses a stack of software, which work in the backend of a website, to store and present data to users online. The stack of software includes: the server software, the database software and PHP interpreting software. PHP is the programming language used, to develop Drupal; many other well-known technologies such as Symphony have been used to develop Drupal 8.

A CMS project development, would consist of developing a front end and a back end of the application. The CMS would sit on top of a programming language, which would make the necessary connections between the front end and the backend of the website or applications. The front end of the application, would include the administrator user interface, which is a graphical interface, that administrators can utilize to interact with the application or website. Users would be able to login through the website’s frontend page and be able to create pages for their websites, manage existing ones, and even add new features to their websites or application, using the CMS. Through the administration front end of the CSM users, would be able to control permissions to certain pages of their website, and add meta tags to their website.

The back end of the CMS would consist of the database the webserver and the code base, which is going to be used to make those connections, between the front end and the back end of the CMS.

The Development of Drupal 8

If a company would like to develop a CMS, that company must approach that development as a project, the project would be an IT solutions project, a project life cycle methodology approach would be ideal to complete this project on time, with high quality and meet project expectations; while not going over budget.

The software development life cycle of choice for this project would be the agile method, which uses incremental, iterative work sequences known as sprints, to assist IT teams in responding to the unpredictable obstacles that can manifest when constructing a software.

The development of a CMS, requires developers to have to do some initial planning and understand how to approach this kind of a project. A lot of moving parts are involved in the development of Drupal, and as the project manager of that project, he/she would have to find out about the system’s requirements, decide on which software to use, plan the system portability, and investigate how to make the system easy to modify, to add additional features to the CMS.

Since this CMS would be scalable, code standards must be put in place as well; so that future development is uniformed.

The Stake Holders and the Drupal Community

The Drupal development project is part of a community of developers, who contribute through modules, to this CMS. Therefore, the most important stakeholder on the development of the Drupal CMS is the community because they are the users and they benefit the most with this great technology.

The community of Drupal involves the maintainers of drupal.org, the developers who continue to contribute to Drupal through the development of contributed modules and those users who use Drupal to develop great websites and application for large organizations.

Even the developers who are employed as Drupal developers are stake holders, because they are also part of the reason why Drupal is needed indeed as a CMS, for all types of web applications. The founder of this CMS Dries Buytaert is also a stakeholder because he changed the lives of millions of people across the globe, as well as his own.

The Drupal project is not controlled by any one, a developer can take whichever version of Drupal and customize it according to their needs. However, the  maintainers at Drupal.org do release a new version of Drupal every so often, to maintain this great technology up to date and usable by millions.

 

References:

Codington-Lacerte, C. (2013). Agile software development. Salem Press Encyclopedia. Retrieved from http://ezproxy.umuc.edu/login?url=http://search.ebscohost.com.ezproxy.umuc.edu/login.aspx?direct=true&db=ers&AN=90558239&site=eds-live&scope=site.

Reiling, J.P. (2016, April 7). Considering the Project Definition for the Project Charter. Brighthub PM. Retrieved from: http://www.brighthubpm.com/project-planning/129244-how-to-wow-your-clients-with-the-project-charter/

Font, V.M. (2013). The Project Management Method and the SDLC. Ultimate Guide to the SDLC. Retrieved from: http://ultimatesdlc.com/project-management-method-sdlc

Drupal.org retrieved from https://www.drupal.org/home

https://www.elated.com/articles/cms-in-an-afternoon-php-mysql/

feature-top
feature-top

Add a Comment

Hernando Cadet

Hi every one, I obtained a bachelor's degree in Bioinformatics back in 2006, from Claflin University, after I received my bachelor's degree, I gained full time employment as a software engineer at a Video Relay Service company, maintaining databases and developing software for a new developed device called the VPAD.

I worked at that company for two years, then I became a web developer, and worked for a magazine for three years. After that job, I worked as a Drupal web developer, as a subcontractor for the NIH, for a year and then left the job to go back to school.

Hernando Cadet

Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without

Collaboratively administrate empowered markets via plug-and-play networks. Dynamically procrastinate B2C users after installed base benefits. Dramatically visualize customer directed convergence without revolutionary ROI.