1 / 16

ITEC 370

ITEC 370. Lecture 14 Implementation. Review. Questions? Draft of design document on F Brief 3-5 minute work update on F (will continue except for mid-term) Design What are some of the factors you have to decide on when designing a project? Are these factors reliant on the client?

linnea
Télécharger la présentation

ITEC 370

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ITEC 370 Lecture 14 Implementation

  2. Review • Questions? • Draft of design document on F • Brief 3-5 minute work update on F (will continue except for mid-term) • Design • What are some of the factors you have to decide on when designing a project? • Are these factors reliant on the client? • Where is thedesign document used in the software process?

  3. Objectives • How to implement code • Not your typical 109/120/220 lecture hopefully

  4. Start • Have description of system and how to build it… • Resources • Documents • People who wrote the documents • Computers • Redbull? • How would you build the system with a team of people?

  5. Environment • What is your ideal coding environment?

  6. Environment • Physical • Individual / team • Coding • IDE • Compilers • Process of write,compile, run or write, upload, view

  7. For me • 4 terminal windows • 2 with code • 1 for building • 1 for running • Doesn’t work for everything • iPod applications

  8. Issues • When you have a team of developers… • What are some of the issues that might come up during the implementation phase?

  9. Style • Seemingly minor point • Can cause major issues • Decide what your team’s style is • Indent with tabs or spaces • Does the { go after the if or on the next line? • Variable naming convention • Global variables • Function length • Usually spelled out

  10. Comments • What are they? • What are they useful for? • How should the be used in implementation? • Is one style better than another?

  11. Comments • Life-blood of a successful project • Tie-in • Requirements • Design document • Testing… • Code should have multiple sources of documentation • In-line, design, user manual

  12. Comments • Bare minimum • Describe what the code does • Describe what is required to use this code • Give examples of how to use this code • Provide test cases and expected output

  13. Word of caution • We typically love clever solutions • Don’t’ come up with a clever / cryptic naming system • KISS • Multiple people are working on a system • Simple is better

  14. Testing • Should you write test cases (paper or actual code) for your project before you actually write the code? • Benefits • Downsides

  15. Errors / warnings • Are warnings acceptable? • How are errors reported? • Allow java runtime errors to handle it • Blank page • Try/catch statements + Console output • Pop-ups

  16. Review • Start of implementation • Concerns about how to start the process • Didn’t even get into actual coding strategies

More Related