Software Engineering Graduate Project Effort Analysis Report
|
|
- Gwenda Elliott
- 8 years ago
- Views:
Transcription
1 Software Engineering Graduate Project Effort Analysis Report Zhihao Chen Center for Software Engineering, University of Southern California, Los Angeles California, USA Abstract: In the graduate courses CSCI577ab, graduate students apply software engineering methodologies, processes, procures, and models to manage software development. This report analyzes their activities and effort distribution from fall 2001 to spring It would be very helpful for students to appropriately arrange their time, manage their schedule and plan their projects. It would also very helpful for software engineering research. Keywords: Software Engineering, effort, software development 1 Introduction There are two software engineering graduate courses (CSCI577a and CSCI577b) in our center for software engineering for us to perform the software engineering education. In the courses, graduate students apply software engineering methodologies, processes, procures, and models to manage software development. In each semester, there are more than 20 real graduate projects with all kinds of the software engineering activities. They study software engineering knowledge, learn the processes, and plan and control their projects. With the study of their activities and effort distribution from fall 2001 to spring 2004, we try to understand the trends in e-services projects and their effort implications, and identify sources of effort reduction/increase. We also try to provide the guidelines for future software project activities. 2 Assessing Effort Data In our graduate projects, people use the Model-Based (System) Architecting and Software Engineering (MBASE) approach for software development. MBASE provides more detailed definitions of the anchor point milestone elements, and a process guide for deriving them. It has intermediate milestones to serve as commitment points and progress checkpoints with the set of anchor point milestones: Inception Readiness Review (IRR), Life Cycle Objectives (LCO), Life Cycle Architecture (LCA), Initial Operational Capability (IOC), and Product Release Review (PRR). Basically, we collect all effort data for all activities during the software development lifecycle in LCO, LCA, IOC and PRR. There are project effort data in different project life-cycle phases inception phase, elaboration phase, construction phase, transition phase and support phase; there are project effort data of win-win negotiation, project requirements, project system design, project implementation, project management; there are project effort data of product model, process model, property model, success model. Table 1 Project activities 1
2 In each year, there are more than 20 projects in our center. People use MBASE/RUP software process to develop the software systems. The effort of 31 development activities shown in table 1 in the projects has been collected and classified into five catalogues management, environment and configuration management, requirements, design, implementation, assessment, deployment, and other effort. Figure 1 The activity effort distribution of the median in the selected projects We select 29 continue small projects (4 to 6 persons) from fall 2001 to spring 2004 in the total 70 projects. Median effort of projects for each week is calculated. With our analysis, we found that most of the effort above the median. We use median because the effort for some projects at that week has extreme high values, and the median can be a better measure of centralness than the mean or average The figure 1 clearly shows MBASE/RUP software processes in practices in small projects. The activity effort increases close to the major milestones, in which projects were reviewed, re-planed, re-estimated, and re-controlled. The vary criteria by phase help people to make decisions. In the inception phase (LCO), the most active activities are A1 - Life Cycle Planning, A3 - Client Interaction, A4 - Team Interaction, B1 - Training and Preparation, C1 - WinWin Negotiations, C3/4 - Modeling & documenting for Operational Concept Description, C5/6 - Modeling & Documenting for System and Software Requirements Definition, and F2 - Feasibility Rationale Description. The stakeholders are working on the project scope definition, cost/schedule estimation, define / negotiate / understand /prioritize requirements, identify risks, and demonstrate architectural prototype. In the elaboration phase (LCA), the most active activities are A1 - Life Cycle Planning, A3 - Client Interaction, A4 - Team Interaction, C5/6 - Modeling & Documenting for System and Software Requirements Definition, D1/2 - Modeling & Documenting for System and Software Architecture Description and F4 - Inspection and Peer Reviews. At the end of this phase, stability of the product vision and architecture, resolution of major risk elements, adequate planning and reasonable estimates for project completion, stakeholder acceptance of the product vision and project plan, and acceptable expenditure level have been done. In the construction phase (IOC), the most active activities are A3 - Client Interaction, A4 - Team Interaction, E2 - Critical Component Implementation, F3 - Test Planning, F4 - Inspection and Peer Reviews, and other activities not-covered-here. In the transition phase, the most active activities are A4 - Team Interaction, E2 - Critical Component Implementation, G1 - Transition and Support Planning, and other activities not-covered-here. It is ready to release the products if the clients satisfy it. The clients may start the initiation of another development cycle to improve or enhance the product. 2
3 Figure 2 The high-level project effort distribution Shown in Figure 1/2, there is a series of iterations within each phase. The effort of the related activities is changing in each iteration. Each iteration marks a minor milestone. Project results are assessed and project plan is revised as necessary in each iteration. It illustrates how phases and iterations, or the time dimension, relates to the development activities performed, or the workflow dimension. The relative effort indicates how much of the activity is performed in each phase/iteration. Each iteration involves activities from all workflows. The relative amount of work related to the workflows changes between iterations. From another hand, we also see that, for the small projects, there are too many overheads between the team communications. The activity of team interaction are always most active. This is true in here because most of the graduate students are new to the software engineering (this is why they take the course), the team members are first time to meet each other, a lot of technologies / processes need to be studied, and team leader management skills need to be improved. In the small projects, the management effort of Life Cycle Planning, Control and Monitoring, Client Interaction and Team Interaction is still major. If we improve the management level, it will save a lot of effort. Figure 3 Major project artifact effort distributions In MBASE/RUP software process, OCD (Operational Concept Description) is to describe how a proposed new system1 will operate within its environment. For the operational stakeholders (including users, operators, administrators, maintainers, owners, general public), it enables them to understand and refine the proposed new system. It also enables them to evolve knowledgeably from their current operational concept to the new one. For the development stakeholders, it enables them to better understand and make development decisions consistent with the operational objectives and constraints. SSRD (System and Software Requirements Definition) is to describe capability requirements (both nominal and off-nominal): i.e., the fundamental services provided by the system, describe Level of Service Requirements (sometimes referred to as Non-functional requirements): i.e., the behavioral properties that the specified functions must have, such as performance, usability, etc. Level of Service Requirements should be assigned a unit of measurement, describe global constraints: requirements and constraints that apply to the system as a whole. SSAD (System and Software Architecture Description) is to document the results 3
4 of analyzing the organizational concept of operation for the system, designing an architecture, and designing an implementation. The SSAD serves as a bridge between the Operational Concept defined during the Inception phase and the Construction phase. The SSAD is started during the Inception phase, refined during the Elaboration phase, and completed during the Construction phase. FRD (Feasibility Rationale Description) is to ensure that the system developers have not just created a number of system definition elements, but have also demonstrated the feasibility and consistency of these elements. LCP (Life Cycle Plan) is to serve as a basis for monitoring and controlling the project's progress, to provide general information during Inception and Elaboration about those project management areas which, to serve as the basis for controlling the project's progress in achieving the software product objectives, to help make the best use of people and resources throughout the life cycle, to provide evidence that the developers have thought through the major life cycle issues in advance, and to to answer the most common questions about a project or activity: why, what, when, who, where, how, how much, and whereas. From the figure 3, OCD, SSAD and SSRD are most active in the inception phase; SSAD, LCP, SSRD are most active in the elaboration phase. During the development, LCP is always active to monitor and control the project, and ensure the project archiving the goals. 3 Conclusions With the above analysis results, people can avoid the same mistakes, solve the recurring issues, manage the software project better, and apply the similar models in different projects. It would be very helpful for students to appropriately arrange their time, manage their schedule and plan their projects. It would also very helpful for software engineering research. References 1. Barry Boehm, A Spiral Model of Software Development and Enhancement Computer, May 1988, pp Barry Boehm, Software Risk Management, IEEE Computer Society Press, Barry Boehm, Unifying Software Engineering and Systems Engineering, IEEE Computer, March 2000, pp Barry Boehm et al., Developing Multimedia Applications with the WinWin Spiral Model, Proceedings, ESEC/FSE 97, Springer Verlag, Barry Boehm et al., Using the Win Win Spiral Model: A Case Study, IEEE Computer, July 1998, pp Barry Boehm, M. Abi-Antoun, A.W. Brown, N. Mehta, and D. Port. Guidelines for the LCO and LCA Deliverables for MBASE, USC-CSE, March 2000, 7. Barry Boehm et al., Theory W Software Project Management: Principles and Examples, IEEE Trans. Software Engr., July Barry Boehm et al., A Collaborative Spiral Software Process Model Based on Theory W, Proceedings, ICSP 3, IEEE, Reston, Va. October Barry Boehm, Dan Port, Escaping the Software Tar Pit: Model Clashes and How to Avoid Them, ACM Software Engineering Notes, January, 1999, pp Barry Boehm, Dan Port, When Models Collide: Lessons from Software Systems Analysis, IEEE IT Professional, January/February 1999, pp Appending Effort Analysis for All Activities 4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Impact and Contributions of MBASE on Software Engineering Graduate Courses
Impact and Contributions of MBASE on Software Engineering Graduate Courses Ricardo Valerdi Massachusetts Institute of Technology rvalerdi@mit.edu Ray Madachy University of Southern California madachy@usc.edu
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 20-21 The Unified Process Dynamic dimension Two dimensions Content
More informationSupporting Workflow Overview. CSC532 Fall06
Supporting Workflow Overview CSC532 Fall06 Objectives: Supporting Workflows Define the supporting workflows Understand how to apply the supporting workflows Understand the activities necessary to configure
More informationValue-Based Feedback in Software/IT Systems
Value-Based Feedback in Software/IT Systems Barry Boehm, USC FEAST/ProSim/SOCE 2000 Keynote July 12, 2000 boehm@sunset.usc.edu http://sunset.usc.edu Outline COCOMO II 4-Cycle feedback model Value-based
More informationThe ROI of Systems Engineering: Some Quantitative Results
The ROI of Systems Engineering: Some Quantitative Results Barry Boehm Center for Systems and Software Engineering University of Southern California boehm@usc.edu Ricardo Valerdi Lean Aerospace Initiative,
More informationImproving the Life-Cycle Process in Software Engineering Education. Barry Boehm and Alexander Egyed 1 )
Improving the Life-Cycle Process in Software Engineering Education Barry Boehm and Alexander Egyed 1 ) Published in the Proceedings of the European Software Day (as part of the 24th Euromicro conference),
More informationHow To Use The Win-Win Spiral Model For A Project
Innovations in Teaching And Learning in Information and Computer Sciences The e-journal of the LTSN-ICS Towards Understanding Software Requirements Capture: Experiences of Professional Students using the
More informationINTERACT INTEGRATE IMPACT
INTERACT INTEGRATE IMPACT Proceedings of the 20th Annual Conference of the Australasian Society for Computers in Learning in Tertiary Education (ASCILITE) Adelaide, Australia 7 10 December 2003 Editors
More informationUSC's Two Semester Software Engineering Graduate Project Course
USC's Two Semester Software Engineering Graduate Project Course A. Winsor Brown Computer Science and USC Center for Systems and Software Engineering, University of Southern California Los Angeles, CA 90089-0781,
More informationScaling Down Large Projects to Meet the Agile Sweet Spot
Scaling Down Large Projects to Meet the Agile Sweet Spot Philippe Kruchten Kruchten Engineering Services Ltd Presenter Philippe Kruchten, Ph. D., P. Eng. KESL 2906 West 37 th avenue Vancouver BC V5Z 2M9
More informationBalancing Plan-Driven and Agile Methods in Software Engineering Project Courses
Computer Science Education 0899-3408/02/1203-187$16.00 2002, Vol. 12, No. 3, pp. 187±195 # Swets & Zeitlinger Balancing Plan-Driven and Agile Methods in Software Engineering Project Courses Barry Boehm,
More informationHow 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
More informationLifecycle 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
More informationSE464/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
More informationRUP for Software Development Projects
RUP for Software Development Projects George Merguerian www.bmc-online.com 1 Specialists in Global Project Management Brussels Frankfurt Houston Istanbul Milan Ottawa Shanghai Singapore Warsaw Washington
More informationCS4507 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
More informationSoftware Process Engineering & Management Models
Software Process Engineering & Management Models Paul Grünbacher Institute for Systems Engineering & Automation Johannes Kepler University Linz Christian Doppler Laboratory for Automated Software Engineering
More informationCombining Models for Business Decisions and Software Development
Combining Models for Business Decisions and Software Development 1 Christina Wallin, 2 Stig Larsson, 3 Fredrik Ekdahl, 1 Ivica Crnkovic 1 Mälardalen University, Department of Computer Engineering, Västerås,
More informationClassical Software Life Cycle Models
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
More informationA Look at Software Engineering Risks in a Team Project Course
A Look at Software Engineering Risks in a Team Project Course Supannika Koolmanojwong and Barry Boehm Center for Systems and Software Engineering (CSSE) University of Southern California (USC) Los Angeles,
More informationCOMP 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: gregb@cs.concordia.ca Winter 2015 Course
More informationCS 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
More informationThe Schedule as Independent Variable (SAIV) Process for Acquisition Software-Intensive Systems
The Schedule as Independent Variable (SAIV) Process for Acquisition Software-Intensive Systems Barry Boehm, Winsor Brown, LiGuo Huang University of Southern California Center for Software Engineering Los
More informationChap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
More informationEffort Distribution in Model-Based Development
Effort Distribution in Model-Based Development Werner Heijstek 1 and Michel R. V. Chaudron 1,2 1 Leiden Institute of Advanced Computer Science, Leiden University Niels Bohrweg 1, 2333 CA Leiden, The Netherlands
More informationManaging Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI
Managing Small Software Projects - An Integrated Guide Based on PMBOK, RUP, and CMMI César Cid Contreras M.Sc. Prof. Dr. Henrik Janzen Published at the South Westphalia University of Applied Sciences,
More informationIn this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development Chapter 5C About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities
More informationPlanning a Project with the Rational Unified Process Author: David West
Planning a Project with the Rational Unified Process Author: David West Rational Software White paper TP 151, 08/02 Table of Contents INTRODUCTION... 1 ABOUT THE PROJECT PLAN... 1 CHARACTERISTICS OF A
More informationAt the 1996 and 1997 International Conferences
Computing Practices Using the WinWin Spiral Model: A Case Study Fifteen teams used the WinWin spiral model to prototype, plan, specify, and build multimedia applications for USC s Integrated Library System.
More informationTime Monitoring Tool Software Development Plan. Version <1.1>
Time Monitoring Tool Software Development Plan Version Revision History Date Version Description Author 10/01/01 1.0 First Draft Sabrina Laflamme 12/01/01 1.1 Completion of Document John Lemon Page
More information1. Definitions and Context
WinWin Spiral Approach to Developing COTS-Based Applications EDSER-5 Position Paper Barry Boehm, Dan Port, Ye Yang University of Southern California, Texas A&M University* {boehm, dport, yey}@cse.usc.edu
More informationWhat 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 informationRecent Results in Software Process Modeling
Recent Results in Software Process Modeling Ray Madachy, Ph.D. C-bridge Internet Solutions University of Southern California Center for Software Engineering rmadachy@c-bridge.com, madachy@usc.edu 1 Introduction
More informationA Rational Development Process
Paper published in: Crosstalk, 9 (7) July 1996, pp.11-16. A Rational Development Process Philippe Kruchten Vancouver, BC pbk@rational.com 1. Introduction This paper gives a high level description of the
More informationSelecting a Software Development Methodology based on. Organizational Characteristics. Adrienne Farrell
ATHABASCA UNIVERSITY Selecting a Software Development Methodology based on Organizational Characteristics BY Adrienne Farrell An essay submitted in partial fulfillment Of the requirements for the degree
More informationRedesigned Framework and Approach for IT Project Management
Vol. 5 No. 3, July, 2011 Redesigned Framework and Approach for IT Project Management Champa Hewagamage 1, K. P. Hewagamage 2 1 Department of Information Technology, Faculty of Management Studies and Commerce,
More informationSoftware Engineering and the Systems Approach: A Conversation with Barry Boehm
IGI PUBLISHING ITJ4305 701 E. Chocolate Avenue, Suite 200, Hershey PA 17033-1240, USA Int l Journal of Tel: Information 717/533-8845; Technologies Fax 717/533-8661; and the Systems URL-http://www.igi-global.com
More informationSoftware 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
More informationProcess 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...
More informationCMM vs. CMMI: From Conventional to Modern Software Management
CMM vs. CMMI: From Conventional to Modern Software Management by Walker Royce Vice President and General Manager Strategic Services Rational Software Corporation This article summarizes some thoughts on
More informationBasic 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 informationProject Management in the Rational Unified Process
CS2 Software Engineering note 3 Project Management in the Rational Unified Process In the last two Software Engineering lectures we have considered the outline description of the Rational Unified Process
More informationThe Role of the Software Architect
IBM Software Group The Role of the Software Architect Peter Eeles peter.eeles@uk.ibm.com 2004 IBM Corporation Agenda Architecture Architect Architecting Requirements Analysis and design Implementation
More informationCSE 435 Software Engineering. Sept 16, 2015
CSE 435 Software Engineering Sept 16, 2015 2.1 The Meaning of Process A process: a series of steps involving activities, constraints, and resources that produce an intended output of some kind A process
More informationSRM UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY
SRM UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY SCHOOL OF COMPUTING DEPARTMENT OF SWE COURSE PLAN Course Code : CS0351 Course Title : SOFTWARE PROJECT MANAGEMENT Semester : VII Course Time : July
More informationA 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
More informationEducating Software Engineers to Become Systems Engineers
Educating Software Engineers to Become Systems Engineers Supannika Koolmanojwong and Barry Boehm Center for Systems and Software Engineering (CSSE) University of Southern California (USC) Los Angeles,
More informationSoftware Lifecycles Models
Software Lifecycles Models Software Engineering Lecture 17 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline of Today s Lecture Modeling the software life cycle Sequential
More informationKeywords Software Engineering, Software cost, Universal models. Agile model, feature of software projects.
Volume 4, Issue 6, June 2014 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Comparative Analysis
More informationProgram 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 informationLecture Slides for Managing and Leading Software Projects. Chapter 1: Introduction
Lecture Slides for Managing and Leading Software Projects Chapter 1: Introduction developed by Richard E. (Dick) Fairley, Ph.D. to accompany the text Managing and Leading Software Projects published by
More informationChapter 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
More informationAgile & PMI Project Management Mapping MAVERIC S POINT OF VIEW. 10-10-2012 Vol. 7
10-10-2012 Vol. 7 MAVERIC S POINT OF VIEW Agile & Abstract: The purpose of this whitepaper is to explore the points of parity and differences between two of the most widely used methodologies. PMI Management
More informationLeveraging RUP, OpenUP, and the PMBOK. Arthur English, GreenLine Systems
Software Project Management Leveraging RUP, OpenUP, and the PMBOK Arthur English, GreenLine Systems GreenLine Systems Inc. 2003 2013 My Background 30+ years of IT project management experience with both
More informationCHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS)
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS) Prescriptive Process Model Defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high quality
More informationDevelopment 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
More informationIterative Project Management 1
Iterative Project Management Module 2 Objectives Understand issues for Project Managers (PM) who use iterative development by: Learning how the PM monitors and steers an iterative project towards success.
More informationEnterprise Architecture Process, Structure and Organization
Organizational development Enterprise Process, Structure and Organization t-eam* - a framework derived from project experience Dipl.-Inform. Klaus D. Niemann Managing Director...act! consulting GmbH Glockengießerwall
More informationA Process Model for Software Architecture
272 A Process Model for Software A. Rama Mohan Reddy Associate Professor Dr. P Govindarajulu Professor Dr. M M Naidu Professor Department of Computer Science and Engineering Sri Venkateswara University
More informationUsing EVMS with COTS-Based Systems
Using EVMS with COTS-Based Systems Mary Jo Staley Patricia Oberndorf Carol A. Sledge June 2002 TECHNICAL REPORT CMU/SEI-2002-TR-022 ESC-TR-2002-022 Pittsburgh, PA 15213-3890 Using EVMS with COTS-Based
More informationOracle Unified Method (OUM)
Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions O R A C L E W H I T E P A P E R J A N U A R Y 2 0 1 5 Table of Contents Executive Overview 1 Introduction
More informationDEVELOPMENT AND EVALUATION OF VALUE-BASED REVIEW (VBR) METHODS. Keun Lee
DEVELOPMENT AND EVALUATION OF VALUE-BASED REVIEW (VBR) METHODS by Keun Lee --------------------------------------------------------------------------------------------------- A Dissertation Presented to
More informationSWEBOK 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
More informationUsing a Hybrid Method for Formalizing Informal Stakeholder Requirements Inputs
Using a Hybrid Method for Formalizing Informal Stakeholder Requirements Inputs Hasan Kitapci, Barry W. Boehm University of Southern California Center for Software Engineering 90089 Los Angeles, CA {hkitapci,
More information3C05: Unified Software Development Process
3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2
More informationPMP Examination Tasks Puzzle game
PMP Examination Tasks Puzzle game Here is a great game to play to test your knowledge of the tasks you will be tested on in the actual examination. What we have done is take each of the domain tasks in
More information(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 informationSoftware Configuration Management Plan
For Database Applications Document ID: Version: 2.0c Planning Installation & Acceptance Integration & Test Requirements Definition Design Development 1 / 22 Copyright 2000-2005 Digital Publications LLC.
More informationCrosswalk Between Current and New PMP Task Classifications
Crosswalk Between Current and New PMP Task Classifications Domain 01 Initiating the Project Conduct project selection methods (e.g., cost benefit analysis, selection criteria) through meetings with the
More informationPractice Overview. REQUIREMENTS DEFINITION Issue Date: <mm/dd/yyyy> Revision Date: <mm/dd/yyyy>
DEPARTMENT OF HEALTH AND HUMAN SERVICES ENTERPRISE PERFORMANCE LIFE CYCLE FRAMEWORK PRACTIICES GUIIDE REQUIREMENTS DEFINITION Issue Date: Revision Date: Document
More informationSoftware Quality Development and Assurance in RUP, MSF and XP - A Comparative Study
Software Quality Development and Assurance in RUP, MSF and XP - A Comparative Study Wolfgang Zuser Vienna University of Technology wolfgang.zuser@inso.tuwien.ac.at Stefan Heil Capgemini Consulting Austria
More informationSOFTWARE DEVELOPMENT PLAN
SOFTWARE DEVELOPMENT PLAN This document outline is based on the IEEE Standard 1058.1-1987 for Software Project Management Plans. This is the controlling document for managing a software project, and it
More informationSoftware 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 informationThe Unified Software Development Process
The Unified Software Development Process Technieche Universal Darmstadt FACHBEREICH IN-FORMAHK BLIOTHEK Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation tnventar-nsr.: Sachgebiete:
More informationValue-Based Processes for COTS-Based Applications
focus cots integration Value-Based Processes for -Based Applications Ye Yang, Jesal Bhuta, and Barry Boehm, University of Southern California Daniel N. Port, University of Hawaii -based applications pose
More informationCOMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES
COMMONWEALTH OF MASSACHUSETTS EXECUTIVE OFFICE OF HEALTH AND HUMAN SERVICES The Office of Information Technology Project Methodology and Lifecycle Guide Version 4.4 Last Updated: November 15, 2011 CE M
More informationReaching CMM Levels 2 and 3 with the Rational Unified Process
Reaching CMM Levels 2 and 3 with the Rational Unified Process Rational Software White Paper TP174 Table of Contents INTRODUCTION... 1 LEVEL-2, REPEATABLE... 3 Requirements Management... 3 Software Project
More informationElite: A New Component-Based Software Development Model
Elite: A New Component-Based Software Development Model Lata Nautiyal Umesh Kumar Tiwari Sushil Chandra Dimri Shivani Bahuguna Assistant Professor- Assistant Professor- Professor- Assistant Professor-
More informationSoftware Process and Models
Agenda Software Process Models Plan-driven Process Models Software Process and Models A software process model simplified, abstracted description of a software development process. A model is good for
More informationSOFTWARE PROCESS MODELS
SOFTWARE PROCESS MODELS Slide 1 Software Process Models Process model (Life-cycle model) - steps through which the product progresses Requirements phase Specification phase Design phase Implementation
More informationThe most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
More informationCS 6361, SPRING 2010 Advanced Requirements Engineering Web Based Meeting Scheduler- Project Plan
1 W E B B A S E D M E E T I N G S C H E D U L E R S Y S T E M Project Plan Version 4.0 CS 6361 ADVANCED REQUIREMENTS ENGINEERING, SPRING 2010 UNIVERSITY OF TEXAS AT DALLAS R E Q U I R E M E N T S E N G
More informationTowards Collaborative Requirements Engineering Tool for ERP product customization
Towards Collaborative Requirements Engineering Tool for ERP product customization Boban Celebic, Ruth Breu, Michael Felderer, Florian Häser Institute of Computer Science, University of Innsbruck 6020 Innsbruck,
More informationProject 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 informationAn 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
More informationSoftware Development: The Waterfall Model
Steven Zeil June 7, 2013 Contents 1 Software Development Process Models 2 1.1 Components of the Waterfall Model................................. 2 1.1.1 What is a requirement?. 2 1.1.2 Testing..........
More informationThe Evolving State of ESPM
Foreword Introduction Part One The Evolving State of ESPM xxxi xxxiii 1 Chapter 1 The Changing Landscape of Software Development What Is a Software Development Project? Examples of Two Software Development
More informationHow To Develop A Multi Agent System (Mma)
S-Tropos: An Iterative SPEM-Centric Software Project Management Process Yves Wautelet, Manuel Kolp, Youssef Achbany IAG Institut d Administration et de Gestion, ISYS Unité de Systèmes d Information, Université
More informationJOURNAL OF OBJECT TECHNOLOGY
JOURNAL OF OBJECT TECHNOLOGY Online at www.jot.fm. Published by ETH Zurich, Chair of Software Engineering JOT, 2006 Vol. 5. No. 8, November-December 2006 Requirements Engineering Tasks Donald Firesmith,
More informationPlan-Driven Methodologies
Plan-Driven Methodologies The traditional way to develop software Based on system engineering and quality disciplines (process improvement) Standards developed from DoD & industry to make process fit a
More informationProject Knowledge Areas
From Houston S: The Project Manager s Guide to Health Information Technology Implementation. Chicago: HIMSS; 2011; pp 27 39. This book is available on the HIMSS online bookstore at www. himss.org/store.
More informationMoving from a Plan Driven Culture to Agile Development
Moving from a Plan Driven Culture to Agile Development Lessons Learned ICSE 2005, St. Louis, 20-May-2005 Michael Hirsch Zühlke Engineering AG hm@zuehlke.com Topic of this Talk In scope: Experiences and
More information<name of project> Software Project Management Plan
The document in this file is adapted from the IEEE standards for Software Project Management Plans, 1058-1998, which conforms to the requirements of ISO standard 12207 Software Life Cycle Processes. Tailor
More informationSoftware Project Management using an Iterative Lifecycle Model
Software Corporation Software Project Management using an Iterative Lifecycle Model 1 Objectives of this Presentation To understand what the Unified Process is To understand the iterative lifecycle approach
More informationRequirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK
IBM Software Group Requirement Management with the Rational Unified Process RUP practices to support Business Analyst s activities and links with BABoK Jean-Louis Maréchaux Software IT Specialist IBM Rational
More informationRose/Architect: a tool to visualize architecture
Published in the Proceedings of the 32 nd Annual Hawaii International Conference on Systems Sciences (HICSS 99) Rose/Architect: a tool to visualize architecture Alexander Egyed University of Southern California
More informationHow To Model Software Development Life Cycle Models
Various Software Development Life Cycle Models Sahil Jindal, Puneet Gulati, Praveen Rohilla Dronacharya College of Engineering, India Abstract:An SDLC model is a conceptual framework describing different
More informationMKS Integrity & CMMI. July, 2007
& CMMI July, 2007 Why the drive for CMMI? Missed commitments Spiralling costs Late delivery to the market Last minute crunches Inadequate management visibility Too many surprises Quality problems Customer
More informationChapter 3 The Integrated Requirements Management Framework (IREQM)
Chapter 3 The Integrated Management Framework (IREQM) During the software requirements development process, customer and development team meet together for many times to obtain customer and product requirements
More information