Calculating Task Set Selector (TSS)

Slides:



Advertisements
Similar presentations
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Advertisements

Software Process Models
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
1 Chapter 7 Project Scheduling and Tracking. 2 Write it Down! SoftwareProjectPlan Project Scope EstimatesRisksSchedule Control strategy.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Project Life Cycle Jon Ivins DMU. Introduction n Projects consist of many separate components n Constraints include: time, costs, staff, equipment n Assets.
Information Systems Development Lecture 2: the idea of the Life Cycle.
1 Introduction to System Engineering G. Nacouzi ME 155B.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Types of Risks 1.Project risks –Impact schedule and cost –Includes budgetary, schedule, personnel, resource, customer, requirement problems 2.Technical.
1 SOFTWARE LIFE-CYCLES Elements and Definitions. 2 Requirements System Design Detailed Design Implementation Installation & Testing Maintenance The WATERFALL.
Project Scheduling and Tracking
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
1 Project Scheduling and Tracking CIS 375 Bruce R. Maxim UM-Dearborn.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Initiating and Planning Systems Development projects
Chapter 2 Process: A Generic View
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Lecture 7 Project Scheduling and Tracking
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
Feasibility Study.
Software Project Management Lecture # 7. Outline Project Scheduling.
Software Engineering Management Lecture 1 The Software Process.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
Project Scheduling 1. Why Are Projects Late? An unrealistic deadline established by someone outside the software development group Changing customer requirements.
Lecture 18: Chapter 27 Project Scheduling
Project Scheduling & Tracking. Why Software Is Delivered Late? An unrealistic deadline Changing but unpredicted customer requirements Underestimation.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Project Life Cycle – Project Initiation © Ed Green Penn State University All Rights Reserved.
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
PROJECT SCHEDULING AND TRACKING
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Statement of Work Lecture. SOW The statement of work is the basis of the contract between the pro- poser and the customer, and is often incorporated into.
10 Stages Of the Engineering Design Process
Software Engineering Management
Chapter 34 Project Scheduling
Project Scheduling.
Project Scheduling and Tracking
Environment Assessment
RET Rules One of the following rules applies when counting RETs:
Software Engineering Lecture #41
For University Use Only
Software Life Cycle “What happens in the ‘life’ of software”
Software Project Management
McCall’s Quality Factors
What is project scheduling&tracking?
Change Control Process—I
Chapter 2 Process: A Generic View
Software Engineering Lecture #2
Software engineering Lecture 21.
Engineering Design Process
SE Tasks for a Concept Development Project
CLINICAL INFORMATION SYSTEM
Program Restructuring
Software Engineering Lecture #3
What is Software? Software is: (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures.
Chapter 27 Project Scheduling
Chapter 34 Project Scheduling
Software Engineering Lecture #29
Software Engineering II
Software Engineering Lecture #28
Presentation transcript:

Calculating Task Set Selector (TSS)

Recap

Software Engineering II Lecture 23 Fakhar Lodhi

New Development Concept Development Between 1-5 Reengineering Projects Enhancement Projects Maintenance Projects Adaptation Criteria Grade Weight Entry Point Multiplier Product Conc. New Dev. Enhan. Maint. Reeng. Size of product 1.2 1 Number of Users 1.1 Business Criticality Longevity 0.9 Stability of requir ements Ease of communication Maturity of technology Performance Constraints 0.8 Embedded / non - embedded Project Staffing 1.0 Interoperability Ree ngineering factors Task set selector

Adaptation Criteria Grade Weight Entry point multiplier Product New Development Size of product 2 1.2 1 2.4 Number of Users 3 1.1 3.3 Business Criticality 4 4.4 Longevity 0.9 2.7 Stability of requirements Ease of communication 1.8 Maturity of technology Performance Constraints 0.8 Embedded / non-embedded 3.6 Project Staffing 1.0 2.0 Interoperability Reengineering factors TSS 2.6

TSS Degree of Rigor < 1.2 Casual 1.0 – 3.0 Structured > 2.4 Strict The overlap in TSS values is intentional and it depicts that sharp boundaries are impossible to define when making task set selection. In the final analysis, the TSS value, past experience, and common sense must all be factored into the choice of the task set for a project.

Example – SE Tasks for a Concept Development Project Potential for new technology or new business idea is explored No certainty of applicability but the potential is there. Major tasks include: Concept scoping Preliminary concept planning Technology risk assessment Proof of concept Concept implementation Customer reaction to concept

Example – SE Tasks for a Concept Development Project Potential for new technology or new business idea is explored No certainty of applicability but the potential is there. Major tasks include: Concept scoping Preliminary concept planning Technology risk assessment Proof of concept Concept implementation Customer reaction to concept

Concept Scoping Sub Tasks or Activities Identify needs and benefits Define desired output/control/input Define the function/behaviour Isolation software elements Research availability of existing software Define technical feasibility Make quick estimate of size Create scope definition

Identify Needs and Benefits Meet with customers Identify needs and project constraints Establish project statement Milestone: project statement defined

Define desired Output/Control/Input Scope keyboard functions Scope voice input functions Scope modes of interaction Scope document diagnosis Scope other ‘Work Product’ functions Document OCI (Output Control and Input) FTR (Formal Technical Reviews) - review OCI with customer Revise OCI as required Milestone: OCI defined