Copyright Joe Kasser 19991 Dr. Joseph Kasser UMUC On-line Requirements Workshop.

Slides:



Advertisements
Similar presentations
Integrated Project Management IPM (Without IPPD) Intermediate Concepts of CMMI Project meets the organization Author: Kiril Karaatanasov
Advertisements

Market Research Ms. Roberts 10/12. Definition: The process of obtaining the information needed to make sound marketing decisions.
Project Scope Management (Day 2)
Heather Woltman, Renée Nossal, Nathalie Gougeon, & Dr. Lise Bisnaire 7 th Annual CANS Conference Baltimore, Maryland May Evaluation of the Connections.
Salome Heyward & Associates Conference Services Program Accessibility And Emerging Technology April , 2014 Presented by Salome Heyward, JD Program.
©2007 by the McGraw-Hill Companies, Inc. All rights reserved. 2/e PPTPPT.
1 Chapter 2: Product Development Process and Organization Introduction Importance of human resources: Most companies have similar technology resources.
A A A N C N U I N F O R M A T I O N T E C H N O L O G Y : IT OPERATIONS 1 Problem Management Jim Heronime, Manager, ITSM Program Tanya Friehauf-Dungca,
1 Quality Management Standards. 2 THE ISO 9000 FAMILY ISO 9000: 2005 Identifies the fundamentals and vocabulary for Quality Management Systems (QMS) ISO.
The ISO 9002 Quality Assurance Management System
Information and Decision Support Systems
1 Adaptive Management Portal April
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Measurement & Analysis Adeel Munir Butt Muhammad Adnan Nasir Muhammad Shoaib Khan.
1 Input: capturing and assembling elements that enter the system to be processed. Example: Raw material, data and human effort must be organized for processing.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems Introduction to Hewlett Packard (HP) Application Lifecycle Management.
Writing Reports and Proposals
Compilation and interpretation of primary and secondary sources of information. The integration of different sources will consolidate the write up of the.
Project Lifecycle Section 6 - Closeout. Project Manager’s Role During Project Close-Out  Ensure that all project deliverables have been completed and.
Managing Project Quality
What is Business Analysis Planning & Monitoring?
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Slide 1 D2.TCS.CL5.04. Subject Elements This unit comprises five Elements: 1.Define the need for tourism product research 2.Develop the research to be.
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Old.libqual.org What will ARL do for you? What will you do? January 2005 Shrivenham, UK.
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Copyright © 2010 Pearson Education InternationalChapter Writing Reports and Proposals.
Design FRAME problem solving with the engineering design process F R A M E TEXAS TECH UNIVERSITY T-STEM Center © 2009 Texas Tech University T-STEM Center.
Karen Herter (HMG) Mike Langley (DGS) April 15, 2008 Portfolio Manager for California State Buildings Meeting the Requirements of Executive Order S
Technical Writing 1ST Lecture.
Communication 2 Report Writing.
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.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Principles of Information Systems, Sixth Edition Information and Decision Support Systems Chapter 10.
Michael Campe U.S. Army Aviation and Missile Command NDIA TID Technical Information Division Symposium Royal Sonesta Hotel, New Orleans, LA August 2003.
Capturing the requirements  Requirement: a feature of the system or a description of something the system is capable of doing in order to fulfill the.
Tracking national portfolios and assessing results Sub-regional Workshop for GEF Focal Points in West and Central Africa June 2008, Douala, Cameroon.
Project Proposal. What is Project Proposal?  A project proposal is written, to make an offer and to try to convince a supervisor or a future customer.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Access to Radiology Information Cor Loef Co-chair IHE Radiology Technical.
Requirement Engineering. Recap Elaboration Behavioral Modeling State Diagram Sequence Diagram Negotiation.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
The Project Plan Plan Your Work, then Work Your Plan
Ch7: Project Monitoring and Control  To reduce differences between plan and actual in the 3D space of T/C/P.  Best utilization of organization’s primary.
Working with your archive organization: Broadening your user community Robert R. Downs, PhD Socioeconomic Data and Applications Center (SEDAC) Center for.
Copyright 2010, The World Bank Group. All Rights Reserved. Principles, criteria and methods Part 1 Quality management Produced in Collaboration between.
Session 6: Data Flow, Data Management, and Data Quality.
B U D I L U H U R U N I V E R S I T Y POST GRADUATE PROGRAM MAGISTER ILMU KOMPUTER (M.Kom) IS PROJECT MANAGEMENT.
 System Requirement Specification and System Planning.
SOFTWARE TESTING TRAINING TOOLS SUPPORT FOR SOFTWARE TESTING Chapter 6 immaculateres 1.
The System Development Life Cycle
Project Management PTM721S
Building Business Transformation Capabilities Our perspective on the building blocks, structure and critical success factors to impact change Gillian.
Sample Fit-Gap Kick-off
CS4311 Spring 2011 Process Improvement Dr
Working with your archive organization Broadening your user community
Software Requirements analysis & specifications
Software Quality Engineering
Presented By: <Names> <Team Name> <Date>
Software Quality Engineering
The Strategic Planning Process
Distribution Statement
Guidance for PALS Proposers Day Poster
Guidance for PALS Proposers Day Poster
Distribution Statement
Distribution Statement
DMAIC STANDARD WORK TEMPLATE
DMAIC STANDARD WORK TEMPLATE
Software Reviews.
Presentation transcript:

Copyright Joe Kasser Dr. Joseph Kasser UMUC On-line Requirements Workshop

Copyright Joe Kasser Objectives Primary –Learn the importance of good requirements –Learn how to evaluate requirements –Understand the difficulty of writing effective requirements Secondary –Learn to collaborate in an on-line environment

Copyright Joe Kasser n The purpose of a document n Requirements n Requirements for requirements n Attributes of good documents n Metrics for documents n Defective requirements n Guidelines for workshop n Exercise (duration of the semester) n Summary and reporting Workshop Agenda

Copyright Joe Kasser The purpose of a document n To communicate something to someone n SOW - communicates the government's needs to potential offerers n PROPOSAL - communicates to the government, that n we understand the need AND n have the optimal (most cost effective and best technical) solution n REQUIREMENTS - Communicate to the designer what is to be designed n CHANGE REQUEST - communications a change

Copyright Joe Kasser Requirements Purpose –Communicate to the designer what is to be designed Formats –document text format –report from the requirements database –graphic format Types –extrinsic –intrinsic

Copyright Joe Kasser Where do requirements come from? * The customer/user Extrinsic sources Lessons learned documents Analysis and extrapolation Government mandates Other places * Kasser, J.E., Applying TQM to Systems Engineering, p210.

Copyright Joe Kasser Requirements drive design and test Requirements Design plans & documents Designs Test Plans Test Procedures Tests Manuals Reports

Copyright Joe Kasser Sample requirement DADS shall monitor and provide reports (to the operator) on all requests for DADS products and services. This capability shall include recording the name and organization of the requester, the product or service requested, the date and time of the request, the service priority, the current disposition of the request, and the date and time of service completion.

Copyright Joe Kasser Better requirement DADS shall monitor and provide reports to the operator about the state of transactions in the system. This capability shall contain the following: a. the name and organization of the requester b. the product or service requested c. the date and time of the request d. the service priority e. the current disposition of the request f. the date and time of service completion.

Copyright Joe Kasser Requirement or wish? DADS shall statistically monitor the integrity of data stored in the archive and safe-store in order to detect degrading media. Define the following terms Statistically monitor Integrity Degrading media

Copyright Joe Kasser Requirements for Requirements n Shall be n Complete n Testable n Achievable n Relevant n Grouped n Specific n Traceable n Shall not be n Vague n Overlapping n Redundant n Shall not use n including n for example n etc. n should

Copyright Joe Kasser Attributes of good documents n Complete n Correct n Concise n Organized n Unambiguous n Pertinent n Customer's language

Copyright Joe Kasser Metrics for documents n Document type specific n Qualitative basis n the presence of characteristics of good documents n Quantitative n RATIO of number of defects to opportunity for defects n Quality n Producing the product to specifications in the most cost effective manner

Copyright Joe Kasser Guidelines for the workshop Each person –reviews a requirements document –Counts number of requirements –Counts number of defective requirements –Posts individual counts in requirements workshop conference Discuss in team study groups Summarize into team count Post team count in requirements workshop conference Discuss in requirements workshop conference

Copyright Joe Kasser Summary and reporting