CS 321 L1 & L2

Software engineering is an engineering discipline concerned with all aspects of software production from initial conception to operation and maintenance.

It is important to produce reliable and trustworthy systems economically and quickly, which can reduce long-term costs for testing, quality assurance, and maintenance.

Specification, Development, Validation, Evolution.

Software Specification is where customers and engineers define the software to be produced and the constraints on its operation.

Software Development is where the software is designed and programmed.

Software Validation is where the software is checked to ensure that it meets the customer's requirements.

Software Evolution is where the software is modified to reflect changing customer and market requirements.

Acceptability, Dependability and Security, Efficiency, Maintainability.

Software must be understandable, usable, and compatible with other systems used by the intended users.

Dependability includes reliability, security, and safety. Dependable software should not cause damage in case of failure and must be secure from malicious users.

Efficiency refers to how software uses system resources like memory and processor cycles, including factors like responsiveness and processing time.

Maintainability is the ability of software to evolve to meet changing customer needs, which is crucial as business environments change.

Agile, Black Box Testing, Prototyping, Rapid Application Development, Spiral Model, White Box Testing, Extreme Programming, Joint Application Development, Scrum, Waterfall Model.

Generic products are stand-alone systems produced by a development organization and sold on the open market, such as mobile apps or word processors.

Customized software, also called bespoke software, is developed specifically for a particular customer, such as control systems for electronic devices.

Heterogeneity, Business and Social Change, Security and Trust, Scale.

The mechanism of dividing software development work into distinct phases to improve design, product management, and project management.

Software Development Life Cycle (SDLC).

It encourages systematic and disciplined development of software.

The Waterfall Model.

Requirements Analysis, System and Software Design, Implementation and Unit Testing, Integration and System Testing, Operation and Maintenance.

The system's services, constraints, and goals are defined in detail to serve as the system specification.

Allocating requirements to hardware or software systems and establishing an overall system architecture.

The software design is realized as a set of programs, and unit testing ensures that each unit meets its specification.

Individual programs are integrated and tested as a complete system to ensure the software meets requirements.

Operation and Maintenance.

A phase has to be complete with full documentation before the next phase starts.

Embedded systems, critical systems, and large software systems involving multiple companies.

Developing an initial implementation, getting feedback, and evolving the software through several versions.

Specification, development, and validation.

The cost of implementing requirement changes is reduced.

The process is not visible, and regular deliverables are needed to measure progress.

Large systems need a stable framework or architecture, which must be planned in advance.