Download What to Do Before the Webmaster Leaves: Documentation and

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Concurrency control wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Database wikipedia , lookup

Relational model wikipedia , lookup

Functional Database Model wikipedia , lookup

Database model wikipedia , lookup

ContactPoint wikipedia , lookup

Clusterpoint wikipedia , lookup

Transcript
What to Do before the
Webmaster Leaves
Documentation and
Planning of Web
Development Projects
Karen Harker, Mitchel Walters, Judi Hill, Brenda Berkins
UT Southwestern Medical Center Library
Dallas, Texas
Library Web site



300 pages
15 locally developed products
150,000+ uses per month
Some products being managed





Document delivery form
Ejournals database
Links database
Class registration database
My Library
What we didn’t have





Written backup plans
Documentation of local products
Maintenance plans
Backup for technical expertise
A well-defined development process
Learning about software documentation
A two-way process
Development Plan
Project Overview
 Steps in Development
 Risk Management Plan
 Staffing Plan
 Schedule
 Testing and Release

Requirements


Constraints
Functional Requirements




User interactions
Database(s)
Measurements of usage
Non-functional Requirements



Look and feel
Usability
Performance
Requirements Table - example
Name
Description
Rationale
Necessity
1.1 Personal
Information
Name
Phone
Affiliation
Required to process
and respond to the
client' s request.
Essential
1.2 Non-personal
Data
Suggested Web site
Comments
This is the substance
of the client's
suggestion.
Essential
1.3 Validation of
client data
IP address
Is the client's
computer on or off
campus?
Conditional
1.4 Etc.
Architecture
Overview





System Overview
System Flowchart
Database(s)
User Interfaces
Software Used
Detailed
Design




Module Flowcharts
Data Dictionary
Database Design:
fields, tables,
relational diagrams
Web Page Design:
screen shots
Architecture Overview:
System Flowchart
Detailed Design: Module Flowchart
Maintenance Plan

Software Maintenance Process
Preventive
 Corrective
 Emergency

Backup Plan
 Evaluation of Product Viability

Benefits
Fast-track product development
 Therapy for ailing projects
 Written documentation

Resources


www3.utsouthwestern.edu/
library/staff/present.htm
Books
McConnell, Steve. Rapid Development. Microsoft
Press, 1996.
McConnell, Steve. Software Project Survival
Guide. Microsoft Press, 1998.

Web sites
Construx Software
<http://www.construx.com/>
Software Engineering Institute
<http://www.sei.cmu.edu/>