---
# System prepended metadata

title: Compsci-320 Ultimate Software Notes
tags: [compsci 320, school]

---

# Compsci-320 Ultimate Software Notes

###### tags: `compsci 320` `school`

## Project Proposal Presentation

#### Employee Perception Application
- Managers create surveys and send to Employees
- Managers can create surveys with custom questions and tags for each question
- Employees can annonymously take surveys
- Managers can view results
- Results are summarized over time and can view by question/tag
- Track results over time

#### Design Points
- Modern technology stack
- Scalable
- Part of a larger ecosystem of services
    - Don't put everything in 1 huge database
    - Be flexible with database integration to allow multiple data sources down the road
- Two user types:
    - Manager
    - Employee
- All surveys are annonymous (For real, not just in perception)
- Need to have a focus on security (but maybe not full end-to-end)
- Should be very extensible
- High/Medium/Low questions (eg. Employees have High feelings towards, medium feelings, etc...)
- Easy to add question types in the future
- Add scale type: 1-10 (eg. satisfaction)
- Comment/Open Response
- Multiple Choice
- System should summarize data (per category)
- Only managers should b able to create surveys
- Employee data will come from external system
- Data should be able to be secured locally
- Managers should be able to see surveys that their employees (who are also managers) give out
- Data should be able to be deleted (effectively deleted: Any employee can delete their own survey)
- Should be accessible to all types of people
- Mobile or web based (in past have gravitated to web-based)
- Output actual screen with insights (possibly output as formatted PDF with charts and all that)
- Don't need to output data as CSV right now
- There might be an official color pallete (Green and white in general, he will send out one later)
- Users should be logging in
- Everyone below an employee should have access to a survey by a manager (recursive tree for all people below)
- Logging in System:
    - Optional, but must be able to get summarized results
    - Some type of logging (See how employee satisfaction changes after payday for example)
- Users should not be able to edit surveys after they have been submitted
- Be able to save progress and come back later to survey before submitting survey
- Email integration: Alert users that there is a new survey that is available to be taken when created
    - Potentially set frequency to reminders
- Track participation percentage
- Make some questions optional in the survey