Skip to content
#Design

Software development (Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design)

#Design #SoftwareDevelopment #Architecture #Processes

This book was written by Larry Constantine and Lucy Lockwood. 1999 It was devoted to the creation of practical software that would be convenient to use and it corresponded to the goals of the user. In Russian, the book came out in 2004 under the title "Software Development", which led to the 2005 I bought it for myself to learn how to write software better. But then this book didn't resonate with me -- because I didn't really think about the product approach, the user experience, and I hadn't yet cracked the topic of human-centric design. (It's a term from Don Norman's "Design of Common Things," to which I wrote a brief summary. sammari). Since the book was published, it has been 25 Some things in it are no longer relevant, and some remained true and now, for example, you can recall the rules of practicality of the author:

  1. The system should be so practical that a user who has knowledge of the subject area, but has never worked with the system before, without the help of instructions and manuals, could immediately start using it.
  2. The system should not in any way interfere with the effective work of experienced users who have worked with it for a long time.
  3. The system should contribute to the continuous improvement of knowledge, skills and adapt to the changing user experience.
  4. The system should contribute to a simpler, faster or more exciting solution of problems facing users, provide new opportunities.
  5. The system must meet existing realities and the current environment of the operational context within which it will be deployed and applied.

Interestingly, in the comments to the book on Amazon, people note that the authors in their book do not quite follow their principles of use-centered design, since the book is too verbose, and is filled with stories and stories that interfere with the structure of the author’s thinking:)

P.S. It was interesting for me to look through the book now, after all these years, and compare my current opinion of the book and the past, and also to assess how much I have come to understand the topic of software design:) But if you want to read something on this topic now, it is better to read Don Norman's book - it was recently reprinted and is generally a classic:)

#Design #SoftwareDevelopment #Architecture #Processes