GradesPosted by Team/Student IDCheck your phase 2Check your attendance#1 is project submission forms, #2,3,4 are actual attendanceMore 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 observationsDouble 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 referencesGrammar and spellingONLY or BARELY following instructions - no motivation to do more (earned 70 pts).

Things that really countedIllustrations, pictures, links to more info.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-75substantial understanding is a B 76 - 89applying it to a wider audience and real life is an A 90 - 100

Phase 3 - The Software Requirements SpecificationAfter review of the customers System Spec.After educated analysisPreliminary designA technical, software approachResults in permission to detail-design and then code

Customer Points-of-ContentionAssumptions, Constraints, LimitsFunctionDocumentation technical, user, and training manualsTrainingMaintenance / EnhancementsHow to handle Requirements ChangesStatus and Reviews

From the customers perspectiveHow smart people are going to solve the problem that was stated in the System Spec.A contract, more or lessIs it doable?TechnicallyOn timeUnder budget

Settles these issues:Software Architecture Object Oriented?Structured?Database Oriented (Informational Flow)?Event DrivenMajor Modulesto 2 or 3 levels of supervisionlow level utilities if they touch hardware or the environment

Risk AssessmentTechnical Riskshardware / software / interfacesbuild vs. buyteam expertise needed

Schedule Risksbudgetcalendarpersonnel level of expertise required

Phase 3Write PARTS OF an SRSArchitectural DrawingsMain User Screen(s)Integration Thread (also a Drawing)Change of Scope FormCross Reference Listing

What is a module?OutputsInputsStorageProcessingSimple Block Diagram FormArrows, of course, should be labeled

Data Flow Diagram - not a flow chartData ConversionDFD Standard ShapesArrows, of course, should be labeledEvery arrow should have an entry in a "data dictionary"Temporary StorageSinkSourceData Movementdata beforedata after

Air TrafficControlDisplayDatabaseRadarAddRemoveEditDiskAccessDisplayRefreshUIRecordPlaybackSweepDataConversionDataInterpretationStructure Chart

No symbols exist on the page to display.

Legend

Legend Subtitle

Symbol

Count

Description

City Simulator

Talking Head

Talker

Data Flow Diagram - shows movement, conversion, and storage of dataThis is the "top" drawing of a $6 million, 45-person, 1 million LOC, 4 year project

CAPE

Sensors

Operator(s)

Result

Database

Aircraft

Flight Guidance

Data

Measurement Results

Measurement Results

SensorData

SensorConfig

User IO

Cloud Chart - (pre UML) object relationships

VI. Change Request FormIf 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 InformationName:______________________________ Position:_______________________________Phone: _____________________________ Email: _________________________________Signature:______________________________________________ Date:_______________

Description of ModificationCheck one: [ ]Feature addition [ ]Feature Removal [ ]New Limitation [ ]Other:________________________Module Affected:_____________________________________________________________Description:

PriorityCheck one: [ ]Mandatory [ ]Highly Preferred [ ]Slightly Preferred

Reason for Priority:

Project ImpactItems in the section are subject to approval of software team.Estimated Budget Change:_____________________________________________________Estimated Schedule Change:___________________________________________________

NotesProvide any other notes necessary. Project Specific!

The Cross Reference Typically the last section of the SRSList 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 columnsA 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 VehicleDevelopment OS (may have been specified in System Spec)Language (may have been specified in System Spec)Editors, Syntax Checkers, LibrariesThe Configuration Management and Version Control SystemsSpecified for budgetary more than technical reasons.

NEXT SEMESTER (CSE453) Execution VehicleA 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 SRSCritical DesignModule Level DetailsStructure Charts / Object Chartsbuild the Integration Thread Major ModuleInterfacesmodule-to-modulehardware to softwaredrivers to control (up levels of supervision)

Cant Go BackOnce 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 changesCatch specification mistakes in the specification phase. How?In the System Spec and SRSUse reviews