软件工程第9版部分习题答案.docx





《软件工程第9版部分习题答案.docx》由会员分享,可在线阅读,更多相关《软件工程第9版部分习题答案.docx(5页珍藏版)》请在淘文阁 - 分享文档赚钱的网站上搜索。
1、习题参考答案Exercises(Homework): P251.3 What are the four important attributes that all professional software should have? Suggest four other attributes that may sometimes be significant.Answer:Four important attributes are maintainability, dependability, performance and usability. Other attributes that m
2、ay be significant could be reusability (can it be reused in other applications), distributability (can it be distributed over a network of processors), portability (can it operate on multiple platforms e.g laptop and mobile platforms) and inter-operability (can it work with a wide range of other sof
3、tware systems).Decompositions of the 4 key attributes e.g. dependability decomposes to security, safety, availability, etc. is also a valid answer to this question.2.1Giving reasons for your answer based on the type of system being developed, suggest the most appropriate generic software process mod
4、el that might be used as a basis for managing the development of the following systems: A system to control anti-lock braking in a car A virtual reality system to support software maintenance A university accounting system that replaces an existing system An interactive travel planning system that h
5、elps users plan journeys with the lowest environmental impactAnswer:1. Anti-lock braking system This is a safety-critical system so requires a lot of up-front analysis before implementation. It certainly needs a plan-driven approach to development with the requirements carefully analysed. A waterfal
6、l model is therefore the most appropriate approach to use, perhaps with formal transformations between the different development stages.2. Virtual reality system This is a system where the requirements will change and there will be an extensive user interface components. Incremental development with
7、, perhaps, some UI prototyping is the most appropriate model. An agile process may be used.3. University accounting system This is a system whose requirements are fairly ell-known and which will be used in an environment in conjunction with lots of other stems such as a research grant management sys
8、tem. Therefore, a reuse-based proach is likely to be appropriate for this.4. Interactive travel planning system System with a complex user interface but which must be stable and reliable. An incremental development approach is the most appropriate as the system requirements will change as real user
9、experience with the system is gained.2.4Suggest why it is important to make a distinction between developing the user requirements and developing system requirements in the requirements engineering process.Answer:There is a fundamental difference between the user and the system requirements that mea
10、n they should be considered separately.1. The user requirements are intended to describe the systems functions and features from a user perspective and it is essential that users understand these requirements. They should be expressed in natural language and may not be expressed in great detail, to
11、allow some implementation flexibility. The people involved in the process must be able to understand the users environment and application domain.2. The system requirements are much more detailed than the user requirements and are intended to be a precise specification of the system that may be part
12、 of a system contract. They may also be used in situations where development is outsourced and the development team need a complete specification of what should be developed. The system requirements are developed after user requirements have been established.Excercises(Homework): P1164.2,*4.44.2Disc
13、over ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system:An automated ticket-issuing system sells rail tickets. Users select their destination and input a credit card and a personal identification number.The rail ticket is issued and their credit c
14、ard account charged. When the user presses the start button, a menu display of potential destinations is activated, along with a message to the user to select a destination. Once a destination has been selected, users are requested to input their credit card.Its validity is checked and the user is t
15、hen requested to input a personal identifier. When the credit transaction has been validated, the ticket is issued.Answer:Ambiguities and omissions include:l Can a customer buy several tickets for the same destination together or must they be bought one at a time?l Can customers cancel a request if
16、a mistake has been made?l How should the system respond if an invalid card is input?l What happens if customers try to put their card in before selecting a destination (as they would in ATM machines)?l Must the user press the start button again if they wish to buy another ticket to a different desti
17、nation?l Should the system only sell tickets between the station where the machine is situated and direct connections or should it include all possible destinations?4.4Write a set of non-functional requirements for the ticket-issuing system, setting out its expected reliability and response time.Ans
18、wer:Possible non-functional requirements for the ticket issuing system include:1. Between 0600 and 2300 in any one day, the total system down time should not exceed 5 minutes.2. Between 0600 and 2300 in any one day, the recovery time after a system failure should not exceed 2 minutes.3. Between 2300
19、 and 0600 in any one day, the total system down time should not exceed 20 minutes.All these are availability requirements note that these vary according to the time of day. Failures when most people are traveling are less acceptable than failures when there are few customers.4. After the customer pr
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- 软件工程 部分 习题 答案

限制150内