Software Engineering
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .A. :-
-: Agile Software Development :-
...
-: Architecture :-
To be updated from a Data Warehouse book
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .D. :-
-: Data Warehouse :-
Bill Inmon, considered to be the father of Data Warehousing provides following defintion: "A Data Warehouse is a subject oriented, integrated, nonvolatile, and time variant collection of data in support of management's decisions."
Thus, the Data Warehouse is an informational environment that:
- Provides an integrated and total view of the enterprise
- Makes the enterprise's current and historical information easily available for decision making
- Makes decision-support transactions possible without hindering operational systems
- Renders the organization's information consistent
- Presents a flexible and interactive source of strategic information.
Data warehouse building blocks or components are: source data (external, production, internal, archived), data staging, data storage, information delivery, metadata, and management and control.
For more information, refer [1]
-: Design Pattern :-
A design pattern in architecture and computer science is a formal way of documenting a solution to a design problem in a particular field of expertise.
For more information, refer [1]
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .E. :-
-: Extreme Programming :-
...
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .O. :-
-: Object-oriented Software Design Patterns :-
Object-oriented Software Design Patterns are Design Patterns that show relationships and interactions between classes and objects, without specifying the final application classes or objects that are involved.
For more information, refer
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .S. :-
-: Software Design Pattern :-
A Software Design Pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or a template for how to solve a problem and it can be used in multiple situations. Not all software patterns are design patterns. For instance, algorithms solve computational problems rather than software design problems.
For more information, refer [1]
-: Software Engineering :-
Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software, and the study of these approaches; that is, the application of engineering to software.
For more information, refer [1], Ref: Software Engineering, A Practitioner's Approach by Roger S. Pressman
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .U. :-
-: UML (Unified Modeling Language) :-
UML is a standardized general-purpose modeling language that helps you specify, visualize, and document models of software systems, including their structure and design, in a way that meets all of these requirements. You can use UML for business modeling and modeling of other non-software systems too. UML is used to specify, visualize, modify, construct, and document the artifacts of an object-oriented software intensive system under development. It offers a standard way to visualize a system's architectural blueprints, including elements such as:
- actors
- business processes
- logical components
- activities
- programming language statements
- database schemas, and
- reusable software components
For more information, refer [1], [2], [3]
| A | B | C | D | E | F | G | H | I | J | K | L | M |
| N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
-: .Z. :-
-: ... :-
...