Both PosiEd and Salesforce Education cloud are designed with one primary purpose in mind, to put the student first and foremost.
To that end both architectures are designed to provide immense levels of flexibility and detail even in the most complex multi school, multi campus environments. In most platforms, offering students flexibility to do things like enroll in more than one campus at a time, to move between classes without interrupting academic assessment, to provide innovative core structures such as IIB and RTO. In addition to HSC etc., have all come to the come with the price of compromise when it comes to the architecture and storage of data on those students. Schools often resort to notes and separate records to keep track of the sometimes complex details.
PosiEd Education Cloud is designed to cater for as many of these challenges as possible. With this in mind, please understand that as you review the architecture. Some of the architectural choices might not immediately appear obvious, so change that to the reasoning behind some of the architectural choices may not immediately appear obvious. There is a far greater depth of consideration for providing are highly flexible Student Record keeping architecture that will accommodate even the most complex School environments and unique needs.
With this in mind, let's consider how we create the records necessary to enroll and manage a student in the PosiEd Environment.
Below is a slightly stylized version ERD of a typical student. Note that it does not include other capabilities that are delivered on top of the standard PosiEd in K-12 applications such as well-being academic assessments, etc. At this point, we are just reviewing the core requirements.
The students and their family
The 1st and most obvious record is to create Contact Record for the student themselves, so change contact to person account. Here you will populate the student's primary contact details. Note that you do not yet have to specify anything related to items such as their grade level. House, etc. This will come later.
The second step is to create Person Account records for their family and career contacts. These can be associated with the student contact via contact, contact relationships. Review how relationships are to be optimally configured. How the cascading of contact details will work and how data import of these relationships can occur?