Contact person: Business Client

Phone:Show

Email:Show

Location: Brussels, Belgium

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"# Software Analyst - UML & Technical Analysis (Klavis - Legal Tech)

## Project Overview
We're seeking a **sharp, experienced software analyst** to work directly with our senior architect/team lead on **Klavis** ([login to view URL], [login to view URL]), an innovative legal technology platform. This is a fast-paced, hands-on role requiring someone who can **hit the ground running** and quickly understand complex systems.

## Your Role
You'll work **closely under supervision** of the senior programmer/architect (project manager/team lead) to handle the analytical heavy-lifting for multiple feature implementations. This is not a passive documentation role - you'll be actively diving into code, understanding architectural patterns, and producing actionable technical specifications.

## Primary Responsibilities

### Analysis & Documentation:
- **Create UML diagrams** (class diagrams, sequence diagrams, activity diagrams, state machines)
- **Write/generate detailed use cases** with preconditions, postconditions, and flow variations
- **Define object structures** including properties, relationships, and constraints
- **Specify method signatures** with parameters, return types, and exception handling
- **Generate comprehensive test cases** covering happy paths, edge cases, and error scenarios
- **Document architectural decisions** and design patterns being applied

### Collaboration & Learning:
- **Quick onboarding** - rapidly understand existing codebase and architectural framework
- **Pattern replication** - identify and adapt existing implementation patterns for new features
- **Propose solutions** - suggest architectural approaches for novel functionality
- **Real-time collaboration** - work synchronously with team lead for quick iterations
- **Ask smart questions** - clarify requirements efficiently without excessive back-and-forth

## Feature Areas (from Requirements Document)

You'll be analyzing implementations for:
- **Legal Case Creation Wizard** (Automation I) - Complex form flows with dynamic issue selection
- **Legal Issue Form Creation Wizard** (Automation II) - AI-powered categorization workflows
- **Messaging System** - Case-related chat with document handling
- **Finance Module** - Invoice generation, storage, and distribution
- **Calendar & Events** - Event management with legal case integration
- **Email Management** - Full inbox, folders, and provider integration
- **Notifications** - Complete notification system redesign
- **Dashboard Integrations** - Cross-feature component integration
- **Security & Compliance** - Encryption, GDPR, server hardening patterns
- **Role-Based Access** - Lawyer, Client, Admin separation and impersonation
- **Documents & File Management** - Database migration analysis

## What You'll Deliver (7 Days)

### Week 1 Deliverables:

! **Important Note**: Unless another method will be more efficient, all analysis and designs will be done using a google app (google docs, google slide, or google draw), for easy sharing, eacy collaboration, and for securing the files...

1. **UML Diagram Suite**
- Class diagrams for all major features
- Sequence diagrams for critical workflows
- Activity diagrams for complex processes
- State diagrams where applicable

2. **Use Case Documentation**
- Detailed use cases for each feature
- Actor definitions and interactions
- Alternative flows and exception handling

3. **Technical Specifications**
- Object/class definitions with full property lists
- Method signatures with complete parameter documentation
- API endpoint specifications (if applicable)
- Data model relationships and constraints

4. **Test Case Specifications**
- Unit test scenarios
- Integration test scenarios
- E2E test case outlines
- Edge cases and error condition tests

5. **Architecture Documentation**
- Pattern applications and justifications
- New architectural proposals where needed
- Integration points between features
- Technical debt notes and recommendations

## Required Skills & Experience

### Must Have:
- **3+ years** as a software analyst or technical analyst role
- **Expert in UML** - can create professional diagrams quickly (Enterprise Architect, Lucidchart, [login to view URL], PlantUML, etc.)
- **Strong OOP principles** - deep understanding of object-oriented design patterns
- **Backend system analysis** experience (REST APIs, database design, service architectures)
- **Test-driven mindset** - naturally thinks about test scenarios while analyzing
- **Fast learner** - can understand complex codebases rapidly
- **Excellent written communication** - specifications must be clear and actionable
- **Proactive approach** - anticipates issues and asks clarifying questions early

### Highly Desired:
- Experience with **Vue.js or modern JavaScript frameworks** (helpful for frontend analysis)
- **Legal tech, SaaS, or enterprise software** analysis experience
- Familiarity with **microservices or modular architectures**
- Knowledge of **GDPR compliance** and security best practices
- Experience with **automated documentation tools** (Swagger, JSDoc, etc.)
- **Agile/Scrum environment** experience

### Tools You Should Be Comfortable With:
- UML modeling tools (any professional tool)
- Documentation platforms (Markdown, Confluence, Notion, etc.)
- Diagramming software
- Git/version control (for code exploration)
- API documentation tools

## Working Style

### What Success Looks Like:
✓ **Day 1-2:** You've reviewed requirements, explored the codebase, and started producing diagrams
✓ **Day 3-5:** Core feature analysis complete with UML, use cases, and object definitions
✓ **Day 6-7:** Test cases documented, final reviews, and deliverable packaging

### Communication Expectations:
- **Daily sync sessions** with team lead (15-30 min)
- **Immediate clarification** when stuck or uncertain
- **Progressive delivery** - share work incrementally for feedback
- **Responsive** - quick turnaround on revision requests
- **Timezone flexibility** - able to overlap working hours for collaboration

## Project Details
- **Budget:** $600 USD (fixed price)
- **Timeline:** 7 days from project start
- **Work Mode:** Remote, with required synchronous collaboration windows
- **Intensity:** Full-time commitment during project period
- **Supervision:** Direct collaboration with senior architect/team lead
- **Documentation Format:** Deliverables in agreed formats (PDF, PNG/SVG diagrams, Markdown, etc.)

## Why This Role?

### Great For You If:
- You love **diving deep into technical systems**
- You want **direct mentorship** from experienced architect
- You thrive in **fast-paced, high-responsibility** environments
- You're building your **enterprise software analysis** portfolio
- You want exposure to **legal tech innovation**

### What You'll Gain:
- **Real-world architectural patterns** from production system
- **Direct collaboration** with senior technical leadership
- **Complex system analysis** experience across multiple domains
- **Portfolio-worthy deliverables** from a real legal tech platform
- **Potential for ongoing work** if delivery exceeds expectations

## Application Requirements

Please provide:

1. **Resume/CV** highlighting relevant analysis experience
2. **UML samples** - 2-3 examples of diagrams you've created (class, sequence, or activity diagrams preferred)
3. **Analysis sample** - brief example of use case or technical specification you've written
4. **Availability confirmation** - can you commit full-time for 7 days starting [your start date]?
5. **Your approach** - in 3-5 sentences, how would you tackle rapid codebase familiarization?
6. **Tool preferences** - what UML and documentation tools do you use?
7. **Questions** - any clarifications needed about scope or requirements?

## Important Notes
- This is **intensive analytical work** - only apply if you can fully commit
- You'll have **access to codebase** and documentation for reference
- **Quality over speed** - but we need both given the timeline
- **Clear, actionable deliverables** are critical - vague documentation won't work
- The role requires **intellectual agility** and **technical depth**

## ! This Role Is NOT For You If:
✗ You need extensive hand-holding or detailed instructions
✗ You're slow to understand technical concepts
✗ You produce generic, template-based documentation
✗ You can't commit to daily collaboration sessions
✗ You're uncomfortable working at a fast pace

## This Role IS For You If:
✓ You're a **quick study** who grasps systems rapidly
✓ You produce **precise, actionable documentation**
✓ You're **self-directed** but collaborative
✓ You thrive under **tight deadlines**
✓ You understand that **analysis enables development**

---

**Ready to dive deep into Klavis and produce exceptional technical analysis? Apply now with your samples and approach!**

*Klavis is transforming how legal professionals work. Join us in building the foundation for the next phase of features.*" (client-provided description)