ADDRESS DEVELOPMENT / CONSTRUCTION TASK PLAN WORK PRODUCTS

CHECKLIST

COMPLETED (Y,
TASK PRODUCT N/A, N) LOCATION / COMMENTS
***************************************************************
DESIGN/CONSTRUCTION-PHASE II
***************************************************************
SCOPING
Preliminary Model QA QA'd Model
Review Analysis Documentation Session Notes
Incorporate Analysis Changes Updated Model
Change Requests
Plan/Conduct SubSystem Specific Training Scheduled Training
Training Materials
Develop SubSystem Context Diagram Prelim SubSystem
Context Diagram
Develop Preliminary Workflow (Function Level) Prelim Workflows
Session Notes
Prepare Prelim. SubSystem Architecture Diagram Application Architecture
Diag
Identify 3rd Party Software Needs Identified 3rd Party SW
Needs
Identify Hardware Needs Identified HW Needs
1st Milestone Preparation Check List
*** 1st Milestone Issue Report for Teams

ON-LINE PROTOTYPING
Develop First Prototype (Window Only) 1st Prototype
Session Notes
**2nd On-line Milestone Issue Report for Teams
Print outs of windows and
dialog boxes
Check List
GUI Design Checkpoint (Prelim) GUI Design Review
Capture Specific Window Functionality Session Notes
Comments in PrADs
Develop Second Prototype (Navigation) 2nd Prototype
Navigation Diagram
Session Notes
Prepare Preliminary Data Access Paths PADs and CABs
Develop Third Prototype (Data Access) 3rd Prototype
Session Notes
3rd Milestone Preparation
** 3rd On-line Milestone Issue Report for Teams
Check List
Generated Executable
Enhance GUI Design Window Design & Client
PrAD

Page 1
 ADDRESS DEVELOPMENT / CONSTRUCTION TASK PLAN WORK PRODUCTS
CHECKLIST

COMPLETED (Y,
TASK PRODUCT N/A, N) LOCATION / COMMENTS
Session Notes
Perform GUI/Code Peer Review (Technical) GUI Checklist
GUI Design Review
Develop Preliminary On-line Help Requirements Memo
Help Tags
Develop User Help Text Help Text
BATCH DESIGN
Develop First Pass Batch Specifications Module Specification
-Structure
**2nd Batch Milestone Issue Report for Teams
Check List
Add Program Flow to Specifications Updated Specs-Flow
Session Notes
Prepare Preliminary Data Access Paths PAD
Add Data Access to Specifications Updated Specs-Data
Access
PADs
** 3rd Batch Milestone Issue Report for Teams
Check List
Perform Batch Spec Review (Technical) Code Check List
Approval
Add Basic Business Rules to Specification Updated Spec -Business
Rules
CROSS TEAM TASKS

Prepare Data Requirements Data Conversion Team

Sign Off Sheet
Prepare Detail Interface Design Interface Team Sign Off
Sheet
Define Internal Dependencies Internal Dependencies
Discovered Issues
Prepare Final Data Access Path Requirements Generated SQL
Refined PADs
DETAIL DESIGN

Identify Security Requirements Security Requirements

Identify Audit Requirements DB Action vs. Audit Req
Matrix
Identify Controls Requirements Controls Report Layouts;
Control Rqmt
Documentation
Develop Program Specs for Complex Processing Process Specifications
Identify Transaction Recovery Recovery Approaches
Develop Detail Transaction Volumetrics Process Freq Volumetrics
Table

Page 2
 ADDRESS DEVELOPMENT / CONSTRUCTION TASK PLAN WORK PRODUCTS
CHECKLIST

COMPLETED (Y,
TASK PRODUCT N/A, N) LOCATION / COMMENTS
Develop System Operating Expectations Response Time
Estimations
Refine Scoping Work Products Context Diagram, Appl.
Architecture Diagram
*** Major Milestone - Confirm Scope/Deliverables - Signoff
Check List
Required

Page 3
 HIGH-LEVEL PRE-DESIGN CHECKLIST

Notes: This Design Milestones Review Checklists contains four worksheets. The first worksheet, "Design
Milestones", lists the major design tasks/milestones during specific stages within the Design/Construction Phase.The
three other worksheets, "High-Level Pre-Design", "Technical Requirements", and "Documentation and User
Interface", list actual design activities. Include any other design activities that suit your particular business
environment and situation. Accuracy and detail create real value when using this document.
VERIFIED (Y,
DESIGN FACTOR N/A, N) COMMENTS

Design Requirements Compliance

Design Review clearly identified all assumptions
and problems with the requirements, such as
missing functions, extraneous functions, and
imprecise, ambiguous, or incorrect functions.

Deviations and other major design decisions from

the requirements have been documented and
approved.

The design adequately addresses the following:

Security and privacy issues
Real-time requirements
Performance issues (memory and timing)
Spare capacity (CPU and memory)
Maintainability
Understandability
Database requirements
Loading and initialization
Error handling and recovery
User interface issues
Software upgrades
Dependencies on other functions, Operating
system kernel, hardware, etc.
Design constraints, such as memory and
timing budgets
Requirements for error checking, error
handling and recovery
Pre-Design Considerations
Ensure that the following system specifications
are documented:

Desired screen resolution (800x600,

1024x768, etc.)
Screen Size (15", 17", 21")
Preferred Font and size (Arial 10, Times New
Roman 12, etc.)
Target Windows version for each client
computer in the system (XP, 2000, NT 4.0,
98, etc.)
Target computer Operating System if not a
Windows Platform - Apple, Unix, etc.
Target workstation hardware for all client
stations
Processor – Pentium, AMD K6, etc.
 Clock speed – 800, 1000, 1333, 1500,
2000, etc. MHz
Hard drive space – 10...40, etc. Gbytes
RAM – 128, 256, 512, etc. Mbytes
If a network application, which network and
version? – XP, Windows 2000, NT 4.0, Novell
3.1, Novell 4.11, etc.
If available, provide a network configuration
diagram with paths to server (where database
will reside) and all clients, security/user
groups, etc.
Target audiences are properly identified and their
needs addressed, including any special
considerations they may require.
A statement of design objective has been
developed, documented and approved to serve as
guideline of desired performance.
The design contains a clearly defined purpose
that matches target audiences’ needs, the
program objectives, and cost-benefit.
Design scope is properly aligned with the overall
program objectives and maintains an appropriate
balance between "must-have" and "nice-to-have"
design goals.
The design objective "anticipates" target
audiences’ concerns, problems, and questions
and addresses them.
The system should support, extend, supplement,
or enhance the user’s skills, background
knowledge, and expertise ----not replace them.

The design is compliant with agreed industry-

standard methods of program development and
delivery.
Design has been tested for clarity and
comprehensibility.
Design addresses clear mechanisms for future
reforms and reusability.
System design takes into account unusual
contingencies.
The design follows established notation
conventions and other compliance standards.
The design been communicated to and approved
by the development team and other stakeholders,
and any risks noted in the Risk Management
section of relevant design documents.
Cost and Business Concerns

Estimated costs and cost constraints effectively

comply with the main purpose of the system.

Metrics are designed and built consistent with the

expected results of implementing the designs
directly into the system.
The following business considerations are
accurately determined:
Desired delivery date or proposed project
schedule
Success and failure criteria
Use cases - Clearly describes how each
group of users will be using the system.
General business process - Web user will buy
a product, Web user will add a customer,
Web user will add contact information, etc.
Input/Output - Web users will enter data into
forms, administrator must run many
management reports, administrator needs to
export to Excel and text, etc.
Frequency of activity - many times each day,
daily, weekly, etc.
Cycles of activity - weekly sales reports to all
sales managers, close books at end of year,
etc.
st worksheet, "Design
Design/Construction Phase.The
ocumentation and User
ur particular business
cument.

SEE DOCUMENT
 TECHNICAL REQUIREMENTS DESIGN CHECKLIST

Notes: This Design Milestones Review Checklists contains four worksheets. The first worksheet, "Design Milestones", lists t
major design tasks/milestones during specific stages within the Design/Construction Phase.The three other worksheets, "Hi
Level Pre-Design", "Technical Requirements", and "Documentation and User Interface", list actual design activities. Include
other design activities that suit your particular business environment and situation. Accuracy and detail create real value wh
using this document.
VERIFIED (Y,
DESIGN FACTOR N/A, N) COMMENTS

Design Logic
Design has been verified for presence of logic errors.
All unique and positional values have been tested.
Design is tested to ensure that increment and loop counters
properly initialized, and that variables and data areas
initialized before use.
The modules have been properly inspected for correct...
Begin and end of table processing
Processing of queues across interrupts
Decision table logic
Precision/accuracy of calculations
Message priorities are allocated properly to ensure the correct
execution of code.
Design has been tested for errors in the message processing
sequence, handling data, data buffers, or tables, incorrect
field updated, conflicting use of data areas, incomplete
initialization or update, inconsistent or invalid data attributes.

Functional Specifications
The documented specifications for each process is accurate
and complete, writen in precise, unambiguous terms.
Human factors considerations are properly addressed in
functions that provide the user interface.

Design Requirements Traceability

The detailed design matches its high level design
requirements, and all functions and interfaces are completely
and accurately described in sufficient detail, including keyword
or positional parameters, field descriptors, attributes, ranges,
and
The limits.
detailed design of each module or interface fulfills its part
of the requirements and identified in the System Requirement
Specifications (SRS) document. Examples include missing
requirements, ambiguous requirements, conflicting
requirements, untestable requirements, and implied
requirements.
Designed data contains logic, all internal data are defined and
there is no extraneous data.
Error Handling and Recovery
Design has been verified to ensure adequate error condition
testing.
Error conditions are tested where the probability of an error is
high or results of an error would be fatal to the system.
The return codes documented and the return messages
understandable.
The program allows for successful error recovery across
module or process failures, across operating system failures,
across interrupts, and across hardware failures.
 , "Design Milestones", lists the
three other worksheets, "High-
al design activities. Include any
d detail create real value when

SEE DOCUMENT
 DOCUMENTATION AND USER INTERFACE DESIGN CHECKLIST

Notes: This Design Milestones Review Checklists contains four worksheets. The first worksheet, "Design Milestones",
lists the major design tasks/milestones during specific stages within the Design/Construction Phase.The three other
worksheets, "High-Level Pre-Design", "Technical Requirements", and "Documentation and User Interface", list actual
design activities. Include any other design activities that suit your particular business environment and situation.
Accuracy and detail create real value when using this document.
VERIFIED (Y,
DESIGN FACTOR N/A, N) COMMENTS

Help Documents and User Interface

The design is flexible, allowing ease of future
change and minimum waste.
The system has been designed for easy access
and maintenance.
Where online help and other documentation is
used, they are designed such that relevant
information are easy to search, focused on the
user’s task, list concrete steps to be carried out,
and not too large.

All components or modules at a system and

subsystem level have been identified on a System
Architecture Model.
The level of decomposition is sufficient to identify
all modules, and further decomposition results in
identifying more modules.
The user’s interactions with the system should
enhance the quality of her or his work-life.

The design should be aesthetically pleasing- with

artistic as well as functional value.
The system should always keep user informed
about what is going on, through appropriate
feedback within reasonable time.
Design the system such that it speak the user’s
language, with words, phrases and concepts
familiar to the user, rather than system-oriented
terms. Follow real-world conventions, making
information appear in a natural and logical order.
Users should be free to select and sequence
tasks (when appropriate), rather than having the
system do this for them.
Design follows industry or company formatting
standards consistently across all screens within a
system.
Error messages are expressed in plain language
(No codes).
Message prompts are stated constructively,
without overt or implied criticism of the user.
Even better than good error messages is a careful
design which prevents a problem from occurring in
the first place.
level of detail that allows quick and easy
verification.
 The layout of the menu facilitates visual scanning
by the user.
structure and relationships among items to
facilitate search.
Knowledge Transfer
The system design capitalizes on prior learning
and experience of the intended users.
learning from one area (e.g., application) to
another.
The system promotes learning of the location of
items in the menu structure.
The system allows the user to study the global
organization or map of the menu structure by
providing training or assistance.
Search Facilities
The designed menu system allows for a variety of
user
Wheresearch styles. menus are used, the system
hierarchical
provide options to redirect search to the beginning
of the menu (top) and one level up (previous).
Where hierarchical menus are used, the design
provides cognitive landmarks that can be used in
redirecting search.
 CKLIST

st worksheet, "Design Milestones",

struction Phase.The three other
on and User Interface", list actual
s environment and situation.

SEE DOCUMENT