Chapter 8. Systems Development. Ralph M. Stair George W. Reynolds
|
|
- Valerie Hood
- 6 years ago
- Views:
Transcription
1 Ralph M. Stair George W. Reynolds Chapter 8 Systems Development
2 An Overview of Systems Development Managers and employees in all functional areas work together and use business information systems Corporations and nonprofit organizations use the systems development process to build information systems to achieve their goals 2
3 Participants in Systems Development The development team: Consists of stakeholders, users, managers, systems development specialists, and various support personnel Determines information system s objectives Delivers a system that meets objectives 3
4 Participants in Systems Development: the Development Team Project manager: the person assigned by the organization to do the work of the project and achieve the project objectives Stakeholders: people who ultimately will be affected (for better or worse) by the systems development project Users: people who will regularly interact with the system 4
5 Participants in Systems Development: the Development Team (cont d.) Systems analysts: specializes in analyzing and designing business systems Programmer: responsible for modifying or developing programs to satisfy user requirements 5
6 Role of the Project Manager 6
7 Systems Development: Others Directly Involved Steering team A small group of senior managers representing the business and IS organizations that provide guidance and support to the project Project sponsor A key member and leader of the steering team who plays such a critical role that lack of this essential individual raises the distinct probability of project failure 7
8 Information Systems Planning Identifies those information systems development initiatives needed to support organizational strategic goals Systems development projects are initiated to meet organizational goals outlined in the strategic plan 8
9 Information Systems Planning (cont d.) 9
10 Initiating Systems Development Systems development initiatives: Arise from all levels of an organization Can be planned or unplanned Can take advantage of new technologies Mergers and acquisitions can trigger many systems development projects 10
11 Traditional Systems Development Life Cycle Also called a systems development life cycle (SDLC) A sequential multistage process where work on the next stage cannot begin until the results of the previous stage are reviewed and approved or modified as necessary 11
12 Traditional Systems Development Life Cycle (cont d.) 12
13 Table 8.1 Advantages and Disadvantages of Traditional SDLC Advantages Formal review at the end of each phase allows maximum management control. This approach requires creation of considerable system documentation. Formal documentation ensures that system requirements can be traced back to stated business needs. Approach produces many intermediate products that can be reviewed to see whether they meet the users needs and conform to standards. Disadvantages Users get a system that meets the needs as understood by the developers; this might not be what the users really needed. Documentation is expensive and time consuming to create. It is also difficult to keep current. Often, user needs go unstated or are miscommunicated or misunderstood. Users can t easily review intermediate products and evaluate whether a particular product (e.g., a dataflow diagram) meets their business requirements. 13
14 SDLC: Systems Investigation The purpose of this phase of systems development is to gain a clear understanding of the specifics of the problem to be solved or the opportunity to be addressed Feasibility analysis: assessment of the technical, economic, legal, operational, and schedule feasibility of a project
15 SDLC: Systems Analysis This phase of systems development involves: Gathering data on the existing system Determining the requirements for the new system Considering alternatives within identified constraints Investigating the feasibility of alternative solutions
16 SDLC: Systems Design The stage of systems development that creates a complete set of technical specifications that can be used to construct the information system
17 SDLC: System Construction The phase of systems development that converts the system design into an operational system by: Acquiring and installing hardware and software Coding and testing software programs Creating and loading data into databases Performing initial program testing
18 SDLC: Integration Testing Also called integration and testing (I & T) Testing that involves linking all of the individual components together and testing them as a group to uncover any defects between individual components
19 Table 8.2 Tests Conducted on an Information System Form of Test What Is Tested Purpose of Test Who Does It User Acceptance Volume Test the complete, integrated system (hardware, software, databases, people, and procedures). Evaluate the performance of the information system under realistic and varying work volume and operating conditions. Verify the information system can complete required tasks in a real-world operating environment and do this according to the system design specifications. Determine the work load at which systems performance begins to degrade and identify and eliminate any issues that prevent the system from reaching its required service- level performance. Trained users of the system System development team and members of the operations organization 19
20 Table 8.2 Tests Conducted on an Information System (cont d.) Form of Test What Is Tested Purpose of Test Who Does It System Test the complete, integrated system (hardware, software, databases, people, and procedures). Validate that the information system meets all specified requirements. Independent test team separate from the software development team Integration Unit Test all of the individual units of the information system linked together. Test individual units of the system. Uncover any defects between individual components of the information system. Verify that each unit performs as designed. Software developers or independent software testers using black box testing measures Software developers 20
21 SDLC: Systems Implementation Successfully introducing an information system into an organization The major challenges to successful implementation of an information system are often more behavioral than technical Strong, effective leadership is required to overcome the behavioral resistance
22 SDLC: Systems Operation and Maintenance Systems operation: using a new or modified system under all kinds of operating conditions Systems maintenance: changing and enhancing the system to make it more useful in achieving user and organizational goals
23 SDLC: System Disposal Those activities that ensure the orderly dissolution of the system Activities include: Closing out any contracts in place Disposing of all equipment in an environmentally friendly manner Safely migrating information from the system to another system or archiving information in accord with records management policies
24 Useful Software Development Techniques Joint Application Development (JAD) Functional decomposition Data flow diagrams Request for proposal
25 Joint Application Development (JAD) A structured meeting process that can accelerate and improve the efficiency and effectiveness of the investigation, analysis, and design phases of a systems development project The success or failure of a JAD session depends on how well the JAD facilitator plans and manages the session
26 Table 8.3 JAD Participants and Their Role Role Responsibilities Qualifications Facilitator Determines JAD session objectives Plans JAD session to meet objectives Leads JAD session Encourages everyone to participate Excellent meeting facilitator Unbiased and does not take sides Decision makers Users Resolve conflicts Avoid gridlock Describe business as it is and as it should be Provide business expertise Define problems, identify potential benefits, analyze existing system, define requirements of a new system, and propose and evaluate possible solutions Stakeholders selected by project sponsor to make decisions Have the authority and willingness to make decisions Represent all major areas affected Expert in their area of the business 26
27 Table 8.3 JAD Participants and Their Role (cont d.) Role Responsibilities Qualifications System developers Observe carefully Offer technical opinion on cost or feasibility, if requested Gain deep understanding of customers Member of system development team Scribe needs and desires Participate in discussion to clarify points and capture them accurately Document key points, issues, next steps, and decisions throughout the JAD session Publish results of JAD session and solicit feedback Excellent listening skills Experience in using software engineering tools to document requirements and create system models 27
28 Functional Decomposition A technique used primarily during the investigation phase to define the business processes included within the scope of the system Create a functional decomposition chart Begin with the name of a system Identify the highest-level processes and assign a verb-subject name to each process Break down to three to four subprocess levels 28
29 Functional Decomposition Chart 29
30 Data Flow Diagram (DFD) A diagram used during both the analysis and design phases to document the processes of the current system or to provide a model of a proposed new system Includes four primary symbols: Data-flow line, process symbol, entity symbol, and data store
31 Data Flow Diagram 31
32 Relative Cost of Custom Software 32
33 Table 8.4 Comparison of Off-the-Shelf and Developed Software Factor Develop (Make) Off-the-Shelf (Buy) Cost Needs Process improvement Quality The cost to build the system can be difficult to estimate accurately and is frequently higher than off-the-shelf Custom software is more likely to satisfy your needs Tend to automate existing business processes even if they are poor Quality can vary depending on the development team The true cost to implement an off-the-shelf solution is also difficult to estimate accurately but is likely to be less than a custom software solution Might not get exactly what you need Adoption of a package may simplify or streamline a poor existing business process Can assess the quality before buying Speed Can take years to develop Can acquire it now Staffing and support Competitive advantage Requires in-house skilled resources to build and support a custom-built solution Can develop a competitive advantage with good software Requires paying the vendor for support Other organizations can have the same software and same advantage 33
34 Request for Proposal A formal document that outlines an organization s hardware or software needs and requests vendors to develop a detailed proposal of how they would meet those needs and at what cost
35 Recommended Table of Contents for a Request for Proposal 35
36 Alternate Systems Development Life Cycles and Approaches Alternate approaches include: Prototyping Agile Object-oriented Mobile End-user development 36
37 Prototyping Software prototype: a working model of a system developed to enable users to interact with it and provide feedback so developers can better understand what is needed Prototyping is an iterative software development approach 37
38 Prototyping: an Iterative Approach to Systems Development 38
39 Table 8.5 Advantages and Disadvantages of Prototyping Advantages Users can try the system and provide constructive feedback during development. A throw-away prototype can be produced in days. As solutions emerge, users become more positive about the process and the results. Prototyping enables early detection of errors and omissions. Disadvantages Each iteration builds on the previous one. The final solution might be only incrementally better than the initial solution. Formal end-of-phase reviews might not occur. Thus, it is very difficult to contain the scope of the prototype, and the project never seems to end. System documentation is often absent or incomplete because the primary focus is on development of the prototype. System backup and recovery, performance, and security issues can be overlooked in the haste to develop a prototype. 39
40 Prototyping (cont d.) A throw-away prototype: one that is used to help define the software A working prototype: evolves into the final software solution The Rational Unified Process (RUP): an iterative systems development approach developed by IBM RUP stresses quality as the software is changed and updated over time 40
41 Agile Development An iterative system development process that develops the system in sprint increments lasting from two weeks to two months Concentrates on maximizing the team s ability to deliver quickly and respond to emerging requirements 41
42 Agile Development (cont d.) Scrum: a method to keep the agile system development effort focused and moving quickly The scrum master coordinates all activities Extreme programming (XP) promotes incremental development of a system using short development cycles to: Improve productivity Accommodate new customer requirements 42
43 Agile System Development Life Cycle 43
44 Table 8.6 Advantages and Disadvantages of Agile Development Advantages For appropriate projects, this approach puts an application into production sooner than any other approach. Documentation is produced as a by-product of completing project tasks. Agile forces teamwork and lots of interaction between users and stakeholders. Disadvantages This intense SDLC can burn out systems developers and other project participants. This approach requires systems analysts and users to be skilled in agile systems development tools and agile techniques. Agile requires a larger percentage of stakeholders and users time than other approaches. 44
45 Table 8.7 Comparison of System Development Life Cycles Characteristic Description Basic assumption System Development Life Cycle Agile Prototype Traditional An iterative process that develops the system in sprint increments lasting 2 8 weeks; each increment focuses on implementing the highest priority requirements that can be completed in the allotted time System requirements cannot be fully defined at start of project An iterative process that constructs prototypes or uses application frameworks System requirements cannot be fully defined at start of project A sequential multistage process where work on the next stage cannot begin until the results of the previous stage are reviewed and approved or modified as necessary All critical system requirements can be fully defined at start of project How requirements and design are defined Users interacting with systems analysts and working software Users interacting with systems analysts and prototypes Users interacting with systems analysts and system documentation and/or models Associated processes Scrum Rapid application development Structured systems analysis and design 45
46 Object-Oriented Systems Development Frequently used in the investigation, analysis, and design phases of system development Systems analysis: examine problems or potential opportunities Design phase: used to design key objects and classes of objects in the new or updated system; also need to consider sequence of events 46
47 Use Case Diagram for a Kayak Rental Application 47
48 Generalization/Specialization Hierarchy Diagram 48
49 Sequence Diagram 49
50 Mobile Application Development How system development differs from development of traditional systems User interface is a touch user interface Development teams are smaller more flexible and agile The application must communicate with the Internet or corporate computers A method of handling phone calls while running an application needs to be resolved 50
51 Table 8.8 Application Development Tools for Mobile Environment Tool Alpha Anywhere App Press ibuildapp Mobile Chrome Development Kit Salesforce1 ViziApps Target Environment ios, Android, Windows Phone iphone, ipad, Android iphone, ipad, Android ios, Android, Chrome ios, Android ios, Android 51
52 User Systems Development End-user systems development The creation, modification, or extension of software by people who are nonprofessional software developers Most common example: creating spreadsheets Must be subjected to the same reliability, performance, and quality issues as software developed by professionals 52
53 Tips to Avoid Project Major reasons projects fail Failure of executives to provide leadership and direction Unclear project scope Poorly managed expectations Insufficient user involvement An organization s unpreparedness for change Poor planning 53
54 Project Failure 54
55 Table 8.9 Factors in Project Failure Factors Potential Reason(s) Countermeasures Business executives fail to provide leadership and direction to project team Project is not aligned with business strategy or addresses the wrong problem or opportunity. Correct business sponsor is not identified or recruited to provide leadership. System investigation team must work hard to ensure that the problem or opportunity is aligned with business strategy and worth working on. Project manager must insist that project steering team be appointed including the correct business sponsor. Scope of the project is unclear The root cause of the problem to be solved or opportunity to be addressed has not been well defined. System investigation team must work with stakeholders to correctly define scope of the project using techniques such as functional decomposition. Narrow the project focus to address only the most important business opportunities. 55
56 Table 8.9 Factors in Project Failure (cont d.) Factors Potential Reason(s) Countermeasures Expectations are poorly managed Insufficient user involvement Organization not prepared for change Poor planning Project manager incorrectly assumes that the initial statement of stakeholder and end-user expectations is complete and unchanging. Users are busy and do not see value in their participation. Project team focuses on technical aspects of project. Project team is unable to define schedule for complex project. Project manager must meet with stakeholders and end users on a regular basis to discuss expectations, document project success criteria, and share project results and status. Key users should be part of the project team and have an ongoing role in ensuring that their needs and the needs of the business are met. Use prototyping. Project steering team should assist in preparing organization to accept change. Use project management tools to determine and document who needs to do what and when. 56
Chapter 13. Building Information Systems
Chapter 13 Building Information Systems Learning Objectives How does building new systems produce organizational change? What are the core activities in the systems development process? What are the principal
More informationThe Systems Development Lifecycle
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system developments projects The project Major attributes of the Lifecycle Moves systematically
More informationBuilding Information Systems
Building Information Systems Content Explain how building new systems produces organizational change. Describe the core activities in the systems development process. Describe the principal methodologies
More informationChapter 3. Information Systems Development. McGraw-Hill/Irwin. Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Chapter 3 Information Systems Development McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 3-2 Describe the motivation for a system development process
More informationMajor attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
More informationSoftware Engineering. M Umair.
Software Engineering M Umair www.m-umair.com Activity and Sprint An activity is a general term for any part of a project that takes place over time (also known as a task) Each step in the software development
More informationCOMM 391. Learning Objective 1. Learning Objectives. Introduction to Management Information Systems
COMM 391 Introduction to Management Information Systems INFORMATION SYSTEMS SOURCING AND PROJECT MANAGEMENT Winter 2014 Term 1 Learning Objectives 1. Explain the basic concepts of IS projects. 2. Describe
More informationCHAPTER 4 PRODUCT DEVELOPMENT LIFE CYCLE
CHAPTER 4 PRODUCT DEVELOPMENT LIFE CYCLE 1 Learning Objectives Review the Systems Development Life Cycle (SDLC). Examine the problems and alternatives with SDLC. Know the key issues in ERP implementation
More informationHarnessing the power of agile development
Microsoft IT Showcase Harnessing the power of agile development Integrating an acquired business means adjusting business processes, integrating data and technology platforms, and onboarding teams. When
More information2 Why is systems development difficult and risky? 3 How do businesses use the systems development life cycle (SDLC) process?
1 What is systems development? 2 Why is systems development difficult and risky? 3 How do businesses use the systems development life cycle (SDLC) process? 4 How do businesses use the rapid application
More informationRequirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
More informationChapter 2: The Project Management and Information Technology Context
Chapter 2: The Project Management and Information Technology Context TRUE/FALSE 1. Many of the theories and concepts of project management are difficult to understand. F PTS: 1 REF: 44 2. If project managers
More informationChapter 2 Analyzing the Business Case
Chapter 2 Analyzing the Business Case Explain the concept of a business case and how a business case affects an IT project Describe the strategic planning process and why it is important to the IT team
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 informationISACA Systems Implementation Assurance February 2009
ISACA Pressures Today Pressure to increase realization of value from IT spending Pressure to deliver on IT projects at a time when resources/budgets are constrained Pressure from risk of technology-based
More informationBuilding Information Systems
Chapter 13 Building Information Systems 13.1 2010 by Prentice Hall LEARNING OBJECTIVES Demonstrate how building new systems produces organizational change. Identify and describe the core activities in
More informationSoftware Design COSC 4353/6353 D R. R A J S I N G H
Software Design COSC 4353/6353 D R. R A J S I N G H Outline Week 2 Software Development Process Software Development Methodologies SDLC Agile Software Development Process A structure imposed on the development
More informationDETERMINING SYSTEM REQUIREMENTS. Systems Analysis and Design
DETERMINING SYSTEM REQUIREMENTS Systems Analysis and Design Introduction Performing Requirements Determination Traditional Methods for Determining Requirements Contemporary Methods for Determining Systems
More informationVendor: GAQM. Exam Code: CSM-001. Exam Name: Certified Scrum Master (CSM) Version: Demo
Vendor: GAQM Exam Code: CSM-001 Exam Name: Certified Scrum Master (CSM) Version: Demo QUESTION 1 What is the maximum amount of time that the team should spend in the daily scrum? A. As long as it takes
More informationIntroduction to Systems Analysis and Design
Introduction to Systems Analysis and Design What is a System? A system is a set of interrelated components that function together to achieve a common goal. The components of a system are called subsystems.
More 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 informationManaging Systems Development. Definitions. Opening case. Off the Shelf software. Custom software. In house system development.
Managing Systems Development October 14, 2015 Off the Shelf software Definitions Standard (not custom) software applications that can be purchased from computer store. Custom software Tailor made software
More informationProject Management Knowledge Areas SECTION III
Project Management Knowledge Areas SECTION III 1 Project Integration Management CHAPTER 4 2 The Key to Overall Project Success: Good Project Integration Management Project managers must coordinate all
More information1) Introduction to Information Systems
1) Introduction to Information Systems a) System: A set of related components, which can process input to produce a certain output. b) Information System (IS): A combination of hardware, software and telecommunication
More informationChapter 2: The Project Management and Information Technology Context
True / False 1. Project managers should lead projects in isolation in order to truly serve the needs of the organization. False Feedback: Even though projects are temporary and intended to provide a unique
More informationSample Exam ISTQB Agile Foundation Questions. Exam Prepared By
Sample Exam ISTQB Agile Foundation Questions Exam Prepared By November 2016 1 #1 Which of the following is the correct pairing according to the Agile Manifesto statement of values? a. Individuals and Interactions
More informationChapter 1 The Systems Development Environment
Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter 1 The Systems Development Environment 1.1 Learning Objectives Define information systems
More informationRedesigning the Organization with Information Systems
Chapter 14 Redesigning the Organization with Information Systems 14.1 2006 by Prentice Hall OBJECTIVES Demonstrate how building new systems produces organizational change Explain how a company can develop
More information[Name] [ ID] [Contact Number]
[Name] [Email ID] [Contact Number] THIS IS ONLY MODEL RESUME - DO NOT COPY AND PASTE INTO YOUR RESUME. PROFILE SUMMARY 15+ years of IT experience in Consulting and worked with the Major clients for the
More informationProject Management Methodology. Construct & Unit Test SubPhase
Project Management Methodology & Unit Test SubPhase Course Purpose Familiarize team members with the & Unit Test Sub- Phase processes. Understand process flows, team member roles, and artifacts employed.
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 informationSoftware Development Software Development Activities
Software Development Software Development Activities Problem Definition Requirements Analysis Implementation Planning High-level Design (or Architecture) Detailed Design Coding and Unit Testing (Debugging)
More informationSoftware Engineering Lecture 5 Agile Software Development
Software Engineering Lecture 5 Agile Software Development JJCAO Mostly based on the presentation of Software Engineering, 9ed Exercise Describe the main activities in the software design process and the
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 informationSoftware Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationSystem Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102
System Development Life Cycle Fall 2016 Introduction to Information and Communication Technologies CSD 102 Outline Software Engineering SDLC Mehwish Fatima - CIIT Lahore 06/11/2016 2 What is the System
More informationChapter 1 Introduction to Systems Analysis and Design
Chapter 1 Introduction to Systems Analysis and Design MULTIPLE CHOICE 1. In launching a new information system, the greatest risk occurs when a company. a. begins by outlining its business models and identifying
More informationLecture 1. Topics covered. Rapid p development and delivery is now often the most important requirement for software systems.
Chapter 3 Agile Software Development Lecture 1 Topics covered Agile g methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods Rapid software development
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 informationBusiness Analysis Essentials
Understand the business analyst's role and responsibilities in a successful project. In this introductory course, you'll delve into the role and responsibilities of the business analyst (BA)- the communication
More informationRequirement Error Taxonomy
Requirement Error Taxonomy Loan arranger system (LA): The LA application supports the business of a loan consolidation organization. This type of organization makes money by purchasing loans from banks
More informationBy: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson
By: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson WATERFALL? XP? SCRUM? While there is really no standard solution, the following presentation will
More informationIT Information Systems & Technology. BIT 1 ST YEAR SEMESTER 1 University of Colombo School of Com puting. Student Manual
IT1105 - Information Systems & Technology BIT 1 ST YEAR SEMESTER 1 University of Colombo School of Com puting Student Manual Lesson 6: Systems Development By G.K.A. DIAS and Dr. Y. Ekanayaka Duration:
More informationPrinciples of Information Systems
Principles of Information Systems Session 08 Systems Investigation and Analysis An Overview of Systems Development Today, users of informa0on systems are involved in their development Avoid costly failures
More informationQUICK FACTS. Designing and Testing a Mobile Application for a Fortune 500 Energy Company TEKSYSTEMS GLOBAL SERVICES CUSTOMER SUCCESS STORIES
[ Energy, Application Development Mobility ] TEKSYSTEMS GLOBAL SERVICES CUSTOMER SUCCESS STORIES Client Profile Industry: Electricity, natural gas and green energy Revenue: $33 billion Employees: Approximately
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 informationOther Agile Approaches & Methodologies
Other Agile Approaches & Methodologies 10 Most common Agile Methodologies Scrum XP Kanban => Lean House D. Sixth Annual State of Agile Survey: State of Agile Development, Atlanta, GA, VersionOne, 2012
More informationII. Software Life Cycle. Laurea Triennale in Informatica Corso di Ingegneria del Software I A.A. 2006/2007 Andrea Polini
II. Software Life Cycle Laurea Triennale in Informatica Corso di Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process
More informationBased on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems
Software Processes Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems Slide 1 Objectives To introduce software
More informationSoftware Engineering
Software Engineering (CS550) Software Development Process Jongmoon Baik Software Development Processes (Lifecycle Models) 2 What is a S/W Life Cycle? The series of stages in form and functional activity
More informationSoftware Processes 1
Software Processes 1 Topics covered Software process models Process activities Coping with change 2 The software process A structured set of activities required to develop a software system. Many different
More informationModern Systems Analysis and Design Seventh Edition
Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich The Systems Development Environment Learning Objectives Define information systems analysis and design.
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationObjectives. Rapid software development. Topics covered. Rapid software development. Requirements. Characteristics of RAD processes
Objectives Rapid software development To explain how an iterative, incremental development process leads to faster delivery of more useful software To discuss the essence of agile development methods To
More informationapproach to successful project
1 The NYS Forum, Inc. Using an Agile / Waterfall Hybrid approach to successful project delivery Presented by Matthew Carmichael Project Management Workgroup 2 When to use Waterfall Projects that require
More information3. Comparison of Above Described SDLC Models
123 3. Comparison of Above Described SDLC Models Waterfall Model is little hard to manage due to the rigidity of the model as each phase has specific deliverables and a review process. It works well for
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More informationInformation Systems Development
Information Systems Development Based on Chapter 3 of Whitten, Bentley, and Dittman: Systems Analysis and Design for the Global Enterprise (7th Ed). McGraw Hill. 2007 Wei-Tsong Wang 1 IIM, NCKU 3 Objectives
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationCritical Skills for Writing Better Requirements (Virtual Classroom Edition)
Critical Skills for Writing Better Requirements (Virtual Classroom Edition) Eliminate Costly Changes and Save Time by Nailing Down the Project Requirements the First Time! Critical Skills for Writing Better
More informationUnit 9 Information Systems
Unit 9 Information Systems Computer Concepts 2016 ENHANCED EDITION 9 Unit Contents Section A: Information System Basics Section B: Enterprise Applications Section C: Systems Analysis Section D: Design
More informationInformation Technology Audit & Cyber Security
Information Technology Audit & Cyber Security Managing Information System Projects Systems & Infrastructure Lifecycle Management Introduction Definitions INTRODUCTION Governance Roles and Responsibilities
More informationChild Welfare Services New System Project. Requirements Management Plan
Child Welfare Services New System Project Requirements Management Plan September 2017 Revision History REVISION HISTORY REVISION/VERSION # DATE OF RELEASE AUTHOR SUMMARY OF CHANGES Version 1.0 October
More informationChapter One PROJECT MANAGEMENT OVERVIEW
Chapter One PROJECT MANAGEMENT OVERVIEW Project management itself is not a new concept. It has been practiced for hundreds, even thousands of years. Any large undertaking requires a set of objectives,
More informationWHEN AGILE MEETS OUTSOURCING
WHEN AGILE MEETS OUTSOURCING By Heiner Himmelreich, Peter Hildebrandt, Rohit Nalgirkar, and Joppe Bijlsma As IT organizations introduce agile ways of working, they often run headon into an existing business
More informationSTUDY GUIDE CHAPTER 10
STUDY GUIDE CHAPTER 10 True/False Indicate whether the statement is true or false. 1. Nonprofit organizations are formed to accomplish social, political, or charitable goals that do not include amassing
More informationINTRODUCTION TO COMPUTER INFORMATION SYSTEMS/INFORMATION SYSTEMS
Page 1 of 9 INTRODUCTION TO COMPUTER INFORMATION SYSTEMS/INFORMATION SYSTEMS 7.1 What is an Information System? A system is a group of procedures and different elements that work together in order complete
More informationBusiness Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura
Business Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura www.linkedin.com/in/linkedincherifamansoura Introduction BA responsibilities in an agile environment PO Responsibilities
More informationCase Study: Applying Agile Software Practices to Systems Engineering
Case Study: Applying Agile Software Practices to Systems Engineering Presented by: Matthew R. Kennedy, PhD IEEE Software Technology Conference April 10 th, 2013 Definitions Agility The speed of operations
More informationElicit the Requirements
Chapter 3 Elicit the Requirements One of the most crucial and challenging aspects of software development is defining the requirements for the proposed software. Elicitation identifies the sources for
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 informationTuesday, October 25. Announcements
Tuesday, October 25 Announcements Crowdsourcing the Midterm http://www.drsusansim.org/teaching/inf111/pligg Homework 5 Skip lab portion Use anything you want to draw the diagrams for the take home portion
More information6/29/ Professor Lili Saghafi
6/29/2014 1 Professor Lili Saghafi MANAGING INFORMATION TECHNOLOGY Lecture 9 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT By : Prof. Lili Saghafi 1-2 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT Large
More informationHarry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning.
Chapter 1 Introduction to Systems Analysis and Design Harry J. Rosenblatt. (2014). Systems Analysis and Design, 10 th Edition, International Edition. Course Technology, Cengage Learning. Describe the impact
More informationSoftware Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000)
Software Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000) armahmood786@yahoo.com alphasecure@gmail.com alphapeeler.sf.net/pubkeys/pkey.htm http://alphapeeler.sourceforge.net
More informationChapter 6 Determining System Requirements
Princess Noura University Department of Computer Science ff IS321 Chapter 6 Determining System Requirements Learning Objectives Describe interviewing options and develop interview plan. Explain advantages
More informationLesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence,
Lesson Three: Business Analysis Planning and Monitoring BANA 110 Analyzing Business Needs and Requirements Planning Gary Mesick and Shelly Lawrence, Instructors YOU ARE HERE Analysis and the Decision to
More informationLectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1
Lectures 2 & 3 Software Processes Software Engineering, COMP201 Slide 1 What is a Process? When we provide a service or create a product we always follow a sequence of steps to accomplish a set of tasks
More informationSystems Analysis and Design 8 th Edition. Chapter 1 Introduction to Systems Analysis and Design
Systems Analysis and Design 8 th Edition Chapter 1 Introduction to Systems Analysis and Design Chapter Objectives Discuss the impact of information technology on business strategy and success Define an
More informationINFORMATION SYSTEMS (IS) SYSTEMS DEVELOPMENT SERVICES TITLE SERIES DEFINITIONS
Effective Date: July 1, 2015 INFORMATION SYSTEMS (IS) SYSTEMS DEVELOPMENT SERVICES TITLE SERIES DEFINITIONS I. DEFINITIONS A. Identifying the Correct Job title This section defines duties performed by
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 informationPART THREE: Work Plan and IV&V Methodology (RFP 5.3.3)
PART THREE: Work Plan and IV&V Methodology (RFP 5.3.3) 3.1 IV&V Methodology and Work Plan 3.1.1 NTT DATA IV&V Framework We believe that successful IV&V is more than just verification that the processes
More informationSystems Requirements. Requirements Determination. Learning Objectives. Major part of Systems Analysis
Systems Requirements 10/4/2010 Abdou Illia MIS 4200 - Fall 2010 Learning Objectives Describe options for designing and conducting interviews. Discuss planning an interview to determine system requirements.
More informationChapter 2: The Project Management and Information Technology Context. PTS: 1 DIF: Difficulty: Easy REF: p.45 OBJ: LO: 2-1 NAT: BUSPROG: Analytic
Chapter 2: The Project Management and Information Technology Context TRUE/FALSE 1. Project managers should lead projects in isolation in order to truly serve the needs of the organization. Even though
More informationMeltem Özturan
Meltem Özturan www.mis.boun.edu.tr/ozturan/samd 2 1 Information Systems (IS) Development Environment Systems Information Systems Information Systems Development 3 (Systems) A system is a collection of
More informationSession 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation
Session 11E Adopting Agile Ground Software Development Supannika Mobasser The Aerospace Corporation The Aerospace Corporation 2017 Overview To look beyond the horizon and to embrace the rapid rate of change
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationWhat are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.
What are requirements? Basics of Requirement Engineering Muzaffar Iqbal Farooqi A requirement is a necessary attribute in a system, a statement that identifies a capability, characteristic, or quality
More informationPROJECT MANAGEMENT OVERVIEW
Chapter One PROJECT MANAGEMENT OVERVIEW Project management itself is not a new concept. It has been practiced for hundreds, even thousands of years. Any large undertaking requires a set of objectives,
More informationDarshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1
Failure Rate Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1 SOFTWARE (What is Software? Explain characteristics of Software. OR How the software product is differing than
More informationChapter 3 Agile Software Development. Part 1b
Chapter 3 Agile Software Development Part 1b 1 Testing in XP Testing is central to XP and XP has developed an approach where the program is tested after every change has been made. XP testing features:
More informationAn Overview of Software Process
An Overview of Software Process Objectives To introduce the general phases of the software development life cycle (SDLC) To describe various generic software process models and discuss their pros and cons
More informationSix Sigma Black Belt Week 3. Six Sigma Black Belt Week 3. Six Sigma Black Belt Week 3. Project Management. Chapter 3-4
Chapter 3-4 Project Management 3-4-1 Project Management Six Sigma involves a process of improvement projects. In order for these to be successful they must be managed. 3-4-2 Administrative Support Steering
More informationAcquiring IT Applications and Infrastructure
Chapter 15 Acquiring IT Applications and Infrastructure Information Technology For Management 6th Edition Turban, Leidner, McLean, Wetherbe Lecture Slides by L. Beaubien, Providence College John Wiley
More information10 Success Factors. for Sales Performance Management. About NICE
About NICE NICE (Nasdaq: NICE) is the worldwide leading provider of both cloud and onpremise enterprise software solutions that empower organizations to make smarter decisions based on advanced analytics
More informationIncident Management Process
OSF Service Support Incident Management Process [Version 1.1] [From https://www.ok.gov/cio/documents/incidentmanagementprocess.doc] Incident Management Process Table of Contents About this document...
More information<Project Name> Business Case
Business Case Author(s) Contributors Department Campus DOCUMENT HISTORY Version Date Person Notes 1.0 ITS Portfolio Management Office Business Case Page 1 TABLE OF CONTENTS
More informationProcesses and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
More information2009 McGraw Hill Ryerson Limited. Kwantlen and Richardson Chpt 6 slide number 1
Chapter 6 Systems Development Phases, Tools, and Techniques Prof. Anita Beecroft, Kwantlen Polytechnic University (2009) Prof. Tim Richardson, University of Toronto (2011) 2009 McGraw Hill Ryerson Limited
More information