The law of Construction reading notes Tenth & 11 chapters

The Tenth & 11 chapter of the law of construction mainly describes the methods and practical experience on the requirement analysis in the pre-design of software, which is divided into "typical users and scenes" and "Software design and implementation". In the tenth chapter, most of the content is the same as that taught in class. For example, the user's classification (typical user can include the following content:

1. Name (the more natural the better)

2. Age (different age and income users have different needs)

3. Income

4. The proportion and importance of the represented user in the market (a large proportion is not equal to
High importance, such as the proportion of users who pay less, but the impact of a large, so heavier
To

5. Typical scenarios for using this software

6. Environment in which the software/service is used (in the Office/home/sofa/bed/Public
Total car/subway ... ）

7. Living/Working Conditions

8. Knowledge levels and competencies (education level, familiarity with computers, the Internet
Dimension

9. Motivation, purpose and difficulty of the user (difficulty = problem to be solved)

10. User preferences)

These 10 points have divided the user's type very detailed, we can also be targeted to write software to meet the needs of different users of the problem.

Then is the user scene analysis, in the absence of lectures or read this book before it I was completely unexpected, then there is only a simple idea in the mind-the function of the realization of No, which has a lot of trouble! Really is the same as the book said the kind of person, but after reading the book found to be true, because our software is to sell to others, not just to achieve some of the so-called functions. So the user scene analysis is very necessary, so that one can detect the user in the process of the problems encountered in order to solve, and in any environment or the user (layman) any operation must make the software look normal, that is, the legendary transposition thinking, Put yourself on the spot a user who doesn't know much about the computer to do the software.

The next thing is to write a document, "What?!" Programmers also need to write documents? You're not kidding me! Yes, not only to write but also to write the very detailed, like, like a TV series as detailed, but do not need to write so vivid "instead of the simpler the more easy to understand the better, but not too dull, so no one would like to read well!" See here, I once again felt a great sense of pressure and glory, mom ah original programmer or mathematical literature all-in-all Ah, all-round talent Ah!!

The 11th chapter is mainly about "software design and realization", which is divided into two parts, the first "design method" and the second "How to Realize"

As for the design method, I will learn a kind of "graphic modeling" that is drawing use case diagram and so on, as well as "express data Flow" and other methods, or we need to use time and energy to learn. As to how to achieve

The law of Construction reading notes Tenth & 11 chapters