Object Oriented Analysis in real world

  • 6 August 2015
  • admin

There is a lot more to succeeding with OOA than mastering the modeling techniques. Some of it is just good project management practices. Some of it is just good analysis practices. Some of it has to do with the process of introducing a new engineering discipline into an organization. Some of it has to do with the general, object-oriented approach of OOA. And some of has to do with application of the specific OOA modeling techniques. If the issues in all of these areas are actively tracked and addressed, the chances of success are greatly enhanced.

OOAD Modelling

  • 6 August 2015
  • admin

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:

OCUP certification

  • 6 August 2015
  • admin

OCUP is a rigorous, comprehensive, and fair test of a person’s knowledge of OMG’s specifications for unified modeling language. The worldwide UML Certification Program provides an objective measure of your UML 2.x Specification knowledge. OCUP Certification will benefit you by giving you an important documentation topresent to employers and clients. It also benefits 

Unified Modeling Language (UML)

  • 6 August 2015
  • admin
Unified Modeling Language (UML) combines techniques from data modeling (entity relationship diagrams), business modeling (work flows), object modeling, and component modeling. It can be used with all processes, throughout the software development life cycle, and across different implementation technologies.[2]
The Unified Modeling Language (UML) offers a standard way to visualize a system's architectural blueprints, including elements such as:
business processes
database schemas

Basics of Object Orientation.

  • 6 August 2015
  • admin
Object-oriented systems
An object-oriented system is composed of objects. The behavior of the system results from the collaboration of those objects. Collaboration between objects involves them sending messages to each other. Sending a message differs from calling a function in that when a target object receives a message, it decides on its own what function to carry out to service that message. The same message may be implemented by many different functions, the one selected depending on the state of the target object.
The implementation of "message sending" varies depending on the architecture of the system being modeled, and the location of the objects being communicated with.
Object-oriented analysis
Object-oriented analysis (OOA) is the process of analyzing a task (also known as a problem domain) to develop a conceptual model that can then be used to complete the task. A typical OOA model would describe computer software that could be used to satisfy a set of customer-defined requirements. During the analysis phase of problem-solving, the analyst might consider a written requirements statement, a formal vision document, or interviews with stakeholders or other interested parties. The task to be addressed might be divided into several subtasks (or domains), each representing a different business, technological, or other areas of interest. Each subtask would be analyzed separately. Implementation constraints, (e.g., concurrency, distribution, persistence, or how the system is to be built) are not considered during the analysis phase; rather, they are addressed during object-oriented design (OOD).
The conceptual model that results from OOA will typically consist of a set of use cases, one or more UML class diagrams, and a number of interaction diagrams. It may also include some kind of user interface mock-up.
Object-oriented design
Main article: Object oriented design from wikipedia.org
During object-oriented design (OOD), a developer applies implementation constraints to the conceptual model produced in object-oriented analysis. Such constraints could include not only constraints imposed by the chosen architecture but also any non-functional – technological or environmental – constraints, such as transaction throughput, response time, run-time platform, development environment, or those inherent in the programming language. Concepts in the analysis model are mapped onto implementation classes and interfaces resulting in a model of the solution domain, i.e., a detailed description of how the system is to be built.
Source: Wikipedia.org