We found 20 results that contain "mathematical analysis"
Posted on: #iteachmsu
Achieving work life balance is possible with effective time management. Learning time management tips will not only help you manage your time better but also boost personal productivity. With that said, here are some time management strategies you can try:
The 80/20 rule is a technique created by the Italian economist Vilfredo Pareto. It’s the idea that 20% of actions are responsible for 80% of outcomes. The goal of Pareto analysis is to help you prioritize tasks that are most effective at solving problems.
Posted by
over 1 year ago
Achieving work life balance is possible with effective time management. Learning time management tips will not only help you manage your time better but also boost personal productivity. With that said, here are some time management strategies you can try:
The 80/20 rule is a technique created by the Italian economist Vilfredo Pareto. It’s the idea that 20% of actions are responsible for 80% of outcomes. The goal of Pareto analysis is to help you prioritize tasks that are most effective at solving problems.
Disciplinary Content
Posted on: #iteachmsu
Posted by
almost 2 years ago
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
Requirement analysis is the most important and fundamental stage in SDLC. It is performed by the senior members of the team with inputs from the customer, the sales department, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas.
Planning for the quality assurance requirements and identification of the risks associated with the project is also done in the planning stage. The outcome of the technical feasibility study is to define the various technical approaches that can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to clearly define and document the product requirements and get them approved from the customer or the market analysts. This is done through an SRS (Software Requirement Specification) document which consists of all the product requirements to be designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with the best architecture for the product to be developed. Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.
A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules (if any). The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle.
Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. are used to generate the code. Different high level programming languages such as C, C++, Pascal, Java and PHP are used for coding. The programming language is chosen with respect to the type of software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the modern SDLC models, the testing activities are mostly involved in all the stages of SDLC. However, this stage refers to the testing only stage of the product where product defects are reported, tracked, fixed and retested, until the product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is released formally in the appropriate market. Sometimes product deployment happens in stages as per the business strategy of that organization. The product may first be released in a limited segment and tested in the real business environment (UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with suggested enhancements in the targeting market segment. After the product is released in the market, its maintenance is done for the existing customer base.
Disciplinary Content
Posted on: #iteachmsu
Posted by
almost 2 years ago
Full blood counts
Department of Haematology
Notes
Full blood counts are performed on automated equipment and provide haemoglobin concentration, red cell indices, white cell count (with a differential count) and platelet count.
The presence of abnormal white cell and red cell morphology is flagged by the analysers.
Blood films may be inspected to confirm and interpret abnormalities identified by the cell counter, or to look for certain specific haematological abnormalities.
Grossly abnormal FBC results and abnormal blood films will be phoned through to the requestor.
There is no need to request a blood film to obtain a differential white count. It is, however, important that clinical details are provided to allow the laboratory to decide whether a blood film, in addition to the automated analysis, is required.
Under some circumstances a differential is not routinely performed, e.g. pre-op, post-op, antenatal and postnatal requests.
Full Blood Counts are performed at CGH and GRH
See also: Reticulocyte Count
The FBC comprises the following tests
Standard
Haemoglobin (Hb)
White Blood Count (WBC)
Platelet Count (Plt)
Red Cell Count (RBC)
Haematocrit (HCT)
Mean Cell Volume - Red cell (MCV)
Mean Cell Haemoglobin (MCH)
Differential White Cell Count (where applicable)
Neutrophils
Lymphocytes
Monocytes
Eosinophils
Basophils
And if appropriate
Blood Film
Sample Requirements
2ml or 4ml EDTA sample or a Paediatric 1ml EDTA sample.
EDTA with cap
1ml Paediatric EDTA
Sample Storage and Retention
Pre analysis storage: do not store, send to laboratory within 4 hours.
Sample retention by lab: EDTA samples are retained for a minimum of 48 hours at 2-10°C
Transport of samples may affect sample viability, i.e. FBC results will degenerate if exposed to high temperatures, such as prolonged transportation in a hot car in summer.
This test can be added on to a previous request as long as there is sufficient sample remaining and the sample is less than 24 hours old.
Turnaround Times
Clinical emergency: 30 mins
Other urgent sample: 60 mins
Routine: within 2 hours
Reference Ranges
If references ranges are required for paediatric patients please contact the laboratory for these.
Parameter Patient Reference Range Units Haemoglobin Adult Male 130 - 180 g/L Adult Female 115 - 165 g/L Red Cell Count Adult Male 4.50 - 6.50 x10^12/L Adult Female 3.80 - 5.80 x10^12/L Haematocrit Adult Male 0.40 - 0.54 L/L Adult Female 0.37 - 0.47 L/L Mean Cell Volume Adult 80 - 100 fL Mean Cell Haemoglobin Adult 27 - 32 pg White Cell Count Adult 3.6 - 11.0 x10^9/L Neutrophils Adult 1.8 - 7.5 x10^9/L Lymphocytes Adult 1.0 - 4.0 x10^9/L Monocytes Adult 0.2 - 0.8 x10^9/L Eosinophils Adult 0.1 - 0.4 x10^9/L Basophils Adult 0.02 - 0.10 x10^9/L Platelet Count Adult 140 - 400 x10^9/L
Department of Haematology
Notes
Full blood counts are performed on automated equipment and provide haemoglobin concentration, red cell indices, white cell count (with a differential count) and platelet count.
The presence of abnormal white cell and red cell morphology is flagged by the analysers.
Blood films may be inspected to confirm and interpret abnormalities identified by the cell counter, or to look for certain specific haematological abnormalities.
Grossly abnormal FBC results and abnormal blood films will be phoned through to the requestor.
There is no need to request a blood film to obtain a differential white count. It is, however, important that clinical details are provided to allow the laboratory to decide whether a blood film, in addition to the automated analysis, is required.
Under some circumstances a differential is not routinely performed, e.g. pre-op, post-op, antenatal and postnatal requests.
Full Blood Counts are performed at CGH and GRH
See also: Reticulocyte Count
The FBC comprises the following tests
Standard
Haemoglobin (Hb)
White Blood Count (WBC)
Platelet Count (Plt)
Red Cell Count (RBC)
Haematocrit (HCT)
Mean Cell Volume - Red cell (MCV)
Mean Cell Haemoglobin (MCH)
Differential White Cell Count (where applicable)
Neutrophils
Lymphocytes
Monocytes
Eosinophils
Basophils
And if appropriate
Blood Film
Sample Requirements
2ml or 4ml EDTA sample or a Paediatric 1ml EDTA sample.
EDTA with cap
1ml Paediatric EDTA
Sample Storage and Retention
Pre analysis storage: do not store, send to laboratory within 4 hours.
Sample retention by lab: EDTA samples are retained for a minimum of 48 hours at 2-10°C
Transport of samples may affect sample viability, i.e. FBC results will degenerate if exposed to high temperatures, such as prolonged transportation in a hot car in summer.
This test can be added on to a previous request as long as there is sufficient sample remaining and the sample is less than 24 hours old.
Turnaround Times
Clinical emergency: 30 mins
Other urgent sample: 60 mins
Routine: within 2 hours
Reference Ranges
If references ranges are required for paediatric patients please contact the laboratory for these.
Parameter Patient Reference Range Units Haemoglobin Adult Male 130 - 180 g/L Adult Female 115 - 165 g/L Red Cell Count Adult Male 4.50 - 6.50 x10^12/L Adult Female 3.80 - 5.80 x10^12/L Haematocrit Adult Male 0.40 - 0.54 L/L Adult Female 0.37 - 0.47 L/L Mean Cell Volume Adult 80 - 100 fL Mean Cell Haemoglobin Adult 27 - 32 pg White Cell Count Adult 3.6 - 11.0 x10^9/L Neutrophils Adult 1.8 - 7.5 x10^9/L Lymphocytes Adult 1.0 - 4.0 x10^9/L Monocytes Adult 0.2 - 0.8 x10^9/L Eosinophils Adult 0.1 - 0.4 x10^9/L Basophils Adult 0.02 - 0.10 x10^9/L Platelet Count Adult 140 - 400 x10^9/L
Navigating Context
Posted on: #iteachmsu
Posted by
almost 2 years ago
Big data is a collection of large datasets that cannot be processed using traditional computing techniques. Testing of these datasets involves various tools, techniques and frameworks to process. Big data relates to data creation, storage, retrieval and analysis that is remarkable in terms of volume, variety, and velocity. You can learn more about Big Data, Hadoop and Mapreduce here In this tutorial we will learn, Testing Big Data application is more a verification of its data processing rather than testing the individual features of the software product. When it comes to Big data testing, performance and functional testing are the key. In Big data testing QA engineers verify the successful processing of terabytes of data using commodity cluster and other supportive components. It demands a high level of testing skills as the processing is very fast. Processing may be of three types Along with this, data quality is also an important factor in big data testing. Before testing the application, it is necessary to check the quality of data and should be considered as a part of database testing. It involves checking various characteristics like conformity, accuracy, duplication, consistency, validity, data completeness, etc.