1 Business Aspects of Software Engineering SWE 513.

Slides:



Advertisements
Similar presentations
Uriel Corporation One Westbrook Corporate Center Suite 300 Westchester, IL USA (708) Call to arrange fax.
Advertisements

1 Software Engineering II The Business Aspects of Software Engineering.
Financial Management F OR A S MALL B USINESS. FINANCIAL MANAGEMENT 2 Welcome 1. Agenda 2. Ground Rules 3. Introductions.
Lecture 17 Chapter 9 Managing IT Outsourcing. 2 Final Exam Outline 12 – 3pm, Wednesday June 14 Half short and long answers on theory and principles from.
Read to Learn The four main ways to become a business owner and the advantages and disadvantages of each The different forms of legal business ownership.
CS 5150 Software Engineering
CS CS 5150 Software Engineering Lecture 28 People 3.
1 CS 501 Spring 2007 CS 501: Software Engineering Lecture 25 Delivering the System Business Considerations.
Software Development Contracts and Legal Issues Cost plus Fixed price Combined.
1 CS 501 Spring 2008 CS 501: Software Engineering Lecture 23 People 1.
CS CS 5150 Software Engineering Lecture 27 People 3.
CS 501: Software Engineering Fall 2000 Lecture 7 Management II Business and Legal Aspects of Software Engineering.
3.1 Sources of Finance Chapter 18 Part 1.
Computer Fundamentals
Frequently Asked Questions. No, in fact DOCTUS considers itself a strategic extension of your organization. Hence, we deliver the work the way you do.
COMP 6005 An Introduction To Computing Session Two: Computer Software Acquiring Software.
WHAT YOU NEED TO KNOW ABOUT JOB ROLES DMC U1 1.1.
OWN A FRANCHISE OR START A BUSINESS
SELECT A TYPE OF OWNERSHIP
Entrepreneurial Mindset and Main Topics in a Sustainable Business Plan By Gonzalo Manchego Business Consultant.
McGraw-Hill/Irwin Copyright © 2009 by the McGraw-Hill Companies, Inc. All rights reserved.
The Multinational Corporation and Globalization
The Purchasing Function
Fees and Pricing (Research and Setting) Virtual Business Business Management & Administration Copyright © Texas Education Agency, All rights reserved.
FEASIBILITY STUDY Aspects of Operating a Business
CS CS 5150 Software Engineering Lecture 26 The Business of Software Development.
SMALL BUSINESS RESOURCE GUIDE CHECKLIST FOR GOING INTO BUSINESS.
Being a Business Owner Section 4.2.
SELECT A TYPE OF OWNERSHIP
1 The George Washington University School of Engineering & Applied Science Department of Electrical & Computer Engineering Engineering Economic Analysis.
Categories of Software
© Pearson Education Copying permitted for purchasing institution only. This material is not copyright free. Functional areas Unit 1: Investigating.
Project Evaluation UNIT 2 Software Project Management.
Software – Acquisition & Testing. ICT5 How to acquire software There are several options: The software may be written by the end-user; A specialist department.
Ravi Block Application Software Module 1.8.
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.
Business Plan and Financials
CS 501: Software Engineering Fall 1999 Lecture 19 Management II Business and legal aspects of software engineering.
Types of business ownership Chapter 4. Academic Preparation  To take business classes in high school  To go to college and get a degree in business.
Accounting Information System By Rizwan Waheed M.Com 710.
Intuit Canada ULC How to Implement QuickBooks Training in your Practice.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 7 Business Aspects of Software Engineering.
Lecture 28. Chapter 17 Understanding the Principles of Accounting.
Select a Type of Business Chapter #4. Way to be a Business Owner Purchase an Existing Business Enter a Family Business Franchise Ownership Starting Your.
Chapter 3 Financial Management Part 2 BCN 4772 Summer 2007.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 24 Delivering the System.
Cost Management Session 3. Overview Theory Exercise: 1.39; 1.42; 1.50;
CS CS 5150 Software Engineering Lecture 24 People 2.
Introduction The dilemma for companies is to find tools that allow the evaluation of managers at all levels in the organization. How would the evaluation.
3.1 Sources of Financing Chapter 18 Part 2.
The Decision Maker. Managing a Profitable Company.
POB 4.01 PARTS 1 & Understand financial planning.
Chapter 9 The People in Information Systems. Learning Objectives Upon successful completion of this chapter, you will be able to: Describe each of the.
1 A Seminar On Pharmaceutical Outsourcing A Seminar On Pharmaceutical Outsourcing.
Business Administration Unit 5 Financial Management Chapter 15 Financial Records in a Business.
LEARNING AIM A: Understand the costs involved in business and how businesses make a profit.
CS 501: Software Engineering Fall 1999 Lecture 22 (a) Managing the Software Process (b) Software Reuse.
FINANCIAL RESOURCES MANAGEMENT
Public Management Information Systems Financing & Contracting Out Tuesday, June 21, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -
 The costs of operating a business are often called overhead expenses.
Enterprise Processes and Systems MIS 2000 Instructor: Bob Travica Updated 2016 Class 16.
ADMINISTRATIVE STRUCTURE OF A COMPUTER CENTRE. The administrative structure is being organized in such a way that a skilled professional personnel is.
The Advertising Agency, Media Services, and Other Services
CS 5150 Software Engineering
CS 501: Software Engineering
Cornerstones of Managerial Accounting, 6e
Decentralization May 27, 2009 Chapter 10: Decentralization.
Decentralization, Profitability and ROI
How to Create a Budget.
Presentation transcript:

1 Business Aspects of Software Engineering SWE 513

2 High Level Decision Making Big software projects are of strategic important for organizations The senior management have a duty to understand the strategic decisions, the cost options, and the risks. Senior personnel requirement: individual who is familiar with both the strategic business aspects and the computing aspects of projects, e.g., Chief Information Officer Consultant Does not require detailed technical expertise

3 Product Manager When software is a product or part of a product, somebody must look at it as a product Product manager: Sees software as a product with many aspects: Function -- What does it do? Market -- Who is it for? Sales -- What price, advertising, sales channels? Packaging -- What media, bundling, packaging, documentation? Legal -- What licenses, legal protections, etc.?

4 In-house Computing Departments Organization Central computing department, reporting through a Chief Information Officer Decentralized model with computing distributed across the organization, reporting to operational units Expertise Full in-house design and software development expertise Outsourcing with project management in-house Even if development is contracted to consultants, software houses, etc., organizations need considerable in-house expertise to oversee the work.

5 Business Models: Bespoke Software Software is tailored to specific environment Very large applications (e.g., air traffic control) Small-scale, highly specific applications (e.g., BU campus access cards) Development options Software is written in-house Software is written by contractor Product may be owned by supplier or customer. Maintenance may be in-house or by contractor.

6 Business Models: Package with Modifications Software house develops general purpose package Client Licenses package Source code is modified for client's specific needs Business consideration Modifications may be by software house or in-house team Maintenance may be by software house or in-house team Legal issues include: access to source code, ownership of modifications, avoiding being locked-in to a supplier Examples: Corporate pay-roll systems, accounting systems for small businesses, etc.

7 Business Models: Package Without Modifications Package Licensed in Binary Form Only Package typically has many options, including configuration options Package may be a self-contained application or may be designed as a component to incorporate in applications Legal considerations: usually there is a clear distinction between the package (license from supplier) and application. Examples: Database systems, mathematical packages, etc.

8 Business Models: Embedded Systems Software bundled with hardware product Product is seen by the user as a hardware product, even if the software development is the major part of the cost Examples: Global Positioning System, automobile engine control, PalmPilot

9 Outsourcing Concept: Contract with software house to develop software for an organization. Benefits: Software house may be better organized to recruit staff, and manage projects. Clear visibility. No need to build an in- house team for a single project. Small organization cannot have all the expertise to cover a complex project. Disadvantages: Software house may not have the same goals as the organization (e.g., incentive to prolong project, to build software that can be used in other projects). Organizations need considerable in-house expertise to oversee the work. Must not over-estimate the expertise of the software house.

10 Free-Lance Software Development You and a few friends create a company to develop software. You are offered a contract to write bespoke software. How much should you charge per hour? You plan to work 40 hours a week for 50 weeks of the year and want to earn $50,000. Hourly rate = $50,000 / (40 x 50) = $25 But...

11 Free-Lance Software Development Salary$50,000 Benefits$15,000 Rent, equipment, etc.$10,000 Fees, services, etc.$15,000 Travel and misc.$10,000 TOTAL EXPENSE $100,000 Hours worked 2,000 less administration 400 less marketing 350 BILLABLE HOURS 1,250 Hourly rate = $100,000 /1,250 = $80

12 Free-Lance Software Development You MUST have a contract with the customer. It may be a simple letter or a complex agreement. What should it contain? Are you being paid by the hour? Or by completion of the task? What acceptance tests will be done? Who decides when the job is done? Who owns the software? What licenses does the other party have? Who provides hardware, software that is required, supplies, etc.? WHEN WILL YOU GET YOUR MONEY!

13 Fixed and Variable Cost: Packaged Software Example: The initial development cost of a software product is $1 million. The cost of packaging and distribution of each copy is $5. Technical support costs average $15 per copy. The package sells for $200 per copy. Fixed cost = $1 million Variable cost = $20

14 Fixed and Variable Costs: Profit or Loss $1.5M $1.0M $0.5M Unit sales 2,5005,0007,500 Revenue Costs

15 Profit or Loss? If you sell 7,500 copies do you make a profit of $350K? Did you borrow money to cover the start-up period? How much interest did you pay? What about taxes? Cash flow When will you be paid (always late)? When do you have to pay your bills? Risk What extra costs do you have if the product is a year late? What if you only sell 5,000 copies? If you increase the price, does your revenue go up or down?

16 Unorthodox Business Models: Shareware Shareware Producer writes a software package. Distribution is open, but requests a fee, e.g., $50. Users who pay the fee may get a small benefit, e.g., no message when they start up the software. Some people have received substantial revenue this way.

17 Unorthodox Business Models: Open Source Examples: Linux, Apache, Perl Market leaders High quality General model Shared development A central developer provides overall coordination Distribution of source code is completely open

18 Notes on Open Source Software may be open source, but packaging and services can be profitable businesses (e.g., IBM Linux). For more information about open source software, see: Many open source software projects are managed on the SourgeForge system: Open source software development and distribution is particularly suitable for organizations such as universities who develop software for the public good.