Get documents about "design_review
Document Sample
Library Management System Version: 1.0
Design Review Checklist Date: 2-Apr-2002
Library Management System
Design Review Checklist
Version 1.0
Thursday Team
Dated: 9th April 2002
Authors
Venkat Subramanian Vs4433@albany.edu (Leader)
Weiwei Miao Weiweimiao@Hotmail.Com
Jiaoheng Meng Mengjj@Hotmail.Com
Zhenyu Dai Zhenyud@Hotmail.Com
Xiaoyu Zheng Xyz_Bupt@Yahoo.Com.Cn
Lanli Yang Lanliyang@Yahoo.Com
Revision History
Date Version Description Author
9th April 2002 1.0 First version Design Team
-
Confidential CSI 518 : Thursday Team Page 1
Library Management System Version: 1.0
Design Review Checklist Date: 2-Apr-2002
A. PRESENTATION AND COVERAGE ASPECTS
Item Yes / No / NA
1. Are all mandatory sections present in the OOADD? If not, is there a reasonable yes
explanation for their absence?
2. Have all mandatory diagrams (Use Case, Class, Collaboration, Sequence, yes
Deployment and Component diagrams) been included?
3. Have symbols and notations been used consistently? yes
4. Have all the required I/O formats (Forms, Reports, Screens etc.) been enclosed? Yes
(no reports in
system)
5. Has the Requirements traceability matrix been included? no
6. Have all assumptions and dependencies been explicitly stated? Are these realistic yes
and reasonable?
7. Does the analysis / design depends upon any assumptions made about the system yes
that have not been explicitly stated? Are such assumptions acceptable?
B. ARCHITECTURE DESIGN
Item Yes / No / NA
1. Are the conventions followed consistent with the methodology adopted? yes
2. Does the standards and conventions followed are customer / product vendor (such yes
as MFC standard by Microsoft) specific? If so, Is the same stated in the OOADD
and followed consistently?
3. (optional) For distributed objects, is the standard that is followed (such as -
CORBA, DCOM) specified?
4. If there are any deviations from specified formats, are they stated and are they -
acceptable?
5. Is there complete information about the target system environment? NA
6. Is the development environment fully compatible with the target environment? If Yes
not, is there a viable plan for porting development outputs to the target system? (java is portable
to any platform)
7. Have all design constraints been identified? Are they acceptable? yes
8. Are design constraints consistent with what is stated in the SRS? yes
9. Does the design incorporate the century check for year 2000 compliance ? yes
C. LOGICAL DESIGN
Item Yes / No / NA
1. Does the deployment diagram represent a good overview of the proposed system? na
2. Is there complete information available about interfaces with different external na
systems? (It is mandatory to know at least the following : identity of the system,
type of interface, contents, media, formats, timing, protocols etc )
3. Have the dependencies/connections/communications between the system yes
components outlined in the SRS been translated into appropriate interfaces
(packages/sub-systems)?
4. Are the concurrency needs identified and handled in the design? na
5. Has an attempt been made to simplify all interfaces? na
6. Is there a correspondence between SRS requirements and use cases identified in yes
the use case diagram?
Confidential CSI 518 : Thursday Team Page 2
Library Management System Version: 1.0
Design Review Checklist Date: 2-Apr-2002
Item Yes / No / NA
7. Is the description of each use case complete, consistent and correct? Has an effort yes
been made to include existing components (developed for other projects)?
8. Is each use case identified is represented by one or more classes in the OOADD? yes
9. Is each class identified in the OOADD linkable with a use case? yes
10. Have the classes been named as per naming conventions? yes
11. Is there complete information available about the class hierarchies? yes
12. Have all defined classes been instantiated at least once? In turn, have all objects yes
been defined by the classes?
13. Are the Collaborations among the classes identified and represented? yes
14. Is the number of messages passed between classes within reasonable limits? yes
15. Is there complete information about every interface with external systems? Can yes
the data structures be linked with user reports and screens?
16. Have the size and composition of data structures been estimated? Have provisions na
been made to guard against overflow?
17. Has a data dictionary been established? Can it be used to define data design? Will na
it facilitate impact analysis of a change?
18. Does the design specify clearly what data has to be backed-up and when? Does it no
specify procedures for restoration?
19. Have storage requirements been estimated (for whatever period has been stated in no
the SRS)? Do they take into account peak loads?
D. USER INTERFACE DESIGN
Item Yes / No / NA
1. Have screens and reports given by the customer been retained without change in yes
the design? If not, is there a good explanation for the change?
2. Is a separate interface required for the System Administrator / Manager? If so, has no
this been properly defined?
3. Are the screens as per Company/customer standards? yes
4. Is there standardization in the following? yes
appearance / structuring of screens
usage of function keys
availability & appearance of icons (in case of a GUI based application)
5. Is there complete information available about the hierarchical organization of yes
screens?
6. Does the design facilitate easy addition/deletion/modification of screens, in terms yes
of the following ?
screen layout
options on the screen
menus available
field layout, etc.
7. Have provision been made to check for date century compliance? yes
8. Is there complete information available about the action associated with each yes
option available on different screens / menus?
9. Is there complete information available about fields on various screens? (It is no
mandatory to know the type, width, source, editing associated with each field)
10. Is there a direct association between screens and use cases identified in the use yes
case diagram?
11. Is there standardization in the appearance / structuring of reports? na
Confidential CSI 518 : Thursday Team Page 3
Library Management System Version: 1.0
Design Review Checklist Date: 2-Apr-2002
Item Yes / No / NA
12. Is there complete information available about reports? (It is mandatory to know yes
details such as Layout, content, periodicity, distribution, presentation details etc )
13. Does the design facilitate easy addition/deletion/modification of reports? na
14. Is there a direct association between screens and processes identified in the yes
process model?
15. Do the screen designs accommodate the Year 2000 date check ? yes
E. DATA DESIGN
Item Yes / No / NA
1. Has every logical data structure been converted into appropriate physical yes
structures in the OOADD?
2. Has the path for storage of each file/table been specified clearly? na
3. Have databases and directories been named as per naming conventions? na
4. Is there complete information about table/record layouts in terms of column/field yes
names, referential integrity details, edit/validation conditions, keys/indexes etc?
5. Has a structured process been followed in identifying Primary and Foreign keys? yes
6. Are secondary keys used to the minimum possible extent? yes
7. Are the indexes used in the tables/files defined in the OOADD? na
8. Does the design facilitate modification of table/record layouts? yes
9. Is there complete information about database/table associated items like views, no
triggers, stored procedures, data definition language procedures etc.?
10. Has a structured process been followed in defining views and triggers? na
11. Has an attempt been made to reduce the number of views and triggers? na
12. Does the design facilitate easy modification or re-definition of views and triggers? yes
13. Is there complete information about administrative details like security and access na
rights, administrative procedures, record locking etc.?
14. Does the system provide for different types of users in terms of privilege levels? na
15. Is there complete information about database/file system interface? na
16. Are the data elements in a file closely related to each other and relevant to the file yes
they are contained in?
17. Have efforts been taken to minimize excessive duplication of variables and data- yes
structures?
18. Are all data structures initialized properly? yes
19. Have storage requirements been estimated (for whatever period has been stated in na
the SRS)? Do they take into account peak loads?
20. Have appropriate actions taken at data design level for year 2000 date compliance? yes
F. YEAR2000 COMPLIANCE ASPECTS
Item Yes / No / NA
1. Is there an impact of Year2000 compliance on this document? If yes, has this No impact
compliance been ensured in all aspects?
Note : NA refers to not applicable in the context of the application under review.
Confidential CSI 518 : Thursday Team Page 4
