Capturing and analyzing the requirements makes it easier to translate into a PageSeeder model.
The most useful requirements to capture for PageSeeder modeling are
- Semantic data model (such as an entity relationship ER model)
- System requirements
- Use cases
The first step is to building a semantic data model by identifying
Identifying semantics and relationship will help translating the model into a PageSeeder solution.
Entities and attributes
An entity is generally expressed as a noun
- Identify primary keys
- Are there any public keys?
- Cardinality – How many possible instances?
- Mutability – Can they change?
- Volatility – How frequently are they changed / created?
- Data types of value (integer, string, boolean, date)
- Range of possible values (1-100, enumerated lists, etc.)
Relationship between entities.
A relationship generally expressed as verb.
Note if relationship is:
- 0..1, 1..1, 1..N, N..M
System requirements will inform design decisions
They should include:
- Business case
- Documentation & help system
- Future developments
Use cases are useful to identify actors and how they interact with PageSeeder
Use cases should include:
- A title or goal
- Success / failure scenarios
- Related information
See common approaches to PageSeeder modeling.
Created on , last edited on