Software Engineering CS 421 SWE 421 Kinga Dobolyi
Software Engineering CS 421 / SWE 421 Kinga Dobolyi 1
Why are you taking this course? n n Alternatively, why are we teaching this course? Do you need a course in software engineering? How is writing the code for a 211 project different from software engineering (or is it)? What do you think we will be focusing on in this class?
What is Software Engineering? n According to Wikipedia: “Software engineering (SE) is a profession dedicated to designing, implementing, and modifying software so that it is of higher quality, more affordable, maintainable, and faster to build” 3
Why worry about SW Engineering? n Quality issues: History of SW failures from http: //www. wired. com/software/coolapps/news/2005/11/69355 n Many more incidents… 4
Software is expensive to maintain n n Maintenance activities consume 70 -90% of the total lifecycle cost of software, summing to over $70 billion per year We want to “get it right” the first time n But as we’ll see this is non-trivial 5
Why is it so hard? n Lots of “parts”. Many more than mechanical devices n n n Dishwasher - 128 parts Car - 14, 000 parts Space shuttle - 2. 5 million parts Red Hat Linux 7. 1 - 30 million source lines of code (SLOC) Mac Office - 30 million SLOC n n Using 70 programmers = 428, 000 SLOC / programmer But those are big… what about “normal size programs”? n n n Average programmer SLOC (Source lines of code) / day = 100 5 days/week * 52 weeks/year = 26, 000 SLOC / year 15 programmer team = 390, 000 SLOC / year 6
Why is it so hard? (continued) n We’re a young field n n n ENIAC/ MARK-I in 1946 FORTRAN - 1957 But giant - As of 2004, the U. S. Bureau of Labor Statistics counts 760, 840 software engineers holding jobs in the U. S. ; for comparison, in the U. S. there are some 1. 4 million practitioners employed in all other engineering disciplines combined. - http: //en. wikipedia. org/wiki/Software_engineering n n n Unanticipated growth Still more art than science Everything we do is “new”. (We don’t build the exact same house 30 times. ) Need to have more reproducible results Need to have more measurements 7
Why do projects fail? Why do projects fail so often? Unrealistic or unarticulated project goals n Inaccurate estimates of needed resources n Badly defined system requirements Question: n Poor reporting of the project's status n Unmanaged risks n Poor communication among customers, developers, and users n Use of immature technology How many of these are n Inability to handle the project's complexity caused by technical incompetence in your n Sloppy development practices developers? n Poor project management A. 0 n Stakeholder politics B. 5 C. 8 n Commercial pressures D. All of them List from: http: //www. spectrum. ieee. org/sep 05/1685 n 8
How do we fix it? n Need to have more reproducible results n n n Standard processes / procedures to produce good outcomes Design patterns Object oriented programming (reuse) More measurements of both the software and the process More testing at all stages of development By creating a better understanding of the process we use to create software, we’ll create better software faster. “Software engineering is the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software. ” - IEEE Standard Glossary of Software Engineering Terminology 9
Software Engineering: A Practitioner’s Approach, 7/e Chapter 1 Software and Software Engineering copyright © 1996, 2001, 2005 R. S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited. 10
Why is software different than hardware? Or manufacturing? n n software is engineered software doesn’t wear out most software is still custom built software is complex 12
Wear vs. Deterioration 13
There are many types of applications n n system software - OS, file management, networking, drivers, etc… application software - data processing, point of sale, other business functions… n n engineering/scientific software - CAD, stress analysis, orbital mechanics embedded software - microwave oven keypad, automobile control, cell phone software, etc… n n n product-line software - word processing, inventory control, etc… Web. Apps (Web applications) - many different things today AI software - robotics, data mining, expert systems 14
Legacy Software Why must it change? n n software must be adapted to meet the needs of new computing environments or technology. software must be enhanced to implement new business requirements. software must be extended to make it interoperable with other more modern systems or databases. software must be re-architected to make it viable within a network environment 15
Software – A. True or B. False? 1. 2. 3. 4. 5. If we get behind schedule we can add more programmers to catch up A general statement of objectives is sufficient to begin writing programs - we can fill in the details later Project requirements change, but change can be easily accommodated because software is flexible Once we write the program and get it working our job is done Software engineering will make us create unnecessary documentation and will invariably slow us down 16
Software Myths Affect managers, customers (and other non-technical stakeholders) and practitioners n Are believable because they often have elements of truth, but … n Invariably lead to bad decisions, therefore … n Insist on reality as you navigate your way through software engineering n One of the goals in this class is to learn you how to determine what reality is! 17
Fixing the problem Software engineering! n Software engineering is really just a set of ideas and tools to use (when it makes sense) to give you a higher likelihood of success on a software project. n Will your project fail if you don’t use any software engineering techniques? No…. but you have a better chance at success if you do. 18
n A Generic Framework Communication n n Planning n n Creation of models to allow the customer and the developer to better understand the requirements and design that will achieve those requirements Construction n n Establish a plan for the work. Technical task to be conducted, risks, needed resources, work products to be created, and a schedule Modeling n n Heavy collaboration with the customer, other stakeholders and encompasses requirements gathering and related activities Combines code generation and testing required to uncover errors in the code Deployment n The software (as a complete entity or partially complete increment) is delivered to the customer who evaluates it and provides feedback. 19
Framework Activities n n n Communication Planning Modeling n n n Construction n Analysis of requirements Design Code generation Testing Deployment What are some artifacts (work tasks, work products, milestones & deliverables, QA checkpoints) of each activity? What tools may help support them? 20
Umbrella Activities n n n n Software project management Formal technical reviews Software quality assurance Software configuration management Work product preparation and production Reusability management Measurement Risk management 21
The Process Model: Adaptability n The framework activities will always be applied on every project. . . BUT n The tasks (and degree of rigor) for each activity will vary based on: n n n the type of project characteristics of the project common sense judgment; concurrence of the project team 23
Question n Pick any one of the project types below and tell me which process activity would be emphasized or deemphasized and why Project Types: - 1. Space Shuttle control system - 2. Web-based calendar - 3. Embedded controller in your refrigerator - 4. Automatic “daily fortune” text-messenger Framework Activities n Communication n Planning n Modeling n n n Construction n Analysis of requirements Design Code generation Testing Deployment 24
How to solve any problem n Polya 1945 n n n Understand the problem Plan a solution Carry out the plan Examine the result for accuracy Do these agree with our basic framework? communication, planning, modeling, construction deployment? 25
How do we improve our performance? n n We want to “provide guidance for developing or improving processes that meet the business goals of an organization” Capability Maturity Model Integration (CMMI) is a process improvement approach that helps organizations improve their performance 26
The CMMI n n CMMI defines characteristics shown to achieve good results. The CMMI defines each process area in terms of “specific goals” and the “specific practices” required to achieve these goals. Specific goals establish the characteristics that must exist if the activities implied by a process area are to be effective. Specific practices refine a goal into a set of processrelated activities. PP - project planning REQM - Requirements Mgmt MA - Measurement and Analysis CM - Configuration Mgmt PPQA - Process and Product QA 27
The CMMI 28
The Waterfall Model n Do all process steps in the following order (this is generally thought of as the most basic model) 1998, the Standish Group analyzed 23, 000 projects to determine failure factors. The top reasons for project failure, according to the report, were associated with waterfall practices. - http: //www 2. umassd. edu/SWPI/xp/articles/r 6047. pdf 31
Different families of models Prescriptive Agile Prescriptive Models 1970 ->Present Agile Models 2001 ->Present -Waterfall (1970) -Evolutionary (1975) -Incremental (1975) -Spiral (1988) -RAD (1991) - e. Xtreme Programming (1999) - SCRUM (1990 s) - DSDM (1997) - Crystal (2001) All dates are approximate based on publications 32
Different families of models Prescriptive Agile Goal: Higher Quality Software Philosophy: • Bring order to chaos • Provide repeatability/consistency • Provide ability to control • Provide ability to coordinate teams • Individuals and interaction over process and tools • Working software over large documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Which is probably better for large teams? A. Prescriptive B. Agile C. Same Which is probably better for a web application? Which is probably better for Mars rover control system? Which is produces better software? 33
Project n Team decisions due tomorrow/today (depending on section) n n Post to blackboard a document containing your team name, and the names and emails of the members of your team 4 -5 students per team Turn in your team interview sheets (handed out Sept 1/2) in class, if you are not part of a team. If I didn’t get an email from your team, I will use these sheets for the rest of you to assign teams for you. I will then set up accounts for teams on XP-dev; you will be emailed information 34
Homework n Pressman ch 1 exercises: 5, 8, 10 n n Due next Thursday by 10 pm Submit on blackboard 35
- Slides: 31