【正文】 hey should be able to view just their inspection schedule, not anyone else’s, and should not be able to edit it in anyway. Component View Schedules Processing Detail Interface DescriptionOne input needed here will be the user’s privileges, decided by the User Verification ponent. As of deployment of this system, there should only be readonly, administrator, and super administrator defined as privilege levels.Another will be the date which to view inspection schedules. The user may do this by navigating through a small calendar on their screen. Clicking an appropriate day will submit that day, as an output, to the database to query. Algorithmic ModelComponent ViewSchedules。 Restrictions/LimitationsThis ponent needs to be able to work in multiple junctions within our system. Thus, making it’s interfaces and inner functions too specific will slow down the team when implementing it in multiple places throughout our system. Local Data StructuresA temporary string object may be instantiated to store entries which cannot be processed on the screen at the moment. Performance IssuesNone at this time. Design ConstraintsThis ponent will be used by many different ponents but for input and output. Therefore, the level of abstraction needs to be high enough that we are able to interface properly with specific ponents or functions while still maintaining a highlevel view allowing it to be replaced by another ponent without much hassle or used in another system altogether. Description for Component Read In Data Component Read In Data PSPECIn order for the system to function prope。send modData to a stored procedure which will allow the database to change entries。 Restrictions/LimitationsNone at this time. Local Data StructuresA set of strings which hold enqueued entries from the Audit Trail when there is too much information to display on screen at one time. Performance IssuesDe to the large amount of entries, retrieving and displaying all of them, which may number into the thousands for the past six months, may take a bit longer than a normal query on the database.The format of the data will not be displayed in a polished manner as it normally would if an administrator or inspector were looking at a current schedule. This may present 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。 Drop down menu for selection of records Program will identify and skip holidays, days off and inactive inspector. 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. get deleteData from ReadInData。 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