Chapter 2. Identifying System Boundaries
By now you have a high-level overview of the project and an idea of the risks you are facing. Let’s define a couple of terms we have been using before going on. The system is whatever you are planning to create. It could be software, hardware, or processes. The project encompasses all the things you do to build a system. So it will include things such as planning, scheduling, and documentation.
The next step in our process is to clearly identify the boundaries of the system. This means finding out what things are inside your system (you have to worry about creating them) and what are outside your system (you don’t have to create them, but you have to worry about interfacing with them). You should also ...
Get Applying Use Cases: A Practical Guide, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
