120 Part II: Planning Your Software Project With (Web hosting packages)
120 Part II: Planning Your Software Project With the completion of each phase comes a new stage, with the product of the phase transitioning (just like a waterfall) into the next phase. Here s the progression: 1. Come up with a concept. In phase one, you and the stakeholders build the concept document, which explains the goals and constraints (such as time and cost) of the project, and a rough order of magnitude estimate (ROM) is created. We discuss ROM in more detail in Chapter 9. 2. Determine the requirements. In phase two, using the concept document, the project team completes the document that details the requirements of the project deliverables. This document includes all of the systems, technologies, and technical interfaces for the deliverables. The requirements document is really the progressively elaborated version of the concept document. (How s that for jargon?) 3. Create a high-level design. You may hear the high-level design phase (phase three) referred to as the satellite point of view or the view from 20,000 feet. Whatever. The high-level phase consists of the big architectural building blocks of the software you re creating. The high-level design document defines how programmers will implement the requirements document. See an evolution here? 4. Narrow down the design to create a detailed design. Ah, now we re getting somewhere. In phase four, based on the high-level design document, you and the programmers can get into the details of how the application will be developed. The output of this phase? You guessed it: the detailed design document. 5. Code implementation phase. In phase five, it s time to follow the documents you ve created with your project team by actually coding. This phase usually includes unit testing to ensure that what s being built actually follows all the documents created up until now. 6. Testing phase. At this stage, you test the entire application to ensure that all the units are coded and working as expected before your customers see it. This is the quality control phase. If you find problems, then you ve got more work to do. The goal of this phase, of course, is to keep mistakes out of the customers hands. When all is well, the deliverable is released. At first glance this looks like a rock-solid model, and it can be. However, the risk with this model is that if changes trickle, or flood, into the project, you basically have to start over. This is because the project is founded on the original capture of the project vision, the requirements, and so on. Changes to the fundamentals can (and will) affect how the application is built. And then troubles ensue.
Note: If you are looking for best quality webspace to host and run your tomcat application check Vision shared web hosting services