Reviews mae, fall 11. Review What: – Have skilled people assess your work –Requires that you have work product that is reviewable Why: – Find problems.

Slides:



Advertisements
Similar presentations
© Crown Copyright (2000) Module 3.1 Evaluation Process.
Advertisements

Baldrige National Quality Program 2003 Baldrige National Quality Program The Site Visit Process and Evaluating Site Visit Issue Worksheets.
The Re-Start Meeting Warren County School Strategic Planning Process Action Team Leaders September 25, 2013.
Ensuring that building products meet code requirements ICC Evaluation Service, Inc. The ICC-ES Evaluation Committee conducts open public hearings on proposed.
More CMM Part Two : Details.
Change Control Change is inevitable - how to manage it?
Scoping in the EIA process Proposal Identification Screening
Internal verification and external standards moderation.
Exec Handover Training Chairing Skills
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
1 MANUFACTURING AND PRODUCTION OF BIOLOGICAL PRODUCTS (ERT 455) HAZARD ANALYSIS AND CRITICAL CONTROL POINT (HACCP) SYSTEM Munira Mohamed Nazari School.
Software Testing and Quality Assurance
CS 5521 Configuration Management the problem Not a simple task! –Different versions of software usually is in the field during the life cycle –Different.
Innovation Leadership Training Day Four Idea Evaluation February 20, 2009 All materials © NetCentrics 2008 unless otherwise noted.
SE 555 Software Requirements & Specification Requirements Validation.
High Level: Generic Test Process (from chapter 6 of your text and earlier lesson) Test Planning & Preparation Test Execution Goals met? Analysis & Follow-up.
Avoiding Common Project Management Pitfalls – A Guide for Super PMs Yvette Soliz Rivers, PMP Director, Project Management November 14, 2012 Disaster Averted!
Configuration Management
About Waterloo website Project report June Outline Overview of process Project deliverables Lessons learned.
Baltic Dental Meeting Palanga Dana Romane The Patient in the Centre – Patient’s Involvement in the Treatment Process, Full Awareness and.
Conducting the IT Audit
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
1 Software Reviews - FTR SWENET Module QUA2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical.
Project Management Life Cycle Katy Koenen 05/07/2013.
Quality Directions Australia Improving clinical risk management systems: Root Cause Analysis.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
ACCOUNTING INFORMATION SYSTEMS
FAO/WHO Codex Training Package Module 3.2 FAO/WHO CODEX TRAINING PACKAGE SECTION THREE – BASICS OF NATIONAL CODEX ACTIVITIES 3.2 How to develop national.
CHAPTER 3 SCOPING AND AGENCY COORDINATION. Scoping - the procedure for determining the appropriate level of study of a proposed project/activity - process.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
Effective Meetings Quick Refresher. 10 Best Practices for Effective Meetings Draft an agenda & send out approximately 48 hours in advance Recap time-sensitive.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
Stakeholder consultations Kyiv May 13, Why stakeholder consultations? To help improve project design and implementation To inform people about changes.
Fun, fun, fun. But first … the code review Preparation Process.
Research & Technology Implementation TxDOT RTI OFFICE.
Post-Secondary Education Program Joint AFN/INAC PSE Program Review with representation from NAIIHL and the Labrador Inuit Regional Information Process.
Project monitoring and Control
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Code Review.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Develop Project Charter
Code review. informal formal ad hoc reviewpair programmingwalk throughinspection/review.
Deliverable 10. Deliverable #10 Class Design and Implementation #1 due 9 April Executive Summary and Statement of Work Iteration Plan (Updated) for remaining.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
1 Kingsley Karunaratne, Department of Accounting, University of Sri Jayewardenepura, Colombo - Sri Lanka Practice Management.
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
Project management Topic 7 Controls. What is a control? Decision making activities – Planning – Monitor progress – Compare achievement with plan – Detect.
EFFECTIVE COMMUNICATION EFFECTIVE COMMUNICATION [UWB 10202] Meeting Mdm Siti Aisyah binti Akiah.
Requirements Workshop Techniques for E-Business Projects
Tips on Project Management Fall 2009 Updated Spring 2012 Presented by: Dr. Bun Yue Chair, Division of Computing and Mathematics Spring 2012 University.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
Peer Review Overview Meeting [Date] [Product name]
Project management Topic 2 Product based planning.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Running Effective Meetings. So what makes a meeting effective? They achieve the meeting's objective. They take up a minimum amount of time. They leave.
THE “WORK” IN TEAMWORK PLANNING THE PROCESS. KNOW THE CONTEXT OF YOUR WORK Analyze the System Identify Responsibilities  Organizational Responsibilities.
Nick Small, Shawn Boughey, Karolina Latkoska Project Briefing 1.
Security Development Lifecycle (SDL) Overview
Running a meeting.
Stakeholder consultations
PROJECT MANAGEMENT AND CONTROL
Software and Systems Integration
Implementation Strategy July 2002
Tips on Project Management Fall 2009
QA Reviews Lecture # 6.
GEME WG Kick-off meeting
Software Reviews.
Bill Coleman IWVTA Ambassador to GRPE
Presentation transcript:

Reviews mae, fall 11

Review What: – Have skilled people assess your work –Requires that you have work product that is reviewable Why: – Find problems early – Find omissions

Types of reviews Requirements review Architectural review UI design review Component design review Test plan review Code review

Architectural review Is it capable of meeting the requirements? Is it practical to build, test, and support? Does it satisfy good design principles? Is it documented such that someone could review it.

Preparation prepare work products + plan examine work products prepare review package ready for review? read package study work products prepare comments, Rubric schedule review send out packages calendar dates Author (from Team being reviewed) Moderator (from team doing review) Reviewers (team doing review) Y N

Work products (design) –use cases –class diagrams –primary responsibility of each class –sequence diagrams –models –etc. Plan –what will be reviewed and the order –what types of issues will be covered don’t hide risks

Preparation prepare work products + plan examine work products + plan prepare review package ready for review? read package study work products prepare comments schedule review send out packages AuthorModerator Reviewers Y N

Preparation prepare work products examine work products prepare review package ready for review? read package study work products prepare comments schedule review send out packages AuthorModerator Reviewers Y N

Review package (hyperlinked) Intro Agenda Criteria Work products Reviewer assignments

Review package - Intro Background –What project are we discussing –What do reviewers need to know about it history, key problems, important decisions, etc. –Where can reviewers find more info requirements, designs, analysis Goals for review –specific work products to be reviewed –scope (what is in/out of bounds) –what approval means

Review package (hyperlinked) Intro Agenda Criteria Work products Reviewer assignments Order materials will be reviewed.

Review - criteria We will provide rubric: Are the uses cases appropriate? Is the architecture able to realize the use cases? Is the design feasible? Are underlying models clear? Does the design follow good design principles? Does it use patterns effectively The author and moderator should amend as appropriate.

Review package (hyperlinked) Intro Agenda Criteria Work products Reviewer assignments Use cases, class diagrams, sequence diagrams, etc.

Review package (hyperlinked) Intro Agenda Criteria Work products Reviewer assignments What each reviewer is responsible for; e.g. give each reviewer responsibility for a subset of the classes

Preparation prepare work products examine work products prepare review package ready for review? read package study work products prepare comments schedule review send out packages AuthorModerator Reviewers Y N We are going to schedule it !!!

Preparation prepare work products examine work products prepare review package ready for review? read package study work products prepare comments schedule review send out packages AuthorModerator Reviewers Y N

Preparation prepare work products examine work products prepare review package ready for review? read package study work products prepare comments schedule review send out packages AuthorModerator Reviewers Y N DESIGN REVIEW

Review process Moderator – not a member of reviewed team –keeps review moving –ensures all voices are heard and key points covered –ensures decisions are made: accepted, major/minor revisions, further review Recorder – member of the reviewed team –takes notes, records all issues raised and decisions reached, all questions, suggestions, and action items –publishes a report of the review

Review process cont. Reviewers –Raise questions, concerns Author and design team –Answers questions but is otherwise silent

Review cont. Stick to specified level Avoid re-specifying/designing system Avoid getting sidetracked