Introduction and Overview

• Drawing diagrams to help us ask the right questions
• Dissecting UML 2 features
• An enterprise architecture: Information, Behaviour, Presentation
• Designing new or refining existing Web-enabled systems
• Exploring the Unified Process and the V-Model

Creating the Information Structure

Analysing information requirements

• Translating the business needs
• Structuring data with simplified UML class diagrams
• Establishing multiple or optional links
• Generalising and simplifying
• Connecting to legacy data systems

Achieving the best practice in data design

• Reducing redundancy with normalisation
• Developing the ontology
• Translating a data model to a relational database
• Managing data in a multitier Web-enabled environment
• Assessing design trade-offs

Formulating a physical data model

• Customising application and user views
• Partitioning data using packages
• Guaranteeing consistency and completeness
• The pros and cons of indexing with B-Trees
• Leveraging SQL Query Optimisers

Developing the Behaviour Model

Analysing behaviour requirements

• Scoping business behaviour with UML use case diagrams
• Realising a use case with a UML activity diagram
• Checking completeness and consistency
• Trading data complexity for control complexity

Determining best practice for application design

• Recognising UML stereotypes: process, boundary and entity
• Monitoring behaviour with UML communication diagrams
• Defining control using UML state charts
• Classifying stereotype responsibilities in SOAs
• Allocating behaviour in a Web-enabled environment

Forming the application architecture

• Managing application complexity
• Coupling and cohesion
• Creating congruent designs
• Matching process and data structure
• Measuring cyclomatic complexity

Presenting Component Objects to Users

Object-modelling techniques for analysis

• Assessing the benefits of an OO approach
• Mapping out structure at the user interface with detailed UML class diagrams
• Achieving consistency between UML class and communication diagrams
• Benefiting from inheritance as a consequence of generalisation
• Delegation arising from aggregation

Benefiting from best practice in component design

• Extending use case diagrams for user-interface design
• Generalising actors and use cases
• Detailing mandatory reusable functionality with <<include>>
• Describing optional functionality using <<extend>>
• Improving the design of user interfaces: prototyping and polymorphism

Finalising the detailed use case

• Reusing knowledge with design patterns
• Model Driven Architectures
• Knowledge management and ontology development

Achieving Optimum-Quality Results

Profiling the organisation

• Choosing appropriate personnel
• Matching the development approach to the organisational culture

Selecting the right software

• "Off the Shelf" vs. "Custom Build"
• Open source vs. proprietary
• Database solutions: Sybase, SQL Server, Oracle, MySQL
• Content management systems
• Benefitting from Web technologies