PPT4: Requirement analysis

Slides:



Advertisements
Similar presentations
Steps of a Design Brief V Design Brief  Problem, identification, and definition Establish a clear idea of what is to be accomplished. Identify.
Advertisements

Lumberton High School Sci Vis I V105.02
Software Requirements Engineering
Capturing the requirements
CS351 © 2003 Ray S. Babcock Requirements What not How “The Pizza Experiment” 1994, 350 companies, 8000 software projects. 31% were canceled before they.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
CS CS 5150 Software Engineering Lecture 10 Requirements 3.
S R S S ystem R equirements S pecification Specifying the Specifications.
The Software Development Life Cycle: An Overview
CS 4310: Software Engineering Lecture 3 Requirements and Design.
Systems Analysis and Design in a Changing World, Tuesday, Feb 27
CSCI 6231 Software Engineering ( Chapter 10?) Requirements Workflow Instructor: Morris Lancaster.
Planning and Writing Your Documents Chapter 6. Start of the Project Start the project by knowing the software you will write about, but you should try.
Introduction to Formal Methods Based on Jeannette M. Wing. A Specifier's Introduction to Formal Methods. IEEE Computer, 23(9):8-24, September,
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4 th edition, Prentice Hall, Hans Van Vliet, Software.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
Process 3a 1 A Spiral Model of Software Development and Enhancement Barry Boehm Computer, May 1988 text pp34-45.
Steps of a Design Brief V  Is a Plan of work A written step-by- step process by which the goal is to be accomplished The plan can include expected.
Essentials of OVID Using UML based notation to capture system requirements and design.
System Requirements Specification
Capturing Requirements. Questions to Ask about Requirements 1)Are the requirements correct? 2)Consistent? 3)Unambiguous? 4)Complete? 5)Feasible? 6)Relevant?
CEN 4020 Software Engineering PPT4: REQUIREMENT ANALYSIS Dishant Patel.
Requirement Analysis SOFTWARE ENGINEERING. What are Requirements? Expression of desired behavior Deals with objects or entities, the states they can be.
1 Capturing The Requirements CEN 4020 Software Engineering By Darren Quichocho.
Software Engineering I. Introduction to Software Engineering Software models Formal Specification using ASML (Abstract State Machines Language) Software.
Requirement Analysis Edwin Gendron CEN 4020 Software Engineering 1.
1 CEN 4020 Software Engineering PPT4: Requirement analysis.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
1 5/18/2007ã 2007, Spencer Rugaber Architectural Documentation Graphical (views) and textual Kruchten's 4+1 Views –Philippe B. Kruchten. "The 4+1 View.
Technical Module C Object Modeling Objects Object – a valuable resource: Money (Account Receivable) Material (Product) Machines (Delivery Truck) Personnel.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Requirements. Outline Definition Requirements Process Requirements Documentation Next Steps 1.
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
Requirements Specification
UML Diagrams By Daniel Damaris Novarianto S..
CMPE 280 Web UI Design and Development August 29 Class Meeting
UML Diagrams Jung Woo.
Requirements: Use Case Models and Narratives
The Process of Object Modeling
System Requirements Specification
Requirements – Scenarios and Use Cases
Guilford County SciVis V105.02
Introduction to Computer Graphics
Introduction to Computer Graphics
PPT and video are due: no later than November 16, 5:00 PM
Modeling Shari L. Pfleeger and Joanne M. Atlee, Software Engineering: Theory and Practice, 4th edition, Prentice Hall, Hans Van Vliet, Software Engineering:
Introduction to Computer Graphics
PPT9: Asserting expectations
PPT1: How failures come to be
PPT6: Scientific debugging
PPT1: Basics of software engineering
CS 8532: Advanced Software Engineering
PPT and video are due no later than February 15, 2019
PPT4: Rational B-spline Curves and Surfaces
PPT12: Shape Modification Tools
PPT3: Project planning and management
PPT3: B-spline Curves and Surfaces
PPT6: Advanced Geometric Algorithms
PPT9: Global and local interpolation
PPT7: Conics and Circles
PPT2: B-spline Basics Functions
PPT8: Common Surfaces as NURBS
PPT6: Object-oriented design
PPT and video are due no later than March 1, 2019
PPT and video are due no later than March 22, 2019
PPT11: Advanced Surface Construction Techniques
PPT and video are due no later than March 29, 2019
PPT11: System maintenance
PPT10: Global and local approximation
PPT5: Fundamental Geometric Algorithms
Presentation transcript:

PPT4: Requirement analysis CEN 4020 Software Engineering PPT4: Requirement analysis PPT and video are due no later than February 8, 2019 Submit to: lpiegl@gmail.com This template file is just an outline of the presentation that you need to complete. Additional pages will be necessary to fully explore the topic above. Each page should contain adequate text as well as illustrations. You are free to use all publicly available information (text as well as graphics) as long as the sources are properly acknowledged.

Team members’ contributions Member [name]:

Progress for capturing requirements Content outline: What are requirements?

Progress for capturing requirements Content outline: Steps of capturing requirements

Progress for capturing requirements Content outline: Forms of requirements Charts and explanations

How users and developers view each other Content outline: How developers view users? How users view developers?

Sources of requirements Content outline: Sources Chart and explanation

Requirement documentation Content outline: Desired requirement documents Lists and explanations

Importance of requirement analysis Content outline: Project surveys

Importance of requirement analysis Content outline: Causes of failed projects

Importance of requirement analysis Content outline: Cost of fixing a bug at different stages of the design process

Types of requirements Content outline: Types of requirements Explanation

Characteristics of requirements Content outline: Characteristics Explanation

Modeling notations Content outline: Entity relationship diagram UML class diagram Event traces Message sequence charts State machines UML state chart diagram Petri nets Data flow diagram Use case diagram Formal methods Decision table Parnas table First order and temporal logic Object constraint language Z

Prototyping requirements Content outline: Types of prototypes Examples

Documenting requirements Content outline: Need for documentation Definition document Specification document

IEEE standard for requirement specification Content outline: Standard Examples

Participants in the requirement process Content outline: The participants Their roles

Validation and verification Content outline: Requirements must meet customer needs

Validation and verification Content outline: Requirement reviews

Validation and verification Content outline: Validation, verification and checking

Measuring requirements Content outline: How to measure requirements?

Measuring requirements Content outline: Measuring requirement readiness

Choosing a specification language Content outline: List of selection criteria Explanation

Examples of modeling notations Content outline: Examples: use case, UML and message sequence charts Explanation