Sri Vidya College of Engineering & Technology-Virudhunagar
|
|
- Roger Ellis
- 5 years ago
- Views:
Transcription
1 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for Introduction to Software Engineering Time: 50 Minutes Lesson. No Unit I Lesson No: 1/9 1.Content List: Introduction to Software Engineering 2.Skill addressed: Understand the Concepts of Software Engineering 3.Objectives of this Lesson Plan: To enable students to list the basic Concepts of Software Engineering 4.Outcome(s): Understanding And Analyse the basic concepts of Software Engineering 5.Link sheet: 1. What is Software? 2. What is Software Engineering? 3. What is Software Product? 4. What is Software Process? CS6403 SOFTWARE ENGINEERING Page 1
2 6.Evocation: (5 Minutes) Subject introduction (40 Minutes): Topics: 7.Lecture notes Introduction Examples: What is Software Engineering? INTRODUCTION TO SOFTWARE ENGINEERING AND PROCESS,PRODUCT Software engineering Software engineering is a discipline in which theories, methods and tools are applied to develop professional software. Software Software is nothing but a collection of computer programs that are related documents that are indented to provide desired features, functionalities and better performance. characteristics of the software a. Software is engineered, not manufactured. b. Software does not wear out. Most software is custom built rather than being assembled from components. various categories of software o System software o Application software o Engineering/Scientific software o Embedded software software process CS6403 SOFTWARE ENGINEERING Page 2
3 Software process is defined as the structured set of activities that are required to develop the software system fundamental activities of a software process Specification Design and implementation Validation Evolution 8.Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, Application: Business software, Data mining closely related to database CS6403 SOFTWARE ENGINEERING Page 3
4 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for Life Cycle Model Waterfall, Prototyping,RAD model Time: 50 Minutes Lesson. No Unit I Lesson No: 2/9 1.Content List: Life Cycle Models 2.Skill addressed: Understand the Concepts of Software Engineering Life Cycle Model 3.Objectives of this Lesson Plan: To enable students to list the Life Cycle Model in Software Engineering 4.Outcome(s): Understandi And Analyse the basic concepts of Software Engineering Life cycle model 5. Link sheet: 1. Name the Evolutionary process Models 2. What are the merits of waterfall model? 3. What are the merits of waterfall model? 4. What are theadvantages &Disadvantages of waterfall model? CS6403 SOFTWARE ENGINEERING Page 4
5 6.Evocation: (5 Minutes) Subject introduction (40 Minutes): Topics: Introduction to lifecycle model Waterfall model, prototyping model RAD 7.Lecture Notes Waterfall model/linear Sequential Model/classic life cycle : Systems Engineering Software as part of larger system, determine requirements for all system elements, allocate requirements to software. Software Requirements Analysis Develop understanding of problem domain, user needs, function, performance, interfaces,. Software Design Multi-step process to determine architecture, interfaces, data structures, functional detail. Produces (high-level) form that can be checked for quality, conformance before coding. Coding Produce machine readable and executable form, match HW, OS and design needs. Testing Confirm that components, subsystems and complete products meet requirements, specifications and quality, find and fix defects. Maintenance Incrementally, evolve software to fix defects, add features, adapt to new condition. Often 80% of effort spent here! CS6403 SOFTWARE ENGINEERING Page 5
6 Waterfall model phases: Requirements analysis and definition System and software design Implementation and unit testing Integration and system testing Operation and maintenance The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase. Each phase terminates only when the documents are complete and approved by the SQA group. Maintenance begins when the client reports an error after having accepted the product. It could also begin due to a change in requirements after the client has accepted the product Waterfall model: Advantages: Disciplined approach Careful checking by the Software Quality Assurance Group at the end of each phase. Testing in each phase. Documentation available at the end of each phase. Waterfall model problems: It is difficult to respond to changing customer requirements. Therefore, this model is only appropriate when the requirements are well-understood and changes will be fairly limited during the design process. Few business systems have stable requirements. The waterfall model is mostly used for large systems engineering projects where a system is developed at several sites. The customer must have patience. A working version of the program will not be available until late in the project time-span Feedback from one phase to another might be too late and hence expensive. The Prototyping Models: Often, a customer defines a set of general objectives for software but does not identify detailed input, processing, or output requirements. In other cases, the developer may be unsure of the efficiency of an algorithm, the adaptability of an operating system, or the form that human machine interaction should take In this case prototyping paradigm may offer the best approach Requirements gathering Quick design Prototype building Prototype evaluation by customers Prototype may be refined Prototype thrown away and software developed using formal process{ it is used to define the requirement} Prototyping CS6403 SOFTWARE ENGINEERING Page 6
7 Strengths: Requirements can be set earlier and more reliably Customer sees results very quickly. Customer is educated in what is possible helping to refine requirements. Requirements can be communicated more clearly and completely Weaknesses: Requires a rapid prototyping tool and expertise in using it a cost for the development organisation Smoke and mirrors - looks like a working version, but it is not. The RAD Model: Rapid Application Development is a linear sequential software development process model that emphasizes an extremely short development cycle Rapid application achieved by using a component based construction approach If requirements are well understood and project scope is constrained the RAD process enables a development team to create a fully functional system Prototype thrown away and software developed using formal process{ it is used to define the requirement} Prototyping Strengths: Requirements can be set earlier and more reliably Customer sees results very quickly. Customer is educated in what is possible helping to refine requirements. Weaknesses: Requires a rapid prototyping tool and expertise in using it a cost for the development organisation Smoke and mirrors - looks like a working version, but it is not. The RAD Model: Rapid Application Development is a linear sequential software development process model that emphasizes an extremely short development cycle Rapid application achieved by using a component based construction approach If requirements are well understood and project scope is constrained the RAD process enables a development team to create a fully functional system Application generation Testing and turnover Business modeling: What information drives the business process? What information is generated? Who generates it? Data Modeling: The information flow defined as part of the business modeling phase is refined into a set of data objects that are needed to support the business. The characteristics ( called attributes) of each object are identified and the relationships between these objects are defined CS6403 SOFTWARE ENGINEERING Page 7
8 Process modeling: The data modeling phase are transformed to achieve the information flow necessary to implement a business function. Processing descriptions are created for adding, modifying, deleting, or retrieving a data object Application generation: RAD assumes the use of 4 generation techniques. Rather than creating software using conventional 3 generation programming languages, the RAD process works to reuse existing program components (when possible) or created reusable components (when necessary) Testing and Turnover: Since the RAD process emphasizes reuse, many of the program components have already been testing. This reduces over all testing time. However, new components must be tested and all interfaces must be fully exercised Advantages &Disadvantages of RAD: Advantages Extremely short development time. Uses component-based construction and emphasises reuse and code generation Disadvantages Large human resource requirements (to create all of the teams). Requires strong commitment between developers and customers for rapid-fire activities. High performance requirements maybe can t be met (requires tuning the components). 8. Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, Application: Business software, Data mining closely related to database CS6403 SOFTWARE ENGINEERING Page 8
9 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for Life Cycle Model Incremental model, Spiral model Time: 50 Minutes Lesson. No Unit I Lesson No: 3/9 1.Content List: Life Cycle Models 2. Skill addressed: o Understand the Concepts of Software Engineering Life Cycle Model 3.Objectives of this Lesson Plan: o To enable students to list the Life Cycle Model in Software Engineering 4.Outcome(s): o Understand And Analyze the basic concepts of Software Engineering Life cycle model 5. Link sheet: 1.What are the merits of incremental model? 2.What are the merits of spiral model 3.Define spiral model 6.Evocation: (5 Minutes) CS6403 SOFTWARE ENGINEERING Page 9
10 Subject introduction (40 Minutes): Topics: Introduction to incremental model Spiral model 7.Lecture Notes The Incremental Model The Incremental development Combination of linear + prototype Rather than deliver the system as a single delivery, the development and delivery is broken down into increments with each increment delivering part of the required functionality CS6403 SOFTWARE ENGINEERING Page 10
11 User requirements are prioritised and the highest priority requirements are included in early increments Once the development of an increment is started, the requirements are frozen though requirements for later increments can continue to evolve Incremental development advantages: The customer is able to do some useful work after release Lower risk of overall project failure The highest priority system services tend to receive the most testing Spiral Model: Spiral model sectors: Customer communication Tasks required to establish effective communication between developer and customer Planning - The tasks required to define recourses, timelines, and project is reviewed and the next phase of the spiral is planned Risk analysis Risks are assessed and activities put in place to reduce the key Risks engineering Tasks required to build one or more representations of the application Construction & release Tasks required to construct, test, install and provide user support (e.g documentation and trainin Spiral Model Advantages: Focuses attention on reuse options. Focuses attention on early error elimination. Puts quality objectives up front. 8.Textbook: T1: Ian Sommerville, Software engineering, Seventh Edition, Pearson Education Asia, T2: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, Application: Software field CS6403 SOFTWARE ENGINEERING Page 11
12 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for SPM-Estimation and Loc based Estimation Time: 50 Minutes Lesson. No Unit I Lesson No: 4,5/9 1.Content List: Estimation and Loc based Estimation 2. Skill addressed: Understand the Concepts of SPM Estimation and Loc based Estimation 3.Objectives of this Lesson Plan: To enable students to list the SPM Estimation and Loc based Estimation 4.Outcome(s): Understandi And Analyse the basic concepts of SPM Estimation and Loc based Estimation 5.Link sheet: 1. Define SPM 2.What is meant by Loc based estimation? 6. Evocation: (5 Minutes CS6403 SOFTWARE ENGINEERING Page 12
13 Subject introduction (40 Minutes): 7.Lecture Notes Project Planning Software project planning encompasses five major activities Estimation, scheduling, risk analysis, quality management planning, and change management planning Estimation determines how much money, effort, resources, and time it will take to build a specific system or product The software team first estimates The work to be done The resources required The time that will elapse from start to finish Then they establish a project schedule that Defines tasks and milestones Identifies who is responsible for conducting each task Specifies the inter-task dependencies Estimation Planning requires technical managers and the software team to make an initial commitment Process and project metrics can provide a historical perspective and valuable input for generation of quantitative estimates Past experience can aid greatly Estimation carries inherent risk, and this risk leads to uncertainty The availability of historical information has a strong influence on estimation risk When software metrics are available from past projects Estimates can be made with greater assurance Schedules can be established to avoid past difficulties Overall risk is reduced Estimation risk is measured by the degree of uncertainty in the quantitative estimates for cost, schedule, and resources Nevertheless, a project manager should not become obsessive about estimation Plans should be iterative and allow adjustments as time passes and more is made certain Estimation of resources, cost, and schedule for a software engineering effort requires experience access to good historical information (metrics the courage to commit to quantitative predictions when qualitative information is all that exists Estimation carries inherent risk and this risk leads to uncertainty Project Estimation Project scope must be understood Elaboration (decomposition) is necessary Historical metrics are very helpful At least two different techniques should be used Uncertainty is inherent in the process Estimation Techniques Past (similar) project experience Conventional estimation techniques task breakdown and effort estimates size (e.g., FP) estimates Empirical models Automated tools CS6403 SOFTWARE ENGINEERING Page 13
14 Estimation Accuracy The degree to which the planner has properly estimated the size of the product to be built the ability to translate the size estimate into human effort, calendar time, and dollars (a function of the availability of reliable software metrics from past projects) the degree to which the project plan reflects the abilities of the software team the stability of product requirements and the environment that supports the software engineering effort. Problem based Estimation In general, the LOC/pm and FP/pm metrics should be computed by project domain Important factors are team size, application area, and complexity LOC and FP estimation differ in the level of detail required for decomposition with each value For LOC, decomposition of functions is essential and should go into considerable detail (the more detail, the more accurate the estimate) For FP, decomposition occurs for the five information domain characteristics and the 14 adjustment factors External inputs, external outputs, external inquiries, internal logical files, external interface files Example of baseline productivity metrics are LOC/pm or FP/pm Making the use of single baseline productivity metric is discouraged In general, LOC/pm or FP/pm averages should be computed by project domain Local domain averages should be used Statistical approach three-point or expected-value estimate S = (s opt + 4s m + s pess )/6 S = expected-value for the estimation variable (size) s opt = optimistic value s m = most likely value s pess = pessimistic value CS6403 SOFTWARE ENGINEERING Page 14
15 Example Loc Based Estimation Function User interface and control facilities (UICF) Two-dimensional geometric analysis (2DGA) Three-dimensional geometric analysis (3DGA) Database management (DBM) Computer graphics display facilities (CGDF) Peripheral control function (PCF) Design analysis modules (DAM) Estimated LOC 2,300 5,300 6,800 3,350 4,950 2,100 8,400 Estimated lines of code 33,200 Estimated lines of code = W = 33,200 Let, Average productivity = 620 LOC/pm = X Labor rate = $8,000 per month = Y So, Cost per line of code = Z = Y/X = $13 (approx.) Total estimated project cost = W*Z = $431,000 (approx.) Estimated effort = W/X = 54 person-months (approx) 8.Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, 2005 CS6403 SOFTWARE ENGINEERING Page 15
16 Sri Vidya College of Engineering &Technology Department of Information Technology Class Subject Code II Year (04 Semester) CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for FP based Estimation Time: 50 Minutes Lesson. No Unit I Lesson No:6,/9 1.Content List: FP based Estimation 2.Skill addressed: Analyze and understanding the Concepts of FP based Estimation 3.Objectives of this Lesson Plan: To enable students to understand the FP based Estimation 4.Outcome(s): Understand And Analyse the FP based Estimation 5.Link sheet: 1. What is meant by Estimstion? 2. What is ment by FB based estimation? 6.Evocation: (5 Minutes) CS6403 SOFTWARE ENGINEERING Page
17 Subject introduction (40 Minutes): Topics: Example FB Based Estimation Information Domain Value Count Weighting factor Simple Average Complex External Inputs (EIS) 3 X = 9 External Outputs (EOs) 2 X = 8 External Inquiries (EQs) 2 X = 6 Internal Logical Files (ILFs) External Interface Files (EIFs) 1 X = 7 4 X = 20 Count Total 50 CS6403 SOFTWARE ENGINEERING Page
18 Fig.Value adjustment factor Now, FP estimated = count-total [ (F i )] F i (i = 1 to 14 are value adjustment factors) So, FP estimated = W = 320 [ ] = 375 (approx.) Let, Average Productivity = X = 6.5 FP/pm Labor rate = Y = $8,000 per month So, Cost per FP = Z = Y/X = $1,230 (approx.) Total estimated project cost = W*Z = $461,000 (approx.) Estimated effort = W/X = 58 person-months (approx) Empirical Estimation Models Uses empirically derived formulas to predict effort as a function of LOC or FP The empirical data are derived from a limited sample of projects So, no estimation model is appropriate for all classes of s/w and in all development environments The results obtained from such models must be used judiciously An estimation model should be calibrated to reflect local conditions Structure of Estimation model Derived using regression analysis on data collected from past s/w projects Overall structure, E = A + B (e v ) c Here, o A, B, and C are empirically derived constants o E is effort in person-months CS6403 SOFTWARE ENGINEERING Page
19 o e v is the estimation variable (either LOC or FP) Some form of project adjustment component is also used Example of a LOC-oriented estimation model (Bailey-Basili model) o E = (KLOC) 1.16 Example of a FP-oriented estimation model (Kemerer model) o E = FP Estimation models must be calibrated for local needs 8. Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition,McGraw-Hill International Edition, 2005 CS6403 SOFTWARE ENGINEERING Page
20 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for COCOMO Model,Project scheduling Time: 50 Minutes Lesson. No Unit I Lesson No: 7,8/9 1.Content List: COCOMO Model,Project scheduling 2.Skill addressed: Analyze the Concepts of COCOMO Model,Project scheduling 3.Objectives of this Lesson Plan: 4.Outcome(s): 5. Link sheet: To enable students to understand the COCOMO Model,Project scheduling Understand And Analyze the COCOMO Model, Project scheduling 1. What is meant by COCOMO model? 2. Define Scheduling? 6.Evocation: (5 Minutes) Subject introduction (40 Minutes): Topics: COCOMO Model,Project scheduling 7.Lecture Notes COCOMO Model Stands for COnstructive COst MOdel Introduced by Barry Boehm in 1981 in his book Software Engineering Economics Became one of the well-known and widely-used estimation models in the industry It has evolved into a more comprehensive estimation model called COCOMO II COCOMO II is actually a hierarchy of three estimation models CS6403 SOFTWARE ENGINEERING Page
21 As with all estimation models, it requires sizing information and accepts it in three forms: object points, function points, and lines of source code Application composition model - Used during the early stages of software engineering when the following are important Prototyping of user interfaces Consideration of software and system interaction Assessment of performance Evaluation of technology maturity Early design stage model Used once requirements have been stabilized and basic software architecture has been established Post-architecture stage model Used during the construction of the software COCOMO Cost Drivers Personnel Factors Applications experience Programming language experience Virtual machine experience Personnel capability Personnel experience Personnel continuity Platform experience Language and tool experience Product Factors Required software reliability Database size Software product complexity Required reusability Documentation match to life cycle needs Product reliability and complexity Platform Factors Execution time constraint Main storage constraint Computer turn-around time Virtual machine volatility Platform volatility Platform difficulty Project Factors Use of software tools Use of modern programming practices Required development schedule Classified security application Multi-site development Requirements volatility Project Scheduling Split project into tasks and estimate time and resources required to complete each task Organize tasks concurrently to make optimal use of workforce Minimize task dependencies to avoid delays caused by one task waiting for another to complete Dependent on project managers intuition and experience Scheduling Problem Estimating the difficulty of problems and hence the cost of developing a solution is hard CS6403 SOFTWARE ENGINEERING Page
22 Productivity is not proportional to the number of people working on a task Adding people to a late project makes it later because of communication overheads The unexpected always happens. Always allow contingency in planning 8.Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, 2005 CS6403 SOFTWARE ENGINEERING Page
23 Sri Vidya College of Engineering &Technology Department of Information Technology Class II Year (04 Semester) Subject Code CS6403 Subject SOFTWARE ENGINEERING Prepared By R.Vidhyalakshmi Lesson Plan for Risk Management Time: 50 Minutes Lesson. No Unit I Lesson No: 9/9 1.Content List: Risk Management 2.Skill addressed: Analyze the Concepts of Risk Management 3.Objectives of this Lesson Plan: 4. Outcome(s): 5. Link sheet: To enable students to understand the Risk Management Understand And Analyse the Risk Management 1. What is meant by risk? 2. How to identify the risk? 6.Evocation: (5 Minutes) Subject introduction (40 Minutes): Topics: Risk Management CS6403 SOFTWARE ENGINEERING Page
24 7.Lecture Notes Risk Management Risks are potential problems that affect successful completion of project which involves Uncertainty and potential lose Risk analysis and management helps the s/w team to overcome the problems caused by the risks. The work product is called a Risk Mitigation, Monitoring and Management Plan(RMMMP). (a) risk strategies: * Reactive strategies: also known as fire fighting, project team sets resources aside to deal with the problem and does nothing until the risks became a problem. * Pro active strategies: risk management begins long before technical works starts, risks are Identified and prioritized by importance, the team lead builds a plan to avoid such risks. (b) S/W risks: * Project risk: * Technical risk: threaten product quality and time line * Business risk: threaten the validity of the s/w. * Known risk: predictable from careful evaluation of current project plan and those extrapolated from past project experience. * Unknown risk: some problems simply occur without warning. (c) Risk identification: * Product specific risk: the project plan and s/w statement of scope are examined to identify any specific characteristics. * Generic risk: Potential threads to any s/w products. (d) Risk impact: * Risk components: performance, cost, support, schedule * Risk impact: negligible, marginal, critical, catastrophic. The risk drivers affecting each risk component are classified according to their impact category and potential consequence of each undetected s/w fault. (e) Risk projection: Establish a scale that reflects the perceived likelihood of each risks. Delineate the consequence of the risk. Estimate the impact of the risk on project and product. (f) risk table construction: * List all risks in the first column of the table * Classify each risk and enter the category label in column 2 * Determine a probability for each risk and enter to third column. * Enter the severity of the risk in column 4. * Sort the table by probability and impact value. * First priority concerns must be managing(rmmm in fifth column). (g) assessing risk impact: * Factors affecting risk consequences: nature, scope, and timing of the risk. * If costs are associated with each risk table entry Halstead s risk exposure can be adopted and added to risk table. RE= probability * cost (h) risk assessment: * Defines referent levels for each project risk that can cause project termination. * Attempt to develop a relationship between each risk triple. * Predict the set of referent point that define a region of termination, bounded by a curve or areas of uncertainties. CS6403 SOFTWARE ENGINEERING Page
25 (i) risk refinement: * process of restating the risks as set of more detailed risk that will be easier to migrate, migrate, and manage. * CTC format may be a good representation for the detailed risk( condition transition consequence) (J) RISK MITIGATION, MONITORING AND MANAGEMENT: * Risk mitigation: proactive planning for risk avoidance * risk monitoring: accessing whether predicted risks occur or not, collect information for further risk analysis. * Risk management and contingency planning : actions to be taken in the event that mitigation step have failed and the risk become a life problem. (k) safety risks and hazards: Risks also associated with s/w failures that occur in the field after the development project has ended. Software safety and hazard analysis and quality assurance activity (l) risk information sheets: alternative to RMMM in which each risk is documented separately. RIS are maintain using a database system (m)examples: Pilot study Market research study of business impact risks Training (n) outline of risk management: identification-define risks for the project projection attempt to indicate quantitative likelihood that a risk will occur. Assessment evaluate the accuracy of projection and prioritize risks. Management and monitoring: move to avert those risks that are of concern and monitor all circumstance that may leave to risks. 1. risk identification: A systematic attempt to specify thread to the project plan. Both generic and product specific risks Risk identification : check list (i) people / staff (ii) customer / user (iii) business/business impact (iv) application, product size, technology (v) process maturity 2. risk projection: establish a scale that reflects the perceived likelihood of the risks. Define the consequence of the risks. Estimate the impact of the risk on the project and or the product 3. risk assessment: recording risks: building the risk table (i) estimate the probability of the occurrence (ii) estimate the impact on the project (iii) add RMMM plan CS6403 SOFTWARE ENGINEERING Page
26 (iv) sort the table by probability and impact 4. risk mitigation, monitoring and management: monitoring: what factors can be track that will enable us to determine the causes of risks. Management: what contingency plans do we have if the risks become a real 8. Textbook: T1: Roger S. Pressman, Software Engineering A practitioner s Approach, Sixth Edition, McGraw-Hill International Edition, 2005 CS6403 SOFTWARE ENGINEERING Page
Estimation for Software Projects. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 26 Estimation for Software Projects Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman
More informationChapter 4 Software Process and Project Metrics
Chapter 4 Software Process and Project Metrics 1 Measurement & Metrics... collecting metrics is too hard... it's too time-consuming... it's too political... it won't prove anything... Anything that you
More informationTopic 12. SW/CIS Project Estimates (LOC, FP, efforts, cost, etc.)
Topic 12 SW/CIS Project Estimates (LOC, FP, efforts, cost, etc.) SW/CIS Development Project Estimation: An Overview 1. SW/CIS D&D Project planning involves estimating how much time, effort, money, and
More informationThe software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
More informationIntroduction to Software Engineering
UNIT I SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, objects oriented) -system engineering computer
More informationSoftware Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
More informationSoftware Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a comple
Estimation for Software Projects 1 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a complex technical project.
More informationSoftware Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationPertemuan 2. Software Engineering: The Process
Pertemuan 2 Software Engineering: The Process Collect Your Project Topic What is Software Engineering? Software engineering is the establishment and sound engineering principles in order to obtain economically
More informationII. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
II. Software Life Cycle Laurea Triennale in Informatica Corso di Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationObjectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationTopics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
More informationSlides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only
Chapter 28 Risk Analysis Slide Set to accompany Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman For non-profit educational
More informationChapter 3 Prescriptive Process Models
Chapter 3 Prescriptive Process Models - Generic process framework (revisited) - Traditional process models - Specialized process models - The unified process Generic Process Framework Communication Involves
More informationLecture 1. In practice, most large systems are developed using a. A software process model is an abstract representation
Chapter 2 Software Processes Lecture 1 Software process descriptions When we describe and discuss processes, we usually talk about the activities in these processes such as specifying a data model, designing
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationUNIT V PROJECT MANAGEMENT
UNIT V PROJECT MANAGEMENT ESTIMATION S/W is the most expensive element of virtually all computer based systems The accuracy of a s/w project estimate is predicated on a number of things: The degree to
More informationDEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING UNIT-1
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Year & Semester : IV Subject Code : CS6403 Subject Name : Software Engineering Degree & Branch : B.E & CSE UNIT-1 1. What is software engineering? 2. What
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationContents. Today Project Management. What is Project Management? Project Management Activities. Project Resources
Contents Last Time - Software Development Processes Introduction Software Development Processes Project Management Requirements Engineering Software Construction Group processes Quality Assurance Software
More informationSelecting Software Development Life Cycles. Adapted from Chapter 4, Futrell
Selecting Software Development Life Cycles Adapted from Chapter 4, Futrell Examples of Software Life Cycle Models Classical Waterfall Waterfall with feedback V-Shaped Prototyping Incremental Spiral Rapid
More informationA Comparative Study on Software Development Life Cycle Models
A Comparative Study on Software Development Life Cycle Models Prof. Supriya Madhukar Salve 1, Prof. Syed Neha Samreen 2, Prof. Neha Khatri-Valmik 3 123Assistant Professor, Dept. of Computer Science and
More informationCLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS
More informationA New Divide & Conquer Software Process Model
A New Divide & Conquer Software Process Model First A. Hina Gull, Second B. Farooque Azam Third C. Wasi Haider Butt, Fourth D. Sardar Zafar Iqbal Abstract The software system goes through a number of stages
More informationSoftware Engineering
Software Engineering Part I. Aspects and Models of Software Development Process Gunadarma University 1 Software Engineering Outline 1 Introduction 2 Aspects of Software Engineering Software Engineering
More informationSoftware Project Management
Software Project Management Ali Ameer Gondal Assistant Professor University of Engineering & Technology Taxila, Pakistan ali.ameer@uettaxila.edu.pk 27 th Oct. 2011 Software Project Management Lecture #
More informationManagement and MDD. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems March 6, 2007
Management and MDD Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems March 6, 2007 2 Management Software Engineering Management 3 Req. Design Const. Test Iterations Management 4 5
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More informationFundamental estimation questions. Software cost estimation. Costing and pricing. Software cost components. Software pricing factors
Fundamental estimation questions Software cost estimation How much effort is required to complete an activity? How much calendar time is needed to complete an activity? What is the total cost of an activity?
More information03. Perspective Process Models
03. Perspective Process Models Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2017 Prescriptive Process Models advocates an orderly approach to software
More informationMTAT Software Economics. Session 6: Software Cost Estimation
MTAT.03.244 Software Economics Session 6: 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 informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationNote 10: Software Process
Computer Science and Software Engineering University of Wisconsin - Platteville Note 10: Software Process Yan Shi Lecture Notes for SE 3330 UW-Platteville Based on Pressman Chapter 2 & 3 Software Process
More informationSoftware cost estimation
Software cost estimation Joseph Bonello (based on slides by Ian Sommerville) Objectives To introduce the fundamentals of software costing and pricing To describe three metrics for software productivity
More informationSoftware Engineering COMP 201
Software Engineering COMP 201 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 Lecture 2 Software Processes
More informationSDLC AND MODEL SELECTION: A STUDY
SDLC AND MODEL SELECTION: A STUDY V. Therese Clara Asst professor of Computer Science, Madurai Kamaraj University College, Madurai, India ABSTRACT In the software industry, the frequency of failure of
More informationFirst, a detailed description of function points Then, how to use function points and lines of code for cost estimation.
Cost Page 1 Cost modeling Monday, October 05, 2009 11:17 AM First, a detailed description of function points Then, how to use function points and lines of code for cost estimation. Reading: SEPA Chapter
More informationObjectives. Topics covered. Software project management. Management activities. Software management distinctions. Project management
Objectives Project management To explain the main tasks undertaken by project managers To introduce software project management and to describe its distinctive characteristics To discuss project planning
More informationChapter 5 Software Project Planning
This chapter will discuss the following concepts: 5-1 Observations on Estimating. 5-2 Project Planning Objectives. 5-3 Software Scope. 5-4 Resources. 5-5 Software Project Estimation. 5-6 Decomposition
More informationChapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
More informationExplore Comparative Analysis Software Development Life Cycle Models
Explore Comparative Analysis Software Development Life Cycle Models Anshu Mishra Assistant Professor, Department of Information Science and Engineering Jyothy Institute of Technology, Bangalore Abstract-The
More informationThe Product and the Process The Product The Evolving Role of Software Software Software: A Crisis on the Horizon Software Myths Summary References
The Product and the Process The Product The Evolving Role of Software Software Software: A Crisis on the Horizon Software Myths Further Readings and Information Sheets The Process Software Engineering
More informationGoals of course. Themes: What can you do to evaluate a new technique? How do you measure what you are doing?
MSWE 607: Software Life Cycle methods and Techniques Instructor: Professor Marvin V. Zelkowitz Office: 4121 AV Williams Phone: 405-2690 or 403-8935 (Fraunhofer Center) Email (Best way to contact) mvz@cs.umd.edu
More informationTutorial Software is the differentiating characteristics in many computer based products and systems. Provide examples of two or three products
Tutorial -1 1. Software is the differentiating characteristics in many computer based products and systems. Provide examples of two or three products and at least one system. 2. Provide five examples of
More informationSoftware Engineering Part 2
CS 0901341 Software Engineering Part 2 In this part, we look at 2.1 Software Process 2.2 Software Process Models 2.3 Tools and Techniques for Processing Modelling As we saw in the previous part, the concept
More informationSoftware Process and Project Metrics
Software Process and Project Metrics Software Engineering 5 1 Measurements When you can measure what you are speaking about and can express it in numbers, you know something about it. But when you cannot
More informationSoftware Engineering. Lab Manual. Software Engineering BE(comp) VII semester
Lab Manual Software Engineering BE(comp) VII semester 1 Index Sr. No. of Programming Page No. 1 Studying Various phases of Water-Fall Model. 3 2 3 Prepare SRS for Banking or On line book store domain problem.
More informationConcepts of Project Management. All projects have followings.
Concepts of Project Management All projects have followings. An overall goal A project manager Individual tasks to be performed Timing for those tasks to be completed (such as three hours, three days,
More informationCMSC 435: Software Engineering Section Back to Software. Important: Team Work. More Resources
CMSC 435: Software Engineering Section 0101! Atif M. Memon (atif@cs.umd.edu)! 4115 A.V.Williams building! Phone: 301-405-3071! Office hours!.tu.th. (10:45am-12:00pm)! Don t wait, don t hesitate, do communicate!!!
More informationSoftware Modeling & Analysis. - Fundamentals of Software Engineering - Software Process Model. Lecturer: JUNBEOM YOO
Software Modeling & Analysis - Fundamentals of Software Engineering - Software Process Model Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr What is Software Engineering? [ IEEE Standard 610.12-1990 ] Software
More informationProfessor Hausi A. Müller PhD PEng FCAE Department of Computer Science Faculty of Engineering University of Victoria
Professor Hausi A. Müller PhD PEng FCAE Department of Computer Science Faculty of Engineering University of Victoria www.engr.uvic.ca/~seng321/ courses1.csc.uvic.ca/courses/201/spring/seng/321 SENG 321
More informationDarshan Institute of Engineering & Technology for Diploma Studies
RESPONSIBILITY OF SOFTWARE PROJECT MANAGER Job responsibility Software project managers take the overall responsibility of project to success. The job responsibility of a project manager ranges from invisible
More informationSDLC Models- A Survey
Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology IJCSMC, Vol. 2, Issue. 1, January 2013,
More informationSoftware Engineering. Page 1. Objectives. Steps in Project Planning. Software Project Planning. Scope. Estimating Resources
Objectives Software Engineering Project Planning James Gain (jgain@cs.uct.ac.za) http://people.cs.uct.ac.za/~jgain/courses/softeng/ 1. Introduce project planning 2. Examine the stages of project planning:
More informationA Comparative Study of Universally Accepted SDLC Models for Software Development
2018 IJSRST Volume 4 Issue 5 Print ISSN: 2395-6011 Online ISSN: 2395-602X Themed Section: Science and Technology A Comparative Study of Universally Accepted SDLC Models for Software Development ABSTRACT
More informationT Software Testing and Quality Assurance Test Planning
T-76.5613 Software Testing and Quality Assurance 10.10.2007 Test Planning Juha Itkonen Outline Test planning, purpose and usage of a test plan Topics of test planning Exercise References: IEEE Std 829-1998,
More informationSoftware Engineering
Software Engineering Project Management 1 Objectives To explain the main tasks undertaken by project managers To introduce software project management and to describe its distinctive characteristics To
More informationFigure 1 Function Point items and project category weightings
Software measurement There are two significant approaches to measurement that project managers need to be familiar with. These are Function Point Analysis (Albrecht, 1979) and COCOMO (Boehm, 1981). 1.
More informationPlanning and the Software Lifecycle. CSCE Lecture 2-08/26/2015
Planning and the Software Lifecycle CSCE 740 - Lecture 2-08/26/2015 Today s Goals Introduce software development processes Definitions - processes and process models Choosing a process AKA: planning and
More informationCMPT 275 Software Engineering
CMPT 275 Software Engineering Software life cycle 1 Software Life Cycle Sequence of processes completed as a software project moves from inception to retirement At beginning of project development, choose
More informationCS605 Software Engineering-II Solved Paper MID Term FALL 2008 MIDTERM EXAMINATION Fall 2008 CS605- Software Engineering II (Session - 2)
MIDTERM EXAMINATION Fall 2008 CS605- Software Engineering II (Session - 2) Question No: 1 ( Marks: 1 ) - Please choose one Every task should be assigned to a specific team -------------. Member Manager
More informationThis tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.
i About the Tutorial SDLC stands for Software Development Life Cycle. SDLC is a process that consists of a series of planned activities to develop or alter the Software Products. This tutorial will give
More informationCommunication Model for Cooperative Robotics Simulator. Project Plan. Version 1.0
Communication Model for Cooperative Robotics Simulator Project Plan Version 1.0 1 Introduction This document provides an overview of project plan for Communication Model for Cooperative Robotics Simulator
More informationSENG380:Software Process and Management. Software Size and Effort Estimation Part2
SENG380:Software Process and Management Software Size and Effort Estimation Part2 1 IFPUG File Type Complexity Table 1 External user type External input types External output types Low Average High 3 4
More informationProject management. ACSC 383 Software Engineering. Efthyvoulos C. Kyriacou (PhD) Assoc. Prof. Computer Science and Engineering Department
Project management ACSC 383 Software Engineering Efthyvoulos C. Kyriacou (PhD) Assoc. Prof. Computer Science and Engineering Department Resources : Ian Sommervile Software engineering, 7 th edition presentations
More informationA Comparison Between Evolutionary and Prototype Model
A Comparison Between Evolutionary and Prototype Model Aditi Thakur Department of Computer Science, Baddi University of Emerging Sciences and Technology ABSTRACT: In this paper, I have examined a number
More informationObject-Oriented Software Engineering Practical Software Development using UML and Java. Chapter 11: Managing the Software Process
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 11: Managing the Software Process 11.1 What is Project Management? Project management encompasses all the
More informationLecture 2: Software Quality Factors, Models and Standards. Software Quality Assurance (INSE 6260/4-UU) Winter 2016
Lecture 2: Software Quality Factors, Models and Standards Software Quality Assurance (INSE 6260/4-UU) Winter 2016 INSE 6260/4-UU Software Quality Assurance Software Quality Quality Assurance Factors and
More information2009 Spring. Software Modeling & Analysis. - Software Process Model. Lecturer: JUNBEOM YOO
2009 Spring Software Modeling & Analysis - Fundamentals of Software Engineering - Software Process Model Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr What is Software Engineering? IEEE Std 610.12-1990 [ IEEE
More information7. Project Management
Subject/Topic/Focus: 7. Project Management Management of Systems Engineering Processes Summary: Project management Systems engineering Maturity model and process improvement Literature: Ian Sommerville:
More informationResearch Article / Paper / Case Study Available online at: Analysis of Strengths and Weakness of SDLC Models Shikha Verma Delhi India
ISSN: 2321-7782 (Online) Volume 2, Issue 3, March 2014 International Journal of Advance Research in Computer Science and Management Studies Research Article / Paper / Case Study Available online at: www.ijarcsms.com
More informationSOFTWARE ENGINEERING
Page 1 MCA302 SOFTWARE ENGINEERING UNIT I - SOFTWARE PROCESS Introduction S/W Engineering Paradigm life cycle models (water fall, incremental, spiral, WINWIN spiral, evolutionary, prototyping, object oriented)
More informationSHRI ANGALAMMAN COLLEGE OF ENGINEERING & TECHNOLOGY (An ISO 9001:2008 Certified Institution) SIRUGANOOR,TRICHY
SHRI ANGALAMMAN COLLEGE OF ENGINEERING & TECHNOLOGY (An ISO 9001:2008 Certified Institution) SIRUGANOOR,TRICHY-621105. DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS1301- SOFTWARE ENGINEERING UNIT I
More informationA Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management
International Journal of Soft Computing and Engineering (IJSCE) A Study on Software Metrics and Phase based Defect Removal Pattern Technique for Project Management Jayanthi.R, M Lilly Florence Abstract:
More informationSOFTWARE ENGINEERING
SOFTWARE ENGINEERING Project planning Once a project is found to be feasible, software project managers undertake project planning. Project planning is undertaken and completed even before any development
More informationSolutions Manual. Object-Oriented Software Engineering. An Agile Unified Methodology. David Kung
2 David Kung Object-Oriented Software Engineering An Agile Unified Methodology Solutions Manual 3 Message to Instructors July 10, 2013 The solutions provided in this manual may not be complete, or 100%
More informationInformation Technology Project Management. Copyright 2012 John Wiley & Sons, Inc.
Information Technology Project Management 6-1 Copyright 2012 John Wiley & Sons, Inc. Estimating Techniques - Software Engineering Approaches Lines of Code (LOC) Function Points COCOMO Heuristics Software
More informationCMMI and FPA. the link and benefit of using FPA when rolling out CMMI. Christine Green IFPUG - Certified Function Point Specialist EDS
CMMI and FPA the link and benefit of using FPA when rolling out CMMI Christine Green IFPUG - Certified Function Point Specialist EDS and the EDS logo are registered trademarks of Electronic Data Systems
More informationProject Management Framework with reference to PMBOK (PMI) July 01, 2009
Project Management Framework with reference to PMBOK (PMI) July 01, 2009 Introduction Context Agenda Introduction to Methodologies What is a Methodology? Benefits of an Effective Methodology Methodology
More informationCS SOFTWARE ENGINEERING QUESTION BANK
CS6403 - SOFTWARE ENGINEERING QUESTION BANK UNIT I- SOFTWARE PRODUCT AND PROCESS Part - A (2 M ARKS) 1. What is the prime objective of software engineering? 2. Define software engineering paradigm. 3.
More informationManagement of Software Engineering. Ch. 8 1
Management of Software Engineering Ch. 8 1 Project control Ch. 8 2 Work Breakdown Structure WBS describes a break down of project goal into intermediate goals Each in turn broken down in a hierarchical
More informationCSE 435 Software Engineering. Sept 14, 2015
CSE 435 Software Engineering Sept 14, 2015 What is Software Engineering Where Does the Software Engineer Fit In? Computer science: focusing on computer hardware, compilers, operating systems, and programming
More informationAdvantages and Disadvantages of. Independent Tests. Advantages. Disadvantages
8.0 Test Management Outline 8.1 Test organisation 8.2 Test planning and estimation 8.3 Test program monitoring and control 8.4 Configuration management 8.5 Risk and testing 8.6 Summary Independent Testing
More informationProject management. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 5 Slide 1
Project management Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 5 Slide 1 Objectives To explain the main tasks undertaken by project managers To introduce software project management
More informationVolume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at
Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Study of Software Development Life Cycle Process Models
More informationBuilding Information Systems
Chapter 13 Building Information Systems 13.1 2010 by Prentice Hall LEARNING OBJECTIVES Demonstrate how building new systems produces organizational change. Identify and describe the core activities in
More informationTassc:Estimator technical briefing
Tassc:Estimator technical briefing Gillian Adens Tassc Limited www.tassc-solutions.com First Published: November 2002 Last Updated: April 2004 Tassc:Estimator arrives ready loaded with metric data to assist
More informationThis chapter illustrates the evolutionary differences between
CHAPTER 6 Contents An integrated approach Two representations CMMI process area contents Process area upgrades and additions Project management concepts process areas Project Monitoring and Control Engineering
More informationSE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?
SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics E-mail: Keti@ii.edu.mk What is Software Engineering? SE is the discipline concerned
More informationCOCOMO Models 26/12/2016 1
COCOMO Models 26/12/2016 1 Project Management and Mr. Murphy 1. Logic is a systematic method of coming to the wrong conclusion with confidence. 2. Technology is dominated by those who manage what they
More informationDRAFT. Effort = A * Size B * EM. (1) Effort in person-months A - calibrated constant B - scale factor EM - effort multiplier from cost factors
1.1. Cost Estimation Models Parametric cost models used in avionics, space, ground, and shipboard platforms by the services are generally based on the common effort formula shown in Equation 1. Size of
More informationChapter 5: Software effort estimation- part 2
Chapter 5: Software effort estimation- part 2 NET481: Project Management Afnan Albahli " Topics to be covered Difficulties of Estimation Where are estimates done? Problems of over- and under- estimate
More informationHU801B Project Management Lecture 7 - Project Planning
HU801B Project Management Lecture 7 - Project Planning Material extracted from Software Engineering 9 th Edition, Sommerville http://softwareengineering-9.com Agenda Project planning and the planning process
More informationSoftware Engineering & Architecture
Software Engineering & Architecture 10. SOFTWARE EVOLUTION Martin Kropp University of Applied Sciences Northwestern Switzerland Institute for Mobile and Distributed Systems References Based on the PowerPoint
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More information