Content Integration Manager Functional Product Specification

Write Quick, Inc.
NONDISCLOSURE AGREEMENT

(Scroll down to Accept or Cancel)

You should carefully read the following terms and conditions before opening this package. By opening this package you indicate your acceptance of these terms and conditions. If you do not agree with them, promptly return the package unopened. Thank you.

Recipient agrees as follows:
1. Restrictions on Use and Disclosure. Recipient shall: (i) protect the Document by using the same degree of care, but not less than a reasonable degree of care, to prevent the unauthorized use, dissemination or publication of the information contained therein as the Recipient uses to protect its own or any other party’s confidential or proprietary information; (ii) not copy, reproduce, create derivative works from, or use for competitive purposes any of the information contained in the Document; and (iii) not directly or indirectly disclose the existence, content, and/or substance of any of the information contained in the Document to any third party without specific written direction or consent of a duly authorized representative of Write Quick, Inc.

2. Ownership/No Warranty. All materials within shall be and remain the property of Write Quick, Inc.; this Agreement does not grant or confer any rights by license or otherwise, expressly or impliedly, to Recipient. The information in the Document is delivered “AS IS”, and all representations or warranties, whether express or implied, including warranties or conditions for fitness for a particular purpose, merchantability, title and non-infringement are hereby disclaimed.

3. Breach. In the event of Recipient’s breach or threatened breach of any of the provisions hereof, an action at law for damages would not be adequate to protect the rights of Write Quick, Inc. Therefore, in the event of a breach or threatened breach Write Quick, Inc. shall be entitled to injunctive and/or other equitable relief to prevent a breach thereof and to secure enforcement, which shall be in addition to any other rights of Write Quick, Inc.

4. No Assignment/Survival. Recipient shall not have the right to assign this Agreement (or any portion hereof) or disclose the information contained in the Document to any assignee or potential assignee without the prior written consent of Write Quick, Inc. Obligations created herein shall survive change or termination of the parties’ business relationship.

5. Miscellaneous. This Agreement contains an agreement between Write Quick, Inc. and Recipient concerning the information contained in the Document. No change, modification, waiver, or alteration of this Agreement shall be binding on Write Quick, Inc. unless approved by it in writing. This Agreement and all terms and conditions hereof shall be construed and in all respects governed by the internal substantive laws of the State of California. The parties understand that nothing herein requires either party to proceed with any proposed transaction or relationship in connection with which information in the Document may be disclosed. The act of opening the enclosed sealed envelope containing the Document shall be considered acceptance of these terms. If you do not so agree, please return the envelope unopened to Write Quick, Inc.

Write Quick, Inc.
110 Grant Avenue, Petaluma, CA 94952

By clicking on Accept you agree to abide by this agreement.

To view the Content Integration Manager Functional Product Specification, click the image below. (Document opens in new browser tab/window.)

Confidentiality Note: Permission has been granted to include this document in the Write Quick portfolio.

Audience

This document is for software engineering team members who are adding a component to the Location Services infrastructure.

Purpose

Working with the Product Designer, I was the co-author of this functional specification. (The engineering department was short-staffed, and since I had been doing software development so recently, I was tapped to “help out.”) The architects and designers had a bare-bones outline, and the planned component was similar to a previously developed component whose spec served as source material for this doc. As well, I received Entity Relationship Diagrams (ERDs) from the database designers, and then dug into the details to correlate the data with how the prototype (to which I had access) functioned. The posted version is an in-progress version that contains many flagged (in bold pink) questions for the architects to answer.

Comments

Shortly after this version, the spec was returned to engineering control, where it was completed. The team was especially pleased to include answers to the many issues and omissions that I’d noted.