Software Engineering I - Introduction Lecture

Study Notes

Software Specification: Involves defining requirements and constraints alongside the customer.
Software Development: The phase where software is designed and programmed.
Software Validation: Checks if the software meets customer requirements.
Software Evolution: Modifications made to adapt to changing customer needs and market demands.

Heterogeneity: Software must operate across diverse systems, including mobile devices and networks.
Business and Social Change: Rapid technological advancements necessitate the agility to modify existing software and develop new solutions.
Security and Trust: Critical for software given its pervasive role in daily life.
Scale: Software ranges from small embedded systems to large-scale cloud services.

Varying types of software systems require tailored techniques and tools, dependent on application type and customer requirements.

Stand-alone Applications: Self-contained applications that run locally on a PC.
Interactive Transaction-based Applications: Accessed remotely, including e-commerce software.
Embedded Control Systems: Software managing hardware devices, predominant in numbers.
Batch Processing Systems: Designed for processing large heaps of data simultaneously.
Entertainment Systems: Primarily for personal use, aimed at user enjoyment.
Modeling and Simulation Systems: Used in scientific applications for simulating physical processes.
Data Collection Systems: Gather environmental data via sensors for processing.
Systems of Systems: Composed of multiple integrated software systems.

Development follows a managed process tailored for specific software types.
Dependability and performance are essential across all systems.
Understanding and managing software specifications and requirements is vital.
Reusing pre-existing software components is preferred over developing new software.

The Web serves as a platform for application development, transitioning from local systems to web-based applications.
Web Services: Enable functionality access online.
Cloud Computing: Offers remote application services where users pay based on usage.

Software Reuse: A vital strategy for constructing web-based systems by utilizing existing components.
Incremental and Agile Development: Encourages developing systems in stages; comprehensive requirements are often impractical upfront.

Confidentiality: Respecting employer or client confidentiality is critical.
Competence: Engineers should accurately represent their capabilities and refrain from overstepping their expertise.
Intellectual Property Rights: Protecting the rights of employers and clients is essential, with awareness of relevant laws.
Computer Misuse: Ethical responsibilities include refraining from unethical computer use, which can range from minor infractions to serious breaches.

A collaborative framework from professional societies offering ethical guidelines for software engineers.
Eight fundamental principles govern professional behavior in software engineering.

Software engineers' influential roles in various sectors necessitate a commitment to ethical practices.
Their impact can either promote or undermine societal benefits, underscoring the importance of ethical commitment.

Public: Act in alignment with public interest.
Client and Employer: Prioritize the interests of clients while maintaining public interest.
Product: Uphold high professional standards for products.
Judgment: Independently maintain integrity in decision-making.
Management: Promote ethical management in software development.
Profession: Enhance the integrity of the profession.
Colleagues: Support and treat colleagues fairly.
Self: Engage in continuous learning and promote ethical practices.

Potential conflicts include disagreement with senior management policies.
Ethical concerns when releasing untested safety-critical systems.
Participation in ethically contentious projects like military weaponry development.