1. Planning Before you want to jump right into planning, you want to meet with your client to talk about the project, you want to obtain certain information so that it can help you learn more about the project and whether or not the project should go ahead. Once you accept doing this project, you want to make sure that the client knows the requirements you’re looking for and whether they will meet your standard. For example, your payment estimates for future stages of the project. Make it clear when you are letting your client know how much you want to receive. For example it cost ‘$X’ per ‘Y’ hours. This will allow the client to consider if you’re doing the project or not. Once the client has approved you doing this project and wants to …show more content…
• Does the client upgrade all users at once, or do they support various versions of the product? • What’s the environment in which this product will be used? • What are the client’s upgrade, updates, and post-development support needs? You want to carefully examine existing ordering systems and how to utilize the best aspects of those systems, while taking advantage of the potential benefits of more centralized systems. You would look at how the various departments might receive a new central ordering system and how costly the new system would be relative to improving each of these individual systems. 1. Analysis In the analysis phase, identified requirements of the system will be gathered. You want to conduct an examination on a specific problem that is being addressed or expectations of a particular system that has been told by a client. In this phase it will articulate what the system is supposed to do, it will carefully . In other words, analysis will articulate what the system is supposed to do. For the central ordering system, the analysis would carefully examine existing ordering systems and how to utilize the best aspects of those systems, while taking advantage of the potential benefits of more centralized