Dealing With an IT Scourge: Process Documentation  

In this article, we outline how IT analysts can effectively make determinations about the value of process documentation, and in the process, transform a potential scourge into a possible blessing.

Schiesser, Rich. TechRepublic (2005). Articles>Documentation>Programming>Project Management

A Gentle Introduction to Object-Oriented Programming  

Object-oriented (OO) programming helps writers and programmers use real-world paradigms. By understanding some basic terminology of OO (classes, instances, and messages), the writer can feel more at ease with OO concepts. A glossary and suggestions for further reading are included.

Chacko, Rajah Y. STC Proceedings (1994). Articles>Project Management>Programming

Getting Started in the Expert System Development Game  

To dispel some of the myths of Expert Systems and explain their rise as a new documentation tool in the computer industry today, we offer this historical and current market overview.

Lohmann, Joan F., Lory Hawkes, Margot B. Casey and Elinor L. Knodel. STC Proceedings (1996). Articles>Knowledge Management>Programming

The New Breed of Version Control Systems

CVS, part of the glue that holds open source development together, is showing its age. Many competitors have emerged recently, fixing misfeatures and adding new ideas. Shlomi Fish explores several current open source version control systems that may be better than CVS for your needs.

Fish, Shlomi. O'Reilly and Associates (2004). Articles>Content Management>Programming>Databases

RUP and Goal-Directed Design: Toward a New Development Process

Interaction design methodologies, such as Goal-Directed Design, tackle the software development process from the top down by defining specific product requirements and interface behavior based on research and user needs. The Rational Unified Process (RUP) and other agile programming methodologies attack software development from the bottom up. RUP creates fluid efficiencies for iterating product development during the construction phase in order to react to changing product requirements while still producing shipping code.

Cronin, Dave. Cooper Interaction Design (2003). Articles>Project Management>Programming

Smart and Lazy Software Development

Smart and energetic people believe 'Never put off till tomorrow what you can do today.' Smart and lazy people say 'Never do today what you can put off till tomorrow!' This is, to me, one of the most useful tenets from the eXtreme Programming movement.

Ferlazzo, Ellen Lawson. Sprezzatura Systems (2002). Articles>Management>Programming

When Requirements Collide

Could it be that not every set of business requirements has the customer's best interest in mind? Karl Wiegers had always believed that implemented software functionality should enable users to accomplish their goals and help the business achieve its objectives. But a recent experience with a less-than-helpful parking meter system suggested to him that conflicts sometimes might exist between business and user requirements.

Wiegers, Karl E. StickyMinds (2007). Articles>Project Management>Programming

The Business Analyst in Model-Driven Architecture

From a software development viewpoint, model-driven architecture (MDA) encourages efficient use of system models. It also encourages reusing best practices as families of systems are produced. One of the main aims of MDA is to separate design from architecture, which places the business analyst in a unique and potentially powerful position within the organization. Learn how you as a business analyst can take an active role in this type of architecture.

Slack, S.E. IBM (2008). Articles>Information Design>Programming>Project Management

Content Management System APIs

Panellists talk about two vendor-neutral programming interfaces for content-management systems. Joel Amoussou discusses JSR 170, a vendor-neutral Java API designed to work across many different content management systems. Michael Wechner discusses Neutron, an Open Content Management User Interface based on XML.

Amoussou, Joel and Michael Wechner. XML 2006 (2006). Articles>Content Management>Programming>XML

What APIs Can Tell You About a Product

I always try to get a look at a vendor's APIs before (or in the process of) evaluating a product. And I recommend you do, too. If you are involved in a product-selection effort, get input from your developers -- have them evaluate APIs as part of the product-evaluation process. Don't wait until after the deal is inked to find out whether the product's APIs are so problematic that your rollout schedule might have to undergo serious changes.

assertTrue (2009). Articles>Content Management>Programming>Collaboration

Hone Your Regexp (Regular Expression) Pattern-Building Skills

Add to your bag of tricks several handy techniques for crafting real-world regular expressions (regexps). Building regexps is a part of the daily life of any administrator. Learning to think in terms of pattern matching, in order to construct successful regexps that return the desired criteria, is a skill that takes both time and practice.

Stutz, Michael. IBM (2006). Articles>Content Management>Programming

Coding Horror: A Modest Proposal for the Copy and Paste School of Code Reuse

If you use copy and paste while you're coding, you're probably committing a design error. Instead of copying code, move it into its own routine. Future modifications will be easier because you will need to modify the code in only one location.

Atwood, Jeff. Coding Horror (2009). Articles>Content Management>Programming

Follow the Recipe

Following a software design process can offer the same kinds of benefits you gain from following a recipe when cooking: getting reliable results. For example, if I have a recipe for gingerbread, but I don’t follow the recipe, should I still expect to get gingerbread? It depends, of course, on how much I choose to deviate from the recipe.

Gagnier, Ron. UXmatters (2009). Articles>Project Management>Programming

From Drawing Board to Working Code: Software in the Real World

Some of my designs never make it to market due to lack of funding prior to release and the company slips quietly away or gets bought and I lose contact. Other times by the time the software is released, the person who hired me has left the company and moved onto other pastures. So it's always a treat when someone calls me back to say "Would you like to come in and see the software? We're nearly done."

Sprezzatura Systems (2007). Articles>Project Management>Programming>Case Studies

Symphony or Jazz Band Metaphor for Software Development

One of the online lists I read frequently has been debating the proper metaphor for the software development environment. The building trade has been used quite often in the past. In fact, we use the term "architect" quite frequently, although ten software engineers will probably give you ten different definitions of what an architect actually should do. I think there is no single metaphor for software development roles because there is not a single software development environment.

Sprezzatura Systems (2007). Articles>Project Management>Programming