SlideShare a Scribd company logo
Software Engineering
By
Mr. Shais Saleem
Lecturer: Department of IT
Lecture #5
Reference books
2
CHAPTER 5
Software engineering lecture NO 5 by shais
Agenda
Cont..
Cont..
Characteristics of a Software Engineer
• To be a successful software engineer, technical
skills are essential—but human traits are just as
important.
• Technical Responsibilities
• Understand problems
• Design effective solutions
• Build and test software
• Use tools and manage change
• Communicate with stakeholders
Traits of an Effective Software Engineer
(Based on Erasmus [Era09])
• Individual Responsibility
• Delivers on promises
• Takes initiative to get the job done
• Stays committed to successful outcomes
• Acute Awareness
• Understands team and stakeholder needs
• Adapts behavior to the work environment
• Cares about others' perspectives
• Brutal Honesty
• Gives honest feedback (even if it's critical)
• Avoids lying about project status or product quality
• Stays truthful and realistic
Traits of an Effective Software Engineer
(Based on Erasmus [Era09])
• Resilience Under Pressure
• Handles stress well (e.g., changing requirements, tight deadlines)
• Performs consistently despite challenges
• Keeps calm and focused
• Fairness
• Shares credit with the team
• Avoids selfish behavior and conflicts of interest
• Supports others instead of sabotaging
• Attention to Detail
• Notices important aspects without being a perfectionist
• Makes technical decisions based on performance, cost, and quality
• Strives for high-quality outcomes
• Pragmatism
• Is flexible and practical
• Follows good practices, but adapts when needed
• Understands that one size doesn’t fit all in software engineering
5.1 Characteristics of a Software Engineer
Cont..
Cont..
5.2 The Psychology of Software
Engineering
• The layered behavioral model proposed by Bill Curtis
and Diane Walz in their 1990 paper presents software
development as a complex, multi-layered human
activity. Each layer in this model represents a level of
behavioral influence, from the individual developer up
to the broader organizational context.
• 1. Individual Layer.
• This is the core layer where each developer's
knowledge, experience, and personal attributes
directly impact software quality and productivity.
• 2. Team Layer
Even if individuals are highly skilled, poor
teamwork can lead to failure. This layer
emphasizes that team performance is not just
the sum of individual skills—it’s about how well
the team functions as a unit.
• 3. Project Layer
This layer deals with the organizational
mechanisms that manage teams, ensuring that
work is progressing toward defined goals
efficiently.
• 4. Organizational Layer
At this level, company-wide behavior and decisions affect
every project. For example, a company with a rigid
hierarchy may stifle innovation, while one that values
continuous learning might promote long-term success.
• 5. Business Milieu (Environment)
This outermost layer represents the broader economic
and societal context in which the company operates. It
sets the outer constraints that influence all internal layers.
5.3 The Software Team
20
The end
Thank you

More Related Content

PDF
what makes a great software engineer?
DOCX
reserach review 1 what makes great software engineer.docx
PDF
Characteristics of Excellent Software Engineers, by Lee Bob Black
PDF
Chapter 1 Introduction to Software Engineering and Process Models.pdf
PPTX
Quality and productivity factors
PPT
Software Testing and Quality Management Subject
PPTX
Pressman_Pressman_SoftwareEngineeringPA_9e_Ch005_PPT.pptx
PPTX
CSE_2014 SE MODULE 1 V.10.pptx
what makes a great software engineer?
reserach review 1 what makes great software engineer.docx
Characteristics of Excellent Software Engineers, by Lee Bob Black
Chapter 1 Introduction to Software Engineering and Process Models.pdf
Quality and productivity factors
Software Testing and Quality Management Subject
Pressman_Pressman_SoftwareEngineeringPA_9e_Ch005_PPT.pptx
CSE_2014 SE MODULE 1 V.10.pptx

Similar to Software engineering lecture NO 5 by shais (20)

PPTX
CSE_2014 SE MODULE 1 V.10 (2).pptx
PPTX
LEC 2asasasasasasasasasasasasasasasasa.pptx
PPTX
Unit 1 OOSE
PPT
software engineering aktu unit 1 lecture 1 Lecture1.ppt
PPT
Lecture1 software engineering
PPT
Introduction to Software Engineering Lecture 1
PPTX
Software Engineering
PDF
The Nature of Software and Software Engineering ppt.pdf
PPSX
Scope of software engineering
PPT
Chapter1 Advanced Software Engineering overview
PPT
What is Software Engineering?
PPT
Introduction Software and Software Engineering
PPTX
Unit 1 Software Engineering and Development Models .pptx
PDF
1914551054_Final-Pass.pdf
PPTX
PPTX
aswjkdwelhjdfshlfjkhewljhfljawerhwjarhwjkahrjar
PPTX
Conventional and Object Oriented Software Engineering
PPTX
Lect3 conventional vs modern spm
PPTX
The Introduction to Software Engineering
PDF
Introduction_SE_Modifiedsoftware engineering.pdf
CSE_2014 SE MODULE 1 V.10 (2).pptx
LEC 2asasasasasasasasasasasasasasasasa.pptx
Unit 1 OOSE
software engineering aktu unit 1 lecture 1 Lecture1.ppt
Lecture1 software engineering
Introduction to Software Engineering Lecture 1
Software Engineering
The Nature of Software and Software Engineering ppt.pdf
Scope of software engineering
Chapter1 Advanced Software Engineering overview
What is Software Engineering?
Introduction Software and Software Engineering
Unit 1 Software Engineering and Development Models .pptx
1914551054_Final-Pass.pdf
aswjkdwelhjdfshlfjkhewljhfljawerhwjarhwjkahrjar
Conventional and Object Oriented Software Engineering
Lect3 conventional vs modern spm
The Introduction to Software Engineering
Introduction_SE_Modifiedsoftware engineering.pdf
Ad

Recently uploaded (20)

PPTX
202450812 BayCHI UCSC-SV 20250812 v17.pptx
PPTX
master seminar digital applications in india
PDF
Anesthesia in Laparoscopic Surgery in India
PDF
O5-L3 Freight Transport Ops (International) V1.pdf
PDF
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
PPTX
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
PPTX
Microbial diseases, their pathogenesis and prophylaxis
PDF
A GUIDE TO GENETICS FOR UNDERGRADUATE MEDICAL STUDENTS
PPTX
human mycosis Human fungal infections are called human mycosis..pptx
PPTX
Pharmacology of Heart Failure /Pharmacotherapy of CHF
PDF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
PDF
Supply Chain Operations Speaking Notes -ICLT Program
PDF
Computing-Curriculum for Schools in Ghana
PDF
OBE - B.A.(HON'S) IN INTERIOR ARCHITECTURE -Ar.MOHIUDDIN.pdf
PPTX
Pharma ospi slides which help in ospi learning
PPTX
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
PDF
Module 4: Burden of Disease Tutorial Slides S2 2025
PPTX
GDM (1) (1).pptx small presentation for students
PPTX
Cell Types and Its function , kingdom of life
PDF
01-Introduction-to-Information-Management.pdf
202450812 BayCHI UCSC-SV 20250812 v17.pptx
master seminar digital applications in india
Anesthesia in Laparoscopic Surgery in India
O5-L3 Freight Transport Ops (International) V1.pdf
ANTIBIOTICS.pptx.pdf………………… xxxxxxxxxxxxx
school management -TNTEU- B.Ed., Semester II Unit 1.pptx
Microbial diseases, their pathogenesis and prophylaxis
A GUIDE TO GENETICS FOR UNDERGRADUATE MEDICAL STUDENTS
human mycosis Human fungal infections are called human mycosis..pptx
Pharmacology of Heart Failure /Pharmacotherapy of CHF
grade 11-chemistry_fetena_net_5883.pdf teacher guide for all student
Supply Chain Operations Speaking Notes -ICLT Program
Computing-Curriculum for Schools in Ghana
OBE - B.A.(HON'S) IN INTERIOR ARCHITECTURE -Ar.MOHIUDDIN.pdf
Pharma ospi slides which help in ospi learning
Introduction-to-Literarature-and-Literary-Studies-week-Prelim-coverage.pptx
Module 4: Burden of Disease Tutorial Slides S2 2025
GDM (1) (1).pptx small presentation for students
Cell Types and Its function , kingdom of life
01-Introduction-to-Information-Management.pdf
Ad

Software engineering lecture NO 5 by shais

  • 1. Software Engineering By Mr. Shais Saleem Lecturer: Department of IT Lecture #5
  • 8. Characteristics of a Software Engineer • To be a successful software engineer, technical skills are essential—but human traits are just as important. • Technical Responsibilities • Understand problems • Design effective solutions • Build and test software • Use tools and manage change • Communicate with stakeholders
  • 9. Traits of an Effective Software Engineer (Based on Erasmus [Era09]) • Individual Responsibility • Delivers on promises • Takes initiative to get the job done • Stays committed to successful outcomes • Acute Awareness • Understands team and stakeholder needs • Adapts behavior to the work environment • Cares about others' perspectives • Brutal Honesty • Gives honest feedback (even if it's critical) • Avoids lying about project status or product quality • Stays truthful and realistic
  • 10. Traits of an Effective Software Engineer (Based on Erasmus [Era09]) • Resilience Under Pressure • Handles stress well (e.g., changing requirements, tight deadlines) • Performs consistently despite challenges • Keeps calm and focused • Fairness • Shares credit with the team • Avoids selfish behavior and conflicts of interest • Supports others instead of sabotaging • Attention to Detail • Notices important aspects without being a perfectionist • Makes technical decisions based on performance, cost, and quality • Strives for high-quality outcomes • Pragmatism • Is flexible and practical • Follows good practices, but adapts when needed • Understands that one size doesn’t fit all in software engineering
  • 11. 5.1 Characteristics of a Software Engineer
  • 14. 5.2 The Psychology of Software Engineering
  • 15. • The layered behavioral model proposed by Bill Curtis and Diane Walz in their 1990 paper presents software development as a complex, multi-layered human activity. Each layer in this model represents a level of behavioral influence, from the individual developer up to the broader organizational context. • 1. Individual Layer. • This is the core layer where each developer's knowledge, experience, and personal attributes directly impact software quality and productivity.
  • 16. • 2. Team Layer Even if individuals are highly skilled, poor teamwork can lead to failure. This layer emphasizes that team performance is not just the sum of individual skills—it’s about how well the team functions as a unit.
  • 17. • 3. Project Layer This layer deals with the organizational mechanisms that manage teams, ensuring that work is progressing toward defined goals efficiently.
  • 18. • 4. Organizational Layer At this level, company-wide behavior and decisions affect every project. For example, a company with a rigid hierarchy may stifle innovation, while one that values continuous learning might promote long-term success. • 5. Business Milieu (Environment) This outermost layer represents the broader economic and societal context in which the company operates. It sets the outer constraints that influence all internal layers.

Editor's Notes

  • #14: Bill Curtis and Diane Walz's Layered Behavioral Model in simple words, with examples for each layer. This model shows that software development isn't just about writing code—it's influenced by many human and organizational factors, from the developer to the entire business environment. 1. Individual Layer – The Developer Focus: The personal skills, mindset, and motivation of each developer. In simple words: This is about the developer themselves—their knowledge, how they think, solve problems, and how motivated they are. Example: Imagine Sarah, a programmer. She understands the task well and knows how to solve it using her coding skills. But if she’s not motivated or is tired, she might not do her best work. Her personal effort and skills directly affect the quality of the software. 2. Team Layer – The Group of Developers Focus: How developers work together as a team. In simple words: Even if every developer is talented, the project won’t succeed unless they communicate well, share tasks properly, and support each other. Example: Sarah is working with 3 other developers. If they don’t talk regularly, don’t understand each other’s work, or argue too much, their software might have bugs or delays—even though all of them are good individually. 3. Project Layer – Management and Planning Focus: How the project is organized and led. In simple words: This is about planning, deadlines, leadership, and solving team issues. A good project manager helps everyone stay on track and work smoothly. Example: The manager sets a clear schedule, assigns tasks properly, and resolves conflicts between team members. If the project is mismanaged—like unclear goals or unrealistic deadlines—even a good team can struggle. 4. Organizational Layer – The Company’s Role Focus: The company’s policies, culture, and resources. In simple words: This is about the company's rules, work environment, tools, training, and overall support for software development. Example: If Sarah’s company doesn’t give her a powerful computer, proper training, or if they punish mistakes harshly, she might feel frustrated or stuck. On the other hand, a supportive environment boosts her productivity. 5. Business Milieu (Environment) – The Outside World Focus: External pressures like the market, laws, and customers. In simple words: This is about outside forces that affect the company, like competitors, government rules, the economy, and customer needs. Example: If a competitor launches a new app, Sarah’s company might rush to release their version. Or if new privacy laws are passed, the software must be updated to stay legal. Summary Example: Let’s say a team is building a mobile app. At the individual layer, each developer must be skilled and motivated. At the team layer, they must communicate and coordinate well. At the project layer, the manager must plan the tasks and timelines. At the organizational layer, the company must provide resources and a good work culture. At the business milieu, the company must respond to competitors, laws, and customer expectations.