Acs223 - Computer Systems And Applications

Front 1

System Definition

Back 1

Related Parts
Shared Functional Goal
Complex Functionality

Front 2

Software and Systems Engineering Definition

Back 2

Systematic approach
methods and Tools
Finding Solution to problems
Software Subset of Systems

Front 3

Life Cycle Processes - V-Model

Back 3

Requirements Capture
Architecture Design
Sub System Design
Implementation
Sub System testing
Integration testing
Verification and Validation

Front 4

Define the V-Model

Back 4

Model of how system life cycle processes fit together
Abstract to refined
general to Detailed

Front 5

Traceability

Back 5

Documenting the change of a requirement from it's definition to its corresponding design and implementation element , to its test case

The evolution of a requirement from low to high level

Front 6

Definition and Types of Requirement

Back 6

A service a system must provide

Functional - Qualitative and Descriptive

Non-Functional - Quantitative and Measurable - Reliability, Response, Portability, Efficiency, Constraints

User Requirements - Type of Functional

Front 7

Embedded Systems Definition

Back 7

Systems with software based control

Front 8

What is a good requirement?

Back 8

Verifiable Attainable Clear Concise Unambiguous and Necessary

Identifies a Complete Set of Services

Front 9

How to find requirements?

Back 9

Gather Information from Stakeholders - What and Why?

Usage Scenarios

Problem Domain

Front 10

Sections of a requirements Documents

Back 10

Glossary and Introduction
User Requirements Definition
System Architecture
System Requirements
System Models
Evolution and Appendices

Front 11

UML - Definition and Creator

SysML - Definition and Creator

Back 11

A graphical Modeling language for systems by OMG

Adaptation of UML - INCOSE

Front 12

Diagrams to include in a requirements document

Back 12

UML Use Case
Block Definition Diagram
Package Diagram
Requirements Diagram
Activity Diagram

Front 13

Use Case Diagram - Definition and Purpose

Back 13

Tools to visualize user requirements

Use Cases - Shows Services Provided
Actors - users of the services - Subsystems, Hardware, people, boundary systems etc

Front 14

Syntax for Textual and Visually Displaying Requirements in a SysML Requirements Diagram

Back 14

Textually - Uniquely numbered, hierarchical and formal language

Visually - Text in rectangle boxes, arrows with relationship names

Front 15

Requirement Relationships

Back 15

Derive Requirement
Namespace Containment
Satisfy
Copy
Verify
Refine - Comments
Trace - Comments

Front 16

Context Model - Definition and Usage

Back 16

Shows scope and boundary of a system

Define the flow of information to and from the system and the environment

Front 17

Activity Diagram

Back 17

Shows information flow to and from
shows Information flow within system
Shows control actions within the program

Describes control flow from one example to another

Front 18

Use and reason for Object Oriented Methods

Back 18

Reliability
Reusability
Abstraction
Modularization

Front 19

Definition of a Class and Object

Back 19

Generic Structure for a set of elements with similar characteristics

Blueprint of the Object

A specific instance of a class. Objects have data and behavior and are the building blocks of the system

Front 20

Encapsulation Definition

Back 20

Combination of data and behavior (attributes and methods in a class)

Front 21

Inheritance Definition

Back 21

Subclass inherits data and behavior from class

Subclass may change/add more

Front 22

Class Relationships

Back 22

Association
Navigation
Aggregation
Composition
Inheritance
Dependency

Front 23

Multiplicity Definition

Back 23

Number of instances of each class in a relationship

Front 24

Identifying Objects?

Back 24

Nouns and Noun Phrases - Responsibilities of a System - Defining Information

Front 25

SysML block diagrams

Back 25

Similar to UML class diagrams - Difference being blocks represent software, hardware and subsystems

Standard ports - Request for Services

Flow Ports - Data flow

Front 26

Sequence Diagrams

Back 26

Shows object cooperation to provide use case functionality

Shows interactions involved in a use case

Front 27

State diagrams

Back 27

Snapshot of an object during a specific instance in time

Front 28

Module in OO

Back 28

Class/Object or a method in a class

Front 29

Cohesion - Definition and Types

Back 29

The strength of the interdependency between the elements of a module

Coincidental (low)
Logical
Procedural
Temporal
Communicational
Sequential
Functional (high)

Object Cohesion - Methods and Attributes
Method Cohesion - private variables, program statements, private methods

Front 30

Coupling - Definition and Types

Back 30

The strength and number of relationships between modules

Common (high)
External
Control
Stamp
Data
Message (low)

Front 31

What happens upon instantiation ?

Back 31

Memory allocated to hold object
Constructor is run
Data is initialised

Front 32

Errors - Types of Failures

Back 32

Fail Hard - System Stops
Fail Soft - Performance Declines
Fail Safe - Failure Leaves system in a safe state

Front 33

Validation

Back 33

Does the system meet the user needs?

Front 34

Verification

Back 34

Does each component meet its specification and is it error free?

Front 35

Scenario Based Testing

Back 35

Plan scenarios for each use case

Sequence Diagrams will help identify objects

Set up tests from a user/actor perspective

Front 36

Approaches to testing

Back 36

Input Stimulus
Measured Response
Test Plan
Strategic Testing