Difference between Structured Analysis and Object Oriented Analysis? Structured Analysis treats processes and data as separate components versus object-oriented analysis combines data and the process that act on the data into objects.

What is Target or Goal Oriented Analysis? The concept of goal orientation (GO) was developed to describe variability in dispositional or situational goals preferences that an individual implicitly sets for him/herself in achievement situations. GOs assist in providing a motivational framework for how individuals perceive, interpret, and judge reaction to key events in their lives. Empirical research on GOs has shown non-trivial effects on a broad range of outcomes such as task-specific self-efficacy, learning strategies, feedback seeking, and state

What is UML? Executable UML, often abbreviated to xtUML [1] or xUML [2], "is a single language in the UML family, designed ... to define the semantics of subject matters precisely."[3] Executable UML is the evolution of the Shlaer-Mellor method[4] to UML. Executable UML is a profile[5] of the UML, that graphically specifies a system "at the next higher level of abstraction, abstracting away both specific programming languages and decisions about the organization of the software."[6] The models are testable, and can be compiled into a less abstract programming language to target a specific implementation.[4][7] Executable UML supports MDA through specification of platform-independent models, and the compilation of the platform-independent models into platform-specific models.[8]

What is the Waterfall Model? The waterfall development model originates in the manufacturing and construction industries; highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development. The first formal description of the waterfall model is often cited as a 1970 article by Winston W. Royce,[1] though Royce did not use the term "waterfall" in this article. Royce presented this model as an example of a flawed, non-working model (Royce 1970). This, in fact, is how the term is generally used in writing about software development—to describe a critical view of a commonly used software practice.[2]

What is Software Lifecycle? An Enterprise Life Cycle integrates the management, business, and engineering life cycle processes that span the enterprise to align its business and IT activities. Enterprise Life Cycle refers generally to an organization’s approach for managing activities and making decisions during ongoing refreshment of business and technical practices to support its enterprise mission. These activities include investment management, project definition, configuration management, accountability, and guidance for systems development according to a System Development Life Cycle (SDLC). The Enterprise Life Cycle applies to enterprise-wide planning activities and decision making. By contrast, a System Development Life Cycle generally refers to practices for building individual systems. Determining what systems to build is an enterprise-level decision.

What is Software Prototype Model? Software prototyping, refers to the activity of creating prototypes of software applications, i.e., incomplete versions of the software program being developed. It is an activity that occurs during certain software development and is comparable to prototyping as known from other fields, such as mechanical engineering or manufacturing.

What is Software Spiral Model? The spiral model is a software development process combining elements of both design and prototyping-in-stages, in an effort to combine advantages of top-down and bottom-up concepts. Also known as the spiral lifecycle model (or spiral development), it is a systems development method (SDM) used in information technology (IT). This model of development combines the features of the prototyping model and the waterfall model. The spiral model is intended for large, expensive and complicated projects.

What is Software Object-Oriented Model? Object-oriented software engineering (OOSE) is an object modeling language & methodology OOSE was developed by Ivar Jacobson in 1992 while at Objectory AB. It is the first object-oriented design methodology to employ use cases to drive software design. It also uses other design products similar to those used by OMT. It was documented in the 1992 book Object-Oriented Software Engineering: A Use Case Driven Approach, ISBN 0-201-54435-0 The tool Objectory was created by the team at Objectory AB to implement the OOSE methodology. After success in the marketplace, other tool vendors also supported OOSE. After Rational Software bought Objectory AB, the OOSE notation, methodology, and tools became superseded.

What is Software Assembly Model? Assembly Modeling is technology and methods used by Computer-aided design and Product visualization computer software systems to handle multiple files that represent components within a product. The components within an assembly are represented as solid or surface models.

What is Software Mixed Model? A mixed model is a statistical model containing both fixed effects and random effects, that is mixed effects. These models are useful in a wide variety of disciplines in the physical, biological and social sciences. They are particularly useful in settings where repeated measurements are made on the same statistical units, or where measurements are made on clusters of related statistical units.