Cover the specifications for the software needs and requirements of the project, presented in a top-down approach (starting with the “big picture” and breaking down from there into the smaller requirements). Remember that not all software needs are programming related. For each need or requirement, propose a software solution. You don’t have to specify the exact program you would use (for example, you could say “word processor” instead of “Microsoft Word”). You may use any requirement tracking technique or tool you like in building the requirements list. One program, platform, application, or piece of software can meet many different needs. In a separate section, you should describe how you will apply prototyping techniques and analysis tools to improve the final product. Again, this discussion should consider what, if any, tools you will need to implement prototyping. You can structure the specification however you think best, as long as it maintains a top-down perspective. Suggested formats include a flowchart style or a tiered outline. You can refer to online resources or independent research for this activity. Can someone do this project for me?