【正文】 nt a problem for the page if the data is not broken into easily displayable chunks. Design ConstraintsNone at this time. Description for Component Create New Inspection Component Create New Inspection PSPECWhen a person requests a new inspection, where an inspection is one inspector inspecting one building, this should be the ponent that allows the administrator to add an inspection to the database. Component Create New Inspection Processing Detail Interface DescriptionFor the input of this ponent, data will be received from the user by way of the Read In Data ponent. The inputs the user should give are: inspector’s name, the address of the building, contact phone number, which side of the city it resides in, the time of the inspection, the status, the type of inspection to be conducted, and a memo if necessary.This ponent should take the data and pass it to the Validity Check ponent of the system. After the data has been submitted to the database, a message stating either a success or failure will be displayed using the Display Messages ponent. Algorithmic Modelponent CreateNewInspection。 The software will only be available for use on the internal network for the time being. This can be remedied by the City should they decide to open it up to the public, but as of now it will only be available internally. Drop down menu for selection of records Data entry clerks will have the ability to enter vacation, sick, training time or other reasons for blocking dates and times Program will identify and skip holidays, days off and inactive inspector. All tables will allow adding, searching, modifying and deleting records from the same screen Only one data entry person may be working on a specific file at a time. If two people are trying to enter the same inspection at the same time it will cause errors to occur.end View Audit Trail。 get deleteData from ReadInData。 send modData to be validated。 Restrictions/LimitationsAs stated above, this ponent will rely on what privileges the user has. If an administrator is using the system, not only can they view all inspector’s schedules but they also have the ability to edit, delete, and create inspections. If a readonly user is logged into the system, they should only be able to view their schedules and not anyone else’s. Local Data StructuresA set of strings which hold enqueued entries from the schedule when there is too much information to display on screen at one time. Performance IssuesQuerying the database for the information and having it display in a timely matter (less than five seconds) would be helpful to the user. If an inspector calls from the field and asks where the next place they need to go is, the quicker the data is displayed the quicker the inspector can do their job. Design ConstraintsThis is one of the ponents which depends on the security being strong enough to keep out people who shouldn’t be viewing others’ schedules and data. One thing that we cannot prevent, however, is having an administrator log into the system and allowing a readonly user to look at the screen. Description for Component Search Schedule Component Search Schedule PSPECThe inspection schedule will probably bee very populated with data. In order to quickly look up an inspection while only knowing pieces of data that are in the inspection, a search function will be implemented. This ponent will allow the user to search through the schedules by such things as inspectors names, phone numbers, date scheduled, addresses, times, parts of the city, what type of inspection it is, and how large of a building is to be inspected.This function can also allow administrators or super administrators to do some back of the envelope analysis. By searching by just one field and one term, the results shown may bring up certain patterns, such as Wednesday is the busiest day for inspections, or that multifamily homes are more likely to be built on the west side of the city than the east. Component Search Schedule Processing Detail Interface DescriptionThis ponent will take data from the Read In Data ponent. This data can be any one or more of the following: inspector’s name, the address of the building, the date to be conducted, contact phone number, which side of the city it resides in, the time of the inspection, the status, the type of inspection to be conducted, and a memo.The output of the system will be a query sent to the database after it is passed through a Validation Check to make sure the data is of the correct type. Algorithmic Modelponent SearchSchedule。end DisplayResults。end SearchSchedule。call generic query in a stored procedure from 。send message of success or failure to DisplayMessages。pass formData in query to database。 Arranging times to meet up with the business. Data DesignA description of all data structures including internal, global, and temporary data structures. Internal Software Data StructurePage: 5You do not just write definitions here, you actually list your data dictionary as it has evolved since the requirements objects were specified (the design objects usually require implementation) This section describes data structures that are passed among ponents the software. ClassesEach form in the interface has a backend class file, which stores all of the interface functions, stored procedure calls, and variables. Form ObjectsWithin each of the forms there are form objects. There consist of data grids, dropdown menus, text boxes, labels, list boxes, calendar controls and several other form objects. Stored ProceduresAll functionalities in the system are performed using a stored procedure. These stored procedures contain transact SQL that manipulate the data in the database. The procedures are called in the classes. Global Data StructureThis section describes data