Unformatted text preview: Software Engineering and Best Practices
Sources: Various. Rational Software Corporation slides, OOSE textbook slides, Per Kroll talk, How to Fail with the UP article, textbooks Most slides have been modified considerably
26 Fundamental Terms / Concepts Science and Engineering Science: Discover Relationships that exist but are not found Formulas; chemical composition, d=r*t; calories in fats, Engineering: Build carbohydrates, proteins; experimentation; Astrophysics origins of the universe Apply principles of science and mathematics to real Software Engineering definition??
30 needs, commodities, structures, products, etc. 2 What is Software Engineering? The process of solving customers' problems by the systematic development and evolution of large, high quality software systems within cost, time and other constraints Note: 30 Process, systematic (not ad hoc), evolutionary, disciplined, quantifiable Constraints: high quality, cost, time, meets user requirements Not only development, but operations and maintenance!!! 3 Analysis of the Definition: Systematic development and evolution An engineering process involves applying well understood techniques in a organized and disciplined way Many wellaccepted practices have been formally standardized Most development work is evolutionary (incremental; adding business value.) e.g. by the IEEE or ISO Large, high quality software systems Software engineering techniques are needed because large systems cannot be completely understood by one person Teamwork and coordination are required Cost, time, budget, and other constraints Finite resources The benefit must outweigh the cost Others are competing to do the job cheaper and faster Inaccurate estimates of cost and time have caused many project failures
4 30 What Happens in Practice
Sequential activities: (Traditional `Waterfall' Process) Requirements Design Code Integration Test
100% Integration Begins Risk inadequately addressed Process not receptive to Change Problems not really `seen' until near delivery date! Until then, `all is well...' Big Bang approach full delivery Long development cycles... Little user involvement, etc. etc... Development Progress (% coded) Late Design Breakage Original Target Date 30 Project Schedule 5 30 Inaccurate understanding of enduser needs Inability to deal with changing requirements Some Symptoms of Software Development Problems Modules that don't fit together (integration) Software that's hard to maintain or extend (brittle) Late discovery of serious project flaws (integration) Poor software quality (architecture, risks unanticipated...) Process not responsive to Change (Gantt Charts...) Unacceptable software performance Team members in each other's way, unable to reconstruct who changed what, when, where, why (software architecture, ... Poor management of the development process ...and we could go on and on... 6 Best Practices of Software Engineering
Develop Iteratively Use Manage Component Requirements Architectures Model Visually Verify Quality Control Changes Know these!
30 7 Addressing Root Causes Eliminates the Symptoms
end-user needs changing requirements modules don't fit hard to maintain late discovery poor quality poor performance colliding developers build-and-release Root Causes
insufficient requirements ambiguous communications brittle architectures overwhelming complexity undetected inconsistencies poor testing subjective assessment waterfall development uncontrolled change insufficient automation Best Practices
develop iteratively manage requirements use component architectures model the software visually verify quality control changes Symptoms of problems can be traced to having Root Causes. Best Practices are `practices' designed to address the root causes of software problems.
30 8 Practice 1: Develop Software Iteratively Develop Iteratively Manage Requirements Use Component Architectures Model Visually Verify Quality Control Changes Considered by many practitioners to be the most significant of the six
30 9 Practice 1: Develop Software Iteratively Until recently, developed under assumption most requirements can be identified up front. The research deconstructing this myth includes work by Capers Jones. (See next slide) In this very large study of 6,700 projects, creeping requirements -- those not anticipated near the start--are a very significant fact of software development life, ranging from around 25% on average projects up to 50% on larger ones.
10 30 Look up a definition of `Function Points.'
30 11 Interestingly, An initial design will likely be flawed with respect to its key requirements. Requirements rarely fully known up front! Latephase discovery of design defects results in costly overruns and/or project cancellation Oftentimes requirements change even during implementation! While large projects are more prone to cost overruns, mediumsize/small projects are vulnerable to cancellation. The key reasons continue to be poor project planning and management, shortage of technical and project management expertise, lack of technology infrastructure, and inappropriate project teams. 30 12 Waterfall Delays Risks
Walker Royce, 1995 R I S K Requirements Design Code Integration System Test Waterfall risk 30 T I M E 13 Accelerate Risk Reduction
Walker Royce, 1995 R I S K Risk reduction Risk reduction Iterative Waterfall risk Iteration
30 Iteration Iteration
T I M E Iteration Iteration
14 Iterative Development
Iteration 1 Iteration 2 Iteration 3 Earliest iterations address greatest risks Each iteration produces an executable release; an increment. Each iteration includes integration, test, and assessment! 30 15 Objective Milestones: short-term focus; short term successes! Iterative Development Characteristics Critical risks are resolved before making large investments Initial iterations enable early user feedback Testing and integration are continuous assures successful integration (parts all fit) Objective milestones provide shortterm focus Progress measured by assessing implementations Partial implementations can be deployed Continuous testing. Easy to resolve problems early. Encourages user feedback in meaningful ways Waterfall method no delivery Incremental development? Is great values in delivering key parts of application. Critical components delivered first
16 30 UP Lifecycle Graph Showing Iterations
In an iteration, you may walk through all disciplines C O N T E N T S T R U C T U R E 30 17 TIME Executable Releases UP Iterations and Phases
Devel. Iteration Inception Construction
Devel. Iteration Devel. Iteration Transition
Transition Transition Iteration Iteration Preliminary Architect. Architect. Iteration Iteration Iteration An iteration is a distinct sequence of activities with an established plan and evaluation criteria, resulting in an `executable release.' (There is a lot of very important `key' terminology used here... (cycle, iteration, phase, milestones, core disciplines, content of iterations, etc....)
30 18 Problems Addressed by Iterative Development
Root Causes Solutions Insufficient requirements Ambiguous communications Brittle architectures Overwhelming complexity Subjective assessment Undetected inconsistencies Poor testing Waterfall development Uncontrolled change Insufficient automation Enables and encourages user feedback Serious misunderstandings evident early in the life cycle Development focuses on critical issues break it down! Objective assessment thru testing and assessment Inconsistencies detected early Risks identified and addressed early via planned iterations!
19 Testing starts earlier continuous 30 Major impacts on Project Managers, though.... No Free Lunch Traps Abound... Trap: When the initial risks are mitigated, new ones emerge Do not do just the easy stuff, to look good. Keep replanning based on all new information. Trap: Remember `some' Rework enables you to enhance your solution Accommodate change early in the project Trap: Iterative development does not mean never to commit to a solution Monitor `scrap and rework' Trap: Must Control "requirement creep, " however... Some clients will now naturally recognize many `musts...' 30 20 Many Traps in Iterative Development
Here is another trap: Too long initial iteration Winning is fun. Winning teams work better than loosing teams Better to have a short initial iteration, than one too long Cut scope if necessary (much more later) Avoid `analysisparalysis' by timeboxing; you can enhance in later iterations (more later) Establish an even rhythm for project (at least w/i a phase) Not completing iterations makes you lose most of the benefit 30 Focus on results and deliverables, not activities 21 Iterations Are Timeboxed
Work is undertaken within an iteration. The iteration plan defines the artifacts to be delivered, roles and activities. An iteration is clearly measurable.
Iterations are riskdriven Generally, initial iterations based on high risk and core functionalities! 30 22 The Iteration Plan Defines....
The deliverables for that iteration. artifacts The to do list for the team members
30 23 Plan With Evolving Levels of Detail
Coarse-grained Plan: Software Development Plan Fine-grained Plans: Iteration Plans Next Iteration One For Entire Project Solution: Phases and major milestones What and when Iterations for each phase Number of iterations Objectives and Duration Current Iteration Iterative Development does not mean less work and shorter schedule It is about greater predictability
30 24 Progress is made against MILESTONES
Each phase is defined by a milestone. Milestones measure success Phases NOT TIMEBOXED. Progress is made by passing milestones. Iterations ARE TIMEBOXED.
30 Inception Elaboration Construction Transition 25 Summary Much more about iteration and iteration planning later in the course... You will see some of these again and, more importantly, use this information in your own iteration planning. 30 26 ...
View Full Document
- Fall '11
- Project Management, Software development process, Iterative and incremental development, Iteration Iteration Iteration