Legacy transcripts Planning Meeting March 7, 2019.

Slides:



Advertisements
Similar presentations
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
Advertisements

Software Process Models
Evaluating Requirements. Outline Brief Review Stakeholder Review Requirements Analysis Summary Activity 1.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
1 Business (Agency) Process Discovery and Documentation Workshop PeopleSoft Phase II Tuesday, October 23, :00 AM to 12:00 Noon Concourse Theatre.
Evaluating Requirements
Robustness Analysis Dr. Neal CIS 480. Outline What is robustness analysis? Key roles in robustness analysis Object types found in discovery Diagramming.
Requirements - Why What and How? Sriram Mohan. Outline Why ? What ? How ?
SE 555 Software Requirements & Specification Requirements Validation.
Introduction to Software Engineering Dr. Basem Alkazemi
Evaluating Requirements
Health Informatics Series
Financial Model ‘An integrated model for STFC’ Draft Blueprint Design v0.1 Project Manager: Mark Affonso Project Champion: Jane Tirard.
Chapter 4 Preliminary Investigation Project triggers Business process redesign (BPR) Strategic planning The preliminary investigation stage Gathering information.
Requirements Gathering : Determining the scope of the system 1. Elicitiation – fact finding 2. Specification 3. Validation.
Facilitation Richard Fisher. 10/9/2000Facilitation - Richard Fisher2 Facilitated Sessions A structured meeting technique designed to gather information.
The Software Development Life Cycle: An Overview
Chapter 4 Requirements Engineering
Web Development Process Description
The Database Development Process
Copyright Course Technology 1999
System Implementation. System Implementation and Seven major activities Coding Testing Installation Documentation Training Support Purpose To convert.
Condor Technology Solutions, Inc. Grace RFTS Application Extension Phase.
Requirements Analysis
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
1.  Project: temporary endeavor to achieve some specific objectives in a defined time  Project management ◦ Dynamic process ◦ Controlled and structured.
REQUIREMENTS - WHY WHAT AND HOW? Steve Chenoweth & Chandan Rupakheti CSSE 371 Chapters Requirements Text. Question 6.
Requirement engineering Good Practices for Requirements Engineering
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Chapter 31 Your Prescription for Requirements Management.
Chapter 16 Quality Assurance Through Software Engineering Systems Analysis and Design Kendall & Kendall Sixth Edition.
Evaluating Requirements
Requirement Engineering
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
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.
Chapter 1 Assuming the Role of the Systems Analyst.
Your Prescription for Requirements Management 1. Assumptions The prescription for requirements management is based on the following assumptions:  The.
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Planning Engagement Kickoff
Advanced Higher Computing Science
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Interset Support Overview March 2017
How to Gain 100% User Adoption for Your Dynamics AX Project
Roles and Responsibilities
From manual test shop to fully automated test coverage: A How-To session to speed up your journey Jayshree Bhakta ITHAKA/JSTOR.
Business (Agency) Process Discovery and Documentation Workshop
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Quick Solution Dial Now 1(800) QuickBooks Payroll Support
ctcLink Project Update Technology Institute – Guided Pathways
Johanna Rothman Know What “Done” Means Chapter 11
Rational Unified Process
Chapter 1 (pages 4-9); Overview of SDLC
Systems Analysis Overview.
Chapter 5 Designing the Architecture Shari L. Pfleeger Joanne M. Atlee
Introduction to Fire Incident Maps
Project Ideation Agile Down-to-Earth © 2016.
CIS 375 Bruce R. Maxim UM-Dearborn
Introduction to Software Planning and Design
Welcome Traceability Software Integrators
Software Engineering Lecture 17.
Chapter 5 Understanding Requirements.
AICT5 – eProject Project Planning for ICT
Chapter 3: Project Integration Management
Software Development In Agile
Reportnet 3.0 Database Feasibility Study – Approach
Executive Project Kickoff
Software Development In Agile
Project Name Here Kick-off Date
Presentation transcript:

Legacy transcripts Planning Meeting March 7, 2019

Objective To make sure the solution is right for everyone and that it fits.

Iterative development Iterative development is a way of breaking down the software development of a large application into smaller chunks. In iterative development, feature code is designed, developed and tested in repeated cycles. With each iteration, additional features can be designed, developed and tested until there is a fully functional software application ready to be deployed to customers.1 1Rouse, Margaret, and Yvette Francino. “What Is Iterative Development? - Definition from WhatIs.com.” SearchSoftwareQuality, 2011, searchsoftwarequality.techtarget.com/definition/iterative-development.

elicit requirements SBCTC facilitates online or in-person workshop(s) Workgroup shares their ideas and expectations SBCTC records feedback Topics Define what we are trying to solve Discover impacted users, external systems Discover user interactions and goals Discover features and design Discover the sequence of activities Discover data that users rely on Discuss decisions that the system will make

Analysis and documentation Topics Design Document Define what we are trying to solve Project scope/overview Discover impacted users, external systems Context diagram Process flows User stories Discover user interactions and goals Story maps Discover features and design Process flow Discover the sequence of activities Discover data that users rely on Data flow diagrams Discuss decisions that the system will make Decision tables SBCTC performs analysis of requirements and prepares design document

Review requirements and design Workgroup reviews and approves design document

implement SBCTC develops web-based application based on design document SBCTC pulls data from legacy systems SBCTC develops test scenarios based on user stories Meets OCIO standards on security, accessibility Responsive design

Test application and evaluate Workgroup validates user stories by executing test scenarios SBCTC and workgroup evaluates results from testing Iterative development process repeats if testing produces errors or missing design elements

deploy OTHER DUTIES SBCTC deploys application Workgroups assists with developing system communication SBCTC maintains project web site SBCTC monitors and reports on project activities and timelines

Workgroup make-up / schedule Suggest 5-7 individuals from colleges representing diverse size and locations 3 - 4 work sessions Online via WebEx or in-person First meeting will last 3-4 hours Subsequent meetings 1-2 hours Quick check-in meetings as needed 30 minutes via WebEx Project / time commitment depends on overall project scope

Any questions? Sandy Main Director, Application Services Washington State Board for Community and Technical Colleges smain@sbctc.edu • o: 360-704-4373 • f: 360-704-4414 • c: 360-280-8038 sbctc.edu • Twitter: @SBCTCWashington • Facebook: @WASBCTC