ITEC 370 Lecture 8 Requirements. Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?

Slides:

Advertisements

Similar presentations

Configuration Management

Advertisements

Dept of IT-CAPE. Introduction Doing it yourselves-attractive Potential suppliers –flexible planning Dept of IT-CAPE.

Exercise Science The Legal & Professional Responsibilities of Personal Trainers.

Ch-11 Project Execution and Termination. System Testing This involves two different phases with two different outputs First phase is system test planning.

Ch-2 Proposals and Contracts. Introduction Many issues have to be handled in a contract and a proposal including legal concerns, commercial arrangements.

ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.

Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.

Informatics 43 – April 16, Homework 1 What is the purpose and goal of each section in the document? Two audiences: non-technical users and technical.

Introduction to software project management. What is a project? One definition ‘a specific design or plan’ ‘a specific design or plan’ Key elements non-routine.

1 Software project management (intro) An introduction.

Lecture 4 Business Use Cases: How to document them 1 SYS366.

Michael S. Zachowski, Robert D. Walla Astrix Technology Group 1090 King Georges Post Rd Edison, NJ A Successful Approach to a LIMS Upgrade In A Public.

CORPORATE COMPLIANCE OVERVIEW David Meisels OSB Corporate Counsel Roundtable April 26, 2012.

© The McGraw-Hill Companies, Software Project Management 4th Edition Managing contracts Chapter 10.

SDLC Phase 2: Selection Dania Bilal IS 582 Spring 2009.

Software project management

Craig J. Nichols, Secretary 1. Mainframe and Other Software Florida State Term Contract Mainframe and Other Software July 22,

Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.

FINAL DEMO Apollo Crew, group 3 T SW Development Project.

Typical Software Documents with an emphasis on writing proposals.

Contractors & contracts

Project Management Development & developers

ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.

ITEC 370 Lecture 5 Requirements. Review Requirements –What did you learn? –Why are requirements part of the process? –What is the difference between a.

1 SYS366 Week 10, Lecture 3 Systems Requirements Gathering: Identifying Operating Requirements.

ITEC 370 Lecture 8 Requirements. Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?

Team Members David Haas Yun Tang Robert Njoroge Tom Kerwin Clients Facilities Management Don Anderson Rick Klein.

ITEC 370 Lecture 11 Design. Review Questions? Today! –Rough draft of your SRS document –Introduction, Features (Functional / Non-functional), Interfaces.

Copyright © 2006, Solbourne Confidential Oracle UPK and Solbourne’s UPK Accelerator April 27, 2007.

End HomeWelcome! The Software Development Process.

ITEC 370 Lecture 14 Implementation. Review Questions? Draft of design document on F Brief 3-5 minute work update on F (will continue except for mid-term)

Employment. Organization Strategy HR and Staffing Strategy Staffing Policies and Programs Staffing System and Retention Management Support Activities.

1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.

SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.

Custom Software Development Intellectual Property and Other Key Issues © 2006 Jeffrey W. Nelson and Iowa Department of Justice (Attach G)

Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.

Corporate Web Site Maintenance.  Urban Office Properties will have a comprehensive Web site that provides current and accurate information for customers.

© Mahindra Satyam 2009 Configuration Management QMS Training.

Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.

Software Development Processes: How to create great software, doing it right the first time and keep your sanity Matt Howland Francesca Noli.

Complying with Acceptable Use Policies.  AUP  Code of Conduct for Internet Use  Used by Organizations and Businesses  Outlines agreement in writing.

ITEC 370 Lecture 23 Maintenance. Review Questions? Project update on F, next F give prototype demonstration Maintenance –Reactive –Proactive.

CSC 395 – Software Engineering Lecture 2: Programming As Art & Intro to Software Engineering.

CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,

Requirements Engineering Lesson 2. Terminologies:  Software Acquisition is where requirement engineering significantly meets business strategy.  Software.

LEGALITIES. Independent Contractors vs. Employees ◦ Personal trainers working in clubs are: ◦ Independent Contractors ◦ Employees ◦ Personal trainers.

Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Put Away Loads.

Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Manage and Disposition Inventory Returns.

Oracle Fusion Applications 11gR1 ( ) Functional Overview (L2) Manage Inbound Logistics (L3) Inspect Material.

-1- Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner Boot Camp Training Courseware.

CS223: Software Engineering Lecture 16: The Agile Methodology.

Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.

Real Estate Brokerage. History Small, independent firms MLS Large franchise operations Consolidation of services “one-stop shopping” Profitability in.

ITEC 370 Lecture 6 Requirements. Review Requirements –What are some of the stages of the requirements gathering process? –What is the end result of this.

1 of 26 For Oracle employees and authorized partners only. Do not distribute to third parties. © 2009 Oracle Corporation – Proprietary and Confidential.

Oracle E-Business Suite R12.1 Accounts Receivables Essentials Partner Boot Camp Training Courseware.

McDonough Bolyard Peck Educational Series Building Commissioning Presented by: Doug Wrenn Steve Baxter July

McDonough Bolyard Peck Educational Series HVAC Commissioning Presented by: Doug Wren Steve Baxter September 30, 2003.

-1- For Oracle employees and authorized partners only. Do not distribute to third parties. © 2009 Oracle Corporation – Proprietary and Confidential Oracle.

BTEC NAT Unit 15 - Organisational Systems Security ORGANISATIONAL SYSTEMS SECURITY Unit 15 Lecture 7 EMPLOYMENT CONTRACTS & CODES OF CONDUCT.

Contract management 1. Acquiring software from external supplier This could be: a bespoke system - created specially for the customer off-the-shelf -

Lesson Objectives 1) Review the steps involved in problem solving 2) Review the stages of the System Life Cycle 3) Describe what prototyping is and the.

Vendor Statements of Work: Your Role as an IT Professional

PROJECT MANAGEMENT AND CONTROL

Recommending a Strategy

Software Engineering Lecture #14.

Introduction to Requirements Management

How to manage Requirements?

IT OPERATIONS Session 7.

Presentation transcript:

ITEC 370 Lecture 8 Requirements

Review Requirements –What are some of the characteristics of a good requirement? –What are use cases?

Requirements Objectives Today –1 page single spaced 12 pt font description of your idea What to do after you have the requirements document…

Requirements Presentatio n Present what you are going to build to the client Invite the stakeholders Formal meeting Short intro / motivation Features Interfaces

Requirements Acceptance testing Have description of how system is supposed to work Need –Software that implements the requirements document –A way for you and the client to agree that the delivered software works as expected

Requirements Acceptance testing Users need to see the software working Could just send a.exe and say done… Better way –Scripted demonstration –Pre-determined –Trial period for usage

Requirements Issues Lawyer needed –Serious contract issues can arise When is it “completed” After software is built who owns it? –Source code vs binaries Tech-support / Maintenance support Updates to the project

Requirements Sample contract Sections –Duties and responsibilities –Ownership of software –Compensation –Are you employees or independent contractors for the company (tax issues) –Customer monitoring –Change in specifications –Confidentiality –Training –Warranty –Term / Termination –Contact between developer and client –Waivers (if you forego one part of the contract, you don’t give it all up) –This contract is it, no previous agreements

Requirements Review Just because you know what to build doesn’t mean you are ready to start designing it