Je pense en Java, Java is fun

Original article:
Best practices for software development projects

Highlight résumé :

1. Development process
   There are several choices, including the Rational Unified Process (RUP), IBM® Global Services Method, and eXtreme Programming (XP). Having a process is better than not having one at all, and in many cases it is less important on what process is used than how well it is executed.
   Recommended books:
   • Ambler, Scott and Constantine, Larry, The Unified Process Inception Phase, ISBN 1929629109
   • Ambler, Scott, The Unified Process Elaboration Phase, ISBN 1929629052
   • Ambler, Scott and Constantine, Larry, The Unified Process Construction Phase, ISBN 192962901X
   • Ambler, Scott and Constantine, Larry, The Unified Process Transition and Production Phases, ISBN 157820092X
2. Requirements
   Quality requirements are broken up into two kinds: functional and non-functional. A good way to document functional requirements is using Use Cases.
   Recommended reading:
   • Writing Quality Requirements
   • non-functional requirements checklist on the Construx Web site

   Recommended books:

   • Armour, Frank and Miller, Granville, Advanced Use Case Modeling, ISBN 0201615924
3. Architecture
   Recommended books:
   • Gamma, E., Helm, R., Johnson, R., and Vlissides, J., Design Patterns, ISBN 0201633612
   • Grand, Mark, Patterns in Java, ISBN 0471258393
   • Marinescu, Floydd, EJB Design Patterns, ISBN 0471208310
   • Alur, D., Crupi, J., Malks, D., Core J2EE Patterns, ISBN 0130648841

   And do NOT forget: antipatterns

4. Design
   The two basic principles here are “Keep it Simple” and information hiding. For many projects, it is important to perform Object-Oriented Analysis and Design using UML.
   Recommended books:
   • Booch, G., Rumbaugh, J., and Jacobson, I., The Unified Modeling Language User Guide, ISBN 0201571684
   • Larman, Craig, Applying UML and Patterns, ISBN 0130925691

   Recommended reading:

   • A Realistic Look at Object-Oriented Reuse, a résumé for quick read is here
5. WebSphere application design
6. Construction of the code
7. Peer reviews
   Experience has shown that problems are eliminated earlier this way and reviews are as effective or even more effective than testing.
   Recommended reading:
   • Seven Deadly Sins of Software Reviews, a résumé for quick read is here
8. Testing
   It is also important that testing is done proactively; meaning that test cases are planned before coding starts, and test cases are developed while the application is being designed and coded.
   Recommended reading:
   • Plan Your Testing, a résumé for quick read is here
   • Software Testing Patterns
9. Performance testing
   One method to catch some architectural defects is to simulate load testing on the application before it is deployed and to deal with performance issues before they become problems.
   Recommended reading:
   • Surviving Performance Fire Drills
10. Configuration management
    Recommended reading:
    • High-level Best Practices in Software Configuration Management

    Recommended books:

    • Stephen P. Berczuk, Brad Appleton Software Configuration Management Patterns: Effective Teamwork, Practical Integration, ISBN 0201741172
11. Quality and defects management
    By using defect tracking, it is possible to gauge when a project is ready to release.
    Recommended reading:
    • Gauging Software Readiness With Defect Tracking
12. Deployment
13. System operations and support
14. Data migration
15. Project management
16. Measuring success

Automation for the people: Improving code with Eclipse plugins

Dans son article Hybridizing Java Bruce Eckel argumente sur les faiblesses de Java et le future de Flex. Il propose une solution hybride: Flex pour le UI et Java pour le back-end (métier).

A lire absolument !

A lire absolument : The Top 10 Attributes of a Great Programmer

Voici un résumé:
1. Being a great problem solver.
2. Being driven and lazy at the same time.
3. Ability to understand other people’s code
4. Having a passion for programming
5. Loving learning for the sake of learning
6. Being good at math
7. Having good communications skills
8. Strong debating skills
9. Extreme optimism
10. Extreme pessimism

Une idée intéressante: How do you become an Architect?
N’oubliez pas de lire les commentaires !

The Pragmatic Programmers Tips

Ce n’est pas pour faire la pub, mais je trouve la solution de SmartClient intéressante et surtout assez complète.

Est-ce qu’il y a une entreprise française qui utilise leur solution ???