Fundamental model calling thru an api
This presentation is the property of its rightful owner.
Sponsored Links
1 / 9

Fundamental Model - Calling Thru an API PowerPoint PPT Presentation


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

Fundamental Model - Calling Thru an API. Coding & design standards. Interface correctness & sufficiency. API Caller. Test. API. Performance. API Provider. Change control / stability. Lessons / Evolution. Were coding standards followed?. Framework unknowns.

Download Presentation

Fundamental Model - Calling Thru an API

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


Fundamental model calling thru an api

Fundamental Model - Calling Thru an API

Coding & design standards

Interface correctness & sufficiency

API Caller

Test

API

Performance

API Provider

Change control / stability

Lessons / Evolution


Jmps building on unknowns

Were coding standards followed?

Framework unknowns

Are there services that the Framework does not supply that applications will need?

How to test the framework itself?

Will there be performance issues for apps?

xxxx framework

(basic svcs)

How stable is the framework? Will it change? Who is in charge of these changes?

Underlying OS and HW

What lessons from designing the Framework API will apply to designing component APIs?

JMPS -- Building on Unknowns


Xxx building on unknowns

Common

components

unknowns

Were coding standards followed?

Who/what defines/enforces coding and development styles??

Will common component(s) need to go around the framework? For what reasons? What interfaces are exposed in the Common component(s) for the ABCs?

Are there services that the Framework does not supply that applications will need?

Common

component

- ZZZZ

Common

component –

WWWW, etc

How to test the framework itself?

How do we test common component(s)?

Will there be performance issues for apps?

Will components raise performance issues?

xxxx framework

(basic svcs)

How stable is the framework? Will it change? Who is in charge of these changes?

Who controls changes to components? How are they decided upon?

What are Lessons learned from the 1st common component? How to leverage these?

What is the plan for evolution of common components?

Underlying OS and HW

What lessons from designing the Framework API will apply to designing component APIs?

Instability at Lower Levels Can Lead to System Wide Chaos

Note: Generic ABC is not totally representative of a “real” ABC or common component

xxx -- Building on Unknowns


Xxxx full architecture

Provides some validation of coding and development styles

tt ABC

tu ABC

Provides some degree of interface validation

Common

component

- ZZZZ

Common

component –

WWWW, etc

Provides testable, integrated thread throughout the system

Enables system throughput analysis

xxxx framework

(basic svcs)

Enables identification and handling of CM, version control and other stability issues

Underlying OS and HW

Enables initial validation of “system manager” roles

xxxx – Full Architecture

A complete pilot requires all layers. Will it all come together?


Fundamental model calling thru an api

UPC Development(s)

document debug repair enhance test

1. Other Integration Efforts

Integration

2. Integration Interface Artifacts

3. Integration Tasks


Fundamental model calling thru an api

UPC Development(s)

Framework

Common Components

document debug repair enhance test

Revision

design

dialogs

Integration

2. Integration Interface Artifacts

3. Integration Tasks


Fundamental model calling thru an api

UPC Development(s)

Framework

Common Components

document debug repair enhance test

Revision

design

dialogs

Source Repository(s)

UPC Problem Reports

Integration

3. Integration Tasks


Fundamental model calling thru an api

UPC Development(s)

Framework

Common Components

document debug repair enhance test

Revision

design

dialogs

Source Repository(s)

UPC Problem Reports

Rebuild

& test

Help desk

Evaluator

/ trainer

Distribute

planner

Integration

2. Integration Interface Artifacts

4. Test Facility


Fundamental model calling thru an api

UPC Development(s)

Framework

Common Components

document debug repair enhance test

Revision

design

dialogs

Source Repository(s)

UPC Problem Reports

test facility(s)

Rebuild

& test

Help desk

Evaluator

/ trainer

Distribute

planner

1. Other Integration Efforts

Integration


  • Login