The Features of a Product or System

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Advertisements

W5HH Principle As applied to Software Projects
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
SE 555 Software Requirements & Specification Requirements Management.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
The Vision Document 1. Importance of a Vision Document  It describes the application in general terms, including descriptions of the target market, the.
Capability Maturity Model
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
COMPGZ07 Project Management Presentations Graham Collins, UCL
N By: Md Rezaul Huda Reza n
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Requirements Traceability: Planning, Tracking and Managing Requirements Presenter: Paula R. Maychruk, BV/TEd., CAPM, CBAP.
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.
CIS 499 Senior Seminar Introduction to IT project management.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Pre-Project Components
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
CSC444F'06Lecture 101 Feature Tracking. CSC444F'06Lecture 102 Feature Tracking Keeping track of all the features that have been requested. Keeping track.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
1 Text Layout Introduction (1-4) Team Skill 1 – Analyzing the problem (5-7) Team Skill 2 – Understanding User and Stakeholder Needs (8-13) Team Skill 3.
State of Georgia Release Management Training
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Establishing Project Scope 1. Factors Affecting Project Scope  The functionality that must be delivered to meet the user’s needs  The resources available.
Team Skill 2 Understanding User and Stakeholder Needs The features of a Product or System (9)
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
1 Team Skill 4 Managing the scope Noureddine Abbadeni Al-Ain University of Science and Technology College of Engineering and Information Technology Based.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Change Request Management
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Continuous Improvement Project (A Guideline For Sponsors)
Software Configuration Management
Software Project Configuration Management
Project Management with VSTS
The Vision Document Group members: Zainab BSEF07M025 Noreen BSEF08M021
Managing the Project Lifecycle
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Principles of Information Systems Eighth Edition
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Project Initiation & Planning
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
TechStambha PMP Certification Training
Configuration Management (managing change)
School of EE and Computer Science
Software Project Planning &
MGMT 404 Education for Service-- tutorialrank.com
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
TPF-5(181) Research Management Database Business Analysis
Unit4 Customer Portal Submitting & Managing Cases.
Project Management Complexity, Risks, Failure and Technology
Phase 1 Tollgate Review Discussion Template
Program Documentation
KEY PROCESS AREAS (KPAs)
Capability Maturity Model
Feature Tracking CSC444F'07 Lecture 9.
Capability Maturity Model
Main S+D Provisions of the WTO-Agreement on Trade Facilitation
CS 426 CS 791z Topics on Software Engineering
CS 426 CS 791z Topics on Software Engineering
Business Planning Meeting Periodic Business Review
Periodic Accounting Review Periodic Revenue Reconciliation
Marketing Planning Meeting Periodic Marketing Review
Marketing Planning Meeting Periodic Marketing Review
Periodic Workflow Review
Project Name Here Kick-off Date
Presentation transcript:

The Features of a Product or System

Getting Better Product Definitions Requires going out and getting them Developers must play an active role in requirements eliciting The entire team needs to be involved in the process

Stakeholder and User Needs A stakeholder need is: a reflection of the business, personal, or operational problem (or opportunity) that must be addressed in order to justify consideration, purchase, or use of a new system For example, “I need easier ways to understand my inventory”

Features A feature is: a service the system provides to fulfill one or more stakeholder needs. Features are a convenient way to describe functionality without getting bogged down in detail. They are high-expressions of system behavior.

Examples of Features Application Domain Example of a Feature Elevator control system Manual control of doors during fire emergency Inventory control system Provide up-to-date status of all inventoried items Defect tracking system Provide trend data to assess product quality Payroll system Report deductions-to-date by category Home lighting automation system (HOLIS) Vacation settings for extended away periods Weapon control system Minimum of two independent confirmations of attack authorization required Shrink-wrap application Windows XP compatibility

Managing Complexity Abstract features to a high enough level that a maximum of 25 – 99 are identified (preferably < 50). These features can be elaborated as necessary into detailed software requirements. Identify each feature as: “Defer to a later release” “Implement immediately” “Reject entirely” “Investigate further”

Attributes of Product Features Attributes are data elements that provide additional information about the feature. They are used to relate the feature to other types of project information. Attributes can be use to track, prioritize, and manage the status of features.

Attributes of Features Description Status Tracks progress during definition of the project baseline and subsequent development. Example: Proposed, Approved, Incorporated status states. Priority/benefit Assists in managing scope and determining priority. All features are not created equal. Ranking by relative priority or benefit to the end user opens a dialogue between stakeholders and members of the development team. Example: Critical, Important, Useful rankings. Effort Helps establish realistic schedules, goals, and costs. Estimating the number of team- or person-weeks, lines of code or function points, or just the general level of effort helps set expectations of what can and cannot be accomplished in a given time frame. Example: Team months, or Low, Medium, High levels of effort. Risk Indicates a measure of the probability that the feature will cause undesirable events, such as cost overruns, schedule delays, or even cancellation. Example: High, Medium, Low risk level.

Attributes of Features (Cont’d) Description Stability Reflects a measure of the probability that the feature will change or that the team’s understanding of the feature will change. This attribute helps establish development priorities and determine those items for which additional elicitation is the appropriate next action. Example: High, Medium, Low stability. Target release Records the intended product version in which the feature will first appear. When combined with the Status field, your team can propose, record, and discuss various features without committing them to development. Example: Version 2.3 Assigned to Indicates who will be responsible for implementing the feature. In many projects, features will be assigned to “feature teams” responsible for further elicitation, writing the software requirements, and perhaps even implementation. Reason Helps track the source of the requested feature. For example, the reference might be to a page and line number of a product specification or to a minute marker on a video of an important customer interview.