1 / 30

ITSE 205: Software Engineering

ITSE 205: Software Engineering. Lecture 1 Introduction to Software Engineering. Academic Integrity. Software Engineering is a collaborative activity. You are encouraged to work together, but ... • Some tasks may require individual work.

jerica
Download Presentation

ITSE 205: 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. ITSE 205: Software Engineering Lecture 1 Introduction to Software Engineering

  2. Academic Integrity Software Engineering is a collaborative activity. You are encouraged to work together, but ... • Some tasks may require individual work. • Always give credit to your sources and collaborators. Good professional practice: To make use of the expertise of others and to build on previous work, withproper attribution. Unethical and academic plagiarism: To use the efforts of others without attribution.

  3. Grading Examinations (Written/Oral) 40% Recitation/Presentation 10% Term Project (group) 10% Course Work Project (individual) 10% Quizzes 20% ORLE 10%

  4. Overall Aim of the Course We assume that you are technically proficient. You know a good deal about computing, can program reasonably, can learn more on the job. When you finish your course, you are going to work on production projects where success or failure costs millions of dollars. Soon you will be in charge! It may be your money! We want you to make your mistakes now and learn from your mistakes. ;-)

  5. Projects The Course is Built around the Projects • Real project for real client who intends to use the software in production. • Select your own project, any branch of software development •Project teams, 3 to 4 team players. • Feasibility study and plan: due before December 18 • Group presentations and reports: requirements, design, final

  6. Project Selection Read the Web site •Some projects are suggested on the Web site (http://wnucict.wordpress.com) • You are encouraged to find other projects Contact potential clients • Gain idea from the course expectations • Estimate scope and complexity of the project • Discuss business decisions Assemble project team • Post message on FB WNU-CICT PROJECTS GROUP • Advertise at the beginning of class

  7. Thoughts about Project Selection Projects • Target must be a production system (not research) • Client should be one or two designated people -- client should be prepared to meet with you regularly and attend the presentations Team • Teams need many strengths -- organizational, technical, writing, etc. • Consider appointing a leader to coordinate the effort

  8. Variety of Software Products Examples Real time: air traffic control Embedded systems: digital camera Data processing: telephone billing, pensions Information systems: web sites, digital libraries Sensors: weather data System software: operating systems, compilers Communications: routers, mobile telephones Offices: word processing, video conferences Scientific: simulations, weather forecasting Graphical: film making, design etc., etc., etc., ....

  9. Client Client (a.k.a. Customer) The client may provides resources and expects some product in return. Client satisfaction is the primary measurement of success in a software project.

  10. Categories of Software Product Categories of client and software product: •Generic – these are stand-alone systems which are produced by a development organization and sold on the open market to any customer who is able to buy them. (e.g., Microsoft Excel) • Packages (e.g., Mathematica) •Customized versions of generic packages (e.g., WNU's enrollment system) •Bespoke (customized) products – these are systems which are commissioned by a particular customer. The software is developed specially for that customer by a software contractor. (e.g., IRS internal system) •Demonstration, prototype, research, ... Who is the client for each category of product?

  11. Previous Experience (Yours) Your background • Biggest program that you have written? • Biggest program that you have worked on? • Biggest project team that you have been part of? • Longest project that you have worked on? • Most people who have used your work? • Longest that your project has been in production?

  12. Observations Most software development is by teams • Effectiveness of team determines success Most large software projects are built on older ones • It is rare to start a new suite of programs from scratch • Building on the work of others is a fundamental skill of software development

  13. Observations about Big Projects • A CSMN120 project is about 3 persons /years. • A big project may be 100 to 1,000 persons/ years. • Every important program is written by many people, who are constantly changing. • Before a big project is completed the requirements have changed many times. • No large system is ever complete.

  14. Future Experience What will you be doing one year from now? Ten years from now? Typical career paths in computing combine technical work with varying degrees of project management, marketing, entrepreneurship, etc.

  15. Software is Expensive Software is expensive! The major costs are salaries (your salaries)! Every software project has a trade-off between: Functionality Resources (cost) Timeliness

  16. Course Themes • Risk • Visibility • Process • Scale

  17. Course Themes: Risk Risk (as Seen by a Manager) •Problems Over budget Late delivery - Does not work as expected •Never used Does the wrong thing Needs change - Users dislike to use it etc. Failures of software development projects can bankrupt companies!

  18. Course Themes: Visibility Visibility (as Seen by a Manager) •Problem Must rely on others for reports of progress or difficulties •Software Developers Have difficulty evaluating progress Optimistic Consider reporting a waste time etc. The people who take the responsibility must know what is happening!

  19. Course Themes: Process Process in Large Software Projects • Software as a product Clients and their needs Quality • Requirements and specification Usability Evolution • Project management Personnel management Economic, legal, and social factors Nobody comprehends more than a fraction of the project!

  20. Course Themes: Scale Techniques for large and very large systems • Software design Software architecture Object-oriented design • Dependable systems Reliability Verification • Legacy systems

  21. What is Software? Computer programs and associated documentation. Software products may be developed for a particular customer or may be developed for a general market.

  22. What is Software Engineering? Software Engineering is an engineering discipline which is concerned with all aspects of software production.

  23. What is the difference between software engineering and computer science? Computer Science is concerned with theory and fundamentals; while Software Engineering is concerned with the practicalities of developing and delivering useful software.

  24. What is a software process? A set of activities whose goal is the development or evolution of software.

  25. What is a software process model? A simplified representation of a software process, presented from a specific perspective.

  26. What is a CASE (Computer-aided software engineering)? Software systems which are intended to provide automated support for software process activities. CASE systems are often used for method support.

  27. What are the key challenges facing software engineering? Coping with legacy systems. Coping with increasing diversity. Coping with demands for reduced delivery times.

  28. What is Good Software? • General characteristics • Usability– Software must be usable without undue effort, by the type of user for whom it is designed. • Maintainability– software should be written in such a way it may evolve to meet the changing needs of customers. • Dependability– software should be reliable, secure and safe. It should not cause physical or economic damage in the event of system failure. • Efficiency– software should not make wasteful use of system resources such as memory and processor cycles..

  29. What is Good Software? Good software products require good programming, but ... Programming quality is the means to the end, not the end itself.

  30. The Craft of Software Development Software products are very varied --> Client requirements are very different --> There is no standard process for software engineering --> There is no best language, operating system, platform, database system, development environment, etc. A skilled software developer knows about a wide variety of approaches, methods, tools. The craftof software development is to select appropriate methods for each project and apply them effectively.

More Related