Requirements Categorisation

["John Merrells" <merrells@xxxxxxxxxxxx>]

Yesterday, Tim Howes suggested that there were four or five broad
categories into which our requirements could be disected.  I've taken
the list of requirements, removed the duplicates, and broken them
down into the groups Tim suggested.

Our architecture proposal will address groups A & B & C.

John


A) ----------- Replication Model -----------

2.4) SHOULD update any unavailable replica when it comes back online.

3) All changes MUST eventually be applied to all Replicas.

4) MUST be interoperable.

9.1) MUST allow scheduled replication.

10.2) Replication Policy MUST allow definition of replication content.

10.4) SHALL allow 'number of changes' Replication Policy .

11.1) MUST support Multi-master.

11.2) MUST support Master-Slave.

14) Master and Replica data SHALL be identical.

15.1) SHALL NOT ensure all Replicas are complete copies.

15.2) SHALL encompass common schema objects and attributes,

16) SHALL define subtree replication (X.525 section 7.2)

26.2) SHOULD support 'every X hours' schedule

26.3) SHOULD support 'every N changes' schedule

27) SHALL support immediate replication of critical attributes.

29) MUST have Replication Agreements.

32.1) MUST scale to internet.

32.2) MUST function in enterprise.

33.1) MUST detect and resolve update conflicts in multi-master topology.

34) SHALL allow replication with any LDAP server on network

B) ----------- Replication Protocol -----------

2.1) MUST be resource efficient.

5.1) MUST authenticate identity of replication partners.

5.2) MUST transfer updates securely.

6.2) MUST recover if a replication party fails during update.

12.1) MUST allow total update.

12.2) MUST allow incremental update.

12.3) MUST allow updates to multiple replicas

13.1) MUST allow either master or replica be initiator

13.2) MUST allow initiator to determine if it is a supplier or consumer.

20) MUST NOT saturate network.

23) SHOULD support transactions.

24) SHALL purge change information after replication.

C) ----------- Replication Agreements -----------

7) MUST provide LDAP access to replication agreements.

17) SHALL store Replication Agreements as entries.

D) ----------- Administration And Management -----------

1) Replication MUST be simple to configure and maintain.

2.2) SHALL allow replication to be postponed.

2.3) SHALL allow user initiated replication.

8) MUST maintain audit log.

33.3) MAY store conflicts to allow user intervention.

35) MUST allow LDAP access to replication topology.

36) SHALL allow diff of Replicas.

37) SHALL allow view of replication topology from single server.

38.1) SHALL report state of each replica.

38.2) SHALL report replication history of each replica.

39) SHALL allow user intervention to resolve conflicts. (Conflict with MAY in 33.3)

E) ----------- Other -----------

25) Replication policies SHOULD contain clauses to account for the
instance of a replica being unavailable at the scheduled update time.

6.1) MUST deal with differing schema

15.3) MAY define a mapping between divergent schemas for non-common schema objects and attributes.


--
John Merrells
Netscape Communications
Directory Server
Software Engineer

http://people.netscape.com/merrells