01.intro
•Download as PPT, PDF•
1 like•594 views
This document provides an overview of the ICS 314 and 613: Software Engineering course taught by Philip Johnson. It outlines the instructor's background and contact information, goals of the course, what constitutes "quality" software, open source development principles, standards and feedback, course structure, prerequisites, grading, differences between 314 and 613, lectures and labs, quizzes, engineering log requirements, developing a professional persona, collaboration vs. cheating policies, and lessons learned from past students.
Report
Share
Report
Share
![Contact Information ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
How to improve Developer Documentations ?
The document proposes solutions to improve the Teams Dev Docs by addressing developer pain points. It identifies key pain points such as difficulty finding relevant content and understanding errors. Possible solutions include a chatbot that can quickly answer questions and documentation that allows coding in native languages. User research is cited to validate the identified pain points. A phased go-to-market strategy is proposed starting with targeted launches of the chatbot and native language support to capture early adopters. The solutions aim to reduce time spent on documentation and increase new developer adoption.
About Dewey Hong
This document introduces Dewey Hong, a software architect with extensive experience leading technical consulting projects. It summarizes his roles and responsibilities in recent projects, technical skills, development experience, and vision. He has worked as a chief architect, software architect, and project manager on projects ranging from ERP systems to mobile apps. His skills include programming languages like Java and frameworks like Spring, as well as SAP expertise. Hong aims to be a technical specialist providing solutions, architecture design, and development process optimization consulting to solve clients' problems.
Enhancing Developer Productivity with Code Forensics
Imagine an engineering system that could evaluate developer performance, recognize rushed check-ins, and use that data to speed up development. “Congratulations Jane. You know this code well. No check-in test gate for you.” Anthony Voellm shares how behavioral analysis and developer assessments can be applied to improve productivity. This approach was motivated by today's test systems, tools, and processes that are all designed around the premise that “all developers are created equal.” Studies have shown developer error rates can vary widely and have a number of root causes—the mindset of the developer at the time the code was written, experience level, amount of code in a check-in, complexity of the code, and much more. With Digital Code Forensics, a set of metrics that can evaluate developers, Anthony demonstrates how even modest applications of this approach can speed up development. Discover and use the cutting edge of engineering productivity.
DataMind: An e-learning platform for Data Analysis based on R. RBelgium meetu...
We're looking for people to give us feedback on the prototype containing a first introduction to R tutorial on http://beta.datamind.org.
Open Source Project Management
The document discusses best practices for managing open source projects, including choosing a name and license, setting up communication channels like mailing lists and version control, managing releases, packaging, and translations. Key aspects are being open and transparent from the start, using tools like wikis to organize documentation, and maintaining a consistent vision to keep developers engaged over time. Managing releases involves numbering schemes, release branches, testing, and supporting multiple versions.
Software Analysis using Natural Language Queries
Understanding a software system consumes a substantial portion of a developer's effort. To support software comprehension and evolution, reverse engineering aims at creating a high-level representation of an existing software system. With state- of-the-art technology, abstract models of software systems are created by reverse engineering tools and analyzed using software analysis tools. Despite the rich functionalities offered by analysis tools, a novice user may find them difficult to use due to an unfamiliar tool environment and query language. In this paper, we propose an approach that allows the developer to formulate a query in a natural language in order to overcome these obstacles.
Let linguistics guide software analysis
Importance of English language in software development and its analysis can help developers in performing various program comprehension tasks.
Why can't developers be testers discussion
Slides from my discussion session at the July 2017 Assurance Leadership Forum (https://ukalf.com/) in London
Recommended
How to improve Developer Documentations ?
The document proposes solutions to improve the Teams Dev Docs by addressing developer pain points. It identifies key pain points such as difficulty finding relevant content and understanding errors. Possible solutions include a chatbot that can quickly answer questions and documentation that allows coding in native languages. User research is cited to validate the identified pain points. A phased go-to-market strategy is proposed starting with targeted launches of the chatbot and native language support to capture early adopters. The solutions aim to reduce time spent on documentation and increase new developer adoption.
About Dewey Hong
This document introduces Dewey Hong, a software architect with extensive experience leading technical consulting projects. It summarizes his roles and responsibilities in recent projects, technical skills, development experience, and vision. He has worked as a chief architect, software architect, and project manager on projects ranging from ERP systems to mobile apps. His skills include programming languages like Java and frameworks like Spring, as well as SAP expertise. Hong aims to be a technical specialist providing solutions, architecture design, and development process optimization consulting to solve clients' problems.
Enhancing Developer Productivity with Code Forensics
Imagine an engineering system that could evaluate developer performance, recognize rushed check-ins, and use that data to speed up development. “Congratulations Jane. You know this code well. No check-in test gate for you.” Anthony Voellm shares how behavioral analysis and developer assessments can be applied to improve productivity. This approach was motivated by today's test systems, tools, and processes that are all designed around the premise that “all developers are created equal.” Studies have shown developer error rates can vary widely and have a number of root causes—the mindset of the developer at the time the code was written, experience level, amount of code in a check-in, complexity of the code, and much more. With Digital Code Forensics, a set of metrics that can evaluate developers, Anthony demonstrates how even modest applications of this approach can speed up development. Discover and use the cutting edge of engineering productivity.
DataMind: An e-learning platform for Data Analysis based on R. RBelgium meetu...
We're looking for people to give us feedback on the prototype containing a first introduction to R tutorial on http://beta.datamind.org.
Open Source Project Management
The document discusses best practices for managing open source projects, including choosing a name and license, setting up communication channels like mailing lists and version control, managing releases, packaging, and translations. Key aspects are being open and transparent from the start, using tools like wikis to organize documentation, and maintaining a consistent vision to keep developers engaged over time. Managing releases involves numbering schemes, release branches, testing, and supporting multiple versions.
Software Analysis using Natural Language Queries
Understanding a software system consumes a substantial portion of a developer's effort. To support software comprehension and evolution, reverse engineering aims at creating a high-level representation of an existing software system. With state- of-the-art technology, abstract models of software systems are created by reverse engineering tools and analyzed using software analysis tools. Despite the rich functionalities offered by analysis tools, a novice user may find them difficult to use due to an unfamiliar tool environment and query language. In this paper, we propose an approach that allows the developer to formulate a query in a natural language in order to overcome these obstacles.
Let linguistics guide software analysis
Importance of English language in software development and its analysis can help developers in performing various program comprehension tasks.
Why can't developers be testers discussion
Slides from my discussion session at the July 2017 Assurance Leadership Forum (https://ukalf.com/) in London
Agile Languages for Rapid Prototyping
These slides were used to teach the above subject for the 3rd year undergrads of the Departement of Computer Engineering, University of Peradeniya in 2009, under IFS-PERADENIYA industry -university collaboration.
Comment soup with a pinch of types, served in a leaky bowl
Comment soup with a pinch of types, served in a leaky bowl
Talk by Pooja Rani and Manuel Leuenberger, PharoDays 2019
Training report
This document provides a project report for an online photo sharing and social networking service called IMAGINATE. It discusses the technologies used including Java, HTML, CSS, JavaScript, MySQL, and provides an overview of the different modules in the project including user and admin modules. It describes the project methodology which involved information gathering, system requirement analysis, and design. The major operations of the project allow users to register, view galleries and top rated photos, contact admin, and vote for good pictures.
How to write maintainable code - Peter Hilton - Codemotion Amsterdam 2017
The problem that new technology doesn’t fix is unmaintainable code. Clean code with good tests is essential, but not enough. This talk introduces techniques like getting better at naming, explaining code with tests, the few code comments you actually need, README-driven development and writing Minimum Viable Documentation. After the excitement of adopting new technology and software craftsmanship comes the horror of your next software maintenance project. As Jean-Paul Sartre said*, ‘Hell is other people’s code’. Whatever your level, your future happiness depends on maintainable code.
CS101- Introduction to Computing- Lecture 45
This lecture provides a review and wrap-up of the CS101 Introduction to Computing course. It summarizes key topics covered over the past 44 lectures such as programming methodology, readable code, algorithm design, testing and debugging. It reviews objectives of the course which were to build an appreciation of fundamental computing concepts, familiarize students with popular productivity software, and achieve beginner proficiency in web development. The lecture concludes by asking for student feedback on how well the course objectives were achieved.
Introduction to Agile Software Development & Python
These slides were used to teach the module "Introduction to Agile Software Development & Python" as a sub-section of the major course "Software Engineering" for the 3rd year undergraduates of the Department of Computer Engineering, University of Peradeniya in 2010.
PRG 421 version 10 Entire Course
This document outlines assignments for a Java programming course across 5 weeks. It includes assignments to write code for GUIs, containers, exceptions, files, applets, and databases. It provides examples and prompts students to design and implement programs that incorporate these Java concepts, including a fundraising tracking program due in Week 5. Students are to submit code and responses following an APA template.
Twelve practices of XP_Se lect5 btech
The document describes the twelve core practices of extreme programming (XP). It discusses each practice in 1-2 paragraphs, covering pair programming, refactoring, simple design, collective code ownership, continuous integration, on-site customer, small releases, 40-hour work week, coding standards, system metaphor, planning game, and testing (including unit and acceptance testing). The advantages include customer focus, incremental releases, and continuous testing/integration improving quality. Disadvantages include being suited for a single co-located team and not working as well without customer involvement or for large scalable systems.
An Ultimate Guide To Hire Python Developer
If you are looking for a python developer, it is not as easy as it sounds. There are many factors that come into play when hiring a developer. This guide will help you find the best python developer for your project.
https://www.hackerearth.com/recruit/resources/e-books/hire-python-developer/
Input, Processing and Output
This document provides an introduction to the Python programming language. It discusses that Python is an easy to learn, powerful, high-level and object-oriented programming language. It supports features like object-oriented programming, dynamic typing, functional programming, and scripting. The document also covers Python history, versions, applications, keywords, input/output/variables, and designing programs using flowcharts and pseudocode.
Jdj Foss Java Tools
This document discusses uncommon Java bugs and how free open source static analysis tools can help detect them. It provides examples of bugs like using the letter "l" instead of the number 1 in a long constant, checking for NaN equality, and null pointer exceptions. The document introduces tools like Jlint, FindBugs, PMD, and QJ-Pro that can find these kinds of bugs and describes how each tool detects bugs in code examples. It concludes that using static analysis tools can improve code quality by finding defects early.
Computer software specialists wikki verma
Wikki Verma Suggest Before opening an IT consultancy, I did my homework. I interviewed lifelong consultants. I read books. I even took personality tests to confirm that my psychological constitution matched the challenges I did face as an entrepreneur owning and operating my own business.
Introduction
This document provides an introduction to C# programming, including why it is an important and versatile language, job prospects for C# developers, and an overview of the software development process. Key points include:
- C# can be used to build a wide range of applications and is in high demand with over 100,000 job openings and a projected growth rate of 22% by 2029.
- The software development process involves analysis, design, implementation, testing, and deployment of applications in an iterative manner using approaches like Waterfall or Agile.
- Becoming proficient in C# provides opportunities for well-paying jobs at many companies in roles like software engineer, developer, and more. Understanding programming fundamentals
11 best practices_for_peer_code_review
White paper recommends 11 best practices for efficient peer code review:
1. Review no more than 200-400 lines of code at a time and take 60-90 minutes or less per review for optimal effectiveness.
2. Aim for an inspection rate of less than 300-500 LOC per hour and spend at least 5 minutes on each review.
3. Have authors annotate source code before review to eliminate most defects beforehand and improve efficiency.
4. Establish quantifiable goals, collect metrics, and refine processes over time to continuously improve results.
Empirical evaluation in 2020: how big, how beautiful?
The document discusses empirical evaluation standards in software engineering research. It notes that evaluation standards have become more rigorous over time, as seen in a comparison of papers from 2001 and 2018. Today's evaluations generally analyze more data, make better use of inferential statistics, but still underutilize qualitative methods and rarely involve developers. The document emphasizes the importance of high quality data and validation when mining software repositories, as these sources often contain imprecise and incomplete information that can bias results. It also stresses selecting a diverse set of projects for studies to improve generalizability.
Lecture 2
This lecture covers creating and structuring C# projects and applications in Visual Studio 2010. It discusses creating solutions and projects, the structure of a C# application including namespaces and classes, writing and running code, using variables and data types, commenting code, and debugging applications using breakpoints, stepping through code, and inspecting variables. The lecture emphasizes the importance of commenting code for future understanding and maintenance.
Stop fearing legacy code
It is time to fight the black holes in your software. Don't let legacy code dictate your work. Start learning and practicing dependency injection and refactoring. Become more agile.
Managing Inquiry-based Learning: Learning from experience
We have taught a suite of inquiry-based learning modules for the past 20 years. Two problems that have occurred frequently are that the students can be poor at organising their schedules and setting deadlines, whilst at the same time we have moved towards marking schemes which are focused on process applied rather than product produced. These two factors have mandated that the students need to provide evidence that they are planning and following the process that has been set. To support this we have introduced a suite of custom support software.
Computer Tools for Academic Research
This document discusses computer tools for academic research. It aims to make computer use more effective for research tasks like downloading data, running regressions, and writing papers. The course covers programming principles, version control, data management beyond spreadsheets, modular Python programming, testing code, and numeric computing tools. It uses a sample research project on social networks and app adoption to illustrate these tools. The document compares the academic research cycle to software development and argues that following good programming practices can help optimize researchers' time.
Software Analytics - Achievements and Challenges
Tutorial presented at SPLASH/OOPSLA 2015 http://2015.splashcon.org/track/splash2015-tutorials#program
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
DheepthiResume
Dheepthi J.J. is a quality assurance engineer with over 6 years of experience. She currently works at Amazon and has previous experience working for Altimetrik, Cognizant, and Hexaware. Her technical skills include Java, Python, Selenium, Oracle, and C#. She has contributed to projects using agile methodologies and has experience analyzing requirements and designing solutions.
More Related Content
What's hot
Agile Languages for Rapid Prototyping
These slides were used to teach the above subject for the 3rd year undergrads of the Departement of Computer Engineering, University of Peradeniya in 2009, under IFS-PERADENIYA industry -university collaboration.
Comment soup with a pinch of types, served in a leaky bowl
Comment soup with a pinch of types, served in a leaky bowl
Talk by Pooja Rani and Manuel Leuenberger, PharoDays 2019
Training report
This document provides a project report for an online photo sharing and social networking service called IMAGINATE. It discusses the technologies used including Java, HTML, CSS, JavaScript, MySQL, and provides an overview of the different modules in the project including user and admin modules. It describes the project methodology which involved information gathering, system requirement analysis, and design. The major operations of the project allow users to register, view galleries and top rated photos, contact admin, and vote for good pictures.
How to write maintainable code - Peter Hilton - Codemotion Amsterdam 2017
The problem that new technology doesn’t fix is unmaintainable code. Clean code with good tests is essential, but not enough. This talk introduces techniques like getting better at naming, explaining code with tests, the few code comments you actually need, README-driven development and writing Minimum Viable Documentation. After the excitement of adopting new technology and software craftsmanship comes the horror of your next software maintenance project. As Jean-Paul Sartre said*, ‘Hell is other people’s code’. Whatever your level, your future happiness depends on maintainable code.
CS101- Introduction to Computing- Lecture 45
This lecture provides a review and wrap-up of the CS101 Introduction to Computing course. It summarizes key topics covered over the past 44 lectures such as programming methodology, readable code, algorithm design, testing and debugging. It reviews objectives of the course which were to build an appreciation of fundamental computing concepts, familiarize students with popular productivity software, and achieve beginner proficiency in web development. The lecture concludes by asking for student feedback on how well the course objectives were achieved.
Introduction to Agile Software Development & Python
These slides were used to teach the module "Introduction to Agile Software Development & Python" as a sub-section of the major course "Software Engineering" for the 3rd year undergraduates of the Department of Computer Engineering, University of Peradeniya in 2010.
PRG 421 version 10 Entire Course
This document outlines assignments for a Java programming course across 5 weeks. It includes assignments to write code for GUIs, containers, exceptions, files, applets, and databases. It provides examples and prompts students to design and implement programs that incorporate these Java concepts, including a fundraising tracking program due in Week 5. Students are to submit code and responses following an APA template.
Twelve practices of XP_Se lect5 btech
The document describes the twelve core practices of extreme programming (XP). It discusses each practice in 1-2 paragraphs, covering pair programming, refactoring, simple design, collective code ownership, continuous integration, on-site customer, small releases, 40-hour work week, coding standards, system metaphor, planning game, and testing (including unit and acceptance testing). The advantages include customer focus, incremental releases, and continuous testing/integration improving quality. Disadvantages include being suited for a single co-located team and not working as well without customer involvement or for large scalable systems.
An Ultimate Guide To Hire Python Developer
If you are looking for a python developer, it is not as easy as it sounds. There are many factors that come into play when hiring a developer. This guide will help you find the best python developer for your project.
https://www.hackerearth.com/recruit/resources/e-books/hire-python-developer/
Input, Processing and Output
This document provides an introduction to the Python programming language. It discusses that Python is an easy to learn, powerful, high-level and object-oriented programming language. It supports features like object-oriented programming, dynamic typing, functional programming, and scripting. The document also covers Python history, versions, applications, keywords, input/output/variables, and designing programs using flowcharts and pseudocode.
Jdj Foss Java Tools
This document discusses uncommon Java bugs and how free open source static analysis tools can help detect them. It provides examples of bugs like using the letter "l" instead of the number 1 in a long constant, checking for NaN equality, and null pointer exceptions. The document introduces tools like Jlint, FindBugs, PMD, and QJ-Pro that can find these kinds of bugs and describes how each tool detects bugs in code examples. It concludes that using static analysis tools can improve code quality by finding defects early.
Computer software specialists wikki verma
Wikki Verma Suggest Before opening an IT consultancy, I did my homework. I interviewed lifelong consultants. I read books. I even took personality tests to confirm that my psychological constitution matched the challenges I did face as an entrepreneur owning and operating my own business.
Introduction
This document provides an introduction to C# programming, including why it is an important and versatile language, job prospects for C# developers, and an overview of the software development process. Key points include:
- C# can be used to build a wide range of applications and is in high demand with over 100,000 job openings and a projected growth rate of 22% by 2029.
- The software development process involves analysis, design, implementation, testing, and deployment of applications in an iterative manner using approaches like Waterfall or Agile.
- Becoming proficient in C# provides opportunities for well-paying jobs at many companies in roles like software engineer, developer, and more. Understanding programming fundamentals
11 best practices_for_peer_code_review
White paper recommends 11 best practices for efficient peer code review:
1. Review no more than 200-400 lines of code at a time and take 60-90 minutes or less per review for optimal effectiveness.
2. Aim for an inspection rate of less than 300-500 LOC per hour and spend at least 5 minutes on each review.
3. Have authors annotate source code before review to eliminate most defects beforehand and improve efficiency.
4. Establish quantifiable goals, collect metrics, and refine processes over time to continuously improve results.
Empirical evaluation in 2020: how big, how beautiful?
The document discusses empirical evaluation standards in software engineering research. It notes that evaluation standards have become more rigorous over time, as seen in a comparison of papers from 2001 and 2018. Today's evaluations generally analyze more data, make better use of inferential statistics, but still underutilize qualitative methods and rarely involve developers. The document emphasizes the importance of high quality data and validation when mining software repositories, as these sources often contain imprecise and incomplete information that can bias results. It also stresses selecting a diverse set of projects for studies to improve generalizability.
Lecture 2
This lecture covers creating and structuring C# projects and applications in Visual Studio 2010. It discusses creating solutions and projects, the structure of a C# application including namespaces and classes, writing and running code, using variables and data types, commenting code, and debugging applications using breakpoints, stepping through code, and inspecting variables. The lecture emphasizes the importance of commenting code for future understanding and maintenance.
Stop fearing legacy code
It is time to fight the black holes in your software. Don't let legacy code dictate your work. Start learning and practicing dependency injection and refactoring. Become more agile.
Managing Inquiry-based Learning: Learning from experience
We have taught a suite of inquiry-based learning modules for the past 20 years. Two problems that have occurred frequently are that the students can be poor at organising their schedules and setting deadlines, whilst at the same time we have moved towards marking schemes which are focused on process applied rather than product produced. These two factors have mandated that the students need to provide evidence that they are planning and following the process that has been set. To support this we have introduced a suite of custom support software.
What's hot (18)
Comment soup with a pinch of types, served in a leaky bowl
Comment soup with a pinch of types, served in a leaky bowl
How to write maintainable code - Peter Hilton - Codemotion Amsterdam 2017
How to write maintainable code - Peter Hilton - Codemotion Amsterdam 2017
Introduction to Agile Software Development & Python
Introduction to Agile Software Development & Python
Empirical evaluation in 2020: how big, how beautiful?
Empirical evaluation in 2020: how big, how beautiful?
Managing Inquiry-based Learning: Learning from experience
Managing Inquiry-based Learning: Learning from experience
Similar to 01.intro
Computer Tools for Academic Research
This document discusses computer tools for academic research. It aims to make computer use more effective for research tasks like downloading data, running regressions, and writing papers. The course covers programming principles, version control, data management beyond spreadsheets, modular Python programming, testing code, and numeric computing tools. It uses a sample research project on social networks and app adoption to illustrate these tools. The document compares the academic research cycle to software development and argues that following good programming practices can help optimize researchers' time.
Software Analytics - Achievements and Challenges
Tutorial presented at SPLASH/OOPSLA 2015 http://2015.splashcon.org/track/splash2015-tutorials#program
Illustrated Code (ASE 2021)
Illustrated Code: Building Software in a Literate Way
Andreas Zeller, CISPA Helmholtz Center for Information Security
Notebooks – rich, interactive documents that join together code, documentation, and outputs – are all the rage with data scientists. But can they be used for actual software development? In this talk, I share experiences from authoring two interactive textbooks – fuzzingbook.org and debuggingbook.org – and show how notebooks not only serve for exploring and explaining code and data, but also how they can be used as software modules, integrating self-checking documentation, tests, and tutorials all in one place. The resulting software focuses on the essential, is well-documented, highly maintainable, easily extensible, and has a much higher shelf life than the "duct tape and wire” prototypes frequently found in research and beyond.
DheepthiResume
Dheepthi J.J. is a quality assurance engineer with over 6 years of experience. She currently works at Amazon and has previous experience working for Altimetrik, Cognizant, and Hexaware. Her technical skills include Java, Python, Selenium, Oracle, and C#. She has contributed to projects using agile methodologies and has experience analyzing requirements and designing solutions.
Nagacv
NagaRaju Addanki is a software developer with over 7 years of experience seeking new project opportunities. He has extensive experience developing web applications using Microsoft technologies like ASP.NET, C#, and SQL Server. Currently he works as a module lead at Value Labs in Hyderabad, India where he supports payroll projects and applications. His background includes developing academic, e-commerce, and database applications for clients.
System design for Web Application
The document provides guidance on designing a complex web application by breaking it into multiple microservices or applications. It recommends asking questions about team size, traffic patterns, priorities for speed vs stability, existing APIs or libraries, and programming languages. Based on the answers, it suggests appropriate frameworks, languages, data storage, testing/deployment processes, and server/container management options. The overall goal is to modularize the application, leverage existing tools when possible, and not overengineer parts of the design.
Brochure curriculum (1)
This document outlines a structured curriculum for tech professionals to accelerate their careers. It is split into an Intermediate section (37 weeks) and Advanced section (30 weeks). Both sections cover the same concepts in computer science fundamentals and system design through projects, with the Intermediate section adding 7 weeks on programming constructs. The curriculum is intended to provide thorough knowledge of core CS topics, specialization in backend/fullstack development, and proficiency in system design through hands-on learning and projects modeling real systems.
Agile Values, Principles and Practices
This presentation reviews the Agile Manifesto and shows how the practices should be in alignment with values and principles.
Nagacv
NagaRaju Addanki is a senior technical lead with over 8 years of experience developing web applications. He has extensive experience using Microsoft technologies like ASP.NET, C#, and SQL Server. Currently he works at Value Labs as a technical lead on payroll projects. He is seeking new project opportunities in software development.
Transferring Software Testing Tools to Practice
ACM SIGSOFT Webinar co-presented by Nikolai Tillmann (Microsoft), Judith Bishop (Microsoft Research), Pratap Lakshman (Microsoft), Tao Xie (University of Illinois at Urbana-Champaign) http://www.sigsoft.org/resources/webinars.html
Periodic Table of Agile Principles and Practices
Recently I fell by chance on the Periodic Table of the Elements... Long time no see... Remembering my physics lessons in University, I always loved that table. I remembered spending hours understanding the layout and admiring the beauty of its natural simplicity.
So I had the idea of trying the same layout, not the same approach since both are not comparable, really only the same layout for Agile Principles and Practices.
The result is in this presentation: The Periodic Table of Agile Principles and Practices:
Pair Programming Explained By Shrikant Vashishtha
Collaborative programming involves two programmers working side-by-side on design, coding, and testing of software. It transforms solitary work into a cooperative effort. Pair programming minimizes distractions, catches errors earlier, and promotes knowledge sharing, leading to increased productivity compared to individual work. While cultural and psychological challenges exist, distributed pair programming tools can enable effective collaboration even when programmers are in different locations.
Effective Collaborative Programming3@March 19th 2009
Collaborative programming, also known as pair programming, involves two programmers working side-by-side to design, code, and test software. It transforms solo work into a cooperative effort. The benefits include fewer distractions, fewer errors, knowledge sharing, and an active reviewer. While challenging due to cultural and psychological factors, distributed pair programming can be effective when teams are remote by using tools that enable screen and audio sharing.
Cs121 Unit Test
The document discusses the pros and cons of using open source software in projects. It notes that open source code comes with various licenses like GPL, BSD, and MIT that differ in how they can be used. While open source lacks perceived accountability, it actually has governance structures. The document aims to provide context on open source licensing and use within the scope of incorporating external code into a project. It addresses common concerns about open source like licensing complexity but clarifies the intent is to protect author rights, not hinder code use.
Software Analytics: Towards Software Mining that Matters (2014)
This document discusses software analytics and summarizes several related papers and projects. It introduces Software Analytics, which aims to enable software practitioners to perform data exploration and analysis to obtain useful insights. It then summarizes papers on techniques for performance debugging by mining stack traces, scalable code clone analysis, incident management for online services, and using games to teach programming.
Writting Better Software
The document provides advice for becoming a better programmer based on experience and theory. It discusses maintaining good code quality through principles like DRY (Don't Repeat Yourself), orthogonality, reversibility, prototyping, and domain-specific languages. Specific techniques mentioned include refactoring, testing, modularity, learning new skills regularly, and critically analyzing information to avoid hype. The goal is to produce good-enough software through an iterative process while fighting software entropy.
Software Analytics: Data Analytics for Software Engineering
This document summarizes a presentation on software analytics and its achievements and opportunities. It begins by noting how both how software and how it is built and operated are changing, with data becoming more pervasive and development more distributed. It then defines software analytics as enabling analysis of software data to obtain insights and make informed decisions. It outlines research topics covering different areas of the software domain throughout the development cycle. It describes target audiences of software practitioners and outputs of insightful and actionable information. Selected projects demonstrating software analytics are then summarized, including StackMine for performance debugging at scale, XIAO for scalable code clone analysis, and others.
Case study
This document provides a case study on a project created using open source technology. It discusses analyzing project goals and resources, evaluating open source options based on total cost of ownership, implementing a solution using LAMP stack, and lessons learned. The project was developed using Linux, Apache, MySQL, and PHP based on the needs of a low budget, ability to invest in internal skills, and reduce dependency on external trends. Key steps included preparing the Linux server, using version control and local testing, and engaging the open source community for support.
Cnpm bkdn
The document provides an introduction to software engineering and discusses the software development process, including project management. It describes various software development models like the waterfall model and iterative development. Key aspects of project management are also covered, such as feasibility studies, requirements definition, scheduling techniques, and the role of the project manager.
Software Development Standard Operating Procedure
This is a sample SOP document that we are using in our company which has helped us improve the quality of output immensely
Similar to 01.intro (20)
Effective Collaborative Programming3@March 19th 2009
Effective Collaborative Programming3@March 19th 2009
Software Analytics: Towards Software Mining that Matters (2014)
Software Analytics: Towards Software Mining that Matters (2014)
Software Analytics: Data Analytics for Software Engineering
Software Analytics: Data Analytics for Software Engineering
More from Philip Johnson
Kukui Cup 2012 Energy Data
This document presents a preliminary report on energy consumption data from buildings at the University of Hawaii (UH) and Hawaii Pacific University (HPU) during their 2012 Kukui Cup energy reduction competition. The data shows that buildings at UH generally saw an increase in energy use from August to October, while buildings at HPU remained flat. The competition appeared to temporarily flatten the rising trend at UH when participation was over 60%. Buildings with 100% participation at HPU saw up to a 20% reduction, while most buildings at both universities showed little impact from the competition.
Introduction to ICS 691: Software Engineering for the Smart Grid
This seminar provides an introduction to software engineering for the smart grid. It will be conducted as a graduate seminar with students leading discussions and presenting on research papers. The seminar topics will focus on areas related to smart grid software research. Assessments will include seminar preparation, presentation, and engagement as well as biweekly progress reports on an individual smart grid software project.
Kukui Cup 2012 Organizing Committee February Meeting
The February meeting of the Kukui Cup/UH 2012 Organizing Committee covered the following topics:
1. Introductions and feedback on past Kukui Cup events, noting things that were liked and could be improved.
2. A review of the 2011 t-shirts, swag, schedule, and point system to gather feedback for 2012.
3. A discussion of workshop reviews and promotional video production for the 2012 Kukui Cup.
4. Next steps including providing feedback over the summer and helping plan events in fall 2012.
How to plan a Kukui Cup
For those interested in planning their own Kukui Cup energy challenge, some of the issues they will need to consider.
Honors thesis overview: Katie Amberg-Johnson
The document discusses using molecular tweezers to investigate the fracture point of the σ54 core binding domain during transcription initiation. The experiment involves generating DNA handles, attaching them to the purified core binding domain protein, and then using molecular tweezers to apply force and simulate the "tugging" by the activator binding domain. This could reveal if the two subdomains of the core binding domain unfold separately or together under stress.
Introduction to Issue Driven Project Management
The document introduces issue-driven project management (IDPM), a simple approach for small group software projects. IDPM divides work into tasks represented as issues on an issue tracking system. Tasks are assigned as issues to individual team members and status is updated as tasks are started, completed, or new tasks identified. Daily stand-up meetings are used to assign new tasks, ensure forward progress, and quickly address any blockers or breakdowns.
Introduction to continuous integration
The document introduces continuous integration (CI), discussing its motivation, benefits, and how to implement it using the Hudson/Jenkins open source tool. CI ensures that code commits can be automatically built, tested and integrated to find issues early. The document recommends setting up a Jenkins server to regularly pull code from source control, run tests, and email developers on failures, improving the development workflow.
Introduction to WattDepot
A brief overview of WattDepot, a system for collection, storage, analysis, and visualization of energy data.
Introduction to Subversion and Google Project Hosting
This document introduces Subversion (SVN) and Google Project Hosting. It describes basic SVN concepts like repositories, working copies, commits, updates and revisions. It explains how SVN uses repository-wide revisions rather than file-based versions. Branches, tags and trunks are organized conventionally in an SVN repository. Google Project Hosting provides a free SVN server and issue tracker for open source projects.
Introduction to Version Control and Configuration Management
Version control systems like SVN aim to address three classic configuration management problems: the double maintenance problem of multiple copies needing separate updates, the shared data problem of developers accessing the same files, and the simultaneous update problem of file clobbering during concurrent edits. SVN improves on CVS by using a database backend instead of file versions, supporting repository-wide instead of file-based versions, and using directory-based tags and branches. Distributed version control systems like Git store a full code repository locally and support decentralized workflows without a central server.
A beginners guide to testing
Testing is important because software errors can have serious consequences like customer bank balances being inflated by $763 billion or radiation therapy machines overexposing patients. Testing helps verify that software meets its specifications and functions as intended. There are two main types of testing: static testing which analyzes source code without running programs, and dynamic testing which executes programs to look for errors. It is difficult to exhaustively test all possible inputs for non-trivial programs, so test cases must strategically sample a small percentage of inputs to uncover many defects. Both black box and white box testing methods aim to design effective test cases.
Introduction to automated quality assurance
This document discusses automated quality assurance tools and how they can be used to complement manual quality assurance techniques. It provides an overview of common automated QA tools like Checkstyle, PMD and FindBugs, describing their strengths and weaknesses. Checkstyle performs source code analysis to check for coding standard compliance and best practices. PMD also analyzes source code but focuses more on design-level issues. FindBugs analyzes bytecodes to find bugs, using data flow analysis. The goal in this class is to teach students to apply the right mix of automated and manual QA to build high quality systems efficiently.
Introduction to Software Build Technology
This document introduces build and packaging technologies, including Ant, Ivy, Maven and Make. It discusses the motivation for using build tools in modern software development which involves multiple developers, platforms and environments. It provides an overview of Ant, Make, Maven and Ivy, comparing their features and advantages. It also describes how to structure an Ant-based build system using the example robocode-pmj-dacruzer project.
Introduction to Software Review
The document discusses software review methods and optimal review practices. It describes different review methods from walkthroughs to inspections and their goals and attributes. Inspections are highlighted as the most formal review method, involving preparation, an orientation, planning, a review meeting, rework, and verification stages. The goals of technical reviews are also outlined, including improving quality and knowledge while minimizing costs.
Introduction to Robocode
This document introduces Robocode, an open-source robot simulation game. It is used to teach students Java programming skills through developing robots that can move, scan for others using radar, and fire guns, while gaining points for survival and hitting opponents. Students will download Robocode, run sample robot matches, and use Eclipse to develop and run their own robot by learning skills like movement, targeting, and firing to make their robot win matches against others.
Codings Standards
The document discusses coding standards and conventions for collaborative Java development. It outlines general principles like adhering to style and least astonishment. It also describes specific formatting, naming, documentation, and programming conventions like using meaningful names, commenting code, making fields private, and exception handling best practices. Automated tools like Checkstyle and Eclipse formatters can help enforce standards but may require configuration. Additional standards for the class are on the website.
Interactive Development Environments
An interactive development environment (IDE) is a software tool that aids in computer programming. Key features of an IDE include language-aware editing, project management, integrated compilation and debugging. While IDEs take more time to learn than basic text editors, they allow developers to work more efficiently on large software projects through features like code navigation, refactoring and testing. For these reasons, potential employers often expect job candidates to be skilled with IDEs like Eclipse rather than basic text editors.
Introduction to Intermediate Java
The document discusses modern Java constructs introduced after Java 5, including collections, generics, autoboxing, enumerated types, annotations, and how to properly design classes to work with collections. It provides code examples and best practices for using these constructs and highlights resources like Java in a Nutshell and Effective Java for further reading.
Professional Persona
This document discusses the components that make up a professional persona, which is an online presence that potential employers can view. It identifies the key elements as: 1) a professional portfolio website, 2) an online engineering blog, 3) participation in open source projects, 4) involvement in professional social networks, and 5) engagement with technical societies and activities. The goal is to help students establish an attractive online presence that showcases their skills and accomplishments to future employers.
iHale Milestone 2 Kickoff
This document provides an overview of the TeamHawaii Solar Decathlon software system interface milestone 2 kickoff. The goal is to implement monitoring and control for five house systems by April 2011 to explore the design space of these capabilities. It discusses what makes a house "smart" through integration, data collection, and control. The system architecture collects data from house systems through various interfaces to a central iHale API and repository for monitoring and sending control commands. Details are provided on assumptions for milestone 2 capabilities for each system and issues to consider regarding monitoring and control capabilities.
More from Philip Johnson (20)
Introduction to ICS 691: Software Engineering for the Smart Grid
Introduction to ICS 691: Software Engineering for the Smart Grid
Kukui Cup 2012 Organizing Committee February Meeting
Kukui Cup 2012 Organizing Committee February Meeting
Introduction to Subversion and Google Project Hosting
Introduction to Subversion and Google Project Hosting
Introduction to Version Control and Configuration Management
Introduction to Version Control and Configuration Management
Recently uploaded
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentationsGenerative AI Deep Dive: Advancing from Proof of Concept to Production
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
20 Comprehensive Checklist of Designing and Developing a Website
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Recently uploaded (20)
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Generative AI Deep Dive: Advancing from Proof of Concept to Production
Generative AI Deep Dive: Advancing from Proof of Concept to Production
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
Monitoring Java Application Security with JDK Tools and JFR Events
Monitoring Java Application Security with JDK Tools and JFR Events
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
01.intro
- 1. ICS 314 and 613: Software Engineering Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii Honolulu HI 96822
- 13. Course Architecture Basic Java Capabilities IDE Coding Standards Software Review Automated Build Testing Config. Man. Agile Development Practices Software Measurement Intermediate Java Automated QA Case Study: WebApp Development Concurrency Performance Analysis