
	Home


	Homework Help


	Answer Board


	Resources (Beta)

You Are Here:

Home > Answer Board > Computer Science > Topic: impct of OO paradigm on software development (program...

Member's Topic Headline:

impct of OO paradigm on software development (programming)

Know the answer? Have a better solution? Share it.

Join the thousands of students
getting ahead in their classes.

Member Testimonials

Question:

Answers:

Ziaxp

Guru

Karma Points: 2,014

Date Posted: 7/24/2008 12:54:10 AM Status: Live

Asker's Rating: None Provided Moderator's Rating: Somewhat Helpful

Response:

Software development is an inefficient and expensive process. More than a quarter of software projects fail and almost every project exceeds its budget and requires extra time to finish. At the same time, high competition forces prices down. Object-orientation seems to be at the time the most promising approach to address most of the software development problems

Two functionally equivalent versions of any approval system were maintained, one object oriented (OO) and the other non-object oriented (NOO). You found that the OO group took less time to maintain a greater number of software artifacts than its Non-OO complement. This difference held for all phases of the software development life cycle. This result was due to the usefulness of UML for impact analysis of the OO version, which contributed to effective comprehension and communication. Insufficient design specifications for the Non-OO version led to ambiguity and costly defects in transferring design solutions to development. Also, the encapsulation of the OO version appeared to reduce mental loads for maintenance tasks and resulted in code reuse. On the other hand, the number of files to be managed increased and, thus, dependency management was required for the OO version. Furthermore, despite much tuning, the OO version ran slower than its Non-OO complement. More field studies on software professionals are needed to compare contextual factors such as methods, processes, and maintenance tools.

Empirical evidence for the maintainability of object-oriented systems is far from conclusive, partly due to the lack of representativeness of the subjects and systems used in earlier studies. We empirically examined this issue for mission-critical software that was currently operational and maintained by software professionals. Two functionally equivalent versions of a credit approval system were maintained, one object oriented (OO) and the other non-object oriented (NOO). We found that the OO group took less time to maintain a greater number of software artifacts than its NOO counterpart. This difference held for all phases of the software development life cycle. This result was due to the usefulness of UML for impact analysis of the OO version, which contributed to effective comprehension and communication. Insufficient design specifications for the NOO version led to ambiguity and costly defects in transferring design solutions to development. Also, the encapsulation of the OO version appeared to reduce mental loads for maintenance tasks and resulted in code reuse. On the other hand, the number of files to be managed increased and, thus, dependency management was required for the OO version. Furthermore, despite much tuning, the OO version ran slower than its NOO counterpart. More field studies on software professionals are needed to compare contextual factors such as methods, processes, and maintenance tools.

Hope this will help you,

Don't forget to LIFE SAVER RATE to my answer plz.

Ziaxp (MIT)

By reading or posting messages on these forums, you are agreeing to the Answer Board's Terms of Service and Conduct (TSC).

impct of OO paradigm on software development (programming)

Question:

Advertisement:

Answers: