【正文】 odel, as well as a data dictionary. Data Objects Action TypeThe action_type table stores information about the types of actions that are performed in the audit trail. These actions may include “update” and “delete”. Audit TrailThe audit_trail table stores information for an action involving an “update” or “delete”. This information involves the user’s id that performed the action, the user’s workstation id, the action performed, the date, the time, and a constructed string of the previous record before action was performed. HolidayThe holiday table stores dates and names for holidays. It is when scheduling inspections so that the system ignores any holidays. Home TypeThe home_type table stores information about the different home types used in the system. This table is used specifically for the inspections table. The current home types are “single”, “duplex”, and “multi”. Each home type has a weight, which is used in determining how many homes an inspector is inspecting in a day. Inspection Date DefaultThe inspection_date_default table is used to store the default number of homes an inspector may expect on any given day. If there isn’t a specific amount for the current date in the inspection_date_specific table, then the num_allowed_per_day value in the inspection_date_default table is used as a maximum amount before an admin is prompted. Inspection Date SpecificThe inspection_date_specific table is used to store the number of homes an inspector may expect on a specific date. The num_allowed_per_day value is used as a maximum amount before an admin is prompted. Inspection TimeThe inspection_time table is used to store the different times of the day that inspections can take place. Currently the only times are “AM” and “PM”. However, in the future they may change to having three or four times a day in which inspections will take place. This gives them flexibility. Inspection LocationThe inspection location table is used to store the different locations in which sections can take place. Currently the only locations are “East” and “West”. However, in the future they may divide the city into a more defined breakdown of city locations. This would allow them extra flexibility. Inspection ScheduleThe inspection schedule table is used to store information about inspections. It acts as the primary table in the system in terms of scheduling and each record in the table represents an appointment. All information pertaining to an appointment is recorded in or related to this table. Inspection StatusThe inspection_status table stores information for the different inspection statuses. Currently the only statuses are “Open” and “Closed”. Inspection TypeThe inspection_type table stores information for the different types of inspections. Currently the inspection types in the system are “first”, “second”, and “final”. InspectorThe inspector table is used to store information about inspectors. It saves their id, name, and status. Inspector Days OffThe inspector_days_off table is used to store the days off for each inspector. Each record stores the id of the inspector, the date that they will have off, and the reason for the day off of work. Inspector StatusThe inspector_status table stores information for each of the types of inspector statuses. The current status types in the system are “active” and “inactive”. UserThe user table stores information about the users of the system. The user id, user name, password, name, and role are stored in the user table. User RoleThe user_role table stores information for the different roles in the system. Currently the only roles in the system are “viewer”, “administrator”, and “super administrator”. Architectural and ComponentLevel Design Program StructureArchitecture is not the operation software. Rather, it is a representation that enables a software engineer to 1) analyze the effectiveness of the design in meeting its stated requirements, 2) consider architectural alternatives at a stage when making design changes is still relatively easy, and 3) reduce the risks associated with the construction of the software. Architectural design focuses on the representation of the structure of the software ponents, their properties, and interactions. Architectural DiagramPlease see the appendix for the architectural diagram of the overall systemPage: 12Does not seem to be present in the appendix (as either an ACD or UML equivalents). AlternativesThe main architecture for this project is a datacentered architecture. Our requirements stated we need to develop a program that will not only store data but also allow multiple users to retrieve and modify that data. As the integrity of that data is very important, some sort of data store would be ideal. This way, different users from all over the department could have access to the same data at the same time pared to the old paper system, in which there was only one clipboard which held the data.Two other minor architectures exist within this system. A dataflow architecture is present, despite that data may not pass through more any more than two filters before reaching it’s destination. This is mostly automated by the suite of programs we are using ( and MSSQL). Most of the data manipulation happens with and formatting it to the next ponent’s expected form.The other minor, and last, design architecture was a layered architecture. There are ponents which handles interactions with the user. Components within the next inner level () handle transform data from the user interface to the database interface or from the database interface to the user interface. Lastly, at the core we have the database itself and it’s ponents in the form of stored procedures.The two other main arch