SWE Ch1 Introduction slides 16-29

Main ideas, concepts, and lessons

1) Software process reliability and quality criteria

• Security is a primary component of reliability.
  • If security fails, serious harm can occur (e.g., someone could access bank account information and balances).
• Scalability is another key quality aspect.
  • It measures whether the system can grow to handle more users/requests without losing efficiency or quality.

Scalability rule (stated as a “rule”):

• Scalability = the ability to provide the service to a larger number than planned while maintaining the same quality and efficiency.

• High scalability means the system can accommodate change (e.g., expanding from 50 users to 1000) while staying efficient.

• Low scalability means the system cannot maintain efficiency/quality under larger load.

---

2) Diversity in software engineering (no one-size-fits-all)

• There is no single system type or single unified method that works for everyone.
• Each project may require its own mechanisms and approach.
• “Diversity” is presented as a challenge/obstacle to consider in software engineering.

---

3) Types of software systems (with examples)

1. Standalone software
   • Runs on a personal computer using only local resources.
   • Example: a downloaded game that doesn’t require internet to run.
2. Interactive transaction-based applications
   • Typically split into client (sends requests) and server (executes requests).
   • Core operation happens on a remote device.
3. Embedded control systems
   • Software dedicated to a specific device/computer system.
   • Examples: smart refrigerator (remote temperature control), car computer systems.
4. Batch process systems
   • Send a single request containing many operations rather than many individual requests.
   • Example: issuing rewards to 1000 students via one request containing all 1000 items.
5. Entertainment systems
   • Example: PlayStation, home audio systems.
6. Simulation programs
   • Used to test or predict outcomes before expensive real-world implementation.
   • Examples: AutoCAD; simulations of construction processes or chemical/car manufacturing scenarios.
7. Data collection tools (IoT-related)
   • Collect data via sensors to provide information (example: weather data from sensors).
8. Systems of Systems
   • A “single system” composed internally of multiple systems working together.
   • Example concept: a unified system that internally uses multiple systems located together.

---

4) Core software engineering process fundamentals

• Systems should have clear procedural steps for building.
• System reliability/performance must be acceptable for all software types.
• Requirements handling and analysis are fundamental concepts.
• Reuse is a core principle:
  • If a requirement-writing standard exists, its procedures should be reusable across projects.
  • Don’t redo the same work repeatedly—store reusable components (e.g., a username/password login mechanism) in a library for future projects.

---

5) Internet software considerations and development approach

• Internet services differ from traditional scheduled/onsite access:
  • Previously: services might be used during work hours.
  • Now: services can be online and available more continuously.
• This drives additional needs:
  • Increased security
  • Support for more users
  • Higher availability, including “earliest possible” service availability

Dealing with change

• Internet environments change rapidly, requiring the ability to keep up with updates.
• Services may be part of larger ecosystems (examples mentioned: Absher, Nafath, national information center, traffic data, passport data), creating complex, distributed, diverse programs.

Process methodology emphasized: Agile/incremental development

• Since internet app requirements change quickly:
  • Agile Development is suggested for more freedom and adaptability.
• Waterfall is contrasted negatively:
  • It requires gathering all requirements upfront, then developing/testing/launching in a long sequence.
  • This long flow can delay quality improvements and impact service quality.
• Instead, incremental delivery is suggested:
  • Provide the system/service in partial steps.
  • Launch service 1, then service 2, then service 3—progressively “consolidating” the overall system.
  • Benefits:
    • faster delivery
    • earlier detection of errors while providing usable parts

---

6) Service-oriented system design and web delivery

• A “system” in this lesson is described as a set of one or more services.
  • Example services mentioned: a verification service and a database connection service.
• Design is described as service-oriented, where you place multiple services inside an existing system.
• Web delivery is said to provide different capabilities than desktop/standalone delivery, enabling better use of existing work.

---

7) Software engineering ethics (explicit list of principles)

Ethics are framed as both technical and personal, covering responsibilities beyond pure coding.

Ethical principles mentioned

• Honesty / truthfulness
  • Must not claim a task is finished when it is not.
  • Lack of integrity harms the development process and procedure flow.
• Confidentiality
  • Protect confidentiality of:
    • services being built
    • clients
    • requirements
  • Rationale: clients may trust engineers with sensitive internal mechanisms.
• Accept work only within your competence
  • Don’t accept tasks you can’t do.
  • Example: being asked to switch into cybersecurity engineering despite lacking the required skill.
• Intellectual property (IP) respect
  • Follow IP rights and give due credit/ownership.
  • Example: using a client-owned idea and selling it to others is a violation.
• Proper use of provided resources
  • Don’t misuse assigned computers or tools for personal purposes.
  • Installing unrelated programs can degrade performance and harm the system/process, so actions must consider performance impact.

---

Speakers / sources featured

• No specific named speakers are provided in the subtitles.
• The content appears to be delivered by an unnamed instructor/presenter (first-person narration: “let me write…”, “see you in future lessons”).