Вы находитесь на странице: 1из 26

Grades

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).

Class participation &


professionalism (individual) 10%
The professional component includes not just the
attendance, but emphasizes more pointedly the
productive value of input a student offers to class
discussion. It could also include professional behaviors
such as not texting during class, looking at laptops
when they are not needed for the class, and not talking
with fellow students during class. It includes other
aspects of professional behavior such as properly
written emails, preparedness when attending office
hours, and advanced notification for classes that are
missed.
I would add incentive, completeness, and level of effort
when completing assignments.
This includes taking the attendance sheets seriously

Phase 2 - some observations


Double

spaces, 2 in. margins, one-half


page of total text, fluffy prose.
You should generally have more to say than
that.
These problems are complex.
General level of effort is clear. Some were
very disappointing.

Research

/ definitive statements with no


references / Internet quotes with no
references
Grammar and spelling
ONLY or BARELY following instructions - no
motivation to do more (earned 70 pts).

Things that really


Illustrations, pictures, links to more info.
counted

Sections beyond the lecture slides (means


your were thinking).
Proposed screen layouts as a specification
tool.
Required database contents (informational vs.
data types).
Research with references.
Remember:
Barely answering the requirements is a C
70-75
substantial understanding is a B 76 - 89
applying it to a wider audience and real life
is an A 90 - 100

Phase 3 - The Software

Requirements Specification
After

review of the customers


System Spec.
After educated analysis
Preliminary design
A technical, software
approach
Results in permission to detaildesign and then code

Customer Points-ofContention
Assumptions,

Constraints, Limits

Function
Documentation

technical, user,
and training manuals
Training
Maintenance / Enhancements
How to handle Requirements
Changes
Status and Reviews

From the customers


perspective
How

smart people are going to


solve the problem that was
stated in the System Spec.
A contract, more or less
Is it doable?
Technically
On time
Under budget

Settles these issues:

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

hardware / software / interfaces


build vs. buy
team expertise needed
Schedule

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

Simple Block Diagram Form


Arrows, of course, should be labeled

Data Flow Diagram - not a flow


chart
Data Movement

Temporary Storage

Source

data
before

Data Conversion

data
after

Sink

DFD Standard Shapes


Arrows, of course, should be labeled
Every arrow should have an entry in
a "data dictionary"

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

Menu PresentationGraphics, Text


User Feedback

Choice
Logging,
Monitoring, &
Annunciation
Build and Release
Edit / Undo/ ReDo

Talker

Data Flow Diagram - shows movement, conversion, and storage of data


This is the "top" drawing of
a $6 million, 45-person,
1 million LOC, 4 year project

Operator(s)

User IO

Sensors

SensorData

CAPE

SensorConfig

Flight Guidance
Data

Aircraft

Measurement Results

Result
Database

Cloud Chart - (pre UML) object relationships

Generation 2 Configuration Control Detail

TCP/IP Stack
(HTTP, SNMP,
Telnet)

Socket Input

= Internal
Communication

File System

Serial
Terminal

File Input

Serial Input

Command
Processor

Serial Input

VI. Change Request Form


If you would like to make any changes to the project description, including new features,
feature cuts, limitations, etc., please fill out this form send it to
talkingheadcompanion@gmail.com as soon as possible.
NOTE: Any change may impact the previously agreed-upon budget and schedule.
Requestor Information
Name:______________________________ Position:_______________________________
Phone: _____________________________ Email: _________________________________
Signature:______________________________________________ Date:_______________
Description of Modification
Check one:
[ ]Feature addition
[ ]Feature Removal
[ ]New Limitation
[ ]Other:________________________
Module Affected:_____________________________________________________________
Description:
Priority
Check one:

[ ]Mandatory

[ ]Highly Preferred

[ ]Slightly Preferred

Reason for Priority:


Project Impact
Items in the section are subject to approval of software team.
Estimated Budget Change:_____________________________________________________
Estimated Schedule Change:___________________________________________________
Notes
Provide any other notes necessary.

Project Specific!

The Cross Reference

Typically the last section of the SRS


List items from the System Spec.
Tell which section of the SRS
provides coverage.
Identify the items that contain risk.
Identify the items that will be
designed with flexibility.
Identify the items that define the
Critical Path

Last
Semester:
2 Columns

this semester at least 3


Acolumns
Table, in which the rows are a simple list of
the individual capabilities of the end system,
nicely numbered for reference later. Clumn 1 is
the description, column 2 is the location of
each requirement in the System Spec, and
column 3 is the location of each requirement in
the SRS. This table will serve you in the
planning phase (as a task list), to assure that
all items that need to be designed and coded
are included.
If you need to change your System Spec, then
please do it.

NEXT SEMESTER (CSE453)


Development Vehicle
Development

OS (may have been


specified in System Spec)
Language (may have been
specified in System Spec)
Editors, Syntax Checkers,
Libraries
The Configuration Management
and Version Control Systems
Specified for budgetary more
than technical reasons.

NEXT SEMESTER (CSE453)


Execution Vehicle
A

large undertaking if not


specified in the System Spec.

SHOULD

be decided with the


customer before the SRS

Usually

the first item in "how we


plan to solve your problem"

NEXT SEMESTER (CSE453) After


the SRS
Critical

Design

Module Level Details


Structure Charts / Object Charts
build the Integration Thread
Major Module
Interfaces
module-to-module
hardware to software
drivers to control (up levels of supervision)

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