You have arrived here because you have a problem or problems that you would like to address.
Your requirements document should describe the problem[s] in detail including the cost to your company in both time and money. It should explain your vision for a solution and describe how the solution addresses the problem[s].
Explain why and how will PLM software will be a part of the solution.
Why Write a Requirements Document
A requirements document serves as a guide for engineers developing the solution and for the testing that will need to be done. It is a list of everything your solution should do. Your requirements should be the basis for your project plan – a plan that can help you plan resources.
Your requirements document should be under rules for managing changes. This should help you minimize scope creep. Scope creep can destroy an otherwise well thought out implementation of any kind of solution.
The Requirements Document
From your user interviews, provide a detailed description. Why is it necessary? Who is affected by the requirement? What is the desired priority?
Building from your list of requirements, your requirements document may include the following:
Introduction – A high level overview of what is in this document.
General Description – Provide a description of the solution in non-technical terms. If the implementation is done properly, describe what it would look like from the users point of view.
Specific Requirements – Provide a list of gathered, prioritized requirements here.
Appendices – Provide other information here that will support the preceding.
Glossary – Explain terms if necessary.
References – List references if there are any.
Index – Depending on the size of your document, you may need to create an index.
Successful PLM Implementations
The successful PLM implementations that I have seen always start with a good requirements document.
A tip for making life easier – put together a dummy user interface showing what the solution might look like. It allows users to see the solution and provide even more input. It provides developers/implementers with a clear picture of the solution. It will get everyone on the same page.
Learn more at PI PLMx 16-17 October 2017 | Fort Worth, Texas
I will be hosting a focus group on the topic of understanding PLM product requirements in Room 4 on 17 October @ 12:20.
Go to this site if you would like to attend: http://events.pi.tv/2017/pi_usa/programme
I will have time for a meeting, contact me if you would like to meet.