1 / 10

SAAM and ATAM analysis of AOCS

SAAM and ATAM analysis of AOCS. CS294-10 Fall 2000 Jason I. Hong. SAAM Stakeholders. Companies that want to use AOCS Developers Ground Control ESA. SAAM Scenarios. Component needs more than standard allocated time to execute? Potential deadlock if components need locks on resources?

meg
Download Presentation

SAAM and ATAM analysis of AOCS

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. SAAM and ATAM analysis of AOCS CS294-10 Fall 2000 Jason I. Hong

  2. SAAM Stakeholders • Companies that want to use AOCS • Developers • Ground Control • ESA

  3. SAAM Scenarios • Component needs more than standard allocated time to execute? • Potential deadlock if components need locks on resources? • Ground control outage?

  4. SAAM Scenarios 1. Component needs more than standard allocated time to execute? • Ex. Task needs lots of processing that cannot be split up • Change Scheduler to give everyone more time (larger uniform time slices) • Or change Tasks to declare timing information (non-uniform time slices)

  5. SAAM Scenarios 2. Potential deadlock if components need locks on resources? • Ex. Need to make sure no one else writes data until done • Can tasks maintain state across time slices? • If so, may need locks to avoid race conditions • Locks may introduce possible deadlock • Affects Tasks, no general resource manager?

  6. SAAM Scenarios 3. Ground control outage? • Ex. Faulty ground control • Potential buffer overflow if needs ACK? • Potential lost data if it doesn't need ACK? • Objects write themselves to telemetry, affects these objects

  7. ATAM Quality Attributes • Reliability • Reusability • Efficient

  8. ATAM Analysis • Reliability • Failure detection • Failure recovery • Redundancy • Not clear how redundancy is handled • Look at why satellites failed historically • See how AOCS can help • Are they app-specific problems or general problems that should be in frameworks?

  9. ATAM Analysis • Reusability • Extensible for new sensors • Extensible for new s/w components • Available tools

  10. ATAM Analysis • Efficient • Hard real-time deadlines • Low overhead • What happens with more resources?

More Related