Requirements analysis and system design

651 Pages·2007·12.895 MB·English

by  Leszek Maciaszek

R 3rd
REQUIREMENTS ANALYSIS AND SYSTEM DESIGN
E edition
Q
Leszek A. Maciaszek 3rd edition
U
REQUIREMENTS
I
R
Strong analysis and design are crucial in the successful development of any enterprise information system.
E
This book will teach you the underlying theory behind designing large-scale object-oriented systems and
M
will show you how to put this theory into practice.
E ANALYSIS AND
The author strongly believes in the philosophy of ‘learning by doing’ and provides numerous examples, N
exercises and questions which allow you to try your hand at what you’ve just read and, in so doing, cement
T
your understanding. The book recognises and identifies the many challenges that software development S
can throw up and arms you with the practical knowledge and adaptability to overcome these issues. SYSTEM DESIGN
A
Key features N
l Seven recurrent case studies feature to put the theory into an applied context. The cases used are: A
university enrolment; video store; contact management; telemarketing; advertising expenditure; L
time logging; and currency converter. Each has their own unique features and educational benefits. Y
l Numerous exercises and questions help reinforce your learning. S Leszek A. Maciaszek
l Balanced blend of theoretical background and practical insight. IS
l Uses UML throughout.
A
New to this edition N
l Addition of review quizzes within chapters and multiple choice tests at the end of chapters add D
to your learning experience.

l New coverage of solution management frameworks (ITIL and COBIT) and system integration. S
Y
l New coverage of business process modeling.
S
l New coverage of Web GUI design.
T
l A comprehensive package of supporting materials, for both lecturers and students, is provided
E
on the companion website.
M
This book is the ideal companion for undergraduates studying: systems analysis; systems design;

D
software engineering; software projects; and databases and object technology. It would also be an
excellent reference for any practitioners wishing to get up to speed with the latest developments E
in this area. S
I
G
Leszek A. Maciaszek is a teacher and researcher as well as consultant, N
writer, industry trainer and organizer of conferences. His assignments
have included numerous corporations and institutions in countries on
M
four continents. He has authored about 120 positions (including several
a
books) related to systems development and integration, software c
engineering, databases, object technology, and distributed computing. ia
s
When not travelling, Leszek resides in Sydney where he is an Associate z
Professor at Macquarie University. e
k
3rd
edition
www.pearson-books.com
9780321440365_03_COVER.indd 1 22/5/07 09:28:59
RASD_A01.QXD 18/5/07 08:38 Page i
Requirements Analysis and System Design
Visit the Requirements Analysis and Systems Design, third editionCompanion
Website at www.pearsoned.co.uk/maciaszek to find valuable student
learning material including:
(cid:2) Printable lecture slides.
(cid:2) Model files for solutions to the case studies, the tutorial, and all other
modeling examples in the textbook.
RASD_A01.QXD 16/5/07 11:56 Page ii
We work with leading authors to develop the
strongest educational materials in computing,
bringing cutting-edge thinking and best
learning practice to a global market.
Under a range of well-known imprints, including
Addison Wesley, we craft high-quality print and
electronic publications that help readers to understand
and apply their content, whether studying or at work.
To find out more about the complete range of our
publishing, please visit us on the World Wide Web at:
www.pearsoned.co.uk
RASD_A01.QXD 16/5/07 11:56 Page iii
REQUIREMENTS
ANALYSIS AND
SYSTEM DESIGN
third edition
leszek a. maciaszek
RASD_A01.QXD 16/5/07 11:56 Page iv
Pearson Education Limited
Edinburgh Gate
Harlow
Essex CM20 2JE
England
and Associated Companies throughout the world
Visit us on the World Wide Web at:
www.pearsoned.co.uk
First published 2001
Second edition published 2005
Third edition published 2007
© Pearson Education Limited 2001, 2005, 2007
The right of Leszek A. Maciaszek to be identified as author of this work has been asserted
by him in accordance with the Copyright, Designs and Patents Act 1988.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval
system, or transmitted in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without either the prior written permission of the
publisher or a licence permitting restricted copying in the United Kingdom issued by the
Copyright Licensing Agency Ltd, Saffron House, 6–10 Kirby Street, London EC1N 8TS.
The programs in this book have been included for their instructional value. They have been
tested with care but are not guaranteed for any particular purpose. The publisher does not
offer any warranties or representations nor does it accept any liabilities with respect to
the programs.
All trademarks used herein are the property of their respective owners. The use of any
trademark in this text does not vest in the author or publisher any trademark ownership rights
in such trademarks, nor does the use of such trademarks imply any affiliation with or
endorsement of this book by such owners.
ISBN 978-0-321-44036-5
British Library Cataloguing-in-Publication Data
A catalogue record for this book is available from the British Library
Library of Congress Cataloging-in-Publication Data
A catalog record for this book is available from the Library of Congress

10 9 8 7 6 5 4 3 2 1
10 09 08 07
Typeset in 10/12 pt TimesNewRoman by 30
Printed and bound in Great Britain by Ashford Colour Press, Hampshire
The publisher’s policy is to use paper manufactured from sustainable forests.
RASD_A01.QXD 16/5/07 11:56 Page v
Brief contents
Contents for case studies xxi
Preface xxvii
Guided tour xxxiv
Publisher’s acknowledgements xxxvi
Chapter 1 The Software Process 1
Chapter 2 Requirements Determination 66
Chapter 3 Fundamentals of Visual Modeling 122
Chapter 4 Requirements Specification 169
Chapter 5 Moving from Analysis to Design 243
Chapter 6 System Architecture and Program Design 304
Chapter 7 Graphical User Interface Design 380
Chapter 8 Persistence and Database Design 441
Chapter 9 Quality and Change Management 490
Chapter 10 Tutorial-style Review and Reinforcement 521

Appendix Fundamentals of Object Technology 565
Bibliography 600
Index 607
RASD_A01.QXD 16/5/07 11:56 Page vi
RASD_A01.QXD 16/5/07 11:56 Page vii
Contents
Contents for case studies xxi
Preface xxvii
Guided tour xxxiv
Publisher’s acknowledgements xxxvi
1 The Software Process 1
Objectives 1
1.1 The nature of software development 2
1.1.1 The software development invariants 2
1.1.2 The software development “accidents” 4
1.1.2.1 Stakeholders 4
1.1.2.2 Process 6
1.1.2.2.1 Iterative and incremental process 6
1.1.2.2.2 Capability maturity model 7
1.1.2.2.3 The ISO 9000 family of quality standards 9
1.1.2.2.4 The ITIL framework 9
1.1.2.2.5 The COBIT framework 11
1.1.2.3 Modeling 12
1.1.2.3.1 Unified modeling language 13
1.1.2.3.2 CASE and process improvement 13
1.1.3 Devel opment or integration? 14
Review quiz 1.1 15
1.2 System planning 15
1.2.1 The SWOT approach 16
1.2.2 The VCM approach 17
1.2.3 The BPR approach 19
1.2.4 The ISA approach 20
Review quiz 1.2 21
1.3 Systems for three management levels 22
1.3.1 Transactional processing systems 23
1.3.2 Analytical processing systems 24
1.3.3 Knowledge processing systems 25
Review quiz 1.3 26
RASD_A01.QXD 16/5/07 11:56 Page viii
viii Contents
1.4 The software development lifecycle 26
1.4.1 The development approach 27
1.4.1.1 The structured approach 27
1.4.1.2 The object-oriented approach 28
1.4.2 Lifecycle phases 30
1.4.2.1 Business analysis 30
1.4.2.1.1 Requirements determination 31
1.4.2.1.2 Requirements specification 31
1.4.2.2 System design 32
1.4.2.2.1 Architectural design 32
1.4.2.2.2 Detailed design 33
1.4.2.3 Implementation 33
1.4.2.4 Integration and deployment 34
1.4.2.5 Operation and maintenance 34
1.4.3 Activities spanning the lifecycle 35
1.4.3.1 Project planning 36
1.4.3.2 Metrics 37
1.4.3.3 Testing 37
Review quiz 1.4 39
1.5 Development models and methods 39
1.5.1 The spiral model 40
1.5.2 IBM Rational Unified Process 41
1.5.3 Model-driven architecture 42
1.5.4 Agile software development 42
1.5.5 Aspect-oriented software development 45
Review quiz 1.5 47
1.6 Problem statements for case studies 47
1.6.1 University enrolment 48
1.6.2 Video store 48
1.6.3 Contact management 49
1.6.4 Telemarketing 50
1.6.5 Advertising expenditure 51
1.6.6 Time logg ing 51
1.6.7 Currency converter 52
Summary 53
Key terms 54
Multiple-choice test 56
Questions 58
Review quiz answers 60
Multiple-choice test answers 60
Answers to odd-numbered questions 61
2 Requirements Determination 66
Objectives 66
2.1 From business processes to solution envisioning 67
2.1.1 Process hierarchy modeling 68
RASD_A01.QXD 16/5/07 11:56 Page ix
Contents ix
2.1.1.1 Processes and process decompositions 68
2.1.1.2 Process hierarchy diagram 68
2.1.2 Business process modeling 70
2.1.2.1 Flow objects,connecting objects,swimlanes and artifacts 70
2.1.2.2 Business process diagram 72
2.1.3 Solution envisioning 73
2.1.3.1 Solution envisioning process 74
2.1.3.2 Implementation strategies and capability architecture 76
Review quiz 2.1 77
2.2 Requirements elicitation 77
2.2.1 System requirements 79
2.2.1.1 Functional requirements 79
2.2.1.2 Non-functional requirements 80
2.2.2 Traditional methods of requirements elicitation 81
2.2.2.1 Interviewing customers and domain experts 81
2.2.2.2 Questionnaires 83
2.2.2.3 Observation 84
2.2.2.4 Study of documents and software systems 84
2.2.3 Modern methods of requirements elicitation 85
2.2.3.1 Prototyping 85
2.2.3.2 Brainstorming 86
2.2.3.3 Joint application development 87
2.2.3.4 Rapid application development 88
Review quiz 2.2 89
2.3 Requirements negotiation and validation 89
2.3.1 Out-of-scope requirements 89
2.3.2 Requirements dependency matrix 90
2.3.3 Requirements – risks and priorities 90
Review quiz 2.3 91
2.4 Requirements management 91
2.4.1 Requirements identification and classification 92
2.4.2 Requirements hierarchies 93
2.4.3 Chang e management 93
2.4.4 Requirements traceability 94
Review quiz 2.4 94
2.5 Requirements business model 94
2.5.1 System scope model 95
2.5.2 Business use case model 97
2.5.3 Business glossary 99
2.5.4 Business class model 101
Review quiz 2.5 103
2.6 Requirements document 103
2.6.1 Document templates 103
2.6.2 Project preliminaries 104
2.6.3 System services 105