School of Business Administration Chap 3 Engineering of Software; Software Engineering Spring Term 2017 Marymount University School of Business Administration Professor Suydam Week 2 Chap 3 Engineering of Software; Case Study 1 (CS1)

Week 2 Class Agenda Review Case Study Assignment Examples Instruction on: SRS Template, PowerPoint, Visio Individual Team Discussion Discussion of Mini-Projects Chapter 3 Review

Case Study Requirements A & B – Use SRS Template This assignment is the product of ALL team members and contains no Plagiarism.

Case Study Requirement C – Preliminary Project Plan in Visio

Case Study Requirement D – PowerPoint

Engineering Software

Software Engineering As size and complexity of software projects increased, so did the number of failed projects “Engineering” Software was thought to be the cure: Put some discipline into “programming” ! Do more than just coding/programming! ‘Study’ (model/measure), ‘Understand’ (analyze), and ‘Improve’ (change) this field! Chaos Report (1995) sampled some 300 software projects and reported that only about 16% of those projects “completed,” “on-time,” and “within-budget” ! That is 84% of projects failed! Chaos Report (2009) stated that software projects have improved with 32% “completed,” “on-time,” and “within-budget.” That is still 68% of projects-failure!

Software Project Success & Failure Factors (Chaos & Capers Jones Report) Profiling attributes for projects that “succeeded”: User Involvement Executive Management Support Clear Requirements Proper Planning Profiling attributes for “challenged” (completed & operational – but over-budget and over-time-estimate) Lack of user input Incomplete user requirements and specification Changing requirements and specifications Profiling attributes for “impaired and ultimately cancelled” Incomplete requirements Lack of user involvement Lack of resources Code errors : 38.33% Design errors : 24.17% Documentation errors : 13.33% Requirements errors : 12.50% Bad-fix errors : 11.67%

Software Engineering (Tsui and Karam) Software Engineering is a broad field that touches upon all aspects of a) developing and b) supporting a software system, spanning across the following key areas: 1. Technical and business processes 2. Specific methodologies and techniques 3. Product characterization and metrics for measurements 4. People skills and team work 5. Project coordination and management There is no equivalent “professional engineer” (PE) designation for software engineers, yet. Except in Texas where the board of professional engineers adopted software engineering as a specific discipline under which en engineering license may be issued.

IEEE-CS/ACM Version 5.2 Report 8 principles** for ethics and professional practices in software engineering Software engineers shall: act consistently with the public interest act in a manner that is in the best interest of their client and employer, consistent with the public interest ensure that their products and related modifications meet the highest professional standards possible maintain integrity and independence in their professional judgment subscribe to and promote an ethical approach to the management of software development and maintenance advance the integrity and reputation of the profession consistent with the public interest be fair to and supportive of their colleagues participate in lifelong learning regarding the practice of their profession and shall promote an ethical approach to the practice of the profession.

Summary and Quiz Questions

Preparation for Week 3

Chapter 3 Review Questions 1. List two key reasons that have caused both software project successes and failures.   Ans: Some reasons that impact software project success and failures include: amount of user involvement clarity of requirements proper planning and changes to requirements Page: 43, 51 2. From the definition of software engineering, list three areas that software engineering must touch upon. Ans: Software engineering touches on (see left side bar page 45): technical and business processes specific methodologies and techniques product characteristics and metrics people, skill, and team work project coordination and management Page: 45

Chapter 3 Review Questions 3. List two of the three strategies cited by the 2004 US General Accounting Office report as key to ensuring delivery of successful software.   Ans: 2004 US General Accounting Office report cites the following as key to ensuring successful software delivery. a. focused attention on software development environment b. disciplined development process c. methodical usage of metrics to gauge cost, schedule, and other performance targets Page: 44 4. When and where was the term software engineering first introduced? Ans: The term, software engineering, was first introduced in 1968 at the NATO conference in Germany to mimic the existing, traditional engineering disciplines. Page: 45 5. What are the eight principles for software engineering code of ethics recommended by the IEEE-CS/ACM Version 5.2 joint task force report? Ans: The IEEE-CS/ACM Version 5.2 joint task force report recommended 8 principles for software engineering code of ethics. (These are listed on page 47 of the text book) They range from acting consistently with the public interest to continuous and lifelong learning of the practices of software engineering Page: 47

Chapter 3 Review Questions 6. What is meant by the term principles of software engineering?   Ans: Principles of software engineering, different from principles in physics or other engineering discipline, are rules and assumptions derived from extensive observations and past experiences in the field of software development and software support. They are not all “proven” or “verified” with experiments. Page: 46 7. Can a software engineer become a certified Professional Engineering (PE)? Explain. Ans: No, at this time a software engineer cannot become a professional engineer (PE). The professional engineering certification process does not exist for software engineers. The state of Texas has initiated an effort to certify software engineers, but it is still under study. Page: 4