1 / 18

CSCE 240 – Intro to Software Engineering

CSCE 240 – Intro to Software Engineering . Instructor Orren Mckay www.cse.sc.edu/~mckayj/cse240.htm. Quote of the Day. “Everything should be made as simple as possible, but not simpler.” -Albert Einstein. Overview. Syllabus Roll/Introductions Start on Chapter 1. Syllabus.

signe-vaughn
Download Presentation

CSCE 240 – Intro to 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. CSCE 240 – Intro to Software Engineering Instructor Orren Mckay www.cse.sc.edu/~mckayj/cse240.htm

  2. Quote of the Day “Everything should be made as simple as possible, but not simpler.” -Albert Einstein

  3. Overview • Syllabus • Roll/Introductions • Start on Chapter 1

  4. Syllabus • See handout • Remember, feel free to ask questions and point out any misteaks. 

  5. Roll/Introductions • Stand up, introduce yourselves as I call the roll. • Name, where you’re from, and what your major is. • Please try and be patient with my mangling your names.

  6. Reading for Next Class • Please Read Chapter 1 in Object Oriented Software Engineering book.

  7. The Big Question What is Software Engineering?

  8. Authors Definition “Software engineering is the process of solving customers’ problems by the systematic development and evolution of large, high-quality software systems within cost, time and other constraints.”

  9. IEEE Definition “(1)the application of systematic, disciplined, quantifiable approach to the development, operation, maintenance of software; that is, the application of engineering to software. (2) The study of approaches as in (1).”

  10. Canadian Standards Assn. Definition “The systematic activities involved in the design, implementation and testing of software to optimize its production and support.”

  11. Software vs. Other Engineering • Finished product more intangible than other engineering fields. • Mass production trivial • Software creation very labor intensive • Poorly trained programmers can create functional (or semi-functional products)

  12. Software vs. Other Engineering (continued) • Easy to modify, hard to modify without repercussions • Software does not wear out, instead design deteriorates through repeated changes and revisions

  13. Types of Software • Custom – developed for needs of (usually) one particular customer (ex. VIP (probably), CSE dropbox system ) • Generic – designed for sale on the open market (ex. MS Word, IE, Netscape) • Embedded – for running specific hardware devices (ex. Digital Watches, Recent cars)

  14. Software Categories • Real-time – has to react immediately to stimuli. • Data processing – Database operations, sales, where operations can be organized into batches for execution.

  15. Stakeholders • Users – people who will use the finished software. • Customers – the people writing the check (and deciding what the check is for). • Software Developers – Most likely, you. • Development Managers – people who run organization developing software.

  16. What makes Quality Software? • Usability – how easy to learn to use, and once experienced with software, use efficiently. Also how well errors are handled. • Efficiency – good use of CPU time, memory, bandwidth, disk space and resources. • Reliability – few failures, and fast recovery from failures that do occur.

  17. What makes Quality Software? (continued) • Maintainability – how easy is it to change, update, fix software. • Reusability – can software components be used for multiple projects with little or no modification.

  18. The Rest of the Semester • Understanding the Customer and User • Object Oriented Methods • UML (Unified Modeling Language) • Producing reusable technology • Iterative development • Communication through documentation • Risk Management

More Related