provide and improving to success your software development project

fact in last year, most software project fail.

80 % because : [over budget, late, missing function]

30 % because : [poorly execute then canceled before comletion]




factor that help improve the sucess of your project



1. DEVELOPMENT PROCESS

I t is important to choose the appropriate dev elopment lifecycle process to the project at hand because all other activ i ties are derived from the process.



2. REQUIREMENTS

Gathering and agreeing on requirements is fundamentalto a successfulproject. This does not necessari ly imply that allrequirements need to be fixed before any architecture, design, and coding are done, but it is important for the development team to understand what needs to be built.



3. ARCHITECTURE

Choosing the appropriate archi tecture for your application is key.



4. DESIGN

Even with a good architecture it is stillpossible to have a bad design. Many applications are either over-designed or under-designed. The two basic principles here are keep it simple and information hiding.



5. WEBSPHERE APPLICATION DESIGN

There is still a tremendous return on investment (ROI) even if you only use the consultants for a short time because you save the costs later in the project. Our experts have also published a great deal of this wisdom, including considerations for highperformance Web sites and guidel ines for autonomic computing.



6. CONSTRUCTION OF THE CODE

Construction of the code is a fraction of the total project effort, but it is often the most visible. Other work equally important includes requirements, architecture, analysis, design, and test. I n projects with no development process (so-called "code and fix"), these tasks are also happening, but under the guise of programming



7. PEER REVIEWS

It is important to review other people's work. Experience has shown that problems are eliminated earlier this way and reviews are as effective or even more effective than testing. Any artifact from the development process is reviewed, including plans, requirements, architecture, design, code, and test cases.



8. TESTING

Testing is not an afterthought or cutback when the schedule gets tight. It is an integralpart of software development that needs to be planned.



9. PERFORMANCE TESTING

Testing is usually the last resort to catch application defects. It is labor intensive and usually only catches coding defects. Architecture and design defects may be missed.



for more factors please read here ()
Full Post