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 think the next stage afterwards is choose two of the use cases and describe them. The first stage is: list of actors and use cases initiated by each actor. My problem is i dont have a clue where to start with the whole requirements list and how each differsRHH– RHH2019-03-11 16:59:47 +00:00Commented Mar 11, 2019 at 16:59
-
@RHH Bear in mind that requirements aren't use cases. You need to read them, then work out who the actors must be - what people will be interacting with the system. That's the easy bit. Teasing out the use cases is more difficult. You need to look at what the system is supposed to do, from the requirements, and then work out how the people will need to interact with the system to achieve that. That is entirely down to you working out what the system is for, and then teasing out what the users will do. The question writers aren't making it easy for you here.Simon B– Simon B2019-03-11 22:50:39 +00:00Commented Mar 11, 2019 at 22:50
-
So where do i begin with this then... I need to read through the requirements and pick out elements of what the system needs to do. Then see who interacts with them. And then what do you mean by teasing? Also, say when i actually understsnd and begin to document it... what will i need to document. Just a list of actors and use cases linked to them. Or the actual diagram, and if so a diagram for each of the 5 seperate areas of the requirements or all togetherRHH– RHH2019-03-12 13:23:16 +00:00Commented Mar 12, 2019 at 13:23
-
By "teasing", I just mean that some use cases are more obvious than others. 3.1.8 looks like a use case to me. 3.2.2 isn't a use case at all. There might be one or even two use cases implied by 3.2.7.Simon B– Simon B2019-03-12 16:01:38 +00:00Commented Mar 12, 2019 at 16:01
-
I think I'm starting to get it a bit more, so basically I've just got to go through the requirements and determine which are actual things the system needs to doRHH– RHH2019-03-12 16:08:14 +00:00Commented Mar 12, 2019 at 16:08
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