Because Fecomas contains multiple interconnected functional areas, the documentation follows a module-by-module approach. Each module will be examined from the main navigation through to its individual screens and operations.
The documentation will also distinguish between overview information, configuration functions, and operational workflows. This is important because some parts of the system are used to configure the environment, while others are used for daily school operations.
For example, academic years, terms, classes, class streams, grading systems, subjects, subject allocation, and fee structures are configuration areas, while student registration, enrollment, fee collection, attendance, examination management, library operations, hostel allocation, asset management, and accounting represent operational activities.
This approach ensures that the documentation provides a complete understanding of the system rather than documenting individual screens in isolation.