SPSS

SPSS:-

SPSS Statistics is a software package used for logical batched and non-batched statistical analysis. Long produced by SPSS Inc., it was acquired by IBM in 2009. The current versions (2015) are officially named IBM SPSS Statistics. Companion products in the same family are used for survey authoring and deployment (IBM SPSS Data Collection, now divested under UNICOM Intelligence), data mining (IBM SPSS Modeler), text analytics, and collaboration and deployment (batch and automated scoring services).

The software name originally stood for Statistical Package for the Social Sciences (SPSS), reflecting the original market, although the software is now popular in other fields as well, including the health sciences and marketing.

Statistics included in the base software:

• Descriptive statistics: Cross tabulation, Frequencies, Descriptives, Explore, Descriptive Ratio Statistics
• Bivariate statistics: Means, t-test, ANOVA, Correlation (bivariate, partial, distances), Nonparametric tests, Bayesian
• Prediction for numerical outcomes: Linear regression
• Prediction for identifying groups: Factor analysis, cluster analysis (two-step, K-means, hierarchical), Discriminant
• Geospatial analysis, simulation
• R extension(GUI)

Why IBM SPSS Software?

IBM SPSS platform offers advanced statistical analysis, a vast library of machine learning algorithms, text analysis, open source extensibility, integration with big data and seamless deployment into applications. Its easy-to-use, flexible and scalable platform makes IBM SPSS accessible to users with all skill levels and outfits projects of all sizes and complexity to help you and your organization to find new opportunities, improve efficiency and minimize risk.

SQA(SOFTWARE QUALITY ASSURANCE)

SQA:-

SQA helps ensure the development of high-quality software. SQA practices are implemented in most types of software development, regardless of the underlying software development model being used. In a broader sense, SQA incorporates and implements software testing methodologies to test software. Rather than checking for quality after completion, SQA processes test for quality in each phase of development until the software is complete. With SQA, the software development process moves into the next phase only once the current/previous phase complies with the required quality standards.

SQA generally works on one or more industry standards that help in building software quality guidelines and implementation strategies. These standards include the ISO 9000 and capability maturity model integration (CMMI).

Quality Assurance Criteria:

Below are the Quality assurance criteria against which the software would be evaluated against:

• correctness
• efficiency
• flexibility
• integrity
• interoperability
• maintainability
• portability
• reliability
• reusability
• testability
• usability

What is Quality Control?

Quality control is a set of methods used by organizations to achieve quality parameters or quality goals and continually improve the organization's ability to ensure that a software product will meet quality goals.

Quality Control Process:

The three class parameters that control software quality are:

• Products
• Processes
• Resources

The total quality control process consists of:

• Plan - It is the stage where the Quality control processes are planned
• Do - Use a defined parameter to develop the quality
• Check - Stage to verify if the quality of the parameters are met
• Act - Take corrective action if needed and repeat the work

Quality Control characteristics:

• Process adopted to deliver a quality product to the clients at best cost.
• Goal is to learn from other organizations so that quality would be better each time.
• To avoid making errors by proper planning and execution with correct review process.

Activities of Software Quality Management:

• Quality Assurance - QA aims at developing Organizational procedures and standards for quality at Organizational level.
• Quality Planning - Select applicable procedures and standards for a particular project and modify as required to develop a quality plan.
• Quality Control - Ensure that best practices and standards are followed by the software development team to produce quality products.

SOFTWARE PROJECT SCHEDULING

What Is Project Scheduling?

Project scheduling is a mechanism to communicate what tasks need to get done and which organizational resources will be allocated to complete those tasks in what timeframe. A project schedule is a document collecting all the work needed to deliver the project on time.

A project is made up of many tasks, and each task is given a start and end (or due date), so it can be completed on time. Likewise, people have different schedules, and their availability and vacation or leave dates need to be documented in order to successfully plan those tasks.We need special kinds of software for that.

Because projects have so many moving parts and are frequently changing, project scheduling software automatically updates tasks that are dependent on one another, when one scheduled task is not completed on time. It also generates automated email alerts, so team members know when their scheduled tasks are due or overdue, and to let the manager know when someone’s availability has changed.

How to Schedule a Project

1. What needs to be done?
2. When will it be done?
3. Who will do it?

Once you’ve got answers to these questions, then you can begin to plan dates, link activities, set the duration, milestones, and resources. The following are the steps needed to schedule a project:

Define Activities

What are the activities that you have to do in the project? By using a Work Breakdown Structure (WBS) and a deliverables diagram, you can begin to take these activities and organize them by mapping out the tasks necessary to complete them in an order that makes sense.

Do Estimates

Now that you have the activities defined and broken down into tasks, you next have to determine the time and effort it will take to complete them. This is an essential piece of the equation in order to calculate the correct schedule.

Determine Dependencies

Tasks are not an island, and often one cannot be started until the other is completed. That’s called a task dependency, and your schedule is going to have to reflect these linked tasks. One way to do this is by putting a bit of slack in your schedule to accommodate these related tasks.

Assign Resources

The last step to finalizing your planned schedule is to decide on what resources you are going to need to get those tasks done on time. You’re going to have to assemble a team, and their time will need to be scheduled just like the tasks.