The Tar Pit Ensnaring the Unsuspecting. The Entangling Tar or pitch traps even the largest of beasts. Today, the same level of precaution must be taken.

Slides:



Advertisements
Similar presentations
Robert Lockyer.
Advertisements

Chapter 2: Software Process
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
Project Estimation: Metrics and Measurement
THE TAR PIT BY FRANKLYN OMORUAN. What Is Tar Pit ? It describes software development as similar to a prehistoric tar pit, where great and powerful beasts.
“Not Fully Specified (Project) Objectives” CS524 – Software Engineering I Azusa Pacific University Professor Dr. Sheldon X. Liang Fall I 2007 Ernie Rosales.
BUS-119A Lecture #11 dbg SJSU 4/7/ Homework #2 is due today - “Effort” to produce a Product i.e.. Staffing - Complexity – key: the Number of interactions.
Lecture Notes 1/21/04 Program Design & Intro to Algorithms.
Organizational Design, Diagnosis, and Development Session 11 Organizational Diagnosis, I.
Kodu Trials Celebration 11 December 2009 Evaluation of the Trials Ian Phillips, I & J Management Services.
Effective Work Groups and Teams
Usability Teppo Räisänen
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
Development and Quality Plans
Design, Implementation and Maintenance
 Software Software  Program vs Software Products Program vs Software Products  Software Characteristics Software Characteristics  Software Crisis.
Lecture 3.
How a Small Change in Labor Rates Leads to A Large Change in Profits.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Effective C# 50 Specific Way to Improve Your C# Item 50 Scott68.Chang.
1 Software Construction Software Construction Chapter 1.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Topics Covered: Software requirement specification(SRS) Software requirement specification(SRS) Authors of SRS Authors of SRS Need of SRS Need of SRS.
SEMINAR ON :. ORGANISATION Organizations are formal social units devoted to attainment of specific goals. Organizations use certain resources to produce.
PLAN AND ORGANISE ASSESSMENT. By the end of this session, you will have an understanding of what is assessment, competency based assessment, assessment.
 What is a tar pit ?  From its original meaning, a tar pit is an accumulation that has acted as a natural trap into which animals have fallen and sunk.
CSC 354 – Software Engineering, Spring 2013, Week 2 Mythical Man-Month Ch. 1-5 Tar Pit, Mythical Man-Month, Surgical Team, Aristocracy / Democracy & System.
OHTO -99 SOFTWARE ENGINEERING “SOFTWARE PRODUCT QUALITY” Today: - Software quality - Quality Components - ”Good” software properties.
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 3 HCI and Interactive Design.
Group 4May Final Design Presentation DUNA* (Dynamic Urban Navigation using A*) Name of Team: A*
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 8 Project Resource Management Resource Planning.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
The Software Development Life Cycle. Software Development SDLC The Software Development Life-Cycle Sometimes called the program development lifecycle.
Process Assessment Method
MIS 673: Database Analysis and Design u Objectives: u Know how to analyze an environment and draw its semantic data model u Understand data analysis and.
ISO NON-CONFORMANCE, CORRECTIVE AND PREVENTIVE ACTION.
Historical Aspects Origin of software engineering –NATO study group coined the term in 1967 Software crisis –Low quality, schedule delay, and cost overrun.
Systems Analysis and Design in a Changing World, Fourth Edition
Topics Covered Phase 1: Preliminary investigation Phase 1: Preliminary investigation Phase 2: Feasibility Study Phase 2: Feasibility Study Phase 3: System.
Task Analysis Strategies and Practices Access to Develop Students with Low Functioning Autism in Vocational Skills Supattra W. Andrade, M.A. Jittirat Tadthiemrom,
SSC SI Data Processing Pipeline Plans Tom Stephens USRA Information Systems Development Manager SSSC Meeting – Sept 29, 2009.
Chapter 9 Putting together a complete system. This chapter discusses n Designing a complete system. n Overview of the design and implementation process.
Software Development Problem Analysis and Specification Design Implementation (Coding) Testing, Execution and Debugging Maintenance.
Digital Libraries1 David Rashty. Digital Libraries2 “A library is an arsenal of liberty” Anonymous.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
Advanced S/w Eng - s/w productivity issues 1 Software Productivity Issues Why do software projects fail? Advanced Software Engineering COM360 University.
Nic Shulver, Welcome to Principles of Software Engineering Tutor: Nic Shulver Web site and Blackboard presence 100% coursework,
Managed by UT-Battelle for the Department of Energy SCL Vacuum Control System Upgrade Derrick Williams
Advanced Software Engineering Lecture 4: Process & Project Metrics.
Cooperation & Interoperability Architecture & Ontology.
State of Georgia Release Management Training
The Tar Pit The Mythical Man-Month Frederick P. Brooks, JR. Chapter 1.
Copyright 2010, The World Bank Group. All Rights Reserved. QUALITY ASSURANCE AND EVALUATION Part 1: Quality Assurance 1.
Lesson Outline: Explore To broaden the students understanding of the range of roles and jobs available in the working world by exploring the career pathway.
Chapter – 8 Software Tools.
FACTORS AFFECTING THE EFFICIENCY OF DATA PROCESSING SYSTEMS.
Lecture 6 Title: Project Cost Management MIS 434.
McDonough Bolyard Peck Educational Series Building Commissioning Presented by: Doug Wrenn Steve Baxter July
The Real Cost of Late- Stage Change Orders Business Management & Information Technology Brief.
Module 5: Communication Plan and Process for Addressing Barriers
DOCUMENTATION DEVELOPMENT LIFE CYCLE (DDLC)
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Analysis and Understanding
Software life cycle models
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
CMSC 345 Programming.
12 Safe Maintenance Rules
  Use of Dynamic Traffic Assignment in FSUTMS in Support of Transportation Planning in Florida FDOT Research #BDK80 Task Work Order No June.
Presentation transcript:

The Tar Pit Ensnaring the Unsuspecting

The Entangling Tar or pitch traps even the largest of beasts. Today, the same level of precaution must be taken when programming large-system projects.

The Value of a Duo’s Work Garage duos program programs that exceed the capabilities of a large team? So why don’t have organizations filled with programming duos? The better question is, what are those garage geeks making?

The Value of a Duo’s Work Program Programming System (Interfaces System Integration) Programming Product (Generalization, Testing, Documentation, Maintenance) Programming Systems Product X3 X3 According to Brooks the Value of the garage geeks’ work is limited. The program is generally restricted to being ran by the author on the system it was developed. Achieving a more useful object is more costly.

The Programming Product Program Programming System (Interfaces System Integration) Programming Product (Generalization, Testing, Documentation, Maintenance) Programming Systems Product X3 X3 The Programming Product is a program that can be repaired, tested, and expanded by any person. To become generalized the programming product must be written in such a format. The form and range of the inputs must be generalized as much as the algorithm permits. It must be thoroughly tested. Finally, it must have thorough documentation.

The Programming System Program Programming System (Interfaces System Integration) Programming Product (Generalization, Testing, Documentation, Maintenance) Programming Systems Product X3 X3 A Programming System is a collection of components that collaborate in a function so that the assemblage is considered as a facility for large tasks. This program must conform its input’s and output’s syntax and semantics with the defined interfaces. The consumed resources of the program must be tamed to the level desired. The final requirement is that the program must be tested with all possibilities that it may encounter with the system components.

The Programming System Product Program Programming System (Interfaces System Integration) Programming Product (Generalization, Testing, Documentation, Maintenance) Programming Systems Product X3 X3 The Programming Systems Product is the final product, and the most desired. However, the cost, as estimated by Brooks, could be as much as 9 times the original cost of the program. This is the most intended object for any system programming efforts.

The Fun Part Why is programming enjoyable for people? Just like a child enjoys playing with his LEGOS, adults enjoy building things. Making things that are useful makes one feel that they can make an impact in the world. The fascination for complexity and watching things work makes it interesting. The ability to constantly learn. Being able to produce things in a moldable environment.

The Downside

Perfection is required. The objectives are set by other sources. Rarely is one given the authority needed to sufficiently do one’s responsibilities. The interdependence of programs creates frustrating situations. The tedious and irritating process of debugging. Program antiquation is an inevitable and soon approaching disappointment.