In chapter ten, we looked at data and how to identify classes that were needed from Use Cases.

In Chapter 11, we look at Information Exchange through Events. An Event is not the data that has been changed, but rather that information has been exchanged between elements.

An Event occurs when information that is exchanged: This can be in the form of Error or Success Messages, Data Entered by a user, Data between two systems, etc.

Once the event has been identified – you need to link the events to the appropriate classes.

Identifying Events with Use Cases was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

Software Process Structure

ByWalter Wimberly

Every software team will experience some sort of problem as they move through the system. These may be technical issues, issues with working with other departments, etc. A Process Pattern describes a process related problem that is encountered during software engineering work, identifies the environment in which the problem occurs, and suggests one or more…

Requirements Gathering

ByWalter Wimberly

The book calls this Eliciting Requirements. They should be done in a collaborative environment. Generally either face to face meetings and/or virtual meetings. Being done in real time allows for faster feedback than over an email/text/phone calls, etc. The meetings should include developers as well as other stakeholders. Rules and an Agenda for the meeting…