According to lei in AUP there is only functional requirement, a functional requirement is not equal to a user history?
According to lei in AUP there is only functional requirement, a functional requirement is not equal to a user history?
Is a functional requirement not the same as a user story?
The answer is no, it is not the same.
A user story belongs to agile methodologies, where only the value of the definition is given to the user, let's say it is a bit more general.
A functional requirement is oriented to the classic project management or commonly known as cascade. A requirement or functional requirement is more in detail, where inputs, outputs, expected behavior, involved and modified components, implementation etc. must be specified.
Can a user story work together with a functional requirement?
I think so, let's say the problem can be as broad as you want to see it. A user story can have complementary documentation with itself that involves the technical detail of what is intended with that story. It is not fought to work the same requirements in different methodologies, however, it is not the best practice and you would lose different advantages such as being an "agile" development.
User history and Functional Requirement are different concepts, user stories have some aspects that make them different from what is a requirement, user stories must not have the level of detail that a requirement specification has, the user stories are short, easy to memorize, being sometimes impossible for a user story to have all the information needed to develop, they have nothing related to tests, regulations, or details to code, while specifying a functional requirement if I would have that information.
Good. Take it as follows. A functional requirement is the real and understandable part of a user's entire story. As you know the story may be full of deception or unnecessary information but the functional requirement is the part that is really understandable and relevant to the whole story.