Mobile robot controller Group 2 Robot controller project

Mobile robot controller Group 2 - Robot controller project TDT 4240 Software Architecture

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

Introduction n Project problem ¨ What we should do ¨ The quality attribute in focus was availability Group 2 - Robot controller project TDT 4240 Software Architecture

Lookout Captain Uses Navigator Uses Pilot Uses Blackboard architectural pattern Blackboard Uses Perception subsystem Group 2 - Robot controller project - TDT 4240 Software Architecture

Attributes realised in architecture n Availability ¨ Redundant blackboards ¨ Voting ¨ Possibility for redundant crewmembers Group 2 - Robot controller project TDT 4240 Software Architecture

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

Findings/achievements n n n 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 TDT 4240 Software Architecture

Demonstration Strategy: 1. 2. 3. 4. Build internal map Map-matching Cover map Move all balls Group 2 - Robot controller project TDT 4240 Software Architecture