Chapter 6 Human Aspects of Software Engineering Slide

  • Slides: 15
Download presentation
Chapter 6 ■ Human Aspects of Software Engineering Slide Set to accompany Software Engineering:

Chapter 6 ■ Human Aspects of Software Engineering Slide Set to accompany Software Engineering: A Practitioner’s Approach, 8/e by Roger S. Pressman and Bruce R. Maxim Slides copyright © 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman For non-profit educational use only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach, 8/e. Any other reproduction or use is prohibited without the express written permission of the author. All copyright information MUST appear if these slides are posted on a website for student use. These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. 1

Traits of Successful Software Engineers ■ ■ ■ ■ Sense of individual responsibility Acutely

Traits of Successful Software Engineers ■ ■ ■ ■ Sense of individual responsibility Acutely aware of the needs of team members and stakeholders Brutally honest about design flaws and offers constructive criticism Resilient under pressure Heightened sense of fairness Attention to detail Pragmatic These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. ﺍﻟﺼﻔﺎﺕ ﻣﻦ ﻣﻬﻨﺪﺳﻲ ﺍﻟﺒﺮﻣﺠﻴﺎﺕ ﺍﻟﻨﺎﺟﺢ • ﺍﻟﺸﻌﻮﺭ ﺑﺎﻟﻤﺴﺆﻮﻟﻴﺔ ﺍﻟﻔﺮﺩﻳﺔ ﺗﻌﻲ ﺗﻤﺎﻣﺎ ﻻﺣﺘﻴﺎﺟﺎﺕ ﺃﻌﻀﺎﺀ ﺍﻟﻔﺮﻳﻖ ﻭﺃﺼﺤﺎﺏ ﺍﻟﻤﺼﻠﺤﺔ ﺻﺎﺩﻗﺔ ﻭﺣﺸﻴﺔ ﻋﻦ ، ﻋﻴﻮﺏ ﻓﻲ ﺍﻟﺘﺼﻤﻴﻢ ﻭﻳﻘﺪﻡ ﺍﻟﻨﻘﺪ ﺍﻟﺒﻨﺎﺀ ﻣﺮﻭﻧﺔ ﺗﺤﺖ ﺿﻐﻂ ﺗﺰﺍﻳﺪ ﺍﻟﺸﻌﻮﺭ ﺍﻹﻧﺼﺎﻑ ﺍﻻﻫﺘﻤﺎﻡ ﺑﺎﻟﺘﻔﺎﺻﻴﻞ ﻭﺍﻗﻌﻴﺔ • • • 2

Behavioral Model for Software Engineering These slides are designed to accompany Software Engineering: A

Behavioral Model for Software Engineering These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. ﺍﻟﻨﻤﻮﺫﺝ ﺍﻟﺴﻠﻮﻛﻲ ﻟﻠﻬﻨﺪﺳﺔ ﺍﻟﺒﺮﻣﺠﻴﺎﺕ 3

Boundary Spanning Team Roles ■ ■ ■ Ambassador – represents team to outside constituencies

Boundary Spanning Team Roles ■ ■ ■ Ambassador – represents team to outside constituencies Scout – crosses team boundaries to collect information Guard – protects access to team work products Sentry – controls information sent by stakeholders Coordinator – communicates across the team and organization ﺍﻟﺤﺪﻭﺩ ﺍﻟﻤﻤﺘﺪﺓ؟ ﺃﺪﻭﺍﺭ ﻓﺮﻳﻖ • ﻳﻤﺜﻞ ﺍﻟﻔﺮﻳﻖ ﺇﻟﻰ ﺍﻟﺪﻭﺍﺋﺮ - ﺍﻟﺴﻔﻴﺮ ﺍﻟﺨﺎﺭﺟﻴﺔ ﻳﻌﺒﺮ ﺍﻟﺤﺪﻭﺩ ﻓﺮﻳﻖ ﻟﺠﻤﻊ - ﺍﻟﻜﺸﻔﻴﺔ ﺍﻟﻤﻌﻠﻮﻣﺎﺕ ﻳﺤﻤﻲ ﺍﻟﺤﺼﻮﻝ ﻋﻠﻰ - ﺣﺎﺭﺱ ﻣﻨﺘﺠﺎﺕ ﻓﺮﻳﻖ ﺍﻟﻌﻤﻞ ﻣﻌﻠﻮﻣﺎﺕ ﺍﻟﻀﻮﺍﺑﻂ ﺍﻟﺘﻲ ﺑﻌﺚ ﺑﻬﺎ ﺧﻔﻴﺮ - ﺃﺼﺤﺎﺏ ﺍﻟﻤﺼﻠﺤﺔ ﺍﻟﺘﻮﺍﺻﻞ ﻋﺒﺮ ﻓﺮﻳﻖ - ﻣﻨﺴﻖ ﻭﺍﻟﺘﻨﻈﻴﻢ These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. • • 4

Effective Software Team ﻓﻌﺎﻟﺔ ﺳﻤﺎﺕ ﻓﺮﻳﻖ ﺍﻟﺒﺮﻣﺠﻴﺎﺕ Attributes ■ ■ ■ Sense of purpose

Effective Software Team ﻓﻌﺎﻟﺔ ﺳﻤﺎﺕ ﻓﺮﻳﻖ ﺍﻟﺒﺮﻣﺠﻴﺎﺕ Attributes ■ ■ ■ Sense of purpose Sense of involvement Sense of trust Sense of improvement Diversity of team member skill sets ﺍﻟﺸﻌﻮﺭ ﺑﺎﻟﻬﺪﻑ ﺍﻟﺸﻌﻮﺭ ﻣﺸﺎﺭﻛﺔ ﺍﻟﺸﻌﻮﺭ ﺑﺎﻟﺜﻘﺔ ﺍﻟﺸﻌﻮﺭ ﺗﺤﺴﻴﻦ ﺗﻨﻮﻉ ﺍﻟﻤﻬﺎﺭﺍﺕ ﻋﻀﻮ ﻓﻲ ﺍﻟﻔﺮﻳﻖ These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. • • • 5

Factors Affecting Team Structure The following factors must be considered when selecting a software

Factors Affecting Team Structure The following factors must be considered when selecting a software project team structure. . . ■ ■ ■ ■ ﺍﻟﻌﻮﺍﻣﻞ ﺍﻟﻤﺆﺜﺮﺓ؟ ﻫﻴﻜﻞ ﺍﻟﻔﺮﻳﻖ ﻳﺠﺐ ﺍﻟﻨﻈﺮ ﻓﻲ ﺍﻟﻌﻮﺍﻣﻞ ﺍﻟﺘﺎﻟﻴﺔ ﻋﻨﺪ ﺍﺧﺘﻴﺎﺭ ﺍﻟﺒﺮﺍﻣﺞ ﻫﻴﻜﻞ . . . ﻓﺮﻳﻖ ﺍﻟﻤﺸﺮﻭﻉ the difficulty of the problem to be solved ﺻﻌﻮﺑﺔ ﺍﻟﻤﺸﻜﻠﺔ ﺍﻟﺘﻲ ﻳﺘﻌﻴﻦ ﺣﻠﻬﺎ the size of the resultant program(s) in lines of code ﺣﺠﻢ ﺍﻟﺒﺮﻧﺎﻣﺞ ﺍﻟﻨﺎﺗﺞ )ﻕ( ﻓﻲ ﺍﻷﺴﻄﺮ or function points ﻣﻦ ﺍﻟﺘﻌﻠﻴﻤﺎﺕ ﺍﻟﺒﺮﻣﺠﻴﺔ ﺃﻮ ﻭﻇﻴﻔﺔ ﻧﻘﻄﺔ the time that the team will stay together (team ﻓﻲ ﺍﻟﻮﻗﺖ ﺍﻟﺬﻱ ﺳﻴﻘﻮﻡ ﺍﻟﻔﺮﻳﻖ ﺍﻟﺒﻘﺎﺀ ﻣﻌﺎ lifetime) the degree to which the problem can be modularized ( )ﻓﺮﻳﻖ ﻣﺪﻯ ﺍﻟﺤﻴﺎﺓ the required quality and reliability of the system to be ﺍﻟﺪﺭﺟﺔ ﺍﻟﺘﻲ ﻳﻤﻜﻦ ﻣﺠﺰﺃ ﺍﻟﻤﺸﻜﻠﺔ built ﺍﻟﺠﻮﺩﺓ ﺍﻟﻤﻄﻠﻮﺑﺔ ﻭﻣﻮﺛﻮﻗﻴﺔ ﺍﻟﻨﻈﺎﻡ ﺳﻴﺘﻢ the rigidity of the delivery date ﺑﻨﺎﺅﻬﺎ the degree of sociability (communication) required ﺻﻼﺑﺔ ﻣﻦ ﺗﺎﺭﻳﺦ ﺍﻟﺘﺴﻠﻴﻢ for the project § § § § ﺩﺭﺟﺔ ﻣﺆﺎﻧﺴﺔ )ﺍﻻﺗﺼﺎﻻﺕ( ﺍﻟﻼﺯﻣﺔ ﻟﻠﻤﺸﺮﻭﻉ These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 8/e (Mc. Graw-Hill, 2014) Slides copyright 2014 by Roger Pressman. 7