Systems Development Process Developing our own software The Business Perspective Copyright © 2016 Curt Hill.

Slides:



Advertisements
Similar presentations
Digital inclusion – a CS perspective Alex Poulovassilis ESRC TLRP-TEL Inclusion and Impact conference, June 2010.
Advertisements

Database Planning, Design, and Administration
ICT Class System Life Cycle.  Large systems development projects may involve dozens of people working over several months or even years, so they cannot.
SDLC Software Development Life Cycle. SDLC Acronym for system development life cycle. Acronym for system development life cycle. Is the process of developing.
Chapter 2 The Origins of Software
Copyright © 2014 Pearson Education, Inc. 1 Managers from across organizations are involved in developing and acquiring information systems Chapter 5 -
Unit 8 Design Strategies and Refactoring. Key Concepts Design strategy deliverables Requirements and constraints Outsourcing Sources of software Platform.
The New Software Accounting Rules-GASB 51
Lab/Sessional -CSE-374. SYSTEM DEVELOPMENT LIFE CYCLE.
Chapter 8 Information Systems Development & Acquisition
Information Systems Development and Acquisition Chapter 8 Jessup & Valacich Instructor: Ramesh Sankaranarayanan.
Chapter 1 Assuming the Role of the Systems Analyst
7.2 System Development Life Cycle (SDLC)
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Management Information Systems, 4 th Edition 1 Chapter 16 Alternative Avenues for Systems Acquisitions.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 2.1.
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 7 System Design and Implementation System Design and.
© Prentice Hall, 2005: Enterprise Resource Planning, 1 st Edition by Mary Sumner 3-1 Enterprise Resource Planning, 1 st Edition by Mary Sumner Chapter.
Introduction to Systems Analysis and Design
Information Systems Development : Overview. Information systems development practice Concept and role of a systems development methodology Approaches.
Chapter 17 Acquiring and Implementing Accounting Information Systems
Acquiring Information Systems and Applications
CORE 1: PROJECT MANAGEMENT Overview TECHNIQUES FOR MANAGING A PROJECT Communication Skills Active Listening Mirroring Paraphrasing Summarizing Clarifying.
Chapter 2 The Origins of Software
Introduction to Information System Development.
SYS364 Evaluating Alternatives. Objectives of the Systems Analysis Phase determine, analyze, organize and document the requirements of a new information.
Categories of Software
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 2 The Sources of Software 2.1.
Chapter 2 The Origins of Software Modern Systems Analysis and Design.
Source: J. Hoffer ,J. George, J. Valacich
Laudon & Laudon: Canadian Edition
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
8-1 Chapter 8 Information Systems Development & Acquisition.
ITEC224 Database Programming
Chapter 1: Introduction to Systems Analysis and Design
ERP. What is ERP?  ERP stands for: Enterprise Resource Planning systems  This is what it does: attempts to integrate all data and processes of an organization.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Chapter 1 Assuming the Role of the Systems Analyst Systems Analysis and Design Kendall & Kendall Sixth Edition.
Database Design and Management CPTG /23/2015Chapter 12 of 38 Functions of a Database Store data Store data School: student records, class schedules,
Chapter 2 The Origins of Software Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Systems Life Cycle A2 Module Heathcote Ch.38.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
Chapter 2 The Origins of Software Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich created by Mr.Mohammed.
Chapter 2 The Origins of Software Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Cis339 Chapter 2 The Origins of Software 2.1 Modern Systems Analysis and Design Fifth Edition.
8-1 © Prentice Hall, 2007 Topic 8: Selecting the Best Alternative Design Strategy Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra,
IS Today (Valacich & Schneider) Copyright © 2010 Pearson Education, Inc. Published as Prentice Hall 1/11/ Chapter 9 Information Systems Development.
IS2210: Systems Analysis and Systems Design and Change Twitter:
Chapter 6 SYSTEMS DEVELOPMENT Phases, Tools, and Techniques.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
Chapter 1 Assuming the Role of the Systems Analyst.
Lecture 2 The Sources of Software. Copyright © 2011 Pearson Education, Inc. 2 Chapter 2 Introduction There are various sources of software for organizations.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 2.1.
Copyright © 2016 Curt Hill Enterprise Resource Planning Systems ERPs Rule!
The Information Systems Development Processes Chapter 9.
Systems Acquisition Process Acquiring software The Business Perspective Copyright © 2016 Curt Hill.
Information Systems Development
Enterprise Resource Planning
Chapter 1: Introduction to Systems Analysis and Design
Systems Analysis and Design
Information Systems Development
Chapter 2 The Sources of Software
Chapter 2 The Origins of Software
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
King Saud University College of Engineering IE – 462: “Industrial Information Systems” Fall – 2018 (1st Sem H) Chapter 2 Information System.
Chapter 1: Introduction to Systems Analysis and Design
UNIT No- III- Leverging Information System ( Investing strategy )
Chapter 8 Information Systems Development & Acquisition
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Systems Development Process Developing our own software The Business Perspective Copyright © 2016 Curt Hill

Introduction Software development is not cheap! Large enterprises often have the both the resources and particular needs to develop software Smaller enterprises do not have this luxury Developing software means either: –Having a staff of IT professionals: developers, analysts and the like –Contracting with an outside group –Sometimes both Copyright © 2016 Curt Hill

Types of Software Customized Software –Tailored to unique needs –Problem specificity—pay only for what is needed Commercial-Off-the-Shelf (COTS) –Less costly than customized systems –Faster to obtain than customized systems –Of higher quality than most customized systems –Less risky than customized systems Copyright © 2016 Curt Hill

Examples There are numerous COTS that are available for purchase/lease Office –Microsoft Office –Open Office Business information systems –Intuit QuickBooks –Intuit Payroll –Intuit Inventory This barely scratches the surface Copyright © 2016 Curt Hill

Why Not Develop Software? The cost of software is large –The vendors may amortize this over thousands or millions of copies –Locally developed cannot Developers are generally the highest paid of the IT people Quality software takes time to develop –More often years than months Most COTS software has some degree of configuration Copyright © 2016 Curt Hill

Why Develop Software? The enterprise must have rather unique requirements to make the argument for developing it in-house or to contract for its development This is the normal case for Department of Defense and NASA –In most other examples the case is hard to make –Often it is about integrating with existing software Rest of this presentation assumes the case has been made Copyright © 2016 Curt Hill

Open Source Software One of the available assets is open source software This is software where all the source code is publicly available It may be downloaded and modified in any way desired Examples include the operating system LINUX and many databases including MySQL, MariaDB and most NoSQL databases –These can be quite good Copyright © 2016 Curt Hill

The Good and Bad Open Source software generally has lower costs to get running It may have higher maintenance costs It may also be a security hazard –The hackers can study the code as well There is no free support for free software –Numerous software companies sell support for consulting fees Many large companies do use Copyright © 2016 Curt Hill

Hybrid Approaches Often COTS software may be used with Open Source software or customized to meet requirements Many ERPs and CRMs use an Open Source database for data storage Sometimes a short and easy to develop program can be the bridge between the COTS and Open Source programs Many companies use all three: COTS, Open Source and home-brew Copyright © 2016 Curt Hill

System Development Very involved process –Full coverage is beyond the scope of this course –Actual development may vary dramatically from what book gives There are multiple tasks that must go on These are considered in the next screen The sequencing and organization of these steps and who does them varies wildly Copyright © 2016 Curt Hill

Tasks Systems planning and selection Systems analysis Systems design Systems implementation and operation Systems maintenance Copyright © 2016 Curt Hill

Planning and Selection Resources are limited so projects must be evaluated and selected Analysts gathers information and build the case Multiple approaches to selecting projects –Formal IS planning process –Ad-hoc planning process The business case role –Business cases for different projects compared –Multiple selection criteria Copyright © 2016 Curt Hill

Analysis Collecting Requirements –May be the most important part of systems development –Dictates how the proposed system should function Modeling Data –What data are needed –Modeled using entity-relationship diagrams Modeling Processes and Logic –Model the data flow –Model the processing logic Develop System Designs and Evaluate, Selecting One Copyright © 2016 Curt Hill

Design The system design chosen previously is now elaborated to where it could be built –Human–computer interface Point of contact between the user and the system Data entry and management forms –Databases and files –Processing and logic Modeled using one of many techniques –Models converted into code Copyright © 2016 Curt Hill

Implementation Convert design into a working system Software programming and software testing System conversion, documentation, training, and support –User and reference guides –User training manuals and tutorials –Installation procedures and troubleshooting suggestions Copyright © 2016 Curt Hill

Implementation Strategies Copyright © 2016 Curt Hill

Maintenance In the long run more is spent on maintenance than in the combined previous steps We expect a long lifetime, but the world continues to change Each change required triggers something like the entire previous process Copyright © 2016 Curt Hill

The List of System Development Methods –Waterfall – the one the book best describes Less than 20% of projects now use this –Prototyping –Spiral –eXteme Programmin –Scrum –Kanban –Rapid Application Development –Among others Copyright © 2016 Curt Hill

Outsourcing It may be determined that the enterprise’s IT staff is unable to do the project The possibility exists to contract this with an outside firm –There are numerous software houses that will take on this type of project Copyright © 2016 Curt Hill

Why? Software houses have an economy of scale –They may often produce better code This is their specialty –They should be more reliable, consistent and experienced An enterprise may wish to focus on core tasks and this may not be one of them IT may be having internal problems Copyright © 2016 Curt Hill

Outsource Management Managing an outsourced project is often more difficult –These are someone else’s people Good measures of performance need to be constructed and monitored Communication must be enhanced between the team and users Copyright © 2016 Curt Hill

Finally In general software development is an expensive process –Develop yourself –Contract for it to be developed This type of project requires unusual requirements in order to justify the expense We still need to consider system acquisition Copyright © 2016 Curt Hill