Chapter 10造句怎么写

8、These buttons also should not be placed so far from the screen or arranged spatially so that the mapping becomes unclear (see Chapter 10 for a more detailed discussion of mapping issues).

10、Items and tools that are most frequently used (many times a day) should be immediately in reach, as discussed in Chapter 10. Less frequently used items, used perhaps once or twice a day, should be no more than a click or two away.

1、Avoid illogical comparisons . (See Chapter 10 .).

3、International Workshop on Agenda 21 - Chapter 10: Integrated Planning and Management of Land Resources 21

5、Generally speaking, it’s a good idea to put these types of functions deeper into the interface (see Chapter 10 for an explanation).

7、Chapter 10 discusses the importance of taking a risk-based approach toward computerized system compliance and how it adds value to the product and process that is commensurate with cost.

11、After you have a good list of top-level functional and data elements, you can begin to group them into functional units and determine their hierarchy.3 Because these elements facilitate specific tasks, the idea is to group elements to best facilitate the persona’s flow (see Chapter 10) both within a task and between related task

4、As discussed in Chapter 10, inconsiderate products ask lots of annoying questions.

9、There is an exception to the rule of multiple vectors: Dangerous commands (like Erase All, Clear, Abandon Changes, and so on) should not have easy, parallel command vectors. Instead, they need to be protected within menus and dialog boxes (in keeping with our design principle from Chapter 10: Hide the ejector seat levers).

6、Chapter 10 focuses heavily on The Single Responsibility Principle (SRP), a concept from Martin's previous work, Agile Software Development: Principles, Patterns, and Practices.

2、But as we discussed in Chapter 10, people don’t like to be asked questions.