Requirements Documents CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 18, 2004 In the book – This is.

Slides:



Advertisements
Similar presentations
Evaluating Credibility of Sources Lesson 7. Credible Sources Just because Google puts a result first does not necessarily give it any credibility. Think.
Advertisements

The Writing Process Communication Arts.
The Writing Process.
XML-Based Course Websites Michael Wollowski Computer Science and Software Engineering Department Rose-Hulman Institute of Technology.
1 CSSE 477: Swre Arch – This year’s course… Steve Chenoweth Tuesday, 11/8/11 Week 10, Day 2 Right – Sunset at the Louvre, in Paris From
Ambiguity and Specificity CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 19, 2004 In the book – This.
Traceability CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 22, 2004 In the book – This is Ch
The Software Team CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 7, 2004 In the book – This is Ch 4.
1 Software Maintenance and Evolution CSSE 575: Session 1, Part 1 Course Introduction Steve Chenoweth Office Phone: (812) Cell: (937)
Experience with an XML- Based Syllabus Editor and Search Engine Michael Wollowski Computer Science and Software Engineering Department Rose-Hulman Institute.
1 Steve Chenoweth Tuesday, 10/04/11 Week 5, Day 2 Right – Typical tool for reading out error codes logged by your car’s computer, to help analyze its problems.
WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits This document should.
1 of 2 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. © 2007 Microsoft Corporation.
Elaboration of Use Cases CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 21, 2004 In the book – This is.
1 Program Understanding Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
Storyboards CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 14, 2004 In the book – This is Ch 13 The.
0-1 Team # Status Report (1 of 4) Client Contact –Point 1 –Point 2 Team Meetings –Point 1 –Point 2 Team Organization –Point 1 –Point 2 Team #: Team Name.
Week 10 CSSE 375 Steve Chenoweth & Everybody. Today Get back Exam 2 This week’s schedule – this Reflection on the course Talk about final assignment Decide.
Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.
0-1 Team # Status Report (1 of 4) Client Contact –Status Point 1 –Status Point 2 Team Meetings –Status Point 1 –Status Point 2 Team Organization –Description.
1 Course Intro Construction & Evolution CSSE 375 Steve Chenoweth.
Actual content in a virtual world Simon Wilson Mersey Gateway Project Manager tel:
1 Questions? CSSE Requirements Steve Chenoweth Department of Computer Science & Software Engineering RHIT Session 6 – Wed, July 18, 2007 Above –
Team Skill 6 - Building The Right System Part 1: Applying Use Cases (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
What makes me ME? What am I good at? What is important to me?
Slide 1 Understanding Interaction, Users and Interfaces and Designing for Collaboration and Communication (Chapters 2-5 of Interaction Design text) CSSE.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
CSSE 533 – Database Systems Week 1, Day 1 Steve Chenoweth CSSE Dept.
SYSTEM LIFE CYCLES. OBJECTIVES o Be able to describe the stages of development of a hardware/software system. o Know what the different stages of the.
Introduction to Interactive Media 02. The Interactive Media Development Process.
Users’ reviews of TuneUp Utilities 2011 A brief Introduction of types of software Install Internet Information Services Install Microsoft Office 2010.
There are hundreds of Internet sites that offer free accounts. Some of the most popular are: Yahoo! Hotmail Excite Juno We’ll use Yahoo! for.
Systems Used for Collaboration When to achieve a common goal, result or work product.
Storytelling Your Way to a Better User Experience Whitney Quesenbery Kevin Brooks UPA Boston June 2010.
We’re going to a New Version? Bill Marlow School of Business, IT & Management.
Unit 1 – Improving Productivity Instructions ~ 100 words per box.
Usability Testing intro.12.ppt CS 121 “Ordering Chaos” “Mike” Michael A. Erlinger.
Using Movies In The Classroom. Open Questions What had global impact? Why? Are any of these events connected? How might you use this clip? Transformative.
PTLC Model: Supporting New Teachers in High Needs Schools Jacqueline McDonnough SheAnna McCloud Joy Casad NSF Robert Noyce Teacher Scholarship Conference.
Unit 2 (task 28) In this PowerPoint I will tell you about 7 important IT job roles and if a candidate might want one what he would have to do to get one.
Team Skill 3 – Organizing Requirements & Product Management (Chapters of the requirements text ) Sriram Mohan/Steve Chenoweth RHIT 1.
1 Design and Integration: Part 2. 2 Plus Delta Feedback Reading and lecture repeat Ambiguous questions on quizzes Attendance quizzes Boring white lecture.
O Gets the team off to a quick start o Make sure everyone understands the task o Makes sure that everyone's voice is heard o Organises and motivates their.
Using Search Engines. What is a search engine? A program that searches documents for specific keywords After its search, it gives you a list of the documents.
The Vision Document & Product Management CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute September 27, 2004 In.
Supervision Workshop for Multiple Subject Student Teachers and Interns.
 Write about something interesting you saw on TV or the Internet, or something you heard on the radio in the last week.
ADVANCED COMPUTERS S.Y.B.M.M. LECTURE SERIES - PART 1 - KANISHKA KHATRI m.
Team Skill 3 - Defining the System (Chapters of the requirements text ) Sriram Mohan 1.
Annotation. Lesson Objectives Unpack the considerations and process for analysing floor plans Annotate your preferred floor plan design Recap the minimum.
What are Background Checking Applications? By: Intelifi Screening Technology.
Easy Access with templates I: Create a database Lesson 16 By the end of this lesson you will be able to complete the following: Find the best database.
Text2PTO: Modernizing Patent Application Filing A Proposal for Submitting Text Applications to the USPTO.
How to Write a Book Review
Super3 Mini~ Page Project.
Finding Sources Introduction Types of sources Locating sources
using the internet for research
CSSE 371, Fall, 2013 “What to do for the client meeting” Week 4
Creative Engineering Design Competition
Visual Literacy - Conclusion
Ensuring Success through Assessment – Conclusion
FOUNDATIONS OF ALGEBRAIC PROBLEM SOLVING
Creative Engineering Design Competition
Creative Engineering Design Competition
IST346: What Is IT?.
Creative Engineering Design Competition
Creative Engineering Design Competition
Starting and Ending Class – Reviewing Previous Lesson
Creative Engineering Design Competition
Presentation transcript:

Requirements Documents CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 18, 2004 In the book – This is Ch 20 Left – People use these throughout engineering. This one’s rom the requirements document at archives.elevated.org/ project/resources.shtm. “Some are more precise than others…”

2 Let’s start with “Where do requirements come from?” Do it first, Then the “lessons” might sound familiar… Get with your project team. One person take notes. In 1 minute, write down the list of all the “sources” of your requirements. Where have they come from? We’ll hear a few examples. In 2 more minutes, write down a list of all the additional people who might know additional requirements (or could have good ideas about what should be in the system). We’ll hear a few examples. Keep these lists! (See p. 5  ) …From your project description. “This project would enable a user to share the real-time contents and actions of their computer screen with any remote user or group of users… ”

3 Do the requirements depend on who you heard them from? Well, yeah…? And in varying amounts, depending… How would you make your requirements reflect that? Above – Kids brainstorming ideas at a Young Authors’ Conference. From arborhts/ya.html. Right – The Codex Alexandrinus version of St Luke xii xiii 5, which is at the British Museum. From mov/ texts/dasc/HWGI04.H TM.

4 Ok, what else can get you? “When they say it!” I thought I told you that… Requirements “creep” What does this imply about how requirements should be done? “Didn’t I tell you so when we started?” cried Sherlock Holmes with a laugh. From canon/stud-207.htm.

5 Let’s look at some additional resources What’s in Ch 20 about all this – From Bill Opdyke , North Central College. (See academics/departments/computer_science/ department_site/faculty.htm. How the “Creative Problem Solving” process model sorts out “How’s and What’s” – This is out on Angel, under Handouts.  Google for “CPS Model” and you’ll get lots on this. At for example. The IEEE spec format, in case you run into it. You can find it on the web (e.g., at IEEE Spec at but we are supposed to pay IEEE for it. For “What does our competition learn on this subject?” see for example  Your devious next step in your project – You just did a list of what else you need to do. How would you contact the right people to get all those things?