Conceptualization

• Every project begins with a rough idea or concept. This idea must be proposed, channeled through the appropriate decision makers then prioritized. If the idea has merit, resources are allocated and a new software project begins.
  
  

Analysis

• To transform an idea or concept into software, someone has to set the scope of the project, determine the basic features, how it fits within the current business processes and weigh the cost of the project against the benefits achieved. In large, formal projects, analysis may include feasibility studies, requirements analysis and/or business process analysis. In a smaller project, the developer may just sit down with a staff member and discuss needs.
  
  

Design

• Before programming begins, the analysis is converted into a general design that addresses the technologies needed, the overall structure of the programs, the major components, data storage, security and other design factors. If this is a large project that includes a number of developers and a large scope of work, the design will include a project plan with schedules, a timeline, budget and tasks.
  
  

Programming

• Once the design is in place, programming begins. Most Visual Basic developers use a circular approach in which the phases are not strictly defined. Each cycle combines analysis, design and programming, resulting in a new set of features that can be reviewed with the business staff. This periodic review ensures that the work meets the staff's needs without going off track.
  
  

Testing

• Testing ensures that the program performs all features determined during the analysis phase and that the program works correctly. In large projects, this may involve formal test plans, running through a variety of test cases.
  
  

Deployment

• After software is built and tested, it has to be released to those who will use it. This may be as simple as uploading it to a Web server or installing it on workstations. For larger projects, it may involve migrating legacy data, installing new hardware or contracting hosting services.
  
  

Maintenance

• Once the software gets released, the difficult work begins. Business requirements always change and the software has to change to meet these needs. As hardware platforms change, databases are upgraded and new projects interface with current systems, the program grows and changes to meet these needs.
  
  

Abandonment

• At some point every software project ends. New technologies arise that make programs obsolete or requirements change so drastically that a rewrite is required. When this occurs, the process starts all over again with a new software development life cycle.