Error Handling in an Activity Diagram

Error Handling in an Activity Diagram

CIS 510

Advanced System Analysis and Design

Error Handling in an Activity Diagram


In my paper, I will be writing about the two added error-handling pathways. I will also be including what is in the diagram in the book figure 2-15. There will be many reasoning behind why it is essential to check for errors along with other possible errors that may occur. And I will end my paper with the diagram of the two error-handling pathways, the original picture of the error-handling pathways, and I will be adding figure 2-16 at the end of my paper to show the difference between the two graphs. So in all, there will be three diagrams included in my article.


In most of the diagrams, you will see processes that are mainly for businesses in which it will show you the users’ activities. Diagrams are mostly for the visual part of it because by not having it many businesses may not get the full understanding of the user’s activities. Inspections in businesses must happen to fix any errors that are lingering there or add things that they feel as though should be in there. The meaning of error-handling is anticipation, detection, resolution of programming, application, and communication errors. (Margaret Rouse, 2007)

Overview Of The Checked Errors

In the activity diagram figure 2-15 shows the process in order as it happens. This process starts as the customer/user completes their order at checkout so their order can start its operation. The graph shows the way things go once the customer checks out and the business get the order; which goes as follows: the order, checking inventory to see if it is in stock, sending the request to the warehouse and finally the shipper ships out the request to the customer/user. Sometimes diagrams can be complicated for the most part if it is someone who has no idea what it is. So by simplifying the chart can make it easier on both parts. Other times the error-handling pathway can overlook things like if something a customer/user wanted is in stock, but the diagram overlooked it saying it’s not there for the order. In the other picture in the book figure 2-16, is slightly different from number 2-15. Figure 2-16 is for when a user orders something that has to be manufactured explicitly to whatever the customer wants.

Checking Errors Are Important

We have to check for errors in any diagram because that is the only way we will know if anything is wrong or missing. We also should make sure that any of the mistakes that are present will not cause any issues. Another reason is that checking for mistakes makes it easier to maintain. It also helps with adding to it. Sometimes errors will not et the customer or the company processing the order to move forward because of a mistake. And other times if an error had occurred then it will let the customer or the company to continue, which can also cause a problem. By allowing the order to go through and the company doesn’t know about it, the error will only remain that way, and won’t get fixed.

Other Possible Errors

Having other possible errors means more issues that can evolve if you don’t catch the mistake before it happens. Once a customer/user finishes their order, and it gets sent out to the inventory subsystem it has to find where the product is at one of there stores or warehouse. And if it doesn’t see the merchandise then let’s say that the system doesn’t do anything after that. Then that is an issue because the customer is/would be expecting that product. Another problem is updating the customer on the product(s) that they ordered. If they do not know anything about their order and they are waiting for something to pick-up or being delivered, then they never know when it is coming, and that also can arise in having the products shipped out.

Error-Handling Pathways

The diagram shows the process in which the order is actuality fulfilled in RMO CSMS. Processing begins when the customer has completed the order checkout process. When looking at the diagram, you will able to see the information between the order subsystem and the inventory subsystem. I will be adding two things in the warehouse part of the description, which will primarily be making sure the address is correct before the order gets sent out and if an item(s) are in the warehouse.

Figure 2-15 Two way Error-Handling Pathway

Figure 2-15 Error-Handling Pathway

Figure 2-16 Activity Diagram Showing Current Paths


(2012). Systems Analysis and Design in a Changing World, 6th Edition. [Strayer University Bookshelf]. Retrieved from

 submission confirmation number is 81706891-81cd-4b77-aa17-fdb5c6f8d846

Place an Order

Plagiarism Free!

Scroll to Top