Reference no: EM131834299

Discussion Question - Object Modeling

Part 1:

Please respond to the following in not more than 200 words:

Which aspect of object modeling did you find the easiest?

Which one was the most challenging for you?

Prof. Comment - "Object modeling is a fundamental tool for analyzing and expressing data requirements. Which aspects seem easiest and most difficult for you? "

Part 2:

In a separate post, follow up to one or more of your fellow students in substantive posts of up to 150 words that further the discussion. For example, you may support or politely challenge a post with your own insights or experience, make a suggestion, or ask probing follow-up questions. (choose one)

a. This method is known to promise increased productivity and a shortened development sched

I found the part where an object interacts with one another to determine how the program would work very interesting. I also found the descriptions and the attributes of the objects easy to understand and self-explanatory.

However, having the objects interact effectively to achieve the desired outcome i believe would be challenging since the research and development time is much shorter than a traditional method. Moreover, Managers and users might not have the technical backgrounds to understand the short falls of the program being developed and may have unrealistic expectations.

b. The aspect of object modeling that I find the easiest to understand and appreciate is encapsulation. The concept shows that everything in the system serves a purpose to not only the system but itsel

Describing encapsulation as a black box helps better understand the structure of Object modeling and gives an in depth look at how information will flow. The basic concept is simple but as the model becomes bigger it can be more complex do to inheritance.

Encapsulation makes it possible to add modular components to change design without altering the overall design. I think the challenging will make itself apparent when the model begins to grow and needs to make use of class relationships. As I said as the system becomes larger it may make it harder to follow who is related to who.

I can imagine if you have designed a model that is very large and you come across a problem with a class taking inheritance from an object that is designed wrong.

c. The easiest aspect of the object modeling for me is the object and attributes-Because you can add any kind of data to the object and attributes for your software design, you can add or delete attributes as needed.

The one for me would be the most challenging would be building the relationship between objects and classes, you have to program the software so that the relationship between the objects and classes understand the changed attribute languages of the software.