![]() Student logs into the educational technology platform and selects the option to take a quizSystem presents the student with the quiz questionsStudent answers the questions and submits the quizSystem evaluates the student's answers and provides instant feedback on their performanceStudent views the feedback and can review their answers if they desireSystem records the quiz results and makes them available for the student, educator, and administration to view Student can take the quiz and receive instant feedback on their performance Student must be logged in, student must have access to the quiz Alternative path (or flow) - a variation of the main success scenario, these usually show what happens when there’s an error or unexpected event in a use case.Īn educational technology company wants to develop a feature that allows students to take quizzes and receive instant feedback.Įducational technology company, students, educators, school administration, investors.Basic flow - also called the main success scenario, this is a use case path that works perfectly and as intended with no exceptions (this is often used as a base to create alternative paths).Post-conditions - the statements about the possible states that the system can be in after the use case ends. ![]() Triggers - used to start a use case, triggers are events that initiate the steps of a scenario.Pre-conditions - the statements about what needs to happen before the use case starts.Primary actor - this is someone or something whose goals are fulfilled by the system in question, and while they don’t always start the use case, it’s fairly common for them to do so.Stakeholders - anyone with interests in the functionality and success of the system are called stakeholders, and are often indirectly involved (not users but those that benefit from how the system functions).If we take an e-commerce site as an example, actors might include buyers, credit card companies, shipping companies, and more. Actor - this is someone or something that performs a behavior or action (can be a person or an object). ![]() Use case name, description, and goal - giving a clear and concise name, description, and goal to each use case also helps organize documentation while preventing scope creep.Use case number - assigning a number to each use case helps organize your records and can be sorted in chronological order or by other criteria depending on how the developers decide to label them.These range from the identifier of the use case to who’s involved and alternative solutions: ![]() As you’re writing your use case, there are several components that should typically be included. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |