《Head First Object-Oriented Analysis and Design》的笔记-第88页
- 页码：第88页 2011-02-11 20:43:50
Chapter 2 Give Them What They Want * requirement: it's a specific thing your system has to do to work correctly. specific: a requirement is usually a single thing, and you can test the thing to make sure you've actually fulfilled the requirement system: is the complete app or project you're working on. a requirement is a singular need detailing what a particular product or service should be or do. It is most commonly used in a formal sense in systems engineering or softwar engineering. * use cases: a use case describes what your system does to accomplish a prticular customer goal. a use case is a technique for capturing the potential requirements of a new system or software change. Each use case provides one or more scemarios that convey how the system should interact with the end user or anoter system to achieve a specific goal. one use case, three parts: 1. clear value: every use case must have a clear value to the stsyem. If the use case doesn't help the customer achieve their goal, then the use case isn't of much use. 2. start and stop: every use case must have a definie starting and stopping point. Something must begin the process, and then there must be a contidion that indicates that the process is complete. 3. external initiator: every use case is started off by an external initiator, outside of the ststem. Sometimes that initiator is a person, but it could be anything outside of the system.
[已注销]对本书的所有笔记 · · · · · ·
Chapter 1 Great Software Begins Here * Finally, you'll understand why OOA&D is a fo...
说明 · · · · · ·