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.
- Agreed. This was also my argument at work but the counter argument states "the communication details is defined already at top level by system architects because they are the ones that know with whom we will interface. Therefore it is a top level constraint". So even though only lower levels need this information, it is still decided at the top level. My suggestion was that the top level designers than write lower levels contraints directly on their layers, but I am not sure if that is a good practice. The writer of lower level requirements should be a lower level engineer, or not necessarily?felipe– felipe2024-08-07 09:26:37 +00:00Commented Aug 7, 2024 at 9:26
- @felipe - stratification or "silos" are bad - when working on medical devices we were often working on multiple levels at once if we had the cross-cutting knowledge. Sometimes in groups - me as an engineer with technical knowledge, someone with clinical knowledge of the product, and someone from testing to ensure that the requirement was written in a testable way.Joris Timmermans– Joris Timmermans2024-08-07 09:36:51 +00:00Commented Aug 7, 2024 at 9:36
- So you mean it is not necessarily considered bad practice if one, for example, creates a kind of "global constraints document" and everyone, that hast a constraint to add, could add it to this document, stating to which level it should apply? Then, this constraint would be only be fed as input to that specific layer when modelling that layer, even though the constraint writer is not necessarily part of the development/architect team of that layer?felipe– felipe2024-08-07 12:20:25 +00:00Commented Aug 7, 2024 at 12:20
- 1No, not a global constraints document - but making sure that at high-level there were only high-level descriptions, with the details of their implications at lower levels possibly written at the same time by the same group of people.Joris Timmermans– Joris Timmermans2024-08-07 12:36:08 +00:00Commented Aug 7, 2024 at 12:36
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