A project on Invisible digital Watermarking

I need a project on Invisible digital watermarking. I need the algorithm, the source code, and its output after execution. I also need comments for every line of he source code. I need even written documents of the project. The following is the information needed and are all mentioned in the buyer templates of the rentacoder website. I need everything according to the website rules. Problem/Opportunity Statement - Defines the problems and/or opportunities that have created a need for this project. Objectives - Defines a list of goals associated with this project. Completion of the project should fulfill these goals. Functionality - Defines a list of high-level functionality that the project should be able to offer at its completion. · Exclusions - Defines a list of functionality, objectives, or actions that will be expressly excluded from the project. · Assumptions - Defines a list of assumptions that you are making about the project in order to communicate them and get widespread agreement at the beginning of the project. · Constraints - Defines a list of the constraints that may hinder progress in order to communicate them and get widespread agreement at the beginning of the project. · Benefits - Defines a list of the tangible and intangible benefits the project offers to the customer. Benefits are quantified whenever possible. · Risks - Defines a list of business and general technical risks related to the project. · Additional References - Defines what other documentation and/or other relevant reference materials: ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased. 4)The following information is from the rentacoder websiteare,which I need. You can view from the website, buyer templates, Please see that I get evrything as mentioned in the buyer templates. Table of Contents Revision History Business Process Flow / Overview Dependencies 5 Current Business Flow Diagram 5 Proposed Business Flow Diagram 5 Information Flow Current System Context Diagram 5 Proposed System Context Diagram 6 Business Requirements Security Requirements 6 Performance Requirements 6 Availability Requirements 6 System Requirements and Processing Rules Technical Services Impact Statement 7 System Environment Needs 7 Questions 7 Network Needs 8 Backup and Recovery Needs 8 Storage Capacity Needs 8 Telecommunications Load 8 Solution Alternatives/ Preliminary architecture diagram Solution #1: [Enter the name of the solution here] 9 Solution #2: [Enter the name of the solution here] 9 Budget and Resource Estimates Glossary Approvals Inspection Checklist for Software Requirements Organization and Completeness 12 Correctness 12 Quality Attributes 12 Traceability 12 Special Issues 12 Revision History This section records the change history of this document. Name Date Reason For Changes Version Business Process Flow / Overview This section shows the current and proposed business process diagrams. The current business process flow diagram describes the current process accurately, including any flaws that exist in today's process that will be repaired by the proposed process. The proposed business flow diagram describes the proposed process accurately. Dependencies Certain business dependencies exist that may affect the project team's ability to implement the project. These dependencies are listed below so that they can be communicated and addressed. The items listed here can affect the success of the project so they should be addressed as quickly as possible. · [Add a dependency here.] Current Business Flow Diagram [Insert diagram here] [Add any comments about the diagram here] Proposed Business Flow Diagram [Insert diagram here] [Add any comments about the diagram here] Information Flow The information in the current business system flows from one place to another with a certain context. The context of the information flow is defined by the following diagrams. The first diagram displays the context of the current system. The second diagram displays the context of the proposed system. These diagrams are a representation of how information flows from external entities to the current and proposed system. Current System Context Diagram [Insert diagram here] [Add any comments about the diagram here] Proposed System Context Diagram [Insert diagram here] [Add any comments about the diagram here] Business Requirements The business requirements describe the needs of the business. The following types of requirements must be defined fully here: · Security Requirements - Define the security measures that must apply to this product as defined by the business unit and the Security Policies and Procedures Guide. · Performance Requirements - Define the performance necessary in the product from a business perspective. · Availability Requirements - Define the timeframes during which the product must be available to meet the needs of the business. · User Requirements - Define exactly what the business wants the finished product to look and function like. Security Requirements The following security requirements must be present in the final product: ·[Insert security requirement here.] Performance Requirements ## Platform Windows operating system.