Example: air traffic controller

Proposed Design of an Inventory Database System at …

Proposed Design of an Inventory Database System at Process research ORTECH System Design Prepared by Andrew Ramadeen Manojav Sridhar Kunendran Deivendran Junaid Yousuf Monday, April 16, 2001 2 5 Identifying the 5 Requirements .. 6 Functional Requirements ..6 Nonfunctional Requirements ..7 Design Phase .. 8 1. Global System 8 Networking .. 9 Software Platform .. 9 10 Network LAN .. 10 Software MS Windows and MS 10 2. Diagrammatic State Diagrams .. 12 Activity Diagrams .. 13 E-R Diagram .. 14 3. Software Architecture ..16 Three-Tier Design .. 16 Repository-Based Design .. 16 4. Database 5. User Interface Design ..20 Conclusions .. 22 Appendix 1.

privatized company that was part of a large government research organization called ORTECH. PRO is part of the Metallurgy and Materials science research ... 300 MB hard disk space c. 256 MB RAM d. 10Base-T Network Interface Card e. Laser Printer ... labs and work areas, thus there is no need to purchase more.

Tags:

  Research, Database, System, Inventory, Labs, Inventory database system at

Information

Domain:

Source:

Link to this page:

Please notify us if you found a problem with this document:

Other abuse

Transcription of Proposed Design of an Inventory Database System at …

1 Proposed Design of an Inventory Database System at Process research ORTECH System Design Prepared by Andrew Ramadeen Manojav Sridhar Kunendran Deivendran Junaid Yousuf Monday, April 16, 2001 2 5 Identifying the 5 Requirements .. 6 Functional Requirements ..6 Nonfunctional Requirements ..7 Design Phase .. 8 1. Global System 8 Networking .. 9 Software Platform .. 9 10 Network LAN .. 10 Software MS Windows and MS 10 2. Diagrammatic State Diagrams .. 12 Activity Diagrams .. 13 E-R Diagram .. 14 3. Software Architecture ..16 Three-Tier Design .. 16 Repository-Based Design .. 16 4. Database 5. User Interface Design ..20 Conclusions .. 22 Appendix 1.

2 24 Brainstorming Session 1 March 27th Appendix 2 .. 25 Explanation of Appendices March 27th 2001 ..25 Appendix 3 .. 26 Organizational Chart March 27th Appendix 4 .. 27 PRO Inventory System Flow Chart March 27th Appendix 5 .. 29 Functional Requirements March 27th I. Details of data storage .. 31 II. Details of 31 III. Details of 32 IV. Details of Information Processing .. 32 Appendix 6 .. 33 Non-functional Requirements March 27th 2001 ..33 1. Software 34 2. Hardware Requirements .. 34 3. Security Requirements .. 34 4. Reliability/Survivability Requirements .. 34 5. Interface Requirements .. 35 6. Lifecycle Requirements .. 35 7. Economic Requirements .. 35 Appendix 7.

3 36 3 Brainstorming Session 2 March 29th Appendix 8 .. 37 Information Gathering Summary March 30th Appendix 9 .. 38 Current Computing Capabilities March 30th 1. Server Computer - (Glass box) .. 38 2. Client Computer(s) - (Glass box) .. 38 3. Networking Components .. 39 4. Software Licenses .. 39 Appendix 10 .. 41 Hardware Considerations April 1st 2001 ..41 Appendix 11 .. 43 Network Considerations April 1st 2001 ..43 Appendix 12 .. 44 Software Platform Considerations April 1st 2001 ..44 Appendix 13 .. 45 Global System Architecture Conclusions April 3rd 2001 ..45 45 Network LAN .. 45 Software MS Windows and MS 45 Appendix 14 .. 46 Explanation of Diagrams April 5th 2001.

4 46 Appendix 15 .. 47 Class Diagram for Inventory System April 5th 2001 ..47 Class Staff Member ..47 Class Office Staff .. 47 Class Technical Staff .. 47 Class Upper Management .. 48 Class Reports .. 48 Class Order 48 Class Order .. 48 Class Inventory .. 48 Class Inventory Item .. 49 Class Project .. 49 Appendix 16 .. 51 Inventory Item State Diagram April 7th Appendix 17 .. 52 Office Staff Activity Diagram April 7th Appendix 18 .. 53 Order Table State Diagram April 7th 2001 ..53 Appendix 19 .. 55 Project State Diagram April 7th 2001 ..55 Appendix 20 .. 56 Technical Staff Activity Diagram April 7th Appendix 21 .. 57 ER Diagram April 8th Data Business Constraints.

5 60 Derivations .. 60 Appendix 22 .. 61 Software Architecture April 10th 2001 ..61 Architecture Selection .. 61 Repository-Based Design .. 62 Appendix 23 .. 64 Software Design : Systems and Subsystems April 10th 2001 ..64 Main System .. 64 Subsystems .. 64 65 Appendix 24 .. 66 Database Architecture April 11th Appendix 25 .. 67 Database Design Analysis April 11th 2001 ..67 Table of Operations .. 68 Table of Accesses, with 68 Appendix 26 .. 73 Schema Translation and the Relational Model April 13th 2001 ..73 Appendix 27 .. 74 Appendix 27 .. 75 User Interface Design April 13th Appendix 28 .. 78 Screen Designs April 11th 2001 ..78 Searching .. 78 Project Administration.

6 80 Inventory Administration ..81 Employee Administration .. 82 Ordering .. 83 Appendix 29 .. 84 Work Division ..84 5 Introduction The Company we are studying is Process research ORTECH (PRO), a newly privatized company that was part of a large government research organization called ORTECH. PRO is part of the Metallurgy and Materials science research industry. They are a small organization with about 20 employees. Most of the work done at PRO is of a contract nature. When a client company approaches them and presents them with a problem, they analyze the problem and try to solve it on a small scale in their laboratories.

7 If the problem is solved successfully and in a cost-effective manner, this solution is sold to the client for a negotiated price. Even though the organization is not a large one, the information that is required to carry out the research is enormous. PRO has a simple management structure. There is a board of directors who advise a company president. Under the president are scientific and office managers who oversee day-to-day operations of the company. And under them are the various scientists and office staff who do the experiments and run the front office. See Appendix 3 for an organizational chart. Identifying the Problem There are many steps involved in the process of solving a client s problem.

8 The steps involve billing the client, purchasing materials, checking Inventory and so on. Due to the rapid growth of the company, many standard procedures used to perform these tasks are becoming insufficient to meet the needs of the company and their clients. We have already carried out a Feasibility Study and a Requirements Analysis at PRO and determined that one of the areas that needs the greatest attention is the Inventory System . The management agrees that this area of their business requires immediate attention and they are actually considering the conclusions of our Feasibility Study. The System was originally designed for a much smaller workforce, but with recent growth and workforce expansion, the System has become inadequate, thus impeding efficiency.

9 This has resulted in relatively large project delays, Inventory wastage and increased cost of maintaining the legacy System . For a complete description on the current System , please refer to Appendix 4. 6 Requirements The first stage in designing a solution to this problem is to determine the requirements of the new System . A complete analysis was performed and documented in the Requirements Analysis document released March 12, 2001. What follows below is the list of functional and non-functional requirements for the new System generated by that study. For a description of each item, please refer to Appendices 5 and 6.

10 Functional Requirements I. Details of data storage a. Inventory Items i. Name ii. Location iii. Usage 1. Dates of usage 2. Projects usage 3. Personnel usage 4. Amounts of usage iv. Date of Order v. Expiry date vi. Cost of item b. Scientists names i. Projects they are working on ii. Current orders they have placed c. Projects names i. Materials needed ii. Project start date iii. Project finish date iv. Supervisor II. Details of output a. Inventory list screen b. Add new item screen c. Remove item screen d. Check availability screen e. Check location screen f. Check-out item screen g. Update item screen h. Place order screen i.