Frameworks for Selected System Engineering Reports eBook

ONLY US$19.95 - BUY NOW

Businesses and projects rely on well-structured reports to ensure accurate communication about goals and objectives, requirements, designs, measuring and recording progress, etc. Unfortunately, many engineering reports are not clear as it should be.

In order to alleviate this problem - particularly for engineers and managers in the early stages of their careers - this eBook contains suggested frameworks for a selection of commonly used system engineering reports. (Two other eBooks by the same authors contain frameworks for business management reports and project management reports).

This eBook is intended as a report writing reference guide, from which ideas can be sourced about the typical structure and contents of commonly used system engineering reports. The eBook does not provide blueprints for all reports that as system engineer might ever have to write, but it provides guidelines which should be tailored and adapted by common sense and experience, in order to suit specific circumstances.

The philosophy underlying this book is: contents follow structure - i.e. first carefully think about, and decide upon a report structure, and then systematically fill in the contents. When a report structure is first defined, the gathering of information becomes focused, and unnecessary material is either not collected at all, or it can be filtered out systematically.

Besides briefly addressing the main generic elements of a report, report quality assurance and the system engineering process, frameworks for the following types of reports are provided in this eBook:

User requirements statement
System engineering management plan
System specification
Development specification
Product specification
Trade-off study report
Technical notes
Design report
Research thesis
Error budget report
Interface control document
Test and evaluation master plan
Test and evaluation report
Failure modes, effects, and critically analysis (FMECA) report
Integrated logistic support plan

Each of these reports is briefly discussed in terms of its typical purpose and scope, followed by a suggested framework for the report.

1. Introduction

- 1.1 Purpose of this book

- 1.2 Scope of this book

- 1.3 Generic elements of a report

- 1.3.1 Title page

- 1.3.2 Executive summary/abstract

- 1.3.3 Table of contents

- 1.3.4 Abbreviations and terminology

- 1.3.5 Introduction

- 1.3.6 Main contents

- 1.3.7 Conclusions/recommendations

- 1.3.8 Appendices

- 1.3.9 Literature references

- 1.3.10 Index

- 1.4 Report quality assurance

- 1.4.1 Ensuring good quality reports

- 1.4.2 Editing

- 1.4.3 Report reviews

- 1.4.4 Configuration management

2. System engineering

- 2.1 The system engineering process

- 2.2 System life cycle

- 2.3 System hierarchy

- 2.4 Specifications

3. User requirements statement

- 3.1 Purpose and scope of a user requirements statement

- 3.2 Framework for a user requirements statement

4. System engineering management plan

- 4.1 Purpose and scope of a system engineering management plan

- 4.2 Framework for a system engineering management plan

5. System specification

- 5.1 Purpose and scope of a system specification

- 5.2 Frameworks for system specifications

6. Development specification

- 6.1 Purpose and scope of a development specification

- 6.2 Framework for a development specification

7. Product specification

- 7.1 Purpose and scope of a product specification

- 7.2 Framework for a product specification

8. Trade-off study report

- 8.1 Purpose and scope of a trade-off study report

- 8.2 Framework for a trade-off study report

9. Technical notes

- 9.1 Purpose and scope of technical notes

- 9.2 Frameworks for technical notes

10. Design report

- 10.1 Purpose and scope of a design report

- 10.2 Framework for a design report

11. Research thesis

- 11.1 Purpose and scope of a research thesis

- 11.2 Framework for a research thesis

12. Error budget report

- 12.1 Purpose and scope of an error budget report

- 12.2 Framework for an error budget report

13. Interface control document

- 13.1 Purpose and scope of an interface control document

- 13.2 Framework for an interface control document

14. Test and evaluation master plan

- 14.1 Purpose and scope of a test and evaluation master plan

- 14.2 Framework for a test and evaluation master plan

15. Test and evaluation report

- 15.1 Purpose and scope of a test and evaluation report

- 15.2 Framework for a test and evaluation report

16. Failure modes, effects, and critically analysis (FMECA) report

- 16.1 Purpose and scope of an FMECA report

- 16.2 Framework for an FMECA report

17. Integrated logistic support plan

- 17.1 Purpose and scope for an integrated logistic support plan

- 17.2 Framework for an integrated logistic support plan

18. Literature references

About the authors

Dr Johan Gouws B.Eng. M.Eng. (Electrical and Electronics) MBA, Ph.D.

Expertise - Feasibility and re-engineering studies, system engineering, project management, modeling, simulation, and has been an expert witness in legal matters involving technical and management issues

Mrs Leonie Gouws B.Eng. (Mechanical) M.Eng. (Engineering Management)

Expertise - Maintenance management for operational systems, computerised management information systems (SAP PM), technical writing and project documentation, and logistics engineering for new and existing systems.

Price: US$19.95

To purchase, simply click here and you will be transferred to our affiliate partner.