Sunteți pe pagina 1din 17

Distributed Application

Critical Design Review (CDR) Checklist

Confidentiality Statement
This <document title> along with all attachments hereto shall be considered <company>s Proprietary/Confidential Information

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Evaluate the software system design according to the items in this Review Checklist. All items must be evaluated according
to whether they meet requirements or will otherwise ensure acceptable functionality of system, with ratings being (a)
satisfactory, (b) passable with modification recommended, or (c) in critical need of modification. Check the appropriate box
for each item. All items should be treated as points for discussion leading to an evaluation and do not require explicit
answers in the Comments field. Items may be skipped or deemed N/A at the discretion of the Review Team.
The design must pass this Review and formal approval must be obtained before full-scale development of the system can
proceed.
System Name/ID:
Date of CDR:
CDR Participants:

Position
ProjectManager
ExecutiveSponsor
BusinessSystem
ArchitectureTeamLead
TechnicalArchitecture
TeamLead
ApplicationDevelopment
TeamLead
BusinessAnalystTeam
Lead
DatabaseAdministrator
BusinessArea
Representative

2007 gantthead.com

Name

Email

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 1: Overall Application


Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Howwellisthe
businesssolution
implementedby
thedesign?
Hasthedesign
evolved
accordingto
requirements?
Overallhigh
levelarchitecture
design
Arethere/have
therebeen
demonstrable
design
prototypes?

2007 gantthead.com

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 2: Performance, Scalability, and Availability


Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Transaction
processing
architecture
Loadbalancing
acrossservers
Pointsoffailure
and
backup/recovery
procedures
Preventionof
bottlenecksinthe
architecture
Howwillthe
systemperform
fortheexpected
volumeoftotal
users?
Isthereadequate
capacityforthe
expectedvolume
ofconcurrent
users?
Isthesystem
capableof
accommodating
uservolume
growthovertime?
Security
2007 gantthead.com

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Singlelogon
support
Accessto
intersystem
passwords
Arerestrictions
ondatasupported
atrequiredlevels
ofgranularity
(tablelevel,
systemlevel,row
leveland/or
objectlevel)?
Willusersalways
haveaccessto
theirowndata?
Aresecurity
groups
supported?What
privilegesdothey
have?Howare
theycreatedand
administered?
Encryption
mechanisms
Isthereawayto
passcredentials
between
componentsor
layersofthe
architecture?
2007 gantthead.com

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Critical
Needs
Modification

Comments

Howsecureis
useraccount
information?
Section 3: Application Development
Review
Item

Satisfactory

NonCritical
Modification
Recommended

Isanon
proprietaryor
mainstream
programming
languageused?
Whatisthe
runtime
environment?
Aretheremultiple
clientplatforms?
Arethey
homogeneous?
Dospecial
interfacesneedto
bebuilt?Are
theremultiple
typesof
components
supported?

2007 gantthead.com

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Howis
configuration
management
addressed?Is
thereacode
repository?
Aredebuggers
available?
Dodevelopers
needtomodify
externalsystem
components?
Will
modificationsbe
trackedand
documented?
Aretherecustom
API's?Howdo
theyintegrateinto
thearchitecture?
Arebusinessrules
externaltothe
architecture?Is
therearules
engine?
Arethe
constituent
programmodules
designedwith
consistency?
2007 gantthead.com

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Areprogram
module
boundarieswell
defined?
Doesthedesign
havelow
complexity?
Willthesoftware
bemaintainable?
Iseachmodule
designedtobe
minimally
impactedby
changesinother
modules?
Isthedesign
lean?Areallof
itspartsstrictly
necessary?

2007 gantthead.com

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 4: Object and Information Management


Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Howareobjects
stored?
WhatDBMS'sor
ODBMS'sare
used?
Howareobjects
accessed?
What
mechanismsare
thereforpurging/
archiving/
restoringdataand
objects?
Howare
persistentobjects
implemented?
What
mechanisms
handleupdates,
performance
monitoring,
currencycontrol
andlocking?
Howarebusiness
transactions
implementedon
thepersistent
objects?
2007 gantthead.com

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Isobjectlocking
optimistic,
pessimisticor
neither?
Whatdata
structuresare
usedtorepresent
objects?
Canyouaddor
extendbusiness
objectsofthe
architecture?
Canyouinclude
externaldata
objects?
Isthedatabase
documentedusing
adatamodel,
objectmodel,or
neither?
Aretablesusedto
representobjects?
Whatnonobject
dataisstoredin
thedatabase?
Howdoyou
accessandupdate
thehostdata?

2007 gantthead.com

10

gantthead.com

Review
Item

Distributed Application Critical Design Review (CDR) Checklist

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Arethererisks
involvedwith
updates?
Isthereadata
conversion
needed?Isthere
anyplanningfor
it?

2007 gantthead.com

11

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 5: Communication
Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Whatnetworking
protocolsare
supported?
Istheresupport
forremoteusers?
Istheresupport
forInternet
access?

2007 gantthead.com

12

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 6: Operations, Administration and Maintenance (O, A & M)


Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Isvendorsupport
providedforthe
databases,
components,
clientsoftware
andserver
software?
Howarenew
releases
maintained/suppo
rted?
Howarereleases
tested?
Howarereleases
movedinto
production?
Canareleasebe
abortedif
necessary?
Aremultiple
databasesneeded
fortest
environments?
Isitpossibleto
replicatethe
production
environmentina
testing
environment?
2007 gantthead.com

13

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Isitpossibleto
makeindividual
codechanges?
Willusersbe
negatively
impactedbynew
releases?
Arethere
dependencies
between
componentsof
thearchitecture
thataffectnew
releases?
Isitpossibleto
troubleshootan
error?
Howareuser
errorsreported?
Aresystemerrors
loggedtoa
central
repository?
Istherea
mechanismfor
certifyingthe
finished
application?
Isthereabatch
componenttothe
environment?
Arethebatch
procedures
documented?
2007 gantthead.com

14

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 7: User Interface


Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Overallqualityof
usabilityfeatures:
intuitiveness,
consistency,
onlinehelp,
integrationwith
windowing
system,skilllevel
adaptability
Isthescreen
navigation
documented?
Isusersession
contextsaved
betweensessions?
Doonline
transactionsmap
tologicalunitsof
workcommitted
onthedatabase?
Isthescreenflow
controlledbythe
userratherthan
thesystem?
Areerror
condition
messages
informative?
2007 gantthead.com

15

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Cantheinterface
becustomizedby
users?
Section 8: Integration with Other Business Systems
Review
Item

Satisfactory

NonCritical
Modification
Recommended

Critical
Needs
Modification

Comments

Withwhatother
systemsdoesthis
architecture
integrate?
Areintegration
adaptersneeded?
Howis
communication
withexternal
systems
achieved?
Canexternal
systemsaccess
thissystem?
Willchangesin
externalsystems
affectthis
system?
Doesthissystem
accommodate
externalsystems
whenthose
systemsare
down?

2007 gantthead.com

16

gantthead.com

Distributed Application Critical Design Review (CDR) Checklist

Section 9: Approval/Rejection of Design


______ The [SYSTEM NAME/ID] has passed this Critical Design Review. It is approved for Development.
______ The [SYSTEM NAME/ID] has not passed this Critical Design Review. It is not approved for Development.
The following Issues must be resolved:

Additional Recommendations:

Signature of Executive Sponsor or Sponsor Representative

2007 gantthead.com

17

S-ar putea să vă placă și