Software Engineering I: Lec 2 Overview

Software specification involves defining the software requirements and operational constraints with customers.
Development phase includes designing and programming the software.
Validation ensures the software meets customer needs and requirements.
Software evolution reflects necessary modifications due to changing customer demands or market dynamics.

Heterogeneity: Systems must function across varied networks and devices, including distributed systems.
Business and Social Change: Rapid changes in business environments and society require agile software development.
Security and Trust: Trust in software is crucial due to its pervasive role in daily life.
Scale: Software is developed for various scales, from small embedded systems to large cloud-based systems.

No universal software techniques fit all types of software systems; methods depend on application type, customer requirements, and development team background.

Stand-alone Applications: Functionality runs locally on a computer without network dependency.
Interactive Transaction-based Applications: Remote applications accessed via user terminals, e.g., e-commerce.
Embedded Control Systems: Control software for hardware devices, prevalent in various systems.
Batch Processing Systems: Designed for processing large data sets in batches.
Entertainment Systems: Systems designed primarily for personal entertainment purposes.
Modeling and Simulation Systems: Created for scientific modeling of physical processes.
Data Collection Systems: Collect environmental data via sensors and relay to other systems.
Systems of Systems: Composed of multiple interacting software systems.

Development should follow a managed process tailored to specific software types.
Dependability and performance are essential characteristics for all software systems.
It’s crucial to understand and manage software specifications and requirements.
Reusing existing software can save time and resources in development.

The Web serves as a primary platform for applications today, favoring web-based over local systems.
Web services facilitate remote access to application functionality.
Cloud computing enables software operation remotely, offering a pay-as-you-go model.

Software reuse dominates web systems development, focusing on integrating pre-existing components.
Incremental and agile development is necessary due to the impracticality of detailed upfront requirement specs.

Ethical responsibilities extend beyond technical skills; integrity is key for professionalism.
Engineers are expected to uphold moral principles, not just legal requirements.

Confidentiality: Respecting client confidentiality, regardless of written agreements.
Competence: Engineers should accurately represent their skill levels and not take on unsuitable tasks.
Intellectual Property Rights: Awareness and protection of local laws on intellectual property for clients and employers are crucial.
Computer Misuse: Engineers must refrain from unethical use of their technical skills.

Established by professional societies to guide ethical practice in software engineering.
Eight principles that govern professional behavior among all levels of software engineers, from students to executives.

Public Interest: Act in ways consistent with public welfare.
Client and Employer: Protect the interests of clients and employers while serving the public good.
Product Quality: Ensure high professional standards in software products.
Integrity in Judgment: Maintain independence in professional decisions.
Management Ethics: Promote ethical management practices within software development.
Professional Integrity: Contribute to the profession's reputation positively.
Collegial Support: Fair treatment and support for peers.
Lifelong Learning: Commitment to ongoing education in ethical practices.

Conflicts may arise with management policies.
Ethical concerns about releasing untested safety-critical systems.
Participation in controversial military or nuclear software development raises moral questions.