Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

Dear students,

Graded Discussion Board for the course 'Software Engineering-I (CS504)' will be open on Monday 10th Feb, 2014 and it will be closed on Tuesday 11th Feb, 2014.

Discussion Topic

For designing a complex nature embedded system one group of thought said that object oriented modeling will be used and another group of thought said that structured oriented modeling will be used. As a software engineer you are required to analyze and design models for this system, so out of these two approaches which approach is suitable and why? Justify your answer with logical reasons.

Read the instructions carefully before sending your comments:

  1. GDB will have weight-age of 5% of your total subject marks.
  2. Your discussion must be based on logical facts.
  3. You should post your comments on the Graded Discussion Board & not on the Regular MDB. Both will run parallel to each other during the time specified above.
  4. Your comments should be relevant to the topic i.e. clear and concise (Maximum 5-10 lines answer).
  5. Books, websites and other reading material may be consulted before posting your comments. (Do not copy the material as it is.)
  6. No extra time will be given for discussion.
  7. You cannot participate in the discussion after the due date or through e-mail.

Views: 2416

Replies to This Discussion

Structured modeling is one of the most important modeling paradigms in the field of decision support systems. It has high generality and shares features to some extent with object-oriented modeling in software engineering. On the other hand, compared with object-oriented modeling paradigms, structured modeling also has some shortcomings. In this paper, we first examine structured modeling from the point view of object-oriented modeling, and show that structured modeling lacks the expressive power to capture the dynamic aspect of systems. Then we propose a framework for structured modeling which aims to model the dynamic aspect of systems. Among others, one of the advantages of this framework is that the resultant dynamic models have some kind of normal form. And the normal form of models will provide a solid foundation for model integration. Example is given to illustrate our framework, and the potential application of this framework is also discussed.


plz some one ffinalize, which approach will be better for Complex embedded system ?? 

too nice sharing

helpfull

Structured programming can be seen as a subset or sub discipline of procedural programming, one of the major programming paradigms. It is most famous for removing or reducing reliance on the GOTO statement.
The rise of the Object Oriented concept brought us debugging comfort as well as expandability as the programs were getting larger and larger and it became difficult to debug. There were functions to reduce the size of the programs and improve readability but it was never enough.

Object-oriented programming (OOP) is a programming language model organized around “objects” rather than “actions” and data rather than logic. Historically, a program has been viewed as a logical procedure that takes input data, processes it, and produces output data. The programming challenge was seen as how to write the logic, not how to define the data. Object-oriented programming takes the view that what we really care about are the objects we want to manipulate rather than the logic required to manipulate them.

Object Oriented Programming has many benefits over Structured programming. Some of them are reusability, extensibility, reliability and maintainability. OOP also helps to reduce large problems to smaller, more manageable problems. In terms of extensibility and reusability, for instance: “Encapsulation allows the internal implementation of a class to be modified without requiring changes to its services (i.e. methods). It also allows new classes to be added to a system, without major modifications to the system. Inheritance allows the class hierarchy to be further refined, and combined with polymorphism, the super class does not have to “know” about the new class, i.e. modifications do not have to be made at the super class.

Structured modeling is one of the most important modeling paradigms in the field of decision support systems. It has high generality and shares features to some extent with object-oriented modeling in software engineering. On the other hand, compared with object-oriented modeling paradigms, structured modeling also has some shortcomings. In this paper, we first examine structured modeling from the point view of object-oriented modeling, and show that structured modeling lacks the expressive power to capture the dynamic aspect of systems. Then we propose a framework for structured modeling which aims to model the dynamic aspect of systems. Among others, one of the advantages of this framework is that the resultant dynamic models have some kind of normal form. And the normal form of models will provide a solid foundation for model integration. Example is given to illustrate our framework, and the potential application of this framework is also discussed.

Object Oriented modeling has many benefits over Structured modeling. Some of them are reusability, extensibility, reliability and maintainability. OOM also helps to reduce large problems to smaller, more manageable problems. In terms of extensibility and reusability, for instance: “Encapsulation allows the internal implementation of a class to be modified without requiring changes to its services (i.e. methods). It also allows new classes to be added to a system, without major modifications to the system. Inheritance allows the class hierarchy to be further refined, and combined with polymorphism, the superclass does not have to “know” about the new class, i.e. modifications do not have to be made at the superclass.

OBJECT ORIENTED MODELING HAS MANY BENEFITS OVER STRUCTURED MODELING. SOME OF THEM ARE REUSABILITY, EXTENSIBILITY, RELIABILITY AND MAINTAINABILITY. OOM ALSO HELPS TO REDUCE LARGE PROBLEMS TO SMALLER, MORE MANAGEABLE PROBLEMS. IN TERMS OF EXTENSIBILITY AND REUSABILITY, FOR INSTANCE: “ENCAPSULATION ALLOWS THE INTERNAL IMPLEMENTATION OF A CLASS TO BE MODIFIED WITHOUT REQUIRING CHANGES TO ITS SERVICES (I.E. METHODS). IT ALSO ALLOWS NEW CLASSES TO BE ADDED TO A SYSTEM, WITHOUT MAJOR MODIFICATIONS TO THE SYSTEM. INHERITANCE ALLOWS THE CLASS HIERARCHY TO BE FURTHER REFINED, AND COMBINED WITH POLYMORPHISM, THE SUPERCLASS DOES NOT HAVE TO “KNOW” ABOUT THE NEW CLASS, I.E. MODIFICATIONS DO NOT HAVE TO BE MADE AT THE SUPERCLAS

OOM is better

Objects provide a good model of the reality adapted to the needs of a specific system. Each IT application system has to manipulate data and has to support business functions by providing procedures and guidance through the allowed sequence of processes. In former analysis and design projects structuring of problem domains was performed data or function oriented, where one orientation was normally dominating the whole modelling effort. Object orientation takes away this dominance and an object combines the two elements (information and function) as equally important features normally called "data" and "behaviour".

RSS

Looking For Something? Search Below

VIP Member Badge & Others

How to Get This Badge at Your Profile DP

------------------------------------

Management: Admins ::: Moderators

Other Awards Badges List Moderators Group

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service