CS504 Software Engineering-1 Assignment no 2 idea solution april 2011

[Vuhelper]

View more random threads:

• CS101 Assignment#4( help required plz)
• CS504 Software Engineering Assignment no 4 spring June 2011
• CS401 VU Current Assignment No. 3 idea solution Fall...
• cs601 assignment no 3 solution 5 Jun 2011
• CS601 VU Current Assignment No.1 Spring April 2012 Last...
• CS607 Artificial Intelligance Assignment No.2 Fall Semester...
• CS201 Introduction to Programming Fall 2010 second...
• MTH603 (Spring 2012) assignment no 1 idea solution
• cs401 Computer Architecture and Assembly Language...
• IT430 E Commerce Assignment No 03 Semester 31 May Spring...

Total marks = 20

Deadline Date = 04-05-2011

Q1 [Marks 10]

Sponsored Links

Consider the following Class, a student claims that the class is poorly (low) cohesive, device more cohesive class(s) out of this class (along with proper methods and attributes).




Q2 [10 Marks]

Discuss all the possible effects of bad / poor object model on the final product

TIP: provide you answer with proper and suitable headings

[Vuhelper]

Q1- [Marks 10]

Answer:

class patmng
{
Int ptn_no;
Date dob;
};
Class physin
{
int surgn no;
String fee;
};
Class operation
{
String operationpoint;
Bool targetachived;
}
;;
Q2- [Marks 10]

Answer:

effects of bad / poor object model on the final system::
It brings collapse to the overall project. Model poorly help the developers to get the solution accepted by the demanding organization. Reduced effort in maintenance and enhancement, resulting from inheritance, encapsulation, low coupling, and high cohesion.
. We can not well maintain our profit. Clarity and understandability of the system, as object-oriented approach is closer to the working of human cognition. Reusability of code resulting from low inter-dependence among objects, and provision of generalization and specialization through inheritance

[vukhan]

effects of bad / poor object model on the final system::
I)-Collapse:
It brings collapse to the overall project.
II)-Acceptance:
Model poorly help the developers to get the solution accepted by the demanding organization.
III)- Maintainence:
Reduced effort in maintenance and enhancement, resulting from inheritance, encapsulation, low coupling, and high cohesion.
Iv)Profit
. We can not well maintain our profit.
V)-Clairity:
Clarity and understandability of the system, as object-oriented approach is closer to the working of human cognition.
Vi)Reusability:
Reusability of code resulting from low inter-dependence among objects, and provision of generalization
VIII)-Inheritence:
and specialization through inheritance.

[sulmanbilly]

alright can you please tell me where is the topic comes from of first question ???

[Xpert]

please consult with your handouts. you will know....