USC
This presentation is the property of its rightful owner.
Sponsored Links
1 / 18

SAIV/CAIV/SCQAIV PowerPoint PPT Presentation


  • 105 Views
  • Uploaded on
  • Presentation posted in: General

USC. University of Southern California. C. S. E. Center for Software. Engineering. SAIV/CAIV/SCQAIV. LiGuo Huang USC. USC. University of Southern California. C. S. E. Center for Software. Engineering. Outline. Why SAIV/CAIV/SCQAIV? The SAIV Process Model Fulltext Title Database

Download Presentation

SAIV/CAIV/SCQAIV

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


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

SAIV/CAIV/SCQAIV

LiGuo Huang

USC


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

Outline

  • Why SAIV/CAIV/SCQAIV?

  • The SAIV Process Model

  • Fulltext Title Database

    • A SAIV Case Study

  • The CAIV/SCQAIV Process Model


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

Is This A Problem?

  • The clients propose cost, schedule, or quality constraints

  • — Want the system on a ridiculously

  • short schedule

  • And they aren’t even willing to commit on just exactly what they want


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

Is This A Problem?

  • Yes, when you accept the schedule target before

    understanding the requirements

    • Retrofit the required capabilities in an ad-hoc way

    • Reduce the scope or dropping features

    • Success is more a matter of luck and heroic efforts

    • Usually, this leads to a Death March

  • No, if you use the SAIV process model


The saiv process model

USC

University of Southern California

C

S

E

Center for Software

Engineering

The SAIV Process Model

“If schedule is your independent variable, then just modulate your functionality to meet schedule.”

1. Shared vision and expectations management

2. Feature prioritization

3. Schedule range estimation

4. Core capabilities determination

5. Architecture Flexibility Determination

6. Incremental development

7. Change and progress monitoring and control


Core capability determination

USC

University of Southern California

C

S

E

Center for Software

Engineering

Core Capability Determination

  • Core capability not just top-priority features

    • Coherent and workable end-to-end operational capability

    • Facilitate evolution to full operational capability

    • Architected for ease of adding, dropping marginal features


Fulltext title database a saiv case study

USC

University of Southern California

C

S

E

Center for Software

Engineering

Fulltext Title Database – A SAIV Case Study

  • Fixed 24-week schedule

  • 12 prioritized features


Prioritized product features

USC

University of Southern California

C

S

E

Center for Software

Engineering

Prioritized Product Features


Core capability determination1

USC

University of Southern California

C

S

E

Center for Software

Engineering

Core Capability Determination

  • Four capabilities of the Fulltext Title Database system

    — Provide a full-text journal title search capability(High)

    — Update the Fulltext Title Database (High)

    — Administrator password maintenance (High)

    — Accommodate vendors’ title lists in various formats

    (Medium)

  • The first three form a coherent core capability!


Cocomo ii analysis

USC

University of Southern California

C

S

E

Center for Software

Engineering

COCOMO II Analysis

With 90% confidence,

12 features — 40 weeks

7 features — 24 weeks


Architecture choices

USC

University of Southern California

C

S

E

Center for Software

Engineering

Intelligent

Router

F12

F1, F2, F3

F4, F5

F6, F7

F8, F9,

F10, F11

Architecture Choices

Rigid

Hyper-flexible

Flexible


Architecture flexibility determination

USC

University of Southern California

C

S

E

Center for Software

Engineering

Architecture Flexibility Determination


Architecture flexibility determination cont

USC

University of Southern California

C

S

E

Center for Software

Engineering

Architecture Flexibility Determination(cont.)

E – total change effort

N– total number of features (N =12)

m– modularity factor (m = 2.74)

 – a fraction of anticipated changes ( = 5/12)

c1 – average effort to develop a feature

c2 – average development effort of per inter-module interaction

c3 – average development effort of per intra-module feature interaction

c4 – average effort to accommodate a new feature with each existing feature in a module


Incremental development and coping with rapid change

USC

University of Southern California

C

S

E

Center for Software

Engineering

Incremental Development, and Coping with Rapid Change

  • Initial Operational Capability Iteration I

    (70~80% of the schedule)

    — Provide a full-text journal title search capability

    — Update the Fulltext Title Database

    — Administrator password maintenance

  • Initial Operational Capability Iteration II

    — Accommodate vendors’ title lists in various formats

    — Negotiated feature demotion

    • Add F13: Partial keyword searching

    • Drop F12: Allow more searching options starting with searching by ISSN, etc.


Revised architecture

USC

University of Southern California

C

S

E

Center for Software

Engineering

Intelligent

Router

F13

F12

F1, F2, F3

F4, F5

F6, F7

F8, F9,

F10, F11

Revised Architecture

Rigid

Hyper-flexible

? F13

F13

Flexible


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

Conclusions: SAIV Critical Success Factors

  • Working with stakeholders in advance to achieve a shared product vision and realistic expectations;

  • Getting clients to develop and maintain prioritized requirements;

  • Scoping the core capability to fit within the high-payoff segment of the application’s production function for the given schedule;

  • Architecting the system for ease of adding and dropping features in an appropriate level of flexibility;

  • Disciplined progress monitoring and corrective action to counter schedule threats


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

CAIV and SCQAIV

  • SAIV process model also works for Cost as Independent Variable

  • SCQAIV model is a straightforward extension of CAIV and SAIV

    • And “Cost, Schedule, Quality: Pick Any Two?”


Saiv caiv scqaiv

USC

University of Southern California

C

S

E

Center for Software

Engineering

C

C

S

Q

Q

Cost, Schedule, Quality: Pick any Two?

  • Consider C, S, Q as Independent Variable

    • Feature Set as Dependent Variable

“Cost, Schedule, Quality: Pick All Three”


  • Login