Software Engineering Management and Ethics Review

Vocabulary terms and definitions covering software engineering ethics, intellectual property, organizational structures, liability, and risk management based on case study scenarios.

IEEE Code of Ethics: Public

Software engineers shall act consistently with the public interest, ensuring that products protect financial information and maintain public trust.

IEEE Code of Ethics: Client and Employer

Software engineers shall act in a manner that is in the best interests of their client and employer, consistent with the public interest.

IEEE Code of Ethics: Product

Software engineers shall ensure that their products and related modifications meet the highest professional standards possible, including thorough testing and compliance with quality requirements.

IEEE Code of Ethics: Judgment

Software engineers shall maintain integrity and independence in their professional judgment, which includes honestly reporting software defects and security vulnerabilities.

Professional Ethics

Rules of conduct based on professional codes, organizational policies, and legal responsibilities that focus on protecting clients, users, and the public.

Personal Ethics

Guidelines based on an individual's personal beliefs, values, and morals, which may vary from person to person.

Copyright

A legal protection for original creative works such as game characters, artwork, music, and software code from unauthorized reproduction or distribution.

Patent

A protection for innovative technologies, inventions, and unique technical processes, such as proprietary matchmaking systems.

Trademark

A protection for brand names, logos, and visual identity that prevents competitors from creating market confusion.

Software License Violation

The act of using software in a manner that disregards the agreed terms of the license, such as installing a single licensed copy on multiple computers for commercial use.

Software Liability

The legal responsibility of a software company for damages, such as financial losses, caused by defects, errors, or failures in its software.

Functional Organizational Structure

A structure where work is department-based, functional managers have complete authority, and communication mainly occurs within departments.

Matrix Organizational Structure

A structure where authority is shared between functional and project managers, allowing resources to be shared across projects to balance expertise with project requirements.

Projectized Organizational Structure

A structure where projects are the primary focus, project managers have full authority, and the team is dedicated to specific project objectives.

Requirements Risk

A project risk category involving frequent changes in customer requirements that can increase project scope and cause rework.

External Risk

A project risk category involving factors beyond the company's direct control, such as delays from third-party service providers or payment gateway integrations.

Resource Risk

A project risk category involving insufficient skilled personnel or a shortage of experienced developers, which reduces productivity and affects quality.

Security Risk

A project risk category involving threats like unexpected cyberattacks that compromise system security, data integrity, and reliability.

Change Management Process

A risk management strategy used to prioritize requirements and obtain client approval before implementing changes to control project costs and schedule.

SDLC

An acronym for Software Development Life Cycle, the framework throughout which code reviews and compliance with banking regulations and standards must be maintained.