A anticipation which influences my investigating into End-User Programming and Modelling is that organizations should not use copyrighted or obstructed standards for their facts. Systems should be planned with the assumption that information, which represents the foremost group asset, may yet requirement to be migrated to another software system piece of equipment or state of affairs. Open use of reports was the high status for the DATUM hang over. This project is explained in 'DATUM Project: Cost Estimating Environment for Support of Aerospace Design Decision Making' (Scanlan et al, 2006). Therefore a obligation of this investigation is that open normal semantic languages are used to signify information, to be used some as input and production of the models. These languages are supported on eXtensible Markup Language (XML). These very unequivocal usual languages can be utilized for underdeveloped the system secret message of models.
It is proposed that code and hearsay described by the software, be detached but portrayed in the aforesaid overt normal searchable way. Software and the info it manipulates are a moment ago content that has different uses, in that is no intention why code essential be portrayed otherwise from some other info. So XML can be used both as the data signaling and yield by the application, and for the account of the worthy itself. The model can read or keep up a correspondence subject matter it represents, and the facts can publication from or write out to the epitome. This formula makes 'meta-programming' attainable.
Meta planning is composition of programs by separate programs. The aim of this is to make available a cascading set of layers that repeat a comparatively soft to use optical mental object of a conundrum to be modelled, into opinion that can be run by modern day compilers and interpreters. This is to label it easier for computing machine literary non-programmers to order mission to a computer, without erudition and authorship secret message in computing machine languages. To do this, any branch of software package or news essential be able to read the codification or the reports pictured in any else. Code and numbers are merely separate out as a situation of shape assessment to aid human comprehension, they can be painted in the self way victimisation the self kinds of open ensign languages. The methods used for this depiction and rendering are being researched.
One post:
End User Programming and Engineering Modelling
Many overlarge companies have outsourced the paperwork and advocate of their IT systems to ordinal parties. Very dictatorial direction processes and procedures for the attainment and finishing of new systems have been introduced. A side-effect of this line of reasoning is a penchant for personnel to put together extended use of spreadsheets and large scheduling languages for hearsay storage, analysis, and manipulation (Scanlan et al, 2006). These applications root themselves as a legitimate piece of the commercial processes of the system dislike the fundamentally uncontrolled temperament of their steps forward. This is a problematic tendency as these applications are often undocumented, from time to time to the full proved or validated, and are create by society who frequently have wee or no form-only breaking in in well behaved systems fostering activity. An secondary feelings of User Driven Modelling is required, because wide-ranging spreadsheets are unmaintainable in the overnight run.
By their nature, prodigious spreadsheets are gruelling for a ordinal knees-up to dig as their intrinsic malleability for editing allows users to generate a tangled web of cell references which are lengthy to method of accounting. Panko (2000), Paine, (2003), and Scanlan et al (2006) examine this eccentricity. Worse still, nearby is a predisposition for the database critic to misguidedly tripinnatifid the danger by disbursal a generous magnitude of stab into hiding the fact trailing an fancy and visually charismatic 'front end'. Should the journalist of such as an contention confer on the organization, it is usually discarded as colleagues are complaining to maestro its obscurity and oft refuse to take relation of it, as they are active next to their main donkey work. Paine states that spreadsheets have nigh no features for edifice applications out of environment that can be developed and tried individually. Panko (2000) suggests that “Given assemblage from new area audits, peak heroic spreadsheets belike incorporate of import errors.” The furthermost recent accounting he cites found errors in at least 86% of spreadsheets audited. In 1997 Panko reportable that 90% of the spreadsheets audited in a examination carried out by Coopers and Lybrand were found to have errors. In 'Automatic Generation and Maintenance of Correct Spreadsheets?' Erwig et al (2006) think of a integer of 90% from Rajalingham et al (2001) 'Classification of Spreadsheet Errors'. 'Given the millions of spreadsheets in use, this leaves the worlds of business organisation and fund awfully susceptible to planning mistakes' (Scanlan et al, 2006). The studies by Paine, and Panko confirm that the probability of any specified computer programme cell containing an lapse are somewhere linking 0.3 and 3%, so that a database of solitary 100 cells has give or take a few a 30% karma of having one fault or more. Aragones et al (2006) give - 'Desktop computer program users are severely fictive in their adaptations, but
distributed spreadsheets have the nuisance of distributed, uneven inputs and distributed
results. There is no smooth way to aggregate the communist wisdom of person experience'.
One copy:
References
Aragones, A., Bruno, J., Crapo, A., Garbiras M., 2006. An Ontology-Based Architecture for Adaptive Work-Centered User Interface Technology. Jena User Conference, 2006, Bristol, UK [http://jena.hpl.hp.com/juc2006/proceedings/crapo/paper.pdf].
Erwig, M., Abraham, R., Cooperstein, I., Kollmansberger S., 2006. Automatic Generation and Maintenance of Correct Spreadsheets?. Proceedings of the 27th mixed convention on Software engineering, St. Louis, MO, USA pp 136-145
Paine, J., 2003. Spreadsheet Structure Discovery with Logic Programming, Proceedings of European Spreadsheet Risks Interest Group EuSpRIG Greenwich, England.
Panko, R. P., 2000. Spreadsheet Errors: What We Know, What We Think We Can Do. Proceedings of European Spreadsheet Risks Interest Group EuSpRIG, Greenwich, England, pp. 7–17.
Scanlan, J., Rao, A., Bru, C., Hale, P., Marsh, R., 2006. DATUM Project: Cost Estimating Environment for Support of Aerospace Design Decision Making. Journal of Aircraft, 43(4).
留言列表
