Ariel M. Vasquez
November 24, 2014
CIS331
System Modeling Theory
Professor Randy Arvay

Software System Architecture For this case the question is asked which system would be best to implement for this case. There are several different types of cases to chose from. They all with their own particular benefits and negatives at the same time The one that fits this needs in particular would be the event driven system. What is an event driven architecture system? An event driven architecture, or EDA for short, is a pattern that focuses on promoting production, detection, and consumption. Most of its works occur during an event. In the medical field, which this case revolves around, have thing change a lot during the course of not only a day even within every hour this change. Whether it's from a patient's medical records, stock of inventory, medicines provided to a patient, and even when a patient enters and exits the hospital. With a system like EDA thing will only occur when things change and this pattern seems to be able to handle those changes better than the others. The following image will show basically how this type of system will work.

A system that integrates EDA may also provide a higher level of service to help with the implementation of EDA. Things like security, reliable messaging, content based routing, and mapping and transformation. The security that this provides is message encryption, authentication, and access control. With the messaging this provides it will ensure that all messages will be delivered once and only once to all subscribers. An EDA will provide you with an integrated broker suite, IBS, that will route a published even to another topic. Last but not least an EDA will also provided you with mapping and transformation. With the help of an IBA you can transform incoming messages into an alternate format based on the receivers application. With EDA there many benefits like the following: * Cuts down the elapsed time of process by working with individual events rather than batches * Subscribers don't need to be available to continue the process * Publish/Subscribe messaging where an event can impact many subscribers * Supports asynchronous operation through event messaging Though with all these benefits to this system there is one drawback. Effective monitoring must be in place to track queue depth, exceptions, and other possible indicators of problems. The traceability of an event through a dynamic multi-path event network can be difficult making problem debugging more difficult in some cases.