uml - Use Cases: separate or not? -


should make 2 separate use cases if member of website can view own personal profile , of other users? should member - view own profile , member-view others' profile? or member - view profile enough?

as per comments, use case can have 1 complete scenario/feature/function of application. hence if talking use-case of member viewing profile, 1 use case if talking test cases verification, 2 test cases.

a member viewing own profile not mean can view others profiles too. hence need have 2 test cases verifying both possibilities.

on other hand, there few more cases in - should have cases member able edit profile, edit others profile , can go individual fields too. member being able edit details, able edit few details of other particular members below him in hierarchy , should not able edit details of other members above him in hierarchy etc.


Comments

Popular posts from this blog

java - SNMP4J General Variable Binding Error -

windows - Python Service Installation - "Could not find PythonClass entry" -

Determine if a XmlNode is empty or null in C#? -