There are two discussions here that need to be responded to thoroughly. Responses must be on APA format 150+words 1-2 legitimate verifiable sources per response.

CIS555 discussion 1 post responses.
Respond to the colleagues posts regarding:
“Representing Operation Models” Please respond to the following:
¢ From the first e-Activity, suppose you were asked to create an UML use case for a system-as-is given the complete requirements. Propose three best practices that you would suggest for the creating of a UML use case from the complete requirements (i.e. selecting actors and operations).
¢ Evaluate operationalization diagrams and UML use case diagrams in relation to operational models. Select the diagram that you believe represents operation models clearer. Defend your position.

MHs post states the following:
From the first e-Activity, suppose you were asked to create an UML use case for a system-as-is given the complete requirements. Propose three best practices that you would suggest for the creating of a UML use case from the complete requirements (i.e. selecting actors and operations).
1. Carefully read the complete requirements.  While reading the requirements, keep a list of all the (a) all actors mentioned, (b) the essential functionality that interact with actors in the environment, (c) a brief “ one or two sentence “ description of the use case, and (d) for each use case, a list of the actors that participate in the use case. This will make creating and verifying the use case diagrams easier.
2. If there is a large number of use cases, create a logical grouping of use case, for example, by sub-system.
3. When preparing the use case diagram, give each actor a name that corresponds to the agent defined in the specification. 
4. When preparing the use case diagram, create succinct use case names that are drawn from the domain.
5. Finally, verify that use case diagrams are complete by referencing the list created during step one (above).  Are all of the use cases shown in the diagram? 

Does the diagram show all of the associations between the actors and the uses cases that they participate in?

Evaluate operationalization diagrams and UML use case diagrams in relation to operational models. Select the diagram that you believe represents operation models clearer. Defend your position.
Operationalization diagrams represent operation models more clearly than use case diagrams.  An operationalization diagram shows system operations, their input-output objects and the goals they operationalize (Lamsweerde, 2009, p. 441).  Use case diagrams, on the other hand, are far more general and provide an overview of a systems operations (Lamsweerde, 2009, p. 436).

References
Lamsweerde, A. van. (2009). Requirements engineering: From system goals to UML models to software specifications. West Sussex, England: John Wiley.

CIS555 discussion 2 post responses.
Respond to the colleagues posts regarding:
“Instance Behaviors” Please respond to the following:
¢ From the second e-Activity, determine whether you believe that the behavior of a system can or cannot be captured without using UML sequence diagrams. Provide rationale.
¢ Determine whether or not you believe that every system being modeled must include state diagrams in order to understand state transitions. Support your position.

MHs post states the following:
From the second e-Activity, determine whether you believe that the behavior of a system can or cannot be captured without using UML sequence diagrams. Provide rationale.

UML sequence diagrams are particularly helpful for illustrating system behavior for a single scenario (Lamsweerde, 2009; Ambler, 2005).  While it is possible to capture system behavior without using UML sequence diagrams, it may be necessary to prepare one or more alternative diagrams, such as a state machine diagram or activity diagram, to replace sequence diagrams.
Determine whether or not you believe that every system being modeled must include state diagrams in order to understand state transitions. Support your position.

While helpful, I do not believe that every system being modeled must include state diagrams to understand state transitions.  As mentioned above, there are other diagram types that are capable of illustrating an entitys state changes within a system.  The amount and type of documentation needed to model the systems behavior should be selected based on the complexity of the system.  

References
Lamsweerde, A. van. (2009). Requirements engineering: From system goals to UML models to software specifications. West Sussex, England: John Wiley.
Ambler, S. W. (2005). The Elements of UML„¢ 2.0 Style. Cambridge University Press. 

Retrieved from http://libdatab.strayer.edu/login?url=https://search.ebscohost.com/login.aspx?direct=true&db=nlebk&AN=149820&site=eds-live&scope=site