Requirement :: Signature Technologies - Leader In Bespoke Software Development

site map

disclaimer

Our Approach
Architecture

Project Management Framework

Requirement

Development Process

Quality Assurance

User Interface design

Requirement

Every great system starts with the successful identification and communication of requirements. Basically, we need to work out what the system should do for the users. Requirements can be functional (e.g. what information we need to show in a specific report) or technical (e.g. what the 'up time' of the system should be).

Signature uses a variety of methods to identify and communicate requirements, including user stories, UML use cases and activity diagrams (explained below). As systems vary in scope, team size and team location, we believe it is important to select the most appropriate methods for each system.

UML Use Cases User stories Acitivity diagrams

Requirements are reflected in
a 'use case'. A use case is a
description of the interaction
between the user and the
system and forms the starting
point of the planning, testing
and development process. User stories serve the same
purpose as use cases but
there are some differences.
User stories are used to
create time estimates for the
release planning meeting.
They are also used instead
of large requirements
documents. User stories are
written by the customer as
things the system must to
support their processes.
User stories also drive the
creation of the
acceptance tests. Activity diagrams can be used to
model business processes and
logic. They help communicate
the flow of both physical and
electronic activities through
a diagram rather than words.

Printed version

Registered in England, Company Number 4585741 Registered Office: 1 Lyric Square, Hammersmith, London W6 0NB