Introduction to Software
Engineering | Study Guide,
Questions & Answers
|Graded A+ | Guaranteed
success|
Updated 2026 Questions and Answers
100% Verified Exam Prep and Comprehensive
Rationales
Included
,Examples of Functional Requirements "A library system that provides a single interface to a number of databases of
articles in different libraries". "Users can search for and download this articles for
personal study". "Users shall be able to search either all of the initial set of
databases or select a subset from it". "The system shall provide appropriate
viewers for the users to read documents in the document store".
Non-Functional Requirements These define system properties and constraints.
Properties: reliability, response time, storage requirements.
Constraints: security, legal impacts, domain expert workflow.
Process Requirements: (e.g.,) a particular programming language.
Example of Non-Functional Requirements "The user interface for LIBSYS shall be implemented as simple HTML without
frames or Java applets". "The system shall not disclose any personal information
about customers apart from their name and their registration identification
number"."The system architecture shall be constructed according to the WC3
standards".
UML Unified Modelling Language: Standard language for specifying, visualising,
constructing, and documenting all the artefacts of a software system during the
software lifecycle.
UML Diagram Types Behavioural.
Functional.
Structural.
Behavioural Diagrams Activity Diagram.
State Diagram.
Sequence Diagram.
Structural Diagrams Class Diagram.
Object Diagram.
Functional Diagrams Use Case Diagram
Use Case Diagram Functional.
Visualise relationships between actors (interacting with the system) and use cases
(functionality).
Activity Diagram Behavioural.
A diagram that shows the flow of control and data form activity to activity.
Activity diagrams address the dynamic view of a system
, Sequence Diagrams Behavioural.
Displays object interactions arranged in a time sequence.
How do components interact?
Class Diagrams Structural.
Collection of objects with common structure, common behaviour, common
relationships, and common semantics.
State Transition Diagram Behavioural.
Show life history of a given class.
Classes that have a lot of dynamic behaviour.
Design Pattern Way of re-suing abstract knowledge about a software design problem and its
solution.
Types of design patterns Creational
Structural
Behavioural
Behavioural patterns Observer
Mediator
Creational patterns Singleton
Abstract Factory
Structural patterns Facade
Proxy
Adapter
Composite
Engineering | Study Guide,
Questions & Answers
|Graded A+ | Guaranteed
success|
Updated 2026 Questions and Answers
100% Verified Exam Prep and Comprehensive
Rationales
Included
,Examples of Functional Requirements "A library system that provides a single interface to a number of databases of
articles in different libraries". "Users can search for and download this articles for
personal study". "Users shall be able to search either all of the initial set of
databases or select a subset from it". "The system shall provide appropriate
viewers for the users to read documents in the document store".
Non-Functional Requirements These define system properties and constraints.
Properties: reliability, response time, storage requirements.
Constraints: security, legal impacts, domain expert workflow.
Process Requirements: (e.g.,) a particular programming language.
Example of Non-Functional Requirements "The user interface for LIBSYS shall be implemented as simple HTML without
frames or Java applets". "The system shall not disclose any personal information
about customers apart from their name and their registration identification
number"."The system architecture shall be constructed according to the WC3
standards".
UML Unified Modelling Language: Standard language for specifying, visualising,
constructing, and documenting all the artefacts of a software system during the
software lifecycle.
UML Diagram Types Behavioural.
Functional.
Structural.
Behavioural Diagrams Activity Diagram.
State Diagram.
Sequence Diagram.
Structural Diagrams Class Diagram.
Object Diagram.
Functional Diagrams Use Case Diagram
Use Case Diagram Functional.
Visualise relationships between actors (interacting with the system) and use cases
(functionality).
Activity Diagram Behavioural.
A diagram that shows the flow of control and data form activity to activity.
Activity diagrams address the dynamic view of a system
, Sequence Diagrams Behavioural.
Displays object interactions arranged in a time sequence.
How do components interact?
Class Diagrams Structural.
Collection of objects with common structure, common behaviour, common
relationships, and common semantics.
State Transition Diagram Behavioural.
Show life history of a given class.
Classes that have a lot of dynamic behaviour.
Design Pattern Way of re-suing abstract knowledge about a software design problem and its
solution.
Types of design patterns Creational
Structural
Behavioural
Behavioural patterns Observer
Mediator
Creational patterns Singleton
Abstract Factory
Structural patterns Facade
Proxy
Adapter
Composite
