Module 2 Lecture Summary

The future is faster than you think 
Summary

Technology is transforming business models and accelerating rapidly. We are living in a time where innovation is more possible than ever thanks to technology.

1. Computation Abundance 

We are living in a time where computers are cheaper but are faster than ever before. Over the last 50 years transistors have doubled every 12 to 18 months. With all the computation abundance leads to faster networks and sensors, synthetic biology, robotics, 3D printing to name a few. 

 2. Time saved

 We have more time to focus on solving problems and being innovative. Before humans needed to spend a lot of time doing other things to survive such as collecting food. Through technology and innovation, we need to spend less time on those things, and we can focus our energy on more meaningful things. 

3. Capital Abundance

There is an abundance of capital which can be used for crowdfunding, venture funding, etc. Investing will accelerate technology. 

4. Demonetization

Somethings are getting cheaper such as internet tech startups. A startup cost about $5 million in 2000, $500,000 in 2005, $50,000 in 2009 and $5,000 in 2011.

5. Communication is cheaper

In the next few years 4.2 billion new people will have access to the internet.

6. Geniuses 

In the years to come we will have more brain power. Companies are working on neocortex connections with computers to create a brain computer interface. 

7. Increase Longevity

Using technology to add 10,20 or 30 more years to a human life spam. Companies are researching synthetic medicines, new organs, mRNA, vaccines, Gene Therapy to help humans live longer. 

Today more than ever before businesses could solve the world’s biggest problems. 

 

The Future of Software Engineering: Key Emerging Trends in 2024
Summary

 

1. Software Engineering:

Uses the fundamentals of engineering principles to test, design, develop, and maintain software products. The goal is to develop software systems that are high-performance, efficient, reliable, and easy to maintenance. 

2. What is the future of the software engineering industry?

It will continue to grow, innovate, and evolve. It will also become more tailored to specific industries.

3. The Past, Present and Future of Standards in Software Engineering

Software Engineering has a set of standards and best practices, but they change over time. Some of the past standards and practices included Waterfall Model, Capability Maturity model and Rational Unified Process. Present standards and practices include Agile Methodologies, Continuous Delivery and Devops. Future may include Al Ethical Standards, Energy Efficiency Computing, and Industry-Specific Standards.

4. Challenges

a. Time to Market

The time it takes for the software product to be produced and made available.

b. Technical Debt

Additional work needed to maintain and update software or systems due to bad or inefficient application development practices and initial architectural designs.

c. Privacy Concerns

Sensitive data is collected from users, and they may not want to share that data. Laws and regulations create more work.

5. Talent Shortage

There is a limited supply of highly skilled software developers and high demand.

6. Five Trends that Shape Software Development in 2024

          a. Low-Code Development opens new Opportunities

Platforms let developers make scalable, extensible, and secure SaaS applications faster and efficient.

b. AI Tech

Day to day work may be accelerated using AI.

c. Greater resilience with digital immunity

Companies need to protect themselves from cybercrime.

d. Cloud Computing will Transform into Hybrid Computing

 Large companies have embraced cloud computing technology. Cloud Computing has benefited such as saving money, improved security, and greater scalability.

7. Future of Software Engineering Forecast and Statistics

Global demand for software engineers will continue to grow. The average annual salary for software engineers in the USA is approximately $86,000. The market for software engineers will grow from $47.3 billion to $89.3 billion by 2030.

8. Demand for skilled software engineers

Lay offs are due to general market slowdowns. A 10% decline for software engineers from 2021 to 2031, is predicted. However, more than 9,600 new software engineering jobs are created every year. The top demand for programing languages is Python, C and Java.

9. Will Software Engineers be Needed in 2030?

The continued expansion of Internet of Things, cloud computing, and cyber security will drive the need for software developers.

10. Will AI replace Software Developers?

No, AI cannot replace the creativity and critical thinking skills that Software Developers have.

 

Intro to Project Management

Summary

1.     What is a project?

a.     A temporary endeavor undertaken to create a unique product, service or result

b.     A project needs 3 things:

                                                   i.     Time- has a start and end date

                                                 ii.     Goal- the product, service or result = output

1.     Output + work = scope

                                               iii.     Cost- resources needed

c.     Projects are complex tasks

2.     Triggers for Projects

a.     Market needs

                                                   i.     Keep up with competition

                                                 ii.     Develop new product

b.     Business Model

                                                   i.     Cost reduction

                                                 ii.     Process increases

                                               iii.     Revenue

c.     Technological Advancement

                                                   i.     Automation

d.     Legal Requirements

                                                   i.     Social needs

                                                 ii.     Ecological considerations

3.     Once a specific need/requirement is needed a project comes to be/Project selection

a.     Prioritizing

                                                   i.     Project proposal

                                                 ii.     Project owner

                                               iii.     Management

b.     Urgency

c.     Management chooses several project

                                                   i.     Project portfolio

4.     The Project Management

a.     Beginning, project, board of directors, Project manager and end.

b.     The project manager is the CEO of the project

                                                   i.     Accountable for the project

1.     Time

2.     Cost

3.     Result

                                                 ii.     Project manager must set realistic goals

1.     Assess

2.     Negotiates

3.     Discusses

4.     Adjusts

                                               iii.     Project manager commit to deliver

1.     Must have full control and visibility of project

5.     Project Managers

a.     Skills

                                                   i.     Professional

                                                 ii.     Ethics

                                               iii.     Morals

                                                iv.     Credibility

b.     Attitude

 

 

 


Comments

Post a Comment

Popular posts from this blog

CST438 Software Engineering: Week 8 (Final week)

 One of the most important things I learned is that software engineering is about much more than just writing code. While coding is a big part, there's a strong emphasis on documentation, understanding client needs, and getting continuous feedback. It’s about designing systems so others can easily improve them and applying principles like "low coupling and high cohesion" to keep things modular and maintainable.      Another key lesson was understanding the entire development process from end to end. This was the first time I worked with both the front end and back end together, fully grasping the HTTP protocol (including how methods like POST work), how JSON is used, and how the front end communicates with the back end. Seeing how everything fits from database interactions to deploying the app online—gave me a fascinating glimpse into the full workflow and a lot of practical experience.      Another important lesson was learning how to work as part of ...
Read more

CST438 Software Engineering: Week 1

What did you expect a course in Software Engineering would cover? I expected it to cover how to build applications from the ground up and the design behind application development. I thought we would look at other things we’ve been learning in this program, like database management, front end development, and back end work, and then put it all together into one complete project. After completing week 1, how has your opinion changed? Well, I never really thought much about keeping an application’s design maintainable for future improvements or changes. There is a lot more that goes into software engineering than just simple programming. It is  about planning ahead, documenting your work, checking for errors, and testing properly to avoid issues later. I’ve also realized software engineering looks at the big picture it is not just about coding and design but about how software impacts people and how teams work together to build it. Developers need to stay motivated, think critical...
Read more

CST370 Week 5

Hello everyone,  This week we studied binary‑tree traversals preorder, inorder, and postorder but I kept mixing them up. I finally got it when I attended TA office hours, and it clicked. Walking through Quick Sort step by step helped me see how the Decrease and Conquer approach works by breaking problems into smaller chunks. Then we looked at Kahn’s algorithm, and watching it remove nodes with no incoming edges reminded me of picking a pivot in Quick Sort. Seeing these patterns repeat helped me realize that many algorithms work by simplifying things piece by piece. 
Read more