본 포스트는 개인 스터디 용으로 작성된 Ian Sommerville의 Software Engineering, 8/E의 요약본입니다.1. Formal methods
- Formal specification is part of formal methods
- based on mathematical representation and analysis of S/W
- includes Formal specification, Specification analysis and proof, transformational development, program verification
2. Specification in the software process
- Specification and design are not seperatable.
- Architectural design is essential to specification process
3. Formal specification
- complements informal specification techniques. It removes areas of dout in a specification
- forces an analysis of the system requirements at an early stage, especially.
- Formal specification techniques are most applicable in the development of critical systems and standards.
- Algebraic techniques are suited to interface specification where the interfaces is defined as a set of object classes.
- Model-based techniques model the system using sets and functions. This simplifies some types of behavioural specification
- Operations are defined in a model-based specification by defining pre and post conditions on the system state.
'기술사 > 소프트웨어공학' 카테고리의 다른 글
| Design : Distributed Systems Architectures 1/3 (0) | 2008/03/29 |
|---|---|
| Design : Architectural Design (0) | 2008/03/29 |
| Requirements Engineering : Formal Specification (0) | 2008/03/28 |
| Requirements Engineering : System models (0) | 2008/03/26 |
| Requirements Engineering : Requirements Engineering Processes (0) | 2008/03/26 |
| Requirements Engineering : Software Requirements (0) | 2008/03/24 |
