What is different between system boundary and automation boundary in uml? [closed]

Closed.开发者_开发知识库 This question needs to be more focused. It is not currently accepting answers.

---

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 3 years ago.

Improve this question

I'm really hard to understand about the differences between system boundary and automation boundary in UML.

I google it, but on exactly same picutre, someone call system boundary, the other call automation boundary.

Could you teach me what is different? or just same word?

Thank you :D

---

System boundary is the separation between a system and its environment that inputs and outputs must cross where as Automation boundary is the separation between the automated part of a system and the manual part of a system.

---

Automation Boundary is the automated part of the system, where the work is done by computers.

---

Well, as far as i know in Use Case Diagrams there is sytem boundary. Generally it is not used much.

Some System Analysis (Systems Analysis and Design in a Changing World) books call it as "automation boundary". I think those books are generally old system analysis and design books which update their content for Uml BUT still use their old jargon.

So what they call "automation boundary" is "system boundary" in practical UML jargon. And generally sytem boundary shape does not used much in UML diagrams.

---

Inside the automated boundary, the actor is the system (or may be the time).

The system boundary contains both, automated and manual (human actor) use cases of the system