Objects are memory allocation for Data held inside it at runtime. So Memory need to be allocated for objects (Creating Objects) and it need to be garbage collected or deallocated
to recover memory after that object no longer needed (Destroying Objects).
UML supports Object Oriented Analysis and Design (OOAD). It has all related concepts like classes, objects, inheritance, encapsulation, polymorphism, etc. UML is most suitable for use case driven, iterative and incremental development processes as most OOAD processes are.
System analysis and design (SA&D) and object-oriented analysis and design (OOAD) are two different approaches to the development of computer-based information systems. SA&D is a traditional approach that focuses on understanding the requirements of the system, analyzing the current system, and designing a new system that meets those requirements. It is a process-oriented approach that typically involves creating a detailed specification of the system before beginning development. On the other hand, OOAD is a modern approach that focuses on modeling the system as a collection of objects that interact with each other to achieve the desired functionality. It is a more object-oriented approach that involves designing a system by first identifying the objects in the system, their properties, and the relationships between them. Some of the key differences between SA&D and OOAD are: Focus: SA&D focuses on the process of designing a system, while OOAD focuses on the objects in the system and their interactions. Design: SA&D is typically a top-down design approach, while OOAD is a bottom-up design approach. Requirements gathering: SA&D emphasizes the gathering of requirements and creating detailed specifications before beginning development, while OOAD emphasizes rapid prototyping and iterative development. Abstraction: OOAD relies heavily on abstraction, while SA&D relies more on specific details and processes. Overall, both SA&D and OOAD are valid approaches to the development of computer-based information systems, and the choice between them depends on the specific needs and requirements of the project.
No, you can be a creator without destroying stuff. You can create a death machine, but that doesn't mean you destroy stuff. Technically, your creating is doing the destroying.
Any time money
Over 9000!
true
by creating class as an static class
Nature of an object represents the state,behaviour and identity
-[objects bar -[function for creating a table object -[an existing table
Money is attained by destroying Government Property such as buildings and creating CHAOS
The buildings are destroying the sacred religious areas of Jerusalem.
Model.