Replies to This Forum

Permalink Reply by M L Singh on February 22, 2011 at 23:36

Re-engineering means again, design and operate. This term was conceived by Michael Hammer in 1990. It is a rapid and radical redesigning of business process, services, policies and organisational structure of an organisation.

Definition:

According to Hammer and Champy, " Re-engineering is the fundamental rethinking and radical redesigning of business process to achieve dramatic improvement in critical contemporary measures of performaces such as Cost, Quality, Services and Speed"

Features:

1. Resources need to be generated

2. Operations have to be stablised.

3. when operations become familiar, the focus shifts to the customers.

• ▶ Reply

Permalink Reply by Gautam Bahl on February 23, 2011 at 17:24

Dear Ms. Kamaljeet,

 

                I shall be greatful if you could send me the detailed bibliography of the literature review quoted by your goodself in the above reply. If you have some relevant articles on the topic of reengineering of libraries, I would request you to share them also.

 

regards, 

• ▶ Reply

Permalink Reply by Dr. Rajpal Purohit on February 23, 2011 at 19:24

Thanks u Kamaljeet mam it very good feeling to see u after long time always veery good ans. thanks a lot

nice morning mam i miss u

thanks a lot.

• ▶ Reply

Permalink Reply by Jayshree Dave on February 23, 2011 at 18:46

Reengineering concerns the examination of the design and implementation of an existing

legacy system and applying different techniques and methods to redesign and reshape that

system into hopefully better and more suitable software.

This process is by no means an easy task, since legacy systems may have come a long way

from the state in which it was first concieved and implemented. Updates and the adding of

new functionality may cause a lack of proper and updated documentation, especially if the

system is entrusted to people not skilled in the reengineering way of thinking.

Also, maintainability may suffer as the source code becomes flooded with new ways of

communication; and the breaking of encapsulation of objects in favour for an easy way to

some immiediate goal may lead to code so complex, it is almost unmaintainable .

The reengineering team must be able to see through the dense jungle that often characterize a

legacy system, and find those parts that still has a meaning in the final system. Taking such

decisions must be done with great care and great thought, since the reengineering process is

about taking care of the end users current and future needs; as well as ensuring a quick and

easy transition to the new system. If the entire system is redesigned and implemented then we

don’t have a reengineering process, but a pure software engineering process with an end

product probably having the need for extensive user training.

You could therefore say that when reengineering, you try to change as little as possible while

still ensuring that fundamental aspects like maintainability, userability, functionality and other

requirements are still addressed in a proper way.

This gives us our main paradigm in reengineering:

“Change, but change as little as possible.”

• ▶ Reply

Permalink Reply by Dr. Rajpal Purohit on February 23, 2011 at 19:25

Very good ans jayshree thaks a lot what going on

have a nice day

• ▶ Reply

Permalink Reply by Gautam Bahl on February 23, 2011 at 19:41

Dear Jaishree,

 

              Please cite some references regarding the content of your post. It is necessary as the concept of reengineering described in your post is totally against the definition of re-engineering given by Hammer and Champy ( quoted by Mr. Singh).

 

The terms used in the definition are "fundamental rethinking and radical redesign" but against these in your post and I quote

"You could therefore say that when reengineering, you try to change as little as possible while

still ensuring that fundamental aspects like maintainability, userability, functionality and other

requirements are still addressed in a proper way."

It would be benificial for all the members if you could clarify more on this point.

• ▶ Reply

Permalink Reply by Jayshree Dave on February 23, 2011 at 20:18

Gautam sir,
Hammer and champy define the term redesign of business processand services.
in my discussion  i not talking about any business ar industry. That is only REENGINEERING pls follow the link for more detail

http://www.idt.mdh.se/kurser/cd5130/msg/2002lp3/download/CD5130%20V...

• ▶ Reply

Permalink Reply by Gautam Bahl on February 23, 2011 at 20:38

Dear Jayshree,

 

          Thanks for the clarification. As per my knowledge goes, the concept of Business process reengineering and so called term only reengineering are the same (please correct me if I am wrong).

         If you open the link given by your goodself, and see the complete context, the statement I pointed out, is being stated particularly in the context of re-engineering legacy systems. Thats why the confusion existed.

 

Thanks for the clarification.

• ▶ Reply