1 / 8

Notify “dispatcher”

Developer Agent Run. Start. Notify “dispatcher”. Dispatcher. Wait for message. “assignment” message. “ partyOver ” message. Run simulation. Send “ done” message. Sensorbase. Terminate. Developer Agent Setup. ACLMessage. PROPOSE. Agent setup. Expertise level

jolie
Télécharger la présentation

Notify “dispatcher”

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. Developer Agent Run Start Notify “dispatcher” Dispatcher Wait for message “assignment” message “partyOver” message Run simulation Send “done” message Sensorbase Terminate

  2. Developer Agent Setup ACLMessage.PROPOSE Agent setup • Expertise level • Allowed expertise deviation • Sensorbase host • Sensorbase email • Sensorbase password ACLMessage.REQUEST Simulation setup • Project name • Project URI • Class name • Number of functional points • LOC per method Simulation run

  3. Developer Agent Run • Expertise level • Allowed expertise deviation • Sensorbase host • Sensorbase email • Sensorbase password • Project name • Project URI • Class name • Number of functional points • LOC per method • Development time • LOC’s • Churns • Builds • Tests Sensorbase

  4. Simulation JADE Conteiner Requirements Number of classes Dispatcher agent Func points /class Developer1 Job queue LOC / method Developer2 Developer parameters Team Developer #n Developer Expertise Dispatcher GUI Sensorbase

  5. Should job carry sensorbasecredential or the agent gets in on setUp stage.

  6. How we calculate • One developer work on the one class at the time • Speed of development is the FP per hour. • Speed of development depends on the level of expertise. • Not yet done • Coverage depends on expertise. • Number of successful tests/builds depends on expertise. • We have 8 hr work day , 5 days a week.

  7. Title Number of developers: Slider: [0, 100] Average level expertise: Slider: [0, 1] St. dev of expertise level: Slider: [0, 1] Number of classes: Slider: [0, 100] Avg methods per class: Slider: [0, 20] Avg LOC per method: Slider: [0, 100] CONTROL BUTTONS STATUS WINDOW Status

More Related