Professional Documents
Culture Documents
Posted
by Team/Student ID
Check your phase 2
Check your attendance
#1 is project submission forms,
#2,3,4 are actual attendance
More than 1 sign-in with different
signatures?
Not legible signature (we have to at
least be able to tell its your name).
Research
Requirements Specification
After
Customer Points-ofContention
Assumptions,
Constraints, Limits
Function
Documentation
technical, user,
and training manuals
Training
Maintenance / Enhancements
How to handle Requirements
Changes
Status and Reviews
Software Architecture
Object Oriented?
Structured?
Database Oriented (Informational
Flow)?
Event Driven
Major Modules
to 2 or 3 levels of supervision
low level utilities if they touch
hardware or the environment
Risk Assessment
Technical
Risks
Risks
budget
calendar
personnel level of expertise required
Phase 3
Write
PARTS OF an SRS
Architectural Drawings
Main User Screen(s)
Integration Thread (also a Drawing)
Change of Scope Form
Cross Reference Listing
What is a module?
Storage
Outputs
Processing
Inputs
Temporary Storage
Source
data
before
Data Conversion
data
after
Sink
Structure Chart
Air Traffic
Control
Radar
Sweep
Data
Conversion
Data
Interpretation
Database
Add
Remove
Disk
Access
Display
Edit
Display
Refresh
Record
UI
Playback
City Simulator
Talking Head
User Interface
Phrasing
MP3s
Prediction
Rules Db
WAVs
Phrase Completion
Presentation
Audio
Construction
Stored Menus
Output
Phrase
Synthesis Engine
Choice
Logging,
Monitoring, &
Annunciation
Build and Release
Edit / Undo/ ReDo
Talker
Operator(s)
User IO
Sensors
SensorData
CAPE
SensorConfig
Flight Guidance
Data
Aircraft
Measurement Results
Result
Database
TCP/IP Stack
(HTTP, SNMP,
Telnet)
Socket Input
= Internal
Communication
File System
Serial
Terminal
File Input
Serial Input
Command
Processor
Serial Input
[ ]Mandatory
[ ]Highly Preferred
[ ]Slightly Preferred
Project Specific!
Last
Semester:
2 Columns
SHOULD
Usually
Design
Cant Go Back
Once
an SRS is approved,
changes become very expensive:
A specification change, leading to
design changes, leading to coding
changes, leading to schedule/budget
changes, leading to testing changes
and finally delivery changes
Catch
specification mistakes in
the specification phase. How?
In the System Spec and SRS
Use reviews