1 / 20

Software Engineering

Software Engineering. Columbia Chapter From Nampa, Idaho. Matthew Little | Matthew Coggins | Kody Kriner | Brandon Thacker. The P oint O f S ale System. Checkout Inventory Control Reporting. Responsibilities. Kriner : User interface & GUI, flow.

alvaro
Download Presentation

Software Engineering

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. Software Engineering Columbia Chapter From Nampa, Idaho Matthew Little | Matthew Coggins | Kody Kriner | Brandon Thacker

  2. The Point Of Sale System • Checkout • Inventory Control • Reporting

  3. Responsibilities • Kriner: User interface & GUI, flow. • Coggins: Exception handling, testing, feedback. • Little: Backbone programming. • Thacker: Database structure and usage.

  4. Design Phase • The most important stage in software development. • Organization is key. • Flow charts for the most advanced functions. • GUI mock-ups.

  5. Checkout had the most features

  6. Entire POS System Correlation Checkout Manage Inventory Add Item To Cart End Transaction Load Items Update Item Database Log Writes to Read by Calc Remaining Percentage Load Items Actions Files Reporting System Parts

  7. GUI, Application Flow • Goal: to keep the design fluid and efficient. • Easy to learn and operate. • Rich layout. • Full featured.

  8. Appealing to the eye • Neat and graphical • Yet not cluttered

  9. OS Native look. • Windows controls. • Took advantage of .NET Framework accessibility.

  10. Windows inherent application flow. • Simple to operate.

  11. The Database • CSV, or Comma Separated Values, database. • Light, flexible, and easy to implement. • Contrary to conventional databases that require: • Much more memory resources • Higher-end computers • Additional Software • Server setup

  12. Database Structure • CSV structure • Rows defined by “line downs” • Columns defined by “commas”

  13. Transaction Logs • Logs (needed for Reporting) create: • Accurate profit reporting. • Remaining stock percentages.

  14. The Code • Programming Language: • C#.NET 3.5 • Compiler/Developer: • Microsoft Visual C# 2008 Express • Readability/Organization: • Code Comments • Region Directives

  15. Code Organization The Region Directive allows for code segments to be titled and minimized.

  16. Source Code Commenting (all commenting is green)

  17. Testing/Feedback • Testing with 20 users. • Several times throughout development • Took in all feedback. • Resulting in very user-friendly UI. • Fixed errors. • Absolutely no errors with normal usage.

  18. We will now take you through the software as an end-user.

More Related