User Driven Programming-Modeling, and Wider Participation

Keli W. Rodriguez

A user-driven approach to visualisation, modelling, and programming can improve software and ease it’s creation and maintenance. Translation then becomes posible from the user’s representation to a software representation, and from design to implementation.

For User Driven Programming, ‘user’ can mean individual and/or organisation. The technique can be applied soonest to modelling/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 (Resourece Description Framework), RSS (this can stand for 3 different things – en.wikipedia.org/wiki/RSS_(file_format), and OWL (Web Ontology Language). Visualisation and interaction with the information can be enabled in a standardised way because the information is structured. This enables diagrammatic editing for modelling/programming. Careful structuring of the information and models/programs simplifies the modelling/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 standardised this enables a common meta-programming based methodology. Visualisation 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. Visualisation at different levels of abstraction from domain to software could enable end-users, designers, and software developers to communicate in a semi-structured way in order to establish procedures for ensuring software is produced that end-users want to use.

Next Post

Challenges in Requirements Elicitation

What is Requirements Elicitation? Requirements elicitation is the most communication intensive part of the requirements process. During requirements elicitation, the business analyst must interact with the stakeholders in many different types of elicitation sessions to draw out the user requirements for a project. Why Requirements Elicitation? Without complete, correct and […]

You May Like