The Artima Developer Community
Sponsored Link

Java Buzz Forum
Core Software Processes

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Bill de hÓra

Posts: 1137
Nickname: dehora
Registered: May, 2003

Bill de hÓra is a technical architect with Propylon
Core Software Processes Posted: May 27, 2004 7:04 AM
Reply to this message Reply

This post originated from an RSS feed registered with Java Buzz by Bill de hÓra.
Original Post: Core Software Processes
Feed Title: Bill de hÓra
Feed URL: http://www.dehora.net/journal/atom.xml
Feed Description: FD85 1117 1888 1681 7689 B5DF E696 885C 20D8 21F8
Latest Java Buzz Posts
Latest Java Buzz Posts by Bill de hÓra
Latest Posts From Bill de hÓra

Advertisement
Programming Building Designing Testing Delivering Versioning Changing Automating Many folks focus only on the first two, usually because their working envionment dictates it. The third, designing, is often outsourced to a specialist role (the architect). XP, TDD and other agile appoaches have helped us remember the value of 4, testing. Delivery, versioning and change - not everyone will think these are core practices - often they seem "happen" to us as a result of working on a project over a long enough time. Automation encompasses the special definition of "laziness" programmers develop. Many programmers pride themselves on their laziness which may sound odd if you're not from a programming background; they're talking about cultivating an efficient and effective mindset to problem solving. Here's the point. The processes are not something that should be serialized in time order. They should as much as possible be done continuously. If you're used to RUP you should agree with this in principle, with the caveat that at certain times we're emphasizing a particular process more than others. Exclusive focus however and we're back to the descredited waterfall model of development where processes are entirely serial ("let's stop for a week to clean the code up", "let's not write any code until we design the architecture", "let's not do any testing until we deliver the code"). Don't go there. The RUP encourages us to iterate the processes, agile methods want to speed this up to the point where the interleaving is effectively morphed into parallel processing. Any approach that tries to parallelize the processes can be called "concerted". Anybody who is effective in their process can be deemed "excellent". By the way there's no point just talking about processes - these are things that you do. You might start out being weak at them, but that's not a reason not to start. You get good at a process by practice, not by analysis - analysis is for deciding what the processes are. The purpose of constant practice is to push the processes out of your consciousness and into your second nature. So you're freed up to act on the problem at hand in the most effective way. [tom petty: freefallin']...

Read: Core Software Processes

Topic: Windows, Java, Linux, ... Previous Topic   Next Topic Topic: New IT-eye website

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use