【正文】 s to cancel it. The administrator can then scroll to find the date specified, look for the address, and delete it’s entry. The rest of the schedules for that day will be left untouched. Component Delete Inspection Processing Detail Interface DescriptionThe input to this ponent should e from the Read In Data ponent. The information passed here should include which address needs to be deleted along with the date that the inspection was scheduled on.The output of this ponent will be the data specified above which is passed to the Format Data ponent. After the database has been modified, a message passed back denoting either success or failure will be displayed using the Display Messages ponent. Algorithmic Modelponent DeleteInspection。pass successFailFlag to DisplayMessages。validate formData。 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。if dataReceived spaceAvailableOnScreen partition up dataReceiveddisplay dataReceived。call generic query in a stored procedure from 。 Time is a major constraint that we have on this project. 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. When an inspector retires from the City the people monitoring the data base will have to go into the system and manually set his/her status to inactive so that they are not scheduled on any more inspections. Audit Trails may bee large if there is a single record that is edited frequently. This should not happen as once it is entered it should be left alone. The most that should happen is a reschedule being done on it once or twice. Anyone using the software must have their PC connected to the internal network. Since it runs off of a server the puter must be able to connect to it. Drop down menu for selection of records Allow the user to schedule an inspection for the first available date by specific inspector Allow the user to schedule an inspection for the first available date Program will print inspection reports by one day, multiple dates, specific inspector, and specific inspector by date range Data entry clerks will have the ability to enter vacation, sick, training time or other reasons for blocking dates and times Each inspector will have inspections in the East and /or west end in each daySoftware Design SpecificationElectronic Inspection SchedulerJim CoanJoe WolfordChris LesnieskiCIS 495 – Senior DesignDr. MaximNovember 10, 2005Page: 1You need a table of contents IntroductionThis software is being created to replace the paper version of the building inspection schedule for the Building and Safety department at the City of Dearborn. The program is going to store past inspections, and future inspections. In addition to the storage of information for the scheduling it will also have some added functionality. The additional criterion for the program is the followingPage: 2These need to be made more specific and the requirements (user visibale behavior) and constraints need to be separarated: Each inspector will have limited inspections during a specific day, will be flexible each day and controlled by the application. Program will identify and skip holidays, days off and inactive inspector. Program must allow plete audit trail of all transaction dates, time, users, and workstation ID A calendar on the forms screen to allow user the pick a date, if available, text range on screen is acceptable also Allow the user to schedule an inspection for the first available date after a specific date All tables will allow adding, searching, modifying and deleting records from the same screen All drop down menus must allow data entry to add more items without exiting the screen Goals and ObjectivesThe goals of this project is to replace the current antiquated system that is being used to schedule building inspections. Our objective is to allow scheduling to be done in a more orderly, and simple fashion with future scheduling being a simple thing to do. The current system that is in place does not allow for inspections to be scheduled to far in advance. We hope