In order to build a software architecture suitable to robotic soccer, it is necessary to model the base concepts of human soccer. In human soccer, the coach plays an important role in planning the moves, tactics and strategies to prepare its team to a match, while in robotic soccer the coach usually does not exist. The architecture must be concerned by concepts like coach, player, player's role, play/move, formation, tactic and strategy, in order to plan and play "correctly" a match. Although there exists other works using these terms, their definitions are not standardized, leading to confusion because they use the same term for different concepts. We propose a definition closer to human soccer facilitating the description of particular instances of players, tactics and strategies. In this way, a human soccer coach can express his ideas and apply them to a robotic soccer match. This paper presents these definitions, their relationships and their application helping the coach to describe his team, his strategies and to deal with the match dynamics. Software process will be used to build architecture and to implement the system. This system will be tested in the simulation category of Robo Cup.