You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- I wasn't aware of ISO/IEC/IEEE 29148. I agree with you about placing activity diagram in the "System overview" section, because in this case it doesn't dig deep into the logic of the software, but it just provide a general understanding of the program. Regarding use-case, in my opinion the level of detail it reaches can tell whether to put it in the "System overview" rather than "Specifications requirements". A use case diagram should be the graphical representation of a requirement, so put it in that section seems fine. But in my particular case I think it fit better in the "System overview".dcfg– dcfg2020-03-18 11:59:18 +00:00Commented Mar 18, 2020 at 11:59
- @dc_Bita98 Yeah. I think level of detail and intended audience of that particular diagram is going to be the best guide for exactly where to put it. If it's to someone trying to get general ideas about the system under design, then system overview is better. But if it's more for someone to consume when doing design work, then closer to the requirements is probably better.Thomas Owens– Thomas Owens ♦2020-03-18 12:16:27 +00:00Commented Mar 18, 2020 at 12:16
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you