Đang chuẩn bị nút TẢI XUỐNG, xin hãy chờ
Tải xuống
Tham khảo tài liệu 'seventh edition - chương 11', công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả | Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 11 CLASSICAL ANALYSIS Overview The specification document Informal specifications Structured systems analysis Structured systems analysis: The MSG Foundation case study Other semiformal techniques Entity-relationship modeling Finite state machines Petri nets Z (Formal method of specification) Overview (contd) Other formal techniques Comparison of classical analysis techniques Testing during classical analysis CASE tools for classical analysis Metrics for classical analysis Software project management plan: The MSG Foundation case study Challenges of classical analysis The Specification Document Must Be Informal enough for the client The client is generally not a computer specialist Formal enough for the developers It is the sole source of information for drawing up the design These two requirements are mutually contradictory 11.1 The . | Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 11 CLASSICAL ANALYSIS Overview The specification document Informal specifications Structured systems analysis Structured systems analysis: The MSG Foundation case study Other semiformal techniques Entity-relationship modeling Finite state machines Petri nets Z (Formal method of specification) Overview (contd) Other formal techniques Comparison of classical analysis techniques Testing during classical analysis CASE tools for classical analysis Metrics for classical analysis Software project management plan: The MSG Foundation case study Challenges of classical analysis The Specification Document Must Be Informal enough for the client The client is generally not a computer specialist Formal enough for the developers It is the sole source of information for drawing up the design These two requirements are mutually contradictory 11.1 The Specification Document The specification document is a contract between the client and the developers Typical constraints Deadline Parallel running Portability Reliability Rapid response time For real-time software Hard real-time constraints must be satisfied Specification Document (contd) Acceptance criteria It is vital to spell out a series of tests If the product passes the tests, it is deemed have satisfied its specifications Some acceptance criteria are restatements of constraints Solution Strategy A general approach to building the product Find strategies without worrying about constraints Then modify the strategies in the light of the constraints, if necessary Keep a written record of all discarded strategies, and why they were discarded To protect the analysis team To prevent unwise new “solutions” during postdelivery maintenance 11.2 Informal Specifications Informal specifications are written in a natural language Examples: English, Mandarin, Kiswahili, Hindi Example “If the sales for
