Dataless programming Export

@inproceedings{citeulike:6043047, abstract = {A programmer using existing programming languages typically codes a problem by (1) defining it, then (2) analyzing the processing requirements, and (3) on the basis of these requirements, choosing a data representation, and finally, (4) coding the problem. Almost always, difficulties arise because necessary processing not envisioned in the analysis phase makes the chosen data representation inappropriate because of a lack of space, efficiency, ease of use or some combination of these. The decision is then made to either live with these difficulties or change the data representation. Unfortunately, changing the data representation usually involves making extensive changes to the code already written. Furthermore, there is no assurance that this dilemma will not recur with the new data representation.}, address = {New York, NY, USA}, author = {Balzer, R. M.}, booktitle = {AFIPS '67 (Fall): Proceedings of the November 14-16, 1967, fall joint computer conference}, citeulike-article-id = {6043047}, citeulike-linkout-0 = {http://portal.acm.org/citation.cfm?id=1465683}, citeulike-linkout-1 = {http://dx.doi.org/10.1145/1465611.1465683}, doi = {10.1145/1465611.1465683}, keywords = {historical\_papers}, location = {Anaheim, California}, pages = {535--544}, posted-at = {2009-10-30 13:29:36}, priority = {2}, publisher = {ACM}, title = {Dataless programming}, url = {http://dx.doi.org/10.1145/1465611.1465683}, year = {1967} }

TY - CONF ID - citeulike:6043047 L3 - citeulike-article-id:6043047 N2 - A programmer using existing programming languages typically codes a problem by (1) defining it, then (2) analyzing the processing requirements, and (3) on the basis of these requirements, choosing a data representation, and finally, (4) coding the problem. Almost always, difficulties arise because necessary processing not envisioned in the analysis phase makes the chosen data representation inappropriate because of a lack of space, efficiency, ease of use or some combination of these. The decision is then made to either live with these difficulties or change the data representation. Unfortunately, changing the data representation usually involves making extensive changes to the code already written. Furthermore, there is no assurance that this dilemma will not recur with the new data representation. CY - Anaheim, California AD - New York, NY, USA EP - 544 TI - Dataless programming PB - ACM T2 - AFIPS '67 (Fall): Proceedings of the November 14-16, 1967, fall joint computer conference SP - 535 KW - historical_papers AU - Balzer, RM PY - 1967/// UR - http://dx.doi.org/10.1145/1465611.1465683 ER -