
1. Developer
1.1. They help the customers with the systems that meet their needs.
1.2. Functions
1.2.1. Test/evaluate the software.
1.2.2. Discuss features with the client.
1.2.3. Identify needs and design solutions.
1.2.4. Write and execute code.
1.2.5. Have knowledge of the software, policies of the company, and limitations of COTS.
1.3. Software developer vs Computer Programmer
1.3.1. Charactheristics of a Software Developer
1.3.1.1. They are in charge of the design of a preexisting software.
1.3.1.2. SDLC
1.3.1.2.1. The software development lifecycle is a defined process that delivers a good quality software implementation.
1.3.1.3. Day-to-day
1.3.1.3.1. Senior
1.3.1.3.2. Junior
1.3.1.4. "Good Hours" vs "Stuck Hours"
1.3.1.4.1. A good hour is effective and sustainable, while a stuck hour is time lost trying to advance in something you may be uncertain, have no previous knowledge, and make no advance in a period of time.
1.3.1.5. Important points to focus
1.3.1.5.1. Maintainability
1.3.1.5.2. Scalability
1.3.2. Charactheristics of a Computer Programmer
1.3.2.1. Software creation through code.
1.4. COTS Systems
1.4.1. Commercial Off The Shelf systems offer basic functionality after installation.
1.4.2. Examples
1.4.2.1. Star LIMS
1.4.2.2. LabVantage
1.4.2.3. LabWare
1.4.3. Configuration vs Customization
1.4.3.1. Config
1.4.3.1.1. Generic establisment of information.
1.4.3.1.2. Allows the stock software to work best for you.
1.4.3.1.3. Favored by the developer.
1.4.3.2. Custom
1.4.3.2.1. Change the code to meet specific expectations.
2. Business Analyst
2.1. What is a Business Analyst?
2.1.1. They are the translators between the client and the rest of the team. Initial impression of Astrix to the clients.
2.2. Functions
2.2.1. Organizes and direct meetings with clients.
2.2.2. Makes the project's information available to every team member.
2.2.3. Understands the process of the client (what they sell, needs, wants, what they do, how the software helps).
2.2.4. Confirms the information received with the client to ensure accuracy.
2.2.5. Facillitates the master data to the developers.
2.2.6. Optional: Makes presentations and explains the demos of the software to the client.
2.3. Elicitation
2.3.1. Collaboration
2.3.1.1. Interviews
2.3.1.1.1. Steps
2.3.1.1.2. Purpose
2.3.1.1.3. Main Points // Tips
2.3.1.1.4. Roles
2.3.1.2. Observations
2.3.1.2.1. Use of experience to understand the problem and the area processes.
2.3.1.3. Requirements
2.3.1.3.1. Needs, desired and expectations of a client for a project.
2.3.2. Visualization
2.3.2.1. Prototyping
2.3.2.1.1. Early model, sample, or release of a product.
2.3.2.2. Interface Analysis
2.3.2.2.1. Explores, identifies, models, and specifies software-user interactions
2.3.2.3. Requirement Analysis
2.3.2.3.1. Diagrams // Flowchart
2.3.3. Research
2.3.3.1. Document Analysis
2.3.3.1.1. Existing documents.
2.3.3.2. Data Analysis
2.3.3.2.1. Statistical analysis of existing data.
3. Validation Engineer
3.1. What are they?
3.1.1. They use CSV (Computer System Validation) to ensure integrity and comppliance with regulatory guidelines.
3.1.2. Digital side of the laboratory process.
3.2. Characteristics of CSVs
3.2.1. Consistent.
3.2.2. Secure.
3.2.3. Accurate.
3.2.4. Traceable.
3.3. What do they ensure?
3.3.1. A validated system has objective evidence that the system works.
3.4. Steps
3.4.1. Plan
3.4.1.1. Start with "master plan".
3.4.1.2. Risk assessment based on master plan.
3.4.2. Write
3.4.2.1. Test cases.
3.4.3. Execute
3.4.3.1. Activate test cases.
3.4.4. Review
3.4.4.1. Do the tests meet the criteria?
3.4.4.2. Account for all observations gathered during the process.
3.4.4.3. Identify variants.
3.5. CA.PA.
3.5.1. Corrective and Preventive measures
3.5.1.1. Short period of time establish to apply measures that counteract the variants found.
3.6. Possible systems
3.6.1. Development
3.6.1.1. Software progress (sometimes dry test runs are performed here).
3.6.2. Test
3.6.2.1. Specifically established for dry test runs.
3.6.3. Production
3.6.3.1. System deployment.