- \n
- Sprint, iteration<\/li>\n
- Feature<\/li>\n
- Build and release<\/li>\n
- Test cases, test results<\/li>\n<\/ul>\n<\/li>\n
- Business Analysis projects:\n
- \n
- Needs, goals, objectives<\/li>\n
- Business functions, processes, tasks<\/li>\n
- Organisations, groups, teams<\/li>\n
- Deliverables, reports\u00a0 and other document types, artefacts, builds<\/li>\n
- Personnel types, skills, roles<\/li>\n<\/ul>\n<\/li>\n
- Enterprise Architecture projects:\n
- \n
- Needs, goals, objectives<\/li>\n
- Processes, functions, tasks<\/li>\n
- Resources, systems, buildings and other facilities, area breakdown structure, site breakdown structure<\/li>\n
- Delivery phases, releases and builds<\/li>\n
- Organisations, groups, teams<\/li>\n
- Deliverables, reports\u00a0 and other document types, artefacts, builds<\/li>\n
- Personnel types, skills, roles, organisation breakdown structure<\/li>\n<\/ul>\n<\/li>\n
- Requirements Management projects:\n
- \n
- Needs, goals, objectives<\/li>\n
- Business requirements, user requirements, system requirements<\/li>\n
- Validations and verifications<\/li>\n<\/ul>\n<\/li>\n
- Application lifecycle management projects:\n
- \n
- Needs, goals, objectives<\/li>\n
- Business requirements, user requirements, system requirements<\/li>\n
- Validations and verifications<\/li>\n
- Analysis models, logical models, architecture models, design models – built using MBSE using one or more of functional analysis, SASD, IDEF, ADARTS, UML and\/or SysML notations<\/li>\n
- System breakdown structure (SBS)<\/li>\n
- Test cases and test results<\/li>\n<\/ul>\n<\/li>\n
- Project Management projects:\n
- \n
- Needs, goals, objectives<\/li>\n
- Business requirements, user requirements, system requirements<\/li>\n
- Product requirements, managed in a library<\/li>\n
- Validations and verifications<\/li>\n
- System breakdown structure (SBS)<\/li>\n
- Product breakdown structure (PBS)<\/li>\n
- Part catalogue, suppliers, orders<\/li>\n
- Production schedules, production runs, batches, samples<\/li>\n
- Quality records, test cases, samples, test results<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
Location and Structure of Default Schemas<\/h2>\n
Each default schema is stored in the sub-directory:<\/p>\n
admin\/defaults<\/p>\n
inside the Cradle installation on the server.<\/p>\n
Inside this directory are:<\/p>\n
- \n
- A file called: prj_params that contains the schema<\/li>\n
- A directory tree containing the project-scope definitions, such as queries, views, forms and so on, called: definitions<\/li>\n<\/ul>\n
Creating New Default Schemas<\/h2>\n
You can create your own default schemas by:<\/p>\n
- \n
- Decide on a name for your new default<\/li>\n
- Create a new directory with this name inside the admin\/defaults directory in the Cradle installation on your server<\/li>\n
- Place the schema for the new default inside this directory in a file called: prj_params – you can copy the prj_params file from inside the database directory of an existing database, or use Cradle’s export to create it (see below)<\/li>\n
- Optionally copy some or all of the Project scope definitions from the definitions directory in an existing database<\/li>\n<\/ul>\n
Export to Create a New Default Schema<\/h2>\n
You can export the schema using the Export Information dialog that is shon when you select Export from the Project tab in WorkBench.<\/p>\n
If you can run WorkBench on the server, then you can export the schema directly into the new defaults directory:<\/p>\n
![\"Export](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2017\/07\/Make-Default-Schema.png\")
How to to Create a New Default Schema<\/figcaption><\/figure>\n Using Your New Default Schemas<\/h2>\n
When you create a new database in Project Manager, select the Schema drop-down list. This will display the list of default schemas. Any new schemas that you have created will appear in this list, for example:<\/p>\n
![\"Create](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2017\/07\/Use-Default-Schema-300x182.png\")
Create Project dialog<\/figcaption><\/figure>\n