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.
What are the best practices for using use cases to model system behavior that is executed periodically based on a schedule (rather than executed as a direct result of an explicit user interaction)?
If ‘time’ is modeled as an actor, what are accepted approaches to describing how time is used to trigger the use case (e.g. whether the period is configurable, valid ranges, etc.)?
Is the scheduling part of your system or external to it?
If the schedule is external, then I treat it as the actor. We then don’t see time.
If scheduling is the system’s responsibility, then I think it’s may be helpful to think of time as an actor “tolling the bell”, or in other words providing input. Enumerating time’s responsibilities helps in the design of the schedule. However there will also be other actors who actually set the schedule. Separate time, from schedule.