1 / 20

Streamlining Administrative Computing: Use Case Driven Approach by Jane Gao

This presentation by Jane Gao from the University of California, Irvine, explores the iterative and incremental development model through use cases in administrative computing services. It highlights the importance of understanding user needs and enhancing communication between developers and users. The presentation details the components of use cases, such as actors and relationships, and outlines a specific use case for timesheet management. By adopting this structured approach, systems can be developed to better meet user requirements while improving efficiency and quality.

sandra_john
Télécharger la présentation

Streamlining Administrative Computing: Use Case Driven Approach by Jane Gao

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. Development ProcessBehind the Scenes Jane Gao Administrative Computing Services

  2. Agenda • Use Case Driven Analysis • Iterative & Incremental Development • Rational Unified Process (RUP) Model • Q & A

  3. Goals of System Analysis • System must conform to the needs of the users. • Simplifies and provides a better understanding of the system from a user’s perspective. • Improves communications between users and developers. • Saves time.

  4. What is UseCase? • A Use Case is a typical interaction between a user and system that enables the user to perform a required task or achieve a specific goal.

  5. UseCaseElements (I) • Actor • Who will interact with the system • Use Case • Interaction between user and the system • Association Relationship • The relationships between an actor and a use case. • The arrow indicates who initiates the communications.

  6. UseCaseElements (II) • Includes Relationship • Allows one use case to use the functionality provided by another use case. • Extends Relationship • Allows one use case the option to extend the functionality provided by another use case.

  7. UseCaseElements (III) • Generalization Relationship • Shows that several actors or use cases have some commonality.

  8. Timesheet Use Case Capture • Actor • Employee, supervisor, and payroll system. • Goals of employee • Create, submit, update, query timesheet. • Goals of supervisor • Approve timesheet and generate report.

  9. Timesheet Use Case List • Use Cases • Employee creates a new timesheet. • Employee updates existing timesheet. • Employee submits timesheet. • Employee inquires leave balance. • Supervisor approves or un-approves timesheet. • Supervisor generates reports. • …

  10. Describe a Use Case (I) • Use Case Name :Approve Timesheet • Actor:Supervisor • Goal:Supervisor approves submitted timesheets. • Pre-conditions:Login,Submitted Timesheet • Post-condition:Post Timesheet to PPS. • Success Conditions:Approved. • Failure Conditions:Passed the due date.

  11. Describe a Use Case (II) • Flow of activities (Approve Timesheet ): • Business rules

  12. Timesheet Use Cases Diagram

  13. Timesheet Use Cases (revised)

  14. Prioritize the Use Cases • Create Timesheet • Submit Timesheet • Approve Timesheet • Login • Update Timesheet • Release Timesheet to Queue • Generate Reports • Query Leave Balance • View Timesheet • Logout • Post timesheet to Payroll system

  15. Identify Iterations • Iterations • A complete development loop resulting in a release of an executable product. Iteration 1: Create Timesheet, Submit Timesheet Iteration 2: Approve Timesheet Iteration 3: Login, Update Timesheet Iteration #: ….. • Check the performance, scalability, security and reliability in every iteration.

  16. Develop Iteratively

  17. Benefits Of An Iterative Approach • Risks are mitigated earlier. • Change is more manageable. • Higher level of reuse. • Project team can learn along the way. • Better overall quality.

  18. Rational Unified Process (RUP) Model

  19. Summary • Use Case Modeling • Lay out application functions in a Use Case diagram, use it as a roadmap. • Iterative & Incremental development • Analyze a little, design a little, test a little, and loop back.

  20. Q & A Thank You ! Jane Gao Administrative Computing Services University of California, Irvine 949-824-8671 jane@uci.edu

More Related