Agile communication is quicker than traditional software
development communication in the following ways:
First, the project teams are "co-located" so that any
questions are immediately answered instead of using phones,
email, etc to ask coworkers for ideas, thoughts or answers.
Every day an Agile team meets for a quick 15 minute meeting
(sometimes called a daily scrum) to refine what tasks were
completed the previous day, what will be done by the team
today and what impediments are prohibiting the team from
getting the work done.
Agile teams are constantly refining scope based on empirical
data from previous releases, test results and discoveries
where traditional projects design and code up to the
delivery date only to discover problems when it's very
expensive to correct.
2. Online Clinical SAS Training Outline.
The focus of the lectures will be mainly on the following
topics:
Our Course syllabus in SAS:-
• Base SAS training
• Advance SAS training
• Clinical SAS Training with Project
• SAS certification
Clinical SAS Course Content:
• Introduction To Sas And Clinical research
• SAS role in Clinical Research
• Project Management in Clinical Research
• What is Clinical Research?
• What is Protocol and role of Protocol in Clinical
Research?
• What is randomization and non randomization?
• Which is playing main role in Clinical Research?
• What is SOP (Standard Operating Procedure)
• Role of DBMS team in Clinical Research
• What is CDM (Clinical Data Management)?
• Importance of CDM systems for data loading
• What is SAP (Statistical Analysis Plan)?
• Role of SAP in Clinical Research
• SAS Work Flow in Clinical Research
• Relation between SAS and DBMS
• Interaction between SAS with CDMs for data access
• Various report generation in Clinical Research
PART-I
BASE SAS:
• Introduction To SAS System & Architecture
• History And Various Modules
• Variables & SAS Syntax Rules
• SAS Data Sets
• Data Set Options
• Operators
• If - Then Else Statement
• Where Statement
• Creating & Redefining Variables
• Reading Raw Data
• Infile Statement With Options
• Multiple Observations and Multiple Datasets.
• Input Styles
• SAS Functions
• Select Statement
• Do Loops
• Output Statement & Put Statement
• Stop And Error Statement s
• Array Statement
• Modifying And Combining Data Sets
• Updating Master Data Set
• Key Board Macros & Add Abbreviations
BASE SAS PROCEDURES
• Proc Sort
• Proc Print
• Proc Means
• Proc Freq
• Proc Plot
• Proc Chart
• Proc Compare
• Proc Copy
• Proc Summary
• Proc Append
• Proc Datasets
• Proc Contents
• Proc Delete
• Proc Format
• Proc Printto
• SAS/ODS:
• Creating Rtf File
• Creating Html File
• Creating Pdf File
• Creating Xml File
PART -II
ORACLE-SQL CONCEPTS:
• Introduction
• History
• Features
• Sql Command Set
• Operators In Sql
• Order By Clause
• Group By Clause
• Having Clause
• Distinct Clause
• Create and Insert
• Deleting, Populating And Updating
• SAS/SQL:
• Introduction To SAS/SQL
• Features & Uses
• Terminology
• Data Types, Key Words, & Operators
• Functions, Predicate s & Functions
• Formatting Output
• Group By Clause, Order By Clause & Having Clause
• Case Expression and Condition al Logic.
• Creating ,Populating & Deleting Tables
• Alter Table Statement
• Renaming A Table & Columns
• Changing Column's Length
• Joins & Views
SAS/ACCESS:
• Import & Export Procedure s
• Importing data from Ms-Access & Ms- Excel
• Importing data from Oracle database
• DbLoad Procedure
• SAS/GRAPH :
• Gchart Procedure
• Vertical, Horizonta l, Pie
• Donut
• Group, Subgroups
• Gplot Procedure
• Mutliple Plots & Overlay
• Symbol Statement
• Title and Footnote Statement s
• Goptions
• SAS/MACROS :
• Macro Concepts
• Macros And Macro Variables
• Creating Macro Variables
• Using Macro Variables
• Creating Modular Code With Macros
• Invoking A Macro
• Adding Parameter s To Macros
• Macros With Condition al Logic
• Using Various Procedure s In Macros
• Automatic Variables
• Macro Functions
3. When we write Test cases? & Why we will write Testing?
Test Case is a document which acts as refrence or record.
Test case includes not only test input and expected behavior
but also test step and description and pass fail criteria.
It is a good practice if we write a test case before we
execute it. It will give a brief idea that what we have to
test. In addition to this it acts as record which can be
used by new tester to understand and then test.
When putting a system together, the different components
interacting may show unexpected behaviors. It is hard to be
able to predict these completely.
A typical example happens in power plants when running steam
boilers or power generators in parallel. The load is not
distributed evenly, as would happen on a stand alone unit,
but needs to be constantly tweaked.
In addition, there are unexpected configurations resulting
from the installation itself, which create unstable modes
due to interaction. These must be addressed and proper
compensation through the control system be applied,
Cleanroom development uses an iterative approach, in which
the product is developed in increments that gradually
increase the implemented functionality. The quality of each
increment is measured against pre-established standards to
verify that the development process is proceeding
acceptably. A failure to meet quality standards results in
the cessation of testing for the current increment, and a
return to the design phase.
In Load Testing, we measure the response time and throughput
for a web based application which has a large number of users.
In Stress testing, we test the same application for slightly
more number of users than it is intended to be used.
7. Explain How you test a Pen?
Using One Note (or many) of MS.And based on the
specifications for the Pen,test the pen.
8. Explain What are the beta test and alpha test?
Beta test & Alpha tests are type of Acceptance Testing.Beta
testing is performed at the client's site in the absence of
the development team.Whereas alpha testing is performed at
the developor's site.
9. Can you explain Difference between ISO and CMM level?
The difference is that the CMM is a way to communicate
capabilities, and ISO is a way to communicate the process.
They are not necessarily incompatible.
The Capability Maturity Model is a very specific way of
classifying an organization's software development methods.
In a certain way, it tells how the quality of its software
designs is likely to be repeated.
ISO-9000 procedures describe a (possibly) definite
development process but gives no indication of the likely
quality of the designs or whether multiple software efforts
are likely to produce software of similar quality.
A quality management system in accordance with ISO 9001:2000
will provide your organization with a set of processes that
ensure a common sense approach to the management of your
organization.
The system should ensure consistency and improvement of
working practices, which in turn should provide products and
services that meet customer's requirements. ISO 9000 is the
most commonly used international standard that provides a
framework for an effective quality management system.
