By Bonnie A. Nardi
A Small topic of Programming asks why it's been so tough for finish clients to command programming energy and explores the issues of finish user-driven software improvement that needs to be solved to have the funds for finish clients higher computational power.Drawing on empirical learn on present finish consumer platforms, A Small subject of Programming analyzes cognitive, social, and technical problems with finish person programming. specifically, it examines the significance of task-specific programming languages, visible software frameworks, and collaborative paintings practices for finish person computing, with the objective of assisting designers and programmers comprehend and higher fulfill the wishes of finish clients who wish the aptitude to create, customise, and expand their functions software.The principles within the e-book are in keeping with the author's study on winning finish person programming structures - spreadsheets and CAD structures - in addition to different empirical learn. Nardi concentrates on wide concerns in finish consumer programming, specifically finish clients' strengths and difficulties, introducing instruments and strategies as they're with regards to higher-level consumer issues.Bonnie A. Nardi is a Member of the Technical employees at Hewlett Packard Laboratories.
Read Online or Download A small matter of programming: perspectives on end-user computing PDF
Best programming languages books
The TCP/IP protocol suite has develop into the de facto average for desktop communications in latest networked global. the ever present implementation of a particular networking regular has ended in an important dependence at the purposes enabled by way of it. at the present time, we use the TCP/IP protocols and the web not just for leisure and knowledge, yet to behavior our company by means of appearing transactions, trading items, and supplying providers to clients.
Sams train your self COBOL in 24 Hours teaches the fundamentals of COBOL programming in 24 step by step classes. each one lesson builds at the past one offering an outstanding starting place in COBOL programming recommendations and methods. Coupled with the resource code and the compiler to be had from Fujitsu, this hands-on advisor is the best, quickest approach to commence developing ordinary COBOL compliant code.
CMMI® for improvement (CMMI-DEV) describes top practices for the advance and upkeep of goods and companies throughout their lifecycle. via integrating crucial our bodies of information, CMMI-DEV offers a unmarried, complete framework for corporations to evaluate their improvement and upkeep methods and increase functionality.
- Icon Programming Language, 3rd Edition
- Prolog programming in depth
- Semantics of Programming Languages and Model Theory
- Functional Programming in Scala
Extra resources for A small matter of programming: perspectives on end-user computing
However, they fall short in capturing the ultimate objective of requirements engineering. No measurement has been proposed to assess whether the specified system will be successful. 9 with the additional dimension of requirements engineering outcome. In the survey we thus ask the respondents whether the specified product met the goals the product was conceived for. 3 Industry Survey We investigated the use of requirements engineering techniques and how much they contributed to requirements engineering success with an online survey .
Analyzing power and influence of stakeholders and planning how to interact with them. Ranking the requirements to obtain an order of how they shall be addressed by the project work . Aligning requirements with company strategy, for example through explicit traceability . Analyzing and selecting alternative features or ways of solving a problem . Structured, possibly tool-supported approach to identification of options for agreement and selection of the appropriate option . baselined and used to manage the development project and the release of the developed product.
Functional requirements dominated. Concepts commonly used for formal reasoning, such as agents, goals, and formal properties, were rare. For specifying the requirements, natural language dominated as the notation. Natural language was often complemented with UML diagrams. The use of other diagram types, user screens, and informal drawings varied. Formal-logic and goal-oriented languages like i* or KAOS were almost never used. The frequency of notations that match requirements analysis techniques was inconsistent with requirements analysis practice.