The Computer Resource Management System

A Computer Resource Management System is used to get up to date information of all the computer resources in an organization. It is basically a management and informative system. This system helps the organization to overcome the complexity in tracing out all the computer resources of the organization by presenting customised reports, there by helps in effective and timely utilization of hardware and 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. It’s 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 Web logic and later move it to a different EJB server, such as IBM’s Web Sphere or Gemstone/J. Implementation independence means that business components are not dependent on the brand of server.

Computer Resource Management System uses Oracle 8i as the back-end RDBMS. Oracle 8i is actually a fully Internet supported database system. Oracle 8i perfectly handles the ACID Transactions. A transaction is the execution of a unit-of-work that accesses one or more shared resources, usually databases. A unit-of-work is a set of activities that relate to each other and must be completed together. The ACID properties are nothing but (Atomic Consistent Isolated Durable) properties

A transaction to be atomic, it must execute completely or not at all. Consistency refers to the integrity of the underlying data store, consistency is ensured by seeing that a transaction is atomic, isolated and durable. Isolated refers to allowing a transaction to execute without interference from other processes or transactions, i.e., the data that a transaction accesses cannot be affected by any other part of the system until the transaction or unit-of work is completed. 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. This ensures that the changes are not lost if the system crashes. Apart from handling the ACID properties Oracle 8i has higher security level and web compatibility features.

2. Problems of Present System:

As of now the resource management in SOFT PRO SYSTEMS LTD 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, as of now it is being done manually which consumes a great manpower and the process is time consuming. The problem of maintaining the bulk database can be solved by atomizing the resources in the organization, which can be of great help to all the administrators, 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.

The Manager has to wait for the manual reports from the development department to know the current status of the resources.

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 view the details of a computer and to know what are the components that are assigned to it, can be done only by a manual checking of that computer for the hardware and software components is a tedious process.

The users of the organization require various reports to be generated in an easy format, which is not so easy when done manually.

The Manager may get problems in finding out a user details in hundreds of records.

2.1 Need For Computerization:

Maintaining the information regarding all employees, components and computers at single or multiple locations give rise to many problems like:

Difficulty in retrieval of data in desired manner.

Checking the uniqueness wherever it is required.

Availability of information in this manner is subjected to damage.

Providing security is also difficult.

One way to overcome all these difficulties is to store all the information in the computer. The computerization helps the users a lot. The user can get information in desired manner. Data retrieval is also easy and fast. This also restricts the users to enter invalid data and reduces the burden on the user.

2.2 Benefits of Computerisation:

A computer based information system is usually needed for the following purposes.

Greater Processing Speed:

Using computers inherent ability to calculate, sort; retrieve data with greater speed than that of the human doing and can get results in less time. Visual Basic guaranties for the faster query processing thus we are satisfied with Visual Basic itself supporting in this direction.

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:

Using computerization we can do the required operations with lower cost than any other methods. Hence by computerization we can reduce the cost drastically.

3. Modules of CRMS:

Of course there are many other systems which can maintain all the resources of the company, but there are some defects and difficulties in those systems regarding security and HR dependent issues. The Computer Resource Management System mainly consists of 6 modules and a brief explanation of those is given below. (Overview of Metadata Annotations and EJB 3.0 Bean Files, 2009)

1 Components:

Each and every component that is either related to software or hardware will be assigned with a unique number and entered in to a folder or shelf. Whatever goes out will be deducted from the shelf and must be entered either to bin, recycle bin or to a computer. For every component appropriate entry should be made.

2 Computers:

Computers will be assembled using the shelf parts. Every computer should be given a unique number. The details of the computer will be entered including its hardware and software profiles with their parts. The computers may be servers, standalone’s and clients etc.

3 Bin:

The damaged components, which are not repairable or replaceable, will be sent to this bin.

4 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.

5 Status:

The status gives the statistics of the shelf, bin, recycle bin, computers. The status gives the present position of the component where it is situated in the organization. Basing on the status the components are used in different transactions.

6. Search / View:

The users can search or view the information of different resources based on their unique number given to them.

The proposed system will be designed by using Java beans as front end and Oracle 8i as RDBMS of the system that is oracle as back end of the system. Hyper text mark-up language is used to hyper text the information which can be moved from one platform to other, and JDBC concepts will be used.

4. Analysis of the Project:

System Planning is one of the important items to be considered before actually beginning the project. Planning is performed on the issues like defining Life Cycle Model and an organizational structure project, configuration management, quality and validation activities.

In the process of the System Planning various phase-dependent tools, techniques and notations are determined. Preliminary cost estimates for the system development and preliminary development schedules are established. Preliminary estimates of the computing resources required to operate and maintain the system are developed, glossary of terms are prepared.

4.1 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. The information regarding company activities is gathered from the company’s website www.lailainfotech.com.

4.2 Feasibility Study:

An initial investigation culminates in a proposal that determines whether an alternative system is feasible than the present candidate system. To do feasible study we have to do Economic, Technical, Behavioural feasible studies.

4.2.1 Economic Feasibility:

It is the most frequently used method for evaluating the effectiveness of a system. It is also called as cost/benefit analysis.

In this project “Computer Resource Management System”, for the development of the candidate system the costs 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. As the company itself is a development centre all the resources are in the company itself and no extra cost are spent for Computer Resource Management System. Hence our candidate system production is economically feasible.

4.2.2 Technical Feasibility:

Technical feasibility centres on 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 technically feasible.

4.2.3 Behavioural Feasibility:

People are inherently resistant to change. Our candidate system is developed in such a way that it is very user friendly, easy to learn how to work with and there is also not much resistant to this package from the staff side also. As the company is basically a development centre it will be very easy for the employees of the company to learn about the developed candidate system. Hence our candidate system production is behaviourally feasible.

5. Conclusion:

This project aimed at developing a Computer Resource Management System (CRMS) is a total management and informative system, where up-to date information of all the computer resources in the company can be provided. It helps the companies to overcome the difficulties in tracking the resources of the company by presenting customized reports, which helps the company to effectively and timely utilise hardware and software resources.

References:

David Austin., (2000), Using Oracle8, Eastern Economic Edition, 2000 Edition.

Overview of Metadata Annotations and EJB 3.0 Bean Files, Retrieved march 15, 2009 from http://e-docs.bea.com/wls/docs100/ejb30/program.html#typical_steps

Patrick Naughton., and Herbert Schildt., (1999),The Complete Reference Java 2, TATA McGRAW-HILL., 1999 Edition.

Pressman, R., S., Software Engineering: A Practitioner’s Approach, seventh edition, Retrieved 06 march, 2009 from http://www.rspa.com/spi/

Roman, Ed.,(1999), Mastering Enterprise Java Beans and the Java 2 Platform, Enterprise Edition, WILEY., 1999 Edition.

Tom Valesky., (2000), Enterprise JavaBeans, Pearson Education Asia, 2000 Edition.

Project proposal:

1. Introduction:

A Computer Resource Management System (CRMS) is used to get up to date information of all the computer resources in an organization. It is basically a management and informative system. This system helps the organization to overcome the complexity in tracing out all the computer resources of the organization by presenting customised reports, there by helps in effective and timely utilization of hardware and software resources.

2. Background of the project:

The purpose of proposed system is to provide a computer based system which can manage total resources of an organization. In previous systems the resource management was done manually, which wastes so much of time and the man power. The most important thing is the lack of security in previous resource management system. The atomized management system is efficient enough to maintain the resources. The development of the proposed system is needed for so many reasons such as security aspects, ease of use for the employees of organization. The disadvantages of the paper based or existing system can be rectified by implementing the proposed system.

The disadvantages of paper based system are mentioned below:

Finding the information about a component in the system is difficult and time taking course of action.

In the existing system any user, who is not authenticated can also view the information and change it, which leads to poor design and implementation of the total system.

A lot of manual work is required in finding and generating the reports about various sections in the organization, because of this work people can become irritate and get bored of doing the work.

The employees of the organization must produce the reports in a simple and understanding way, generating of such reports is not that easy to do.

Authentication of a user cannot be given in the existing system, and there is so much difficulty in taking out and recovery of data in a preferred manner.

The present system is going to provide the security to the database, and atomizing the system to manage the resources in the organization by using the enterprise java beans, oracle 8i as front end and back end of the system. To develop this system a good knowledge about life cycle model of software development, different functions of the organization and about marketing strategies is required. The knowledge of various reports that are to be generated which are helpful to different branches in the organization is required. In the development of the proposed system the different phase dependent tools, methods and document specifications are determined. (Roman, 2002)

3. Aims and objectives:

Aim:

To design an automated computer based system and to get up-to-date information about components which helps organizations to conquer the complexity in tracking all the resources of the company by generating reports that are more easily understandable and to improve security for database. It provides proper initiatives and approaches that need to be undertaken, thereby avoiding the huge cost of implementing a new system or by simply adapting to one currently deployed.

Objectives:

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 a user friendly and multi-user interface for handling the application.

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.

To provide the necessary reports to various users in time.

4. Intellectual challenge:

4.1 System Architecture:

4.1.1 Physical Architecture Model:

4.1.2 Layered Architecture:

Database Layer

Contains the data and database-related objects like stored procedures, triggers, packages, etc.

Application Layer

Contains the objects addressing the business logic; Most of the middle-level Java objects will be here in application layer.

Web Interface Layer

It will be on the web server; It contains the web pages (JSPs) of the application which will interact with the front-end browsers

Client Layer

Contains the web browser which interacts with web server

4.2 DATAFLOW DIAGRAM:

LocID

1 User Authentication

USER ID AND PASSWORD

Location

User Profile

Users

2 Master Administrator Setup

5 Normal User Setup

3 Hardware Administrator Setup

4

Purchase Manager Setup

4.3 System Design:

SYSTEM DESIGN phase follows system analysis phase. Design is maintaining a record proof design division and providing a blueprint for the implementation phase. Design is the bridge between system analysis and system implementation.

System design is transition from a user oriented, document oriented to programmers or database personnel. The design is a solution, a “how to” approach to the creation a new system. This is composed of several steps. It provides the understanding and procedural details necessary for implementing the system recommended in the feasibility study. Design goes through logical and physical stages of development, logical design reviews the present physical system, prepare input and output specifications, detail the implementation plan, and prepare a logical design walkthrough. (Dennis, A. & Wixom, B. H. (2000))

The database tables are designed by analyzing various functions involved in the system and the format of the fields is also designed. The fields in the database table should define their role in the system. The unnecessary fields should be avoided because it affects the storage areas of the system. Care is to be taken to encode the lengthy names. Then in the input and the output screen design, the design should be made user friendly. The menu should be precise and compact.

4.3.1 Objectives of Design

System design is like a blue print for a building, it specifies all the features that are to be in the finished product. Design states how to accomplish objectives determined in the analysis phase.

Logical Design

The design of an information system produces the details that state how a system will meet the requirements identified during systems analysis. This stage is login design.

Physical Design

The process of developing program software is referred to as physical design. In this stage the logical design elements are specified which support the business activities. The physical design ensures the system features to meet the user requirements.

5. Schedule:

The above mentioned project is said to be start in March 2010 and ends on September 2010. The total duration required to develop the system is 5 months.

Task no.

Description

Duration

Collect the information about the current project and conduct research to know about the previously implemented systems in various organizations

3 weeks

Studying the technologies used in developing the proposed project

2 weeks

Analyzing the outcomes of the project and draw a flowchart for the modules to be developed

2 weeks

Designing the typical architecture of the project and steps involved in it

2 weeks

Developing the project code based on the architecture and requirements

2 weeks

Testing and validating the designed system

2 weeks

Writing guidelines for end users

1 week

Preparing the final report of the proposed system

2 weeks

Possible amendments and closing up everything into a report

4 days

Final submission

1 day

6. Deliverables:

The final result of this project is as follows.

Ordinary users can do the simple operations like searching, viewing the components by some key words.

Any changes in the all modules, like deleting the components, adding components will be done by master administrator, and he will be having total permissions to do any changes or modifications to the database.

By using the up-to date information various reports will be generated in less time.

Maximum security of database will be achieved.

Atomization of system will be done and the system will become user friendly and multi user interface.

Provides good trust among the customers.

7. Resources:

The resources required can be summed up as:

Accessing the IEEE explorer technical papers from the university library.

Latest technical papers and journals about HTML, Java, Oracle 8i, and design implementations.

Database system management text books to know how to implement tables in the system.

Books on current trends in CRMS

Collections of Library Resources and Archives

Real time assessment of an online business retailer to know the current trends involved.

8. Requirements:

Software and hardware:

Operating System: Windows NT98

Web Server:

Server side Application Software: Java Server Pages (JSP)

Business Logic Software: Enterprise Java Beans. (EJB)

Client Side Application Software: Java Script, HTML

Data Base: Oracle 8i

Client Browsers:

Internet Explorer 5.0 or Netscape Navigator 4.7

Dream Weaver 3.0/JRUN4.0s

Hardware: Pentium PCs with 128 MB RAM/ 20 GB HDD.

Order Now