Author: Anne Gentle
Publisher: Lulu.com
ISBN: 1387081322
Category : Computers
Languages : en
Pages : 118
Book Description
Looking for a way to invigorate your technical writing team and grow that expertise to include developers, designers, and writers of all backgrounds? When you treat docs like code, you multiply everyone's efforts and streamline processes through collaboration, automation, and innovation. Second edition now available with updates and more information about version control for documents and continuous publishing.
Docs Like Code
The Office of Environmental Management Technical Reports
Author:
Publisher:
ISBN:
Category : Environmental management
Languages : en
Pages : 972
Book Description
Publisher:
ISBN:
Category : Environmental management
Languages : en
Pages : 972
Book Description
IEEE Standard for Software Project Management Plans
Author:
Publisher:
ISBN:
Category : Computer programming
Languages : en
Pages : 0
Book Description
Publisher:
ISBN:
Category : Computer programming
Languages : en
Pages : 0
Book Description
Title List of Documents Made Publicly Available
Author:
Publisher:
ISBN:
Category : Nuclear power plants
Languages : en
Pages : 640
Book Description
Publisher:
ISBN:
Category : Nuclear power plants
Languages : en
Pages : 640
Book Description
The Insider's Guide to Technical Writing
Author: Krista Van Laan
Publisher: XML Press
ISBN: 1457182424
Category : Reference
Languages : en
Pages : 512
Book Description
Every complex product needs to be explained to its users, and technical writers, also known as technical communicators, are the ones who do that job. A growing field, technical writing requires multiple skills, including an understanding of technology, writing ability, and great people skills. Whether you're thinking of becoming a technical writer, just starting out, or you've been working for a while and feel the need to take your skills to the next level, The Insider's Guide to Technical Writing can help you be a successful technical writer and build a satisfying career. Inside the Book Is This Job for Me? What does it take to be a technical writer? Building the Foundation: What skills and tools do you need to get started? The Best Laid Plans: How do you create a schedule that won’t make you go crazy? How do you manage different development processes, including Agile methodologies? On the Job: What does it take to walk into a job and be productive right away? The Tech Writer Toolkit: How do you create style guides, indexes, templates and layouts? How do you manage localization and translation and all the other non-writing parts of the job? I Love My Job: How do you handle the ups and downs of being a technical writer? Appendixes: References to websites, books, and other resources to keep you learning. Index
Publisher: XML Press
ISBN: 1457182424
Category : Reference
Languages : en
Pages : 512
Book Description
Every complex product needs to be explained to its users, and technical writers, also known as technical communicators, are the ones who do that job. A growing field, technical writing requires multiple skills, including an understanding of technology, writing ability, and great people skills. Whether you're thinking of becoming a technical writer, just starting out, or you've been working for a while and feel the need to take your skills to the next level, The Insider's Guide to Technical Writing can help you be a successful technical writer and build a satisfying career. Inside the Book Is This Job for Me? What does it take to be a technical writer? Building the Foundation: What skills and tools do you need to get started? The Best Laid Plans: How do you create a schedule that won’t make you go crazy? How do you manage different development processes, including Agile methodologies? On the Job: What does it take to walk into a job and be productive right away? The Tech Writer Toolkit: How do you create style guides, indexes, templates and layouts? How do you manage localization and translation and all the other non-writing parts of the job? I Love My Job: How do you handle the ups and downs of being a technical writer? Appendixes: References to websites, books, and other resources to keep you learning. Index
Technical Approaches to Characterizing and Cleaning Up Automotive Repair Sites Under the Brownfields Initiative
Author:
Publisher:
ISBN:
Category : Automobile repair shops
Languages : en
Pages : 68
Book Description
Publisher:
ISBN:
Category : Automobile repair shops
Languages : en
Pages : 68
Book Description
Monthly Catalogue, United States Public Documents
Author:
Publisher:
ISBN:
Category : Government publications
Languages : en
Pages : 752
Book Description
Publisher:
ISBN:
Category : Government publications
Languages : en
Pages : 752
Book Description
Technical Approaches to Characterizing and Cleaning Up Brownfields Sites
Author: United States. Environmental Protection Agency
Publisher:
ISBN:
Category : Brownfields
Languages : en
Pages : 76
Book Description
Publisher:
ISBN:
Category : Brownfields
Languages : en
Pages : 76
Book Description
Technical Approaches to Characterizing and Cleaning Up Brownfields Sites
Author:
Publisher:
ISBN:
Category : Brownfields
Languages : en
Pages : 92
Book Description
Publisher:
ISBN:
Category : Brownfields
Languages : en
Pages : 92
Book Description
Documenting Software Architectures
Author: Paul Clements
Publisher: Pearson Education
ISBN: 0132488590
Category : Computers
Languages : en
Pages : 651
Book Description
Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system’s architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed. Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition: Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models Guidance for documentation in an Agile development environment Deeper treatment of documentation of rationale, reflecting best industrial practices Improved templates, reflecting years of use and feedback, and more documentation layout options A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system Reference guides for three important architecture documentation languages: UML, AADL, and SySML
Publisher: Pearson Education
ISBN: 0132488590
Category : Computers
Languages : en
Pages : 651
Book Description
Software architecture—the conceptual glue that holds every phase of a project together for its many stakeholders—is widely recognized as a critical element in modern software development. Practitioners have increasingly discovered that close attention to a software system’s architecture pays valuable dividends. Without an architecture that is appropriate for the problem being solved, a project will stumble along or, most likely, fail. Even with a superb architecture, if that architecture is not well understood or well communicated the project is unlikely to succeed. Documenting Software Architectures, Second Edition, provides the most complete and current guidance, independent of language or notation, on how to capture an architecture in a commonly understandable form. Drawing on their extensive experience, the authors first help you decide what information to document, and then, with guidelines and examples (in various notations, including UML), show you how to express an architecture so that others can successfully build, use, and maintain a system from it. The book features rules for sound documentation, the goals and strategies of documentation, architectural views and styles, documentation for software interfaces and software behavior, and templates for capturing and organizing information to generate a coherent package. New and improved in this second edition: Coverage of architectural styles such as service-oriented architectures, multi-tier architectures, and data models Guidance for documentation in an Agile development environment Deeper treatment of documentation of rationale, reflecting best industrial practices Improved templates, reflecting years of use and feedback, and more documentation layout options A new, comprehensive example (available online), featuring documentation of a Web-based service-oriented system Reference guides for three important architecture documentation languages: UML, AADL, and SySML