Computer Resource Management System

ABSTRACTABSTRACT Computer Resource Management System (CRMS) is a total management and informative system, which provides the up-to date information of all the computer resources in the company. CRMS helps the company to overcome it’s difficulty in tracking the resources of the company by presenting the customized reports, which helps in effective and timely utilization of the hardware and the software resources. CRMS is a web-based application using the three-tire architecture. The ability to handle the multi-user environment and the maintaining the highest security for the access are some of the features of this application. CRMS uses Oracle 8i as the back end for the database and uses all its features offered in the web based technology for its transactions. CRMS uses the Enterprise Java Beans as the middle ware for its business logic implementation. It uses the Weblogic Server , Version 5.1 provided by the BEA Solutions. INTORDUCTION INTORDUCTION: Computer Resource Management System (CRMS) is a total management and informative system, which provides the up-to date information of all the computer resources in the company. CRMS helps the company to overcome it’s difficulty in tracking the resources of the company by presenting the customized reports, which helps in effective and timely utilization of the hardware and the software resources. Computer Resource Management System uses the Enterprise JavaBeans Version 1.1, it’s the component model for the enterprise applications. Enterprise JavaBeans combines server-side components with distributed object technologies such as Java RMI to greatly simplify the task of application development. The EJB automatically takes into account many of the requirements of business systems: security, resource pooling, persistence, concurrency and transactional integrity. One of java’s most important features is platform independence. Since it was released, Java has been marketed as “write once, run anywhere”. Enterprise JavaBeans is not only platform independent –it’s also implementation independent. Its like JDBC API runs on a Windows machine or on a Unix machine, it can access any vendor’s relational database that has a JDBC driver. Ideally, an Enterprise JavaBeans component, an enterprise bean, can run in any application server that implements the Enterprise JavaBeans (EJB) specification. That is we can develop and deploy EJB business system in one server, such as BEA’s Weblogic and later move it to a different EJB server, such as IBM’s WebSphere or Gemstone/J. Implementation independence means that a business components are not dependent on the brand of server. The ACID properties are nothing but (Atomic Consistent Isolated Durable) properties A transaction to be atomic. Search / View 1.e. Recycle Bin 5. Status 6. consistency is ensured by seeing that a transaction is atomic. Durability means that all the data changes made during the course of a transaction must be written to some type of physical storage before the transaction is successfully completed.. Oracle 8i perfectly handles the ACID Transactions. The computer resource management system mainly consists the following : 1.Computer Resource Management System uses Oracle 8i as the back-end RDBMS. isolated and durable. i. Components 2. Oracle 8i is actually a fully Internet supported database system. A transaction is the execution of a unit-of-work that accesses one or more shared resources. Bin 4. And apart from handling the ACID properties Oracle 8i has higher security level and web compatibility features. it must execute completely or not at all. Components : . Isolated refers to allowing a transaction to execute without interference from other processes or transactions. Computers 3. the data that a transaction accesses can not be affected by any other part of the system until the transaction or unit-of work is completed. A unit-of-work is a set of activities that relate to each other and must be completed together. This ensures that the changes are not lost if the system crashes. Consistency refers to the integrity of the underlying data store. usually databases. Every computer should be given a unique number. 6. 4. . Bin : The damaged components. bin. The status gives the present position of the component where it is situated in the organization. Search / View : The users can search or view the information of different resources based on their unique number given to them. For every component appropriate entry should be made. which are not repairable or replaceable. standalone’s and clients etc. Whatever goes out will be deducted from the shelf and must be entered either to bin. 3.Whatever the component that is either software or hardware will be assigned a unique number and entered into the shelf. recycle bin or to a computer. Computers : Computers will be assembled using the shelf parts. recycle bin. Basing on the status the components are used in different transactions. computers. 5. will be sent to this bin. Status : The status gives the statistics of the shelf. 2. Recycle Bin : The repairable and replaceable parts will be kept here. A time report is given like when a part is submitted for repairs or replacement and expected back time and able to give warnings of delays etc. The computers may be servers. The details of the computer will be entered including its hardware and software profiles with their parts. PROBLEM DESCRIPTION . which can be of great help to all the administrators.  In the present system there is no security for the details of the resources as any user who is not authenticated to view the records may see them. to know the current status of the resources. The problem of maintaining the bulk database can be solved by atomizing the resources in the organization. which is not so easy when done manually. as of now it is being done manually which consumes a great bit of manpower and the process is time consuming.PROBLEM DESCRIPTION As of now the resource management in Laila Infotech is done manually. If an employee intends to know the information regarding the resources pertaining to computers or components and their present and accurate information in the organization.  The Manager has to wait for the manual reports from the development dept.  The users of the organization require various reports to be generated in an easy format. employee and the management members. Some of the frequent occurring problems in the present manual system are as follows:  Finding the current status or position of a component in the organization is a time-consuming process. can be done only by a manual checking of that computer for the hardware and software components is a tedious process. .  The Manager may get problems in finding out a user details in hundreds of records.  To view the details of a computer and to know what are the components that are assigned to it. Visual Basic guaranties for the faster query processing thus we are satisfied with Visual Basic itself supporting in this direction. The computerization helps the users a lot.  Checking the uniqueness wherever it is required. The user can get information in desired manner. BENEFITS OF COMPUTERIZATION OF PROPOSED SYSTEM: A computer based information system is usually needed for the following purposes. Better Accuracy and Improved Consistency: The computer carries out computing steps including arithmetic accurately and consistently from which really human is escaped which yields more fatigue and boredom. Cost Reduction: . One way to overcome all these difficulties is so store all the information in the computer. retrieve data with greater speed than that of the human doing we can get results in less time. sort.  Providing security is also difficult. This also restricts the users to enter invalid data and reduces the burden on the user. Greater Processing Speed: Using computers inherent ability to calculate. components and computers at single or multiple locations give raise to many problems like :  Difficulty in retrieval of data in desired manner. Data retrieval is also easy and fast.NEED FOR COMPUTERISATION: Maintaining the information regarding all employees.  Availability of information in this manner is subjected to damage.  To provide the necessary reports to various users in time.Using computerization we can do the required operations with lower cost than any other methods.  To provide a user authentication and different interface depending upon the type of user logged in  To provide maximum level of security for the data. Hence by computerization we can reduce the cost drastically. . OBJECTIVES OF STUDY: The main objectives of this study are as follows:  The main objective of Computer Resource Management System is to provide an automated system to maintain the resources of the company.  To provide an user friendly and multi-user interface for handling the application. These are the main objectives of the Computer Resource Management System. . SYSTEM ANALYSIS . lailainfotech. Behavioral feasible studies. glossary of terms are prepared. Information Gathering: Information relevant to the “Computer Resource Management System” of Laila Infotech is collected from the Laila Infotech Limited and the finance department of the company.4. . To do feasible study we have to do the Economic. SYSTEM ANALYSIS System Planning is one of the important items to be considered before actually beginning the project. quality and validation activities. Preliminary estimates of the computing resources required to operate and maintain the system are developed. In the process of the System Planning various phase-dependent tools. The information regarding company activities is gathered from the company’s website www. Preliminary cost estimates for the system development and preliminary development schedules are established. techniques and notations are determined.com. configuration management. Technical. Feasibility Study: An initial investigation culminates in a proposal that determines whether an alternative system is feasible than the present candidate system. Planning is performed on the issued like defining Life Cycle Model and an organizational structure project. Hence our candidate system production is behaviorally feasible. easy to learn how to work with and there is also not much resistant to this package from the staff side also. 2. As the company is basically a development center it will be very easy for the employees of the company to learn about the developed candidate system. 3.Behavioural Feasibility: People are inherently resistant to change. Our candidate system is developed in such a way that it is very user friendly.Economic Feasibility: It is the most frequently used method for evaluating the effectiveness of a system. In this project “Computer Resource Management System”. .Technical Feasibility: Technical feasibility centers around the existing computer system (software/hardware) configuration and good software facilities in such a way that any new candidate system can be implemented without a large alteration of the lab nut with slight modification of the existing system. Hence our candidate system production is economically feasible. As the company itself is a development center all the resources are in the company itself and no extra cost is spent for Computer Resource Management System. It is also called as cost/benefit analysis. for the development of the candidate system the cost that have to spend is the computer resources like the required software and hardware that supports the software in an effective and efficient manner and the money to be paid to the developers. Hence our candidate system production is technically feasible.1. Master Administrator: Has all the privileges of creating and deleting all type users. which provides the up-to date information of all the computer resources in the company. 4.1. SYSTEM DESCRIPTION 4. . There are four types of users. component models. The administrator can also search on shelves. users and computers. Recycle-Bin.4.1. Purchase Manger: Is the responsible person to buy the parts from the external vendors and keep them in the shelf. locations and computers).1 Hierarchy of Users The hierarchy of the system is maintained by the privileges to access the system. Hardware Administrator: Will be having the privilege of moving the components between various modules (shelves. for moving the components from one location to another and also for changing the designation of a particular user.1 About Computer Resource Management System Computer Resource Management System (CRMS) is a total management and informative system. He periodically views and updates the shelf.2 Functional Requirements Specification 4. Bin. Bin and Recycle-Bin.1.1. He can create and delete computers.2. shelves. Normal User: Has only the privileges of viewing and searching the site for the information about the resources or the other users. locations. He also has the privilege to change his password.  For master administrator. creation and deletion of computers is provided. moving the shelves from one location to another. Bin and recycle-Bin  For the normal users. locations.  For Purchase Manager provision for viewing and updating the shelf. shelves. . location and components. moving the components between various modules.2. provision for searching on usernames.4.  For hardware administrator provision for viewing and editing the components.2 High Level Functional Requirements  Provides the Interface for users. editing the components and changing the designation of users is provided. purchase manager and administrators to login.1. provision of creating and deleting the users. wherever they were installed along with Key-numbers. Computers: The Computers assembled from shelf parts are maintained with unique numbers and each computer has the hardware profile and software profile. . Software: All the purchased software should be assigned to computers. which searches the system on various search criteria’s. And whatever goes out will be deducted form the shelf and must be entered in the Bin.2. Bin. Recycle-Bin. Recycle-Bin or to a Computer. PRODUCT SCOPE AND FUNCTIONAL SPECIFICATIONS 4. Bin: When a component is irreparably damaged then the component is placed into Bin. Recycle-Bin: The reparable and replaceable parts will be assigned to Recycle-Bin. In the Computer Resource Management System the main modules are as follows. Status: The status gives the statistics of the Shelf. Computers and the exchanged parts from one system to another system.1 Scope: The functional scope of Computer Resource Management System is to provide a userfriendly management system for resources as well as to give a search engine. This module has the time report like when a part is submitted and what is the expected back.2.time. Shelf: Whatever comes into the company either software or hardware will be placed in the shelf and each product is given a unique id with all the other details.4. Bin.Search: The Search will be on product name.  The hardware administrator assembles various parts and updates the shelf.  The normal user will be created by the master administrator with the userid and password. shelf. software and Recycle-Bin. component wise. editing the components. location wise and user wise. Bin and Recycle-Bin after taking the necessary action. The search can also be on user name and location. The user will have the privilege to change the password and the user can do the search operation. product code. manufacture-name and on computer number. The following functional activities are considered for executing the project. . computers.  The master administrator apart from doing all the activities of other users. assigning the components to a shelf and moving the shelves form one location to other besides having the privilege to change the designation of the users. creates and deletes a user. location.  Purchase manager will update the shelf.  Present status – Total computers.  User wise / Location wise – All the users in the specified location with full profile. idle status. Database: The Computer Resource Management System application has the JDBCODBC connectivity. The Oracle 8i is chosen for Computer Resource Management System because of higher security level and web compatibility features offered by it. Will be generated based on a date specified by user or between two particular dates.Reports should be generated on the current status and every report will be accountable to the Administrators.Will be generated based on a date specified by user or between two particular dates. Will be generated based on a date specified by user.Bin wise.  Bin wise – To the Purchase manager and both administrators. which is provided to interface with Oracle 8i database. Will be generated based on a date specified by user.  Recycle. present working. . cause for idle status. 2. (EJB)  Client Side Application Software: Java Script. HTML  Data Base: Oracle 8i The system requires Oracle as a database.  Dream Weaver 3. however the system will be ODBC complaint to work on any standard database.2.2.7 The system requires Internet Explorer or Netscape Navigator browser for client side.0/JRUN4.0s The system will be developed with Java Technologies using J2SE (JDK and JRE).0 or Netscape Navigator 4. Dream Weaver 3. ..  Client Browsers: Internet Explorer 5. JRUN for rapid development tools for Servlet and JSP editing.2.1 Development Environment  Operating System: Windows NT\98 The system will be built on windows compatible environment.0\Front Page 2000\98 as HTML editor. The application will be web based using Java technology  Web Server: BEA ‘s Weblogic Web Server to serve as Servlet\JSP engine.4. The system requires weblogic Web Server for serving the requests with Servlet Exec.  Server side Application Software: Java Server Pages (JSP)  Business Logic Software: Enterprise Java Beans. Software and hardware requirements 4.  Dream Weaver 3.  Server side Application Software: JSP Client Side Application Software: Java Script. Hardware: Pentium PCs with 128 MB RAM/ 20 GB HDD. Dream Weaver 3.2 Production Environment  Operating System: Windows NT/98 The system will be built on windows compatible environment.  Data Base: Oracle 8i The system requires Oracle as a database.  Web Server: BEA ‘s Weblogic Server to serve as Servlet\JSP engine.0/JRUN4.0\Front Page 2000\98 as HTML editor.2.. The application will be web based using Java technology. however the system will be ODBC complaint to work on any standard database.2. 4.0 and above Netscape Navigator 4.0s The system will be developed with Java Technologies using J2SE (JDK and JRE). HTML.  Client Browsers: Internet Explorer 4. . JRUN for rapid development tools for Servlet and JSP editing. The system requires weblogic Web Server for serving the requests with Servlet Exec.0 and above The system requires Internet Explorer or Netscape Navigator browser for client side. . Normal user Setup: An Interface will be provided for user to login. 4.3. Hardware Administrator Setup: The Hardware administrator will be provided with the following interfaces. 4.3. Bin and Recycle.  An interface for editing the shelves. computers.2. Hardware: Pentium PCs with 128 MB RAM/ 20 GB HDD. computers and components.Bin will be provided.2. 4.2 Purchase Manager Setup:  An interface for viewing the shelves.2.  An interface for Creation and deletion of Normal users.3. editing the component models. Functional Specifications 4. Bin and Recycle-Bin will be provided.2.  Provision will be made for changing the password.1.3. The user can login into the system by entering a valid userID and password with the location.  A provision will be made by which the user can search for the other users.3.  An interface to view all the users. computers and shelf unassigned.4.2.2. Hardware Administrators and other master administrators.3. display of component model and computers.  An interface for creation and deletion of Purchase managers. there are  Hardware wise report and  Software wise report.3.5. Master Administrator Setup: Apart from doing all the activities of Hardware Administrator. locations.  Interface for assigning components to a computer from the shelf. 4. shelves 4.  Interface for moving components between Bin. Reports: An interface is created for viewing the reports on  Based on user and Location wise – This report can be again categorized into two types  Report on a particular user and  Report on users in a department. . master administrator has the following additional interfaces.  An interface for creation and deletion of new location. shelves with components. recycle-Bin.  Shelf wise – The availability of components is given in this report. 2.3. Recycle – Bin and on Shelf.  Date wise – In the date wise report the reports will be generated on particular date. the two type of reports are  A report on the full hardware and software profile of a computer and  The report on the current status of the computer  Component wise – The report based on a particular component. These reports will be generated on the Bin. 4. User functions are not permitted through the nonadministrative network ports. Securing the Web Data: Appropriate security Features will be provided for protecting the web data. Status of the computer – This report gives the current status of the component.6. 1. .2. Database is password protected. Administrative functions will be kept separate from user functions. between two particular dates. All administrative functions will be performed only on the administrative network port. 1 Physical Architecture Model .2.3.2.3.4.7 COMPUTER RESOURCE MANAGEMENT SYSTEM ARCHITECTURE 4.7. 7. Most of the middle-level Java objects will be here Web Interface Layer in application layer. triggers. It contains the web pages (JSPs) of the application which will interact with the front-end browsers .3. Contains the objects addressing the business logic.4. It will be on the web server. etc.2 Layered Architecture Database Layer Contains the data and database-related objects like Application Layer stored procedures. packages.2. 1 High Level DFD: LocID Location 1 Users User Profile User Authentication USER ID AND PASSWORD 2 Master Administrator Setup 5 Normal User Setup 4 Purchase Manager 3 Hardware Administrator Setup .Client Layer Contains the web browser which interacts with web server 4.3 DATAFLOW DIAGRAMS 4.3. 3.4.1 2 User Details Creating and Deleting Users 2.2 Locations Creating and Deletion of Locations Location Details 3 All Reports of HW-Admin REPORTS Location wise User wise .2 Master Administrator DFD: User Profile 2. Computer HW and SW profile 3.4.3.1 Search on Computer.1 3 4. RecycleBin and Component 3.4 Purchase Manager DFD: Bin & Recycle Bin Component Master . Bin.3 Hardware Administrator DFD: 3.2 Creation and deletion of Computer Computer Master. Computer HW and SW profile REPORTS Computer Master.3 Bin Recycle Bin Moving Components REPORTS All Reports of PM Computer wise Component wise Date Wise 4.3. 5 Normal User DFD: Normal User 5.1 Manager Component HW and SW Profile Search On Bin. Recycle Bin and Component REPORTS 4. Recycle Bin Component if it is in Shelf Bin Recycle Bin Bin Wise REPORTS Component in Shelf Recycle Bin Wise 4.1 .3.2 Edit Bin.4 4. 2 Location Search On User.3.5 Password User Profile Change Password User Profile Figure 1 5. Computer Component Computer Master Component Master 4.1 Change Password User id or password not found Error Messag e .6 LOW LEVEL DFD’s: Change Password DFD User Profile User User details New Password 5. 2. User Search On Users 5.1 5.2 On Component Computers 5. Computers and Components.New Password User Search on Users.2.2.1 5.1 Users Getting Location details Search On Users Location ID Location Location ID .2 Search Operation Users Search On Computers Search 5.3 Component Search On Users DFD: User ID User ID User Profile User Details Location ID 5.2.1.2. 2 Error Search 5. Hardware And Software Profile Component ID 5.2.Location Result Users Search On Computers DFD: Users Computer Master Computer Details Computer ID 5.2.2.1 Error Processing Users Error Messages .1 On Computers Error Processing Computer Details Error Message Users Search On Components DFD: Users Component Master.3 Component Details Search LocID On Components Component Not found Location Location Component Details 5.2.3.2. 1. RecycleBin and Component in Shelf 4.1 Search on Bin.2 Recycle Bin 4. Components in Shelf DFD: User 4.Search on Bin.1. RecycleBin.3 Component in Shelf Search On Bin DFD: .1 Bin 4.1. HW&SW Profile Purchase Manager Component ID Component ID Error .1 Search On Recycle Bin 4.1.1.Bin Purchase Manager BSno Record Details Error 4.1.1 Error Processing Result Error Message Purchase Manager Search On Recycle Bin DFD: Recycle Bin Purchase Manager Error RBSno Record Details 4.1.1 Search On Bin 4.1.1 Error Processing Result Error Message Purchase Manager Search On Component DFD: Component Master.1. 2.2 Delete Record BSno Bin Error .1 Purchase Manager Add Record BSno and Other 4.2 Recycle Bin 4.Record Details 4. Components in Shelf DFD: 4.2.1. RecycleBin.2.1 Error Processing Result Error Message Purchase Manager Edit Bin.1.1.1 Search On Recycle Bin 4.2.2 Edit Bin.2.3 Component in Shelf Edit Bin DFD: 4.1. RecycleBin and Component in Shelf 4.1 Bin 4.1. 2.2.1.2.2.4 Error Processing Modify Record Purchase Manager Message .4 Error Processing Modify Record Purchase Manager Message Edit Recycle Bin DFD: 4.3 and Error RBSno and New Details 4.BSno and New Details 4.2.2.1.2 RecycleBin RBSno Delete Record 4.1 RBSno Add Record Purchase Manager Other Details 4.2.3 4.2.2.2. 3 .2.3 Modify Record If Status is Shelf CID HW&SW Profile Error CID and New Details 4.1 Add Record Purchase Manager CID and Other Details 4.Edit Component DFD: 4.1 Creation of Computer Computer Master 3.2.4 Error Processing Purchase Manager Message Creation and Deletion of Computers DFD: Hardware Administrator 3. Delete Record If Status is Shelf 4.2.2.2.2 Deletion of Computers 3.2.2.2.2 Component Master.2.2. 3 Moving Components 3.3.1 Purchase Manager B/W Shelf and Computer 3.2 CID Update Status Remove CID Add Rec 3.3.3.3 Update Status Computer HW or SW Profile Profile Bin Component Computer HW or Software SW Profile Add Rec Or Remove or Software HW B/W Computer and Recycle Bin 4.4 E / R Diagrams: Component HW Computer To Bin Computer HW or Software Profile Profile RecycleBin or .Move Components Moving Components DFD: Update Status Component HW or Software Profile 3. Location – User_prof – Component – Computer : LocID UserID Password LocName Locations 1 M LocI D Users LocAdd FNam e 1 CmpID CmtID M Cmt_master M Cmp_master CmtTyp e CmpNam e Status Cmt_master– Cmt_swprof – Cmt_hwprof : AssBy . Cmt_Master 1 CmtID 1 Cmt_swprof Version SerialN o 1 Cmtswsn Cmt_hwprof o ModelN o Warexp dt Cmthwsno . Cmt_master – Cmp_swprof – cmp_hwprof : CmtID 1 M Cmt_Master Cmp_swprof CmpSwSno 1 Cmp_hwprof CmpHwSno CmtID Cmp_master – Cmp_swprof – Cmp_hwprof : Cmp_Master 1 Cmpswpno 1 Cmp_swprof CmtID . 1 CmtID Cmphwpno 1 CmtID cmpswsno Cmp_hwprof Cmphwsn o Cmt_mast – Bin – Recycle Bin : . Cmt_Master 1 CmtID M Bin BinSno 1 CmtID RBin RBinSn o ExpRtD t CmtID DtOfEn t . SYSTEM DESIGN 5. SYSTEM DESIGN: . a “how to” approach to the creation a new system. logical design reviews the present physical system. Design is the bridge between system analysis and system implementation. This is composed of several steps. The design is a solution. Design states how to accomplish objectives determined in the analysis phase. The unnecessary fields should be avoided because it affects the storage areas of the system. prepare input and output specifications. the design should be made user friendly. The fields in the database table should define their role in the system. document oriented to programmers or database personnel. OBJECTIVES OF DESIGN System design is like a blue print for a building. System design is transition from a user oriented. The database tables are designed by analyzing various functions involved in the system and the format of the fields is also designed. It provides the understanding and procedural details necessary for implementing the system recommended in the feasibility study. and prepares a logical design walkthrough. Then in the input and the output screen design. . Care is to be taken to encode the lengthy names. The menu should be precise and compact. detail the implementation plan. it specifies all the features that are to be in the finished product.SYSTEM DESIGN phase follows system analysis phase. Design is maintaining a record proof design divisions and providing a blueprint for the implementation phase. Design goes through logical and physical stages of development. In this stage the logical design elements are specified which support the business activities.LOGICAL DESIGN The design of an information system produces the details that state how a system will meet the requirements identified during systems analysis. PHYSICAL DESIGN The process of developing program software is referred to as physical design. The physical design ensures the system features to meet the user requirements. This stage is login design. . a) Database Design: User_prof Table Location Table Cmp_Master Table PK UserID PK LocID PK UserName Password LocID (FK ) : : LocName Add1 City : : CmpName LocID (FK) CmpSwPno(UQ) CmpHwPno(UQ) : Cmt_Master Table Cmp_swprof PK PK CmtID CmtName CmtType LocID(FK) Status : : Cmpid CmpSwSno CmpSwPno(FK) CmtID(FK) LModOn LModBy : : Cmt_swprof Cmt_hwprof Cmp_hwprof PK CmpHwSno CmpHwPno(FK) CmtID(FK) LModOn LModBy : : Bin RBin PK CmtSwSno CmtID(FK) Version Serial No. Remarks : : PK CmtHwSno CmtID(FK) ModelNo WarExpDt : : PK BSno CmtID(FK) Complaint LModBy : : PK RBSno CmtID(FK) Complaint DtOfEnt : : . Software Component Profile Table.1. Location Table.6.1. Hardware Component Profile Table. 5. Computer Master Table.1. 1. Computer Software-Profile Table.1.2.1. 1. 1. 1. created by Master Password Administrator. Recycle Table.7.3. . 1.5.9.10. Column Name Description UserID A unique ID identifying a particular user.1. password.1. User Profile Table.1. User type and Designation etc. 1.1. A password created (at least 4 but not more than 15 characters) by the administrator and can be changed by the user.1. 1.2.1.5.1. 1. 1.8. Computer Hardware-Profile Table. Description of Entities Entity Name : User_Prof Table Description : This table is used to store the user information along with the User ID. Description of Tables 1. Component Master Table. Bin Table.4. City of the user. Default is ALL. State of the User. Address 1 of the user. for displaying all records . Will be LName used in the system for reports etc. Will be MName used in the system for reports etc. Will be Add1 used in the system for reports etc. Last Name of the user. Work Phone number Home Phone number Cell Phone number Fax number Email The Designation of the user.LocID FName To Which location the user belong First Name of the user. Country Pin PhWork PhHome Cell Fax Email Desig UserType Country of the User Pin Code of the user location. Last Name of the user. The user Created By who is Display specified. Add2 City State Address 2 of the user. Whether he is an master admin or hardware admin or purchase CreatedOn CreatedBy manager or normal user Date on which the user is created. The Name of the Location. Description : This table is used to store the locations of the company with the full address and other details. Country where the company is PhNumber CreatedBy CreatedOn located. City where the company is Country located. Description : This table is used to store the Component details like component id. for displaying all records Entity Name : Cmt_Master Table. Address 1 of the company. Company Phone Number The User ID of the creator The date when the location is Display created. Address 2 of the Company.Entity Name : Location Table. Default is ALL. Element Name LocID Description An unique Location id is LocName Add1 Add2 City assigned to each office. component type etc. Element Name CmtID Description A unique Component id is . The name of the manufacturer. The location of the component. The Status can be computer.. it has the details like model no.CmtName CmtType assigned to each component. The Name of the Component It can be either Hardware or Status Software type. The Component Id of the component. bin. . The date when purchased. The price of the component The name of the vendor. The User ID of the user who entered the component. Elemen Description t Nam e CmtHwSno An Auto number assigned to CmtID each component. manufacturer. Description : This table is used to store the hardware profile. Entity Name : Cmt_ HwProf Table. The Date when the component EntBy is entered. price etc. LocID CmtManuf CmtPrice CmtPurFrom CmtPurOn EntOn recycle-bin or shelf. manufacturer. Entity Name : Cmt_SwProfile Table. Description : This table is used to store the software profile of each component. The Date when the component EntBy first entered. price etc. The general remarks. Elemen Description t Nam e CmtSwSno An Auto number assigned to CmtID each software component. The dated when last modified. Default ALL. for Auto generation of cmthwsno. The User ID of the User who LModBy LModOn Remarks Display entered The user who lastly modified. it has the details like model no.. The Component Id of the .ModelNo The Model Number of the WarExDate hardware component The date when the warranty EntOn expires. The Date when the component LModBy first entered. The Location where the CmpSWPNo computer is situated. for Auto generation of cmtswsno. Default ALL. Element Name CmpID Description An Unique id given to each CmpName computer. The Computer hardware profile number assigned to each AssBy computer The User ID of the Hardware or master administrator . Description : This table is used to store the Computer profile of each computer. The version number The Serial Number of the s/w The Date in the Software.Version SerialNo SWDate LModOn component. Entity Name : Cmp_Master Table . The Name assigned to each LocID computer. The User ID of the User who Remarks Display entered The general remarks. it has the details like computer id. name etc. The Computer Software Profile Number assigned to each CmpHWPNo computer. . The general remarks. for Auto generation of cmphwsno. Default ALL. CmtHwSno etc. Sno CmpHwPno The Computer hardware profile CmtID number The Component id of the LModBy LModOn Remarks Display component. The user who lastly modified. The dated when last modified. The general remarks.LModOn The Date when the component LModBy first entered. Description : This table is used to store the hardware profile of each computer. The User ID of the User who AssOn Remarks Display entered The date when assembled. Default ALL. Entity Name : Cmp_HwProfile Table. for Auto generation of cmthwsno. it has the details like component id. Element Name CmpHw Description The unique number assigned. The dated when last modified. The Component id of the Complaint component. for Auto generation of cmpswsno. Element Name CmpSwSno CmpSwPno Description The unique number assigned. it has the details like component id. The user who lastly modified. CSSno etc. The user who lastly modified. Description : This table is used to store the details of the components that cannot be replaced. for Auto . The dated when last modified. Default ALL. The general remarks. Element Name BinSno Description The bin unique number assigned CmtID to each component. The Computer hardware profile CmtID number The Component id of the LModBy LModOn Remarks Display component.Entity Name : Cmp_SwProfile Table. The Description of the LModBy LModOn Remarks Display complaint. The general remarks. Description : This table is used to store the software profile of each computer. complaint etc. Default ALL. Entity Name : Bin Table . it has the details like component id. generation of BinSno.3. Administrators or Master administrator can login into the system using User Id and password. it has the details like component id. complaint. for Auto generation of RBinSno. The Description of the DtOfEnt complaint. The Actual Date when the LModBy LModOn Remarks Display component is returned The user who lastly modified. Description : This table is used to store the details of the components that can be replaced. return date etc. Default ALL. 3 TECHNICAL SPECIFICATIONS (USER INTERFACE DESIGN) 5. The general remarks. The dated when last modified. The date when the record is ExpRetDt entered. Entity Name : RBin Table . User authentication is .1 Login Module: Module Name: Login Module Functionality : The existing Users. 5. The Component id of the Complaint component. Element Name RBinSno CmtID Description The unique number assigned. The Date When the Component ActRetDate is required. done in the login screen. If the user enters the incorrect User Id or Password the corresponding error page is given. Purchase Managers. Module Type : Screen Input Parameters: Parameter Data type Mandatory Validation Name UserID (Length) Varchar2 (10) Y A UserID should be of at least 5 and not more than Password Varchar2 (15) Y 15 characters A Password of at least 5 but not more than 15 characters Screen Layout 1.2 Master Administrator Module: Module Name: Master Administrator Menu Functionality : In this module the Master Administrator can create. Bin or Recycle bin and he also assigns the Users and Administrators to different Locations. Login Screen 5. Computers and Shelf. delete and modify the Locations. Shelf. He can also assign the Components to Computers. He can also access the information of all Locations. Users.3. Hardware Administrators. Normal Users. Administrators. Module Type : Screen This module includes the following options: . Components and Computers. Master Administrator Setup Screen 5. User Modification 3. Module Type : Screen This module includes the following options: 1. Component Manipulation 5. So.1 User Module: Module Name: User Setup Functionality : The Users will be registered through this screen. User Deletion. they have to fill the necessary fields in the registration form. And also the User modification and deletion is also done through this module. User Creation 2.3. Search Screen Layout 1. Screen Layout . Computer Manipulation 4. User Manipulation 2.2.1. Reports 6. Location Manipulation 3. 1 New User Setup: Module Name: New User Setup Functionality : The Master Administrator can create a new User through this module.1. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A UserID of at least 4 but UserID Varchar2 (10) Y not more than 15 characters created by the Master Administrator A password of at least 4 Password Varchar2 (15) Y but not more than 15 characters created by the Master Administrator and can be changed by the Administrator or User LocID FName MName LName Add1 Add2 City State Country Pin Varchar2 (12) Varchar2 (21) Varchar2 (21) Varchar2 (21) Varchar2 (30) Varchar2 (30) Varchar2 (21) Varchar2 (21) Varchar2 (21) Varchar2 (7) Y Y Y Y Y Y Y . User Manipulation Screen 5.2.1.3. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A UserID of at least 4 but UserID Varchar2 (10) Y not more than 15 characters created by the .3. New User Creation Screen 2. New User Creation Result Screen 5.PhWork PhHome Desig Cell Email Fax UserType Varchar2 (15) Varchar2 (15) Varchar2 (50) Varchar2 (21) Varchar2 (50) Varchar2 (21) Varchar2 (3) Y Y Y Screen layout 1.2 User Modification Setup: Module Name: User modification Setup Functionality : The Master Administrator can modify a User through this module.2.1. Master Administrator Screen layout (click the link to view the corresponding Screen) 1.User Modification Screen1 3.3 User Deletion Setup: Module Name: User Deletion Setup Functionality : The Master Administrator can delete a User through this module.User Modification Screen 2.User Deletion Screen 2.2.1. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A UserID of at least 4 but UserID Varchar2 (10) Y not more than 15 characters created by the Master Administrator Screen layout (click the link to view the corresponding Screen) 1.User Deletion Result Screen1 .3.User Modification Result Screen 5. Location Creation 2. And also the Location modification and deletion is also done through this module.2. Location Manipulation Screen 5.2 Location Module: Module Name: Location Setup Functionality : The Location will be registered through this module. Location Deletion.3.3.1 New Location Module: Module Name: New Location Setup Functionality : The Master Administrator can create a new location through this module. Module Type : Screen Input Parameters : Parameter Data type Mandatory Validation Name LocID (Length) Varchar2(12) Y A LocationID of (at least 5 but not more than 15 characters) created by the Master Administrator . Location Modification 3. Screen Layout 1.2.2.5. Module Type : Screen This module includes the following options: 1. 2 Location Modification Setup: Module Name: Location modification Setup Functionality : The Master Administrator can modify a Location through this module. New Location Creation Result Screen 5.2.3.Location Modification Screen1 3. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A LocID of at least 4 but LocID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout (click the link to view the corresponding Screen) 1.LocName Add1 Add2 City State Country PhNumber Screen layout Varchar2 (15) Varchar2 (30) Varchar2 (30) Varchar2 (15) Varchar2 (15) Varchar2 (15) Varchar2 (15) Y Y Y Y 1.Location Modification Screen 2.2.Location Modification Result Screen . New Location Creation Screen 2. Also the component modification.3 Component Module: Module Name: Component Setup Functionality : The Component will be registered through this module.Location Deletion Screen 2.3.2. Module Type : Screen This module includes the following options: . moving between shelf-others and deletion is also done through this module.5.3 Location Deletion Setup: Module Name: Location Deletion Setup Functionality : The Master Administrator can delete a Location through this module. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A LocID of at least 4 but LocID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout 1.2.Location Deletion Result Screen1 5.2.3. Basing on the type the other details will be entered. ‘R’ – .3. Module Type : Screen Input Parameters : Parameter Data type Mandatory Name CmtID CmtName CmtType (Length) Varchar2 (12) Varchar2 (21) Varchar2 (3) Y Y Y Validation It should be either ‘HW’ – H/W or ‘SW’ – S/W LocID CmtManuf Status Varchar2 (12) Varchar2 (21) Varchar2 (2) Y Y Y It should be either ‘S’Shelf. Component Deletion. Component Moving 4. Type may be either S/W or H/W. Screen Layout 1. Component Manipulation Screen 5. Component Modification 3.2.1.1 New Component Module: Module Name: New Component Setup Functionality : A Component is entered into the Shelf by giving a unique Component Id and type of the Component. Component Creation 2.3. ‘B’ – Bin. Foreign key from cmt_master If the Component type is HW (Hardware) then the Additional input parameters are as follows. generated CmtID Varchar2 (12) Y automatically. Input Parameters (HW) : Parameter Data type Name CmtHwSno (Length) Number(38) Mandatory Validation Is the primary key. ‘C’ – Computer CmtPrice CmtPurFrom CmtPurOn Number (8. Input Parameters(SW) : Parameter Data type Mandatory Name CmtSwsno (Length) Number(38) CmtID Varchar2 (12) Y Version SerialNo.Recycle bin. Foreign key cmt_master from . generated automatically.2) Varchar2 (21) Date Y Y Y If the Component type is SW (Software) then the Additional input parameters are as follows. SwDate Remarks Varchar2 (5) Varchar2 (15) Date Varchar2 (30) Y Y Y Validation Is the primary key. 2.2 Component Modification Setup: Module Name: Component modification Setup Functionality : The Master Administrator can modify a Component through this module. New Component Creation Result Screen 5.ModelNo WarExpDate Remarks Varchar2 (15) Date Varchar2 (30) Y Y Screen layout 1.Component Modification Screen1 3.Component Hardware Modification Screen .3. New Component Creation Screen 2.3. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A CmtID of at least 4 but CmtID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout 1. New Component-Hardware Creation Screen 3.Component Modification Screen 2. 4.3.3.Component Modification Result Screen 5.3 Component Deletion Setup: Module Name: Component Deletion Setup Functionality : The Master Administrator can delete a Component through this module.4 Computer Module: Module Name: Computer Setup . Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A CmtID of at least 4 but CmtID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout 1.2.3.Component Deletion Result Screen 5.2.Component Deletion Screen 2. Module Type : Screen This module includes the following options: 1.1 New Computer Module: Module Name: New Computer Setup Functionality : A Computer is assembled using the components in the Shelf and is assigned a unique Identity number for every computer. Computer Manipulation Screen 5. Also the computer modification and deletion is also done through this module.3. Computer Creation 2.4.2. Computer Deletion.Functionality : The Computer will be registered through this module. Screen Layout 1. Module Type : Screen Input Parameters : . Computer Modification 3. Generated CmtID Varchar2 (12) Y Automatically Foreign key from CmpSwPno Varchar2 (7) Y cmt_master Foreign key from Remarks Varchar2 (30) cmp_master The Computer Hardware profile is entered by the following input parameters Input Parameters (Hardware) : Parameter Data type Name CmpHwSno (Length) Number(38) Mandatory Validation Primary key. Generated . New Computer Registration Screen The Computer software profile is entered by the following input parameters Input Parameters (Software) : Parameter Data type Mandatory Validation Name CmpSwSno (Length) Number(38) Primary key.Parameter Data type Mandatory Name CmpID CmpName CmpSwPno CmpHwPno LocID (Length) Varchar2 (12) Varchar2 (21) Varchar2 (7) Varchar2 (7) Varchar2 (12) Y Y Y Y Y Remarks Varchar2 (30) Validation Primary Key Unique Unique Foreign key from location Screen Layout 1. 4.2.Computer Hardware Modification Screen 4.3.3. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A CmpID of at least 4 but CmpID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout 1.2.Computer Modification Result Screen 5.CmtID CmpHwPno Varchar2 (12) Varchar2 (7) Y Automatically Foreign key from Y cmt_master Foreign key from cmp_master Remarks 5.2 Varchar2 (30) Computer Modification Setup: Module Name: Computer modification Setup Functionality : The Master Administrator can modify a Computer through this module.Computer Modification Screen 2.4.Computer Modification Screen1 3.3 Computer Deletion Setup: Module Name: Computer Deletion Setup . Bin or Recycle bin He can also access the information of all Locations.3 Hardware Administrator Module: Module Name: Hardware Administrator Menu Functionality : In this module the Hardware Administrator can create.3. He can also assign the Components to Computers.Computer Deletion Result Screen 5. Administrators. Shelf.Functionality : The Master Administrator can delete a Computer through this module. Module Type : Screen This module includes the following options: . Users. delete and modify the Components and Computers. Module Type : Screen Input Parameters : Parameter Data type Name (Length) Mandatory Validation A CmpID of at least 4 but CmpID Varchar2 (12) Y not more than 15 characters created by the Master Administrator Screen layout 1.Computer Deletion Screen 2. Computers and Shelf. He can also see the reports that are assigned to him Module Type : Screen This module includes the following options: 1. Search . Component Manipulation 2. 5.1.3.4 Purchase Manager Module: Module Name: Purchase Manager Administrator Menu Functionality : In this module the Purchase Manager can only move the components from the shelf to the bin or recycle-bin. Reports 4. Computer Manipulation 2. Reports 3. component and Reports and search modules are similar to the Master Administrator module. Component Manipulation 3. Search Screen Layout 1. Hardware Administrator Setup Screen The computer. 3.5 Normal User Module: Module Name: Normal User Menu Functionality : In this module the Normal user can only do the search operation and see some reports Module Type : Screen This module includes the following options: 1.Screen Layout 1.3.6 Reports Module: Reports will be generated basing on the option chosen by the Master Administrator. Reports and search modules are similar to the Master Administrator module. Search Screen Layout 1. Normal User Setup Screen The Reports and search modules are similar to the Master Administrator module. The following are the options on which reports can be generated. 5. . 5. Purchase Manager Setup Screen The component. Change Of Password 2.  On User  On Single User  On All Users in a Location  On Location  On Components  On Computer  On Hardware Components  On Software Components  On Bin  On Shelf  On Recycle Bin . Testing . systematically and with minimum effort and time.Testing performs a very critical role for quality assurance and for ensuring the reliability of software.The results of testing are used later on during maintainence also Psychology of Testing The aim of testing is often to demonstrate that a program works by showing that it has no errors. Testing is the process of executing a program with the intent of finding errors. . . Stating formally. we can say.Hence one should not start testing with the intent of showing that a program works.but the intent should be to show that a program doesn’t work.TESTING Testing is the process of detecting errors.The basic purpose of testing phase is to detect the errors that may be present in the program. Testing Objectives: The main objective of testing is to uncover a host of errors. the module. if it exists. Using the detailed design and the process specifications testing is done to uncover .  The tests are inadequate to detect possibly present errors.e.  A successful test is one that uncovers an as yet undiscovered error. Testing is a process of executing a program with the intent of finding an error. LEVELS OF TESTING In order to uncover the errors present in different phases we have the concept of levels of testing.  A good test case is one that has a high probability of finding error.  The software more or less confirms to the quality and reliable standards.The basic levels of testing are Client Needs Requirements Design Code Acceptance Testing System Testing Integration Testing Unit Testing Unit testing: Unit testing focuses verification effort on the smallest unit of software i. MasterAdmin.This testing activity can be considered as testing the design and hence the emphasis on testing module interactions. PManager.when developing the module as well as finishing the development so that each module works without any error.The goal here is to see if modules can be integrated proprerly. SYSTEM TESTING . In this project the main system is formed by integrating all the modules.There are so many modules like Login. Integration Testing: After the unit testing we have to perform integration testing. In this project each service can be thought of a module. All modules must be successful in the unit test before the start of the integration testing begins.When integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration. Each module has been tested by giving different sets of inputs.The inputs are validated when accepting from the user. NormalUser.HWAdmin.the emphasis being on testing interfaces between modules.errors within the boundary of the module. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied. In this project ‘Network Management Of Database System’ I have collected some data and tested whether project is working correctly or not. . I have generated a list of test cases .The reference document for this process is the requirements document.Here the entire software system is tested. White Box Testing This is a unit testing method where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. ACCEPTANCE TESTING Acceptance Test is performed with realistic data of the client to demonstrate that the software is working satisfactorily. Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. Testing here is focused on external behavoiur of the system.sample data. and the goal os to see if software meets its requirements.the internal logic of program is not emphasized. taking care that every statement in the code is executed at least once. The white box testing is also called Glass Box Testing.The testing phase is an important part of software development.which is used to check all possible combinations of execution paths through the code at every module level. I tested step wise every piece of code. Here entire ‘CRMS’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not. Black Box Testing This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output.Output for a given set of input combinations are forwarded to other modules. Output Design 6.1 SYSTEM FLOW CHART: Login Yes No Is User Maste Log Out Master Administrator Setup r Admi n Yes No Is User Hard Hardware Administrator Setup ware Yes Admi n Log Out Is User Log Purc O Error Message Purchase Manager Setup hase Man Log Yes Normal User Setup O CONCLUSION No ager Is No Nor mal User 7. CONCLUSION By doing the Computer Resource Management System Infotech Ltd. I have gained knowledge about the various functions of the system organization, such as how the Marketing department works and what are the main strategies that they follow to market the product. I also gained a considerable knowledge about the development environment and the SDLC (Software Development Life Cycle) and also the Finance department functionalities. One more great advantage is that of moving with people i.e. the communication during the project development, both the informal communication and the formal communication regarding the project work. As part of Computer Resource Management System development I learnt a lot about the reports that are useful to the various departments and also the frequency of generation of them. One more important aspect that I want to mention is Database designing, the normalization of the database and the other relational database features. And also by doing Computer Resource Management System I gained a lot of knowledge in the Enterprise JavaBeans, the development, deployment and the implementation of the Enterprise beans. 7.1 BIBLIOGRAPHY  Patrick Naughton & Herbert Schildt “The Complete Reference Java 2” TATA McGRAW-HILL, 1999 Edition.  Ed Roman “Mastering Enterprise Java Beans Enterprise Edition” WILEY, 1999 Edition. and the Java 2 Platform,  Tom Valesky “Enterprise JavaBeans ” Pearson Education Asia, 2000 Edition.  Richard Monson-Haefel “Enterprise JavaBeans ”O’REILLY, March 2000 Edition.  David Austin “Using Oracle8 ”, Eastern Economic Edition, 2000 Edition. run anywhere”. Enterprise JavaBeans is not only platform independent –it’s also implementation independent. .2 References One of java’s most important features is platform independence. an enterprise bean. it can access any vendor’s relational database that has a JDBC driver.html#1025959 7. Ideally.weblogic.weblogic.com/docs51/classdocs/API-ejb/index. Its like JDBC API runs on a Windows machine or on a Unix machine. an Enterprise JavaBeans component.Websites visited:  www.html  www. Java has been marketed as “write once.weblogic. Since it was released.com  www.com/docs51/classdocs/API-ejb/EJB-whatsnew. can run in any application server that implements the Enterprise JavaBeans (EJB) specification - Richard Monson-Haefel. . The ACID properties are nothing but (Atomic Consistent Isolated Durable) properties - Ed Roman. usually databases. A unit-of-work is a set of activities that relate to each other and must be completed together.A transaction is the execution of a unit-of-work that accesses one or more shared resources.