Level 7 Level 9
Level 8

Methodologies


10 words 0 ignored

Ready to learn       Ready to review

Ignore words

Check the boxes below to ignore/unignore words, then click save at the bottom. Ignored words will never appear in any learning session.

All None

Ignore?
Requirements analysis
tasks that go into determining the needs or conditions to meet for a new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements.
Use case
a list of action or event steps, typically defining the interactions between a role (known in the Unified Modeling Language as an actor) and a system, to achieve a goa
Unified Modeling Language (UML)
a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system
Modeling language
any artificial language that can be used to express information or knowledge or systems in a structure that is defined by a consistent set of rules
Agile software development
a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.
Object-Oriented Analysis and Design (OOAD)
a popular technical approach for analyzing, designing an application, system, or business by applying the object-oriented paradigm and visual modeling throughout the development life cycles to foster better stakeholder communication and product quality.
Object-oriented programming (OOP)
a programming paradigm based on the concept of "objects", which are data structures that contain data, in the form of fields, often known as attributes; and code, in the form of procedures, often known as methods.
Software development process
a division of software development work into distinct phases (or stages) containing activities with the intent of better planning and management
Model-driven architecture (MDA)
a software design approach for the development of software systems. It provides a set of guidelines for the structuring of specifications, which are expressed as models
Entity–relationship model (ER model)
a data model for describing the data or information aspects of a business domain or its process requirements, in an abstract way that lends itself to ultimately being implemented in a database such as a relational database