1 / 14

IS351-System Analysis

IS351-System Analysis. Lab3 Use Case Modeling - Event decomposition technique. Use Case Modeling Techniques. The user goal technique. A technique to identify use cases by determining what specific goals or objectives must be completed by a user.

tteresa
Download Presentation

IS351-System Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IS351-System Analysis Lab3 Use Case Modeling - Event decomposition technique

  2. Use Case Modeling Techniques • The user goal technique. A technique to identify use cases by determining what specific goals or objectives must be completed by a user. • The event decomposition technique. A technique to identify use cases by determining the business events to which the system must respond Modeling System Requirements – Use Case Model

  3. The Event Decomposition Technique • Event : something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system. • Events drive or trigger all processing that a system does, so listing events and analyzing them makes sense when you need to define system requirements by identifying use cases. • Examples for an event: a user places a reservation, periodically monthly paid fees statements and validating user data. Modeling System Requirements – Use Case Model

  4. Event Decomposition technique • Event types: • External Event • Ex: a customer places an reservation order • Temporal Event • Ex: generating a monthly fees statement. • Internal/State Event • Ex: Validating the customer data after places an order Lab 1: IS Analyst Skills and Ethics

  5. The Event Decomposition Technique The Event Decomposition Technique steps 1. Consider the external events in the system environment that require a response from the system 2. For each external event, identify and name the use case that the system requires and the external agent who initiated it. 3. Consider the temporal events that require a response from the system 4. For each temporal event, identify and name the use case that the system requires and then establish the point of time that will trigger the use case. 5. Consider the internal/state events that the system might respond to, particularly if it is a real-time system in which devices or internal state changes trigger use cases. 6. For each state event, identify and name the use case that the system requires and then define the state change.

  6. Considerations for Use Case Diagrams • Do not represent the flow of information or sequence of events. • Do not represent communication between actors. Keep the focus on putting the system in context, not the actors. Actors may collaborate through a use case. • Actors are not always roles played by a person. Actors may represent the role played by anything that acts on the system such as another system.

  7. Example (FCI-Course Registration) • In FCI each student enroll in any course through the ecom system. The student first needs to Login with a valid username and Password, then he/she chooses the course he wants to register in. To complete the course registration, The system checks if the student took the prerequisite courses of the selected course or not. If the student took all course prerequisites the course registration is done successfully, If not, then the student is informed by the pre-requisite courses that he/she needs to take before registering in this course. • Instructors who teach courses are the ones responsible for recording attendance of the students in their lectures/labs. Modeling System Requirements – Use Case Model

  8. Identifying Events • In FCI each student enroll(External)in any course through the ecom system. The student first needs to Loginwith a valid username and Password, then he/she chooses the course he wants to register in. To complete the course registration, The system checks(Internal/State) if the student took the prerequisite courses of the selected course or not. If the student took all course prerequisites the course registration is done successfully, If not, then the student is informed(Internal/State) by the pre-requisite courses that he/she needs to take before registering in this course. • Instructors who teach courses are the ones responsible for recording attendance(External)of the students in their lectures/labs. Modeling System Requirements – Use Case Model

  9. Identifying Use Cases • In FCI each student enrollin any course through the ecom system. The student first needs to Login with a valid username and Password, then he/she chooses the course he wants to register in. To complete the course registration, The system checks if the student took the prerequisite courses of the selected course or not. If the student took all course prerequisites the course registration is done successfully, If not, then the student is informed by the pre-requisite courses that he/she needs to take before registering in this course. • Instructors who teach courses are the ones responsible for recording attendanceof the students in their lectures/labs. Modeling System Requirements – Use Case Model

  10. Identifying Actors • In FCI each student enroll in any course through the ecom system. The student first needs to Login with a valid username and Password, then he/she chooses the course he wants to register in. To complete the course registration, The system checks if the student took the prerequisite courses of the selected course or not. If the student took all course prerequisites the course registration is done successfully, If not, then the student is informed by the pre-requisite courses that he/she needs to take before registering in this course. • Instructors who teach courses are the ones responsible for recording attendance of the students in their lectures/labs. Modeling System Requirements – Use Case Model

  11. Use Case Diagram Enroll in Course <<Include>> <<Include>> Student Instructor Login Check Course Prerequisites Modeling System Requirements – Use Case Model Display Prerequisites <<Extends>> Record Attendance

  12. Exercise: Multi-Clinic System • In a multi-clinic system a patient makes a call for an appointment reservation. Once the call is done, the system has to record all patient information such as patient name, address, and telephone number. • During the notification with a patient, he/she should know all possible appointments in order to choose his/her desired appointment. • The patient may cancel or change his/her appointment before 24 hours from his actual appointment. • Two daily reports have to be prepared to each doctor, one of them is about patient report and the other is an appointment report. • When a patient comes for examination, the doctor writes a prescription which includes all drugs the patient have to take, number of times and dose he has to take for each medicine. In the end, the doctor Prints the prescription to the patient before he leaves Modeling System Requirements – Use Case Model

  13. Exercise: Multi-Clinic System Modeling System Requirements – Use Case Model

  14. Multi Clinic System Use Case Diagram Modeling System Requirements – Use Case Model 17

More Related