Leture-w1-1

Leture-w1-1 - SE 210 Software Specification and Design I...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
SE 210: Software Specification and Design I Fall 2008 Lecture 1 on Mon., Sept. 22, 2008
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Today’s Agenda Introduction to course content Introduction to the requirements problem Course Information
Background image of page 2
3 Course Title “Software Specification and Design” I: Fall 2008 II Winter 2009 Together is a complete course for obtaining necessary and  useful knowledge and techniques in Requirements  Analysis and management for software-intensive  systems.
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 SE 210: Course Description Study of the principles, practices, and techniques used to gather  system requirements. Document them in a requirements specification.  Includes techniques for requirements discovery such as user  interviews and prototyping.  Introduces approaches for organizing and expressing software  requirements in a requirements specification. 
Background image of page 4
5 SE 210: Learning Objectives Upon successful completion of this course, a student will be able  to: Explain and apply basic techniques for gathering and managing software  requirements.  Create a requirements document for a small software system.  Discuss issues and uses of diagrammatic and formal techniques of system  specification.  Create a specification for a small software system using a well-accepted  specification technique. 
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 About Your Instructor Yuan An, Ph.D. in CS (2007), University of Toronto. Assistant professor in iSchool at Drexel. Research Interests: Database, Conceptual Modeling,  Software Engineering, Requirements Engineering. http://www.ischool.drexel.edu/faculty/yan
Background image of page 6
7 What is Software Engineering? The application of a systematic, disciplined, quantified approach  to the development, operation, and maintenance of software.  [IEEE’90] Attributes of Engineering: High quality Responsibility and accountability Application of methodology Planned Managed Traceable steps Risk management
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
8 But we have Software Failures… Example failures: Usability problems: e.g., a web page with  yellow text on white  background. Functionality problems: e.g., a library system returns nothing if  you do not provide the full &  accu. tite of the book. Maintainability problems: e.g.,  a billing system does not  accept new services. Safety problems: e.g., air traffic controller lost voice contact  with 400 airplanes in LA airport in Setp. 14, 2004.
Background image of page 8
9 Why Does Software Fail?
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
10 Requirements At the beginning of software engineering, we have  requirements. ..
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 28

Leture-w1-1 - SE 210 Software Specification and Design I...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online