LIST OF FIGURES AND TABLES

Figure 1.1 The main stages of systems development
Figure 1.2 Systems development in a wider context
Figure 2.1 The main stages of systems development
Figure 2.2 Elements of the system development lifecycle
Figure 2.3 The Waterfall lifecycle
Figure 2.4 The ‘V’ model
Figure 2.5 The extended ‘V’ model
Figure 2.6 The Incremental lifecycle
Figure 2.7 The Iterative lifecycle
Figure 2.8 Boehm’s Spiral lifecycle
Figure 2.9 Evolution of Agile
Figure 3.1 POPIT™ model (© Assist Knowledge Development)
Figure 3.2 The extended ‘V’ model
Figure 3.3 Business analysis process model
Figure 4.1 The business case in the lifecycle of an IT project
Figure 4.2 Aspects of feasibility
Figure 4.3 Option selection
Figure 4.4 Categories of costs and benefits
Figure 5.1 A framework for requirements engineering
Figure 5.2 Roles in requirements engineering
Figure 5.3 Contents of a requirements document
Figure 5.4 Example of a user story from an inventory management system
Figure 5.5 Traceability
Figure 6.1 Development approaches: schematic overview
Figure 6.2 Advantages and disadvantages of the COTS approach
Figure 6.3 Integrated components forming a sales order processing solution
Figure 6.4 Definition of the iOrders interface
Figure 6.5 UML deployment diagram showing a component-based solution
Figure 6.6 Elements of a systems development methodology
Figure 6.7 The MDA process
Figure 7.1 The U curve
Figure 7.2 The three-view model of a system
Figure 7.3 Data flow diagram
Figure 7.4 Entity relationship diagram (Everest’s ‘crows foot’ notation)
Figure 7.5 Statechart (Harel)
Figure 7.6 UML diagram types
Figure 7.7 BookStack Mountain stock management system – use case diagram
Figure 7.8 Activity diagram for ‘record movement’ in use case
Figure 7.9 Sequence diagram (incomplete)
Figure 7.10 Class diagram used purely to model static data
Figure 7.11 State machine for a BookStock instance
Figure 7.12 Generalisation and specialisation in class diagram and Barker Ellis ERD form
Figure 7.13 Books composed of chapters (UML)
Figure 7.14 BookStack Mountain – context diagram
Figure 7.15 BookStack Mountain – system use case diagram
Figure 7.16 The Functional model map and development activities
Figure 7.17 Functional model map, populated with typical use case types
Figure 7.18 Functional model map, populated with diagram types selected for a specific project
Figure 7.19 CRUD matrix – mapping use cases to classes
Figure 7.20 Functional model map, overlaid with traceability paths from requirements to code
Figure 7.21 Unified Process 4 + 1 architecture
Figure 8.1 Objectives of systems design
Figure 8.2 Constraints upon systems design
Figure 8.3 The place of design in the Waterfall SDLC
Figure 8.4 The place of design in the ‘V’ model SDLC
Figure 8.5 The place of design in the Incremental SDLC
Figure 8.6 The place of design in an Iterative SDLC
Figure 8.7 Key elements of a computer system
Figure 8.8 Use case diagram for a sales order processing system
Figure 8.9 Stages during data input
Figure 8.10 Simple module chart for a stand-alone system
Figure 8.11 High-level design showing separate components and their interfaces
Figure 8.12 UML class diagram showing a detailed definition of an interface
Figure 8.13 Structure chart showing the de-composition of the Place Order module
Figure 8.14 Activity diagram specification of the Enter Customer Details module
Figure 8.15 Pseudocode specification of the Enter Customer Details module
Figure 8.16 Definition of an order object
Figure 8.17 Class model showing abstraction (generalisation) and polymorphism
Figure 9.1 Spreadsheet showing un-normalised data
Figure 9.2 Normalised data structures
Figure 9.3 Example of a faceted code (UK vehicle registration number)
Figure 9.4 Example of a self-checking code
Figure 9.5 Example of a hierarchical database structure
Figure 9.6 Example of a network database structure
Figure 9.7 Example of a relational database structure
Figure 9.8 Example of a result set from joining relations
Figure 9.9 Example of an object database structure
Figure 9.10 Example of a serial file organisation
Figure 9.11 Example of a sequential file organisation
Figure 9.12 Example of an index file
Figure 9.13 UML state machine diagram showing the lifecycle for an invoice object
Figure 9.14 UML deployment diagram showing physical components
Figure 10.1 Architecture domains in enterprise architecture
Figure 10.2 Hierarchical domain services
Figure 10.3 Solution scope – focus, breadth and depth
Figure 10.4 Client-server patterns
Figure 10.5 Three-tier software architecture with components shared across clients
Figure 10.6 N-tiered software architecture
Figure 11.1 The quality triangle
Figure 11.2 Static and dynamic testing in the ‘V’ model lifecycle
Figure 11.3 Dynamic testing
Figure 11.4 Testing in the lifecycle
Figure 12.1 Implementation in the lifecycle
Figure 12.2 Data creation and data conversion
Figure 12.3 Data mapping
Figure 12.4 Migration of software modules
Figure 13.1 Maintenance in the Waterfall lifecycle
Figure 13.2 ‘V’ model lifecycle
Figure 13.3 The ‘b’ model of systems development
Figure 13.4 Spiral lifecycle (Boehm)
Figure 13.5 Extended ‘V’ model showing benefits realisation stage
Figure 14.1 Areas covered by solution development tools
Table 4.1 Example of a payback calculation
Table 4.2 Example of a discounted cash flow or net present value calculation
Table 6.1 Common defined (procedural) methodologies and frameworks
Table 6.2 Common Agile methodologies and frameworks
Table 8.1 Common input technologies
Table 8.2 Common output technologies
Table 9.1 Common design patterns (after Gamma et al.)
Table 10.1 Features of loose and tight coupling
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset