SoftwareCostEstimation. Spring,2012

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "SoftwareCostEstimation. Spring,2012"

Transcription

1 SoftwareCostEstimation Spring,2012

2 Chapter 3 SOFTWARE COST ESTIMATION DB Liu Software Cost Estimation

3 INTRODUCTION Estimating the cost of a software product is one of the most difficult and error-prone tasks in software engineering (unknown factors during planning phase). But contracting practices often requires a firm cost commitments as part of the feasibility study. ~ Some organizations use a series of cost estimates: A preliminary cost estimate is prepared during the planing phase and presented at projectfeasibility review, and an improved estimate is presented at the software requirements review(srr). A second estimate is presented at the preliminary design review(pdr). And a final estimate is presented at the Critical Design Review(CDR). DB Liu Software Cost Estimation 3

4 3~1 SOFTWARE COST FACTORS Major factors that influence software cost: 1. Programmer ability 20 Product complexity 3. Product size 4. Available time 5. Required reliability 6. Level of technology DB Liu Software Cost Estimation 4

5 3e1.1 PROGRAMMER ABILITY Nevertheless, variability of 5 to 1 in programmer productivity is a significant factor in cost estimation. On very large projects, the differences in individual programmer ability will tend to average out, but on projects utilizing five or fewer programmers, individual differences in ability can be significant. DB Liu Software Cost Estimation 5

6 3~1.2 PRODUCT COMPLEXITY Three levels of product complexity are organic, semidetached, and embedded programs. These levels roughly correspond to application programs (data processing and scientific programs), utility programs (compilers, linkage editors, inventory systems), and systems programs (operating systems, data-base management systems). PM = programmer-months of effort, in terms of thousands delivered source instructions (KDSI), given by Boehrn: Application programs: PM = 2.4*(KDSI)**1.05 Utility programs: PM = 3.O*(KDSI)**1.12 Systems Programs: PM = 3.6*(KDSI)**1.20 (See graphs of these equations on next pages) Programmer cost for the software project can be obtained by rnulçipiying the effort in programmer-months by the cost per programmer-month. DB Liu Software Cost Estimation 6

7 COCOMO EFFORT ESTIMATES Systems 0 Utility E Pioduct ~~Le KUSI 500 Figure 3.1 Cocotito effort estimates (BOE8J). DB Liu Software Cost Estimation 7

8 3.1~2 PRODUCT COMPLEXITY (cont.) The ~ç~çp line for a program, as given by Boehm, is: Application programs: Utility programs: Systems Programs: TDEV = 2.5*(PM)**O.38 TDEV = 2.5*(PM)**O.35 TDEV = 2.5*(PM)**O,32 (See graphs of these equations on next page) The Development Time is roughly the same for all three types of systems. For example, a 60 KDSI program can be developed in approximately 18 months, regardless of its complexity level. DB Liu Software Cost Estimation 8

9 COCOMO SCHEDULE ESTIMTES Utility Systems 0 E 4) :1 0 4) 4, 18F Product size~kdsl 600 Figure 3.2 Cocomo schedule estimates (BOE8I). DB Liu Software Cost Estimation 9

10 3.1.2 PRODUCT COMPLEXITY (cont.) Average Staffing Level Given total programmer-months for a project and nominal development time required, the Average Staffing Level can be obtained by simple division. For our 60 KDSI program, we obtain the following results: Application programs: Utility programs: Systems Programs: PM / MO = 9.9 programmers 294 PM / 18.3 MO = 16 programmers PM / 18.1 MO = 27 programmers ~ It must be emphasized that these above results presented only for the purpose of illustration. These equations should NOT be used to estimate software effort without careful readini~ ofboehin to understand the assumptions and limitations of the method. The estimates are no better than our ability to estimate the final number of instructions (KDSI) in the program. DB Liu Software Cost Estimation ~j 0

11 3.1.3 PRODUCT SIZE A large sofiware product is obviously more expensive to develop than a small one. Boehm s equations indicate that the rate of increase in required effort grows with the number of source instructions at an exponential rate slightly greater than 1. Table 12 Effort and schedule estimators (BOE8I) Effort equation Schedule equation Reference MM = 5~2(KDSI)**O.91 TDEV = 2.47(MM)**O~35 (WAL77) MM = 4.9(KDSI)**O.98 TDEV 3.04(MM)**O.36 (NEL78) MM = L5(KDSJ)**1.02 TDEV = 4.38(MM)**O.25 (FRE79) MM 2.4(KDSI)**1.05 TDEV = 2.50(MM)**O.38 (BOE81) MM = 3.O(KDSI)**1.12 TDEV = 2.50(MM)**O.35 (BOE81) MM = 3~6(KDSI)**1.2O TDEV = 2.50(MM)**O.32 (BOE81) MM = 1.O(KDSI)**1.40 (J0N77) MM = O.7(KDSI)**l.50 (11AL77) MM = 28 (KDSI)** 1.83 (5CH78) DB Liu Software Cost Estimation 11

12 3d 4 AVAILABLE TIME Total project effort is sensitive to the calendar time available for project completion. Most investors agree that sofiware projects require more total effort if development time is compressed or expanded from the optimal time. The results are shown in following figure: 1.5 ~(RCA 78) 78) 0 z w 01 0 > \ / / / / d // (AIR 74) (13(712 81) (1.9 Figure 3.3 Relative effort for off-nominal schedules (BOE$i ). DB Liu Software Cost Estimation 12

13 3.1.4 AVAILABLE TIME (cont,) In a study of 63 software projects, Boehm found that only four had compression factors less than 75 percent of the development time predicted by his cost estimation model. Boehm states: There is a limit beyond which a software project cannot reduce its schedule by buying more personnel and equipment. This limit occurs roughly at 75% of the nominal schedule. DB Liu Software Cost Estimation 13

14 3~1~5 REQUIRED LEVEL OF RELIABILITY Software Reliability can be defined as the probability that a program will perform a required function under stated conditions for a stated period of time. Reliability can be expressed in terms of accuracy, robustness, completeness, and consistency of the source code. There is a cost associated with the increased level ofanalysis, design, implementation, and ver~fication and validation effort that must be exerted to ensure high reliability. Boehm describes 5 categories of reliability and recommends a development effort multiplier for each. (See table in next page) DB Liu Software Cost Estimation 14

15 DEVELOPMENT EFFORT MULTIPLIERS FOR SOFTWARE RELIABILITY Category Effect of failure Effort Multiplier Very low Slight inconvenience 0.75 Low Losses easily recovered 0.88 Normal Moderately difficult to recover losses 1.00 High High financial loss 1.15 Very high Risk to human life Note that multipliers range from 0.75 for very low reliability to 1.4 for very high reliability. The effort ration is thus 1.87 (1.4/0.75). DB Liu Software Cost Estimation 15

16 3.1.6 LEVEL OF TECHNOLOGY Level of Technology in a software development project is reflected by the programming language, the abstract machine (hardware and software), the programming practices, and the software tools used. Use of a high level language instead of assembly language increases programmer productivity by a factor of 5 to 10. Modem programming languages provide additional features to improve programmer productivity and software reliability. These features include: strong type-checking, data abstraction, separate compilation, exception handling, interrupt handling, and concurrency mechanism. Use of Modern Programming Practices (systematic analysis and design techniques, structured design notations, walkthroughs and inspections, structured coding, systematic testing, program development library). DB Liu Software Cost Estimation 16

17 3J,6 LEVEL OF TECHNOLOGY (cont0) ~ Use of Modern Development Tools (requirements specification analyzer, fully integrated development environments that include configuration management and automated verification tools.) Boehm provides Effort Multipliers for modem programming practices that range from 1.24 (no modem practices) to 0.82 (full use of modem practices), and Effort Multipliers for software tools that range from 1.24 (very basic tools) to 0.83 (advanced development tools). Thus, the use of modem practices and the use of modem development tools, can each reduce programming effort to 0.67 (0.82/1.24) of the effort required using assembly language and primitive development tools. Use of both modern practices and modern development tools can reduce development effort to 0.45 (0.67*0.67) of that required using primitive tools and techniques. DB Liu Software Cost Estimation 17

18 3.2 SOFTWARE COST ESTIMATION TECHNIQUES In most organizations, software cost estimates are based on past performance. * Top-down Cost Estimation: First focuses on system-level costs such as computing resources and personnel required, configuration management, quality assurance, system integration, training, and publications. * Bottom-up Cost Estimation: First estimate the cost to develop each module or subsystem. Those costs are combined to arrive at an overall estimate. Cost estimates can be made either top-down or bottom-up. In practice, both top-down and bottom-up cost estimates should be developed, compared, and iterated to estimate differences. DB Liu Software Cost Estimation 18

19 3.2.1 EXPERT JUDGMENT The most widely used cost estimation technique is expert judgment (a top-down technique). Expert judgment relies on the experience, background, and business sense of one or more key people in the organization. Groups of experts sometimes prepare a consensus estimate. * Disadvantage of group estimate is the possible presence of authority figures in the group, or the dominance of an overly assertive group member. DB Liu Software Cost Estimation 19

20 3.2.2 DELPHI COST ESTIMATION The Delphi technique was developed at the Rand Corporation to gain expert consensus without introducing the adverse side effects ofgroup meetings. The Delphi technique can be adapted to software cost estimation in the following manner: (1) A coordinator provides each estimator with the System Definition document and a form for recording a cost estimate. (2) Estimators study the definition and complete their estimates anonymously. They may ask questions of the coordinator, but they do not discus their estimates with one another. (3) The coordinator prepares and distributes a summary of the estimators responses, and includes any unusual rationales noted by the estimators. (4) Estimators complete another estimate, again anonymously, using the results from the previous estimate. Estimators whose estimate differ sharply from the group may be asked, anonymously, to provide justification for their estimates. (5) The process is iterated for as many rounds as required. No group discussion is allowed during the entire process. DB Liu Software Cost Estimation 20

21 3~2,3 WORK BREAKDOWN STRUCTURES The WBS is a bottom-up estimation tool. A WBS is a hierarchical chart that accounts for the individual parts of a system. A BWS chart can indicate either product hierarchy or process hierarchy. Product hierarchy identifies the product components and indicates the manner in which the components are interconnected. Using WBS technique, costs are estimated by assigning costs to each individual component in the chart and summing the costs. (See WBS figure on next page) DB Liu Software Cost Estimation 21

22 3.2.3 WORK BREAKDOWN STRUCTURES (cont.) DB Liu Software Cost Estimation 22

23 3.3~4 ALGORITHMIC COST MODELS Algorithmic Cost Estimators compute the estimated cost of a software system as the sum of costs of the modules and subsystems that comprise the system. It is a bottom-up estimator The COnstructive COst Model (COCOMO) is an algorithmic cost model described by Boehm. When using COCOMO, Boehm s equations are used to provide nominal estimates of Programmer-Months and Development Schedule for a program unit, based on the estimated number of Delivered Source Instructions (DSI) in the unit. [DSJ s all statements, exclude comments and unmodified utility routines.] DB Liu Software Cost Estimation 23

24 3,3.4 ALGORITHMIC COST MODELS (cont.) Effort Multipliers are then used to adjust the estimate for Product Attributes, Computer Attributes, Personnel Attributes, and Project Attributes. See the Table on next page for COCOMO Effort Multipliers and their ranges of values. DB Liu Software Cost Estimation 24

25 3 3~4 ALGORITHMIC COST MODELS Table3A COCOMO effort mufltipliers Multiplier Range of values Product attributes Required reliability 0.75 to 1.40 Data-base size 0.94 to 1.16 Product complexity 0.70 to 1.65 Computer attributes Execution time constraint 1.00 to 1.66 Main storage constraint 1.00 to 1.56 Virtual machine volatility 0.87 to 1.30 Computer turnaround time 0.87 to 1.15 Personnel attributes Analyst capability 1.46 to 0.71 Programmer capability 1.42 to 0.70 Applications experience 1.29 to 0.82 Virtual machine experience 1.21 to 0.90 Programming language experience 1.14 to 0.95 Project attributes Use of modem programming practices 1.24 to 0.82 Use of software tools 1.24 to 0.83 Required development schedule 1.23 to DB Liu Software Cost Estimation 25

26 3.3.4 ASSUMPTIONS MADE FOR COCOMO Small to Medium size project ( 2K to 32K DSI) Familiar application areas Stable, well-understood virtual machine o Definition and validation requirements are performed by a small group of capable people. Requirements are stable throughout the proj ect Architectural design is performed by a small number of capable people Detailed design, coding, unit testing are performed in parallel by groups of programmers working in teams Integration testing is based on early test planning Interface errors are mostly found by unit testing and by inspection and walkthroughs before integration testing o Documentation is performed incrementally as part of the development process. DB Liu Software Cost Estimation 26

27 3.3,4 ALGORITHMIC COST MODELS (cont.) EXAMPLES: To develop a 1 O-KDSI embedded software product for telecommunication processing. Step 1: The nominal effort equations predict: PM = 3.6*(1O)**1.20 = 57.1 TDEV = 2.5*(44.4)**O.32 = 8.4 Step 2: Effort Multipliers are used to adjust the estimate for off-nominal aspects of the project: See table 3.5 from Fairley s book on next page (the effort adjustment factor of 1.17 is the product of the effort multipliers shown in that table) Adjusted PM = PM * 1.17 = 57.1 * programmer-months. Adjusted-TDEV = TDEV* 1.17 = 8.4*1.17 = 9.83 months. DB Liu Software Cost Estimation 27

28 3.3.4 ALGORITHMIC COST MODELS (cont.) Table 3.5 Effort multipliers for embedded telecommunications example Multiplier Rationale Value Reliability Local use only. No serious recovery problems (nominal) 1.00 Database 20,000 bytes (low) 0.94 Complexity Telecommunication processing (very high) 1.30 Timing Will use 70% of processing time (high) 1.11 Storage 45K of 64K available (high) 1.06 Machine Stable. c ommercially available microprocessor (nominal) 1.00 Tu~riaround Two hours average (nominal) 1.00 Analysts Good senior people (high) 0.86 Programmers Good senior people (high) 0.86 Experience Three years in telecomrn (nominal) 1.00 Experience Six months on the micro (low) 1.10 Experience Twelve months with the language (nominal) 1.00 Practices More than 1 year experience with modem techniques (high) 0.91 Tools Basic micro software (low) 1.10 Schedule Nine months; 8.4 estimated (nominal) 1.00 Effort adjustment factor DB Liu Software Cost Estimation 28

29 3.3~4 ALGORITHMIC COST MODELS (cont.) Total Cost of Project Personnel: Assume that the programmers and analysts cost $6,000 per PM, the total cost of project personnel will be: => DOLLARS = (66.8 PM)* ($ 6,000 per PM) = $ 400,800 COCOMO can also be used to investigate trade-offs in the development process by performing sensitivity analysis on the cost estimate. For example: Less capable personnel might be used to implement the telecommunications processor at a cost savings of $1,000 per programmermonth; however, the effort multipliers must both be increased from 0.86 to 1.0 to reflect the change. The effort adjustment factor becomes 1.58 and then Adjusted PM = PM * 1.58 = 57.1 * 1.58 = 90.2 programmer-months (more) Adjusted-TDEV = TDEV* 1.58 = 8.4*1.58 = 13.3 months (longer) => DOLLARS = $5,000 * 90.2 = $ 451,000 (a cost increase of $50,200). DB Liu Software Cost Estimation 29

30 3~3,4 ALGORITHMIC COST MODELS (cont0) If we expand the memory from 46K to 96K for an additional $10,000. The storage multiplier will be reduced from 1.06 to 1.00, which results in a new cost adjustment factor of We now have: Adjusted PM = PM * 1.10 = 57.1 * 1.10 = 62.8 programmer-months. Adjusted-TDEV = TDEV* 1.10= ~ 4* 1.10=9.24 months (shorter) > DOLLARS = $6,000 * 62.8 = $ 376,800 (lower) The total savings: $400,800 - project in a shorter time. $376,800 = $ 24,000 and can finish the Therefore, purchasing additional memory is a wise decision. DB Liu Software Cost Estimation 30

31 3.3.4 ALGORITHMIC COST MODELS (cont.) Advantage of COCOMO: The model can be used to gain insight into the cost factors within an - organization. Data can be collected and analyzed, new factors can be identified, and - the effort multipliers can be adjusted as necessary to calibrate COCOMO to the local environment. Disadvantage of COCOMO: Assumption of various independent effort multipliers is too strong. - In reality, varying one factor ofien implies that the other factors - should also be adjusted. DB Liu Software Cost Estimation 31

32 3.4 ESTIMATING SOFTWARE MAINTENANCE COSTS o Software maintenance typically requires 40% to 60% of total life-cycle effort. Maintenance activities include adding enhancements to the product, adapting the product to new processing environment, and correcting problems. Use the estimated number of delivered source instructions Business data processing: 32 KDSI I maintenance Real-time or Aerospace Software System: 8 KDSI 10 KDSI I maintenance programmer. - DB Liu Software Cost Estimation 32

33 3.4 ESTIMATING SOFTWARE MAINTENANCE COSTS (cont,) Use ACTIVITY RATIO: Boehm suggests that maintenance effort can be estimated by use of an Activity Ratio. ACT = (DSI added + DSI modified) I)~ total PM m = Number of programmer-months required for maintenance PM d = Number of programmer-months required for development PMm = ACT *PMd An enhance version is: PM m = ACT * EAF * PM d where EAF is the effort adjusted factor for different effort multipliers. DB Liu Software Cost Estimation 33

34 o 3.5 SUMMARY Software cost estimation is one of the most difficult and error-prone task in software engineering. o Cost estimation techniques rely on historical data covering past performance. Most cost estimates are in terms of estimated number of source instructions in the product to be developed. o Expert Judgment and Algorithmic Prediction are two fundamental approaches to cost estimation. Delphi technique of cost estimation by a group of experts was described. o The principal features of COCOMO were presented. Techniques for estimating software maintenance costs were discussed. Data must be collected during current proj ects in order to estimate effort and schedule for future ones. DB Liu Software Cost Estimation 34

35

36

37

38

Cost Estimation Strategies COST ESTIMATION GUIDELINES

Cost Estimation Strategies COST ESTIMATION GUIDELINES Cost Estimation Strategies Algorithmic models (Rayleigh curve Cost in week t = K a t exp(-a t 2 ) Expert judgment (9 step model presented later) Analogy (Use similar systems) Parkinson (Work expands to

More information

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur Module 11 Software Project Planning Lesson 28 COCOMO Model Specific Instructional Objectives At the end of this lesson the student would be able to: Differentiate among organic, semidetached and embedded

More information

Software cost estimation. Predicting the resources required for a software development process

Software cost estimation. Predicting the resources required for a software development process Software cost estimation Predicting the resources required for a software development process Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 23 Slide 1 Objectives To introduce the fundamentals

More information

Project Planning and Project Estimation Techniques. Naveen Aggarwal

Project Planning and Project Estimation Techniques. Naveen Aggarwal Project Planning and Project Estimation Techniques Naveen Aggarwal Responsibilities of a software project manager The job responsibility of a project manager ranges from invisible activities like building

More information

Software cost estimation

Software cost estimation Software cost estimation Sommerville Chapter 26 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity assessment To explain why different

More information

Introduction and Overview

Introduction and Overview Introduction and Overview Definitions. The general design process. A context for design: the waterfall model; reviews and documents. Some size factors. Quality and productivity factors. Material from:

More information

Software cost estimation

Software cost estimation Software cost estimation Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 26 Slide 1 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for

More information

Chapter 23 Software Cost Estimation

Chapter 23 Software Cost Estimation Chapter 23 Software Cost Estimation Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 23 Slide 1 Software cost estimation Predicting the resources required for a software development process

More information

ICS 121 Lecture Notes Spring Quarter 96

ICS 121 Lecture Notes Spring Quarter 96 Software Management Cost Estimation Managing People Management Poor managment is the downfall of many software projects Ð Delivered software was late, unreliable, cost several times the original estimates

More information

SOFTWARE ECONOMICS UNIT 15. Presented by. Stefano Street

SOFTWARE ECONOMICS UNIT 15. Presented by. Stefano Street SOFTWARE ECONOMICS UNIT 15 Presented by Stefano Street Objectives Software economics its importance and place in software systems Provide an empirical view of where money goes Why it is important to understand

More information

MTAT.03.244 Software Economics. Lecture 5: Software Cost Estimation

MTAT.03.244 Software Economics. Lecture 5: Software Cost Estimation MTAT.03.244 Software Economics Lecture 5: Software Cost Estimation Marlon Dumas marlon.dumas ät ut. ee Outline Estimating Software Size Estimating Effort Estimating Duration 2 For Discussion It is hopeless

More information

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management?

Contents. Today Project Management. Project Management. Last Time - Software Development Processes. What is Project Management? Contents Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software Management and Evolution Last Time - Software

More information

Lecture 14: Cost Estimation

Lecture 14: Cost Estimation Overview Project management activities Project costing Project scheduling and staffing Project monitoring and review General cost estimation rules Algorithmic Cost Modeling Function point model COCOMO

More information

Software Requirements Metrics

Software Requirements Metrics Software Requirements Metrics Fairly primitive and predictive power limited. Function Points Count number of inputs and output, user interactions, external interfaces, files used. Assess each for complexity

More information

Project Plan 1.0 Airline Reservation System

Project Plan 1.0 Airline Reservation System 1.0 Airline Reservation System Submitted in partial fulfillment of the requirements of the degree of Master of Software Engineering Kaavya Kuppa CIS 895 MSE Project Department of Computing and Information

More information

Comparison of SDLC-2013 Model with Other SDLC Models by Using COCOMO

Comparison of SDLC-2013 Model with Other SDLC Models by Using COCOMO International Journal of Emerging Science and Engineering (IJESE) Comparison of SDLC-2013 Model with Other SDLC Models by Using COCOMO Naresh Kumar, Pinky Chandwal Abstract There exist a large number of

More information

An Approach to Find Maintenance Costs Using Cost Drivers of Cocomo Intermediate Model

An Approach to Find Maintenance Costs Using Cost Drivers of Cocomo Intermediate Model An Approach to Find Maintenance Costs Using Cost Drivers of Cocomo Intermediate Model C.V.S.R SYAVASYA 1, M.Tech, GITAM UNIVERSITY Abstract: Maintenance of software under several cost drivers is as sort

More information

CISC 322 Software Architecture

CISC 322 Software Architecture CISC 322 Software Architecture Lecture 19: Software Cost Estimation Emad Shihab Slides adapted from Ian Sommerville Last Class Program Evaluation and Review Technique (PERT) Determine critical path Calculate

More information

Software Engineering. Dilbert on Project Planning. Overview CS / COE 1530. Reading: chapter 3 in textbook Requirements documents due 9/20

Software Engineering. Dilbert on Project Planning. Overview CS / COE 1530. Reading: chapter 3 in textbook Requirements documents due 9/20 Software Engineering CS / COE 1530 Lecture 4 Project Management Dilbert on Project Planning Overview Reading: chapter 3 in textbook Requirements documents due 9/20 1 Tracking project progress Do you understand

More information

Valuation of Software Intangible Assets

Valuation of Software Intangible Assets Valuation of Software Intangible Assets Eric A. Thornton Senior Associate (703) 917-6616 eathornton@willamette.com ASA International Conference San Diego, California August 28, 2002 San Francisco, California

More information

Next-Generation Software Economics

Next-Generation Software Economics Next-Generation Software Economics by Walker Royce Vice President and General Manager Strategic Services Rational Software Software engineering is dominated by intellectual activities focused on solving

More information

CS 458 - Homework 4 p. 1. CS 458 - Homework 4. To become more familiar with top-down effort estimation models, especially COCOMO 81 and COCOMO II.

CS 458 - Homework 4 p. 1. CS 458 - Homework 4. To become more familiar with top-down effort estimation models, especially COCOMO 81 and COCOMO II. CS 458 - Homework 4 p. 1 Deadline Due by 11:59 pm on Friday, October 31, 2014 How to submit CS 458 - Homework 4 Submit these homework files using ~st10/458submit on nrs-labs, with a homework number of

More information

CS/SWE 321 Sections -001 & -003. Software Project Management

CS/SWE 321 Sections -001 & -003. Software Project Management CS/SWE 321 Sections -001 & -003 Software Project Management Copyright 2014 Hassan Gomaa All rights reserved. No part of this document may be reproduced in any form or by any means, without the prior written

More information

Software Cost Estimation

Software Cost Estimation Lecturer: Sebastian Coope Ashton Building, Room G.18 E-mail: coopes@liverpool.ac.uk COMP 201 web-page: http://www.csc.liv.ac.uk/~coopes/comp201 Software Cost Estimation 1 Software Cost Estimation Software

More information

Software Architecture and Engineering Project Cost Management Peter Müller

Software Architecture and Engineering Project Cost Management Peter Müller Software Architecture and Engineering Project Cost Management Peter Müller Chair of Programming Methodology Spring Semester 2012 12. Project Cost Management Overview 2 12. Project Cost Management 12.1

More information

Project Plan. Online Book Store. Version 1.0. Vamsi Krishna Mummaneni. CIS 895 MSE Project KSU. Major Professor. Dr.Torben Amtoft

Project Plan. Online Book Store. Version 1.0. Vamsi Krishna Mummaneni. CIS 895 MSE Project KSU. Major Professor. Dr.Torben Amtoft Online Book Store Version 1.0 Vamsi Krishna Mummaneni CIS 895 MSE Project KSU Major Professor Dr.Torben Amtoft 1 Table of Contents 1. Task Breakdown 3 1.1. Inception Phase 3 1.2. Elaboration Phase 3 1.3.

More information

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java. What is Project Management?

11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java. What is Project Management? 11.1 What is Project Management? Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process Project management encompasses all the

More information

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur Module 11 Software Project Planning Lesson 29 Staffing Level Estimation and Scheduling Specific Instructional Objectives At the end of this lesson the student would be able to: Identify why careful planning

More information

(Refer Slide Time: 01:52)

(Refer Slide Time: 01:52) Software Engineering Prof. N. L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture - 2 Introduction to Software Engineering Challenges, Process Models etc (Part 2) This

More information

CISC 322 Software Architecture

CISC 322 Software Architecture CISC 322 Software Architecture Lecture 20: Software Cost Estimation 2 Emad Shihab Slides adapted from Ian Sommerville and Ahmed E. Hassan Estimation Techniques There is no simple way to make accurate estimates

More information

Software cost estimation. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 26 Slide 1

Software cost estimation. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 26 Slide 1 Software cost estimation Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 26 Slide 1 Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for

More information

Tutorial: Estimation and Planning Examples. Friday, October 25 th

Tutorial: Estimation and Planning Examples. Friday, October 25 th Tutorial: Estimation and Planning Examples Friday, October 25 th Overview Task Integration Example Pert/CPM Graph Gantt Chart COCOMO Quick SDL refresher Task Integration Modules taken from design doc Integration

More information

Project Management. Lecture 3. Software Engineering CUGS. Spring 2012 (slides made by David Broman) Kristian Sandahl

Project Management. Lecture 3. Software Engineering CUGS. Spring 2012 (slides made by David Broman) Kristian Sandahl Project Lecture 3 Software Engineering CUGS Spring 2012 (slides made by David Broman) Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle

More information

Project Management. Lecture 3. Software Engineering CUGS. Spring 2011 (slides made by David Broman)

Project Management. Lecture 3. Software Engineering CUGS. Spring 2011 (slides made by David Broman) Lecture 3 Software Engineering CUGS Spring 2011 (slides made by David Broman) Kristian Sandahl Department of Computer and Information Science Linköping University, Sweden A Software Life-cycle Model Which

More information

Project Planning Objectives. Project Estimation. Resources. Software Project Estimation

Project Planning Objectives. Project Estimation. Resources. Software Project Estimation Project Planning Objectives Project Estimation Providing a framework that allows managers to make responsible estimates of the resources and time required to build a software product. Determining the scope

More information

Finally, Article 4, Creating the Project Plan describes how to use your insight into project cost and schedule to create a complete project plan.

Finally, Article 4, Creating the Project Plan describes how to use your insight into project cost and schedule to create a complete project plan. Project Cost Adjustments This article describes how to make adjustments to a cost estimate for environmental factors, schedule strategies and software reuse. Author: William Roetzheim Co-Founder, Cost

More information

WBS, Estimation and Scheduling. Adapted from slides by John Musser

WBS, Estimation and Scheduling. Adapted from slides by John Musser WBS, Estimation and Scheduling Adapted from slides by John Musser 1 Today Work Breakdown Structures (WBS) Estimation Network Fundamentals PERT & CPM Techniques Gantt Charts 2 Estimation Predictions are

More information

ABSTRACT. would end the use of the hefty 1.5-kg ticket racks carried by KSRTC conductors. It would also end the

ABSTRACT. would end the use of the hefty 1.5-kg ticket racks carried by KSRTC conductors. It would also end the E-Ticketing 1 ABSTRACT Electronic Ticket Machine Kerala State Road Transport Corporation is introducing ticket machines on buses. The ticket machines would end the use of the hefty 1.5-kg ticket racks

More information

Computer Science and Software Engineering University of Wisconsin - Platteville 3.Time Management

Computer Science and Software Engineering University of Wisconsin - Platteville 3.Time Management Computer Science and Software Engineering University of Wisconsin - Platteville 3.Time Management SE 2730 Lecture Notes Yan Shi Based on Introduction to the Personal Software Process by Watts Humphrey

More information

Topics. Project plan development. The theme. Planning documents. Sections in a typical project plan. Maciaszek, Liong - PSE Chapter 4

Topics. Project plan development. The theme. Planning documents. Sections in a typical project plan. Maciaszek, Liong - PSE Chapter 4 MACIASZEK, L.A. and LIONG, B.L. (2005): Practical Software Engineering. A Case Study Approach Addison Wesley, Harlow England, 864p. ISBN: 0 321 20465 4 Chapter 4 Software Project Planning and Tracking

More information

Software Engineering. Reading. Effort estimation CS / COE 1530. Finish chapter 3 Start chapter 5

Software Engineering. Reading. Effort estimation CS / COE 1530. Finish chapter 3 Start chapter 5 Software Engineering CS / COE 1530 Lecture 5 Project Management (finish) & Design CS 1530 Software Engineering Fall 2004 Reading Finish chapter 3 Start chapter 5 CS 1530 Software Engineering Fall 2004

More information

E-COCOMO: The Extended COst Constructive MOdel for Cleanroom Software Engineering

E-COCOMO: The Extended COst Constructive MOdel for Cleanroom Software Engineering Database Systems Journal vol. IV, no. 4/2013 3 E-COCOMO: The Extended COst Constructive MOdel for Cleanroom Software Engineering Hitesh KUMAR SHARMA University of Petroleum and Energy Studies, India hkshitesh@gmail.com

More information

AC 20-148 REUSABLE SOFTWARE COMPONENTS

AC 20-148 REUSABLE SOFTWARE COMPONENTS AC 20-148 REUSABLE SOFTWARE COMPONENTS December 7, 2004 12/7/04 AC 20-148 CONTENTS Paragraph Title Page 1. Purpose....1 2. Motivation for this Guidance....1 3. Document Overview...1 4. General Guidelines

More information

System Engineering Plan

System Engineering Plan Project Documentation Document SPEC-0064 Revision A System Engineering Plan Rob Hubbard, Jeremy Wagner, Larry Daggert, Larry Stepp, Christoph Keller Systems Engineering / Project Management 5 October 2006

More information

SWEN 256 Software Process & Project Management

SWEN 256 Software Process & Project Management SWEN 256 Software Process & Project Management Plan: Identify activities. No specific start and end dates. Estimating: Determining the size & duration of activities. Schedule: Adds specific start and end

More information

Applied Software Project Management

Applied Software Project Management Applied Software Project Management Estimation http://www.stellman-greene.com 1 What is estimation? The project manager must set expectations about the time required to complete the software among the

More information

USTC Course for students entering Clemson F2013 Equivalent Clemson Course Counts for Clemson MS Core Area. CPSC 822 Case Study in Operating Systems

USTC Course for students entering Clemson F2013 Equivalent Clemson Course Counts for Clemson MS Core Area. CPSC 822 Case Study in Operating Systems USTC Course for students entering Clemson F2013 Equivalent Clemson Course Counts for Clemson MS Core Area 398 / SE05117 Advanced Cover software lifecycle: waterfall model, V model, spiral model, RUP and

More information

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur

Module 11. Software Project Planning. Version 2 CSE IIT, Kharagpur Module 11 Software Project Planning Lesson 27 Project Planning and Project Estimation Techniques Specific Instructional Objectives At the end of this lesson the student would be able to: Identify the job

More information

Pearson Education Limited 2003

Pearson Education Limited 2003 156 Activities Activity 9.1 (PP. 357 358) [Project planning exercise] You are required to construct a project plan for the following information system development project. Your objective is to schedule

More information

Establishing Great Software Development Process(es) for Your Organization. By Dale Mayes DMayes@HomePortEngineering.com

Establishing Great Software Development Process(es) for Your Organization. By Dale Mayes DMayes@HomePortEngineering.com Establishing Great Software Development Process(es) for Your Organization By Dale Mayes DMayes@HomePortEngineering.com Class: ETP-410 Embedded Systems Conference San Francisco 2005 Abstract: There are

More information

Software Metrics. Lord Kelvin, a physicist. George Miller, a psychologist

Software Metrics. Lord Kelvin, a physicist. George Miller, a psychologist Software Metrics 1. Lord Kelvin, a physicist 2. George Miller, a psychologist Software Metrics Product vs. process Most metrics are indirect: No way to measure property directly or Final product does not

More information

Estimating Size and Effort

Estimating Size and Effort Estimating Size and Effort Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm SAPM Spring 2007:

More information

Management. Project. Software. Ashfaque Ahmed. A Process-Driven Approach. CRC Press. Taylor Si Francis Group Boca Raton London New York

Management. Project. Software. Ashfaque Ahmed. A Process-Driven Approach. CRC Press. Taylor Si Francis Group Boca Raton London New York Software Project Management A Process-Driven Approach Ashfaque Ahmed CRC Press Taylor Si Francis Group Boca Raton London New York CRC Press is an imprint of the Taylor St Francis Croup, an Informa business

More information

A DIFFERENT KIND OF PROJECT MANAGEMENT

A DIFFERENT KIND OF PROJECT MANAGEMENT SEER for Software SEER project estimation and management solutions improve success rates on complex software projects. Based on sophisticated modeling technology and extensive knowledge bases, SEER solutions

More information

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction

Acknowledgement. Software Engineering. CS 3141: Team Software Project Introduction CS 3141: Team Software Project Introduction Ali Ebnenasir Department of Computer Science Michigan Technological University Acknowledgement Betty H.C. Cheng Software Engineering Systematic approach for

More information

Karunya University Dept. of Information Technology

Karunya University Dept. of Information Technology PART A Questions 1. Mention any two software process models. 2. Define risk management. 3. What is a module? 4. What do you mean by requirement process? 5. Define integration testing. 6. State the main

More information

INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE

INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE PREFERRED RELIABILITY PRACTICES PRACTICE NO. PD-ED-1228 PAGE 1 OF 6 INDEPENDENT VERIFICATION AND VALIDATION OF EMBEDDED SOFTWARE Practice: To produce high quality, reliable software, use Independent Verification

More information

Independent Verification and Validation of SAPHIRE 8 Software Project Plan

Independent Verification and Validation of SAPHIRE 8 Software Project Plan INL/EXT-09-17022 Rev. 2 Independent Verification and Validation of SAPHIRE 8 Software Project Plan March 2010 The INL is a U.S. Department of Energy National Laboratory operated by Battelle Energy Alliance

More information

Measurement Information Model

Measurement Information Model mcgarry02.qxd 9/7/01 1:27 PM Page 13 2 Information Model This chapter describes one of the fundamental measurement concepts of Practical Software, the Information Model. The Information Model provides

More information

A DIFFERENT KIND OF PROJECT MANAGEMENT: AVOID SURPRISES

A DIFFERENT KIND OF PROJECT MANAGEMENT: AVOID SURPRISES SEER for Software: Cost, Schedule, Risk, Reliability SEER project estimation and management solutions improve success rates on complex software projects. Based on sophisticated modeling technology and

More information

2. Analysis, Design and Implementation

2. Analysis, Design and Implementation 2. Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Individual Programs to Complete Application Systems Software Development: Goals, Tasks, Actors,

More information

OKLAHOMA SUBJECT AREA TESTS (OSAT )

OKLAHOMA SUBJECT AREA TESTS (OSAT ) CERTIFICATION EXAMINATIONS FOR OKLAHOMA EDUCATORS (CEOE ) OKLAHOMA SUBJECT AREA TESTS (OSAT ) FIELD 081: COMPUTER SCIENCE September 2008 Subarea Range of Competencies I. Computer Use in Educational Environments

More information

Systems Analysis and Design in a Changing World, Fourth Edition

Systems Analysis and Design in a Changing World, Fourth Edition Systems Analysis and Design in a Changing World, Fourth Edition Learning Objectives Describe implementation and support activities Choose an appropriate approach to program development Describe various

More information

September 25, 2014 EFFECTIVE METHODS FOR SOFTWARE AND SYSTEMS INTEGRATION P R E S E N T E D B Y: D R. B O Y D L. S U M M E R S

September 25, 2014 EFFECTIVE METHODS FOR SOFTWARE AND SYSTEMS INTEGRATION P R E S E N T E D B Y: D R. B O Y D L. S U M M E R S September 25, 2014 EFFECTIVE METHODS FOR SOFTWARE AND SYSTEMS INTEGRATION P R E S E N T E D B Y: D R. B O Y D L. S U M M E R S 1 Software Engineer (Quality) Defense and Space The Boeing Company - Seattle,

More information

Project Management Estimation. Week 11

Project Management Estimation. Week 11 Project Management Estimation Week 11 Announcement Midterm 2 Wednesday, May. 4 Scope Week 11 Week 13 Short answer questions Estimation Agenda (Lecture) Agenda (Lab) Implement a softwareproduct based on

More information

Applications in Business. Embedded Systems. FIGURE 1-17 Application Types and Decision Types

Applications in Business. Embedded Systems. FIGURE 1-17 Application Types and Decision Types 22 CHAPTER 1 Overview of Software Engineering she may determine his or her degree of confidence in the ES's results. These four application types-transaction, query, DSS, and ES-will be referenced throughout

More information

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II)

Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which

More information

PROJECT COST MANAGEMENT

PROJECT COST MANAGEMENT 7 PROJECT COST MANAGEMENT Project Cost Management includes the processes required to ensure that the project is completed within the approved budget. Figure 7 1 provides an overview of the following major

More information

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc.

Your Software Quality is Our Business. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. INDEPENDENT VERIFICATION AND VALIDATION (IV&V) WHITE PAPER Prepared by Adnet, Inc. February 2013 1 Executive Summary Adnet is pleased to provide this white paper, describing our approach to performing

More information

What is a life cycle model?

What is a life cycle model? What is a life cycle model? Framework under which a software product is going to be developed. Defines the phases that the product under development will go through. Identifies activities involved in each

More information

Software Project Management Part 2: Work Breakdown Structures

Software Project Management Part 2: Work Breakdown Structures Software Project Management Part 2: Work Breakdown Structures Introduction into Software Engineering Lecture 20 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Where are we?

More information

Project Scheduling & Tracking

Project Scheduling & Tracking Project Scheduling & Tracking Traditional Techniques: Work Breakdown Structure (WBS) Gantt Charts Precedence Diagrams Earned Value Planning It is the mark of an instructed mind to rest satisfied with the

More information

VIDYAVAHINI FIRST GRADE COLLEGE

VIDYAVAHINI FIRST GRADE COLLEGE VIDYAVAHINI FIRST GRADE COLLEGE SOFTWARE ENGINEERING 5 th Sem BCA Vidyavahini First Grade College Near Puttanjaneya Temple, Kuvempunagar, Tumkur 572103. E-Mail:vvfgc.bca@gmail.com Website:www.vidyavahini.org/bca

More information

Introduction to Embedded Systems. Software Update Problem

Introduction to Embedded Systems. Software Update Problem Introduction to Embedded Systems CS/ECE 6780/5780 Al Davis logistics minor Today s topics: more software development issues 1 CS 5780 Software Update Problem Lab machines work let us know if they don t

More information

Manual Techniques, Rules of Thumb

Manual Techniques, Rules of Thumb Seminar on Software Cost Estimation WS 2002/2003 Manual Techniques, Rules of Thumb Pascal Ziegler 1 Introduction good software measurement and estimation are important simple methods are widely used simple,

More information

Basic Unified Process: A Process for Small and Agile Projects

Basic Unified Process: A Process for Small and Agile Projects Basic Unified Process: A Process for Small and Agile Projects Ricardo Balduino - Rational Unified Process Content Developer, IBM Introduction Small projects have different process needs than larger projects.

More information

Adapted from slides by John Musser

Adapted from slides by John Musser Adapted from slides by John Musser 1 What s the difference? Plan Identify activities. No specific start and end dates. Estimate Determine the size and duration of activities. Schedule Add specific start

More information

Program Lifecycle Methodology Version 1.7

Program Lifecycle Methodology Version 1.7 Version 1.7 March 30, 2011 REVISION HISTORY VERSION NO. DATE DESCRIPTION AUTHOR 1.0 Initial Draft Hkelley 1.2 10/22/08 Updated with feedback Hkelley 1.3 1/7/2009 Copy edited Kevans 1.4 4/22/2010 Updated

More information

PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING

PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING PMI PMBOK & ESTIMATING 03-23-05 Christine Green, PMI PMBOK and Estimating EDS, Delivery

More information

Improving Software Project Management Skills Using a Software Project Simulator

Improving Software Project Management Skills Using a Software Project Simulator Improving Software Project Management Skills Using a Software Project Simulator Derek Merrill and James S. Collofello Department of Computer Science and Engineering Arizona State University Tempe, AZ 85287-5406

More information

COCOMO II and Big Data

COCOMO II and Big Data COCOMO II and Big Data Rachchabhorn Wongsaroj*, Jo Ann Lane, Supannika Koolmanojwong, Barry Boehm *Bank of Thailand and Center for Systems and Software Engineering Computer Science Department, Viterbi

More information

TDWI strives to provide course books that are content-rich and that serve as useful reference documents after a class has ended.

TDWI strives to provide course books that are content-rich and that serve as useful reference documents after a class has ended. Previews of TDWI course books are provided as an opportunity to see the quality of our material and help you to select the courses that best fit your needs. The previews can not be printed. TDWI strives

More information

Software Engineering. Objectives. Designing, building and maintaining large software systems

Software Engineering. Objectives. Designing, building and maintaining large software systems Software Engineering Objectives Designing, building and maintaining large software systems To define software engineering and explain its importance To discuss the concepts of software products and software

More information

Project Management Planning

Project Management Planning Initial Release 1. Overview of Project Paralleling the development of the schedule is the development of a budget. At the initial stages of project planning, budgeting is the determination of costs associated

More information

Software Engineering 1

Software Engineering 1 THE BCS PROFESSIONAL EXAMINATIONS Diploma April 2006 EXAMINERS REPORT Software Engineering 1 General Comments Most of the scripts produced by candidates this year were well structured and readable, showing

More information

IDC Reengineering Phase 2 & 3 US Industry Standard Cost Estimate Summary

IDC Reengineering Phase 2 & 3 US Industry Standard Cost Estimate Summary SANDIA REPORT SAND2015-20815X Unlimited Release January 2015 IDC Reengineering Phase 2 & 3 US Industry Standard Cost Estimate Summary Version 1.0 James Mark Harris, Robert M. Huelskamp Prepared by Sandia

More information

Software Engineering CSCI 4490. Lesson 9 Project Management Part 1- Planning & Estimating. February 23, 2015

Software Engineering CSCI 4490. Lesson 9 Project Management Part 1- Planning & Estimating. February 23, 2015 Lesson 9 Project Management Part 1- Planning & Estimating February 23, 2015 Projects and Project Managers Project a [temporary] sequence of unique, complex, and connected activities having one goal or

More information

PROJECT SCOPE MANAGEMENT

PROJECT SCOPE MANAGEMENT 5 PROJECT SCOPE MANAGEMENT Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the project successfully

More information

Echtzeittesten mit MathWorks leicht gemacht Simulink Real-Time Tobias Kuschmider Applikationsingenieur

Echtzeittesten mit MathWorks leicht gemacht Simulink Real-Time Tobias Kuschmider Applikationsingenieur Echtzeittesten mit MathWorks leicht gemacht Simulink Real-Time Tobias Kuschmider Applikationsingenieur 2015 The MathWorks, Inc. 1 Model-Based Design Continuous Verification and Validation Requirements

More information

Software cost estimation

Software cost estimation CH26_612-640.qxd 4/2/04 3:28 PM Page 612 26 Software cost estimation Objectives The objective of this chapter is to introduce techniques for estimating the cost and effort required for software production.

More information

Dr. Barry W. Boehm USC Center for Software Engineering

Dr. Barry W. Boehm USC Center for Software Engineering 7th Annual Practical Software and Systems Measurement Users Group Conference Keystone, CO July 16, 2003 Dr. Barry W. Boehm USC 1 Workshop Agenda Day 1 (1:30 AM 5:00 PM 7/16) Next-level tutorial Review

More information

Chapter 12. Development Tools for Microcontroller Applications

Chapter 12. Development Tools for Microcontroller Applications Chapter 12 Development Tools for Microcontroller Applications Lesson 01 Software Development Process and Development Tools Step 1: Development Phases Analysis Design Implementation Phase 1 Phase 2 Phase

More information

Michigan Staff Augmentation Management Program Contract Job Titles and Descriptions

Michigan Staff Augmentation Management Program Contract Job Titles and Descriptions Applications... 3 1. Programmer Analyst... 3 2. Programmer... 5 3. Software Test Analyst... 6 4. Technical Writer... 9 5. Business Analyst... 10 6. System Analyst... 12 7. Software Solutions Architect...

More information

Digital System Design. Digital System Design with Verilog

Digital System Design. Digital System Design with Verilog Digital System Design with Verilog Adapted from Z. Navabi Portions Copyright Z. Navabi, 2006 1 Digital System Design Automation with Verilog Digital Design Flow Design entry Testbench in Verilog Design

More information

Chapter 13: Program Development and Programming Languages

Chapter 13: Program Development and Programming Languages 15 th Edition Understanding Computers Today and Tomorrow Comprehensive Chapter 13: Program Development and Programming Languages Deborah Morley Charles S. Parker Copyright 2015 Cengage Learning Learning

More information

ELET 7404 Embedded & Real Time Operating Systems. Fixed-Point Math. Chap. 9, Labrosse Book. Fall 2007

ELET 7404 Embedded & Real Time Operating Systems. Fixed-Point Math. Chap. 9, Labrosse Book. Fall 2007 ELET 7404 Embedded & Real Time Operating Systems Fixed-Point Math Chap. 9, Labrosse Book Fall 2007 Fixed-Point Math Most low-end processors, such as embedded processors Do not provide hardware-assisted

More information

What methods are used to conduct testing?

What methods are used to conduct testing? What is testing? Testing is the practice of making objective judgments regarding the extent to which the system (device) meets, exceeds or fails to meet stated objectives What the purpose of testing? There

More information

Work Breakdown Structures. Configuration & Build Management. Object-Oriented Software Engineering. Using UML, Patterns, and Java

Work Breakdown Structures. Configuration & Build Management. Object-Oriented Software Engineering. Using UML, Patterns, and Java Object-Oriented Software Engineering Using UML, Patterns, and Java Configuration & Build Management Work Breakdown Structures Outline of today s class Determining Work and Tasks Sizes Work Breakdown Structure

More information

Peter Mileff PhD SOFTWARE ENGINEERING. The Basics of Software Engineering. University of Miskolc Department of Information Technology

Peter Mileff PhD SOFTWARE ENGINEERING. The Basics of Software Engineering. University of Miskolc Department of Information Technology Peter Mileff PhD SOFTWARE ENGINEERING The Basics of Software Engineering University of Miskolc Department of Information Technology Introduction Péter Mileff - Department of Information Engineering Room

More information