You are on page 1of 62

Introduction: Contexts

1.Teams and teamwork:


• What is a team?
• Stages of team development.
• Characteristics of effective team
• Team process guidelines.
2.Project management:
• Time management.
• Cost management

1
Introduction: Contexts
3.Ethical and legal issues:
• Ethical issues:
- Definition of ethics.
- Types of ethical systems.
- IEEE code of ethics.
• Legal issues:
- Intellectual property.
- Patent.
- Copyrights.
- Whistleblower.

2
Outline of the presentation
• Teams&Teamwork:
• What’s a team?
• Stages of team development
• Characteristics of effective team
• Team process guidelines
• Project Mangment:
• Time management
• Tool of tema mangment
• Cost management
• Example of cost management

3
Outline of the presentation
• Ethical and legal issues:

• Ethics

• Legal

4
What is a team?
• A small groub of people with complemntary skills.(1)

• Who have some common performance objective.(2)

• For which they hold themselves mutually accountable.(1)

5
Why teamwork is important?
• Engineers generally work on very large project.(2)

• A good team effort is neded to complete the project.(1)

• Even if your individual skills are excellent, you will be unable to


complete the project successfully without the assistance of
team work.(2)

6
Stages of team development
Team development has five main stages:
1. Forming

2. Storming

3. Norming

4. Performing

5. Adjourning
7
1st stage of team development
1. Forming:

 Is the foundation of the team.(1)

 Where you must ensure that team members' skills complement one another.(2)

 Following a procedure.(1)

8
Forming Example

9
2nd stage of team development and
teamwork
2.Storming:

 Storming is associated with achieving common goals and objectives.(1)

 To ensure common goals, a team discussion should be formed.(2)

 At this point, everyone on the team has agreed on "What to do."(1)

10
Storming Example

11
3rd stage of team development and
teamwork
3.Norming:
 The team decides how all team members will be held accountable.(1)

 They also determine how everyone will be assessed.(2)

 It means that a procedure has been established to ensure team accountability.


(1)

12
Norming Example

13
4th stage of team development and
teamwork
4.Performing:

 The actual execution of the assigned tasks is referred to as performing.(2)

 Which were agreed upon during the storming phase.(1)

 Team members must ensure that all methods and evaluations are followed
when performing their tasks.(2)

14
5th stage of team development and
teamwork
5.Adjourning:

 This is the final stage of team development.(1)

 When the project is completed and the team is disbanded.(2)

15
Characteristics of effective team
• Choose team members based on their abilities
• determine and agree on goals
• specify how the team will make decisions
• decide on team roles
• assign responsibilities and tasks
• hold efficient meetings to monitor progress
• spend a significant amount of time discussing progress

16
Team process guidelines
• Attend all meetings and arrive on time.(1)
• Arrive prepared.(2)
• Complete assignments on time.(1)
• Constructively criticize ideas rather than people.(2)
• Resolve conflicts constructively.(1)
• Pay attention and refrain from engaging in disruptive behavior.(2)
• When you don't understand something, ask a question.(1)

17
Project Mangment
• Time mangment

• Tools of team mangment

• Cost mangment

• Examole of cost mangment

18
Project management definition
• The use of methods, knowledge, and skill.

• To achieve specific project goals.

• Within the parameters agreed upon.

19
Why project management is important
for engineers
• Without proper project management, projects become difficult
to manage.

• It may be more expensive than anticipated.

• And there will be latency.

20
Time mangment
• It implies that you should be able to complete the project
before the deadline.

• There are numerous time management tools, including:


1. Work breakdown structure.

2. Network diagram.

3. Gantt chart.

21
work breakdown structure
• Making a hierarchical tree out of the work in your project.

• A product-oriented family tree is made up of

• Hardware, software, services, data, and infrastructure

• The family tree is the result of efforts in systems engineering.

22
WBS Example

23
WBS Example

24
Total time of project = 120 days

25
Network diagram Example

26
Example of critical path and float
P1: {1, 3, 4, 6, 7, 8, 10, 11, 14, 17}, duration for P1 = 120 days
P2: {1, 3, 4, 6, 7, 8, 10, 12, 15, 17}, duration for P2 = 120 days
P3: {1, 3, 4, 6, 7, 8, 10, 13, 16, 17}, duration for P3 = 120 days
P4: {1, 3, 4, 6, 7, 9, 10, 11, 14, 17}, duration for P4 = 113 days
P5: {1, 3, 4, 6, 7, 9, 10, 12, 15, 17}, duration for P5 = 113 days
P6: {1, 3, 4, 6, 7, 9, 10, 13, 16, 17}, duration for P6 = 113 days
P7: {1, 3, 5, 6, 7, 8, 10, 11, 14, 17}, duration for P7 = 118 days
P8: {1, 3, 5, 6, 7, 8, 10, 12, 15, 17}, duration for P8 = 118 days
P9: {1, 3, 5, 6, 7, 8, 10, 13, 16, 17}, duration for P9 = 118 days
P10: {1, 3, 5, 6, 7, 9, 10, 11, 14, 17}, duration for P10 = 111 days
P11: {1, 3, 5, 6, 7, 9, 10, 12, 15, 17}, duration for P11 = 111 days
P12: {1, 3, 5, 6, 7, 9, 10, 13, 16, 17}, duration for P12 = 111 days
P13: {2, 3, 4, 6, 7, 8, 10, 11, 14, 17}, duration for P13 = 116 days
P14: {2, 3, 4, 6, 7, 8, 10, 12, 15, 17}, duration for P14 = 116 days

27
Example of critical path and float
P15: {2, 3, 4, 6, 7, 8, 10, 13, 16, 17}, duration for P15 = 116 days
P16: {2, 3, 4, 6, 7, 9, 10, 11, 14, 17}, duration for P16 = 109 days
P17: {2, 3, 4, 6, 7, 9, 10, 12, 15, 17}, duration for P17 = 109 days
P18: {2, 3, 4, 6, 7, 9, 10, 13, 16, 17}, duration for P18 = 109 days
P19: {2, 3, 5, 6, 7, 8, 10, 11, 14, 17}, duration for P19 = 114 days
P20: {2, 3, 5, 6, 7, 8, 10, 12, 15, 17}, duration for P20 =114 days
P21: {2, 3, 5, 6, 7, 8, 10, 13, 16, 17}, duration for P21 = 114 days
P22: {2, 3, 5, 6, 7, 9, 10, 11, 14, 17}, duration for P22 = 107 days
P23: {2, 3, 5, 6, 7, 9, 10, 12, 15, 17}, duration for P23 = 107 days
P24: {2, 3, 5, 6, 7, 9, 10, 13, 16, 17}, duration for P24 = 107 days
The Critical Paths are [P1, P2, P3]: 120 Days

28
Gantt chart
• A diagram consisting of a series of horizontal lines.

• demonstrates the amount of work completed

• During specific times.

• In relation to the amount planned for those periods.

29
Example of Gantt chart

30
Example of Gantt chart

31
Example of Gantt chart

32
Cost mangment
• It implies that you should be able to complete the project within the
allocated budget.
 We have several methods for estimating costs:
The total amount you receive from the project is referred to as revenue.
Profit is defined as the difference between revenue and expenses.
Profit = Revenue – Cost.
If the revenue and cost are equal, it means the profit is zero
If revenue is more than cost, you will get profit.
If revenue is less than cost, you will be in loss

33
Example of cost management

34
Example of cost management

35
Break-even analysis

36
Ethical and legal issues

37
Ethical definition
• A branch of philosophy concerned with the general nature of
good and bad.

• When making a decision, ethics comes into play.

• or whenever you have to make a decision

38
Why ethics are important?
• Everyone will benefit from ethics when it comes to working
with loyalty.

• They cannot avoid doing their work.

• And create a better working environment

39
Morals
• Things that are universally accepted.

• E.g (Speaking the truth or being truthful).

• You are not required to justify them because they are


universally accepted.

40
Principles
• These are the principles upon which a moral system is
founded.

• These are generally recognized principles.

41
Values
• These are not as broad in scope as morals or principles.

• Values are culturally specific.

42
Rule-Based Ethics
1- Rule-Based Ethics:To make all decisions, follow a set of rules.
1. Universality:The rules should be acceptable to everyone.
 It means that everyone agrees with the rules.
 In other words, the action that all members of society could support.
2.Transitivity:You would accept it if others made the same decision as you.
 It denotes making a decision on behalf of others.
 You can expect others to feel the same way about you.
What are the benefits?
 The rules are the same for everyone.
What are the issues with this?
 Making such rules is extremely difficult.

43
Conditional Rule-Based Ethic
2- Conditional Rule-Based Ethic:It means that there are some circumstances under
which you can break the rules.

• The person's practical but defining conditions vary.

44
Utilitarian Ethics
3- Utilitarian Ethics:The decision that results in the greatest good for all parties
involved.

 It means you make decisions that should benefit as many people as possible.

 You may break some rules while doing so.

 You might do something stupid.

 But you say that my overall intention is to produce positive results.

45
Situational Ethics
4- Situational Ethics:You make decisions based on the circumstances.

 You make some rules for one situation.

 However, you violate the rule.

 When the circumstances change.

46
IEEE code of ethics
• IEEE is a formal organization.

• IEEE standards should be familiar to an electrical and computer


engineer.

47
IEEE code of ethics
• IEEE code of ethics:
1. people's safety, health, and well-being
2. truthful and realistic
3. estimates of time and cost
4. Bribery must be avoided.
5. understand the consequences of technology
6. You should always keep up with new technologies.
7. Accept constructive criticism.
8. Assist your coworkers.
9. You should not be prejudiced.

48
Legal issues

49
legal issues
• There is a significant distinction between legal and ethical issues

• A legal issue is something that occurs that has legal ramifications and may
necessitate the assistance of a lawyer to resolve.

50
Intellectual property (IP)
• IP is a product that has been designed to prevent it from being sold for free.

• When you work for a company, you are responsible for all of the company's
products and design ideas.

• It is entirely owed by the company.

51
Patent
• Legal safeguards for a design or invention

• Innovation is required in patent but is not required in IP.

52
Utility patent
• Utility patent: Obtaining a utility patent (application patent).
The concept must be:

1. Novel (new): It did not exist previously.

2. Non-obvious: It should not be too easy.

3. Useful.

53
Copyrights
• Copyright: safeguards published works such as:

• books, articles, software, etc

• Copyright simply protects things from being copied.

54
Trade secret
• Every company has its own set of secrets.

• Any company practice or process that is generally unknown outside of the


company

55
Legal liability
• Liability : something owed, such as an obligation or a debt

• Tort : Any wrongful act that is not a breach of contract and for
which a civil suit can be filed.

• Negligence : not adhering to reasonable rules and standards


and committing a wrongful act

56
Legally negligent
• If the following four conditions are met, an act is considered legally
negligent:

1. The manufacturer was required to adhere to reasonable standards and rules.

2. There was a violation of duty (i.e., failed to include safety devices).

3. The plaintiff suffered harm.

4. The damage was caused by the breach.

57
Strict liability
• A standard that is even less stringent.
• This is known as strict liability.
• has been implemented
• The person or company suing you is not required to prove negligence.
• If the four conditions listed below are met, you are liable.
1. The product was potentially hazardous and/or defective.
2. The flaw existed when it was no longer under your control.
3. The flaw caused harm.
4. The defect is responsible for the damage.

58
Ethical and legal issues

59
Whistelblower
• When should a person become a whistleblower?

1. The public must suffer significant or serious harm.

2. Concerns must have been expressed to your superiors (all the way up to the
CEO) with no satisfactory resolution.

3. You have documented evidence that would persuade an unbiased observer


that your company is incorrect.

4. The release of the information outside the company will mitigate the risk.

60
References
(1) M. Rashid, “System Level Approach for Computer Engineering
Education”, International Journal of Engineering Education, vol.
31, no. 1, pp. 141-153, January 2015.
The End

62

You might also like