Basic Protocal showing Processes in requirement specification in Software Developement

The processes of requirements analysis and requirements specification are key in any software project development You are required to write a full review of these areas and develop and test a basic protocol to control these processes. You should present your test results, and make any conclusions as to the practicality of your protocols. **I NEED BOTH THE PARTS... (1) WRITTEN EXPLANATORY MATERIAL ON THE processes of requirements analysis and requirements specification.. (2) BASIC AND SIMPLE PROTOCOL in any suitable platform TO CONTROL THESE ABOVE MENTIONED PROCESSES.. ** ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Windows XP / Vista