DOC PREVIEW
ODU CS 350 - Lecture Notes

This preview shows page 1-2-21-22 out of 22 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 22 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CS 350, slide set 9aOutlineBackground readingA Little FORTRANDriver?AECLP (p. 47)ARSP (p. 53)ASP (p. 55)CP (p. 59)CRCP (p. 63)GP (p. 65)GSP (pg. 74)RECLP (p. 75)TDLRSP (p. 77)TDSP (p. 83)TSP (p. 85)Assume 4 member groupsRequired modulesSimplified Task Planning Template (p. 82)Task Plan/Report per ModuleAnother omissionMinutes due by Sunday!CS 350, slide set 9aM. OverstreetOld Dominion UniversitySpring 2005OutlineWhat to read?What to implement?What to stub?What should instructor provide?Background readingRead pp. 1-17Particularly, make sure you understand:Rotation of History Variables (p. 15)•In general, you are required to keep copies of previous values of several variables just in case•Anytime you compute a new value, throw away the oldest oneException Handling (p. 16)A Little FORTRANREAL*8 means doubleLook in .h files to see all C++ equivalentsIf an exception occurs the spec says to print:What the exception is (see spec)The name of the module,The name of the function within that moduleThe current value of frame counterThe The FORTRAN statement FORMAT( x, a6, x, a32, x, i4)means to print an ASCII string (module name), another ASCII string (function name) and an integer (frame counter)Driver?Calls other modulesWhat’s tricky?Calling order (page 43)TerminationWhat about GCS_SIM_RENDEZVOUS?•StubbedAECLP (p. 47)5 pagesControls big engines (axial)Similar to RECLPHas some “messy” mathIntegrationSolve differential equation for te_limitARSP (p. 53)2 pagesUse radar to find heightMath:Need to fit third-order polynomial to existing dataSome prior knowledgeASP (p. 55)4 pagesMeasure acceleration (in all 3 directions)Math:Matrix multiplyError handlingCP (p. 59)4 pagesPrepare data packet for transmissionCodingPacking different data types on byte boundariesA little prior knowledgeCRCP (p. 63)1 pageRelease parachuteGP (p. 65)7 pagesFly the space craftMathIntegrationMatrix multipliesComplex!GSP (pg. 74)2 pagesMeasure rotation rates using gyroscopesRECLP (p. 75)2 pagesControl roll enginesTDLRSP (p. 77)5 pagesMeasure velocity with 4 radar beamsIssuesError handling?TDSP (p. 83)1 pageTSP (p. 85)3 pagesMathFind equations of quadraticAssume 4 member groupsWhich modules to implementWhat can be stubbed?What routines should be provided?Due to lack of math prerequisites for classRequired modulesDriverStubbed routines for any not writtenE.g. GP, GCS-sim-rendezvousModules:ARSPASPCPGSPExtra credit for extra modulesHow much depends on difficulty of module; please inquireSimplified Task Planning Template (p. 82)Rows: include only:Launch & strategyPlan-tasks and scheduleSystem test planOnly one line per module (but see next slide)PostmortemTotalsColumns: include only:Task Name Planned ValuePlan hours by person Cumulative PVTotal team hours Actual hoursCumulative hours Cumulative hoursSize Actual WeekPlanned WeekTask Plan/Report per ModuleTask Size WhoPlan-hrsPV Act-hrsPlan com. dateAct. com. dateEVDesignDesign revCodeCode rev.CompileCode insp.Test dataTest driverTest rev.Test insp.TestingAnother omissionGiven the limited time:Log where errors are found onlyOmit noting where errors are insertedYou must report errors found for each taskSome tasks may be unlikely to discover errors, but also include them in your error report.Minutes due by Sunday!For this meeting, do not use week formWill be used after this weekInclude:Team NameChosen regular team meeting timeTentative decision on who will implement whatTeam


View Full Document

ODU CS 350 - Lecture Notes

Download Lecture Notes
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture Notes and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture Notes 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?