Should I make two separate use cases if a Member of the website can View their own personal profile and those of other users? Should it be Member – View Own Profile and Member-View Others’ Profile? Or just Member – View Profile is enough?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Should I make two separate use cases if a Member of the website can View their own personal profile and those of other users? Should it be Member – View Own Profile and Member-View Others’ Profile? Or just Member – View Profile is enough?
As per comments, An use case can have one complete scenario/feature/function of the application. Hence if you are talking about use-case of member viewing profile, then it will be one use case but if you are talking about test cases for verification, then it would be two test cases.
A member viewing own profile does not mean that he can view others profiles too. Hence you need to have two test cases for verifying both the possibilities.
On the other hand, there are few more cases in this too – you should have cases like member able to edit his profile, edit others profile and this can also go to individual fields too. Member being able to edit all his details, but able to edit few details of other particular members below him in hierarchy and should not be able to edit any details of other members above him in hierarchy etc.