TIM-5120 v1

Kmiec, D., Longo, B., & Longo, B. (2017). The IEEE guide to writing in the engineering and technical fields. ProQuest Ebook Central.
Read chapter 3, “Writing to Know: Informative Documents.” Read this entire chapter carefully; you will find value throughout. Pay specific attention to pages 104-108 where specifications are discussed.
The IEEE Guide to Writing in the Engineering and Technical Fields is an authority reference to elements of process, style, audience, format, and tone associated with writing technical documents. As a technical manager or technologist, this will likely be an important document for you to reference as your career develops.

The National Academies of Science, Engineering, Medicine. (n.d.). FDP expanded clearinghouse pilot phase 2 – Web-based system: Functional and technical requirements document.
The FDP Expanded Clearinghouse Pilot Functional and Technical Requirements Document provides an example of a complex specification that acts as a hybrid for functional and technical documentation. The purpose of this document is to provide an example of what a comprehensive specification looks like. Focus on the sections of the document, how they flow, and the ways in which they describe the required solution. Do not spend time focusing on the contents of this document. Rather, consider how other technical solutions could be described using the formats and processes articulated in specification.

Casecomplete. (n.d.). Five tips for writing use cases.
This web article was written by a qualified technical manager and or engineer with specific recommendations and suggestions that can be applied to this assignment and any similar technical documentation undertaken in your career.

Systems Flow Incorporated. (2018, July 10). 5 rules for writing effective use cases.
This web article was written by a qualified technical manager and or engineer with specific recommendations and suggestions that can be applied to this assignment and any similar technical documentation undertaken in your career.

The National Academies of Science, Engineering, Medicine. (n.d.). FDP expanded clearinghouse pilot phase 2 – Web-based system: Functional and technical requirements document.
The FDP Expanded Clearinghouse Pilot Functional and Technical Requirements Document provides an example of a complex specification that acts as a hybrid for functional and technical documentation. The purpose of this document is to provide an example of what a comprehensive specification looks like. Focus on the sections of the document, how they flow, and the ways in which they describe the required solution. Do not spend time focusing on the contents of this document. Rather, consider how other technical solutions could be described using the formats and processes articulated in specification.

Tiwari, S.,Gupta, A. (2013). A controlled experiment to assess the effectiveness of eight use case templates. 2013 20th Asia-Pacific Software Engineering Conference (APSEC), 2013, pp. 207-214.
Use case models, that include use case diagrams along with their documentations, are typically used to specify the functional requirements of the software systems. This study analyzes a set of use cases and reports results.

TemplateLab. (n.d.). 40 Use Case Templates & Examples (Word, PDF).
A Use Case is usually used in software designing, but as a tool, it is effective for any type of management. A USE Case defines what needs to happen upon a particular action in order for that action to be completed successfully. It is important to use a USE Case because it easily outlines all that is needed for a particular process to succeed and also outlines all the people involved in it.