INDEX

abstraction, modelling 108, 120–3

classification 120

composition 121–2

generalisation 121

idealisation 122–3

abstraction, OO design 171, 172

acceptance testing see user acceptance testing

access controls 193

activity sampling 67

adaptive maintenance 262

adaptive software development 99

Agile Alliance 97

12 underlying principles 97–8

Agile development approach

adjustment of requirements 77–8

documentation 135

methodologies 26–8, 98–100

testing 238

Agile Unified Process 100

analysis of business needs see business analysis

anti-malware software 193

Application Service Providers (ASPs) 103

architecture 202–3

communication 206–7

contract 214

enterprise 207–10

ISO 42010 definition 202, 203, 223

management 222–4

patterns 203–6

principles 210–11

software 214–20

software tools 272–3

solution 211–14

stakeholders and roles 220–2

‘As-Is’ and ‘To-Be’ models 110

U-curve 110–11

attribute of an object, OO development 101

audit trail 193–4

bar codes 156

Barker Ellis data mode 121

benefits realisation 265, 266

benefits review 44, 265

bespoke solutions 81–2

‘big bang’ implementation 253–4

binary chop 184

black-box elements 123–4

black-box techniques 234–5

black- and white-box testing 125

‘b’ model of systems development 260–1

Boehm, Barry, Spiral model 25–6, 261–2

Box, George 108

break-even/payback analysis 56–7

business analysis 35–46

definition of 38

outcomes from 44–5

place in development lifecycle 38–44

rationale for 37

techniques 68–9

business analysts 63

business case 47–59

cost-benefit analysis 52–3

elements of 50–1

feasibility checking 49–50

impact analysis 56

investment appraisal techniques 56–9

in lifecycle of IT project 47–9

option selection 51–2

purpose of 47

risk analysis 53–6

business feasibility 41, 49

business logic layer 217

business modelling tools 272–3

business objectives 266

business and project risks 54–6

business use cases (BUCs) 129–30

CARE (computer-aided requirements engineering) 273, 276

‘cascade’ training 252–3

CASE (computer-aided software engineering) 92, 272, 276

CAST (computer-aided software testing) 275, 276

change control 76, 270

change elements 44–5

changeover

direct/ ‘big bang’ 253–4

parallel running 254–5

phased 255–6

pilot 255

see also implementation

check digit 177–8

class 170

classification, abstraction 120

class model 171

clerical controls 188–9

client-server patterns, architecture 215–18

closed source/shared source software 88

cloud computing 102–3

Cockburn’s use cases 126–8

code design 175–8

faceted codes 176–7

self-checking codes 177–8

sequential numbers 176

cohesion 205

commercial off-the-shelf (COTS) packages 83–7

communication/interoperation patterns 206–7

component-based software architecture 218–20

component-based software development 88–91

component design 168–9

component testing 234

composition, abstraction 121–2

conceptual models 122

configuration management 76, 271

confirmation testing (re-testing) 235

constraints on system design 142–6

context 10, 92–3

contextual models 122

control totals 188

corrective maintenance 262

cost-benefit analysis 52–3

COTS (commercial off-the-shelf solutions) 82

pros and cons of 83–7

coupling 204–5

cross-field validation 188

cross-referencing/linking 131–4, 270–1

CRUD matrix 132–3

Crystal clear 99

cutover see changeover

database management systems (DBMS) 178–86

hierarchical databases 178–9

network databases 179–80

object-oriented databases 182–3

physical files 183–6

relational databases 180–2

data controls 189–90

data conversion 247–8

data design 173–86

code deisgn 175–8

database management systems 178–86

normalisation 174–5

data flow diagrams 116

data input stages 153–5

data interchange, system to system 163

data item, OO development 101

data layer 217

data mapping 246–7

data migration 245–6

data models 122–3, 173–4

data protection legislation 145

DBMS see database management systems

default value 190

define requirements stage, role of business analyst 41–2

deliverables 12, 93

on demand software 102–3

Department of Defence Architecture Framework (DoDAF) 12, 210

design constraints 142–6

organisational constraints 144–6

project constraints 144

technical constraints 144–5

design patterns 196–200

design specification, static testing 231–2

design stage 9

role of business analysts 42–3

design use cases (DUCs) 129–30

developers 64

development (programming) stage 9

approaches 79–81

component-based 88–91

methodologies 92–100

role of business analysts 42–3

diagrams and models 109–10

pre-UML 115–17

UML 117–20

direct files 186

direct implementation 253–4

discounted cash flow (DCF) method 57–8, 59

document analysis 67

documentation

COTS products 84

requirements 73–6

software generation of 272

support 249–51

using models 134–7

domain architects 220

domain experts 63

domains, architecture 208–9, 211–12

double-keying 187

DSDM (Dynamic Systems Development Method) 29–30, 99

dynamic testing 230

progression through stages 236–7

‘V’ model test stages 233–5

elicitation of requirements 64–7

qualitative techniques 65–6

quantitative techniques 66–7

encapsulation 101, 170

encryption 150, 193

enterprise architects 220

enterprise architecture (EA) 207–10

domains 208–9

frameworks 209–10

strategy vs. tactics 208

entity relationship diagrams (ERDs) 116

ETL (Extract, Transform and Load) 245–6

evaluation 263–7

benefits review 265

metrics for 265–8

post-implementation review 264–5

post-project review 264

of software tools 276–7

event modelling techniques 116–17

evolutionary lifecycle approaches 16, 23–6

iterative development 23–5

maintenance 261–2

Spiral model 25–6

strengths & weaknesses 16–17

existence checks 187

experience-based testing 235

extended ‘V’ model 20, 39, 266

Extreme programming (XP) 99

faceted codes 176–7

feasibility checking 49–50

feasibility study 9, 39–41

feature-driven development 99

file access/retrieval mechanisms 185–6

file organisation systems 183–5

sequential file organisation 184–5

serial file organisation 183–4

financial feasibility 41, 49

firewalls 193

focus groups 65

foreign key 181

functional fit 267

functional model map 128–31, 134, 219

functional requirements 68, 139, 140

functional specification, static testing 231

Gamma, Erich, design patterns 196–200

gap analysis 112

generalisation

abstraction 121

OO design 171, 172

general requirements 68

‘good’ requirements, features of 69–71

governance

enterprise architecture 210, 211

solution architecture 214

hardware installation 249

hash totals 189

hierarchical architecture 206

hierarchical client-server 216

hierarchical databases 178–9

hierarchical domain services 212

high-level system design 164–8

coupling and cohesion 168

programming constructs 167

stepwise refinement 166–7

holistic solution 211

hub-and-spoke architecture 206–7

human-computer interfaces

output user interfaces 162–3

user interface (UI) design 152–3

hybrid lifecycle approaches 28–32

IaaS (infrastructure as a service) 102

idealisation, abstraction 122–3

immediate and long-term costs 52–3

impact analysis 56

implementation 9–10, 242–57

data conversion 247–8

data mapping 246–7

documentation supporting 249–51

file and data conversion or creation 245–6

implementation in the lifecycle 242–4

implementation plan 256–7

installation of hardware and infrastructure 249

migration of software modules 248–9

planning for 244–5

role of business analysts 43

system implementation 253–6

training 251–3

Incremental lifecycle 21–3

and systems design 148–9

testing 238

Incremental processes, modelling 135–7

Infrastructure as a service (IaaS) 102

infrastructure installation 249

inheritance, OO design 172

input controls 187–8

input devices/technologies 156–7

input and output (I/O) design 150–63

input design 153–8

output design 158–63

user interface (UI) design 152–3

input user-interfaces 157–8

intangible and tangible costs 52, 53, 54

integration testing 234

internal rate of return (IRR) 58, 59

interviews 65

investment appraisal techniques 56–9

iteration 167

iterative development 23–5

place of design 149

IT/IS change 44

Jackson Structured Programming (JSP) 96, 100

Kanban 99

key performance indicators (KPIs) 267

Lean Software Development (LSD) 31–2, 99

license issues 86, 87, 88, 103

lifecycles 8–34

Agile, impact of 26–8

choosing 32–3

evolutionary approach 23–6

hybrid approaches 28–32

linear approach 17–23

system development lifecycle 8–17

linear lifecycle approaches 15, 17–23

Incremental 21–3

strengths & weaknesses 15–16

‘V’ model 19–21

Waterfall 17–19

linking/cross-referencing 131–4, 270–1

links and cross-references 270–1

logical design 194–5

logical models 123

logical security 192–3

long-term and immediate costs 52–3

loose and tight coupling, component architecture 204–5

LSD (Lean Software Development) 31–2

maintenance 258–63

categories 262–3

regression testing 263

in system development lifecycle 258–62

maintenance agreements COTS products 84

malware 193

management, requirements 62, 76–7

managers 63, 221–2

Manifesto for Agile development 97

manuals, operational 250

matrices 132–3

metrics for evaluation of project 265–7

Model Driven Architecture (MDA) 103–4

modelling 107–38

abstraction 120–3

cross-referencing and mapping 131–4

documentation 134–7

layers or levels of models 125–31

limitations 112–13

model element opaqueness 123–5

multiple views 114–15

pre-UML techniques 115–17

rationale 111–14

and traceability 131–2

UML 117–20

value of 113–14

modular architecture 204

module testing 234

MoSCoW prioritisation technique 71–2

multiple models and views 114–15

net present value (NPV) 58

network databases 179–80

non-functional requirements 68, 139, 140

normalisation 174–5

n-tiered software architecture 217–18

object-oriented database management systems (OODBMS) 182–3

object-oriented design 169–72

object-oriented development (OOD) 101

object-relational mapping 182

observations 65

OCR (Optical Character Recognition) 157

off-the-shelf solutions 78, 81, 82

pros and cons of 83–7

offshoring 4

OLAP (OnLine Analytical Processing) 163

OMR (Optical Mark Recognition) 157

online help 250

opaqueness of model elements 123–5

open source software 87–8

operational manuals 250

operations managers 221–2

optimisation 262

organisational constraints on system design 144–6

organisation change 45

output controls 188

output design 158–63

output user interfaces 162–3

output devices/technologies 159–62

outsourcing 4, 222

ownership issues 85–6

PaaS (platform as a service) 102

parallel running 254–5

payback/break-even analysis 56–7

people change 45

perfective maintenance (optimisation) 262

phased implementation 255–6

physical data design 195

physical files, database management 183–6

physical models 123

physical process design 195–6

physical security 192

pilot implementation 255

platform-agnostic (logical) design 194–5

Platform as a service (PaaS) 102

point-to-point architecture 206

policies, architecture 210–11

political constraints 144–5

polymorphism, OO design 171, 172

post-implementation review 264–5

post-implementation review, role of business analysts 43

post-project review 264

pre-numbering 188

pre-UML modelling techniques 115–17

preventative maintenance 263

primary key 181

prioritisation of requirements 71–2

process 11

defined processes 94–6

empirical processes 96–100

process change 44–5

process controls 190–1

process design 163–72

high-level design 164–8

object-oriented design 169–72

unit/component design 168–9

procurement 81

programming constructs 167

programming and development approaches 79–106

build vs. buy 81–8

component-based development 88–91

development approaches 79–81

methodologies 92–100

software engineering paradigms 100–2

technological advances, influence of 102–4

program specifications 168–9

static testing 232

project and business risks 54–6

project constraints 144

project management tools 273

project manager 63

project sponsor 63

prototyping 66

qualitative techniques 65–6

quality 225–8

of a COTS solution 83–4

definition of 227–8

quality triangle 226

of requirements, constraints on design 146

see also testing

quantitative techniques 66–7

questionnaires 66

range checks 188

Rapid Application Development (RAD) 97

Rational Unified process (RUP) 31, 136

ready-made solutions

COTS 82–7

Open Source software 87–8

record searching 67

regression testing 235–6, 263

relational databases 180–2

release management 275–6

reliability 267

remotely delivered training 252

requirements catalogue 74–5

requirements engineering 9, 60–78

and Agile development 77–8

analysis of requirements 69–72

business analysis techniques 68–9

definition 60–1

documentation 73–6

elicitation 64–7

framework for 61–2

management 76–7

and off-the-shelf solutions 78

roles in 62–4

tools 273

validation of requirements 72–3

requirements specification, static testing 231

reviews

evaluative 264–5

static testing 231–3

RFID (Radio Frequency IDentification) 157

risk analysis 53–6

roles 11–12, 93

in architecture 220

requirements engineering 62–4

RUP (Rational Unified process) 31

SaaS (software as a service) 102, 103

scenarios 65–6

Schwaber, Ken 94

scope of design 149–63

scope of solution 213–14

breadth 213

depth 214

focus 213

Scrum 30, 99

SDLC see system development lifecycle

security 270

security and control design 186–94

clerical controls 188–9

data controls 189–90

input controls 187–8

output controls 188

process controls 190–1

security and audit 192–4

selection, programming construct 167

self-checking codes 177–8, 187

sequence, programming construct 167

sequential file organisation 184–5

sequential numbers, code design 176

serial file organisation 183–4

service level agreements (SLAs) 267

service management tools 276

service-oriented analysis 125

service-oriented architecture 207

service-oriented development (SOD) 101–2

shadowing 65

‘shared source’ software 88

SLAs (service level agreements) 267

SOD (service-oriented development) 101–2

software architects 220

software architecture 214–20

component-based 218–20

tiered 215–18

Software as a service (SaaS) 102

software development tools 274–5

software engineering, definition of 80

software engineering paradigms 100–2

software modules migration 248–9

software/system development methodologies (SDMs) 92–100

software tools

business modelling & architecture 272–3

functions and benefits 269–72

project management 273

release management 275–6

requirements engineering 273

service management 276

software development 274–5

system modelling 273–4

testing 275

solution architects 220

solution development tools 269–78

evaluation of 276–7

functions and benefits 269–72

pros and cons of adopting 277

terminology 276

through solution lifecycles 272–6

solution-related architectures 202–24

architecture patterns 203–6

communication patterns 206–7

enterprise architecture 207–10

management 222–4

principles 210–11

roles/stakeholders 220–2

software architecture 211–14

solution architecture 210–11

solution scope 213–14

special-purpose records 67

specification of software components 219

Spiral lifecycle model 25–6, 261–2

sponsor of project 63

spot checks 188

SSADM (Structured Systems Analysis and Design Method) 28–9, 95

SSM (Soft Systems Methodology) 95

stakeholders 145

architecture 221–2

standardisation 270

standards, constraints of 145

Statecharts, event modelling 117

static data model notations 115–16

static testing 230–3

stepwise refinement 166–7

storage 270

structured methods 96

structured programming (SP) 96, 100

Structured Systems Analysis and Design Method (SSADM) 28–9, 95

‘super-users’ 252–3

suppliers 222

surveys 66

system development lifecycle (SDLC) 8–34

Agile approaches 26–8

choice of 32–3

elements 10–13

evolutionary approaches 23–6

hybrid approaches 28–32

implementation in 242–4

linear approaches 17–23

maintenance 258–62

meaning of 13–17

position of systems design 146–9

stages of 9–10

system implementation 253–6

system interface layer 217

system lifecycle 14–15

system modelling techniques 107–38

abstraction 120–3

cross-referencing 131–4

documentation and specification 134–7

levels of models and model elements 125–31

modelling 111–14

multiple models and views 114–15

opaqueness of model elements 123–5

pre-UML modelling techniques 115–17

unified modelling language (UML) 117–20

system modelling tools 273–4

systems architecture 3

systems design 139–201

constraints upon 142–6

data design 173–86

design patterns 196–200

in development lifecycle 146–9

logical and physical design 194–6

objective of 139–42

process design 163–72

scope of design 149–63

security and control design 186–94

systems development 1–2

offshoring & outsourcing of 4

and other disciplines 2–4

systems development methodology (SDM) 92–4

defined processes 94–6

empirical process 96–100

system specification, modelling notation 134–6

system to system data interchange 163

system testing 234

system use cases (SUCs) 130–1

‘tailor-made’ (bespoke) solutions 81–2

tangible and intangible costs 52, 53, 54

technical constraints on system design 144–5

technical documentation 250

technical feasibility 41, 49

technical requirements 68

techniques 12–13, 94

technological advances 102–4

technology 80

test-driven development 99

testers 64

testing 9, 228–40

7 principles of 229

components 220

dynamic stages of ‘V’ model 233–5

in the lifecycle 237–9

objectives and limitations 228–31

progression through dynamic stages 236–7

regression 235–6, 263

re-testing 235

role of business analysts 42–3

static and dynamic 230

static stages of ‘V’ model 231–3

test plans 239–40

tools 275

three-tiered software architecture 216

three-view model of a system 114–15

tiered/layered software architecture 206, 215–18

tight and loose coupling, component architecture 204–5

time value of money 57, 58, 59

touch screen technology 156

traceability 77, 271

training 251–3

COTS software products 84

training needs analysis (TNA) 251

train-the-trainer 252–3

‘try before you buy’ 84–5

two-tier, client-server 215

UAT (user acceptance testing) 43, 234, 236

U-curve process pattern 110–11

Unified Modelling Language (UML) 104, 117–20

events 120

functionality 118–19

static data 119

Unified Process 4 + 1

architecture 136–7

unique identifiers, data design 175, 176

unit/component design 168–9

unit testing 234

usability 267

usability checklist 152–3

use cases 126–7

design scope 127

goal level 127–8

usefulness of models 108–9

user acceptance testing (UAT) 43, 234, 236

‘user-friendly’ checklist 152–3

user guides 250

user interface (UI) design 152–3

input Uls 156–7

output Uls 162–3

users 63, 222

user stories 76

validation of input data 187–8

validation of requirements 72–3

verification of input data 187

verification of requirements 72–3

version control 76, 270

views/viewpoints 110

visibility, data control 190

visual modelling 271

‘V’ model 19–21

dynamic test stages 233–5

extended ‘V’ model 20, 39, 266

maintenance 260

static test stages 231–3

and systems design 147–8

testing 238

voice recognition 157

Waterfall lifecycle 17–19

documentation 134–5

maintenance 259

systems design 146–7

testing 238

white-box techniques 235

white-box views 125

workshops 65

XP (Extreme programming) 99