軟件工程：誰是軟件工程師？甚麼是軟件開發生命週期（SDLC）？

Software Engineering: Who Is a Software Engineer, and What Is the Software Development Life Cycle (SDLC)?

1. Who Is a Software Engineer?

A software engineer is a professional who applies engineering principles, programming knowledge, and problem-solving techniques to design, develop, test, deploy, and maintain software applications and systems.

Software engineers do more than write code. They analyze problems, plan solutions, design software architecture, ensure software quality, fix errors, and maintain applications to meet users' needs.

Software engineering involves developing software that is reliable, efficient, secure, maintainable, and scalable.

Responsibilities of a Software Engineer

The major responsibilities of a software engineer include:

1. Problem Analysis: Understanding a problem and identifying the requirements of the software needed to solve it.
2. Software Design: Planning how the software will work, including its structure, components, database, and user interface.
3. Programming: Writing instructions using programming languages such as Python, Java, JavaScript, and C++.
4. Testing and Debugging: Checking that the software works correctly, identifying errors, and correcting them.
5. Deployment: Making the completed software available for users.
6. Maintenance: Updating the software, fixing bugs, improving performance, and adapting it to new requirements.
7. Documentation and Collaboration: Documenting the software and working with other professionals to develop and improve the system.

Examples of Software Engineering

Software engineers develop different types of applications, including:

• Web applications: Online shopping platforms, educational websites, and banking portals.
• Mobile applications: Messaging applications, learning applications, and mobile banking apps.
• Desktop applications: Text editors, accounting software, and development tools.
• Artificial Intelligence applications: Object detection systems, recommendation systems, and AI-powered assistants.
• Backend systems: APIs, databases, authentication systems, and services that process application data.

Skills Required to Become a Software Engineer

Some important skills include:

• Programming and computational thinking.
• Data structures and algorithms.
• Database management.
• Software testing and debugging.
• Version control using Git and GitHub.
• Understanding software architecture and design.
• Communication, teamwork, and problem-solving.

Example

Consider a university that wants to develop a student management system.

A software engineer may analyze the university's requirements, design the system, create the database, write the code, test the application, deploy it, and maintain it.

The system may allow students to register for courses, check their results, and update their profiles.

This example demonstrates how software engineering combines technical knowledge and structured problem-solving to develop a practical solution.

1. What Is the Software Development Life Cycle (SDLC)?

The Software Development Life Cycle (SDLC) is a structured process used to plan, design, develop, test, deploy, and maintain software.

It provides a systematic approach to software development, helping teams manage project requirements, control costs, identify risks, and deliver software that meets users' needs.

SDLC describes the major phases involved in developing software, from identifying a problem to maintaining the completed system.

Phases of the Software Development Life Cycle

1. Planning

The planning phase identifies the problem the software will solve, its objectives, expected users, available resources, estimated cost, and project timeline.

The development team evaluates whether the project is feasible and determines what will be required to complete it.

Example: A university decides to develop an online student registration system and estimates the time, budget, and personnel needed.

1. Requirements Analysis

During this phase, the team gathers and analyzes the requirements of the users and the organization.

Requirements are commonly divided into:

• Functional requirements: What the system must do, such as allowing students to register for courses.
• Non-functional requirements: How well the system must operate, such as its security, performance, reliability, and usability.

Example: The university requires students to log in securely, register for courses, and view their registration status.

1. System Design

The design phase determines how the software will be structured and how its components will interact.

It may include database design, system architecture, user-interface design, data flow, and technology selection.

Example: The team designs the registration pages, database tables, authentication process, and connections between the frontend and backend.

1. Implementation (Coding)

During implementation, developers translate the approved design into working software by writing code using appropriate programming languages and frameworks.

They may also use version-control tools such as Git to track changes and collaborate.

Example: Developers use Python and Django to build the backend of the student registration system.

1. Testing

The testing phase checks whether the software meets its requirements and works as expected.

The team identifies defects, verifies functionality, and checks aspects such as performance, security, and usability.

Common types of testing include:

• Unit testing: Testing individual functions or components.
• Integration testing: Checking whether different components work together.
• System testing: Testing the complete application.
• Acceptance testing: Checking whether the software meets the users' requirements.

Example: Testers verify that students can register successfully, invalid information is rejected, and unauthorized users cannot access protected accounts.

1. Deployment

Deployment involves releasing the software into an environment where its intended users can access it.

Depending on the project, deployment may involve installing software on computers, publishing a website, or hosting an application on a server or cloud platform.

Example: The university publishes its registration system online so that students can access it through a web browser.

1. Maintenance

Maintenance begins after deployment and continues throughout the software's useful life.

It involves fixing defects, improving performance, updating features, addressing security issues, and adapting the system to changing requirements.

Example: After students begin using the registration system, the developers fix reported errors and add new features when the university introduces new registration requirements.

Summary of the SDLC Phases

The seven commonly described phases are:

1. Planning
2. Requirements Analysis
3. System Design
4. Implementation
5. Testing
6. Deployment
7. Maintenance

These phases provide a general structure. Depending on the development methodology, some phases may overlap, repeat, or occur continuously rather than strictly one after another.

1. Common SDLC Models

An SDLC model describes how a development team organizes and carries out the phases of software development.

Waterfall Model

The Waterfall model follows a largely sequential process. Each phase is generally completed before the next phase begins.

It can be appropriate when requirements are stable and clearly understood, although changes later in the process can be difficult and costly.

Agile Model

Agile is an iterative and incremental approach that emphasizes collaboration, frequent feedback, and delivering software in small, useful increments.

It allows teams to respond to changing requirements throughout development.

Spiral Model

The Spiral model organizes development into repeated cycles that emphasize planning, risk analysis, engineering, and evaluation.

It is particularly useful for projects with significant risks or complex requirements.

DevOps Approach

DevOps emphasizes collaboration between software development and IT operations, using automation and continuous practices to improve building, testing, releasing, and operating software.

It supports practices such as Continuous Integration and Continuous Delivery or Deployment (CI/CD).

1. Why Is the SDLC Important?

The SDLC is important because it:

• Provides an organized process for developing software.
• Helps teams understand and manage project requirements.
• Identifies potential problems and risks earlier.
• Improves software quality through systematic testing.
• Helps manage project time, cost, and resources.
• Supports communication among developers, testers, project managers, and users.
• Makes software maintenance and future improvements easier to manage.

1. Relationship Between Software Engineering and SDLC

Software engineering and the SDLC are closely related, but they are not the same thing.

Software engineering is the discipline of applying engineering principles and methods to the development and maintenance of software.

SDLC is a structured framework that organizes the activities involved in creating and maintaining a software product.

Software engineers use the SDLC, along with suitable tools, methods, and engineering practices, to develop software systematically.

For example, when developing an AI-powered object detection system, a software engineer may identify the problem, define the system requirements, design the application, implement an object detection model, test its accuracy, deploy the application, and maintain it as requirements change.

This demonstrates how software engineering principles and the SDLC work together in a real-world project.