Development process behind the scenes
1 / 20

Development Process Behind the Scenes - PowerPoint PPT Presentation

  • Uploaded on

Development Process Behind the Scenes. Jane Gao Administrative Computing Services. Agenda. Use Case Driven Analysis Iterative & Incremental Development Rational Unified Process (RUP) Model Q & A. Goals of System Analysis. System must conform to the needs of the users.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Development Process Behind the Scenes' - sandra_john

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Development process behind the scenes

Development ProcessBehind the Scenes

Jane Gao

Administrative Computing Services


  • Use Case Driven Analysis

  • Iterative & Incremental Development

  • Rational Unified Process (RUP) Model

  • Q & A

Goals of system analysis
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.

What is use case
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.

Use case elements i
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.

Use case elements ii
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.

Use case elements iii
UseCaseElements (III)

  • Generalization Relationship

    • Shows that several actors or use cases have some commonality.

Timesheet use case capture
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.

Timesheet use case list
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.

Describe a use case i
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.

Describe a use case ii
Describe a Use Case (II)

  • Flow of activities (Approve Timesheet ):

  • Business rules

Prioritize the use cases
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

Identify iterations
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.

Benefits of an iterative approach
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.


  • 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.

Development process behind the scenes

Q & A

Thank You !

Jane Gao

Administrative Computing Services

University of California, Irvine