Notice: Undefined index: action in /home2/armanpow/programmingcodex.com-old/code/public/blog/wp-content/themes/hello-elementor/functions.php on line 2
User Driven Programming-Modeling, and Wider Participation - Programming Codex

User Driven Programming-Modeling, and Wider Participation

User Driven Programming-Modeling, and Wider Participation

A user-driven approach to visualization, modeling, and programming can improve software and ease its creation and maintenance. Translation then becomes possible from the user’s representation to a software representation, and from design to implementation.

For User Driven Programming, ‘user’ can mean the individual and/or organization. The technique can be applied soonest to modeling/programming problems that require calculation. E.g. scientific, engineering, and business problems. The basis of the technique is enabling the information to be represented in a structured format e.g. XML (eXtensible Markup Language), RDF (Resource Description Framework), RSS (this can stand for 3 different things – en.wikipedia.org/wiki/RSS_(file_format), and OWL (Web Ontology Language). Visualization and interaction with the information can be enabled in a standardized way because the information is structured. This enables diagrammatic editing for modeling/programming. Careful structuring of the information and models/programs simplifies the modeling/programming process. A translation process from abstract/domain models to code can then be provided using recursive techniques.

As the structure and design and editing process for these models/programs can be standardized this enables a common meta-programming based methodology. Visualization of this methodology to allow User-Driven participation could enable wider participation than is currently possible for open source development, which is limited to more technical users. Visualization at different levels of abstraction from domain to software could enable end-users, designers, and software developers to communicate in a semi-structured way to establish procedures for ensuring software is produced that end-users want to use.

Source by Peter Hale

Leave a Reply

Your email address will not be published.