---
# System prepended metadata

title: Requirements Interview
tags: [kevin-depelseneer, ' interview', requirements]

---

---
title: Requirements Interview
description: Interview with Sven Eyckerman to discuss the requirements for the tool.
tags: kevin-depelseneer,requirements, interview
---

# Requirements Interview

## Outline
* The core of the project is to simulate the assembly of a plasmid from a destination vector, enzyme recognition sequence, and overhangs. Is this true?
> Yes. The idea is to automate the Golden Gateway design as much as possible with a seperate tool. Nowadays, it happens in CLC but it takes a huge amount of time.
>


* Which inputs are provided by the user and which are either provided by the system (as a narrowing selection for the user), or computed based on user input?
> The user should be guided while making the design.
>

* Does the user know what specific vector or vectors they want to use in the reaction?
> Yes the users knows that in advance.
>

* What should the output be? FASTA formatted sequence or...?
> The output should be a genbank file.>
>

* How are inputs specifically structured?
> The inputs can be sorted into six different categories, depending on their role in the construct:
> * Promotor
> * Kozak-ATG (+ N-terminal tag)
> * Gene Of Interest
> * Linkers: Longer pieces of DNA that provide more flexibility in the protein structure, hence enhancing the functionality of the protein.
> * Fusion partner + Stop-codon
> * Termination signal or post-transcription regulatory sequences.
> 
> These different donor-vectors also have differnt overhangs so there is only one way to build them in.


* How are clevage sites to be specified? Maybe multiple options?
>
>
>

* What are the labels 'A', 'B', 'G' etc in the overhang labels? What do they refer to specifically? Are these sequences necessary for the simulation?
> Every label corresponds with a 4 nucleotide region.
>
![](https://i.imgur.com/aj7ADml.png)


* Does it make sence to store the simulation results? e.g. Inserts and destination vectors? Or also level 1 and level 2 constructs?
> It definitely makes sence to store the level 1 constructs because you need them to combine them in level 2 constructs.
>

* Number of inserts for a level 1 construct => Max. 6?
> Has to be flexible: Between 3 and 6.
>

* Number of level 1 constructs for a level 2 construct? => 2?
> No, 3 is the maximum.
>

* Are the backbones for the level 1 constructs different from those used in level 2 reactions? Do we need to make the distinction between both?
> Yes! Backbones from the level 1 constructs are not used to design level 2 constructs. They have different enzyme recognition sites.
>

* Are there any calculations to be made that are useful for the experiment itself? e.g. Calculating ratio's Inserts / backbone
> Not really, the amounts are fixed.
>

## Features

* What would you like to change and/or keep about Kevin's current application?
> The visual design
> The filtering possibilities in the UI of the database entries
>

* What is the most important or most immediately useful feature(s)? Which are "nice to have" features?
> Nice to have: level -1 (pre-donor vector) implementation
>

* Some columns were added to Kevin's database? What use-cases are/were these intended for?
> Not sure why...
> The donor- and destination vectors are now stored in an excel. Use the colomn headers as fields for the database.
>


## Requests

* We need example input data and expected outputs for those inputs.
    * For varying levels and input combinations
    * Including examples of any/some special cases
    * An export of the sequences of all the donor- and destination vectors.
