The tasks of resource management are: analyzing the requirements of these resources, assessing their availability, monitoring the production and supply of the right resources to the right places at the right time to meet any shortfall in resources to ensure production stable etc. DATABASE DESIGN FOR RESOURCE MANAGEMENT - A CASE STUDY 2.1 Resource Management in an Industry: A Case Study 2.2 Software Requirements Analysis.
Computer Aided Resource Management
The bank's branch name, account number, the name of the account holder and the balance. 34;Balance" indicates the account balance of all customers registered here. There are some problems that may occur during data .. representation due to a large number of attributes in a table.
Design methods of relational database
Actually, ER chart gives the relationship between the entities but bubble chart method gives relationship at attribute level. The operation sequence of Relational database design using bubble diagram is depicted.
DATA BASE DESIGN FOR RESOURCE MANAGEMENT -- A CASE STUDY
Software requirement analysis
The Procurement Department, after completing all the necessary procurement formalities, sends the procurement order to the supplier. i) Procurement order no. and the date. ii) List of items to be procured under this procurement order and expected arrival date, delivery method etc. iii) Name, Address, etc. of the supplier. Relational Table - MaterialLookUp Contains the primary key of the material entity (Part No.) and the primary key of the database Pseudo Party (File Name) of that item's part list.
Development of algorithm
If the user does not enter any data, the program will ask whether the user intends to leave the program or continue. If the user types the exit option, the program will exit and if the user wants to continue, ~,d11 will appear on the screen again to open!' product part number. If the part number does not exist, the program displays an error message and gives the user a chance to correct it.
If not found, the program will issue an error message and the user will be given back the entered part number for correction. Then the program will do something for the next operation - ie. in the new item database file it will count how many quantities of this item are ordered under the same order. If the entered quantity is less than or equal to zero, the program generates an error message and asks the user whether he intends to exit or not.
If the quantity entered is more than the quantity ordered by the customer, an error message will be generated .. and the user will get the screen to correct the quantity.. e) When the quantity is valid, the Program will ask for the list file of its parts. And when found, the program will keep an empty temporary file ready to receive the items that will be "called" from the store to produce this item. Then the program will ask to enter the target date by which the production department should finish the production. f) After entering if the target date, the program starts its operation in "callout".
FLOW-DIAGRAM FOR NEW ENTRY OF PRODUCTION ORDER
You can do this by displaying all relevant records and asking the user to select the record to update. All relevant data of different database files should be updated at the same time to avoid data inconsistency. The program first displays 10 records no. orders" (or less if end of file encountered) from the procurement order file and asks the user to select which order to update. If the user enters a record number, ne)rt 10 records (or less) will be displayed and the program will ask the user to select a record to update and so on.
If the user does not select any record and end of file, the program is terminated. If the user selects and if the selection is out of range, an error message will be displayed and request a reselection". If the selection is correct, the program will display 10 records (or less) of the order of items under the selected order number from the subject of the public procurement and the user will be prompted, to select the record to update.
And if it is not less than zero, the user will be prompted to update the expected arrival date. And if it is not less than zero users' it will be asked to update the status. After entering the status, the program will be set to update the next record (if any) with the same procedure. h) When all data is updated, calculate the total quantity (Q2) of these items according to this order in the procurement status file. i) If 01=Q2, the update operation is completed. j) If 01<02, "err" or message will be given and the user will be prompted to once again update the quantity of all those procurement status file records.
FLOW-DIAGRAM FOR UPDATE OPERATION OF PROCUREMENT ORDER
If he does not agree to add registration, he will be asked to update quantity as described in j). If the quantity entered is less than or equal to zero, an error message will be given and the user must re-enter the quantity. If the entered quantity is greater" than (01-02), an error message will be given and correction will be the consequence.
After entering a new quantity, 01 new quantity is added (01=01+ new quantity) the user is prompted to enter the status. For example, when a parts list needs to be printed, the database provides the parts list and quantity. The program at 1st creates an empty temporary base acta file and the program starts by entering the part number on the screen, and the user has to enter the part number of the item for which the material requirement calculation and report generation is required.
If it is not found in the material file, an error message is given and the user must correct the part number. If the quantity is less than or equal to zero, an error message is displayed and the user is given the option to exit. And if not, he will be given the opportunity to re-enter the quantity. d) When the quantity is entered correctly, the program will search for.
FLOW-DIAGRAM FOR GENERATION OF MATERIAL REQUIREMENT REPORT
If empty, the program will terminate after giving a message. f) When there are some records in partlist file, fetch the 1st record. If it has a parts list, user Idll is asked whether or not further component breakdown is required. i). When there is no parts list of an item or breakdown of parts list is not desired or parts list has no records, the part number and total quantity thereof required to manufacture, the items must be entered into the temporary database. h).
If there is no longer a record in the BOM, check to see if there is a previous BOM from which the program jumped to this BOM. If it exists, the next record of that record of the parts list from which the program jumped is retrieved and continued as f). J). If there is no BOM from which the program jumped to this program, it means the end of the material calculation.
Fig.-23 shows the generic query report flow diagram. a) When a certain query type is selected, the program will display the fields (or database attributes) for selection - which fields will be printed in the report. The user must have adequate knowledge of dBase III+ query syntax. d) When the query condition is entered, the user will choose to print it or not. Otherwise, the program will be terminated. e) When the print option is selected, the program will prompt the user to prepare the printer with paper. f) The program then prints a formatted report.
FLOW-DIAGRAM FOR QUERY REPORT GENERATION
In edit operation user gets access to all available data to edit while in update operation user gets access to only few data fields to edit. Editing parts list is an example of editing operation and its algorithm and flow chart are written below. All other flow charts are given in Appendix-A. Fig-24 shows the flow diagram for editing parts list. a) At the beginning, the program displays 10 records or less (if the end of file is encountered) from the material lookup table and prompts the user to select any record.
If the user selects add option, the next operational sequence will be as (K) written later. d) When the edit option is selected, 10 entries from the selected sublist will be displayed and the user must select an entry to edit. The display and selection method is similar to (a) to (b). e) Once an entry is correctly selected from the part list, the user will access the part number to edit it. If he enters blank, the record will be deleted from the database. f) If it is not empty, the program will check the existence of this part number in the material database file.
If not found, the user is given the option to enter this new item in the material base file or correct the newly entered part number. h). If the user chooses to enter this item in the material database, the user must enter its tag and then this part will be attached to the material database. i) Then the user edits the quantity. If the quantity entered is less than zero, an error message is displayed and the user must correct a new entry.
FLOW-DIAGRAM FOR EDIT OPERATION ON PART LIST
- Feature of Package
- CONCLUSION
- RECOMMENDATION FOR FUTURE WORK
The next step will be like r). k).If the user chooses to add data, enter the part number. If the user chooses to enter it in the material file, he must enter the designation and it will then be added to the material file. p) Then the user enters the quantity. If the quantity is less than zero, an error message is displayed and the user must correct it.
When he enters the correct password, he will gain access to the database up to Primary keys, generally tens of thousands of characters long, where the code will be a maximum of 5 characters (for a maximum of 100,000 records). For example, the item no. a primary key used in many files and is 18. eighteen~n) characters long and is replaced by 5-digit code. Databases for all these systems can be designed separately and can be added to them with the database of the resource management database to make an integrated database system.
Distributed database is a collection of data that logically belongs to the same system, but is distributed over the site of a computer network. LOGICAL CO-RELATION i.e. the fact that the data have certain characteristics that bind them together, so that the distributed database can be distinguished. The separate databases like resource management database, payroll database, inventory database, etc.
EOF?
FLOW-DIAGRAM FOR NEW ENTRY OF PROCUREMENT ORDER
CLOSE ALL CREATE CREATE BACK ENDIF CREATE DONE GO BONA sl&b=RECNO() cn&b=MCode q=q8:b*qty.
