Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 1 Requirements  Elicitation  Analysis  Specification.

Slides:



Advertisements
Similar presentations
1 Lecture 2: Processes, Requirements, and Use Cases.
Advertisements

CSC 480 Software Engineering
Chapter 2 Process Models
Object-Oriented Analysis and Design
Using UML, Patterns, and Java Object-Oriented Software Engineering Royce’s Methodology Chapter 16, Royce’ Methodology.
Software Life Cycles ECE 417/617: Elements of Software Engineering

1 Lecture 1: Processes, Requirements, and Use Cases.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
CIS 321—IS Analysis & Design
UML - Development Process 1 Software Development Process Using UML (2)
Software Waterfall Life Cycle Requirements Construction Design Testing Delivery and Installation Operations and Maintenance Concept Exploration Prototype.
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
CompSci 230 Software Design and Construction
1 ICS 122: Software Specification and Quality Engineering Spring 2002Lecturers: H. Muccini and D. J. Richardson Lecture 13: Summary The three aspects:
Chapter 1: Introduction to Systems Analysis and Design
What is a life cycle model?
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010/2013.
CS361 Winter 2013 Final Exam Review Software Engineering I Oregon State University.
Copyright © 2015 Pearson Education, Inc. Chapter 7: Software Engineering.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university 1Worshop in SE ProjectSpring 2013.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Testing Workflow In the Unified Process and Agile/Scrum processes.
Iterative development and The Unified process Chapter 2 Applying UML and Patterns -Craig Larman.
Review for the Final Exam CSCI Software Project Management.
1/23 Prescriptive Process Models. 2/23 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
1. What do you understand by software engineering? Discuss the role of engineering software development. 2. What do you understand by software requirement.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
The principles of an object oriented software development process Week 04 1.
Software Engineering1  Verification: The software should conform to its specification  Validation: The software should do what the user really requires.
Exam 2 Review Software Engineering CS 561. Outline Requirements Development UML Class Diagrams Design Patterns Users, Usability, and User Interfaces Software.
Chapter 7: Software Engineering
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Review for the Final Exam CSCI Software Project Management.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Engineering I. Introduction to Software Engineering Software models Formal Specification using ASML (Abstract State Machines Language) Software.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010/2013.
Testing Overview Software Reliability Techniques Testing Concepts CEN 4010 Class 24 – 11/17.
Unified Software Practices v 5.0-D Copyright  1998 Rational Software, all rights reserved 1 /26 Rational Unified Process – Part 2 Original slides modified.
Review for Final July 24 th – 8:00am to 11:00am. Topics to Study Java code. Look at: – Examples from class – Homework 3 Class Diagram State Diagram Activity.
© NALO Solutions Limited NALO Solutions, presents the – Revenue Collector App Using Mobile Phones to gather Revenue SOFTWARE ENGINEERING.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Testing Worshop in Software Engineering Project Department of Computer Science Ben-Gurion university 1Worshop in SE ProjectSpring 2013.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Software Development Framework
Process 4 Hours.
The Unified Software Development Process
Chapter 7: Software Engineering
(Complex) Problem domain Requirements Specification
Chapter 7: Software Engineering
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Chapter 1: Introduction to Systems Analysis and Design
Review for Final, Fall 2010 Close book, Close notes
Introduction to Software Engineering
Object Oriented Analysis and Design
كارگاه مهندسي نرم افزار
Basic SDLC Models SDLC  System Development Life Cycle.
Practical Software Engineering
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 1 Requirements  Elicitation  Analysis  Specification  Modeling  Formalization  Validation  IEEE Std 830  Natural language specifications  Use-case  Actor  Classes  Data model  Non-functional requirements

Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 2 Design and architecture  Box-and-line diagram  Time  Development  Run-time  Deployment  Coupling - Cohesion  Scale up - scale out  Architecture styles  Pipes and filters  Layers  Client-server  Design patterns  Strategy  Observer  Façade  UML: sketching, blueprinting, programming language  class diagram: attributes, association. composition, generalization  object diagrams  sequence diagram  state machine diagrams  activity diagrams  deployment diagrams

Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 3 Testing  Error, Fault. Failure  Black-box testing  White-box testing  Oracle  Equivalence class testing  Boundary value testing  Control graph testing coverage  Data-flow testing coverage  Unit testing  Regression testing  Integration testing  System testing  Acceptance testing  Benchmarking  Pilot testing  alpha test  beta test  Installation testing  Parallel testing

Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 4 Planning and processes  Project, Process  Stakeholders  SMART goals  Milestone, Tollgate  Critical path  COCOMO  Delphi  Risk analysis: Probability, Impact  Risk plan: Avoid, Transfer, Accept  Risk management  Models  Waterfall  V-model  Spiral  Iterative development  Incremental development  Time-boxing  Processes and methodologies  RUP - Inception, Elaboration, Construction, Transition  Agile Extreme programming (XP) Scrum  Configuration Management

Part I Heading text 1 Part II Heading text 2 Kristian Sandahl Part III Heading text 3 5 Quality factors  Usability engineering  Relevance  Efficiency  Attitude  Learnability  Reliability engineering  Failure intensity  Safety  Hazard, Incident, Accident  Inspection  Roles  Process  Inspection record  Weaker methods  Management  Software metrics  Software quality factors  ISO  Total Quality management  CMMI or CMM levels 2 and 3