If it's not obvious why an entity belongs on the diagram, make a note about the interaction between the system and the entity. If it doesn't have a name yet, just label the circle as "System." Then list each of the external entities around your system and draw a line between the entity and the system. If your system has a name, use it to label the circle. a brief note about the interaction between each thing and the system (#3 is optional).īecause it's an overview and lacks much detail, this diagram is an easy way to start building momentum in your requirements gathering process.Ĭreate a context diagram by drawing a circle in the center of the page.the things that need to interact with the system (use case experts call these things external entities), and.the system you're going to be gathering requirements for,.A context diagram is a high-level, informal view of three things: People new to use cases are often unsure of where to start gathering requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |