-- Example: Project Management Application

-- Main Entities
User {
  id: UUID (PK)
  email: STRING UNIQUE
  password_hash: STRING
  first_name: STRING
  last_name: STRING
  role: ENUM(USER, ADMIN, MANAGER)
  created_at: TIMESTAMP
  updated_at: TIMESTAMP
}

Project {
  id: UUID (PK)
  name: STRING
  description: TEXT
  status: ENUM(DRAFT, ACTIVE, COMPLETED, ARCHIVED)
  owner_id: UUID (FK -> User.id)
  start_date: DATE
  end_date: DATE
  created_at: TIMESTAMP
}

Task {
  id: UUID (PK)
  title: STRING
  description: TEXT
  status: ENUM(TODO, IN_PROGRESS, DONE)
  priority: ENUM(LOW, MEDIUM, HIGH, URGENT)
  project_id: UUID (FK -> Project.id)
  assigned_to: UUID (FK -> User.id)
  due_date: DATE
  created_at: TIMESTAMP
}

-- Relations
ProjectMember {
  project_id: UUID (FK -> Project.id)
  user_id: UUID (FK -> User.id)
  role: ENUM(MEMBER, LEAD, OBSERVER)
  joined_at: TIMESTAMP
}

### Interface Design

#### Wireframes and Mockups


# UI/UX Design Process

## 1. User Journey Mapping
- [ ] Identify main user paths
- [ ] Map steps and touchpoints
- [ ] Identify friction moments
- [ ] Define emotions at each step

## 2. Information Architecture
- [ ] Existing content inventory
- [ ] Categorization and hierarchy
- [ ] Navigation and menu structure
- [ ] Taxonomy and labeling

## 3. Wireframing
- [ ] Low-fidelity sketch (paper/balsamiq)
- [ ] Main page structure
- [ ] Key element placement
- [ ] Inter-screen navigation

## 4. Prototyping
- [ ] High-fidelity mockups (Figma/Sketch)
- [ ] Design system and components
- [ ] Interactions and animations
- [ ] User testing on prototype

#### Design System


# Design System - [Project Name]

## Colors
### Primary Colors
- **Primary**: #3B82F6 (Main blue)
- **Secondary**: #64748B (Secondary gray)
- **Success**: #10B981 (Success green)
- **Warning**: #F59E0B (Warning orange)
- **Error**: #EF4444 (Error red)

### Background Colors
- **Background**: #FFFFFF (White)
- **Surface**: #F8FAFC (Very light gray)
- **Border**: #E2E8F0 (Border gray)

## Typography
### Main Font
- **Font Family**: Inter, sans-serif
- **Weights**: 400 (Regular), 500 (Medium), 600 (Semi-bold), 700 (Bold)

### Hierarchy
- **H1**: 2.25rem (36px), Semi-bold
- **H2**: 1.875rem (30px), Semi-bold
- **H3**: 1.5rem (24px), Medium
- **Body**: 1rem (16px), Regular
- **Caption**: 0.875rem (14px), Regular

## Spacing
- **XS**: 0.25rem (4px)
- **S**: 0.5rem (8px)
- **M**: 1rem (16px)
- **L**: 1.5rem (24px)
- **XL**: 2rem (32px)
- **XXL**: 3rem (48px)

## 📋 Risk Analysis

### Risk Identification


# Risk Matrix

## Technical Risks
| Risk | Probability | Impact | Criticality | Mitigation |
|------|-------------|--------|-------------|------------|
| Insufficient performance | Medium | High | **High** | Load testing, scalable architecture |
| Data security | Low | Very High | **High** | Security audit, encryption |
| Browser compatibility | High | Medium | **Medium** | Cross-browser testing, polyfills |
| Third-party API integration | Medium | Medium | **Medium** | Fallback API, error handling |

## Project Risks
| Risk | Probability | Impact | Criticality | Mitigation |
|------|-------------|--------|-------------|------------|
| Delivery delay | Medium | High | **High** | Planning buffer, prioritization |
| Requirements change | High | Medium | **Medium** | Agile method, MVP |
| Unavailable resources | Low | High | **Medium** | Backup plan, training |
| Budget exceeded | Medium | High | **High** | Regular monitoring, scope control |

### Contingency Plan


# Contingency Plan

## If Insufficient Performance
### Immediate Actions
- [ ] Complete performance audit
- [ ] Identify bottlenecks
- [ ] Optimize critical code

### Long-term Actions
- [ ] Architecture refactoring
- [ ] Implement caching
- [ ] Migrate to more powerful infrastructure

## If Development Delay
### Immediate Actions
- [ ] Prioritize MVP features
- [ ] Temporarily increase resources
- [ ] Reduce non-critical scope

### Long-term Actions
- [ ] Revise estimates
- [ ] Improve processes
- [ ] Team training

## 🎯 Validation and Approval

### Validation Checklist


# Pre-design Validation

## Analysis Documents
- [ ] **User needs**: Validated by stakeholders
- [ ] **Functional specifications**: Complete and unambiguous
- [ ] **Technical constraints**: Identified and documented
- [ ] **Risk analysis**: Completed with mitigation plans

## Technical Design
- [ ] **System architecture**: Validated by technical team
- [ ] **Data model**: Coherent and normalized
- [ ] **User interfaces**: Validated by end users
- [ ] **Test strategy**: Defined and planned

## Planning
- [ ] **Product roadmap**: Approved by management
- [ ] **Development planning**: Realistic and detailed
- [ ] **Budget**: Validated and allocated
- [ ] **Team**: Assembled and trained

## Success Criteria
- [ ] **Metrics**: Defined and measurable
- [ ] **Acceptance criteria**: Clear for each feature
- [ ] **Definition of Done**: Established for the team

<Note type="success">
**Objective**: At the end of pre-design, all participants should have a clear and shared vision of the project, its objectives, architecture, and implementation.
</Note>

## 🚀 Transition to Development

### Team Preparation


# Development Team Onboarding

## Documentation to Provide
- [ ] **Complete specifications**: Functional and technical
- [ ] **Mockups and designs**: Complete design system
- [ ] **Detailed architecture**: Diagrams and technical documentation
- [ ] **Coding standards**: Guidelines and best practices

## Necessary Training
- [ ] **Project presentation**: Context, objectives, users
- [ ] **Technical architecture**: Technologies, patterns, conventions
- [ ] **Tools and processes**: Git workflow, CI/CD, collaboration tools
- [ ] **Quality standards**: Tests, code review, documentation

## Environments to Prepare
- [ ] **Development**: Standardized local configuration
- [ ] **Integration**: Automated testing environment
- [ ] **Staging**: Client validation environment
- [ ] **Production**: Deployment infrastructure

### Monitoring Metrics


# Development KPIs

## Progress
- **Velocity**: Story points completed per sprint
- **Burndown**: Progress toward objectives
- **Scope Creep**: Scope evolution

## Quality
- **Code Coverage**: Percentage of tested code
- **Bug Rate**: Number of bugs per feature
- **Technical Debt**: Accumulated technical debt

## Performance
- **Lead Time**: Feature completion time
- **Cycle Time**: Time between start and end of development
- **Deployment Frequency**: Production deployment frequency

---

Successful pre-design is the foundation of a successful project. It transforms a vague idea into a clear and achievable action plan!