The document discusses the need for standards around measuring and accounting for non-functional requirements (NFRs) and project requirements and constraints (PRCs) in software project performance, benchmarking, and estimating. There is currently no common understanding of NFRs across the industry. The COSMIC and IFPUG organizations have developed a joint glossary to help standardize terms for NFRs and PRCs, in order to improve consistency in measuring, benchmarking, and estimating software projects. They have agreed on defining and structuring the terms in the glossary to help bring more coherence to how these critical non-functional aspects are addressed.
When do software issues get reported in large open source software - Rakesh RanaIWSM Mensura
This document summarizes a study examining reporting patterns of issues and bugs in five large open source software projects. The study found:
1) While there are distinct variations in when defects are reported, the ratio of reported defects to actual defects remains fairly stable over time.
2) Using reported defect inflow data in software reliability growth models results in predicted asymptotes that on average deviate only 4.8% from models using actual defect data.
3) The reporting patterns provide insights into groups of people who contribute to open source projects, with more issues reported mid-week and fewer on weekends and Mondays.
Tips and hints for an effective cosmic learning process gained from industria...IWSM Mensura
This document provides an overview of common issues encountered in COSMIC functional size measurement (FSM) trainings conducted with industrial professionals. It describes the diverse audience profiles and objectives of the trainings. The trainings involve both group theory sessions and individual practical exercises using company case studies. Some highlighted issues include difficulties understanding why FSM is a good estimation method, focusing on technical rather than requirements aspects, accounting for non-functional requirements, determining the appropriate level of granularity, and properly identifying data groups and data movement. The document aims to better understand challenges faced by trainees and improve the training approach.
Workshop early or rapid cosmic fsm - Frank VogelezangIWSM Mensura
This document discusses various approximation approaches that can be used for early or rapid COSMIC functional size measurement (FSM). It outlines reasons why approximation may be needed, such as for speed, timing or quality reasons. It then describes established approximation approaches like average functional process, fixed size classification, equal size bands, average use case, Early & Quick (EASY), and EPCU. Newer approaches discussed include textual requirements and machine learning classification. The document emphasizes that approaches need local calibration. It provides an example application of various approaches to estimate the size of a web advice module, finding estimates ranging from 39.6 to 56.1 COSMIC function points.
Practical usage of fpa and automatic code review piotr popovskiIWSM Mensura
This document discusses Orange Polska's use of function point analysis (FPA) for estimating the size, effort, and pricing of IT projects, as well as their use of automated code review. It describes how Orange Polska counts over 1 million function points annually across 800 projects in many technologies. It also explains their four-step process for converting function points to price, including custom adjustment rules. Additionally, it outlines the quality metrics and tools used for automated code review of vendors' source code.
Requirements effort estimation state of the practice - mohamad kassabIWSM Mensura
This document summarizes the results of a survey on requirements engineering practices. It found that while agile practices are widely used, many classic requirements techniques are still common, including interviews, prototyping, and use case modeling. Effort estimation is still important for projects of all sizes, with story points and expert judgment being frequently used. Both agile and waterfall projects reported high satisfaction with productivity and quality, though agile projects tended to have higher satisfaction. Overall the survey found that while agile has increased in popularity, many requirements practices are still applied across both agile and traditional methodologies.
Machine Learning Approach for Quality Assessmentand Prediction in Large Soft...RAKESH RANA
This document proposes a machine learning approach for assessing and predicting software quality in large organizations. It suggests using ML techniques within the ISO/IEC 15939 measurement information model framework. Specifically, it recommends using historical metrics data to train ML models that can classify different quality characteristics and predict overall quality based on measurable attributes, without needing to explicitly define the relationships. The proposed approach has benefits like being self-improving as more data is collected over time, making it suitable for software quality analysis in large organizations.
The significance of ifpug base functionality types in effort estimation cig...IWSM Mensura
This document presents an empirical study on the significance of IFPUG base functionality types (BFC types) in effort estimation. The study uses project data from the ISBSG repository to analyze how using multiple BFC types versus just total function points affects estimation accuracy. The results show that using combinations of BFC types, such as EQ and EIF, leads to higher R2 values and better model fitting than using just total function points. The conclusions are that profiling projects by BFC type distribution can provide more accurate effort estimates than only considering total size.
Continuous Security / DevSecOps- Why How and WhatMarc Hornbeek
This presentation explains what Continuous Security / DevSecOps is, Why it is important, How it works and What you can do to realized a well-engineered DevSecOps solution in your own organization or enterprise.
When do software issues get reported in large open source software - Rakesh RanaIWSM Mensura
This document summarizes a study examining reporting patterns of issues and bugs in five large open source software projects. The study found:
1) While there are distinct variations in when defects are reported, the ratio of reported defects to actual defects remains fairly stable over time.
2) Using reported defect inflow data in software reliability growth models results in predicted asymptotes that on average deviate only 4.8% from models using actual defect data.
3) The reporting patterns provide insights into groups of people who contribute to open source projects, with more issues reported mid-week and fewer on weekends and Mondays.
Tips and hints for an effective cosmic learning process gained from industria...IWSM Mensura
This document provides an overview of common issues encountered in COSMIC functional size measurement (FSM) trainings conducted with industrial professionals. It describes the diverse audience profiles and objectives of the trainings. The trainings involve both group theory sessions and individual practical exercises using company case studies. Some highlighted issues include difficulties understanding why FSM is a good estimation method, focusing on technical rather than requirements aspects, accounting for non-functional requirements, determining the appropriate level of granularity, and properly identifying data groups and data movement. The document aims to better understand challenges faced by trainees and improve the training approach.
Workshop early or rapid cosmic fsm - Frank VogelezangIWSM Mensura
This document discusses various approximation approaches that can be used for early or rapid COSMIC functional size measurement (FSM). It outlines reasons why approximation may be needed, such as for speed, timing or quality reasons. It then describes established approximation approaches like average functional process, fixed size classification, equal size bands, average use case, Early & Quick (EASY), and EPCU. Newer approaches discussed include textual requirements and machine learning classification. The document emphasizes that approaches need local calibration. It provides an example application of various approaches to estimate the size of a web advice module, finding estimates ranging from 39.6 to 56.1 COSMIC function points.
Practical usage of fpa and automatic code review piotr popovskiIWSM Mensura
This document discusses Orange Polska's use of function point analysis (FPA) for estimating the size, effort, and pricing of IT projects, as well as their use of automated code review. It describes how Orange Polska counts over 1 million function points annually across 800 projects in many technologies. It also explains their four-step process for converting function points to price, including custom adjustment rules. Additionally, it outlines the quality metrics and tools used for automated code review of vendors' source code.
Requirements effort estimation state of the practice - mohamad kassabIWSM Mensura
This document summarizes the results of a survey on requirements engineering practices. It found that while agile practices are widely used, many classic requirements techniques are still common, including interviews, prototyping, and use case modeling. Effort estimation is still important for projects of all sizes, with story points and expert judgment being frequently used. Both agile and waterfall projects reported high satisfaction with productivity and quality, though agile projects tended to have higher satisfaction. Overall the survey found that while agile has increased in popularity, many requirements practices are still applied across both agile and traditional methodologies.
Machine Learning Approach for Quality Assessmentand Prediction in Large Soft...RAKESH RANA
This document proposes a machine learning approach for assessing and predicting software quality in large organizations. It suggests using ML techniques within the ISO/IEC 15939 measurement information model framework. Specifically, it recommends using historical metrics data to train ML models that can classify different quality characteristics and predict overall quality based on measurable attributes, without needing to explicitly define the relationships. The proposed approach has benefits like being self-improving as more data is collected over time, making it suitable for software quality analysis in large organizations.
The significance of ifpug base functionality types in effort estimation cig...IWSM Mensura
This document presents an empirical study on the significance of IFPUG base functionality types (BFC types) in effort estimation. The study uses project data from the ISBSG repository to analyze how using multiple BFC types versus just total function points affects estimation accuracy. The results show that using combinations of BFC types, such as EQ and EIF, leads to higher R2 values and better model fitting than using just total function points. The conclusions are that profiling projects by BFC type distribution can provide more accurate effort estimates than only considering total size.
Continuous Security / DevSecOps- Why How and WhatMarc Hornbeek
This presentation explains what Continuous Security / DevSecOps is, Why it is important, How it works and What you can do to realized a well-engineered DevSecOps solution in your own organization or enterprise.
This document summarizes a 30-minute talk on engineering DevOps given by Marc Hornbeek. The talk discusses defining engineering DevOps, how to engineer people, processes, and technology for DevOps. It also covers how to engineer applications, pipelines, and infrastructures for DevOps. The talk presents a seven-step DevOps engineering transformation blueprint and discusses the future of engineering DevOps beyond continuous improvement. The document provides benefits of a well-engineered DevOps approach and why engineering is needed to implement DevOps successfully. It also summarizes DevOps engineering tools and maturity levels.
This presentation explains how testing activities constitute the main bottleneck to flow in most continuous delivery pipelines. Continuous Testing strategies are designed to reduce testing bottlenecks, and accelerate time-to-quality.
A blueprint is presented for Continuous Testing. Specific strategies are presented including Continuous Test Tenets, Leadership and Culture practices, Test strategies and Plans, Test Management, Test Automation, Test Tools, Test Environment Management and Test Results Analysis. A Continuous Testing Assessment approach is described to help assess current state of of continuous testing. A phased implementation approach is explained.
Haradhan Pal has over 9 years of experience in software testing, including automation and manual testing. He has worked in the retail, travel, and insurance domains, testing applications like Oracle, web applications, and GuideWire Billing Center. Currently he works as an Offshore Test Lead at Cognizant Technology Solutions in Kolkata. He has expertise in test automation with QTP and test management tools like Quality Center.
This document provides an overview of independent verification and validation (IV&V) as used by NASA. It defines IV&V as a rigorous software evaluation process conducted throughout development to ensure quality and correctness. Key points include that IV&V independently assesses whether the product is being built correctly and if the correct product is being built. IV&V aims to identify risks and increase quality, safety, timeliness and reliability while reducing costs.
This document presents an overview of independent verification and validation (IV&V) provided by Maneat. It defines verification as evaluating work products to ensure they meet requirements, while validation ensures the product meets user needs. The benefits of IV&V include improved quality, reduced costs and failures. Maneat's 5-step methodology covers the full lifecycle and priorities include understanding business flows and risks. Maneat tailors its IV&V approach to each client's needs and industry.
This document contains contact and professional information for Rathna Arun Solomon, including a summary of his work experience as a Business/Data Analyst and QA professional over 8 years, primarily in the banking and retail domains. It lists 6 projects he has worked on, highlighting his roles and responsibilities, as well as technical skills and qualifications.
This presentation will give you insights into where the testing industry will be in 2020 and what are the skills required to survive in the testing world.
Thuy Tran has over 5 years of experience as a Test Analyst and Quality Control Engineer. She has expertise in manual testing, performance testing, API testing, and some automation testing using tools like Selenium and QTP. She has worked on projects in various domains including banking, retail, and government. Her technical skills include languages like Java, .NET, and databases like SQL Server and MySQL.
The effects of duration based moving windows with estimation by analogy - sou...IWSM Mensura
Fixed-size and fixed-duration moving windows were evaluated with estimation by analogy (EbA) effort estimation. With fixed-size windows, the modified EbA showed moving windows became significantly advantageous over the growing portfolio at medium window sizes, while trends were similar but ranges differed from past studies. With fixed-duration windows, moving windows improved accuracy less significantly than fixed-size windows over smaller window sizes. Comparisons with past studies found overall trends the same but effective window sizes and ranges differed.
This document contains the resume of Sandeep Reddy Amaram. It summarizes his career objective, professional experience, educational background, skills, and projects. He has 4 years of experience as a manual and database tester. He is proficient in testing methodologies and has experience using tools like Quality Center and Oracle Database. He has worked on projects in finance and banking domains as a tester and software engineer.
I have been working on a new breed of estimation methodologies called "Open estimation methodologies". They can be called "Deliverable based estimation methodologies" also. This presentation is about this family of methodologies.
The key to a successful project is being able to quickly and effectively identify the quality of the application under test
For a multi-shore project this can be achieved with automation and test frameworks, an agile integrated testing model, and visibility and communication across the process.
The document provides an overview of the International Software Testing Qualifications Board (ISTQB). It discusses ISTQB's mission to advance the software testing profession through defining a body of knowledge, connecting the international testing community, and encouraging research. ISTQB offers certification programs at the Foundation, Advanced, and Expert levels, and its syllabi are available in many languages. Surveys have found benefits of ISTQB certification for both professionals and their employers, including improved productivity, recognition of skills, and increased marketability. The document also summarizes ISTQB's Agile Tester Extension, which aims to satisfy the growing demand for skills in agile testing environments.
The document is a curriculum vitae for Prasad that summarizes their professional experience and qualifications. Prasad has over 12 years of experience in software quality assurance, including testing web applications, APIs, databases, and both Agile and traditional development methodologies. They are currently a SIT analyst for CGI UK testing a smart metering program.
Madhusudana Akkasali has over 14 years of experience in testing roles including 9 years onsite at clients like IBM, AT&T, and Walmart. He has experience in test management, test delivery, test process transformation, and currently works on cloud migration projects. He leads teams of up to 25 people and has experience testing applications in various industries including banking, retail, petroleum, and telecom.
QualityGate measures and monitors the source code's quality continuously, provides real-time feedback on the change of low and high-level quality attributes of the software. It also qualifies the system in terms of maintainability based on hundreds of source code metrics, coding issues, vulnerabilities, code copies, etc. By comparing these attributes to thousands of other systems' in our benchmarks, you get an objective picture where your system stands in terms of maintainability compared to others. Of course, it is not only the quality of the system that is revealed but also the reasons that led to the particular qualification. This can be used by the developers to improve maintainability in a straightforward way. You can also use QualityGate to keep track of individual developer performance, which can either help you revealing motivational and competence-related issues or let you adopt a performance-based rewarding system.
• Total Experience (in Years): 8 Years 5 Months
• Experienced Software Testing Professional with overall 8+ years of experience,
• Performed Test Automation using QTP , Selenium
• Experience in preparing automation scripts in Linear driven, Modular driven, Data Driven automation frameworks
• Performed Mobile testing , Cloud Testing
• Expertise in Functional, Regression and UAT testing
• Worked on waterfall and agile methodologies
This is a free module from my course ISTQB CTAL Test Manager revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
Cloud computing is the delivery of computing resources as a service over the Internet. It allows users to access software and data stored on remote servers. TABS, an existing telecom management system, could be adapted for use in cloud computing in several ways. It could be offered as a cloud-based service for managing both telecom and cloud services. Its features could be abstracted to support cloud management. And its development process could utilize cloud-based tools to improve collaboration. This would help align TABS with the cloud-focused strategy of its new owner, Huawei.
This document discusses a unified ontology of cloud computing architecture and proposes modifications to account for service-oriented architecture, network architecture, and a federated cloud model. It also summarizes the Network Centric Operations Industry Consortium's mission to facilitate global interoperability across joint operations. Finally, it argues that developing "operational art" through collaboration can help establish cloud computing interoperability standards that meet government needs while not dictating solutions to industry.
This document summarizes a 30-minute talk on engineering DevOps given by Marc Hornbeek. The talk discusses defining engineering DevOps, how to engineer people, processes, and technology for DevOps. It also covers how to engineer applications, pipelines, and infrastructures for DevOps. The talk presents a seven-step DevOps engineering transformation blueprint and discusses the future of engineering DevOps beyond continuous improvement. The document provides benefits of a well-engineered DevOps approach and why engineering is needed to implement DevOps successfully. It also summarizes DevOps engineering tools and maturity levels.
This presentation explains how testing activities constitute the main bottleneck to flow in most continuous delivery pipelines. Continuous Testing strategies are designed to reduce testing bottlenecks, and accelerate time-to-quality.
A blueprint is presented for Continuous Testing. Specific strategies are presented including Continuous Test Tenets, Leadership and Culture practices, Test strategies and Plans, Test Management, Test Automation, Test Tools, Test Environment Management and Test Results Analysis. A Continuous Testing Assessment approach is described to help assess current state of of continuous testing. A phased implementation approach is explained.
Haradhan Pal has over 9 years of experience in software testing, including automation and manual testing. He has worked in the retail, travel, and insurance domains, testing applications like Oracle, web applications, and GuideWire Billing Center. Currently he works as an Offshore Test Lead at Cognizant Technology Solutions in Kolkata. He has expertise in test automation with QTP and test management tools like Quality Center.
This document provides an overview of independent verification and validation (IV&V) as used by NASA. It defines IV&V as a rigorous software evaluation process conducted throughout development to ensure quality and correctness. Key points include that IV&V independently assesses whether the product is being built correctly and if the correct product is being built. IV&V aims to identify risks and increase quality, safety, timeliness and reliability while reducing costs.
This document presents an overview of independent verification and validation (IV&V) provided by Maneat. It defines verification as evaluating work products to ensure they meet requirements, while validation ensures the product meets user needs. The benefits of IV&V include improved quality, reduced costs and failures. Maneat's 5-step methodology covers the full lifecycle and priorities include understanding business flows and risks. Maneat tailors its IV&V approach to each client's needs and industry.
This document contains contact and professional information for Rathna Arun Solomon, including a summary of his work experience as a Business/Data Analyst and QA professional over 8 years, primarily in the banking and retail domains. It lists 6 projects he has worked on, highlighting his roles and responsibilities, as well as technical skills and qualifications.
This presentation will give you insights into where the testing industry will be in 2020 and what are the skills required to survive in the testing world.
Thuy Tran has over 5 years of experience as a Test Analyst and Quality Control Engineer. She has expertise in manual testing, performance testing, API testing, and some automation testing using tools like Selenium and QTP. She has worked on projects in various domains including banking, retail, and government. Her technical skills include languages like Java, .NET, and databases like SQL Server and MySQL.
The effects of duration based moving windows with estimation by analogy - sou...IWSM Mensura
Fixed-size and fixed-duration moving windows were evaluated with estimation by analogy (EbA) effort estimation. With fixed-size windows, the modified EbA showed moving windows became significantly advantageous over the growing portfolio at medium window sizes, while trends were similar but ranges differed from past studies. With fixed-duration windows, moving windows improved accuracy less significantly than fixed-size windows over smaller window sizes. Comparisons with past studies found overall trends the same but effective window sizes and ranges differed.
This document contains the resume of Sandeep Reddy Amaram. It summarizes his career objective, professional experience, educational background, skills, and projects. He has 4 years of experience as a manual and database tester. He is proficient in testing methodologies and has experience using tools like Quality Center and Oracle Database. He has worked on projects in finance and banking domains as a tester and software engineer.
I have been working on a new breed of estimation methodologies called "Open estimation methodologies". They can be called "Deliverable based estimation methodologies" also. This presentation is about this family of methodologies.
The key to a successful project is being able to quickly and effectively identify the quality of the application under test
For a multi-shore project this can be achieved with automation and test frameworks, an agile integrated testing model, and visibility and communication across the process.
The document provides an overview of the International Software Testing Qualifications Board (ISTQB). It discusses ISTQB's mission to advance the software testing profession through defining a body of knowledge, connecting the international testing community, and encouraging research. ISTQB offers certification programs at the Foundation, Advanced, and Expert levels, and its syllabi are available in many languages. Surveys have found benefits of ISTQB certification for both professionals and their employers, including improved productivity, recognition of skills, and increased marketability. The document also summarizes ISTQB's Agile Tester Extension, which aims to satisfy the growing demand for skills in agile testing environments.
The document is a curriculum vitae for Prasad that summarizes their professional experience and qualifications. Prasad has over 12 years of experience in software quality assurance, including testing web applications, APIs, databases, and both Agile and traditional development methodologies. They are currently a SIT analyst for CGI UK testing a smart metering program.
Madhusudana Akkasali has over 14 years of experience in testing roles including 9 years onsite at clients like IBM, AT&T, and Walmart. He has experience in test management, test delivery, test process transformation, and currently works on cloud migration projects. He leads teams of up to 25 people and has experience testing applications in various industries including banking, retail, petroleum, and telecom.
QualityGate measures and monitors the source code's quality continuously, provides real-time feedback on the change of low and high-level quality attributes of the software. It also qualifies the system in terms of maintainability based on hundreds of source code metrics, coding issues, vulnerabilities, code copies, etc. By comparing these attributes to thousands of other systems' in our benchmarks, you get an objective picture where your system stands in terms of maintainability compared to others. Of course, it is not only the quality of the system that is revealed but also the reasons that led to the particular qualification. This can be used by the developers to improve maintainability in a straightforward way. You can also use QualityGate to keep track of individual developer performance, which can either help you revealing motivational and competence-related issues or let you adopt a performance-based rewarding system.
• Total Experience (in Years): 8 Years 5 Months
• Experienced Software Testing Professional with overall 8+ years of experience,
• Performed Test Automation using QTP , Selenium
• Experience in preparing automation scripts in Linear driven, Modular driven, Data Driven automation frameworks
• Performed Mobile testing , Cloud Testing
• Expertise in Functional, Regression and UAT testing
• Worked on waterfall and agile methodologies
This is a free module from my course ISTQB CTAL Test Manager revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
Cloud computing is the delivery of computing resources as a service over the Internet. It allows users to access software and data stored on remote servers. TABS, an existing telecom management system, could be adapted for use in cloud computing in several ways. It could be offered as a cloud-based service for managing both telecom and cloud services. Its features could be abstracted to support cloud management. And its development process could utilize cloud-based tools to improve collaboration. This would help align TABS with the cloud-focused strategy of its new owner, Huawei.
This document discusses a unified ontology of cloud computing architecture and proposes modifications to account for service-oriented architecture, network architecture, and a federated cloud model. It also summarizes the Network Centric Operations Industry Consortium's mission to facilitate global interoperability across joint operations. Finally, it argues that developing "operational art" through collaboration can help establish cloud computing interoperability standards that meet government needs while not dictating solutions to industry.
The document discusses the Jitterbit Harmony Spring'15 cloud integration platform. It allows for seamless integration between cloud and on-premise systems, providing real-time data across applications like ERP and call centers. Key features include a unified subscription-based platform for simple integration, plug-and-play deployment options, and an elastic cloud agent network for secure connectivity globally. New capabilities in the release include a new "Sonic Architecture" for improved performance and reliability, as well as reliable messaging to ensure data delivery.
Cloud Computing: A New Computing Paradigm
Welcome to an interactive Webinar on Cloud Computing which has brought about a new approach to developing, deploying and managing applications at scale. With its unique and efficient on-demand and elastic capabilities it can level the playing field for companies from start-ups to large corporations.
Speaker Profile: Viswanathan K (Vish) was most recently VP of Engineering and CIO at Yahoo! India R&D. He has over 20 years experience in the IT industry in Internet, Brokerage, Financial Services and Telecom verticals. About 14 years of his professional career was spent in the US working for large multinationals.
Google App Engine is a platform for building and hosting web applications in Google's cloud. It allows developers to build, run, and maintain applications without having to manage infrastructure. Some key features include automatic scaling for traffic, simple administration, and a free usage tier. Over 250,000 developers have built over 250 million apps on App Engine using languages including Java, Python, PHP and JavaScript.
AS400 webservices - the adapter create cloud apps in a couple of days112Motion
1. The document describes how WAS400 can be used to implement a modern business services layer on top of an AS/400 system for purchase order processing.
2. It shows how WAS400 generates web services from AS/400 tables and RPG programs, replicates transactional data, and supports integrating the AS/400 with modern applications and systems.
3. The example implementation creates web services for AS/400 sales order entry and implements new purchasing and warehousing solutions using business rules and workflow that integrate with the AS/400 through WAS400.
This document provides an introduction to concepts and design principles for building applications with Harmony. It discusses how Harmony can be used to model business processes and logic using common flowchart elements like dialogs, rules, templates and data references. Decision tables are introduced as a way to capture complex logic. The document gives an overview of the key concepts in Harmony and provides an example case of building an online tourism booking application. It demonstrates how to model workflows, access data, send emails and add more advanced features to the application using Harmony's tools.
The document discusses the importance of non-functional requirements (NFRs) in software development. It notes that NFRs such as performance, reliability, and usability must be defined, tested, and validated throughout the development lifecycle. Ignoring NFRs can negatively impact the cost, timeline, and ultimate success of a project. The document provides examples of different types of NFRs and urges considering stakeholders' perspectives to prioritize the most important NFRs to test.
What are the impacts of using COSMIC in an organization and what benefits can you expect, as presented on the Congreso Nacional de Medición y Estimación de Software in Mexico City.
The document outlines a checklist of non-functional requirements for software development projects. It includes sections on security, audit, performance, capacity, availability, reliability, integrity, recovery, compatibility, maintainability, usability, and documentation. Each section lists specific requirements to consider such as login requirements, response times, storage needs, backup frequencies, look and feel standards, and required documentation.
The document introduces Google App Engine (GAE). It discusses that GAE allows developers to build applications that run on Google's infrastructure, providing scalability and efficiency. It also overview cloud computing concepts and GAE's features like dynamic web applications, data storage, and additional services. Finally, it provides a toy example of a GAE application and how to develop applications using the Python SDK.
This document outlines a Service Level Agreement between JK Production and National Bank for the provision of digital media services. The SLA details the services to be provided, including updating an image gallery and content, software reviews and upgrades, and tutorials. It also specifies the requirements and responsibilities of both the service provider and client, as well as service measurements, reporting, requests, and any exceptions. The SLA is effective until superseded and will be reviewed quarterly.
An SLA (Service Level Agreement) defines the relationship between a developer and client by outlining standards and expectations for a project. It aims to reduce risks and strengthen the relationship through clear communication. Key elements an SLA should include are choosing a methodology, ensuring customer involvement through regular meetings and issue management, and defining requirements management processes. While not a legal contract, following the terms of an SLA is important to maintain trust in the relationship.
This document discusses different types of software requirements. It outlines functional requirements that specify system behaviors and non-functional requirements that specify qualities like usability, reliability, and performance. Domain requirements capture characteristics specific to the application area. Inverse requirements specify what a system should not do. Design and implementation constraints provide guidelines for system development. Metrics are important for quantifying non-functional requirements so they can be objectively tested. Requirements should be explored from different perspectives and categorized to best inform system design and development.
In 2004, with only 150,000 registered users and very little revenue, Facebook raised $500,000 and less than a year later raised another $12.7 million. It was not the most popular social network nor was it even the most popular college social network. So what metrics were early indicators of it's future success?
How do Software Architects consider Non-Functional Requirements - An explorat...Jordi Cabot
Software architects consider non-functional requirements in their work but there is room for improvement. The study interviewed 12 software architects and found they often had other primary roles. Architects struggled with terminology around non-functional requirements and mainly focused on usability and performance. Non-functional requirements were usually elicited iteratively by architects alone without documentation and validation was limited. Tool support for managing non-functional requirements was not used. The study contributes new insights but also found some inconsistencies with prior work suggesting more research is needed.
So you have a website, blog, social media, and other digital platforms, but how do you know if your efforts are worthwhile? How do you know if you should measure unique page views, organic reach, retweets, or some other metric? This presentation explores how to figure out which digital metrics matter most for your organization, and how to use them to take meaningful action and advance your mission. We revieww hich digital metrics matter most for your organization, key metrics (almost) every organization should be capturing, and tools and processes for collecting, reporting, and putting data into action.
This presentation features case studies and how-tos for collecting and reporting data from digital platforms such as websites, blogs, Facebook, and Twitter.
Experimental Study Using Functional Size Measurement in Building Estimation M...Luigi Buglione
This paper reports on an experiment that investigates the predictability of software project size from software product size. The predictability research problem is analyzed at the stage of early requirements by accounting the size of functional requirements as well as the size of non-functional requirements. The experiment was carried out with 55 graduate students in Computer Science from Concordia University in Canada. In the experiment, a functional size measure and a project size measure were used in building estimation models for sets of web application development projects. The results show that project size is predictable from product size. Further replications of the experiment are, however, planed to obtain more results to confirm or disconfirm our claim.
CloudSim is a framework for modeling and simulating cloud computing infrastructures and services. It allows modeling of datacenters, virtual machines, hosts, and workloads. Key components include data centers, hosts, virtual machines, brokers, and cloudlets. It supports modeling of policies for resource provisioning and scheduling.
This document summarizes a presentation on CloudSim 2.0, a toolkit for modeling and simulating cloud computing environments. CloudSim 2.0 features include modeling large cloud environments, simulating resource allocation policies, and simulating federated cloud networks. The presentation describes CloudSim's layered architecture, including modeling data centers, virtual machines, workloads, and power consumption. It also discusses experiments in CloudSim for evaluating scalability, hybrid cloud provisioning strategies, and energy-efficient management of data centers.
IWSM2014 COSMIC masterclass part 2 - dealing with NFR (Chris Woodward)Nesma
The document outlines the agenda and goals of the COSMIC Masterclass on dealing with non-functional requirements. It discusses challenges in measuring non-functional requirements and proposes focusing on detailed functional requirements implemented in software. A taxonomy is presented to organize non-functional requirements into quality requirements, true non-functional requirements, technical constraints, system demographics, and project constraints. The document also discusses evolving requirements and measurement as a project progresses from outline to detailed levels. Next steps include defining standard sets of project constraints and system demographics.
The document summarizes a COSMIC masterclass on measuring non-functional requirements (NFRs) using the COSMIC method. It discusses challenges in measuring NFRs, how NFRs evolve over a project's lifecycle, and proposes distinguishing NFR-related effort from functional requirements effort. A taxonomy is presented to organize NFRs into independent categories including quality requirements, technical constraints, system demographics, and project constraints. Next steps include defining standard sets of project constraints and demographics.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Project backup repository and avoiding requirements creepAswin Vijayakumar
Requirements Engineering to use a backup repository to develop a software project management methodology used within Agile. Fit Criterion, Refinery, Traceability and Deployment are key techniques
Software Requirements and Specificationsvustudent1
CS510 - SRS handouts for Computer Science students of Virtual University of Pakistan.
Prepared by ForumVU.com Staff from the updated lectures and PowerPoint slides of CS510 - Software Requirements and Specifications in VU LMS.
Efficient use of Standards-based Interfaces and Encodings in Geospatial Intel...Luis Bermudez
Presentation provided at GEOINT 2019. This training session Provides an overview of OGC standards that have been adapted by National System for Geospatial Intelligence (NSG) specifications. It will enable GEOINT professionals to more efficiently use standards-based interfaces and encoding formats to solve geospatial problems. By equipping GEOINT professionals with the skills to identify and apply OGC standards, this training course will improve the professionals’ ability to meet challenges within their day-to-day work.
Presentation on the promises and pitfalls of applying Agile in a Quality Management System. How do you get the benefits of agile while maintaining quality and regulatory compliance?
Analyst360 is one of the largest and most forward-thinking learning services providers in the world,
delivering more than 10 million hours of training globally each year.
Analyst360 is one of the largest and most forward-thinking learning services providers in the world,
delivering more than 10 million hours of training globally each year.
Bertrandt | Automotive Best Practice: How to Design, Review, Approve, and Eff...Intland Software GmbH
This talk was presented by Alexandros Velikis (Bertrandt AG) at Intland Connect: Annual User Conference 2020 on 22 Oct 2020. To learn more, visit: https://intland.com/intland-connect-annual-user-conference-2020/
Retrospective and Trends in Requirements Engineering for Embedded Systems: A ...Tarcísio Couto
This document summarizes the results of a systematic literature review on requirements engineering for embedded systems. The review analyzed 75 studies published between 1970 and 2016. Key results include identifying important requirements to consider at the enterprise, system, and context levels. Requirements engineering contributions focused on integrating requirements and architecture, specifying safety requirements, and integrating hardware and software. Important challenges are applying the studies to industry projects, further specifying safety and non-functional requirements, and addressing variability in embedded systems development.
Requirements' Quality Improvement: A Successful Case StudyThe REUSE Company
This document summarizes a presentation on improving requirements quality. It discusses how poor quality requirements can impact projects and introduces requirements quality analysis. It then describes a proof of concept project conducted with a company to test a requirements quality suite tool. The project involved benchmarking tools, defining quality metrics, analyzing a specification, modifying requirements, and assessing the results. The proof of concept demonstrated the tool's ability to improve requirements quality and established next steps to further enhance requirements processes.
The document proposes using software requirement patterns (SRPs) to improve requirements engineering (RE) by enabling reuse of textual requirements. It defines SRPs as templates that generate natural language requirements from parameters. A PAtterns Based RE framework (PABRE) is designed to facilitate SRP use, addressing research questions about SRP structure/semantics, integration into RE processes, and benefits. The approach involves defining SRPs and a catalog, designing and implementing the PABRE system, and validating the framework and assets. Future work includes improving SRP relationships, evolving PABRE assets, and conducting a validation case study.
This presentation is about a lecture I gave within the "Software systems and services" immigration course at the Gran Sasso Science Institute, L'Aquila (Italy): http://cs.gssi.infn.it/.
http://www.ivanomalavolta.com
Analyzing Natural-Language Requirements: The Not-too-sexy and Yet Curiously D...Lionel Briand
The document discusses challenges in analyzing natural language requirements and how natural language processing (NLP) techniques can help address these challenges. It describes challenges faced by industry such as ensuring compliance with templates, handling domain knowledge, enabling traceability and change impact analysis, and configuring requirements. It then discusses approaches developed through collaborative research to help with template conformance checking, change impact analysis between requirements, and analyzing impact of changes from requirements to design. The approaches leverage NLP techniques such as text chunking, syntactic and semantic analysis. Evaluation with industrial partners found the approaches to be effective at analyzing hundreds of requirements with high accuracy and limiting unnecessary inspection effort during change.
Cordoba Corp: Best Practices for Security Camera ImplementationCordoba Corp
This document outlines best practices for implementing a district-wide security camera system at Long Beach City College. It discusses initial project steps like forming a core project team and developing standard operating procedures. It also covers the design process, including defining coverage requirements and integrating the system with local law enforcement. Finally, it addresses procurement, construction phasing to minimize impacts, and planning for future projects and maintenance. The goal is to provide a comprehensive overview of implementing a large-scale security camera system.
Traceability Beyond Source Code: An Elusive Target?Lionel Briand
This document discusses traceability beyond source code, which is an elusive target. It provides an overview and examples from industrial research projects on requirements-requirements, requirements-design, requirements-test cases traceability. The examples show challenges in capturing changes precisely and change rationales. Automated traceability approaches can reduce effort but may lack accuracy required for certification. Traceability is important for certification, change management and economic decision making.
This document discusses software quality management standards. It defines software quality and explains that standards aim to manage quality and development processes. The document outlines three major standards activities: software quality assurance which establishes organizational procedures; software quality plans which select applicable procedures for a project; and software quality control which ensures procedures are followed. It provides examples of standards organizations and types of standards including quality assurance, project management, system engineering, safety, and product standards. The document also notes some problems with software quality standards.
This document provides an overview of commissioning data centers. It discusses the roles and responsibilities of various members of the commissioning team, including the owner, architect, commissioning provider, general contractor, and facilities management staff. It outlines the commissioning process from programming and design through construction, acceptance testing, and occupancy. It also notes how commissioning data centers differs from commissioning typical office buildings due to data centers being mission critical facilities.
Similar to Accounting for non functional and project requirements - cosmic and ifpug development - talmon ben-cnaan - charles symons (20)
Software or service that's the question luigi buglioneIWSM Mensura
The document discusses knowledge management (KM) in the context of maturity and capability models (MCMs) for software and services. It presents CMMI-DEV/SVC and ISO 15504-2 as examples of horizontal MCMs that reference KM. CMMI-DEV/SVC only mention KM practices in GP 2.5, while ISO 15504-2 defines a knowledge management process (RIN.3) with specific base practices. The document also reviews other KM frameworks like APQC KMMM, Siemens KMMM, ONTOKNOM, and G-KMMM that provide staged representations for assessing KM maturity levels.
Quantitative functional change impact analysis in activity diagrams a cosmi...IWSM Mensura
This document proposes a COSMIC-based approach to analyze the impact of functional changes in UML activity diagrams. It classifies functional change impacts into three directions: internal impact, intra-level impact, and inter-level impact. It also identifies three categories of functional change based on their size: minor, moderate, and major. The approach is demonstrated on a sample activity diagram for a ticket vending machine. In conclusion, analyzing functional change impacts in UML diagrams using the COSMIC method can help decision making regarding change requests.
Performance measurement of agile teams harold van heeringenIWSM Mensura
This document discusses performance measurement of agile teams working on continuous development projects. It proposes using an Agile Normalized Size (ANS) metric to more accurately measure productivity when sprints include both functional and non-functional backlog items. The ANS estimates the functional size that could have been delivered if only functional items were in the sprint backlog. This allows comparing productivity to benchmarks based on functional size. It helps address issues that can arise when traditional metrics like hours per function point are distorted by non-functional work in sprints.
Measurement as-a-service a new way of organizing metrics programs - wilhelm m...IWSM Mensura
MaaS (Measurement as a Service) is a model where metrics are licensed through subscriptions, hosted centrally, collected automatically and delivered on demand. It provides benefits like reduced costs, faster reporting, and improved uptime compared to traditional measurement approaches. Key enablers of MaaS include standards, automation of data collection and processing, cloud-based storage, and a dedicated metrics team. MaaS allows organizations to optimize their measurement programs.
Improving the cosmic approximate sizing using the fuzzy logic epcu model al...IWSM Mensura
The document describes an experiment to improve the accuracy of the COSMIC functional size measurement (FSM) method for early stage software projects. It uses a fuzzy logic model called EPCU, which considers two variables - the perceived size of use cases and number of related objects of interest - to estimate functional size. The experiment applied the EPCU model and traditional "equal size bands" approach to estimate sizes for 14 use cases. The EPCU model initially underestimated sizes but accuracy improved when expanding the output range, demonstrating its sensitivity to variable definitions. Further experiments are needed with more test cases to validate the approach.
Functional size measurement for processor load estimation hassan soubraIWSM Mensura
This document summarizes a study that examined the relationship between functional size measurement (FSM) and processor load for software models in AUTOSAR. The study developed linear regression models to estimate processor load based on COSMIC FSM. An automation tool was created to measure FSM for AUTOSAR models to speed up the data collection process. The regression models were found to estimate processor load with 90% accuracy based on evaluation with 24 software models.
From software to service sustainability a still broader perspective - luigi...IWSM Mensura
The document discusses expanding the view of sustainability from software products to services. It proposes hybridizing software and service management models to leverage value management. The goals are to take a broader view of sustainability as an ISO standard characteristic and lower project costs by applying the same standards to both software and services, which often only differ in name. While software and services sometimes compete, they can also work together toward value through outcomes. Future work includes measuring sustainability systematically for both domains and benchmarking through hybrid models.
Estimation and measuring of software size within the atos gobal delivery plat...IWSM Mensura
The document discusses Atos' use of functional point analysis (FPA) for software estimation within its Global Delivery Platform (GDP). It describes how Atos uses FPA to estimate project size, calculate standard effort, and convert effort into cost. FPA is integrated into GDP's processes and phases to enable estimation of main build effort and full lifecycle effort. Historical FPA data collected within GDP is used to determine productivity ratios for estimation.
The document discusses the development of an Energy Wasting Rate metric for measuring software energy efficiency. It proposes a top-down approach to define the metric involving identifying needs, requirements, use cases and a measurement process. This would involve instrumenting code to collect fine-grained energy consumption measurements at the method and class level under different conditions. Statistical analysis of the data could then identify inefficient practices and guide code refactoring to improve energy efficiency. An example case study compares energy usage measurements for implementations of a Fibonacci sequence using ArrayLists versus LinkedLists.
Do we measure functional size or do we count thomas fehlmannIWSM Mensura
This document contains the slides from a presentation given by Dr. Thomas Fehlmann on October 7, 2015 in Kraków, Poland. The presentation discusses using transfer functions and the solution profile to combine multiple functional size measurement methods into a single measurement in accordance with international standards for measurement. This allows defining a functional size unit specific to the transfer function and measurement goals. The solution profile shows the contribution of each size count to measurement precision and goals.
Designing an unobtrusive analytics framework for monitoring java applications...IWSM Mensura
This document discusses designing an unobtrusive analytics framework for monitoring Java applications. It proposes using aspect-oriented programming with AspectJ to monitor usage without altering the target application's code. Event data would be collected via Fluentd and stored in ElasticSearch for analysis with Kibana. This allows usage data to be gathered and compared across versions while avoiding complications from changes to the target application.
Combining qualitative and quantitative software process evaluation sylvie t...IWSM Mensura
The document discusses combining qualitative and quantitative software process evaluation approaches. It proposes an approach that measures software functional size and process efficiency during qualitative interviews and documentation reviews. A field trial of the approach was conducted at a financial trading organization with 100 staff developing trading software. Both qualitative and quantitative data were collected from 6 selected projects ranging from small to large. The results provided insights into the software process and identified requirements defects and variances in process efficiency across projects.
Automatic measurements of use cases with cosmic thomas fehlmannIWSM Mensura
This document contains information about an Excel-based tool called CosmicCount.xltm that allows automatically counting COSMIC function points of use case diagrams. It describes the tool's features such as automatically detecting actors, business classes, data groups and data movements from use case diagrams drawn or imported into the tool. The tool outputs the total COSMIC function point count. Information is also provided on how the tool is licensed under the GNU Free Documentation License and how it represents definitions, application boundaries, functional user requirements and objects of interest within use case diagrams.
Automated functional size measurement for three tier object relational mappin...IWSM Mensura
This document summarizes a presentation on automated functional size measurement for three-tier object relational mapping architectures. It discusses three-tier ORM architectures and a proposed COSMIC measurement mapping for them. It then describes an automated measurement tool developed to implement this mapping for applications built with ASP.NET, C#, and NHibernate. The tool was tested on an open-source case study, and results showed high accuracy for data movements but lower accuracy for entries and exits due to variability in implementation. The presentation concludes that the approach is currently limited but shows potential for improving measurement efficiency with some expansion.
Applying manufacturing performance figures to measure software development ex...IWSM Mensura
This document proposes applying manufacturing performance figures to measure software development excellence. It discusses challenges in monitoring software development in manufacturing companies. The authors believe manufacturing KPIs can be applied to software since managers understand these KPIs. The document outlines related work transferring methods from manufacturing to software. It then proposes specific manufacturing KPIs that can be mapped to software metrics to measure quantity and quality. An industrial partner validated the approach technically by measuring prototype data and gained management support through interviews. While limited, the validation was positive. More work is needed to generalize the approach.
Analytic hierarchy process for pif thomas fehlmannIWSM Mensura
This document discusses using the Analytic Hierarchy Process (AHP) to measure performance impact factors (PIF) and develop a transfer function to estimate costs for new projects based on PIF profiles. It provides an example of using AHP to determine the key PIF for a sample technology project ("Project X") and develop a PIF-based estimation model calibrated using data from 22 past projects. The model achieved good prediction accuracy, demonstrating how measuring PIF profiles with AHP can help benchmark and estimate new projects.
An architecture for effort estimation of solutions donatien koulla moullaIWSM Mensura
This document proposes an architecture for estimating the effort required for software projects based on open source software. It acknowledges that existing effort estimation models do not account for the differences in open source projects, including volunteer development teams and lack of formal management.
The proposed architecture includes estimating the effort to integrate open source components, the effort related to the number of code changes, and the effort related to code complexity. It also accounts for functional and non-functional requirements, as well as characteristics specific to open source software development like the voluntary nature of contributions. The total effort is estimated as the sum of efforts across each project activity.
A unified model for custom software price determination in contracts robert...IWSM Mensura
This document proposes a unified model for determining custom software prices in contracts. It discusses factors that affect software development effort and costs such as functional size, non-functional requirements, productivity adjustment factors, reuse, and technical constraints. The model represents price as a function of an adjusted unitary price based on functional size plus additional non-functional dependent prices. This provides a framework to systematically and quantitatively account for various factors in a transparent manner for both customers and suppliers.
A process to improve the accuracy of mk ii fp to cosmic charles symonsIWSM Mensura
This document presents a process to improve the accuracy of converting sizes measured using the MkII Functional Point (FP) method to sizes using the COSMIC method. Statistical analysis of 22 pairs of MkII and COSMIC size measurements showed good correlation but some outliers. A calculation method is proposed using "functional profiling" to group similar systems and determine conversion ratios based on each system's input, process, and output components. Applying this method improved the accuracy of predicted COSMIC sizes compared to a simple statistical conversion formula. The study provides new insights into the design assumptions of the COSMIC method.
Automatic measurements of use cases with cosmic thomas fehlmannIWSM Mensura
This document contains information about an Excel-based tool called CosmicCount.xltm that allows automatically counting COSMIC function points of use case diagrams. It describes the tool's features such as automatically detecting actors, business classes, data groups and data movements from use case diagrams drawn or imported into the tool. The document provides examples of how the tool counts function points and how the results are displayed. It also describes various worksheets in the Excel file that define elements like the application boundary, functional user requirements, objects of interest involved in use case diagrams.
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
What is Master Data Management by PiLog Groupaymanquadri279
PiLog Group's Master Data Record Manager (MDRM) is a sophisticated enterprise solution designed to ensure data accuracy, consistency, and governance across various business functions. MDRM integrates advanced data management technologies to cleanse, classify, and standardize master data, thereby enhancing data quality and operational efficiency.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Artificia Intellicence and XPath Extension FunctionsOctavian Nadolu
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
E-Invoicing Implementation: A Step-by-Step Guide for Saudi Arabian CompaniesQuickdice ERP
Explore the seamless transition to e-invoicing with this comprehensive guide tailored for Saudi Arabian businesses. Navigate the process effortlessly with step-by-step instructions designed to streamline implementation and enhance efficiency.
Transform Your Communication with Cloud-Based IVR SolutionsTheSMSPoint
Discover the power of Cloud-Based IVR Solutions to streamline communication processes. Embrace scalability and cost-efficiency while enhancing customer experiences with features like automated call routing and voice recognition. Accessible from anywhere, these solutions integrate seamlessly with existing systems, providing real-time analytics for continuous improvement. Revolutionize your communication strategy today with Cloud-Based IVR Solutions. Learn more at: https://thesmspoint.com/channel/cloud-telephony
WhatsApp offers simple, reliable, and private messaging and calling services for free worldwide. With end-to-end encryption, your personal messages and calls are secure, ensuring only you and the recipient can access them. Enjoy voice and video calls to stay connected with loved ones or colleagues. Express yourself using stickers, GIFs, or by sharing moments on Status. WhatsApp Business enables global customer outreach, facilitating sales growth and relationship building through showcasing products and services. Stay connected effortlessly with group chats for planning outings with friends or staying updated on family conversations.
Do you want Software for your Business? Visit Deuglo
Deuglo has top Software Developers in India. They are experts in software development and help design and create custom Software solutions.
Deuglo follows seven steps methods for delivering their services to their customers. They called it the Software development life cycle process (SDLC).
Requirement — Collecting the Requirements is the first Phase in the SSLC process.
Feasibility Study — after completing the requirement process they move to the design phase.
Design — in this phase, they start designing the software.
Coding — when designing is completed, the developers start coding for the software.
Testing — in this phase when the coding of the software is done the testing team will start testing.
Installation — after completion of testing, the application opens to the live server and launches!
Maintenance — after completing the software development, customers start using the software.
Hand Rolled Applicative User ValidationCode KataPhilip Schwarz
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdfUndress Baby
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
Revolutionizing Visual Effects Mastering AI Face Swaps.pdf
Accounting for non functional and project requirements - cosmic and ifpug development - talmon ben-cnaan - charles symons
1. Accoun&ng for Non-‐Func&onal and Project
requirements
in so9ware project performance measurement, benchmarking and es&ma&ng:
COSMIC and IFPUG developments
IWSM/Mensura
Conference,
Krakow,
October
2015
Talmon
Ben-‐Cnaan
(IFPUG),
Charles
Symons
(COSMIC)
2. IWSM
MENSURA
Krakow,
October
2015
Agenda
• IntroducJon:
Why
the
need
for
standards
for
Non-‐
FuncJonal
Requirements
(NFR)
and
for
Project
Requirements
and
Constraints
(PRC)?
• The
joint
COSMIC/IFPUG
development
of
a
Glossary
of
NFR
and
PRC
terms
• The
COSMIC
Guideline
on
how
to
consider
NFR
and
PRC
• The
IFPUG
SoTware
Non-‐FuncJonal
Assessment
Process
(SNAP)
to
measure
NFR
• Conclusions
and
next
steps
• QuesJons
and
debate
3. IWSM
MENSURA
Krakow,
October
2015
The ac&vi&es of so9ware project performance
measurement, benchmarking and es&ma&ng
need consistent data and terminology
Measuring
project
performance
Project
estimating
Benchmarking
Project
data &
benchmark
repository
Recording
&
measuring
software
system
project
requirements
4. IWSM
MENSURA
Krakow,
October
2015
Func&onal size measurements are used
consistently across all ac&vi&es
• There
are
three
types
of
requirements
for
a
soTware
system
project
• FuncJonal
User
Requirements
(FUR)
• Non-‐funcJonal
Requirements
(NFR)
• Project
Requirements
and
Constraints
(PRC)
• FuncJonal
size
measurement
methods,
e.g.
the
COSMIC
or
IFPUG
methods,
are
used
consistently
to
measure
the
size
of
FUR
across
all
acJviJes
But
what
about
NFR
and
PRC?
5. IWSM
MENSURA
Krakow,
October
2015
There is no good exis&ng defini&on of
Non-‐Func&onal Requirements (NFR)
Example:
ISO
24756
definiJon
1):
“A
so%ware
requirement
that
describes
not
what
the
so%ware
will
do
but
how
the
so%ware
will
do
it.
Example:
so%ware
performance
requirements,
so%ware
external
interface
requirements,
so%ware
design
constraints,
and
so%ware
quality
a>ributes.”
Comment:
only
‘design
constraints’
define
‘how
the
soTware
will
do
it’
6. IWSM
MENSURA
Krakow,
October
2015
Next, each ac&vity has defined its own
data and terminology for NFR and PRC 2)
Requirements Recording
(50)
IEEE 804, ISO 9126
Wikipedia
Requirements Sizing
(36)
VAF, TCA, SNAP
Benchmarking
(48)
ISBSG, SEI
Project Estimating
(39)
COCOMO II
One common NFR
(= “Interfaces”)
7. IWSM
MENSURA
Krakow,
October
2015
Past surveys have found varying
numbers of NFR terms
• ‘at
least’
161
terms
(Chung
et
al
3))
• 122
terms
in
a
structured
hierarchy
(Saito
et
al
4))
• 108
terms
(Symons
2))
• ISO/IEC
SQuaRE
5)
standard
lists
32
Quality
terms
A
complete,
standard
list
of
NFR
and
PRC
terms
may
be
impossible
8. IWSM
MENSURA
Krakow,
October
2015
Past aSempts to measure a collec&ve
size of NFR are now discredited
Albrecht’s
10
components
of
the
‘Value
Adjustment
Factor’
6)
14
components
(IFPUG)
7)
19+
components
(MkII
FPA)
8)
…..
but
they
did
have
value
when
they
were
first
invented.
9. IWSM
MENSURA
Krakow,
October
2015
Conclusions
• There
is
no
common
understanding
in
the
soTware
industry
of
what
is
meant
by
NFR
• ExisJng
standards
for
NFR
and
PRC
are
not
coherent
• These
issues
handicap
acceptance
of
methods
for:
• quanJfying
requirements,
• developing
project
performance
benchmarks,
• project
esJmaJng.
These
were
the
drivers
for
COSMIC
and
IFPUG
to
develop
the
joint
Glossary
of
NFR
and
PRC
terms
10. IWSM
MENSURA
Krakow,
October
2015
Agenda
• IntroducJon:
Why
the
need
for
standards
for
Non-‐
funcJonal
Requirements
(NFR)
and
for
Project
Requirements
and
Constraints
(PRC)?
• The
joint
COSMIC/IFPUG
development
of
a
Glossary
of
NFR
and
PRC
terms
• The
COSMIC
Guideline
on
how
to
consider
NFR
and
PRC
• The
IFPUG
SoTware
Non-‐FuncJonal
Assessment
Process
(SNAP)
to
measure
NFR
• Conclusions
and
next
steps
• QuesJons
and
debate
11. IWSM
MENSURA
Krakow,
October
2015
Words
What
do
we
mean
when
saying
• A
date
is
a
date.
• Right!
• It
is
not
my
type
12. IWSM
MENSURA
Krakow,
October
2015
We have agreed many aspects of
NFR and PRC over the past year
• Scope
of
the
Glossary
9)
• Clarity
on:
• ‘Requirements’
versus
‘constraints’
• The
‘things’
that
NFR
and
PRC
apply
• DisJnguishing
and
defining
NFR
and
PRC
• Structuring
NFR
(aligned
with
SQuaRE)
and
PRC
to
classes
à
groups
à
terms
• The
terms:
• 67
NFR
terms,
mainly
from
ISO
and
ISBSG
(27
COSMIC/IFPUG)
• 19
PRC
terms,
mainly
from
PMI
and
ISBSG
13. IWSM
MENSURA
Krakow,
October
2015
We have clarified the terms
Requirements and Constraints
Thesaurus:
Requirement:
“a
thing
demanded
or
obligatory”
Constraint:
“limitaJon
or
restricJon”
The
difference
is
not
always
clear:
• A
requirement
that
the
so%ware
shall
use
C#
is
also
a
constraint
• ‘Latency’
can
be
a
requirement
for
some
real-‐Fme
systems
but
a
constraint
for
the
Mars
Rover
system
• Staffing
skills
can
be
a
project
requirement
or
a
constraint
Constraints
Requirements
We
use
requirements
for
convenience.
We
use
constraints
only
when
it
is
helpful
to
disAnguish
constraints
from
requirements.
14. IWSM
MENSURA
Krakow,
October
2015
The scope of requirements and
constraints
Requirements
and
constraints
can
apply
to
• The
soCware;
• The
data
maintained
or
used
by
the
soTware;
• The
technology
to
be
used,
e.g.
the
planorms;
• Other
deliverables,
e.g.
documentaJon
or
training;
• The
combined
hardware/soCware
system,
e.g.
a
response
Jme;
and
some
constraints
come
from
the
environment
15. IWSM
MENSURA
Krakow,
October
2015
Data
Technology
Hardware/Software
System
Project
Environment
Other
Deliverables
Software
Project, System, Product
A
project:
a
temporary
endeavor
to
achieve
defined
objecJves
of
delivering
a
product
by
defined
dates.
Following
a
Project,
there
is
a
Product
in
place
(A
new
Product
or
a
Product
that
was
changed
by
the
project).
A
product
is
a
hardware/
soTware
system
or
an
item
of
soTware
such
as
a
soTware
package
Product
A
Product
C
Product
B
16. IWSM
MENSURA
Krakow,
October
2015
Requirements
for
a
SoTware
System
Project
Project
Requirements
and
Constraints
(PRC)
System
and
SoTware
Non-‐FuncJonal
Requirements
(NFR)
SoTware
FuncJonal
User
Requirements
(FUR)
System
Environment
Requirements
Technical
Requirements
Quality
Requirements
(SoTware
System)
Quality
Requirements
(Data)
Classifica&on of Requirements
17. IWSM
MENSURA
Krakow,
October
2015
System
and
SoTware
Non-‐FuncJonal
Requirements
(NFR)
System
Environment
Requirements
Technical
Requirements
Quality
Requirements
(SoTware
System)
Quality
Requirements
(Data)
Classifica&on of NFR
1 Quality
of
the
data
maintained
by
the
soTware
2 System
performance
3 CompaJbility
4 Ease
of
use
5 System
reliability
6 Control
of
access
7 Maintainability
8 Ease
of
deployment
9 System
or
soTware
architecture
or
design
1 Context
2 ApplicaJon
Domain
3 ImplementaJons
4 User
Base
1 OperaJonal
Planorm
2 Database
3 OperaJonal
Planorm
constraints
4 Development
requirements
Class
Group
Type
18. IWSM
MENSURA
Krakow,
October
2015
COSMIC and IFPUG defini&ons
FuncAonal
User
Requirements
(FUR)
-‐
ISO/IEC
14143-‐1
DefiniAon
Adopted
by
COSMIC
and
IFPUG
A
sub-‐set
of
the
user
requirements.
Requirements
that
describe
what
the
soCware
shall
do,
in
terms
of
tasks
and
services.
NOTE:
FuncJonal
User
Requirements
relate
to
but
are
not
limited
to:
• data
transfer
(for
example
Input
customer
data;
Send
control
signal)
• data
transformaJon
(for
example
Calculate
bank
interest;
Derive
average
temperature)
• data
storage
(for
example
Store
customer
order;
Record
ambient
temperature
over
Jme)
• data
retrieval
(for
example
List
current
employees;
Retrieve
latest
aircraT
posiJon)
19. IWSM
MENSURA
Krakow,
October
2015
COSMIC and IFPUG defini&ons
Non-functional requirement – COSMIC and IFPUG
Definition
Any
requirement
for
a
soCware
system
or
for
a
soCware
product,
including
how
it
should
be
developed
and
maintained,
and
how
it
should
perform
in
operaAon,
except
any
funcAonal
user
requirement
for
the
soCware.
Non-‐funcJonal
requirements
concern:
• the
soTware
system
or
soTware
product
quality;
• the
environment
in
which
the
soTware
system
or
soTware
product
must
be
implemented
and
which
it
must
serve;
• the
processes
and
technology
to
be
used
to
develop
and
maintain
the
soTware
system
or
soTware
product,
and
the
technology
to
be
used
for
their
execuJon.
20. IWSM
MENSURA
Krakow,
October
2015
COSMIC and IFPUG defini&ons
Project Requirements and Constraints - Definition
Requirements
that
define
how
a
soCware
system
project
should
be
managed
and
resourced,
or
constraints
that
affect
its
performance.
Requirements
may
include:
• The
targets
the
project
should
achieve
(e.g.
budget,
delivery
date,
product
quality);
• The
project
management
processes
that
should
be
used;
• How
the
project
should
be
governed
and
resourced.
Constraints
may
include:
• LimitaJons
on
the
project
resources;
• Dependencies
on
other
projects
outside
the
control
of
the
project
concerned.
21. IWSM
MENSURA
Krakow,
October
2015
67
Terms
Examples
COSMIC
/
IFPUG
DefiniJon
NFR
sub-‐type
(Quality,
System
Environment
Requirements,
Technical
Requirements)
Quality:
9
groups
Environment:
4
groups
Technical:
4
groups
ISO
DefiniJon
22. IWSM
MENSURA
Krakow,
October
2015
COSMIC and IFPUG strongly
recommend their joint Glossary
• Developed
through
>
20
iteraJons
over
a
year
• Reviewed
by
many
experts
(academic
and
pracJJoners)
from
around
the
world
• Available
for
free
download
from:
• www.cosmic-‐sizing.org
• www.ifpug.org
• We
welcome
feedback
and
comments
23. IWSM
MENSURA
Krakow,
October
2015
Agenda
• IntroducJon:
Why
the
need
for
standards
for
Non-‐
funcJonal
Requirements
(NFR)
and
for
Project
Requirements
and
Constraints
(PRC)?
• The
joint
COSMIC/IFPUG
development
of
a
Glossary
of
NFR
and
PRC
terms
• The
COSMIC
Guideline
on
how
to
consider
NFR
and
PRC
• The
IFPUG
SoTware
Non-‐FuncJonal
Assessment
Process
(SNAP)
to
measure
NFR
• Conclusions
and
next
steps
• QuesJons
and
debate
24. IWSM
MENSURA
Krakow,
October
2015
The COSMIC Guideline builds on
the joint COSMIC/IFPUG Glossary
Contents
• Terminology,
NFR/PRC
definiJons
• ClassificaJon
of
NFR/PRC
terms
• Glossary
of
NFR/PRC
terms
• EvoluJon
of
NFR
in
a
project
• How
to
deal
with
NFR/PRC
in
performance
measurement,
benchmarking
&
esJmaJng
• Measurement
of
NFR
(interim)
Glossary9)
ü
ü
ü
Guideline10)
ü
ü
ü
ü
ü
ü
25. IWSM
MENSURA
Krakow,
October
2015
Requirements that first appear as NFR
may evolve, wholly or partly, into FUR
Outline
Funct-
-ional
Requts.
Outline
NFR
Project
Requts. &
Constraints
Require-
ments
Analysis
Definition
& Design
Build, Test
&
Implement
A
r
c
h
i
t
e
c
t
u
r
e
Approx.
Funct-
-ional
Requts.
Detailed
NFR
Imple-
mented
software
system
or
software
product
Detailed
FUR
……
as
demonstrated
by
Al
Sarayreh,
Abran
and
others,
e.g.
[11]
26. IWSM
MENSURA
Krakow,
October
2015
The ‘addi&onal’ FUR can be measured by
approximate or standard COSMIC sizing
Outline
Funct-
-ional
Requts.
Outline
NFR
Project
Requts. &
Constraints
Require-
ments
Analysis
Definition
& Design
Build, Test
&
Implement
A
r
c
h
i
t
e
c
t
u
r
e
Imple-
mented
software
system
or
software
product
Approx.
Funct-
-ional
Requts.
Detailed
NFR
Detailed
FUR
Size by analogy or
expert judgement
Approx. COSMIC
size measurement
Precise COSMIC
size measurement
27. IWSM
MENSURA
Krakow,
October
2015
The Guideline gives examples for all
Quality NFR how they may evolve as a
project progresses
FuncAonality
that
may
evolve
from
the
NFR,
that
can
be
measured
‘Middleware’
funcJonality
to
enable
portability
across
mulJple
DBMS
or
OS
or
hardware
Graphical
User
Interface
funcJons;
and
FuncJonality
to
assist
users,
e.g.
‘Help’
funcJons
FuncJonality
to
import
external
data
in
real-‐Jme
so
that
it
is
available
for
immediate
use
IniAal
NFR
term
Portability
Usability
Response
Jme
‘Residual’
or
‘Real’
NFR
statement
The
specific
environments
across
which
the
soTware
must
be
portable
The
specific
usability
requirements
(e.g.
‘must
be
usable
by
public
with
no
training’)
-‐
The
response
Jme
target;
-‐
Specific
hardware;
-‐
Low-‐level
programming
language.
Examples:
28. IWSM
MENSURA
Krakow,
October
2015
COSMIC has no plans to develop a
collec&ve size measure for NFR
Inherent
difficulJes:
1. How
to
form
a
collecJve
size
measure
that
will
add
pracJcal
value,
long-‐term?
2. The
large
number
and
variety
of
NFR
3. How
to
collect
effort
data
related
to
NFR
when
NFR
evolve
into
FUR?
29. IWSM
MENSURA
Krakow,
October
2015
1. Collec&ve size measures are
common and o9en valuable
Examples
of
valuable
collecJve
size
measures.
(All
are
mathemaJcally
invalid,
but
they
work.)
• The
IFPUG
Value
Adjustment
Factor
(when
first
introduced)
• Indices
that
affect
stock
market
senJment,
e.g.
the
PMI
• Measures
of
‘biological
age’
• Total
Factor
ProducJvity
CondiJons
for
a
usable
collecJve
size
measure:
• A
finite,
stable,
well-‐defined
set
of
components
• If
possible,
a
common
unit
of
measure
for
all
components
• A
simple
formula
for
the
index
(avoid
complex
maths)
30. IWSM
MENSURA
Krakow,
October
2015
2. There is a large number and variety of
NFR. Many overlap in meaning
How
many
separate
NFR
should
we
include
in
a
collecJve
size
measure?
(10,
14,
19+,
67,
108,
122,
161+
…?)
Maintain-‐
ability
Test-‐
ability
Flex-‐
ibility
Adapt-‐
ability
Extend-‐
ability
Evolv-‐
ability
Modula-‐
rity
Modifia-‐
ability
Reus-‐
ability
Port-‐
ability
31. IWSM
MENSURA
Krakow,
October
2015
3. How to capture the effort
associated with implemen&ng NFR?
….
given
that
NFR
evolve
as
a
project
progresses
into
FUR
…..
?
....
&
noJng
that
effort
to
implement
NFR
varies
with:
• soTware
domain,
• type
of
NFR,
• the
parJcular
‘soluJon’
for
the
NFR,
• technology,
re-‐use,
etc.
32. IWSM
MENSURA
Krakow,
October
2015
Instead, we propose basic sets of NFR/PRC to
record and measure for performance
measurement, benchmarking, es&ma&ng
NFR and PRC
Class
Terms
Quality NFR Response time, Transaction rate
Security, Privacy
Maintainability, Reusability
Interfaces, Operational processing mode
System
Environment NFR
Application type, sub-type
Implementations (numbers of)
Maximum number of concurrent users
Technical NFR Operational platform type
Programming language
DBMS software
Project
Requirements and
Constraints (PRC)
Many, but not all of the 19 project requirements and constraints are worth
recording. Example: if staff experience levels, processes and methods
and tools are the same for all projects, then they need not be recorded
for internal purposes.
33. IWSM
MENSURA
Krakow,
October
2015
…. and advise how to deal with NFR in
performance measurement,
benchmarking and es&ma&ng
• EsJmate
and
measure
total
funcJonal
size,
including
funcJonality
that
evolves
from
NFR
• Within
a
defined
‘environment’,
i.e.
• soTware
domain
(business,
real-‐Jme)
• soTware
architecture,
technology
• project
type
(new,
enhancement,
etc)
….
collect
and
record
data
on
‘real’
NFR
and
PRC
so
that
you
can
make
like-‐for-‐like
comparisons
(This
is
normal
pracJce
for
benchmarking
acJviJes,
plus
a
few
addiJonal
parameters.)
34. IWSM
MENSURA
Krakow,
October
2015
Guideline Conclusions
The
COSMIC
‘Guideline
for
dealing
with
Non-‐
FuncFonal
Requirements
in
project
performance
measurement
&
esFmaFng’
• builds
on
the
joint
COSMIC/IFPUG
Glossary
• provides
pracJcal
advice
on
how
to
deal
with
manageable
sub-‐sets
of
NFR
and
PRC
and
will
be
available
in
October
for
free
download
from
www.cosmic-‐sizing.org
35. IWSM
MENSURA
Krakow,
October
2015
Agenda
• IntroducJon:
Why
the
need
for
standards
for
Non-‐
funcJonal
Requirements
(NFR)
and
for
Project
Requirements
and
Constraints
(PRC)?
• The
joint
COSMIC/IFPUG
development
of
a
Glossary
of
NFR
and
PRC
terms
• The
COSMIC
Guideline
on
how
to
consider
NFR
and
PRC
• The
IFPUG
SoTware
Non-‐FuncJonal
Assessment
Process
(SNAP)
to
measure
NFR
• Conclusions
and
next
steps
• QuesJons
and
debate
36. IWSM
MENSURA
Krakow,
October
2015
FPA and SNAP covers functional and
non-functional requirements
PRC
–
do
not
impact
soTware
size
NFR
–
measured
with
SNAP
Points
FUR
–
measured
with
FP
Guidelines
to
prevent
doubled
counJng
37. IWSM
MENSURA
Krakow,
October
2015
PRC affects produc&vity
and not size
• Effort
depends
on
PRC
classes.
No
standard
/
industry
mathemaJcal
formula
• Examples:
Project
type;
(same
size
different
effort)
• Effort
may
be
formulated
for
some
PRC
(“producJvity
drivers”)
• Examples:
Skill
level;
LocaJon;
Schedule
compression
(“crashing”)
(same
size
different
effort)
• Effort
(or
deviaJon
from
esJmaJon)
can
be
explained
by
some
PRC
• Examples:
Risk
that
was
materialized;
scope
creep
38. IWSM
MENSURA
Krakow,
October
2015
SNAP
• SNAP
idenJfies
fourteen
non-‐funcJonal
characterisJcs
(“sub
categories”)
that
classify
the
way
NFR
are
met.
• In
each
sub-‐category,
the
size
is
assessed
within
a
counJng
unit
(SCU).
The
SCU
is
part
of
the
definiJon
of
the
sub-‐category.
• Non
funcJonal
size
is
determined
by
a
set
of
parameters
/
complexity
levels.
The
parameters
that
define
each
sub-‐category
answer
the
quesJon
“what
factors
affect
the
effort
to
deliver
a
NFR”
• Example:
The
effort
to
add
input
methods
(e.g.
barcode
reader,
fax
server,
reading
CSV
file)
with
same
funcJonality
depends
on
number
of
added
input
methods
39. IWSM
MENSURA
Krakow,
October
2015
SNAP
• Parameters
can
be
used
as
a
table
of
values
(e.g.
“High,
medium,
low”,
“<10,
10
to
15,
16+”)
or
as
a
mulJplier
(“SP
=
3*#
addiJonal
input
methods),
or
a
combinaJon
of
the
above
• Once
the
parameters
are
assessed,
the
size
of
the
SCU
is
calculated.
SP
size
is
the
sum
of
the
SPs
of
the
SCUs
40. IWSM
MENSURA
Krakow,
October
2015
SNAP sub categories are independent of
the way NFR are classified / defined
Accuracy
Performance
Ease of use / customer
satisfaction
Response Time
Requirements
CharacterisJcs
41. IWSM
MENSURA
Krakow,
October
2015
SNAP sub-‐categories are independent
of the way NFR are classified
Accuracy
Ease of use / customer
satisfaction
Response Time
ISO9126
ISO25010
COSMIC/IFPUGGlossary
Requirements
CharacterisJcs
Time Behavior
Performance
42. IWSM
MENSURA
Krakow,
October
2015
Data Func&ons and Transac&onal
Func&ons are not sufficient to size NFR
The effort to deliver NFR is also affected by
• Database ac&vi&es
• Dealing with UI proper&es
• Extensive Logical / Mathema&cal opera&ons
• Batch processes that do not cross the boundaries
and are not exposed to users
• Mul&ple inputs/output
• …..
43. IWSM
MENSURA
Krakow,
October
2015
Example 1 – The requirements
NFR:
Improve
CRM
system
performance
for
“Retrieve
and
View
Customer
Details“-‐
by
loading
the
‘customer
details’
screen
in
3
seconds
or
less.
(Currently
it
takes
0.5
sec
to
6
sec.)
Problem
analysis:
The
system
is
slow
when
the
user
(call
center
representaJve)
opens
a
big
customer
with
many
products
and
many
interacJons.
It
also
happens
when
users’
virtual
memory
is
low
44. IWSM
MENSURA
Krakow,
October
2015
Example 1 -‐ the design
1. Increase
the
virtual
memory
of
‘Windows’
to
maximum;
2. Create
a
database
view,
which
includes
data
from
three
tables
(Assigned
Products,
TransacJons,
and
Payments)
(Assuming
30
different
DETs
are
fetched).
3. Add
Logic
to
idenJfy
which
customers
will
be
loaded
to
the
new
view
4. Add
a
field
to
‘Customers’
table
to
indicate
whether
recent
informaJon
moved
to
the
new
view
and
add
logic
to
idenJfy
which
transacJons
will
be
copied
(not
seen
by
the
users,
hence
non-‐
funcJonal
change).
5. A
batch
process
runs
in
the
background
every
2
hours,
refreshing
this
view
with
large
and
most
acJve
users
45. IWSM
MENSURA
Krakow,
October
2015
Example 1 – SNAP count
• Increasing
virtual
memory:
InstallaJon
of
a
larger
size
virtual
memory
is
a
hardware
configuraJon
and
not
a
soTware
change.
It
is
not
counted
using
soTware
sizing
methods.
• CreaJng
a
database
view
(CUST_DETAIL_SUMMARY_
TEMP)
and
adding
an
indicator
(field)
to
‘Customer’
table:
• Count
SP
using
3.2
Database
changes;
SNAP
count
is
based
on
two
database
changes,
20-‐50
DETs,
2-‐5
RETs
• Adding
a
batch
process:
(this
batch
job
does
not
cross
the
boundary,
hence
it
is
not
counted
using
FP)
• Count
SP
using
3.3
Batch
Processes.
SNAP
count
is
based
on
30
DETs
and
3
FTRs
• Adding
logic
to
meet
the
NFR:
Count
SP
using
1.2
Logical
and
MathemaJcal
OperaJons.
SNAP
count
is
based
on
3
FTRs,
type
=
‘Logical’
and
10
DETs
used
for
the
added
logic
46. IWSM
MENSURA
Krakow,
October
2015
IFPUG Coun&ng Process
Gather
available
documentaJon
Determine
counJng
purpose,
scope,
boundaries
and
parJJons
IdenJfy
requirements
as
FUR,
NFR.
Separate
mixed
requirements
to
FUR
and
NFR
Measure
Data
FuncJons
Measure
TransacJonal
FuncJons
Associate
NFR
to
sub-‐
categories
Calculate
funcJonal
size
Determine
SNAP
size
of
each
sub
category
Calculate
SNAP
size
Document
and
report
FuncJonal
Non-‐FuncJonal
47. IWSM
MENSURA
Krakow,
October
2015
Es&ma&on and benchmark
Es&ma&on
𝑬𝒇𝒇𝒐𝒓𝒕=
[ 𝑷𝑫𝑹↓ 𝟏 (𝑷𝒓𝒐𝒋𝒆𝒄 𝒕↑′ 𝒔 𝑪𝒉𝒂𝒓𝒂𝒄𝒕𝒆𝒓𝒊𝒔𝒕𝒊𝒄𝒔)× 𝑭𝒖𝒏𝒄𝒕𝒊𝒐𝒏𝒂𝒍
𝑺𝒊𝒛𝒆]+[ 𝑷 𝑫𝑹↓ 𝟐 (𝑷𝒓𝒐𝒋𝒆𝒄 𝒕↑′ 𝒔 𝑪𝒉𝒂𝒓𝒂𝒄𝒕𝒆𝒓𝒊𝒔𝒕𝒊𝒄𝒔)× 𝑵𝒐𝒏
−𝒇𝒖𝒏𝒄𝒕𝒊𝒐𝒏𝒂𝒍 𝑺𝒊𝒛𝒆]
PDR
–
ProducJvity
Delivery
Rate
Note:
Feedback
from
users
show
that
PDR2
diverges
in
3
of
the
14
sub-‐categories.
NSFFC
will
reformulate
them
based
on
collected
data
Benchmarking
• Based
on
linear
regression
to
extract
PDR1
and
PDR2:
• Two
different
baselines,
two
business
values
to
customers
48. IWSM
MENSURA
Krakow,
October
2015
Agenda
• IntroducJon:
Why
the
need
for
standards
for
Non-‐
funcJonal
Requirements
(NFR)
and
for
Project
Requirements
and
Constraints
(PRC)?
• The
joint
COSMIC/IFPUG
development
of
a
Glossary
of
NFR
and
PRC
terms
• The
COSMIC
Guideline
on
how
to
consider
NFR
and
PRC
• The
IFPUG
SoTware
Non-‐FuncJonal
Assessment
Process
(SNAP)
to
measure
NFR
• Conclusions
and
next
steps
• QuesJons
and
debate
49. IWSM
MENSURA
Krakow,
October
2015
COSMIC and IFPUG have come
closer over the past year
Close
exchange
of
ideas
has
led
to:
• Agreeing
to
disJnguish
NFR
and
PRC
• AdopJng
PMI
definiJons
for
PRC
terms
• Many
refinements
to
the
classificaJon
structure
and
Glossary
contents
–
through
>
20
iteraAons
Further,
we
agree
that:
• NFR
increase
the
size
of
the
soTware,
and
should
be
measured
• Performance
measurement,
benchmarking
and
project
esJmaJng
must
consider
both
FUR
and
NFR
50. IWSM
MENSURA
Krakow,
October
2015
Conclusions
Whilst
COSMIC
&
IFPUG
sJll
have
different
views
on
how
to
measure
NFR,
we
have
collaborated
very
well
to
agree:
• DefiniJons
and
classificaJon
of
NFR
and
PRC
• The
Glossary
of
NFR
and
PRC
terms,
v1.0
We
strongly
recommend
these
to
the
soTware
engineering
community
51. IWSM
MENSURA
Krakow,
October
2015
Next steps
• Enhance
the
Glossary
to
take
into
account
‘Data
Quality’
requirements
• Enhance
the
Glossary
(and
define
measurements?)
to
take
into
account
‘Other
Deliverables’
such
as
training
and
documentaJon
This
is
a
quesJon
to
YOU:
Should
we?????
52. Thank
you
for
your
a^enAon
Talmon
Ben-‐Cnaan
(www.ifpug.org
);
talmonbc@amdocs.com
Charles
Symons
(www.cosmic-‐sizing.org
);
cr.symons@bJnternet.com
53. IWSM
MENSURA
Krakow,
October
2015
References
1. ISO/IEC/IEEE
24765:2010
‘Systems
and
soTware
engineering
–
vocabulary’.
2. Symons,
C.R.,
‘AccounJng
for
Non-‐FuncJonal
Requirements
in
ProducJvity
Measurement,
Benchmarking
and
EsJmaJng’,
UKSMA/COSMIC
InternaJonal
Conference
on
SoTware
Metrics
&
EsJmaJng,
London,
27/28
October
2011.
3. L.
Chung,
B.
Nixon,
E.
Yu,
and
J.
Mylopoulos,
"Non-‐funcJonal
Requirements
in
SoTware
Engineering,“
Kluwer
Academic
Publishing,
2000.
4. Saito,
Y.,
Monden
A.,
Matsumoto
K.,
‘EvaluaJon
of
non-‐funcJonal
requirements
in
a
request
for
proposal
(RFP)’,
Nara
InsJtute
of
Science
&
Technology,
Japan,
at
InternaJonal
Workshop
on
SoTware
Measurement
(IWSM),
Nara,
2012..
5. ISO/IEC
FCD
25010:
Systems
and
soTware
engineering,
–System
and
soTware
product
Quality
Requirements
and
EvaluaJon
(SQuaRE)
–System
and
soTware
quality
models
6. Albrecht,
A.
J.,
‘Measuring
applicaJon
development
producJvity’,
In
Proc.
of
the
IBM
ApplicaJons
Development
Symposium,
pp.
83-‐-‐92.
Monterey,
California
(1979)
7. IFPUG,
CounJng
PracJces
Manual,
Release
4.3.1
–
Appendix
C
8. Symons,
C.R.,
SoTware
sizing
&
esJmaJng:
Mk
II
FPA’,
John
Wiley
&
Sons,
1991,
ISBN
0
471
92985
9
9. ‘Glossary
of
terms
for
Non-‐FuncJonal
Requirements
and
Project
Requirements
used
in
soTware
project
performance
measurement,
benchmarking
and
esJmaJng’,
Version
1.0,
September
2015
10. ‘Guideline
on
Non-‐FuncJonal
&
Project
Requirements:
How
to
consider
non-‐funcJonal
and
project
requirements
in
soTware
project
performance
measurement,
benchmarking
and
esJmaJng’,
version
1.0,
October
2015
11. Khalid
T.
Al-‐Sarayreh,
Alain
Abran
and
Juan
J.
Cuadrado-‐Gallego,
‘A
Standards-‐based
model
of
system
maintainability
requirements’,
Journal
of
SoTware:
EvoluJon
and
Process,
2013,
Vol.
25,
no.
5,
pp.
459-‐505