Object-Oriented & Classical Soft Engineering
|
|
- Helen Caldwell
- 6 years ago
- Views:
Transcription
1 Object-Oriented & Classical Soft Engineering Seventh Edition Stephen R. Schach Vanderbilt University Higher Education Boston Burr Ridge, IL Dubuque, IA New York San Francisco St. Louis Bangkok Bogota Caracas Kuala Lumpur Lisbon London Madrid Mexico City Milan Montreal New Delhi Santiago Seoul Singapore Sydney Taipei Toronto
2 Contents Preface v PART ONE INTRODUCTION TO SOFTWARE ENGINEERING 1 Chapter 1 The Scope of Software Engineering 3 Learning Objectives Historical Aspects Economic Aspects Maintenance Aspects Classical and Modern Views of Maintenance The Importance of Postdelivery Maintenance Requirements, Analysis, and Design Aspects Team Development Aspects Why There 1s No Planning Phase Why There Is No Testing Phase Why There Is No Documentation Phase The Object-Oriented Paradigm The Object-Oriented Paradigm in Perspective Terminology Ethical Issues 27 Chapter Review 28 For Further Reading 28 Key Terms 29 Problems 30 References 31 Chapter 2 Software Life-Cycle Models 35 Learning Objectives Software Development in Theory Winburg Mini Case Study Lessons of the Winburg Mini Case Study Teal Tractors Mini Case Study Iteration and Incrementation Winburg Mini Case Study Revisited Risks and Other Aspects of Iteration and Incrementation Managing Iteration and Incrementation Other Life-Cycle Models Code-and-Fix Life-Cycle Model Waterfall Life-Cycle Model Rapid-Prototyping Life-Cycle Model Open-Source Life-Cycle Model Agile Processes Synchronize-and-Stabilize Life-Cycle Model Spiral Life-Cycle Model Comparison of Life-Cycle Models 64 Chapter Review 65 For Further Reading 66 Key Terms 67 Problems 67 References 68 Chapter 3 The Software Process 71 Learning Objectives The Unified Process Iteration and Incrementation within the Object-Oriented Paradigm The Requirements Workflow The Analysis Workflow The Design Workflow The Implementation Workflow The Test Workflow Requirements Artifacts Analysis Artifacts Design Artifacts Implementation Artifacts 82 xiii
3 xiv Contents 3.8 Postdelivery Maintenance Retirement The Phases of the Unified Process The Inception Phase The Elaboration Phase The Construction Phase The Transition Phase One- versus Two-Dimensional Life-Cycle Models Improving the Software Process Capability Maturity Models Other Software Process Improvement Initiatives Costs and Benefits of Software Process Improvement 96 Chapter Review 98 For Further Reading 98 Key Terms 99 Problems 100 References 100 Chapter 4 Teams 104 Learning Objectives Team Organization Democratic Team Approach Analysis ofthe Democratic Team Approach Classical Chief Programmer Team Approach The New York Times Project lmpracticality ofthe Classical Chief Programmer Team Approach Beyond Chief Programmer and Democratic Teams Synchronize-and-Stabilize Teams Teams for Agile Processes Open-Source Programming Teams People Capability Maturity Model Choosing an Appropriate Team Organization 117 Chapter Review 118 For Further Reading 118 Key Terms 118 Problems 119 References 119 Chapter 5 The Tools of the Trade 121 Learning Objectives Stepwise Refinement Stepwise Refinement Mini Case Study Cost-Benefit Analysis Software Metrics CASE TaxonomyofCASE ScopeofCASE Software Versions Revisions Variations Configuration Control Configuration Control during Postdelivery Maintenance Baselines Configuration Control during Development Build Tools Productivity Gains with CASE Technology 142 Chapter Review 144 For Further Reading 144 Key Terms 144 Problems 145 References 146 Chapter 6 Testing 149 Learning Objectives Quality Issues Software Quality Assurance Managerial Independence Non-Execution-Based Testing Walkthroughs Managing Walkthroughs Inspections 154
4 Contents xv Comparison of Inspections and Walkthroughs Strengths and Weaknesses of Reviews Metrics fbr Inspections Execution-Based Testing What Should Be Tested? Utility Reliability Robustness Performance Correctness Testing versus Correctness Proofs Example of a Correctness Proof Correctness Proof Mini Case Study Correctness Proofs and Software Engineering Who Should Perform Execution-Based Testing? When Testing Stops 171 Chapter Review 171 For Further Reading 172 Key Terms 172 Problems 173 References 174 Chapter 7 From Modules to Objects 177 Learning Objectives What Is a Module? Cohesion Coincidental Cohesion Logical Cohesion Temporal Cohesion Procedural Cohesion Communicational Cohesion Functional Cohesion Informational Cohesion Cohesion Example Coupling Content Coupling Common Coupling Control Coupling Stamp Coupling Data Coupling Coupling Example The Importance of Coupling Data Encapsulation Data Encapsulation and Development Data Encapsulation and Maintenance Abstract Data Types Information Hiding Objects Inheritance, Polymorphism, and Dynamic Binding The Object-Oriented Paradigm 212 Chapter Review 214 For Further Reading 215 Key Terms 215 Problems 216 References 217 Chapter 8 Reusability and Portability 219 Learning Objectives Reuse Concepts Impediments to Reuse Reuse Case Studies Raytheon Missile Systems Division European Space Agency Objects and Reuse Reuse during Design and Implementation Design Reuse Applikation Frameworks Design Patterns Software Architecture Component-Based Software Engineering Reuse and Postdelivery Maintenance Portability Hardware Incompatibilities Operating System Incompatibilities Numerical Software Incompatibilities Compiler Incompatibilities 237
5 xvi Contents 8.8 Why Portability? Techniques for Achieving Portability Portable System Software Portable Application Software Portable Data 243 Chapter Review 244 For Further Reading 245 Key Terms 246 Problems 246, References 247, Chapter 9 Planning and Estimating 252 Learning Objectives Planning and the Software Process Estimating Duration and Cost Metricsfor the Size ofa Product Techniques of Cost Estimation Intermediate COCOMO COCOMO II Tracking Duration and Cost Estimates Components of a Software Project Management Plan Software Project Management Plan Framework IEEE Software Project Management Plan Planning Testing Planning Object-Oriented Projects Training Requirements Documentation Standards CASE Tools for Planning and Estimating Testing the Software Project Management Plan 276 Chapter Review 276 For Further Reading 277 Key Terms 277 Problems 278 References 279 PART TWO THE WORKFLOWS OF THE SOFTWARE LIFE CYCLE 283 Chapter 10 Requirements 285 Learning Objectives Determining What the Client Needs Overview of the Requirements Workflow Understanding the Domain The Business Model Interviewing Other Techniques Use Cases Initial Requirements Initial Understanding of the Domain: The MSG Foundation Case Study Initial Business Model: The MSG Foundation Case Study Initial Requirements: The MSG Foundation Case Study Continuing the Requirements Workflow: The MSG Foundation Case Study Revising the Requirements: The MSG Foundation Case Study The Test Workflow: The MSG Foundation Case Study The Classical Requirements Phase Rapid Prototyping Human Factors Reusing the Rapid Prototype CASE Tools for the Requirements Workflow Metrics for the Requirements Workflow Challenges of the Requirements Workflow 325 Chapter Review 327 For Further Reading 327 Key Terms 327 Case Study Key Terms 328 Problems 328 References 329
6 Contents xvii Chapter 11 Classical Analysis 331 Learning Objectives The Specification Document Informal Specifications Correctness ProofMini Case Study Redux Structured Systems Analysi s Salfy 's Software Shop Mini Case Study 335 1T.4 Structured Systems Analysis: The MSG Foundation Case Study Other Semiformal Techniques Entity-Relationship Modeling Finite State Machines Finite State Machines: The Elevator Problem Case Study PetriNets Petri Nets: The Elevator Problem Case Study Z Z: The Elevator Problem Case Study Analysis ofz Other Formal Techniques Comparison of Classical Analysis Techniques Testing during Classical Analysis CASE Tools for Classical Analysis Metrics for Classical Analysis Software Project Management Plan: The MSG Foundation Case Study Challenges of Classical Analysis 367 Chapter Review 367 For Further Reading 368 Key Terms 368 Case Study Key Terms 369 Problems 369 References 371 Chapter12 Object-Oriented Analysis 375 Learning Objectives The Analysis Workflow Extracting the Entity Classes Object-Oriented Analysis: The Elevator Problem Case Study Functional Modeling: The Elevator Problem Case Study Entity Class Modeling: The Elevator Problem Case Study Noun Extraction CRC Cards Dynamic Modeling: The Elevator Problem Case Study The Test Workflow: Object-Oriented Analysis Extracting the Boundary and Control Classes The Initial Functional Model: The MSG Foundation Case Study The Initial Class Diagram: The MSG Foundation Case Study The Initial Dynamic Model: The MSG Foundation Case Study Revising the Entity Classes: The MSG Foundation Case Study Extracting the Boundary Classes: The MSG Foundation Case Study Extracting the Control Classes: The MSG Foundation Case Study Use-Case Realization: The MSG Foundation Case Study Estimate Funds Available for Week Use Case Manage an Asset Use Case Update Estimated Annual Operating Expenses Use Case Produce a Report Use Case Incrementing the Class Diagram: The MSG Foundation Case Study The Test Workflow: The MSG Foundation Case Study The Specification Document in the Unified Process More on Actors and Use Cases CASE Tools for the Object-Oriented Analysis Workflow 425
7 xviii Contents Challenges of the Object-Oriented Analysis Workflow 425 Chapter Review 426 For Further Reading 427 Key Terms 427 Problems 428 References 429 Chapter 13 Design 431, Learning Objectives Design and Abstraction Operation-Oriented Design Data Flow Analysis Mini Case Study: Word Counting Data Flow Analysis Extensions Transaction Analysis Data-Oriented Design Object-Oriented Design Object-Oriented Design: The Elevator Problem Case Study Object-Oriented Design: The MSG Foundation Case Study The Design Workflow The Test Workflow: Design The Test Workflow: The MSG Foundation Case Study Formal Techniques for Detailed Design Real-Time Design Techniques CASE Tools for Design Metrics for Design Challenges of the Design Workflow 457 Chapter Review 458 For Further Reading 458 Key Terms 459 Problems 459 References 460 Chapter 14 Implementation 463 Learning Objectives Choice of Programming Language Fourth-Generation Languages Good Programming Practice Use of Consistent and Meaningful Variable Names The Issue of Self-Documenting Code Use of Parameters Code Layout for Increased Readability Nested if Statements Coding Standards Code Reuse Integration Top-down Integration Bottom-up Integration Sandwich Integration Integration of Object-Oriented Products Management of Integration The Implementation Workflow The Implementation Workflow: The MSG Foundation Case Study The Test Workflow: Implementation Test Case Selection Testing to Specifications versus Testing to Code Feasibility of Testing to Specifications Feasibility of Testing to Code Black-Box Unit-Testing Techniques Equivalence Testing and Boundary Value Analysis Functional Testing Black-Box Test Cases: The MSG Foundation Case Study Glass-Box Unit-Testing Techniques Structural Testing: Statement, Branch, and Path Coverage Complexity Metrics Code Walkthroughs and Inspections Comparison of Unit-Testing Techniques Cleanroom Potential Problems When Testing Objects Management Aspects of Unit Testing 498
8 Contents xix When to Rewrite Rather than Debug a Code Artifact Integration Testing Product Testing Acceptance Testing The Test Workflow: The MSG Foundation Case Study CASE Tools for Implementation CASE Tools for the Complete Software Process Integrated Development Environments Environments for Business Applications Public Tool Infrastructures Potential Problems with Environments CASE Tools for the Test Workflow Metrics for the Implementation Workflow Challenges of the Implementation Workflow 507 Chapter Review 507 For Further Reading 508 Key Terms 509 Problems 509 References 511 Chapter15 Postdelivery Maintenance 515 Learning Obj ectives Development and Maintenance Why Postdelivery Maintenance IsNecessary What Is Required of Postdelivery Maintenance Programmers? Postdelivery Maintenance Mini Case Study Management of Postdelivery Maintenance Defect Reports Authorizing Changes to the Product Ensuring Maintainability Problem of Repeated Maintenance Maintenance of Obj ect-oriented Software Postdelivery Maintenance Skills versus Development Skills Reverse Engineering Testing during Postdelivery Maintenance CASE Tools for Postdelivery Maintenance Metrics for Postdelivery Maintenance Postdelivery Maintenance: The MSG Foundation Case Study Challenges of Postdelivery Maintenance 530 Chapter Review 531 For Further Reading 531 Key Terms 532 Problems 532 References 533 Chapter 16 More on UML 535 Learning Objectives UML Is Not a Methodology Class Diagrams Aggregation Multiplicity Composition Generalization Association Notes Use-Case Diagrams Stereotypes Interaction Diagrams Statecharts Activity Diagrams Packages Component Diagrams Deployment Diagrams Review of UML Diagrams UML and Iteration 5 51 Chapter Review 551
9 XX Contents For Further Reading 552 Key Terms 552 Problems 552 References 553 Bibliography 554 Appendix A Term Project: Osric's Office Appliances and Decor 579 Appendix B Software Engineering Resources 583 Appendix C * Requirements Workflow: The MSG Foundation Case Study 585 Appendix D Structured Systems Analysis: The MSG Foundation Case Study 586 Appendix E Analysis Workflow: The MSG Foundation Case Study 589 Appendix F Software Project Management Plan: The MSG Foundation Case Study 590 Appendix G Design Workflow: The MSG Foundation Case Study 595 Appendix H Implementation Workflow: The MSG Foundation Case Study (C++ Version) 600 Appendix I Implementation Workflow: The MSG Foundation Case Study (Java Version) 601 Appendix J Test Workflow: The MSG Foundation Case Study 602 Author Index 603 Subject Index 606
SOFTWARE ENGINEERING WITH JAVA
SOFTWARE ENGINEERING WITH JAVA Stephen R. Schach Vanderbilt University Irwin McGraw-Hill Boston, Massachusetts Burr Ridge, Illinois Dubuque, Iowa Madison, Wisconsin New York, New York San Francisco, California
More informationPEARSON. Addison Wesley
PEARSON Addison Wesley Boston San Francisco N e w York London Toronto Sydney Tokyo Singapore Madrid Mexico City Munich Paris Cape Town Hong Kong Montreal :. - - } r / : '... : '. : : I Preface i Overview
More informationLIFE-CYCLE MODELS AND PROCESS. Software Engineering 1/9/2008. CHAPTER 1, 2, and 3. Stephen R. Schach
Slide 2.1 CHAPTER 1, 2, and 3 Slide 2.2 Object-Oriented Oriented Software Engineering WCB/McGraw-Hill, 2008 Stephen R. Schach srs@vuse.vanderbilt.edu SOFTWARE LIFE-CYCLE MODELS AND PROCESS Overview Slide
More informationPEARSON. Amsterdam Cape Town Dubai London Madrid Milan Munich Paris Montreal Toronto
PEARSON Boston Columbus Indianapolis New York San Francisco Hoboken Amsterdam Cape Town Dubai London Madrid Milan Munich Paris Montreal Toronto Delhi Mexico City Sao Paulo Sydney Hong Kong Seoul Singapore
More informationObject-Oriented and Classical Software Engineering
Slide 3.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 3 Slide 3.2 THE SOFTWARE PROCESS Overview Slide 3.3
More informationProject Management Process,Technology, and Practice
Project Management Process,Technology, and Practice Indiana University PEARSON Boston Columbus Indianapolis New York San Francisco Upper Saddle River Amsterdam Cape Town Dubai London Madrid Milan Munich
More informationObject-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
More informationPrinciples Of Services Marketing Palmer 6th Edition
We have made it easy for you to find a PDF Ebooks without any digging. And by having access to our ebooks online or by storing it on your computer, you have convenient answers with principles of services
More informationThe Unified Software Development Process
The Unified Software Development Process Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation TT ADDISON-WESLEY An Imprint of Addison Wesiey Longman, Inc. Reading, Massachusetts Harlow,
More informationCONTENTS. Introduction to Software Engineering. Software Process and Life Cycle Models. Software Life-Cycle Model-2. Chapter 1. Chapter 2.
Contents (v) CONTENTS Preface About the Author (xv) (xvii) Chapter 1 Introduction to Software Engineering 1.1 Introduction 1 1.2 Basics of Software Engineering 2 1.3 Principles of Software Engineering
More informationSE310 Analysis and Design of Software
SE310 Analysis and Design of Software Lecture 7 REVIEW SM&D Chapters 1 to 11 & Notes February 13, 2018 Sam Siewert Domain Models Use Case Details UML is Universal Modeling Language [OMG, UML.org] Use to
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving
More informationSoftware Quality Engineering Courses Offered by The Westfall Team
Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering
More informationSoftware Engineering in the Agile World. Table of contents
Table of contents Chapter 1 14 Software Engineering 14 1.1 Introduction 14 1.2 No standard software engineering methodology 14 1.3 Waterfall methodology 15 1.3.1 Software development under Waterfall model
More informationThe Art of Agile Practice
The Art of Agile Practice A Composite Approach for Projects and Organizations Bhuvan Unhelkar Lap) CRC Press VV^ ^^-""^ J Taylor & Francis Group Boca Raton London New York CRC Press is an imprint of the
More informationA Practical Approach. Development. to Large-Scale Agile. FutureSmart Firmware. How HP Transformed LaserJet. AAddison-Wesley. Mike Young.
A Practical Approach to Large-Scale Agile Development How HP Transformed LaserJet FutureSmart Firmware Gary Gruver Mike Young Pat Fulghum AAddison-Wesley Upper Saddle River, NJ Boston Indianapolis San
More information7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
More informationSYLLABUS. What is Agility, What is an Agile Process, Agile Process Models.
Contents i SYLLABUS UNIT - I CHAPTER - 1 : INTRODUCTION TO Introduction to Software Engineering. CHAPTER - 2 : A GENERIC VIEW OF PROCESS Software Engineering, Process Framework, CMMI, Process Patterns,
More informationDevelopment Process Bennett, McRobb and Farmer 1
Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using UML 4 th Edition, McGraw Hill, 2010 1 In This Lecture You Will Learn: About the Unified
More informationSOA Principles of Service Design
SOA Principles of Service Design Thomas Erl 0 0 PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO PRENTICE HALL NEW YORK «TORONTO MONTREAL LONDON MUNICH PARIS MADRID CAPETOWN SYDNEY
More informationReuse Concepts. Portable. Reuse. Easily modifying a product as a whole to run under another compiler, OS, or hardware architecture
Reusability, Portability, and Interoperability If reinventing the wheel were a criminal offense, many software professionals would be languishing in jail [Schach 2001] 1 Reuse Concepts Portable Easily
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 informationGaining and Sustaining Competitive Advantage
Fourth Edition Gaining and Sustaining Competitive Advantage Jay B. Barney The Ohio State University Boston Columbus Indianapolis New York San Francisco Upper Saddle River Amsterdam Cape Town Dubai London
More informationSoftware Engineering QUESTION BANK
Software Engineering QUESTION BANK UNIT - 1 1. What is software? Explain the two fundamental types of software products. 2. What is software engineering? What is the difference between software engineering
More informationTest Workflow. Michael Fourman Cs2 Software Engineering
Test Workflow Michael Fourman Introduction Verify the result from implementation by testing each build Plan the tests in each iteration Integration tests for every build within the iteration System tests
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 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 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 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 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 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 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 informationDevelopment Process and Analysis. LTOOD/OOAD - Verified Software Systems 1
Development Process and Analysis LTOOD/OOAD - Verified Software Systems 1 Software Crisis Declared in the late 60 s Expressed by delays and failures of major software projects (unreached goals, unpredictable
More informationSoftware Engineering
Software Engineering Lecture 02: Processes Peter Thiemann University of Freiburg, Germany SS 2013 Peter Thiemann (Univ. Freiburg) Software Engineering SWT 1 / 41 Terms Software Component SW System Organized
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 informationANAlysis an<j. DEsiqN. BiOREACTORS. Education Private Limited TAPOBRATA PANDA. Professor of Biochemical Engineering, NEW DELHI. McGraw-Hill Offices
BiOREACTORS ANAlysis an
More informationIn this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities in the development
More informationSOA Design Patterns. Thomas Erl. (with additional contributors) PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO
SOA Design Patterns Thomas Erl (with additional contributors) E PRENTICE HALL UPPER SADDLE RIVER, NJ BOSTON INDIANAPOLIS SAN FRANCISCO NEW YORK TORONTO MONTREAL LONDON MUNICH PARIS MADRID CAPETOWN SYDNEY
More informationAUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT
AUTOMATED DEFECT PREVENTION: BEST PRACTICES IN SOFTWARE MANAGEMENT Preface. Features and Organization. Practice Descriptions. Intended audience. Acknowledgements. Permissions. Disclaimer. 1. The Case for
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 informationSoftwaretechnik. Lecture 02: Processes. Peter Thiemann SS University of Freiburg, Germany
Softwaretechnik Lecture 02: Processes Peter Thiemann University of Freiburg, Germany SS 2012 Peter Thiemann (Univ. Freiburg) Softwaretechnik SWT 1 / 34 Terms Software Program SW System organized collections
More informationHANDBOOK OF DIE DESIGN
HANDBOOK OF DIE DESIGN Ivana Suchy Consultant, Design Engineer Fair Lawn, New Jersey Second Edition McGRAW-HILL New York Chicago San Francisco Lisbon London Madrid Mexico City Milan New Delhi San Juan
More informationHUMAN RESOURCE MANAGEMENT DEREK TORRINGTON, LAURA HALL, CAROL ATKINSON, STEPHEN TAYLOR TENTH EDITION. v v :? % '"v f ' ; ' f. !3fc * .
HUMAN RESOURCE MANAGEMENT DEREK TORRINGTON, LAURA HALL, CAROL ATKINSON, STEPHEN TAYLOR TENTH EDITION v v :? % '"v f ' ; ' f.!3fc * #' ( «. * * " r'" T> Pearson Marlow, England London New York Boston San
More informationPrerequisites It is recommended that the participants have a working knowledge of traditional Business Analysis tasks and techniques.
BA31 - Unified Modeling Language (UML) for Business Analysts This course will provide Business Analysts with new capabilities to improve their skills with using visual modeling techniques to document requirements.
More informationCM M Is for Services. AAddison-Wesley. Guidelines for Superior Service. Sandy Shrum. Second Edition. Eileen C. Forrester Brandon L Buteau
CM M Is for Services Guidelines for Superior Service Second Edition Eileen C. Forrester Brandon L Buteau Sandy Shrum AAddison-Wesley Upper Saddle River, NJ Boston Indianapolis San Francisco New York Toronto
More informationSystems Analysis for Business Analysts (3 Day)
www.peaklearningllc.com Systems Analysis for Business Analysts (3 Day) This is a basic course to help business analysts understand the basics of systems analysis. This course is ideal for people who are
More informationKINGS COLLEGE OF ENGINEERING DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING SYLLABUS
KINGS COLLEGE OF ENGINEERING DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING SYLLABUS Sub.Code : CS1021 Branch / Year / Sem : B.E CSE/IV/VIII Sub.Name : Software Project Management Batch : 2009-2013 Staff
More informationEric Shiu, Joseph Hair, Robert Bush and David Ortinau
, r^: j- o Eric Shiu, Joseph Hair, Robert Bush and David Ortinau Me Graw Hill McGraw-Hill Higher Education London Boston Burr Ridge, IL Dubuque, IA Madison, Wl New York San Francisco St. Louis Bangkok
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 informationMICRO- ECONOMICS AND BEHAVIOR Seventh Edition
MICRO- ECONOMICS AND BEHAVIOR Seventh Edition ROBERT H. FRANK Cornell University McGraw-Hill Irwin Boston Burr Ridge, IL Dubuque, IA New York San Francisco St. Louis Bangkok Bogota Caracas Kuala Lumpur
More informationSecurity Risk Management
Security Risk Management Building an Information Security Risk Management Program from the Ground Up Evan Wheeler Technical Editor Kenneth Swick ELSEVIER AMSTERDAM BOSTON HEIDELBERG LONDON NEW YORK OXFORD
More informationRational Unified Process
Rational Unified Process Software development Life Cycle The life of a software system can be represented as a series of cycle. A cycle ends with the release of a version of the system to the customers.
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 informationSE300 Software Engineering Practices
SE300 Software Engineering Practices Lecture 14 REVIEW April 14, 2015 Sam Siewert Domain Models Use Case Details Complete a Design Provide Code Re-Use Candidates and PoC Start Here! https://www.modelio.org/
More informationmethodologies (SOFTWARE ENGINEERING) CONTENTS 1.1 INTRODUCTION TO O SOFTWARE ENGINEERING Basic Stages in Software Development... 1.
Contents i software development methodologies FOR m.tech (jntu - hyderabad) i year i semester (SOFTWARE ENGINEERING) CONTENTS UNIT - I [CH. H. - 1] ] [INTRODUCTION TO SOFTWARE ENGINEERING]... 1.1-1.18
More informationSoftware Modeling & Analysis
Software Modeling & Analysis OOPT (Object Oriented Process with Trace) Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr What is OOPT? OOPT (Object Oriented Process with Trace) A software process based on RUP Revision
More informationChapter. Redesigning The Organization With Information Systems
Chapter Redesigning The Organization With Information Systems 1 Objectives Demonstrate how building new systems produces organizational change Explain how a company can develop information systems that
More informationIntroduction of RUP - The Rational Unified Process
Introduction of RUP - The Rational Unified Process Jong-Hoon Lee Dependable Software Laboratory Konkuk University References Textbook: The Rational Unified Process Made Easy A Practitioner s Guide to the
More informationCHAPTER 2 LITERATURE SURVEY
10 CHAPTER 2 LITERATURE SURVEY This chapter provides the related work that has been done about the software performance requirements which includes the sub sections like requirements engineering, functional
More informationABHELSINKI UNIVERSITY OF TECHNOLOGY
T 76.3601 Introduction to Software Engineering Software Life-Cycle Models http://www.soberit.hut.fi/t-76.3601/ Casper.Lassenius@tkk.fi Software Engineering? 1. The application of a systematic, disciplined,
More informationSoftware Metrics. Practical Approach. A Rigorous and. Norman Fenton. James Bieman THIRD EDITION. CRC Press CHAPMAN & HALIVCRC INNOVATIONS IN
CHAPMAN & HALIVCRC INNOVATIONS IN SOFTWARE ENGINEERING AND SOFTWARE DEVELOPMENT Software Metrics A Rigorous and Practical Approach THIRD EDITION Norman Fenton Queen Mary University of London. UK James
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 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 informationSOFTWARE QUALIT ASSURANCE- QUESTION BANK
Velammal College of Engineering & Technology, Madurai-625 009 Department of Information Technology 2017-2018 Even Semester Degree Course Code-Title B.Tech-IT IT6013/Software Quality Assurance Batch 2014-2018
More informationCONTENTS. Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1. Part II TECHNOLOGY FOR BUSINESS PROCESSES AND INFORMATION SYSTEMS 65
CONTENTS Part I BUSINESS PROCESSES AND INFORMATION SYSTEMS FOUNDATION 1 Chapter 1 Introduction to Information Systems 2 Synopsis 3 Introduction 4 The Textbook s Three Themes 4 Challenges and Opportunities
More informationQuality Management of Software and Systems: Processes and QM
Quality Management of Software and Systems: Processes and QM Contents V-Model XT Rational Unified Process (RUP) Extreme Programming (XP) Processes 2 V-Model XT Starting point: V-Model 97 Broadened guideline
More informationProcess, Models, Methods, Diagrams Software Development Life Cyles. Part - II
Process, Models, Methods, Diagrams Software Development Life Cyles Part - II A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process maturity based
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 informationUnified Process and Testing with EasyAccept. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007
Unified Process and Testing with EasyAccept Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007 2 UP Unified Process, 1990 s Iterative, not agile Risk-driven development
More informationMARKETING MANAGEMENT
MARKETING MANAGEMENT A STRATEGIC DECISION-MAKING APPROACH llusirei J^- uu y (MlsilitiSiOproi @inicql (fj) Boston Burr Ridge, IL Dubuque, IA- New York San Francisco St. Louis Bangkok Bogota Caracas Kuala
More informationIntroduction to Software Engineering: Project Management ( Highlights )
Introduction to Software Engineering: Project Management ( Highlights ) John T. Bell Department of Computer Science University of Illinois, Chicago Based on materials from chapters 14, 15, and 16 of Object
More informationIntroduction to Software Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016
Introduction to Software Life Cycles CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016 1 Goals Present an introduction to the topic of software life cycles concepts and terminology benefits
More informationThe good news. 34% of software projects succeed. Standish Group, CHAOS Report, 2003
The good news 34% of software projects succeed. Standish Group, CHAOS Report, 2003 1 The bad news That means 66% failed! Standish Group, CHAOS Report, 2003 2 Best Practices Develop Iteratively Manage Requirements
More informationFocus Area Level Report Including Knowledge and Skills, and Performance Indicators
Including Knowledge and Skills, and CSPB01.01 Identify and analyze customer software needs and requirements. CSPB01.01.01.00 Gather data to identify customer requirements. CSPB01.01.01.01 Gather information
More informationSERVICES MARKETING PEOPLE, TECHNOLOGY, STRATEGY. Christopher Lovelock. Yale University. Jochen Wirtz. National University of Singapore
Seventh Edition SERVICES MARKETING PEOPLE, TECHNOLOGY, STRATEGY Christopher Lovelock Yale University Jochen Wirtz National University of Singapore Prentice Hall Boston Columbus Indianapolis New York San
More informationKINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK
KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK Subject Code & Subject Name: IT1251 Software Engineering and Quality Assurance Year / Sem : II / IV UNIT I SOFTWARE PRODUCT
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 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 informationUnderstanding SOA with Web Services
Understanding SOA with Web Services Eric Newcomer and Greg Lomow.:Addison-Wesley Upper Saddle River, NJ m Boston x Indianapolis San Francisco m New York m Toronto u Montreal London m Munich r Paris m Madrid
More information! To solve problems. ! To take up new opportunities. ! Requirements - descriptions of. " Behavior. " Data. " Constraints (eg. cost and schedule)
COMP3110/6311, Software Analysis and Design Why do we Develop Software? To solve problems To take up new opportunities The value of Requirements "#$"%&'(%)#*+"%#)&),'$&+)& '()#-&)'$./,0.&+%/&.%1"*(%2.%#
More informationFocus Area Level Report Including Knowledge and Skills, and Performance Indicators
Including Knowledge and Skills, and ICPB01.01 Identify and analyze customer software needs and requirements. ICPB01.01.01.00 Gather data to identify customer requirements. ICPB01.01.01.01 Gather information
More informationUnified Process. Peter Dolog dolog [at] cs [dot] aau [dot] dk Information Systems March 3, 2008
Unified Process Peter Dolog dolog [at] cs [dot] aau [dot] dk 5.2.47 Information Systems March 3, 2008 2 Outline Model Driven Design Tutorial on Requirements Eng. and SCRUM reflections (D402a, s601c) Unified
More informationService-Oriented Modeling (SOA): Service Analysis, Design, and Architecture
Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture Preface. Chapter 1. Introduction. Service-Oriented Modelling: What Is It About? Driving Principles Of Service-Oriented Modelling.
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 informationChapter 1. Contents. What is Software Engineering 9/9/13. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationSTRATEGIC MANAGEMENT INACTION
SIXTH EDITION STRATEGIC MANAGEMENT INACTION Missouri State University PEARSON Boston Columbus Indianapolis New York San Francisco Upper Saddle River Amsterdam Cape Town Dubai London Madrid Milan Munich
More informationVALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur
VALLIAMMAI ENGNIEERING COLLEGE SRM Nagar, Kattankulathur 603203. DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING Year & Semester : II/ III Section : M.E -CSE Subject Code : CP7301 Subject Name : SOFTWARE
More information2009 Spring. Software Modeling & Analysis. Introduction to OSP. Lecturer: JUNBEOM YOO
2009 Spring Software Modeling & Analysis Introduction to OSP OSP Stage 1000 Lecturer: JUNBEOM YOO jbyoo@konkuk.ac.kr What is OSP? OSP (Object Space Process) A software process based on RUP Tailored to
More informationGlobal Marketin. McGraw-Hill Irwin
Global Marketin Foreign Entry, Local Marketing, & Global Management Fifth Edition Johny K. Johansson Georgetown University McGraw-Hill Irwin Boston Burr Ridge, IL Dubuque, IA Madison, WI New York San Francisco
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 information(c) Addison Wesley Chapter 1. ! Software production is an art. ! Two groups. ! Main causes of software failures
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 1 Software Process Copyright 2000 by Addison Wesley Version 1.0 Software
More information7. What is planning? It is an act of formulating a program for a definite course of action. Planning is to decide what is to be done.
UNIT I FUNDAMENTALS 2 MARKS QUESTIONS & ANSWERS 1. What is software project management? Software project management is the art and science of planning and leading software projects. It is sub discipline
More informationIT Architectures and Middleware
IT Architectures and Middleware Second Edition Strategies for Building Large, Integrated Systems Chris Britton Peter Bye AAddison-Wesley TT Boston San Francisco New York Toronto Montreal London Munich
More informationContents. About the authors
Contents About the authors Glossary Prologue References xi xiii xvii xxii Part I Modeling and simulation framework for value-based healthcare systems 1 1 Healthcare systems modeling and simulation 3 1.1
More informationChapter 1. What is Software Engineering. Shari L. Pfleeger Joanne M. Atlee. 4 th Edition
Chapter 1 What is Software Engineering Shari L. Pfleeger Joanne M. Atlee 4 th Edition Contents 1.1 What is Software Engineering? 1.2 How Successful Have We Been? 1.3 What Is Good Software? 1.4 Who Does
More informationInception. Describe the vision and business case for this project. Determine if the enterprise should build or buy the necessary system.
Inception What needs to be done? Describe the vision and business case for this project. Determine if the project is feasible. Determine if the enterprise should build or buy the necessary system. Make
More informationCourse title: SOFTWARE ANALYSIS AND DESIGN
Course title: SOFTWARE ANALYSIS AND DESIGN Lecturers Full Prof. Neven Vrček, Ph.D., Asst. Prof. Zlatko Stapić, Ph.D., Ivan Švogor, Ph.D., Mišo Džeko, M. Inf. Language of Croatian and English instruction
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 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 information