CSV SDLC Comparision
•
1 like•267 views
The document compares the CSV (Computer System Validation) process used in pharmaceutical manufacturing to the SDLC (Software Development Life Cycle) process used in IT. Both follow high-level steps of requirements, design, configuration, testing, and maintenance. The CSV process categorizes products as configured, non-configured, infrastructure, custom built, standard, or custom applications, mirroring the different types of software and hardware developed through the SDLC.
Report
Share
Report
Share
Recommended
Functional vs Non-functional Requirements - Which comes first?
What is the actual value of non functional requirements? How to identify them? What is the best practice of managing NFR?
Sw Requirements Engineering
The document discusses requirements engineering for software development. It defines requirements engineering, outlines the requirements engineering process, and describes key requirements documents like the software requirements specification. It also covers topics like requirements attributes, validation, management, and traceability.
Functional and non functional
This document discusses functional and non-functional requirements. Functional requirements describe the behavior of a system and support user goals, while non-functional requirements describe how the system works and make it more usable. Functional requirements should include data descriptions, screen operations, workflows, and access controls. Non-functional requirements should cover usability, reliability, performance, and supportability. Non-functional requirements are further classified into categories like process, delivery, implementation, and external constraints.
Non-functional requirements
The document discusses non-functional requirements (NFRs), including what they are, when they can be used, how acceptance criteria support NFRs, and NFR elicitation. It provides examples of functional vs. non-functional requirements for a fictional "Batmobile" project. It also discusses how Twitter failed to adequately plan for scalability, a common non-functional requirement. Finally, it shares examples of common NFRs like usability, reliability, performance, and maintainability.
software requirement
Types of Requirements
Business requirements
Business rules
User requirements
Functional requirements
Non-functional requirements
External interfaces
Physical product settings
Development constraints
Software requirement specification
Software Requirement Specification definition
Types of requirement
Functional Requirement
Non-Functional Requirement
SRS Document Structure
Importance of SRS
Non-Functional Requirements Are Important (with Explanatory Notes)
This version of the presentation includes extra slides with the text of the speaker's notes as I discovered that Slideshare does not make the notes visible to users.
Software Requirements in Software Engineering SE5
The document introduces software requirements and describes how they are used to define what a system should do. It explains that requirements can be functional or non-functional, and discusses how requirements are organized in documents. Requirements describe the services and constraints for the system from the perspectives of users and developers.
Recommended
Functional vs Non-functional Requirements - Which comes first?
What is the actual value of non functional requirements? How to identify them? What is the best practice of managing NFR?
Sw Requirements Engineering
The document discusses requirements engineering for software development. It defines requirements engineering, outlines the requirements engineering process, and describes key requirements documents like the software requirements specification. It also covers topics like requirements attributes, validation, management, and traceability.
Functional and non functional
This document discusses functional and non-functional requirements. Functional requirements describe the behavior of a system and support user goals, while non-functional requirements describe how the system works and make it more usable. Functional requirements should include data descriptions, screen operations, workflows, and access controls. Non-functional requirements should cover usability, reliability, performance, and supportability. Non-functional requirements are further classified into categories like process, delivery, implementation, and external constraints.
Non-functional requirements
The document discusses non-functional requirements (NFRs), including what they are, when they can be used, how acceptance criteria support NFRs, and NFR elicitation. It provides examples of functional vs. non-functional requirements for a fictional "Batmobile" project. It also discusses how Twitter failed to adequately plan for scalability, a common non-functional requirement. Finally, it shares examples of common NFRs like usability, reliability, performance, and maintainability.
software requirement
Types of Requirements
Business requirements
Business rules
User requirements
Functional requirements
Non-functional requirements
External interfaces
Physical product settings
Development constraints
Software requirement specification
Software Requirement Specification definition
Types of requirement
Functional Requirement
Non-Functional Requirement
SRS Document Structure
Importance of SRS
Non-Functional Requirements Are Important (with Explanatory Notes)
This version of the presentation includes extra slides with the text of the speaker's notes as I discovered that Slideshare does not make the notes visible to users.
Software Requirements in Software Engineering SE5
The document introduces software requirements and describes how they are used to define what a system should do. It explains that requirements can be functional or non-functional, and discusses how requirements are organized in documents. Requirements describe the services and constraints for the system from the perspectives of users and developers.
Software requirement specification
Software Requirement Specification is a most important topic asked in exams and for presentations in B.Tech comp. engg. This presentation contains all the important topic and deep knowledge of SRS.It includes definition, scope, role, how to write srs, template and template description. It tells how to build SRS and also includes examples for ease.
Requirements engineering
This chapter discusses requirements engineering, which involves establishing the services customers require from a system and the constraints it operates under. It describes different types of requirements like functional and non-functional requirements. Functional requirements specify system services and behaviors, while non-functional requirements constrain aspects like timing and development process. The chapter also covers topics like ambiguous requirements, completeness, consistency, and how requirements are documented in a software requirements specification.
software requirement
The document discusses the key activities involved in software requirements: eliciting requirements by meeting with clients to understand their needs; expressing requirements through representations like use cases or user stories; prioritizing requirements by determining essential, important, and optional features; analyzing requirements to ensure the best possible product; and managing requirements as a continuous process of organizing, reprioritizing, and tracking changes to requirements. It also lists common types of requirements like business, user, functional, and non-functional requirements.
Reading Summary - Software Requirements + Characteristics of Well Written Req...
Reading Summary - Software Requirements + Characteristics of Well Written Req...Artemisa Yescas Engler
[WIEGERS-2003], Chapter 1
[WIEGERS-2003], Chapter 2
[WIEGERS-2003], Chapter 3
[WIEGERS-2003], Chapter 5Non functional performance requirements v2.2
How to write and structure non-functional requirements. Focusing upon performance requirements. This is a quick get you going guide in how to avoid writing untestable requirements and make sure what you want is delivered.
Software Specification Requirement
This document outlines the requirements for an eCommerce product to be developed by IBEE Solutions. It includes sections for an introduction, overall description of the product, external interface requirements, functional requirements for both the front-end storefront and back-end administrative tools, non-functional requirements regarding usability, performance, and compatibility. The functional requirements section lists over 40 specific requirements for features like registration, login, product catalog, search, shopping cart, and administrative functions such as managing products, categories, orders, and reports. The document provides a detailed outline of system requirements to guide development of the eCommerce platform.
Requirements engineering
The document discusses key aspects of requirements engineering including types of requirements, the requirements engineering process, and techniques used in requirements elicitation and analysis. It describes user requirements, system requirements, functional requirements, non-functional requirements, and domain requirements. The requirements engineering process involves activities like feasibility studies, requirements elicitation and analysis, requirements specification, validation, and management. Requirements elicitation and analysis techniques include requirements discovery, classification, prioritization, documentation, and dealing with issues that can arise.
Software Requiremnets
This document discusses different levels of software requirements including business requirements, user requirements, functional requirements, and non-functional requirements. It also describes the importance of involving stakeholders, and outlines characteristics of good requirement statements and specifications such as being complete, consistent, unambiguous, and traceable.
Quality attributes
The document discusses quality attributes that affect system design. It identifies four types of quality attributes: runtime system qualities, non-runtime system qualities, business qualities, and architecture qualities. Runtime system qualities include functionality, performance, security, and usability. Non-runtime qualities include modifiability, portability, reusability, and testability. Business qualities are cost and marketability. Architecture qualities are integrity and correctness. The document emphasizes that as an architect, understanding how design choices impact these quality attributes is important.
Non functional requirement
The document provides details on common nonfunctional requirements for software systems:
1) Availability specifies the percentage of time the system is expected to be operational and available for use.
2) Performance constraints identify software functions that have timing requirements.
3) Reliability specifies the system's ability to maintain its performance over time and tolerate failures in sensitive tasks.
3) Integrity, scalability, usability, and other nonfunctional aspects influence the system design and development.
The software requirements specification
The document discusses the Software Requirements Specification (SRS) which is a communication tool between stakeholders and software designers. The SRS aims to describe the scope of work, provide a reference for software designers, provide a framework for testing, include customer requirements, and allow for ongoing refinement. An example organization of an SRS is provided which includes sections on introduction, system overview, user interfaces, requirements, and more. Characteristics of a good SRS are also listed, such as being correct, unambiguous, complete, consistent, ranked, verifiable, modifiable, and traceable.
software engineering
This document discusses requirements engineering and its key processes. It describes how requirements engineering involves eliciting requirements through activities like interviews and prototyping. It also involves analyzing requirements by documenting them, resolving conflicts between stakeholder needs, and validating requirements. The document stresses the importance of requirements engineering in defining a system's functionality and ensuring project success.
SRS(software requirement specification)
The document defines an SRS as the official statement of what system developers should implement, providing a complete description of the system behavior. An SRS precisely defines the software product and is used to understand requirements to design the software. It includes the purpose, product scope, features, interfaces, and other functional and non-functional requirements. The SRS benefits include establishing agreement between customers and suppliers, reducing development effort, and providing a baseline for validation.
Software requirement and specification
The document discusses software requirements and specifications. It explains that requirements engineering is the process of establishing customer requirements for a system. Requirements can range from high-level abstract statements to detailed functional specifications. Both types of statements may be called requirements. The document also discusses different types of requirements like user requirements, system requirements, functional requirements, and non-functional requirements. It provides examples and explanations of each. The structure and intended users of a requirements document are also covered.
Non Functional Requirement.
Non-functional requirements describe how a system will operate rather than what it will do. They include qualities like usability, reliability, performance, and supportability. Usability measures how easy a system is to use, learn, and adapt to user needs. Reliability refers to the likelihood of failures and is measured by metrics like mean time between failures. Performance requirements specify the system's efficiency and response times. Supportability involves how easily a system can be maintained, internationalized, and adapted to changes.
software requirement specification
Software requirement document is official statement of what the system developers should implement.
Chap4 RE validation
Requirements validation certifies that the requirements document accurately describes the system to be built. It checks for completeness, consistency, standards compliance, and technical errors. Validation analyzes the final requirements document, while analysis works with initial requirements. Validation inputs include the requirements document and organizational standards. Outputs are a problem list and agreed actions. Requirements reviews involve analyzing the document for problems, discussing issues, and agreeing on solutions. Validation techniques include reviews, prototyping, modeling, and testing.
Validation and part 11 compliance of computer systems and data
Analytical and other equipment should be qualified and computer systems should be validated to demonstrate suitability for the intended use. Electronic records must comply with FDA Part 11 and EU/PICS GMP Annex 11 requirements to ensure data integrity, security and availability.
Requirement Management 3
The document discusses the importance of properly defining software requirements and the risks of inadequate requirements processes. It outlines three levels of software requirements - business, user, and functional requirements. Between 40-60% of defects can be traced back to errors in the requirements stage. The requirements must be documented and represent the needs of users external to the system. Risks of poor requirements include insufficient user involvement, creeping requirements, and inaccurate planning.
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
The Electrocardiogram - Physiologic Principles
These lecture slides, by Dr Sidra Arshad, offer a quick overview of the physiological basis of a normal electrocardiogram.
Learning objectives:
1. Define an electrocardiogram (ECG) and electrocardiography
2. Describe how dipoles generated by the heart produce the waveforms of the ECG
3. Describe the components of a normal electrocardiogram of a typical bipolar lead (limb II)
4. Differentiate between intervals and segments
5. Enlist some common indications for obtaining an ECG
6. Describe the flow of current around the heart during the cardiac cycle
7. Discuss the placement and polarity of the leads of electrocardiograph
8. Describe the normal electrocardiograms recorded from the limb leads and explain the physiological basis of the different records that are obtained
9. Define mean electrical vector (axis) of the heart and give the normal range
10. Define the mean QRS vector
11. Describe the axes of leads (hexagonal reference system)
12. Comprehend the vectorial analysis of the normal ECG
13. Determine the mean electrical axis of the ventricular QRS and appreciate the mean axis deviation
14. Explain the concepts of current of injury, J point, and their significance
Study Resources:
1. Chapter 11, Guyton and Hall Textbook of Medical Physiology, 14th edition
2. Chapter 9, Human Physiology - From Cells to Systems, Lauralee Sherwood, 9th edition
3. Chapter 29, Ganong’s Review of Medical Physiology, 26th edition
4. Electrocardiogram, StatPearls - https://www.ncbi.nlm.nih.gov/books/NBK549803/
5. ECG in Medical Practice by ABM Abdullah, 4th edition
6. Chapter 3, Cardiology Explained, https://www.ncbi.nlm.nih.gov/books/NBK2214/
7. ECG Basics, http://www.nataliescasebook.com/tag/e-c-g-basics
More Related Content
What's hot
Software requirement specification
Software Requirement Specification is a most important topic asked in exams and for presentations in B.Tech comp. engg. This presentation contains all the important topic and deep knowledge of SRS.It includes definition, scope, role, how to write srs, template and template description. It tells how to build SRS and also includes examples for ease.
Requirements engineering
This chapter discusses requirements engineering, which involves establishing the services customers require from a system and the constraints it operates under. It describes different types of requirements like functional and non-functional requirements. Functional requirements specify system services and behaviors, while non-functional requirements constrain aspects like timing and development process. The chapter also covers topics like ambiguous requirements, completeness, consistency, and how requirements are documented in a software requirements specification.
software requirement
The document discusses the key activities involved in software requirements: eliciting requirements by meeting with clients to understand their needs; expressing requirements through representations like use cases or user stories; prioritizing requirements by determining essential, important, and optional features; analyzing requirements to ensure the best possible product; and managing requirements as a continuous process of organizing, reprioritizing, and tracking changes to requirements. It also lists common types of requirements like business, user, functional, and non-functional requirements.
Reading Summary - Software Requirements + Characteristics of Well Written Req...
Reading Summary - Software Requirements + Characteristics of Well Written Req...Artemisa Yescas Engler
[WIEGERS-2003], Chapter 1
[WIEGERS-2003], Chapter 2
[WIEGERS-2003], Chapter 3
[WIEGERS-2003], Chapter 5Non functional performance requirements v2.2
How to write and structure non-functional requirements. Focusing upon performance requirements. This is a quick get you going guide in how to avoid writing untestable requirements and make sure what you want is delivered.
Software Specification Requirement
This document outlines the requirements for an eCommerce product to be developed by IBEE Solutions. It includes sections for an introduction, overall description of the product, external interface requirements, functional requirements for both the front-end storefront and back-end administrative tools, non-functional requirements regarding usability, performance, and compatibility. The functional requirements section lists over 40 specific requirements for features like registration, login, product catalog, search, shopping cart, and administrative functions such as managing products, categories, orders, and reports. The document provides a detailed outline of system requirements to guide development of the eCommerce platform.
Requirements engineering
The document discusses key aspects of requirements engineering including types of requirements, the requirements engineering process, and techniques used in requirements elicitation and analysis. It describes user requirements, system requirements, functional requirements, non-functional requirements, and domain requirements. The requirements engineering process involves activities like feasibility studies, requirements elicitation and analysis, requirements specification, validation, and management. Requirements elicitation and analysis techniques include requirements discovery, classification, prioritization, documentation, and dealing with issues that can arise.
Software Requiremnets
This document discusses different levels of software requirements including business requirements, user requirements, functional requirements, and non-functional requirements. It also describes the importance of involving stakeholders, and outlines characteristics of good requirement statements and specifications such as being complete, consistent, unambiguous, and traceable.
Quality attributes
The document discusses quality attributes that affect system design. It identifies four types of quality attributes: runtime system qualities, non-runtime system qualities, business qualities, and architecture qualities. Runtime system qualities include functionality, performance, security, and usability. Non-runtime qualities include modifiability, portability, reusability, and testability. Business qualities are cost and marketability. Architecture qualities are integrity and correctness. The document emphasizes that as an architect, understanding how design choices impact these quality attributes is important.
Non functional requirement
The document provides details on common nonfunctional requirements for software systems:
1) Availability specifies the percentage of time the system is expected to be operational and available for use.
2) Performance constraints identify software functions that have timing requirements.
3) Reliability specifies the system's ability to maintain its performance over time and tolerate failures in sensitive tasks.
3) Integrity, scalability, usability, and other nonfunctional aspects influence the system design and development.
The software requirements specification
The document discusses the Software Requirements Specification (SRS) which is a communication tool between stakeholders and software designers. The SRS aims to describe the scope of work, provide a reference for software designers, provide a framework for testing, include customer requirements, and allow for ongoing refinement. An example organization of an SRS is provided which includes sections on introduction, system overview, user interfaces, requirements, and more. Characteristics of a good SRS are also listed, such as being correct, unambiguous, complete, consistent, ranked, verifiable, modifiable, and traceable.
software engineering
This document discusses requirements engineering and its key processes. It describes how requirements engineering involves eliciting requirements through activities like interviews and prototyping. It also involves analyzing requirements by documenting them, resolving conflicts between stakeholder needs, and validating requirements. The document stresses the importance of requirements engineering in defining a system's functionality and ensuring project success.
SRS(software requirement specification)
The document defines an SRS as the official statement of what system developers should implement, providing a complete description of the system behavior. An SRS precisely defines the software product and is used to understand requirements to design the software. It includes the purpose, product scope, features, interfaces, and other functional and non-functional requirements. The SRS benefits include establishing agreement between customers and suppliers, reducing development effort, and providing a baseline for validation.
Software requirement and specification
The document discusses software requirements and specifications. It explains that requirements engineering is the process of establishing customer requirements for a system. Requirements can range from high-level abstract statements to detailed functional specifications. Both types of statements may be called requirements. The document also discusses different types of requirements like user requirements, system requirements, functional requirements, and non-functional requirements. It provides examples and explanations of each. The structure and intended users of a requirements document are also covered.
Non Functional Requirement.
Non-functional requirements describe how a system will operate rather than what it will do. They include qualities like usability, reliability, performance, and supportability. Usability measures how easy a system is to use, learn, and adapt to user needs. Reliability refers to the likelihood of failures and is measured by metrics like mean time between failures. Performance requirements specify the system's efficiency and response times. Supportability involves how easily a system can be maintained, internationalized, and adapted to changes.
software requirement specification
Software requirement document is official statement of what the system developers should implement.
Chap4 RE validation
Requirements validation certifies that the requirements document accurately describes the system to be built. It checks for completeness, consistency, standards compliance, and technical errors. Validation analyzes the final requirements document, while analysis works with initial requirements. Validation inputs include the requirements document and organizational standards. Outputs are a problem list and agreed actions. Requirements reviews involve analyzing the document for problems, discussing issues, and agreeing on solutions. Validation techniques include reviews, prototyping, modeling, and testing.
Validation and part 11 compliance of computer systems and data
Analytical and other equipment should be qualified and computer systems should be validated to demonstrate suitability for the intended use. Electronic records must comply with FDA Part 11 and EU/PICS GMP Annex 11 requirements to ensure data integrity, security and availability.
Requirement Management 3
The document discusses the importance of properly defining software requirements and the risks of inadequate requirements processes. It outlines three levels of software requirements - business, user, and functional requirements. Between 40-60% of defects can be traced back to errors in the requirements stage. The requirements must be documented and represent the needs of users external to the system. Risks of poor requirements include insufficient user involvement, creeping requirements, and inaccurate planning.
What's hot (19)
Reading Summary - Software Requirements + Characteristics of Well Written Req...
Reading Summary - Software Requirements + Characteristics of Well Written Req...
Validation and part 11 compliance of computer systems and data
Validation and part 11 compliance of computer systems and data
Recently uploaded
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa CentralClinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
The Electrocardiogram - Physiologic Principles
These lecture slides, by Dr Sidra Arshad, offer a quick overview of the physiological basis of a normal electrocardiogram.
Learning objectives:
1. Define an electrocardiogram (ECG) and electrocardiography
2. Describe how dipoles generated by the heart produce the waveforms of the ECG
3. Describe the components of a normal electrocardiogram of a typical bipolar lead (limb II)
4. Differentiate between intervals and segments
5. Enlist some common indications for obtaining an ECG
6. Describe the flow of current around the heart during the cardiac cycle
7. Discuss the placement and polarity of the leads of electrocardiograph
8. Describe the normal electrocardiograms recorded from the limb leads and explain the physiological basis of the different records that are obtained
9. Define mean electrical vector (axis) of the heart and give the normal range
10. Define the mean QRS vector
11. Describe the axes of leads (hexagonal reference system)
12. Comprehend the vectorial analysis of the normal ECG
13. Determine the mean electrical axis of the ventricular QRS and appreciate the mean axis deviation
14. Explain the concepts of current of injury, J point, and their significance
Study Resources:
1. Chapter 11, Guyton and Hall Textbook of Medical Physiology, 14th edition
2. Chapter 9, Human Physiology - From Cells to Systems, Lauralee Sherwood, 9th edition
3. Chapter 29, Ganong’s Review of Medical Physiology, 26th edition
4. Electrocardiogram, StatPearls - https://www.ncbi.nlm.nih.gov/books/NBK549803/
5. ECG in Medical Practice by ABM Abdullah, 4th edition
6. Chapter 3, Cardiology Explained, https://www.ncbi.nlm.nih.gov/books/NBK2214/
7. ECG Basics, http://www.nataliescasebook.com/tag/e-c-g-basics
Best Ayurvedic medicine for Gas and Indigestion
Here is the updated list of Top Best Ayurvedic medicine for Gas and Indigestion and those are Gas-O-Go Syp for Dyspepsia | Lavizyme Syrup for Acidity | Yumzyme Hepatoprotective Capsules etc
share - Lions, tigers, AI and health misinformation, oh my!.pptx
• Pitfalls and pivots needed to use AI effectively in public health
• Evidence-based strategies to address health misinformation effectively
• Building trust with communities online and offline
• Equipping health professionals to address questions, concerns and health misinformation
• Assessing risk and mitigating harm from adverse health narratives in communities, health workforce and health system
REGULATION FOR COMBINATION PRODUCTS AND MEDICAL DEVICES.pptx
It includes regulation of combination products and medical devices. FDA and industry liaisons.
Top-Vitamin-Supplement-Brands-in-India List
Swisschem Dermacare provides the Top 10 Vitamin Supplement Brands in India. To know more about us give us call at our official number
Integrating Ayurveda into Parkinson’s Management: A Holistic Approach
Explore the benefits of combining Ayurveda with conventional Parkinson's treatments. Learn how a holistic approach can manage symptoms, enhance well-being, and balance body energies. Discover the steps to safely integrate Ayurvedic practices into your Parkinson’s care plan, including expert guidance on diet, herbal remedies, and lifestyle modifications.
Efficacy of Avartana Sneha in Ayurveda
Avartana Sneha is a unique method of Preparation of Sneha Kalpana in Ayurveda, mainly it is indicated for the Vataja rogas.
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Kat...
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Kat...rightmanforbloodline
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Katzung, Verified Chapters 1 - 66, Complete Newest Version.
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Katzung, Verified Chapters 1 - 66, Complete Newest Version.
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Katzung, Verified Chapters 1 - 66, Complete Newest Version.
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Katzung, Verified Chapters 1 - 66, Complete Newest Version.Post-Menstrual Smell- When to Suspect Vaginitis.pptx
Do you have abnormal smell after periods? It may be vaginitis. Do not worry, herbal medicine Fuyan Pill can help you get a cure.
Recently uploaded (20)
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
Clinic ^%[+27633867063*Abortion Pills For Sale In Tembisa Central
Tests for analysis of different pharmaceutical.pptx
Tests for analysis of different pharmaceutical.pptx
Ear and its clinical correlations By Dr. Rabia Inam Gandapore.pptx
Ear and its clinical correlations By Dr. Rabia Inam Gandapore.pptx
share - Lions, tigers, AI and health misinformation, oh my!.pptx
share - Lions, tigers, AI and health misinformation, oh my!.pptx
REGULATION FOR COMBINATION PRODUCTS AND MEDICAL DEVICES.pptx
REGULATION FOR COMBINATION PRODUCTS AND MEDICAL DEVICES.pptx
Integrating Ayurveda into Parkinson’s Management: A Holistic Approach
Integrating Ayurveda into Parkinson’s Management: A Holistic Approach
CHEMOTHERAPY_RDP_CHAPTER 6_Anti Malarial Drugs.pdf
CHEMOTHERAPY_RDP_CHAPTER 6_Anti Malarial Drugs.pdf
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Kat...
TEST BANK For Basic and Clinical Pharmacology, 14th Edition by Bertram G. Kat...
Post-Menstrual Smell- When to Suspect Vaginitis.pptx
Post-Menstrual Smell- When to Suspect Vaginitis.pptx
Vestibulocochlear Nerve by Dr. Rabia Inam Gandapore.pptx
Vestibulocochlear Nerve by Dr. Rabia Inam Gandapore.pptx
CSV SDLC Comparision
- 1. CSV | SDLC End result is the same Aniruddha Mehta
- 2. THE BIG COMPARISION The big similarity between Pharma and IT Industry.
- 3. High Level Steps Requirements Design Configure Test Maintenance User Requirements Functional Requirements Risk Analysis/Impact Analysis System Design Hardware Requirements Business Design Coding, Customisation, Integration, Configuration Installation Qualification Operational Qualification Performance Qualification Tracebility Matrix Risk Assesment Validation Summary Report Sounds Similar !
- 4. Category 4 Configured Products Category 3 Non- Configured Software Categorization Category 1 Infrastructure Software Hardware Category 2 Custom built Hardware Components Hardware Category 1 Standard Hardware Components Category 5 Custom Applications