I’m working on a computer science discussion question and need guidance to help me learn.
In your responses to your peers:
- Discuss whether you agree or disagree with the claims that your peers make.
- Reflect on what could happen if the system solution acts differently than what is shown in the UML activity diagram.
PEER POST # 1:
UML activity diagrams is an example of one of the best ways you can lay out Use-Cases with objects and figures that make it very easy to understand and implement. Anyone should be able to read a UML activity diagram, making it a great way for technical and non-technical groups of people to speak and interact with. Although UML diagrams would seem to be great within the planning phase of the project since it would help define the scope of the project, I think it best fits the define requirements phase. I believe this since it really helps everyone plan out the specific uses that the project could have – allowing everyone to contribute to the requirements. Use-cases could easily be used to determine what would need to be required from the project.
It is essential to develop a UML activity diagram prior to the developers writing the code for a system since the UML diagram basically lays out how everything would interact with one another. This needs to be done before coding the system since it definitively defines what needs to be able to interact with each other within the code, and essentially how things need to be for the code to work properly. Without the diagram, the coders might miss a very important function/interaction!
I can easily see UML diagrams being incredibly useful for my professional career as a future developer or IT professional on a project team. It would allow me to visually explain what I am thinking while also having the technical side there. It would allow non-technical group members to add to the project, while allowing the technical group members to make changes to the table as-needed. These diagrams create a link between project members, making them paramount to any discussion.
Use case diagrams and UML activity diagrams are similar in the sense that they create a very visual way of presenting information while also being easy to understand. It makes technical jargon become visual, allowing anyone to comment on these aspects.
PEER POST # 2:
Based on what I’ve learned about system design, analysis, and SDLC, I think that a UML activity diagram should be created as early as possible. By doing this in one of the earliest phases, it gives all stakeholders a clear understanding of what the project entails. It also gives a clear outline as to what functions the project needs to ensure success. Therefore, I think that UML belongs in the Systems Analysis Phase. It is important to develop a UML activity diagram prior to the developers writing the code for a system because it can ensure that the development team has a clear and concise understanding of where the project needs to go. This can ensure that the correct features and functions are targeted, and time is not wasted on unnecessary features and details. These diagrams help to visualize the flow and attributes of each of the classes. They also can show how each class can relate to another one, or even not at all. The system boundary helps to show what would be included and how it relates to the actors within the completed workflow of the system.