CRC cards and class relationship diagrams should also be A use case describes a collection of scenarios. A use case involves an actor and the flow that a particular actor takes in a given functionality or path. These often get grouped so you have a. High-level use-case; Extended use-case; Difference between use case and scenario. Use- A use-case achieves a discrete goal for the user; Examples.
User Stories have become more popular with the advent of Agile Methodologies that emphasize customer collaboration, user interaction and simplicity.
Use Case Diagrams These are diagrams that can be used to more clearly illustrate the set of use cases that are provided by the functionality in a system. The diagrams contain both the external entities that will be using the system also known as "actors" and the discrete use cases or goals that the users will be carrying out. These diagrams are typically represented in the UML modeling language though other forms do exist and will help the business analyst convey the relationships between the actors and their business goals and how the design of the system needs to support their different objectives with integrated business processes.
Relationship to Functional and System Requirements Use cases are often used as a means of discovering and representing functional and system requirements since they define the interactions and tasks necessary for carrying our specific business objectives.
However they typically are not a good way of defining non-functional requirements such as technical requirements or system qualities. A requirements traceability matrix is used to ensure completeness - namely that all functional requirements are covered by at least one business use case, and that all system requirements are covered by at least one system use case. Relationship to Test Cases Since you typically need to ensure that there is complete requirements test coverage for a successful quality assurance program, use cases provide a good starting point for the design of test cases that will be used to test that the system meets the specified requirements.
Once the requirements engineering activities have been completed and the business analysts are happy with the requirements definitionthe test writers can create test cases based on the system use cases. This usually involves adding more detailed pre-conditions and post-conditions and writing different test cases "variants" of the same use-case to cover different testing scenarios.
Create a Schedule The student enters 4 primary course offering numbers and 2 alternate course offering numbers. The student then submits the request for courses. Checks that prerequisites are satisfied for the requested course. Adds the student to the course offering if the course offering is open. Alternate flow If a primary course offering is not available, the system will substitute an alternate course offering.
Review a Schedule The student requests information on all course offerings in which the student is registered for a given semester. The system displays all courses for which the student is registered including course name, course number, course offering number, days of the week, time, location, and number of credit hours.
Change Schedule - Delete a Course The student indicates which course offerings to delete. The system checks that the final date for changes has not been exceeded.
The system deletes the student from the course offering. The system notifies the student that the request has been processed. Change Schedule - Add a Course The student indicates which course offerings to add. Verifies that the maximum course load for the student has not been exceeded.
Difference between scenario and use-case - Software Engineering Stack Exchange
The Elaboration Phase During Elaboration, some of the most important and critical use cases are implemented. During this phase, the focus is good class structure and architecture. Development of Scenarios Each use case is a web of scenarios. Scenarios are documented using Sequence Diagrams. Objects are represented as vertical lines and messages between objects are shown as directed horizontal lines. Sequence diagrams are drawn in the Use Case View of the tool. Each class should have a definition which states the purpose of the class.
Attempt Assessment A candidate indicates to a proctor their desire to take an assessment. This may involve simply showing up at a previously-schedule time and place when the assessment is going to be available.
The proctor provides the candidate with a copy of the assessment and an empty response document. The proctor authorizes the start of the assessment session. The candidate reads the assessment, and repeatedly selects items from it. For each selected item, the candidate creates a response, adding it to the response document.
The proctor ends the assessment session after time has expired. The candidate returns the response document to the proctor. Grade Assessment The scorer begins with an assessment and a collection of response documents. Then for each response document, the scorer goes to the item response for that same item, grades the response using that rubric, and adds the resulting core and if provided feedback to the result document for that response document.
When all items have been graded, then the scorer computes a total score for each results document. The scorer add the score from each result document to the grade book. Grade Item Given an assessment item, its rubric, and an item response, The scorer applies the rubric to the item response to obtain a raw score and, possibly, feedback text for the item. The raw score is scaled to match the point value in the rubric to the point value of the item in the assessment.
The results is returned as the result score, together with any feedback. The basic path constitutes a single scenario. Author edits an existing assessment, possibly altering one or more of the assessment properties.
Author concludes this work session, saving the assessment for later editing without releasing it to the proctors. A candidate indicates to a proctor their desire to take an assessment.
The proctor determines that the candidate is not eligible to take the assessment at this time the assessment is not available or the candidate has not fulfilled assessment requirements such as being enrolled in the course. The use case terminates immediately. Proctor randomly selects one of multiple available variants of the assessment.
The proctor gives that selected assessment and an empty response document to the candidate. The response document and the assessment copy are a single document. Candidate provided response document 2: