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.
Katherine Johnson’s mathematical calculations helped guide some of America’s most important early space missions while she confronted the racial and gender barriers faced by Black women in twentieth-century America.
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. (October 2008) |
A lightweight methodology is a software development method that has only a few rules and practices, or only ones that are easy to follow. In contrast, a complex method with many rules is considered a "heavyweight methodology".[1]
Examples of lightweight methodologies include:
Most of these lightweight processes emphasize the need to deal with change in requirements and change in environment or technology by being flexible and adaptive.
Source: Wikipedia. Article content is retrieved live through the MediaWiki API.
A lightweight methodology is a software development method that has only a few rules and practices, or only ones that are easy to follow. In contrast, a complex method with many rules is considered a "heavyweight methodology". Examples of lightweight methodologies include: Adaptive Software Development by Jim Highsmith, described in his 1999 book Adaptive Software Development Crystal Clear family of methodologies with Alistair Cockburn, Extreme Programming (XP), promoted by people such as Kent Beck and Martin Fowler Feature Driven Development (FDD) developed (1999) by Jeff De Luca and Peter Coad ICONIX process, developed by Doug Rosenberg: An UML Use Case driven approach that purports to provide just enough documentation and structure to the process to allow flexibility, yet produce software that meets user and business requirements Most of these lightweight processes emphasize the need to deal with change in requirements and change in environment or technology by being flexible and adaptive.
Jeff De Luca is a global information technology strategist and an author in the field of software development methodology. He is considered the primary architect of Feature Driven Development (FDD) circa 1999 [^JDLBIO], a lightweight methodology for developing computer software with reduced management overhead, time and money. In 1999, Jeff De Luca co-authored Java Modeling In Color With UML (1999, ISBN 0-13-011510-X), along with Peter Coad and Eric Lefebvre. Jeff De Luca was born in 1964. Although Jeff dropped out of secondary school (high school), and did not start with a college degree, he learned, on-the-job, working for years with programmers and designers at IBM in Melbourne, Australia and transferred with IBM to the United States in Raleigh, North Carolina (^JDLBIO). At the IBM Rochester Minnesota Programming Laboratory, Jeff developed network software to connect different types of IBM computer systems, and continued learning at IBM for those 11 years. He had begun in the mailroom: in 1981, aged 17, he had left school and started working at IBM, Melbourne, as the mailroom clerk. Jeff resigned from IBM in 1993, as a senior systems strategist. After IBM, Jeff formed his own consultancy company, Nebulon Pty Ltd, based in Melbourne, Australia, and developed extensive, complex software systems using the Java technology (with the programming language), object-modelling in UML, and FDD.
Lightweight software test automation is the process of creating and using relatively short and simple computer programs, called lightweight test harnesses, designed to test a software system. Lightweight test automation harnesses are not tied to a particular programming language but are most often implemented with the Java, Perl, Visual Basic .NET, and C# programming languages. Lightweight test automation harnesses are generally four pages of source code or less, and are generally written in four hours or less. Lightweight test automation is often associated with Agile software development methodology. The three major alternatives to the use of lightweight software test automation are commercial test automation frameworks, open source test automation frameworks, and heavyweight test automation. The primary disadvantage of lightweight test automation is manageability. Because lightweight automation is relatively quick and easy to implement, a test effort can be overwhelmed with harness programs, test case data files, test result files, and so on. However, lightweight test automation has significant advantages. Compared with commercial frameworks, lightweight automation is less expensive in initial cost and is more flexible. Compared with open source frameworks, lightweight automation is more stable because there are fewer updates and external dependencies. Compared with heavyweight test automation, lightweight automation is quicker to implement and modify. Lightweight test automation is generally used to complement, not replace these alternative approaches. Lightweight test automation is most useful for regression testing, where the intention is to verify that new source code added to the system under test has not created any new software failures. Lightweight test automation may be used for other areas of software testing such as performance testing, stress testing, load testing, security testing, code coverage analysis, mutation testing, and so on. The most widely published proponent of the use of lightweight software test automation is Dr. James D. McCaffrey.
The Hipster PDA is a paper-based personal organizer, popularized by Merlin Mann in 2004. Originally a tongue-in-cheek reaction to the increasing expense and complexity of personal digital assistants (PDA), the Hipster PDA (said to stand for "Parietal Disgorgement Aid" and often abbreviated to "hPDA") comprises a sheaf of index cards held together with a binder clip. Following widespread coverage in the media and blogs, the hPDA became a popular personal management tool, particularly with followers of David Allen's Getting Things Done methodology. Although it began as a joke, or perhaps a statement about technology fetishism, the Hipster PDA rapidly gained popularity with serious users, with hundreds posting pictures of their customized hPDAs on photo sharing sites and exchanging tips on Internet mailing lists. Advocates of the hPDA claim that it is a cheap, lightweight, freeform organizer that does not need batteries and is unlikely to be stolen. Enthusiasts also design and share index-card-size printable templates for storing contacts, to-do lists, calendars, notes, project plans, and so on. A Hipster Nano PDA uses business cards with blank backs and one that has a calendar on the back.
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 →Mae Jemison, aboard Space Shuttle Endeavour in 1992.