Civil Rights
Movements, leaders, victories and the continuing fight for equality.
q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
Explore the people, places, events, achievements, struggles and stories that shaped our journey.
Movements, leaders, victories and the continuing fight for equality.
Innovation, patents, science, technology and world-changing contributions.
Pioneers, champions, Negro Leagues, records, activism and excellence.
Meet the people whose lives, choices and achievements shaped the journey.
Black towns, communities, institutions and places where history happened.
Moments that changed communities, movements, institutions and the nation.
In August 1908, a white mob attacked Springfield, Illinois’s Black community, destroying homes and businesses and lynching two Black men. National outrage over the violence helped spur the movement that created the NAACP the following year.
MORE →Reflects the personal views, recollections, and perspective of the author, Mike Davis.
This is a personal recollection on the Move fire on May 13, 1985
 | This article needs more citations. (July 2019) |
Object-oriented modeling (OOM) is an approach to modeling a system as objects. It is primarily used for developing software, but can be and is used for other types of systems such as business process. Unified Modeling Language (UML) and SysML are two popular international standard languages used for OOM.[1]
For software development, OOM is used for analysis and design and is a key practice of object-oriented analysis and design (OOAD). The practice is primarily performed during the early stages of the development process although can continue for the life of a system. The practice can be divided into two aspects: the modeling of dynamic behavior like use cases and the modeling of static structures like classes and components, generally as visual modeling diagrams.
The benefits of using OOM include:
The notation used for modelling is a language of graphical elements that imply design based on convention. Many conventions have been devised and they vary in formality. It may be relatively informal in nature, or consist of predefined graphical templates or consist of a formally defined grammar.
A modeling language is often associated with an object-oriented software development methodology since a methodology often spawns a language. The modeling language defines the elements of a model, such as classes, methods, properties, etc. The methodology defines the steps developers take to create and maintain a software system in relation to the models. For example, the Booch method may refer to Grady Booch's standard for diagramming, his methodology, or both. Or the Rumbaugh Object Modeling Technique is both a set of diagrams and a process model for developing object-oriented systems.
In the early years of the object-oriented development there were several competing modeling and methodology variants. Booch and Rumbaugh were two of the most popular, and Ivar Jacobson's Objectory, Shlaer-Mellor, and Yourdon-Coad were also popular. Starting in the mid-1990s, efforts began to harmonize modelling languages—to reconcile the leading models and focus on one unified specification. The graphic shows the evolution of and adoption of the Unified Modeling Language (UML).
If it weren't for the dominance that UML has gained over the industry, MDA and related modeling standards couldn't even exist.
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
Object-oriented modeling (OOM) is an approach to modeling a system as objects. It is primarily used for developing software, but can be and is used for other types of systems such as business process. Unified Modeling Language (UML) and SysML are two popular international standard languages used for OOM. For software development, OOM is used for analysis and design and is a key practice of object-oriented analysis and design (OOAD). The practice is primarily performed during the early stages of the development process although can continue for the life of a system. The practice can be divided into two aspects: the modeling of dynamic behavior like use cases and the modeling of static structures like classes and components, generally as visual modeling diagrams. The benefits of using OOM include: Efficient and effective communication Users typically have difficulties understanding technical documentation and source code. Visual diagrams can be more understandable and can allow users and stakeholders to give developers feedback on the appropriate requirements and structure of the system. A key goal of the object-oriented approach is to decrease the "semantic gap" between the system and the real world, and to have the system be constructed using terminology that is almost the same as the stakeholders use in everyday business. OOM is an essential tool to facilitate this. Useful and stable abstraction Modeling supports coding. A goal of most modern development methodologies is to first address "what" questions and then address "how" questions, i.e. first determine the functionality the system is to provide without consideration of implementation constraints, and then consider how to make specific solutions to these abstract requirements, and refine them into detailed designs and codes by constraints such as technology and budget. OOM enables this by producing abstract and accessible descriptions of requirements and designs as models that define their essential structures and behaviors like processes and objects, which are important and valuable development assets with higher abstraction levels above concrete and complex source code.
Real-Time Object-Oriented Modeling (ROOM) is a domain-specific language. ROOM was developed in the early 1990s for modeling real-time systems. The initial focus was on telecommunications, even though ROOM can be applied to any event-driven real-time system. ROOM was supported by ObjecTime Developer (commercial) and is now implemented by the official Eclipse project eTrice When UML2 was defined (version 2 of UML with real time extensions), many elements of ROOM were adopted.
Object-oriented role analysis and modeling (OOram) is a method, based on the concept of role, for performing object-oriented modeling. Originally (1989) coined Object Oriented Role Analysis, Synthesis and Structuring (OORASS), the method focuses on describing patterns of interaction without connecting the interaction to particular objects/instances. OOram was originally developed by Trygve Reenskaug (1996), a professor at the University of Oslo and the founder of the Norwegian IT company Taskon. The use of "roles" in OOram is similar in application to that of agent-oriented programming. Enterprise models created according to OOram may have a number of views, with each view presenting certain aspects of a model. The following ten views are proposed: Area of concern view: Textual description of a phenomenon represented in the role model. Stimulus-response view: Describes how environment roles may trigger activities in the organization (stimulus), together with the effect (response). Role list view: List describing all roles of a role model together with attributes and textual explanation. Semantic view: Describes meaning of roles and relationships between roles. Collaboration view: Describes patterns of roles and message paths. Interface view: Describes all messages that can be sent along a message path. Scenario view: Provides a sample sequence of messages flowing between roles (a concrete example). Process view: Describes data flow between roles and associated activities performed by the roles. State diagram view: For each role, the legal states can be described together with messages that trigger transitions. Method specification view: Describes what messages to send for each method belonging to a role. May also specify procedures to perform. OOram suggests a varied mix of formal and informal notations and languages for representing and communicating models. Which view to use depends upon the needs in a particular situation.
The object-modeling technique (OMT) is an object-oriented modeling (OOM) approach for software modeling and designing. It was developed around 1991 by Rumbaugh, Blaha, Premerlani, Eddy and Lorensen as a method to develop object-oriented systems and to support object-oriented programming. OMT describes object model or static structure of the system. OMT was developed as an approach to software development. The purposes of modeling according to Rumbaugh are: testing physical entities before building them (simulation), communication with customers, visualization (alternative presentation of information), and reduction of complexity. OMT has proposed three main types of models: Object model: The object model represents the static and most stable phenomena in the modeled domain. Main concepts are classes and associations with attributes and operations. Aggregation and generalization (with multiple inheritance) are predefined relationships. Dynamic model: The dynamic model represents a state/transition view on the model. Main concepts are states, transitions between states, and events to trigger transitions. Actions can be modeled as occurring within states. Generalization and aggregation (concurrency) are predefined relationships. Functional model: The functional model handles the process perspective of the model, corresponding roughly to data flow diagrams. Main concepts are process, data store, data flow, and actors. OMT is a predecessor of the Unified Modeling Language (UML). Many OMT modeling elements are common to UML. Functional Model in OMT: In brief, a functional model in OMT defines the function of the whole internal processes in a model with the help of "Data Flow Diagrams (DFDs)". It details how processes are performed independently.
Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.
MORE →Joe Louis.