Where do we stand in Requirements Engineering Improvement Today? First Result...Daniel Mendez
This document summarizes the results of a mapping study on requirements engineering (RE) improvement approaches. The study analyzed 58 publications to understand the current state of RE improvement research. The main findings were:
1) Publications focused on activity-based and normative improvement approaches that assess practices against best practice norms.
2) Most work supported the construction and validation phases of improvement.
3) Little is known about the benefits and limitations of different improvement principles and paradigms.
4) There are opportunities to explore problem-driven and artifact-based improvement approaches.
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.it/.
http://www.ivanomalavolta.com
This document provides an overview of empirical software engineering. It begins with an introduction to the need for empirical studies in software engineering to systematically evaluate human activities. The document then covers basic concepts like measurement, data collection, and analysis. It discusses empirical strategies like surveys, case studies, and controlled experiments. The document also outlines the process for conducting an empirical study and current tools. It concludes by examining the state of the art in empirical software engineering and opportunities to better integrate experimental results.
Where do we stand in Requirements Engineering Improvement Today? First Result...Daniel Mendez
This document summarizes the results of a mapping study on requirements engineering (RE) improvement approaches. The study analyzed 58 publications to understand the current state of RE improvement research. The main findings were:
1) Publications focused on activity-based and normative improvement approaches that assess practices against best practice norms.
2) Most work supported the construction and validation phases of improvement.
3) Little is known about the benefits and limitations of different improvement principles and paradigms.
4) There are opportunities to explore problem-driven and artifact-based improvement approaches.
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.it/.
http://www.ivanomalavolta.com
This document provides an overview of empirical software engineering. It begins with an introduction to the need for empirical studies in software engineering to systematically evaluate human activities. The document then covers basic concepts like measurement, data collection, and analysis. It discusses empirical strategies like surveys, case studies, and controlled experiments. The document also outlines the process for conducting an empirical study and current tools. It concludes by examining the state of the art in empirical software engineering and opportunities to better integrate experimental results.
Theory Building in RE - The NaPiRE InitiativeDaniel Mendez
Talk I gave on the "Naming the Pain in Requirements Engineering" initiative (www.re-survey.org) at the Seminar on Forty Years of Requirements Engineering – Looking Forward and Looking Back (RE@40) in Kappel am Albis, Switzerland
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
This document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes three individual assignments analyzing a work-related project using SDLC phases and a final group project applying the full SDLC methodology. Discussion questions address key elements of each SDLC phase like scope, requirements, design constraints, and challenges of system development.
Design Thinking for Requirements EngineeringDaniel Mendez
This document provides an overview of a tutorial on Design Thinking for Requirements Engineering (DT4RE). The tutorial aims to introduce basic principles and methods of Design Thinking and discuss how it can be integrated with Requirements Engineering. It outlines different approaches to integrating Design Thinking and Requirements Engineering based on the complexity of the project from pure Design Thinking to fully integrated approaches. The tutorial also discusses open research challenges around principles, artifacts, project influences, methods adoption, and operationalization of Design Thinking and Requirements Engineering processes.
This document outlines the coursework for BSA 376 which includes several individual assignments and a group assignment. The individual assignments involve analyzing a work-related project using systems analysis and the SDLC process. This includes gathering requirements, designing system architecture and processes, and discussing the development and implementation stages. The group assignment involves applying the full SDLC methodology to address a specific functional area need through a paper and presentation. Discussion questions are also provided for each week.
Collaborative Agile Research, por Claudia MeloThoughtworks
Pesquisa ágil colaborativa: princípios para uma pesquisa aplicada de impacto.
Mais do que nunca, a união de forças entre academia e indústria se faz necessária para que a sociedade possa criar as soluções de seu tempo. Como ex-aluna do IME, pesquisadora e profissional de mercado, vou falar sobre princípios de como fazer pesquisa aplicada de alta qualidade e impacto, de maneira ágil, contando histórias reais de sucesso (e algumas de fracasso).
The document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes three individual assignments analyzing a work-related project using different SDLC phases, from analysis to design to implementation. It also includes a final group project applying the full SDLC methodology to address a specific functional area need. Discussion questions cover key elements of different SDLC phases and methodologies.
In this presentation we introduce SAMOD, a.k.a. Simplified Agile Methodology for Ontology Development, a novel agile methodology for the development of ontologies by means of small steps of an iterative workflow that focuses on creating well-developed and documented models starting from exemplar domain descriptions.
Euro symposium Action Design Research practise 19092019Matti Rossi
Matti Rossi is a professor at Aalto University School of Business in Finland. He discusses action design research (ADR), which integrates design research and action research. ADR aims to solve organizational problems while also contributing to academic knowledge. It involves four stages: problem formulation, building/intervention/evaluation, reflection/learning, and formalization of learning. As an example, Rossi describes a case where ADR was used to develop strategies and tools to improve transparency in a software company's globally distributed R&D network.
This document contains information about assignments and discussion questions for a business systems development life cycle (SDLC) course. It includes assignments on analyzing a work-related project using systems analysis tools, describing the architecture and process design, and discussing the development and implementation stages. It also includes discussion questions about important elements in SDLC phases, different SDLC approaches, defining project scope, constraints on system design, and development and implementation approaches. A final group project involves applying the full SDLC methodology to address a functional area's needs.
Presentation of IEEE TSE Journal First paper at ICSE 2020
Abstract:
Developer satisfaction and work productivity are important
considerations for software companies. Enhanced developer satisfaction may improve the attraction, retention and health of employees, while higher productivity should reduce costs and increase customer satisfaction through faster software improvements. Many researchers and companies assume that perceived productivity and job satisfaction are related and may be used as proxies for one another, but these claims are a current topic of debate. There are also many social and technical
factors that may impact satisfaction and productivity, but which factors have the most impact is not clear, especially for specific development contexts. Through our research, we developed a theory articulating a bidirectional relationship between software developer job satisfaction and perceived productivity, and identified what additional social and technical
factors, challenges and work context variables influence this relationship. The constructs and relationships in our theory were derived in part from related literature in software engineering and knowledge work, and we validated and extended these concepts through a rigorously designed survey instrument. We instantiate our theory with a large software company, which suggests a number of propositions about the relative impact of various factors and challenges on developer satisfaction and perceived productivity. Our survey instrument and analysis approach
can be applied to other development settings, while our findings lead to concrete recommendations for practitioners and researchers.
Authors:
Margaret-Anne Storey, Tom Zimmermann, Chris Bird, Jacek Czerwonka, Brendan Murphy and Eirini Kalliamvakou
This document discusses criteria and techniques for prioritizing projects for sustainable economic development in the Sudurnes region of Iceland. It outlines several criteria for prioritization including accession, competitiveness, financial and economic, technical, social and political, and commercial and institutional factors. The document also describes approaches to prioritization such as selecting a prioritization team, identifying relevant criteria, selecting and weighting criteria, applying the criteria to projects to calculate scores and rankings. Project selection procedures and techniques like financial analysis, cost-benefit analysis, and multi-criteria analysis are also summarized.
This document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes 3 individual papers and 1 group paper analyzing different phases of an SDLC for a work-related project. It also includes discussion questions about important elements, approaches, scope, requirements, design constraints, security, and challenges of the SDLC process.
Mehmet Aydın, KHU - Nurullah Battal, Roche | Agile Turkey Summit 2013Agile Turkey
Enabling Organizational Change through Agile Methods
Agile approaches and methods have been promoted as a panacea for long-standing problems in IT projects. Such problems may be denoted as “one-size-fits-all issues”, “failing to embrace changes in the projects”, “lack of IT-Business Alignment”. Recently, practitioners have experienced that agile methods can be used as a means to facilitate change concerning IT mind-set and practice as well. This talk is concerned with the effects of agile method on organizational change. We explore underpinnings of an agile-enabled organizational change in terms of the way of thinking and actions. To articulate such underpinnings an exemplary case is used. Reflections on lessons-learned and practical insights are to be presented as well.
Evaluability Assessments and Choice of Evaluation MethodsDebbie_at_IDS
The document discusses evaluability assessments (EAs) and how they can inform the choice of evaluation methods. Key points:
- EAs examine a project's design, available information, and context to determine if and how an evaluation could be conducted. They help ensure evaluations are useful and feasible.
- Common EA steps include reviewing documentation, engaging stakeholders, and making recommendations about a project's logic, monitoring systems, and potential evaluation approaches.
- Choosing evaluation methods depends on the EA results as well as the evaluation's purpose, required credibility, complexity of the intervention, and available resources. Methods like experiments provide strong evidence of impact but are difficult to implement.
- EAs improve evaluation quality by engaging
Different testers have different understandings of the role and mission of software testing; of the approaches, methods, and techniques to use during testing.
Comparative Recommender System Evaluation: Benchmarking Recommendation Frame...Alan Said
Video available here http://www.youtube.com/watch?v=1jHxGCl8RXc
Recommender systems research is often based on comparisons of predictive accuracy: the better the evaluation scores, the better the recommender.
However, it is difficult to compare results from different recommender systems due to the many options in design and implementation of an evaluation strategy.
Additionally, algorithmic implementations can diverge from the standard formulation due to manual tuning and modifications that work better in some situations.
In this work we compare common recommendation algorithms as implemented in three popular recommendation frameworks.
To provide a fair comparison, we have complete control of the evaluation dimensions being benchmarked: dataset, data splitting, evaluation strategies, and metrics.
We also include results using the internal evaluation mechanisms of these frameworks.
Our analysis points to large differences in recommendation accuracy across frameworks and strategies, i.e. the same baselines may perform orders of magnitude better or worse across frameworks.
Our results show the necessity of clear guidelines when reporting evaluation of recommender systems to ensure reproducibility and comparison of results.
On the Distinction of Functional and Quality Requirements in PracticeDaniel Mendez
The document presents results from a survey of 103 practitioners regarding their handling of functional requirements (FRs) versus quality requirements (QRs). Key findings include:
1) Most practitioners document QRs separately from FRs, but some do not distinguish between the two.
2) Reasons for distinguishing include different nature/stakeholders of QRs, influence on architecture/testing, while reasons for not distinguishing include guidance/tool limitations and seeing no difference.
3) Potential benefits of distinguishing include focused design/testing and increased QR awareness, while drawbacks include increased effort and potential neglect of QRs.
Theory Building in RE - The NaPiRE InitiativeDaniel Mendez
Talk I gave on the "Naming the Pain in Requirements Engineering" initiative (www.re-survey.org) at the Seminar on Forty Years of Requirements Engineering – Looking Forward and Looking Back (RE@40) in Kappel am Albis, Switzerland
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
This document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes three individual assignments analyzing a work-related project using SDLC phases and a final group project applying the full SDLC methodology. Discussion questions address key elements of each SDLC phase like scope, requirements, design constraints, and challenges of system development.
Design Thinking for Requirements EngineeringDaniel Mendez
This document provides an overview of a tutorial on Design Thinking for Requirements Engineering (DT4RE). The tutorial aims to introduce basic principles and methods of Design Thinking and discuss how it can be integrated with Requirements Engineering. It outlines different approaches to integrating Design Thinking and Requirements Engineering based on the complexity of the project from pure Design Thinking to fully integrated approaches. The tutorial also discusses open research challenges around principles, artifacts, project influences, methods adoption, and operationalization of Design Thinking and Requirements Engineering processes.
This document outlines the coursework for BSA 376 which includes several individual assignments and a group assignment. The individual assignments involve analyzing a work-related project using systems analysis and the SDLC process. This includes gathering requirements, designing system architecture and processes, and discussing the development and implementation stages. The group assignment involves applying the full SDLC methodology to address a specific functional area need through a paper and presentation. Discussion questions are also provided for each week.
Collaborative Agile Research, por Claudia MeloThoughtworks
Pesquisa ágil colaborativa: princípios para uma pesquisa aplicada de impacto.
Mais do que nunca, a união de forças entre academia e indústria se faz necessária para que a sociedade possa criar as soluções de seu tempo. Como ex-aluna do IME, pesquisadora e profissional de mercado, vou falar sobre princípios de como fazer pesquisa aplicada de alta qualidade e impacto, de maneira ágil, contando histórias reais de sucesso (e algumas de fracasso).
The document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes three individual assignments analyzing a work-related project using different SDLC phases, from analysis to design to implementation. It also includes a final group project applying the full SDLC methodology to address a specific functional area need. Discussion questions cover key elements of different SDLC phases and methodologies.
In this presentation we introduce SAMOD, a.k.a. Simplified Agile Methodology for Ontology Development, a novel agile methodology for the development of ontologies by means of small steps of an iterative workflow that focuses on creating well-developed and documented models starting from exemplar domain descriptions.
Euro symposium Action Design Research practise 19092019Matti Rossi
Matti Rossi is a professor at Aalto University School of Business in Finland. He discusses action design research (ADR), which integrates design research and action research. ADR aims to solve organizational problems while also contributing to academic knowledge. It involves four stages: problem formulation, building/intervention/evaluation, reflection/learning, and formalization of learning. As an example, Rossi describes a case where ADR was used to develop strategies and tools to improve transparency in a software company's globally distributed R&D network.
This document contains information about assignments and discussion questions for a business systems development life cycle (SDLC) course. It includes assignments on analyzing a work-related project using systems analysis tools, describing the architecture and process design, and discussing the development and implementation stages. It also includes discussion questions about important elements in SDLC phases, different SDLC approaches, defining project scope, constraints on system design, and development and implementation approaches. A final group project involves applying the full SDLC methodology to address a functional area's needs.
Presentation of IEEE TSE Journal First paper at ICSE 2020
Abstract:
Developer satisfaction and work productivity are important
considerations for software companies. Enhanced developer satisfaction may improve the attraction, retention and health of employees, while higher productivity should reduce costs and increase customer satisfaction through faster software improvements. Many researchers and companies assume that perceived productivity and job satisfaction are related and may be used as proxies for one another, but these claims are a current topic of debate. There are also many social and technical
factors that may impact satisfaction and productivity, but which factors have the most impact is not clear, especially for specific development contexts. Through our research, we developed a theory articulating a bidirectional relationship between software developer job satisfaction and perceived productivity, and identified what additional social and technical
factors, challenges and work context variables influence this relationship. The constructs and relationships in our theory were derived in part from related literature in software engineering and knowledge work, and we validated and extended these concepts through a rigorously designed survey instrument. We instantiate our theory with a large software company, which suggests a number of propositions about the relative impact of various factors and challenges on developer satisfaction and perceived productivity. Our survey instrument and analysis approach
can be applied to other development settings, while our findings lead to concrete recommendations for practitioners and researchers.
Authors:
Margaret-Anne Storey, Tom Zimmermann, Chris Bird, Jacek Czerwonka, Brendan Murphy and Eirini Kalliamvakou
This document discusses criteria and techniques for prioritizing projects for sustainable economic development in the Sudurnes region of Iceland. It outlines several criteria for prioritization including accession, competitiveness, financial and economic, technical, social and political, and commercial and institutional factors. The document also describes approaches to prioritization such as selecting a prioritization team, identifying relevant criteria, selecting and weighting criteria, applying the criteria to projects to calculate scores and rankings. Project selection procedures and techniques like financial analysis, cost-benefit analysis, and multi-criteria analysis are also summarized.
This document outlines the assignments and discussion questions for a course on systems development lifecycle (SDLC). It includes 3 individual papers and 1 group paper analyzing different phases of an SDLC for a work-related project. It also includes discussion questions about important elements, approaches, scope, requirements, design constraints, security, and challenges of the SDLC process.
Mehmet Aydın, KHU - Nurullah Battal, Roche | Agile Turkey Summit 2013Agile Turkey
Enabling Organizational Change through Agile Methods
Agile approaches and methods have been promoted as a panacea for long-standing problems in IT projects. Such problems may be denoted as “one-size-fits-all issues”, “failing to embrace changes in the projects”, “lack of IT-Business Alignment”. Recently, practitioners have experienced that agile methods can be used as a means to facilitate change concerning IT mind-set and practice as well. This talk is concerned with the effects of agile method on organizational change. We explore underpinnings of an agile-enabled organizational change in terms of the way of thinking and actions. To articulate such underpinnings an exemplary case is used. Reflections on lessons-learned and practical insights are to be presented as well.
Evaluability Assessments and Choice of Evaluation MethodsDebbie_at_IDS
The document discusses evaluability assessments (EAs) and how they can inform the choice of evaluation methods. Key points:
- EAs examine a project's design, available information, and context to determine if and how an evaluation could be conducted. They help ensure evaluations are useful and feasible.
- Common EA steps include reviewing documentation, engaging stakeholders, and making recommendations about a project's logic, monitoring systems, and potential evaluation approaches.
- Choosing evaluation methods depends on the EA results as well as the evaluation's purpose, required credibility, complexity of the intervention, and available resources. Methods like experiments provide strong evidence of impact but are difficult to implement.
- EAs improve evaluation quality by engaging
Different testers have different understandings of the role and mission of software testing; of the approaches, methods, and techniques to use during testing.
Comparative Recommender System Evaluation: Benchmarking Recommendation Frame...Alan Said
Video available here http://www.youtube.com/watch?v=1jHxGCl8RXc
Recommender systems research is often based on comparisons of predictive accuracy: the better the evaluation scores, the better the recommender.
However, it is difficult to compare results from different recommender systems due to the many options in design and implementation of an evaluation strategy.
Additionally, algorithmic implementations can diverge from the standard formulation due to manual tuning and modifications that work better in some situations.
In this work we compare common recommendation algorithms as implemented in three popular recommendation frameworks.
To provide a fair comparison, we have complete control of the evaluation dimensions being benchmarked: dataset, data splitting, evaluation strategies, and metrics.
We also include results using the internal evaluation mechanisms of these frameworks.
Our analysis points to large differences in recommendation accuracy across frameworks and strategies, i.e. the same baselines may perform orders of magnitude better or worse across frameworks.
Our results show the necessity of clear guidelines when reporting evaluation of recommender systems to ensure reproducibility and comparison of results.
On the Distinction of Functional and Quality Requirements in PracticeDaniel Mendez
The document presents results from a survey of 103 practitioners regarding their handling of functional requirements (FRs) versus quality requirements (QRs). Key findings include:
1) Most practitioners document QRs separately from FRs, but some do not distinguish between the two.
2) Reasons for distinguishing include different nature/stakeholders of QRs, influence on architecture/testing, while reasons for not distinguishing include guidance/tool limitations and seeing no difference.
3) Potential benefits of distinguishing include focused design/testing and increased QR awareness, while drawbacks include increased effort and potential neglect of QRs.
Case studies in industry - fundamentals and lessons learntDaniel Mendez
This document discusses case study research and provides guidance on conducting case studies. It defines a case study as an empirical inquiry that investigates real-world phenomena in their natural context. The document outlines why case studies are used to learn from realistic environments and scale findings to practice. Challenges of approaching, conducting, and analyzing case studies are presented, such as properly characterizing context, defining instruments, and drawing conclusions. Transversal challenges include addressing subjectivity and generalizability. Key takeaways emphasize careful planning, transparency, collaboration, and being unbiased, accurate, patient and flexible.
In Quest for Requirements Engineering Oracles: Dependent Variables and Measur...Daniel Mendez
This document summarizes the results of a study to identify dependent variables and measurements in requirements engineering (RE). The study found 93 RE-related variables with 167 dependencies. Variables in the RE dimension had a high degree of measurability, often based on artifacts. Measurability decreased farther from the RE context. However, the system of variables is complex and incomplete, and variables depend strongly on subjectivity. There is no "oracle" or generalizable set of variables, limiting evidence-based RE research.
Theories in Empirical Software EngineeringDaniel Mendez
Slides from the International Advanced School on Empirical Software Engineering 2015, held as part of the Empirical Software Engineering International Week in Beijing. The slides are posted with the permission of the main organiser Roel Wieringa.
Scientific software engineering methods and their validityDaniel Mendez
This document summarizes a talk on scientific methods and their validity given at Technische Universität München. The talk discusses key concepts in the philosophy of science like epistemology and different views of science. It provides an overview of common scientific methods like empirical methods, case studies, and hypothesis testing. The talk delves into challenges of obtaining truth and impacts of human factors. It also discusses how scientific methods can be applied in a PhD dissertation and the importance of increasing validity. The overall document aims to discuss implications of scientific methods for everyday scientific work.
An Introduction into Philosophy of Science for Software Engineers Daniel Mendez
This document provides an overview of the key concepts and historical context related to philosophy of science. It discusses what science is about at a high level, including systematically gaining and disseminating knowledge. It also discusses the necessary postulates for scientific work, including that there is a reality that exists independently of individuals' observations. The document then discusses what constitutes a scientific theory, including that theories must survive tests and criticism. It also discusses the relationship between theories and hypotheses. Finally, it provides an overview of the process of moving from real-world observations to developing theories and back.
Assessment and Feedback programme update (April 2012)jisc-elearning
This document provides an overview of the JISC Assessment and Feedback programme, which has three strands of projects running from 2011-2014 aimed at increasing the usage of technology-enhanced assessment and feedback practices in UK higher education. Strand A involves 8 implementation projects, Strand B includes 8 evidence and evaluation projects, and Strand C comprises 4 larger innovation projects. The programme aims to provide increased efficiencies and improvements in assessment quality, enhance the student and staff experience, and generate clear business cases and models of sustainable institutional support. It is supported by a central programme team and synthesis project to capture learning across the initiatives.
The document discusses a workshop for program evaluators (PEVs) organized by the Board of Accreditation for Engineering and Technical Education (BAETE) in Dhaka. The workshop covers several interactive sessions to help PEVs design assessment forms and schedule on-site visits. It emphasizes evaluating programs based on BAETE's 11 accreditation criteria, with a focus on assessing attainment of program outcomes and continuous quality improvement. The document provides guidance on what PEVs should look for during visits and how outcomes should be assessed to determine compliance with accreditation standards.
This document discusses project auditing and closure. It describes the tasks of a project audit, which include evaluating stakeholder benefits and satisfaction, assessing successes and failures, and identifying improvements. The audit process involves initiation, data collection, analysis, and reporting. Project closure objectives are also outlined, such as determining termination reasons and describing closure tasks like getting acceptance, releasing resources, and evaluating performance. Lessons learned through retrospectives are emphasized as important for organizational improvement.
1. Formative evaluation is a crucial part of the design research process that aims to improve educational interventions and refine design principles through iterative prototyping.
2. It provides insights to identify shortcomings in prototypes of interventions and their underlying design principles in order to improve the quality and effectiveness of the final intervention.
3. The formative evaluation process involves developing research questions focused on evaluating key attributes of a prototype, selecting appropriate evaluation methods, sampling respondents, collecting and analyzing data to inform revisions to the prototype and design principles.
The document summarizes an initiative called interACT that aimed to improve feedback and assessment practices through the use of technology. The project developed an online system for students to self-evaluate their work, request specific feedback, and engage in dialogue about feedback with tutors. An evaluation found that students found the process clear and valuable for obtaining targeted feedback and discussing their work. Future work includes developing more interactive digital tools to improve feedback exchanges.
CAPM exam preparation developed for self learning.
Plz don't mind some logo and strikethrough.. they were meant to create fun for myself.
You may join the course from Udemy as I take and enjoy the class from there.
With discount it was only $11.
Mr.Joseph Phillips
https://www.udemy.com/share/101WE2AkcZd15VRn4=/
The self-assessment report summarizes Indus University's presentation on the concept and procedure of self-assessment reports to Lasbela University. It discusses the importance of quality assurance in higher education and outlines the objectives and components of conducting a self-assessment, including analyzing program missions and outcomes, curriculum, facilities, and other criteria. The presentation provides examples of how to measure objectives and outcomes both qualitatively and quantitatively and identify areas for improvement in order to enhance student learning and meet international standards.
The document summarizes a panel discussion on quality assurance programs for online courses. The panelists represented Quality Matters, Texas Woman's University, Park University, and UT TeleCampus. They discussed their respective quality assurance programs and addressed key issues like the impact on faculty participation, study outcomes, the value of the review process, and lessons learned. The document provides details on each program and studies that showed improvements in student learning and satisfaction from applying a quality review process to online course design.
Curriculum evaluation: The assessment of the merit and worth of any program curriculum.
Curriculum evaluation is an attempt to toss light on two questions: Do planned programs, courses, activities, and learning opportunities as developed and organized actually produce desired results/learning outcomes? How can the curriculum offerings best be improved?
Curriculum Evaluation Models: How can the merits and worth of such aspects of curriculum is determined? Evaluation specialists have proposed an array of models, an examination of which can provide useful background for the process curriculum evaluation.
This document outlines expectations and guidelines for undergraduate final year projects (FYP) in engineering at UniMAP. It discusses common challenges students may face, including delays in starting their projects, poor time management, and unrealistic expectations. It also summarizes the expectations for FYPs based on the Engineering Accreditation Council manual, including integrating investigative research, analysis, and developing technical skills. Finally, it discusses evaluating FYPs based on rubrics that assess project management, progress reports, and presentations.
This document outlines key aspects of outcome-based education (OBE) and the accreditation process for engineering programs. It discusses OBE principles like focusing on what students learn rather than what is taught. The document also describes international accords for engineers, technologists, and technicians. It provides details on curriculum review, teaching methods, assessment tools, and continuous quality improvement in OBE. Finally, it lists the documentation required for accreditation visits, including program outcomes, course files, facilities, and actions taken on previous deficiencies.
The document discusses changes to the PMP certification exam announced by PMI. It provides details on the new exam content outline structure, including domains, tasks, and enablers. The exam outline has been simplified and restructured, with People and Process domains now accounting for 42% and 50% of exam questions respectively. The document provides the full new exam content outline detailing the tasks and enablers within each domain.
This document describes the interACT project which aims to improve assessment and feedback practices through the use of technology. It discusses how the project embarked on a literature review to identify key principles of effective feedback. Baseline activities revealed inconsistencies in feedback that the project sought to address. The project re-engineered assessments, provided faculty development, and engaged students in feedback through self-review and use of a wiki. Future developments include creating e-activities to improve feedback dialogue and introducing new assignment types.
Value engineering is a technique used to improve projects, processes, products, or services by determining the best functional balance between cost, reliability, and performance. It aims to identify unnecessary costs that can be eliminated without compromising quality, performance, or customer satisfaction. A value engineering study is conducted systematically using an eight-step job plan involving information gathering, functional analysis, creative idea generation, evaluation, and implementation. The goal is to deliver necessary functions at the lowest cost through improvements to design, materials selection, production processes, maintenance, and other factors.
Outcome Based Education, Washington Accord, International Engineering Alliance, Graduate Attributes, Program Outcome, Competency, Performance Indicator, Examination Reforms by AICTE
Help my project is in trouble. I have put this together to give project managers a guideline on how to move your project back into a successful journey
The document summarizes ISO/IEC 20246, which provides guidance on work product reviews. It describes the generic review process, including planning, individual reviews, issue collation, and reporting. It also covers different review techniques like checklist-based and scenario-based reviewing. Finally, it discusses factors to consider when choosing a review approach and provides an overview of the ISO 20246 standard development process and opportunities to get involved.
In Quest of Requirements Engineering Research that Industry NeedsDaniel Mendez
The document discusses the need for requirements engineering (RE) research that is relevant to industry. It argues that RE research should become more theory-centric and problem-driven by understanding the real problems faced by practitioners. The author advocates for increased collaboration between academia and industry to analyze problems in their natural environments. As an example, the document summarizes the findings of a large global survey of RE practices and problems called NaPiRE, which identified common issues reported by 228 companies in 10 countries. The goal is to use empirical evidence from industry to inform RE research and increase its practical impact.
This document outlines an agenda for a workshop on surveys in software engineering. The workshop will cover four sessions: an introduction to surveys, best practices for designing and conducting software engineering surveys, a hands-on session for designing a survey using an online tool, and a question and answer session. The introduction will cover basic concepts of survey research including research objectives, sampling, instrument design, and analysis. The best practices session will focus on key aspects of software engineering surveys and lessons learned. Participants are encouraged to actively engage by asking questions and sharing their experiences with survey research.
Mending Clothing to Support Sustainable Fashion_CIMaR 2024.pdfSelcen Ozturkcan
Ozturkcan, S., Berndt, A., & Angelakis, A. (2024). Mending clothing to support sustainable fashion. Presented at the 31st Annual Conference by the Consortium for International Marketing Research (CIMaR), 10-13 Jun 2024, University of Gävle, Sweden.
TOPIC OF DISCUSSION: CENTRIFUGATION SLIDESHARE.pptxshubhijain836
Centrifugation is a powerful technique used in laboratories to separate components of a heterogeneous mixture based on their density. This process utilizes centrifugal force to rapidly spin samples, causing denser particles to migrate outward more quickly than lighter ones. As a result, distinct layers form within the sample tube, allowing for easy isolation and purification of target substances.
Signatures of wave erosion in Titan’s coastsSérgio Sacani
The shorelines of Titan’s hydrocarbon seas trace flooded erosional landforms such as river valleys; however, it isunclear whether coastal erosion has subsequently altered these shorelines. Spacecraft observations and theo-retical models suggest that wind may cause waves to form on Titan’s seas, potentially driving coastal erosion,but the observational evidence of waves is indirect, and the processes affecting shoreline evolution on Titanremain unknown. No widely accepted framework exists for using shoreline morphology to quantitatively dis-cern coastal erosion mechanisms, even on Earth, where the dominant mechanisms are known. We combinelandscape evolution models with measurements of shoreline shape on Earth to characterize how differentcoastal erosion mechanisms affect shoreline morphology. Applying this framework to Titan, we find that theshorelines of Titan’s seas are most consistent with flooded landscapes that subsequently have been eroded bywaves, rather than a uniform erosional process or no coastal erosion, particularly if wave growth saturates atfetch lengths of tens of kilometers.
Sexuality - Issues, Attitude and Behaviour - Applied Social Psychology - Psyc...PsychoTech Services
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Candidate young stellar objects in the S-cluster: Kinematic analysis of a sub...Sérgio Sacani
Context. The observation of several L-band emission sources in the S cluster has led to a rich discussion of their nature. However, a definitive answer to the classification of the dusty objects requires an explanation for the detection of compact Doppler-shifted Brγ emission. The ionized hydrogen in combination with the observation of mid-infrared L-band continuum emission suggests that most of these sources are embedded in a dusty envelope. These embedded sources are part of the S-cluster, and their relationship to the S-stars is still under debate. To date, the question of the origin of these two populations has been vague, although all explanations favor migration processes for the individual cluster members. Aims. This work revisits the S-cluster and its dusty members orbiting the supermassive black hole SgrA* on bound Keplerian orbits from a kinematic perspective. The aim is to explore the Keplerian parameters for patterns that might imply a nonrandom distribution of the sample. Additionally, various analytical aspects are considered to address the nature of the dusty sources. Methods. Based on the photometric analysis, we estimated the individual H−K and K−L colors for the source sample and compared the results to known cluster members. The classification revealed a noticeable contrast between the S-stars and the dusty sources. To fit the flux-density distribution, we utilized the radiative transfer code HYPERION and implemented a young stellar object Class I model. We obtained the position angle from the Keplerian fit results; additionally, we analyzed the distribution of the inclinations and the longitudes of the ascending node. Results. The colors of the dusty sources suggest a stellar nature consistent with the spectral energy distribution in the near and midinfrared domains. Furthermore, the evaporation timescales of dusty and gaseous clumps in the vicinity of SgrA* are much shorter ( 2yr) than the epochs covered by the observations (≈15yr). In addition to the strong evidence for the stellar classification of the D-sources, we also find a clear disk-like pattern following the arrangements of S-stars proposed in the literature. Furthermore, we find a global intrinsic inclination for all dusty sources of 60 ± 20◦, implying a common formation process. Conclusions. The pattern of the dusty sources manifested in the distribution of the position angles, inclinations, and longitudes of the ascending node strongly suggests two different scenarios: the main-sequence stars and the dusty stellar S-cluster sources share a common formation history or migrated with a similar formation channel in the vicinity of SgrA*. Alternatively, the gravitational influence of SgrA* in combination with a massive perturber, such as a putative intermediate mass black hole in the IRS 13 cluster, forces the dusty objects and S-stars to follow a particular orbital arrangement. Key words. stars: black holes– stars: formation– Galaxy: center– galaxies: star formation
JAMES WEBB STUDY THE MASSIVE BLACK HOLE SEEDSSérgio Sacani
The pathway(s) to seeding the massive black holes (MBHs) that exist at the heart of galaxies in the present and distant Universe remains an unsolved problem. Here we categorise, describe and quantitatively discuss the formation pathways of both light and heavy seeds. We emphasise that the most recent computational models suggest that rather than a bimodal-like mass spectrum between light and heavy seeds with light at one end and heavy at the other that instead a continuum exists. Light seeds being more ubiquitous and the heavier seeds becoming less and less abundant due the rarer environmental conditions required for their formation. We therefore examine the different mechanisms that give rise to different seed mass spectrums. We show how and why the mechanisms that produce the heaviest seeds are also among the rarest events in the Universe and are hence extremely unlikely to be the seeds for the vast majority of the MBH population. We quantify, within the limits of the current large uncertainties in the seeding processes, the expected number densities of the seed mass spectrum. We argue that light seeds must be at least 103 to 105 times more numerous than heavy seeds to explain the MBH population as a whole. Based on our current understanding of the seed population this makes heavy seeds (Mseed > 103 M⊙) a significantly more likely pathway given that heavy seeds have an abundance pattern than is close to and likely in excess of 10−4 compared to light seeds. Finally, we examine the current state-of-the-art in numerical calculations and recent observations and plot a path forward for near-future advances in both domains.
The cost of acquiring information by natural selectionCarl Bergstrom
This is a short talk that I gave at the Banff International Research Station workshop on Modeling and Theory in Population Biology. The idea is to try to understand how the burden of natural selection relates to the amount of information that selection puts into the genome.
It's based on the first part of this research paper:
The cost of information acquisition by natural selection
Ryan Seamus McGee, Olivia Kosterlitz, Artem Kaznatcheev, Benjamin Kerr, Carl T. Bergstrom
bioRxiv 2022.07.02.498577; doi: https://doi.org/10.1101/2022.07.02.498577
Anti-Universe And Emergent Gravity and the Dark UniverseSérgio Sacani
Recent theoretical progress indicates that spacetime and gravity emerge together from the entanglement structure of an underlying microscopic theory. These ideas are best understood in Anti-de Sitter space, where they rely on the area law for entanglement entropy. The extension to de Sitter space requires taking into account the entropy and temperature associated with the cosmological horizon. Using insights from string theory, black hole physics and quantum information theory we argue that the positive dark energy leads to a thermal volume law contribution to the entropy that overtakes the area law precisely at the cosmological horizon. Due to the competition between area and volume law entanglement the microscopic de Sitter states do not thermalise at sub-Hubble scales: they exhibit memory effects in the form of an entropy displacement caused by matter. The emergent laws of gravity contain an additional ‘dark’ gravitational force describing the ‘elastic’ response due to the entropy displacement. We derive an estimate of the strength of this extra force in terms of the baryonic mass, Newton’s constant and the Hubble acceleration scale a0 = cH0, and provide evidence for the fact that this additional ‘dark gravity force’ explains the observed phenomena in galaxies and clusters currently attributed to dark matter.
Anti-Universe And Emergent Gravity and the Dark Universe
A Case Study on Artefact-based RE Improvement in Practice
1. Technische Universität München
A Case Study on
Artefact-based RE Improvement in Practice
Joint work with
Stefan Wagner, University of Stuttgart
Daniel Méndez
Technical University of Munich
Germany
PROFES 2015
Bozen-Bolzano, Italy
@mendezfe
2. Notion of RE quality is eventually relative to its context!
[RUP-derivate]
Does this represent a good or a bad
Requirements Engineering (RE)?
3. Notion of RE quality and its improvement
Socio-economic context
RE “Best Practice” Norm
Goals,
expectations,
…
1. Solution orientation
Assess/Benchmark
RE reference modelAdopt
RE improvement principles
4. Notion of RE quality and its improvement
Socio-economic context
RE “Best Practice” Norm
Goals,
expectations,
…
1. Solution orientation
2. Problem orientation
Serves as
Orientation
Steer
RE reference model
RE improvement principles
5. Notion of RE quality and its improvement
Socio-economic context
RE “Best Practice” Norm
Goals,
expectations,
…
1. Solution orientation
2. Problem orientation
Paradigms (simplified)
Serves as
Orientation
Steer
RE reference model
RE improvement principles
6. Notion of RE quality and its improvement
Socio-economic context
RE “Best Practice” Norm
Goals,
expectations,
…
1. Solution orientation
2. Problem orientation
Paradigms (simplified)
A
A. Activity orientation
B
B. Artefact orientation
Serves as
Orientation
Steer
RE reference model
RE improvement principles
7. Potential and limitations of problem-driven, artefact-based RE improvement still unknown
Problem
Problem-driven, artefact-based RE improvement
Why? Goals,
expectations,
…Steer
» Notion of RE quality is something relative to context
» Reluctance against solution orientation in practice*
„I am not convinced of the benefits of external standards.“
Why problem orientation
Why artefact orientation
» Allows to abstract from complex processes
» Supports, e.g., flexibility and consistency in artefacts
* http://re-survey.org
8. Artefact-based RE improvement approach
• Blueprint of an artefact-b. and problem-driven RE improvement
• Process realisation in EPF composer, templates, …
Details on theapproach presentedat PROFES 2013 & PROFES 2014
9. Artefact-based RE Improvement
Process
engineers
Comparative
evaluation
(against CMMI-based approaches)
Art.-based
RE Imp.
Approach
Evaluation of artefact-based RE improvement
Study design overview
• Case 1:Wacker Chemie
• Case 2: SupplyOn AG (independent replication)
Goals
• Evaluate
problem-driven and artefact-based RE improvement
in industrial context compared to
solution-driven and activity-based approaches
Approach: Case study research
Research questions
Project environment
Artefact-based
RE Project
participants
Comparative
evaluation
Legacy RE approach
1. How well are process engineers supported in their RE improvement tasks?
2. How well are project participants supported by the resulting RE reference model?
10. Study 1
Study 2
Study 1
Study 2
Case studies on artefact-based RE improvement
Essence of rating
RQ 1 Structured approach to RE improvement
Context-specific RE impr. goals achieved
The good: It worked
RQ 2
(The actually interesting parts…)
The bad: It worked, but only “somehow”…
Research questions
1. How well are process engineers supported in their RE improvement tasks?
2. How well are project participants supported by the resulting RE reference model?
11. Case studies on artefact-based RE improvement
Qualitative feedback from participants
Process engineers (RQ 1)
• Domain knowledge is essential for efficient improvement
• Workshops fostered discussions engineers would otherwise not have
• Need for fast improvement cycles (e.g. meetings every week)
• Need for additional studies when many changes have been made
• The success of a pilot study strongly depends on the quality of the tools
• Coaching should focus on why things should be done, not how
• Focus not only on artefacts, but also suggest methods and techniques
• Not too many changes at once
Project participants (RQ 2)
12. Limitations
• Problem orientation at the cost of certification
• Social factors never fully covered by models and approaches
• Improvement effects beyond RE not objectively measurable
• Relation between process quality and artefact quality not completely clear
Success factors (selected)
• Awareness of management for problems at project level
• Willingness to participate and openness to change
• Domain knowledge
• Respect (and reflect) organisational culture
• Skills (social skills, empirical skills) and openness for pragmatism
Case studies on artefact-based RE improvement
13. Thank you!
Daniel Méndez
Daniel.Mendez@tum.de
@mendezfe
Further reading
• Slides will be made available
(and probably tweeted)
• Ask me if you need material
(tools, instruments …)
http://www4.in.tum.de/~mendezfe/openspace.shtml
[PROFES 2013]
[PROFES 2015]