Behavioral requirements engineering of large-scale software systems, using current Formal Description Techniques (FDT), is complex and difficult. In Statecharts, this complexity is evident in the form of a blow-up in the number of states and difficulty of managing the name space. We have introduced a notation, called Viewcharts, which reduces the complexity of expressing behavioral requirements of large systems. Viewcharts extends Statecharts to include behavioral views and their composition. In this paper we present an overview of the Viewcharts notation and establish its semantics via translation to Statecharts.