SE735 - Data and Document Representation & Processing
This assignment is related to your project.
1. Analyze the domain of your project and identify the important actors in it. These actors can be human actors or computational ones (i.e., services or information resources used by other actors). You should have at least four actors, and you might have more than that.
2. Model the interactions among the actors as transactions.
3. Organize sets of related transactions into collaborations when they have meaningful and necessary overlap with each other. Determine how many collaborations are required to represent your model. Note: you need at least two or there isn't any point, and if you have nearly as many collaborations as transactions then the collaboration level isn't providing an additional abstraction level.
4. Represent the specifications for each transaction using transaction worksheets as found in section 9.4 of the Document Engineering text.
Write a paragraph or two that explains the purpose and scope of your process model.
Create a diagram that depicts the relationships between the actors that are stated or implied in the previous section. You can use either an activity diagram (see Figure 9-15), or a sequence diagram (Figure 9-6a or 9-14). (You need to label both the transactions and the collaborations in your diagram)..
You can use a UML tool or even Visio, SmartDraw, Powerpoint, or any other tool you like because it's the model that matters, not the notation (but any tool that understands process modeling notations will make it go a lot faster). Two free UML tools are ArgoUML and StarUML.
Your model should include exception or failure states where the transactions do not achieve the desired outcome(s). These are easier to depict in the traditional Activity Diagram but can be represented as annotations on Sequence Diagrams or Blueprints.
For each transaction in your model, identify its transaction pattern (section 9.6) and annotate your diagram from Activity 2 with this information.
Create Transaction Worksheets (Figure 9-6b) for at least three of the transaction in your model from at least two different collaborations. You don't need to turn in worksheets for every transaction in your model because that would encourage you to create models with a minimal number of transactions.