tailieunhanh - Lecture Software design and architecture – Chapter 19

Lecture 19 – Software requirement specification. Requirements are the descriptions of the services provided by a system and its operational constraints. It may range from a high level abstract statement to a detailed mathematical specification. | SOFTWARE DESIGN AND ARCHITECTURE LECTURE 19 Review Basic Concepts of Object Oriented Modeling UML and OO Modeling Out line Software Requirements Requirements Engineering Process What is a requirement? It is about WHAT not HOW Requirements are the descriptions of the services provided by a system and its operational constraints It may range from a high level abstract statement to a detailed mathematical specification What is requirements engineering? It is the process of discovering, analyzing, documenting and validating the requirements of the system Each software development process goes through the phase of requirements engineering Why requirements? What are the advantages of a complete set of documented requirements? Ensures the user (not the developer) drives system functionalities Helps avoiding confusion and arguments Helps minimizing the changes Changes in requirements are expensive. Changing the requirements costs: 3 x as much during the design phase 5-10 x as much during . | SOFTWARE DESIGN AND ARCHITECTURE LECTURE 19 Review Basic Concepts of Object Oriented Modeling UML and OO Modeling Out line Software Requirements Requirements Engineering Process What is a requirement? It is about WHAT not HOW Requirements are the descriptions of the services provided by a system and its operational constraints It may range from a high level abstract statement to a detailed mathematical specification What is requirements engineering? It is the process of discovering, analyzing, documenting and validating the requirements of the system Each software development process goes through the phase of requirements engineering Why requirements? What are the advantages of a complete set of documented requirements? Ensures the user (not the developer) drives system functionalities Helps avoiding confusion and arguments Helps minimizing the changes Changes in requirements are expensive. Changing the requirements costs: 3 x as much during the design phase 5-10 x as much during implementation 10-100 x as much after release [Code Complete, p30] Why requirements? 2/3 of finished system errors are requirements and design errors [RG] A careful requirements process doesn’t mean there will be no changes later Average project experiences about 25% changes in the requirements This accounts for 70-80% if the rework of the project [Code Complete, p40] Important to plan for requirements changes The case of critical applications Different levels of abstraction User requirements (abstract +) Usually the first attempt for the description of the requirements Services and constraints of the system In natural language or diagrams Readable by everybody Serve business objectives System requirements (abstract -) Services and constraints of the system in detail Useful for the design and development Precise and cover all cases Structured presentation Example User requirement: The library system should provide a way to allow a patron to borrow a book from the library. System .

• Đồ họa - Thiết kế - Flash
• Software requirement specification
• Software design
• Software design and architecture
• Software architecture
• Software architectural design
• Object oriented design
• Software development
• Requirement engineering
• Lecture Requirement engineering
• Software requirement
• Requirement specification
• System requirement specification
• External interface requirement
• Functional requirement
• Formal specification
• System test case generation
• Specify software functional requirements
• Language USL
• Báo cáo bài tập tuần 3
• Phân tích yêu cầu phần mềm
• Biểu mẫu IEEE 830 1998
• Các Tips để viết đặc tả
• Bài tập Công nghệ thông tin
• Object oriented software engineering
• Software engineering
• Practical software development
• Object orientation
• Reusable technology
• Lecture Software Engineering
• Rapid software development
• Agile methods
• Software prototyping
• Extreme programming
• Rapid application development
• Object oriented software engineering
• Software quality
• Software engineering projects
• Bài giảng Kỹ thuật phần mềm
• Agile software development
• Agile development techniques
• Agile project management
• Scaling agile methods
• Head First Software Development
• Software
• application software
• Software reuse
• Critical systems development
• Software evolution
• Software testing
• Critical systems validation
• Software development activities
• Software process
• Công nghệ phần mềm
• Agile development
• Adaptive software development
• Software design methods
• Data flow software architecture
• Component based software engineering
• Professional software development
• Software engineering ethics
• Software process activities
• Software engineering diversity
• Designing software
• Architecting software