Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

Graded Discussion Board Dated: Feb 04, 14

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: 1324

Replies to This Discussion

share ur ideas to make easy understanding of the gdb topic

what's ur opinion regarding which approach is best for complex nature embedded system ? 

FIRSTLY ANSWERS THE FOLLOWINGS

WHAT IS THE  object oriented modeling AND ITS ADVANTAGES AND SHORT COMINGS?

AND

WHAT IS THE  structured oriented modeling  AND ITS ADVANTAGES AND SHORT COMINGS?

object oriented modeling is a bigning phase of softwere development,,,,,

user usually cannot understand the code, modles are easy to understand for users to give feedback to developers.

key goal of object oriented is to decrease the semantic gap between users and developers.

Object oriented modeling usually done with the help of use cases and abstract points of the most important objects.

Please Discuss here about this GDB.Thanks

Our main purpose here discussion not just Solution

We are here with you hands in hands to facilitate your learning and do not appreciate the idea of copying or replicating solutions.

Object-Oriented Modeling (OOM)
Definition - What does Object-Oriented Modeling (OOM) mean?
Object-oriented modeling (OOM) is the construction of objects using a collection of objects that contain stored values of the instance variables found within an object. Unlike models that are record-oriented, object-oriented values are solely objects.

The object-oriented modeling approach creates the union of the application and database development and transforms it into a unified data model and language environment. Object-oriented modeling allows for object identification and communication while supporting data abstraction, inheritance and encapsulation.
Techopedia explains Object-Oriented Modeling (OOM)
Object-oriented modeling is the process of preparing and designing what the model’s code will actually look like. During the construction or programming phase, the modeling techniques are implemented by using a language that supports the object-oriented programming model.

OOM consists of progressively developing object representation through three phases: analysis, design, and implementation. During the initial stages of development, the model developed is abstract because the external details of the system are the central focus. The model becomes more and more detailed as it evolves, while the central focus shifts toward understanding how the system will be constructed and how it should function.

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.

Structured Analysis and Object Oriented Analysis are different techniques of
developing a computer system. Structured Analysis In Structured Analysis,
the focus is only on process and procedures.Modeling techniques used in it are
DFD(Data Flow Diagram), Flowcharts etc.This approach is old and is not preferred
Object Oriented Analysis Whereas in Object Oriented Analysis, the focus is
more on capturing the real world objects in the current scenario that are of
importance to the system. [2] It stresses more on data structure and less on
procedural structure. Without actually identifying objects, what are you going
to interact with, and whose state will you change. In this approach, objects are
identified, their relationships among each other, possible states that each
object can be in, and finally how all objects collaborate with each other to
achieve a broader system goal are identified.Modeling techniques used in it are
UML(Unified modeling Language), that can present both structural and
behavioural/procedural aspect of the system. UML includes Class Diagram, State
Diagram, Use case diagram, Sequence Diagram, etc.Using this approach keeps your
system more maintainable and reusable, and is a common choice nowadays
References System Analysis and Design, Fifth Edition. Author: Shelly Cashman
Rosenblatt. Pg20 Object Oriented Modeling and Design with UML, Second Edition.
Author: Blaha Rumbaugh

Structured Analysis and Object Oriented Analysis are different techniques of
developing a computer system. Structured Analysis In Structured Analysis,
the focus is only on process and procedures.Modeling techniques used in it are
DFD(Data Flow Diagram), Flowcharts etc.This approach is old and is not preferred
Object Oriented Analysis Whereas in Object Oriented Analysis, the focus is
more on capturing the real world objects in the current scenario that are of
importance to the system. [2] It stresses more on data structure and less on
procedural structure. Without actually identifying objects, what are you going
to interact with, and whose state will you change. In this approach, objects are
identified, their relationships among each other, possible states that each
object can be in, and finally how all objects collaborate with each other to
achieve a broader system goal are identified.Modeling techniques used in it are
UML(Unified modeling Language), that can present both structural and
behavioural/procedural aspect of the system. UML includes Class Diagram, State
Diagram, Use case diagram, Sequence Diagram, etc.Using this approach keeps your
system more maintainable and reusable, and is a common choice nowadays
References System Analysis and Design, Fifth Edition. Author: Shelly Cashman
Rosenblatt. Pg20 Object Oriented Modeling and Design with UML, Second Edition.
Author: Blaha Rumbaugh

Object-oriented modeling

Object-oriented modeling is an approach to modeling an application that is used at the beginning of the software life cycle when using an object-oriented approach to software development.
The software life cycle is typically divided up into stages going from abstract descriptions of the problem to designs then to code and testing and finally to deployment. Modeling is done at the beginning of the process. The reasons to model a system before writing the code are:
Communication. Users typically cannot understand programming language code. Model diagrams can be more understandable and can allow users to give developers feedback on the appropriate structure of the system. A key goal of the Object-Oriented approach is to decrease the "semantic gap" between the system and the real world, to have the system be constructed using terminology that is the same as the functions that users perform. Modeling is an essential tool to facilitate this.
Abstraction. A goal of most software methodologies is to first address "what" questions and then address "how" questions. I.e., first determine the functionality the system is to provide without consideration of implementation constraints and then consider how to take this abstract description and refine it into an implementable design and code given constraints such as technology and budget. Modeling enables this by allowing abstract descriptions of processes and objects that define their essential structure and behavior.
Object-oriented modeling is typically done via use cases and abstract definitions of the most important objects. The most common language used to do object-oriented modeling is the Object Management Group's Unified Modeling Language (UML)

RSS

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

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