Serban Petrescu
I'm an IT enthusiast which graduated Computer Science at TU-CN and works full time at @msg-systems Romania.
Introduction: place the document in respect to other documents, by defining a scope, references, etc.
Positioning: defines the problem addressed and how the product will solve it.
Stakeholders / users: identify who your users are and who else has a stake in your product.
Define the three use cases in your project:
Define a goal,
Specify which actor is driving this use case,
Define a success scenario from the trigger which started the use case until the goal fulfillment.
Optionally define extension scenarios for error conditions, failure, additional actor interactions (that are not usually carried out).
Draw a use case diagram.
Detail any non-functional requirements. You should mostly talk here about security and testability.
Describe the design constraints (both those imposed by yourself and by me).
Define any terms used throughout the other documents or the project as a whole.
A very high-level class / data model diagram which defines the business domain and the concepts tackled by the system.
Define the architecture patterns / styles used and also the rationale for using them.
Define what types of tests will be created, how the test will be executed, test cases.
By Serban Petrescu
I'm an IT enthusiast which graduated Computer Science at TU-CN and works full time at @msg-systems Romania.