Introduction to Analysis & Design

Introduction

Frequently ignored in these days of "methods", are the basic job skills still required of analysts and designers. Technical training, "methods" or experience usually do not equip people to cope with information acquisition, problem solving, or the sociological, political and psychological aspects of software systems development. Of course, having mastered basic analysis and design skills, participants may well want to go on to study a modern "method" in detail. An ideal follow-up to this course would be Object-Oriented Analysis and Design using UML.

Duration and Construction

The course lasts two days. Each day will start at 09.30 and finish at 16.30. The delivery is via lecture, exercise and discussion.

The days consist of two morning sessions and three, shorter afternoon sessions, with one hour for lunch. Time will be available after 16.30 for extended discussions or related issues.

Intended Audience

Participants will be involved in the analysis and design of software intensive systems. They may have attended, or are considering attending, a course on an analysis or design "method". They will have realised that whilst "methods" bring needed rigour and repeatability they offer no guidance and training in the basic analysis and design job skills.

Aims

To understand the human factors that influence and distort a specification and to have begun thinking about how to deal with them
To be aware of the possible sources of input to the analysis phase and the way in which they are best used
To have practised skills such as neutral questioning, active listening and meeting discipline and facilitation
To have begun practising modelling and abstraction
To appreciate the designer's mental state and to have begun to practise an awareness of fitness, style and feel

Deliverables

Lectures
Facilitation of discussions
Direction, assistance and feedback on exercises
Proposed solutions to the exercises
Copies of lecture slides, plus explanatory text and summaries
Reference list of books and sources

Numbers

We recommend that there are no more than 12 participants, with the best results usually obtained when there are at least 8 participants. It is possible, by negotiation and mutual agreement, for more than 12 participants to be present.

What is systems analysis? It's often not analysis, and it rarely involves analysing systems
Investigation techniques
Modelling and abstraction
People as sponsors, users and influencers
What is design? How much can we engineer? Do imagination, intuition and other such skills remain, and where?
Technological influences
Modelling and documentation

Site Requirements

Data projector of at least 1024 x 768 resolution, and suitable screen
White-board, preferably not doubling up as the OHP's screen; blackboard and chalk are acceptable
Flip-chart and easel, with additional flip-chart paper
It is best if the seating is not fixed. Auditorium style seating, for example, makes it difficult to switch from lecture to group work.

Contacting

Please contact Matrice by telephone on +44 7010 704705; by fax on +44 7010 704706; by emailing bookings@matrice.co.uk; or by visiting http://www.matrice.co.uk