NAME: (Please PRINT) CEN Software Engineering
|
|
|
- Easter Booker
- 10 years ago
- Views:
Transcription
1 NAME: (Please PRINT) CEN Software Engineering Quiz 1 -- Spring 2007 You have 50 minutes to work on this closed-book/closed-notes test. Please pay attention to point values since you may not have time to complete all 20 problems. PLEASE PRINT ALL ANSWERS IN THE SPACE PROVIDED ONLY. Print your name above NOW and sign the pledge at the end of the test WHEN YOU FINISH. 1. (2 pts.) Sommerville identifies three key challenges facing software engineering today: Heterogeneity, Delivery, and Trust. Briefly describe what he means by the delivery challenge. 2. (3 pts.) Sommerville notes that the Waterfall model s major problem is its inflexible partitioning of a project into distinct stages. What does he claim the models advantages are? 3. (4 pts.) Sommerville describes two problems that the evolutionary development approach has from an engineering and management perspective. What are they? 4. (6 pts.) Briefly describe the distinguishing characteristics of Boehm s spiral development model.
2 2 5. (6 pts.) Fred Brooks, author of The Mythical Man-Month, argues that adding people to a late software project can actually make it later. Graphically depict the general relationship one would expect to see between the number of PEOPLE working vs. calendar TIME for (a) perfectly partitionable tasks (i.e., tasks that can be partitioned with no additional cost or overhead), (b) tasks that are not partitionable, and (c) software development projects. a. perfectly partitionable b. not partitionable c. software development more more more T I M E T I M E T I M E less less less few PEOPLE many few PEOPLE many few PEOPLE many 6. a. (6 pts.) Develop an activity network for the following tasks, durations (in days), and dependencies: (Do NOT include milestones in your network.) Tasks Duration Dependencies T1 4 T2 1 T1 T3 2 T1 T4 7 T5 2 T2, T4 T6 4 T3, T4 (start) (finish) b. (3 pts.) What is the "critical path" for this network? c. (6 pts.) How many days can the following tasks be delayed without causing an overall project schedule slippage? T2: T3: T6:
3 3 7. (2 pts.) As discussed in class, one of the reasons why requirements engineering is so hard is the difficulty of anticipation. Explain what anticipation means in this context. 8. (3 pts.) One of the problems associated with eliciting domain requirements is what Sommerville calls implicitness. Briefly describe what he means by this. 9. (2 pts.) One of the potential problems described by Sommerville with using natural language to specify requirements is requirements amalgamation. Briefly describe what he means by this. 10. (4 pts.) What is ethnography? How does it differ from focused ethnography? What is the principal advantage of the latter over the former in requirements engineering? 11. (4 pts.) Why is documenting the origin/rationale of requirements potentially useful? Briefly illustrate your answer with an example. 12. (4 pts.) Sommerville notes that one of the problems with agile development methods (and other incremental development and delivery approaches) concerns contracts. Briefly explain why this can be a problem.
4 4 13. a. (3 pts.) One of the practices associated with Extreme Programming is known as refactoring. Briefly describe WHAT refactoring is, WHEN it is employed, and WHAT BENEFIT(S) accrue(s) from it. b. (3 pts.) Briefly compare the development philosophy underlying Extreme Programming as reflected by the practice of refactoring vs. traditional design based on the concept of information hiding. 14. a. (4 pts.) Sommerville describes two types of operations used in the Algebraic specification of abstract data types. What are they and how do they differ? b. (3 pts.) What is the rule of thumb discussed in class for defining a sufficient set of axioms? c. (3 pts.) The List specification given in class was comprised of the following axioms: Head(Create) = Undefined exception (empty list) Head(Cons(L,v)) = if L=Create then v else Head(L) Length(Create) = 0 Length(Cons(L,v)) = Length(L) + 1 Tail(Create) = Create Tail(Cons(L,v)) = if L=Create then Create else Cons(Tail(L),v) Do these axioms accurately reflect the rule of thumb discussed in class for defining a sufficient set of axioms? Briefly explain your answer.
5 5 15. Model-based specification via pre-and post-conditions utilizes predicates that (when considered together) reflect a program s intended functional behavior. a. (3 pts.) What do pre-conditions express in this context, and what does this represent to a designer/implementer of a program? b. (3 pts.) What do post-conditions express in this context, and what does this represent to a designer/implementer of a program? 16. a. (5 pts.) Give a suitable pre- and post condition for a program that searches a non-empty array LIST[1..N] for the value stored in KEY. If present, set FOUND to true and J to an index of LIST which corresponds to KEY. Otherwise, set FOUND to false. pre-condition: post-condition: b. (4 pts.) Give a suitable OPERATIONAL specification for this program. c. (3 pts.) Give a single-threaded SCENARIO reflecting nominal program behavior consistent with the program description. 17. (4 pts.) Briefly explain why it can be difficult to structure systems using the abstract machine system structuring model.
6 6 18. a. (3 pts.) Briefly describe the repository system structuring architectural model. b. (4 pts.) Describe 2 advantages and 2 disadvantages of this model. 19. Two models for distributing the layers of an application across a twotiered C/S architecture were discussed at length in class. a. (2 pts.) What is a two-tiered C/S architecture comprised of? b. (3 pts.) Briefly describe the C/S application layers model. c. (4 pts.) Briefly describe the two-tier thin and fat client architectures in terms of the C/S application layers model. 20. (6 pts.) Briefly describe the roles played by IDL skeletons and IDL stubs in CORBA objects. What happens when an object calls another service-providing object? On my honor, I have neither given nor received unauthorized aid on this exam. SIGNATURE
IT3205: Fundamentals of Software Engineering (Compulsory)
INTRODUCTION : Fundamentals of Software Engineering (Compulsory) This course is designed to provide the students with the basic competencies required to identify requirements, document the system design
Course Overview CEN 5035 Software Engineering
Course Overview CEN 5035 Software Engineering Stephen M. Thebaut, Ph.D. University of Florida Contact Info Instructor: Steve Thebaut, E314-A Office Hours: Wed/Fri 9:15-10:15 or by appt. e-mail: smt AT
IT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3
Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document
CS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.
CS 389 Software Engineering Lecture 2 Chapter 2 Software Processes Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed. Topics covered Software process models Process activities Coping
Project management. Organizing, planning and scheduling software projects
Project management Organizing, planning and scheduling software projects Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 3 Slide 1 Objectives To introduce software project management and
Organizing, planning and scheduling software projects
Project management Organizing, planning and scheduling software projects Ian Sommerville 1995 Modified by Spiros Mancoridis 1998 Software Engineering, 5th edition. Chapter 3 Slide 1 Objectives To introduce
Distributed Systems Architectures
Software Engineering Distributed Systems Architectures Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain the advantages and disadvantages of different distributed systems
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
Project management. Organizing, planning and scheduling software projects. Objectives. Chapter 3. Chapter 3 Project Management. Learning Objective
Chapter 3 Chapter 3 Project Management Learning Objective...to give an appreciation for and to introduce project management and to place it into context and give some of the fundamentals to project management
COSC 3351 Software Design. Recap for the first quiz. Edgar Gabriel. Spring 2008. For the 1 st Quiz
COSC 3351 Software Design Recap for the first quiz Spring 2008 For the 1 st Quiz Three large topic areas: UML syntax and diagrams Software architectural styles Object oriented design principles A couple
1) Testing of general knowledge 25%. Each right question counts 1. Each wrong counts 0.5. Empty
Exam 2 The exam consists of four parts: 1) Testing of general knowledge 25%. Each right question counts 1. Each wrong counts 0.5. Empty counts zero 2) Planning 25%. All sub-questions count equally. 3)
Process Methodology. Wegmans Deli Kiosk. for. Version 1.0. Prepared by DELI-cious Developers. Rochester Institute of Technology
Process Methodology for Wegmans Deli Kiosk Version 1.0 Prepared by DELI-cious Developers Rochester Institute of Technology September 15, 2013 1 Table of Contents 1. Process... 3 1.1 Choice... 3 1.2 Description...
System types. Distributed systems
System types 1 Personal systems that are designed to run on a personal computer or workstation Distributed systems where the system software runs on a loosely integrated group of cooperating processors
Project management. Objectives. Topics covered. Organizing, planning and scheduling software projects DISCUSSION
Project management 1 Objectives 2 Organizing, planning and scheduling software projects DISCUSSION Project Managers? To introduce software project management and to describe its distinctive characteristics
How To Understand Software Engineering
PESIT Bangalore South Campus Department of MCA SOFTWARE ENGINEERING 1. GENERAL INFORMATION Academic Year: JULY-NOV 2015 Semester(s):III Title Code Duration (hrs) SOFTWARE ENGINEERING 13MCA33 Lectures 52Hrs
Project management. Organising, planning and scheduling software projects. Ian Sommerville 2000 Software Engineering, 6th edition.
Project management Organising, planning and scheduling software projects Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 4 Slide 1 Objectives To introduce software project management and
2. Analysis, Design and Implementation
2. Analysis, Design and Implementation Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Programs to Application Systems Products Software Development:
SE464/CS446/ECE452 Software Life-Cycle and Process Models. Instructor: Krzysztof Czarnecki
SE464/CS446/ECE452 Software Life-Cycle and Process Models Instructor: Krzysztof Czarnecki 1 Some of these slides are based on: Lecture slides by Ian Summerville accompanying his classic textbook software
6 Contracts and Scenarios in the Software Development Process
6 Contracts and Scenarios in the Software Development Process Summary: Software development processes play an important role in the successful and timely delivery of software. There are different approaches
(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
Introduction to Software Engineering. 9. Project Management
Introduction to Software Engineering 9. Project Management Roadmap > Risk management > Scoping and estimation > Planning and scheduling > Dealing with delays > Staffing, directing, teamwork 2 Literature
CS 791Z Graduate Topics on Software Engineering
Department of Computer Science and Engineering College of Engineering, University of Nevada, Reno CS 791Z Graduate Topics on Software Engineering Set of questions for the midterm test of April 27 th, 2015
Module 17. Client-Server Software Development. Version 2 CSE IIT, Kharagpur
Module 17 Client-Server Software Development Lesson 42 CORBA and COM/DCOM Specific Instructional Objectives At the end of this lesson the student would be able to: Explain what Common Object Request Broker
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,
CS 487. Week 8. Reference: 1. Software engineering, roger s. pressman. Reading: 1. Ian Sommerville, Chapter 3. Objective:
CS 487 Week 8 Reading: 1. Ian Sommerville, Chapter 3. Objective: 1. To check the understandibility of the students in life cycle and process model for development of a software product. 2. To check if
Software Engineering
1 Software Engineering Lecture 2: Software Life Cycles Stefan Hallerstede Århus School of Engineering 25 August 2011 2 Contents Naive Software Development Code & Fix Towards A Software Process Software
CS4507 Advanced Software Engineering
CS4507 Advanced Software Engineering Lectures 2 & 3: Software Development Lifecycle Models A O Riordan, 2015 Some diagrams from Sommerville, some notes from Maciaszek/Liong Lifecycle Model Software development
SWX: The Software Extension to the PMBOK Guide for Project Management
SWX: The Software Extension to the PMBOK Guide for Project Management prepared and presented by Richard E. (Dick) Fairley, PhD, CSDP Software and Systems Engineering Associates (S2EA) SWX Software Extension
Rapid Development & Software Project Survival Guide Steve McConnell Dave Root (Developed with Mel Rosso-Llopart)
Lifecycle Planning Rapid Development & Software Project Survival Guide Steve McConnell Dave Root (Developed with Mel Rosso-Llopart) Version 1.4 David Root, 2005, all rights reserved 1 Topics Who am I to
software studio software development processes Daniel Jackson
software studio software development processes Daniel Jackson 1 One of the planning documents for software research revealed --in a parenthetical remark only-- an unchallenged tacit assumption by referring
Project management. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 1
Project management Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 5 Slide 1 Objectives To explain the main tasks undertaken by project managers To introduce software project management
I219 Software Design Methodology
I219 Software Design Methodology JAIST Master s Program Fall 2014 Nguyen Van Vu [email protected] Topics Course Introduction Objectives and Scope Evaluation Policies Content and Schedule Basic Concepts
Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
General Problem Solving Model. Software Development Methodology. Chapter 2A
General Problem Solving Model Software Development Methodology These focus on understanding what the problem is about Chapter 2A Concerned with understanding more about the nature of the problem and possible
A Comparison between Five Models of Software Engineering
International Journal of Research in Information Technology (IJRIT) www.ijrit.com ISSN 2001-5569 A Comparison between Five Models of Software Engineering Surbhi Gupta, Vikrant Dewan CSE, Dronacharya College
Post-Class Quiz: Software Development Security Domain
1. A step-by-step implementation instruction is called A. Policy B. Standard C. Procedure D. Guideline 2. An approved configuration of software packages that describes how and what components are assembled
WHY THE WATERFALL MODEL DOESN T WORK
Chapter 2 WHY THE WATERFALL MODEL DOESN T WORK M oving an enterprise to agile methods is a serious undertaking because most assumptions about method, organization, best practices, and even company culture
Software Life Cycle Models
Software Life Cycle Models Waterfall model Prototyping models Rapid prototyping Incremental prototyping Evolutionary prototyping Spiral model 1 Waterfall Model Like liquid flows down stair steps... the
Software development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali
Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 [email protected] Spring 2014 (elicitation)
Software Engineering. Project Management. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering Project Management Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain the main tasks undertaken by project managers To introduce software project
UML TUTORIALS THE USE CASE MODEL
UML TUTORIALS THE USE CASE MODEL www.sparxsystems.com.au Sparx Systems 2004 Page 1/5 describes the proposed functionality of the new system. A Use Case represents a discrete unit of interaction between
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
Scheduling. Anne Banks Pidduck Adapted from John Musser
Scheduling Anne Banks Pidduck Adapted from John Musser 1 Today Network Fundamentals Gantt Charts PERT/CPM Techniques 2 WBS Types: Process, product, hybrid Formats: Outline or graphical organization chart
Software Engineering I (02161)
Software Engineering I (02161) Week 8 Assoc. Prof. Hubert Baumeister DTU Compute Technical University of Denmark Spring 2015 Last Week State machines Layered Architecture: GUI Layered Architecture: Persistency
Life Cycle Models. V. Paúl Pauca. CSC 331-631 Fall 2013. Department of Computer Science Wake Forest University. Object Oriented Software Engineering
Life Cycle Models V. Paúl Pauca Department of Computer Science Wake Forest University CSC 331-631 Fall 2013 Software Life Cycle The overall framework in which software is conceived, developed, and maintained.
The software process. Generic software process models. Waterfall model. Software Development Methods. Bayu Adhi Tama, ST., MTI. [email protected].
The software process Software Development Methods Bayu Adhi Tama, ST., MTI. [email protected] A structured set of activities required to develop a software system Specification; Design; Validation; Evolution.
Introduction to Software Engineering (ESE : Einführung in SE)
Introduction to Software Engineering (ESE : Einführung in SE) Prof. O. Nierstrasz Selected material courtesy of Prof. Serge Demeyer, U. Antwerp ESE Introduction Lecturers Assistants Lectures Exercises
Chapter 4 Software Lifecycle and Performance Analysis
Chapter 4 Software Lifecycle and Performance Analysis This chapter is aimed at illustrating performance modeling and analysis issues within the software lifecycle. After having introduced software and
Mastering Microsoft Project 2013
Course 55054: Mastering Microsoft Project 2013 Page 1 of 9 Mastering Microsoft Project 2013 Course 55054: 2 days; Instructor-Led Introduction This two-day, instructor-led course is intended for individuals
Lehrstuhl für Informatik 4 Kommunikation und verteilte Systeme. Middleware. Chapter 8: Middleware
Middleware 1 Middleware Lehrstuhl für Informatik 4 Middleware: Realisation of distributed accesses by suitable software infrastructure Hiding the complexity of the distributed system from the programmer
Mastering Microsoft Project 2013 Course: 55054A Course Length: 3 Days
3 Riverchase Office Plaza Hoover, Alabama 35244 Phone: 205.989.4944 Fax: 855.317.2187 E-Mail: [email protected] Web: www.discoveritt.com Mastering Microsoft Project 2013 Course: 55054A Course Length:
4. Software Project Management
4. Software Subject/Topic/Focus: Management of Systems Engineering Projects Summary: Influences on projects and potential risks Software systems engineering and project management Activity network and
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
Models of Software Development
October 28, 2015 Verification & Validation In many computer science courses, software is submitted once, graded, and thrown away. In real life, software development is an process. Some attempts to codify
ASSESSMENT OF SOFTWARE PROCESS MODELS
ASSESSMENT OF SOFTWARE PROCESS MODELS Akhilesh Research Scholar, Department of Computer Science, Manav Bharti University, Solan (H.P.) ABSTRACT The field of software engineering is related to the development
Chapter 3 Managing the Information Systems (IS) Project
Content Chapter 3 Managing the Information Systems (IS) Project Process of managing IS projects Skills required to be an effective project manager Skills and activities of a project manager during project
COMP 354 Introduction to Software Engineering
COMP 354 Introduction to Software Engineering Greg Butler Office: EV 3.219 Computer Science and Software Engineering Concordia University, Montreal, Canada Email: [email protected] Winter 2015 Course
How To Manage 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
1. Software Process Models (Sommerville Chapters 4, 17, 19, 12.4)
1. Software Process Models (Sommerville Chapters 4, 17, 19, 12.4) A software process model is a standardised format for planning organising, and running a development project. 1 Hundreds of different models
Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering
Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Overview Phases during Software Development
Development models. 1 Introduction. 2 Analyzing development models. R. Kuiper and E.J. Luit
Development models R. Kuiper and E.J. Luit 1 Introduction We reconsider the classical development models: the Waterfall Model [Bo76], the V-Model [Ro86], the Spiral Model [Bo88], together with the further
Software Processes. The software process. Generic software process models. Waterfall model. Waterfall model phases
Software Processes CSC 221 Introduction to Software Engineering software processes extract from Sommerville s chapter 3 slides Alan Dix Coherent sets of activities for specifying, designing, implementing
CS 121 Midterm Exam Fall 12 CLOSED BOOK THE RULES - PLEASE READ CAREFULLY
CS 121 Midterm Exam Fall 12 CLOSED BOOK THE RULES - PLEASE READ CAREFULLY Due Saturday, 13 Oct, 9 PM. Take this test in a SINGLE 1.5 hour setting. This test is: CLOSED Book - NO textbook, NO notes, etc.
Requirements Analysis (RA): An Analytical Approach for Selecting a Software Process Models ABSTRACT
Evolving Ideas Computing, Communication and Networking Publish by Global Vision Publishing House Edited by Jeetendra Pande Nihar Ranjan Pande Deep Chandra Joshi Requirements Analysis (RA): An Analytical
Umbrella: A New Component-Based Software Development Model
2009 International Conference on Computer Engineering and Applications IPCSIT vol.2 (2011) (2011) IACSIT Press, Singapore Umbrella: A New Component-Based Software Development Model Anurag Dixit and P.C.
6. Software Lifecycle Models. A software lifecycle model is a standardised format for planning organising, and running a new development project.
6. Software Lifecycle Models A software lifecycle model is a standardised format for planning organising, and running a new development project. Hundreds of different kinds of models are known and used.
CHAPTERS A NEW KNOT MODEL FOR COMPONENT BASED SOFTWARE DEVELOPMENT
CHAPTERS A NEW KNOT MODEL FOR COMPONENT BASED SOFTWARE DEVELOPMENT CONTENTS 5.1 Introduction 5.2 Component based software life cycle process model 5.2.1 Rapid Application Development Model 5.2.2 The Y
Software Development Process and Activities. CS 490MT/5555, Fall 2015, Yongjie Zheng
Software Development Process and Activities CS 490MT/5555, Fall 2015, Yongjie Zheng Software Process } A set of activities that leads to the production of a software product } What product we should work
IV. Software Lifecycles
IV. Software Lifecycles Software processes and lifecycles Relative costs of lifecycle phases Examples of lifecycles and processes Process maturity scale Information system development lifecycle Lifecycle
27 Formal Specification
1 Chapter 27 Formal Specification 27 Formal Specification Objectives The objective of this chapter is to introduce formal specification techniques that can be used to add detail to a system requirements
Chakra Vs Spiral Model - A Practical Approach
Chakra - A new era in Software Lifecycle modeling technique R.P.Muthu Assistant Professor, Department of Computer Science Indian Institute of Technology, Bombay. Abstract: Every old thing has to be modified
Development Techniques. CSE301 University of Sunderland Harry R. Erwin, PhD
Development Techniques CSE301 University of Sunderland Harry R. Erwin, PhD Sources Boehm, 1981, Software Engineering Economics, Prentice- Hall. Stephens and Rosenberg, 2003, Extreme Programming Refactored:
A Comparison Between Five Models Of Software Engineering
94 A Comparison Between Five Models Of Software Engineering Nabil Mohammed Ali Munassar 1 and A. Govardhan 2 1 Ph.D Student of Computer Science & Engineering Jawahrlal Nehru Technological University Kuktapally,
Software Development Life Cycle Models - Process Models. Week 2, Session 1
Software Development Life Cycle Models - Process Models Week 2, Session 1 PROCESS MODELS Many life cycle models have been proposed } Traditional Models (plan-driven) } Classical waterfall model } Iterative
Software Process Models. Xin Feng
Software Process Models Xin Feng Questions to Answer in Software Engineering? Questions to answer in software engineering What is the problem to be solved? Definition What are the characteristics of the
Lifecycle Models: Waterfall / Spiral / EVO
Lifecycle Models: Waterfall / Spiral / EVO Dror Feitelson Basic Seminar on Software Engineering Hebrew University 2011 Lifecycle The sequence of actions that must be performed in order to build a software
How To Understand The Software Process
Ingegneria del Software Corso di Laurea in Informatica per il Management Software process model Davide Rossi Dipartimento di Informatica Università di Bologna The task of the software development team
Software Engineering. What is a system?
What is a system? Software Engineering Software Processes A purposeful collection of inter-related components working together to achieve some common objective. A system may include software, mechanical,
Chapter 2 Software Processes
Chapter 2 Software Processes Chapter 2 Software Processes Slide 1 Topics covered Software processes and process models Generic models: Waterfall Incremental development Reuse-oriented software engineering
A Meeting Room Scheduling Problem
A Scheduling Problem Objective Engineering, Inc. 699 Windsong Trail Austin, Texas 78746 512-328-9658 FAX: 512-328-9661 [email protected] http://www.oeng.com Objective Engineering, Inc., 1999-2007. Photocopying,
Software Process. Process: A sequence of activities, subject to constraints on resources, that produce an intended output of some kind.
Software Process Process: A sequence of activities, subject to constraints on resources, that produce an intended output of some kind. Any process has these characteristics: The process prescribes all
Rapid software development. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1
Rapid software development Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 17 Slide 1 Objectives To explain how an iterative, incremental development process leads to faster delivery of
BCN 4612 Estimating II - Semester Course Outline Course Syllabus
BCN 4612 Estimating II - Semester Course Outline Course Syllabus Prerequisites: BCN 3611, Senior Standing 3 Credits COURSE DESCRIPTION: Analysis of determination of the cost of construction operations
An Assessment between Software Development Life Cycle Models of Software Engineering
International Journal of Electronics and Computer Science Engineering 700 Available Online at www.ijecse.org ISSN- 2277-1956 An Assessment between Software Development Life Cycle Models of Software Engineering
Software Life Cycle. Main issues: Discussion of different life cycle models Maintenance or evolution
Software Life Cycle Main issues: Discussion of different life cycle models Maintenance or evolution Not this life cycle SE, Software Lifecycle, Hans van Vliet, 2008 2 Introduction software development
Process Models and Metrics
Process Models and Metrics PROCESS MODELS AND METRICS These models and metrics capture information about the processes being performed We can model and measure the definition of the process process performers
SWEBOK Certification Program. Software Engineering Management
SWEBOK Certification Program Software Engineering Management Copyright Statement Copyright 2011. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted
3F6 - Software Engineering and Design. Handout 15 Software Management I With Markup. Steve Young
3F6 - Software Engineering and Design Handout 15 Software Management I With Markup Steve Young Contents 1. Software Engineering 2. Software Life Cycle 3. Team Organisation 4. Product Development 5. Specification
TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW
Year 2014, Vol. 1, issue 1, pp. 49-56 Available online at: http://journal.iecuniversity.com TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW Singh RANDEEP a*, Rathee AMIT b a* Department of
A Rapid Development Process with UML
A Rapid Development Process with UML Giuliano Armano DIEE, Dipartimento di Ingegneria Elettrica ed Elettronica, University of Cagliari Piazza d Armi I-09123, Cagliari (Italy) Tel. +39-70-675.5878 [email protected]
Organising, planning and scheduling software projects. Software management distinctions
Project management Organising, planning and scheduling software projects Software management distinctions The product is intangible The product is uniquely flexible Software engineering is not recognized
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
Unit 1 Learning Objectives
Fundamentals: Software Engineering Dr. Rami Bahsoon School of Computer Science The University Of Birmingham [email protected] www.cs.bham.ac.uk/~rzb Office 112 Y9- Computer Science Unit 1. Introduction
Software Project Models
INTERNATIONAL JOURNAL OF TECHNOLOGY ENHANCEMENTS AND EMERGING ENGINEERING RESEARCH, VOL 1, ISSUE 4 135 Software Project Models Abhimanyu Chopra, Abhinav Prashar, Chandresh Saini [email protected],
