1 / 8

Mobile robot controller

Mobile robot controller. Group 2. Group 2. Leif Hamang Bru Lisa W. Eriksen Kay Are Ulvestad Gunnar René Øie. Introduction. Project problem What we should do The quality attribute in focus was availability. Lookout. Captain. Navigator. Pilot. Uses. Uses. Uses. Uses. Blackboard.

sage
Download Presentation

Mobile robot controller

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. Mobile robot controller Group 2

  2. Group 2 • Leif Hamang Bru • Lisa W. Eriksen • Kay Are Ulvestad • Gunnar René Øie Group 2 - Robot controller project - TDT4240 Software Architecture

  3. Introduction • Project problem • What we should do • The quality attribute in focus was availability Group 2 - Robot controller project - TDT4240 Software Architecture

  4. Lookout Captain Navigator Pilot Uses Uses Uses Uses Blackboard Uses Perception subsystem Blackboard architectural pattern Group 2 - Robot controller project - TDT4240 Software Architecture

  5. Attributes realised in architecture • Availability • Redundant blackboards • Voting • Possibility for redundant crewmembers Group 2 - Robot controller project - TDT4240 Software Architecture

  6. We have learned • We should have learned more about the robot before setting our goals, and taken a simpler approach. • Got some more documentation practice. • The ATAM process should be used with larger teams. • Using software architecture may be hard if the system is small and highly interconnected. Group 2 - Robot controller project - TDT4240 Software Architecture

  7. Findings/achievements • ATAM works as a structured way to give feedback. Feedback was valuable, to improve explanation of architectural choices. • Quality requirements are sacrificed to achieve functionality • We were able to make all the modules needed to solve the problem, but didn’t finish putting them together. Why: Discrete movement problem. Group 2 - Robot controller project - TDT4240 Software Architecture

  8. Demonstration Strategy: Build internal map Map-matching Cover map Move all balls

More Related