1 / 16

Evaluation of the ALCA Project

Evaluation of the ALCA Project. Workshop Group 1 Jeffrey Schott Bhavana Mungara Kiran Bojja Sri Harsha Meda. Presentation Overview. Overview of ALCA What method for Evaluation? Evaluation of ALCA Architecture Additional features we propose Analysis. Overview of ALCA.

quito
Download Presentation

Evaluation of the ALCA Project

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. Evaluation of the ALCA Project Workshop Group 1 Jeffrey Schott Bhavana Mungara Kiran Bojja Sri Harsha Meda

  2. Presentation Overview • Overview of ALCA • What method for Evaluation? • Evaluation of ALCA Architecture • Additional features we propose • Analysis

  3. Overview of ALCA • Purpose of ALCA • Features • Architecture Overview

  4. Architectural Overview – Use Case Diagram

  5. Architectural Overview - Sequence Diagram

  6. Architectural Overview - Class Diagram

  7. Evaluation Method • ATAM • Comparison with other evaluation methods

  8. Evaluation of Architecture • Analysis of an existing component. • A function specified in the requirements but missing in the architecture. • Additional function to increase the reliability of the architecture. • Addition of a component to the architecture.

  9. Scenario 1 : Single Sign-On • “UMKC single sign on is used to login”. • Key attributes that affect the architecture: • Performance • Reliability • Security • Modifiability • Sensitivity and Tradeoff points • Analysis • Performance → Only have to login Once • User Friendly • Security → Can’t access application unless logged in. • Modifiability → Changes to the application do not affect single sign on.

  10. Scenario 2 :Update Grades • “ Teachers will be able to override the system assigned grade”. Original View : Changes Made:

  11. Scenario 2 :Update Grades (contd.) • Key attributes that affect the architecture: • Performance • Reliability • Sensitivity and Tradeoff points • Analysis • Performance & Reliability → Overcome incorrect grading algorithm → Overcome incorrect grading keys.

  12. Scenario 3 : Test Lock • Why Test Lock? Changes made:

  13. Scenario 3 :Test Lock (contd.) • Key attributes that affect the architecture: • Performance • Reliability • Security • Modifiability • Sensitivity and Tradeoff points • Analysis • Performance & Reliability → Accurate reflection of student performance • Security → Increase test security for teachers-students cannot retake the same test. • Modifiability → Allows for addition of test cancellation function. • Good for Traditional and bad for Adaptive

  14. Scenario 4: Cache DB • Saving test progress to resume a test • Requirement fulfilled by a Cache Database

  15. Scenario 4 :Cache DB (contd.) • Key attributes that affect the architecture: • Performance • Reliability • Sensitivity and Tradeoff points • Analysis • Performance & Reliability → Recover from system crashes → Prevents exhaustion of limited number of tests. • Good for Adaptive and Bad for Traditional

  16. Questions

More Related