Mostrar mensagens com a etiqueta Report. Mostrar todas as mensagens
Mostrar mensagens com a etiqueta Report. Mostrar todas as mensagens

quinta-feira, 21 de março de 2019

Security: What Are The Most Secure Programming Languages (State of Open Source Security Report)

A report on "security of programming languages" used in open source.

Quoting:
"Behind every developer is a beloved programming language. In heated debates over which language is the best, the security card will come into play in support of one language or discredit another.
We decided to address this debate and put it to the test by researching WhiteSource’s comprehensive database. We focused on open source security vulnerabilities in C, Java, JavaScript, Python, Ruby, PHP, and C++, to find out which programming languages are most secure, which vulnerability types (CWEs) are most common in each language, and why."

What Are The Most Secure Programming Languages

To download the report: https://resources.whitesourcesoftware.com/blog-whitesource/is-one-language-more-secure

Quoting:

"Language vulnerabilities

Let’s look at the list from the report and break it down.
Total reported open source vulnerabilities per language:

  1. C (46.9%)
  2. PHP (16.7%)
  3. Java (11.4%)
  4. JavaScript (10.2%)
  5. Python (5.45%)
  6. C++ (5.23%)
  7. Ruby (4.25%)


WhiteSource pulled their info from their database which includes multiple sources including “the National Vulnerability Database, security advisories, GitHub issue trackers, and popular open source project issue trackers”."

Quote Source: https://jaxenter.com/security-vulnerabilities-languages-157038.html








sábado, 6 de outubro de 2018

REPORT: The State of Developer Ecosystem (JetBrains)

6,000 developers were surveyed to identify the State of Developer Ecosystem in 2018:


https://www.jetbrains.com/research/devecosystem-2018/

Quoting:
"The State of Developer Ecosystem in 2018

In the beginning of 2018 we surveyed 6,000 developers to identify the State of Developer Ecosystem.


Here's what we learned."

terça-feira, 3 de abril de 2018

REPORT: Standish Group 2015 Chaos Report - Q&A with Jennifer Lynch

Project failures, overall, by project size, Agile vs Waterfall and some contributing factors to success (in the opinion of the participants):
Standish Group 2015 Chaos Report - Q&A with Jennifer Lynch

Quoting:

"The 2015 CHAOS Report has recently been released by the Standish Group.  The CHAOS Reports have been published every year since 1994 and are a snapshot of the state of the software development industry.  This year the report studied 50,000 projects around the world, ranging from tiny enhancements to massive systems re-engineering implementations.  This year the report includes an enhanced definition of success looking at some additional factors which were covered in previous surveys.

The results indicate that there is still work to be done around achieving successful outcomes from software development projects. This table summarises the outcomes of projects over the last five years using the new definition of success factors (on time, on budget with a satisfactory result)"
(...)

Listed factors that could help in project success include:

"The definitions for these factors are:
Executive Support: when an executive or group of executives agrees to provide both financial and emotional backing. The executive or executives will encourage and assist in the successful completion of the project.

Emotional maturity is the collection of basic behaviors of how people work together. In any group, organization, or company it is both the sum of their skills and the weakest link that determine the level of emotional maturity.

User Involvement: takes place when users are involved in the project decision-making and information-gathering process. This also includes user feedback, requirements review, basic research, prototyping, and other consensus-building tools.

Optimization is a structured means of improving business effectiveness and optimizing a collection of many small projects or major requirements. Optimization starts with managing scope based on relative business value.

Skilled staff are people who understand both the business and the technology. A skilled staff is highly proficient in the execution of the project’s requirements and deliver of the project or product.

SAME is Standard Architectural Management Environment. The Standish Group defines SAME as a consistent group of integrated practices, services, and products for developing, implementing, and operating software applications.

Agile proficiency means that the agile team and the product owner are skilled in the agile process. Agile proficiency is the difference between good agile outcomes and bad agile outcomes.

Modest execution is having a process with few moving parts, and those parts are automated and streamlined. Modest execution also means using project management tools sparingly and only a very few features.

Project management expertise is the application of knowledge, skills, and techniques to project activities in order to meet or exceed stakeholder expectations and produce value for the organization.

Clear Business Objectives is the understanding of all stakeholders and participants in the business purpose for executing the project. Clear Business Objectives could also mean the project is aligning to the organization’s goals and strategy"

(...)

Success, namely project success is (re)defined as:

"The Standish Group has redefined project success as onTime, onBudget, with a satisfactory result.
Success is hard to define and we had a hard time coming to this conclusion.
Merriam-Webster dictionary defines success as the fact of getting or achieving wealth: respect or fame: the correct or desired result of an attempt; someone or something that is successful: or a person or thing that succeeds.
The Project Management Institute (PMI) has defined success as onTime, onBudget, and onTarget also known as the Triple Constraints and the Iron Triangle. However, we have seen many projects that have met the Triple Constraints and did not return value to the organization or the users and executive sponsor were unsatisfied."




sexta-feira, 26 de janeiro de 2018

REPORT: State of Testing report (PDF)

State of Software Testing Report 2017:
http://qablog.practitest.com/wp-content/uploads/2017/03/State_of_testing_2017_final_report.pdf

And the 2018 edition in the preparation:
http://qablog.practitest.com/state-of-testing/

Quoting;
"What is the State of Testing?
The State of Testing™ seeks to identify the existing characteristics, practices, and challenges facing the testing community in hopes to shed light and provoke a fruitful discussion towards improvement.
The final report is translated into several languages and shared globally, further expanding the reach and impact this report has on all of us in the QA world.
This is the 5th year that the QA Intelligence Blog is running this survey in collaboration with TeaTime with Testers, and with your help,  it can be bigger and more comprehensive than in previous years.
Each year the amount of participants has increased, and the final reports become even more valuable as a culminated reflection of testing trends, challenges, and characteristics."


quinta-feira, 2 de novembro de 2017

Security: CSA guidance V4 (Report)

A collaborative effort on mitigating (security) risks brought together by the Cloud Security Alliance (CSA):
https://cloudsecurityalliance.org/guidance/#_overview

Quoting:
"This version [V4] incorporates advances in cloud, security, and supporting technologies, reflects on real-world cloud security practices, integrates the latest Cloud Security Alliance research projects, and offers guidance for related technologies.

The goal of the fourth version of Security Guidance for Critical Areas of Focus in Cloud Computing is to provide both guidance and inspiration to support business goals while managing and mitigating the risks associated with the adoption of cloud computing technology."

And the V3 PDF can be found here:
https://downloads.cloudsecurityalliance.org/assets/research/security-guidance/csaguide.v3.0.pdf&ved=0ahUKEwjk9NXbw5_XAhWIuRQKHUq1BfYQFggxMAI&usg=AOvVaw3OEGdJjEzR7a4T762_jjLm

segunda-feira, 30 de outubro de 2017

REPORT: 2017 State of DevOps report

https://puppet.com/resources/whitepaper/state-of-devops-report

Quoting:
"Over the past six years and more than 27,000 State of DevOps survey responses, we’ve found clear evidence that DevOps practices yield remarkable results for IT teams and organizations.

This year we also discovered new findings about transformational leadership, automation practices, continuous delivery, lean product management, and DevOps in not-for-profits and organizations that use off-the-shelf software.

Here are a few things you’ll learn in this year's report:

- How DevOps practices affect deployment frequency, lead time, change failure rate and MTTR
- The influence leadership has on DevOps transformations
- How high- and low-performing teams automate differently
- The impact of architecture and team structure on IT performance
- How DevOps helps organizations reach both their financial and non-financial goals."

quinta-feira, 20 de julho de 2017

IoT: Enterprise IoT Solutions and Platform Technology (ThingWorx)

The Short Story

ThingWorx, Enterprise IoT Solutions and Platform Technology (from PTC)

Quoting:
"ThingWorx was purpose-built from the ground up for the Internet of Things. It contains the most complete set of integrated IoT-specific development tools and capabilities available, offering the industry’s deepest functional capabilities.  ThingWorx makes it easy to develop and deliver powerful Enterprise IoT solutions that deliver transformative business value.

The extensive ecosystem of ThingWorx partners exists to create and extend smart, connected capabilities to all things for all industries. The economic impact that the Internet of Things will have on product makers, factories, and other complex systems such as smart cities is projected by McKinsey to reach $11.1 trillion a year by 2025. To capture this value, IoT solutions will be formed of many parts and players, from sensor and hardware providers, to independent software vendors (ISVs) and System Integrators. ThingWorx provides the technology foundation to organizations to capture real value that will transform the way they compete, and the way they work."

The Long Story

Forrester Wave IoT Software Platforms Report | PTC

Other players (per strength categories) include:
- IBM, Microsoft, GE;
- SAP, Amazon Web Services, Cisco Jasper;
- LogMeIn, ExoSite, Ayla Networks, Zebra Technologies.
(lower strength according to Forrester Report, see quadrant image in the Forrester Wave Report).

quinta-feira, 30 de março de 2017

Low-code development platforms?

What are low-code development platforms? Think on platforms that allow for rapid development (some decades ago there were tools called RAD, Rapid Application Development). Ever heard of Outsystems? It is considered a low-code development platform.

The Forrester Wave has reports on this: "Low-Code Development
Platforms, Q2 2016 - The 14 Providers That Matter Most And How They Stack Up."
Google for them,

Quoting Forrester Wave:
"Low-Code Platforms Help Accelerate The Journey To Digital Business:
Digital business means different things to different AD&D leaders. But all agree that speedy, iterative delivery of customer-facing software helps separate digital leaders from digital laggards. Speed is crucial in introducing new disruptive products, engaging and responding to customers across different channels, and adapting existing services based on shifting competitive drivers. This relentless focus on “digital speed” is forcing AD&D leaders to reach for new approaches and platforms that enable  delivery of new apps in days and weeks, instead of months. This shift is also forcing AD&D leaders  to augment coding in programming languages, such as Java and C#/.NET, with new development platforms that emphasize declarative and visual development.

In 2014, Forrester started tracking a rapidly growing software category that we labeled “low-code
platforms.” Forrester defines low-code platforms as:
Platforms that enable rapid delivery of business applications with a minimum of hand-coding and minimal upfront investment in setup, training, and deployment.
The low-code development platforms market consists of wide range of vendors that provide platforms that support building, deploying, and managing apps through declarative tooling that supports visual drag-and-drop composition."

sexta-feira, 17 de fevereiro de 2017

Mobile Development Forrester-Wave Report (PDF)

Interesting resource recently shared with me (PDF) evaluating mobile development platforms, Q4 2016:
And "The Forrester Wave™: Mobile Infrastructure Services, Q3 2015 - Ten Providers That Matter And How They Stack Up", can be downloaded here:


PS. Kudos to Mr. A, Martinho for sharing.

terça-feira, 15 de novembro de 2016

Security: Industrial Control Systems (2016, PDF, Report)

Interesting report on the security of Industrial Control Systems (ICS), FFR:

Overload: Critical Lessons from 15 Years of ICS Vulnerabilities
2016 Industrial Control Systems (ICS) Vulnerability Trend Report


sábado, 4 de junho de 2016

The State of Scrum 2015 Report - Scrumalliance.org (PDF)

Interesting PDF report from the organization that manages the framework:

https://www.scrumalliance.org/scrum/media/scrumalliancemedia/files%20and%20pdfs/state%20of%20scrum/scrum-alliance-state-of-scrum-2015.pdf

Quoting:
"The State of Scrum reports offer comprehensive coverage of global usage of Scrum -- who is using Scrum, where, how, and why. The report also looks at how and where Scrum is best adopted and is growing. "

PS. Heard of it from the "Fluffy Side of Scrum" book authors @ Agile Portugal 2015 (2016-06-05).
(@2016-10-13: Added quote)

sexta-feira, 19 de fevereiro de 2016

On software project failures

Software projects fail a lot. And since software is on most modern equipments (read carefully: almost everywhere) most equipments will also fail when running faulty software produced by some of those projects. This is one of the reasons current systems (meaning hardware + software) will also fail a lot.

How much do software projects fail? It's an interesting question and here are some possible "answers":


The latter study, published on Dr. Dobbs (which is now inactive BTW), criticizes the CHAOS report. On any case, a good percentage of projects fail and / or are challenged (they do not meet the on-quality, on-budget, on-schedule initial criteria). Just look at the trailer, I mean, just look at the numbers.