A:Another name for the rapid application development model. £¨ÊÇ¿ìËÙ¿ª·¢Ä£Ð͵ıðÃû¡££©
B:Often used for the development of client/server applications. £¨Í¨³£±»ÓÃÓÚ¿ª·¢¿Í»§¶Ë/·þÎñÆ÷³ÌÐò¡££©
C:Only used for development of parallel or distributed systems. £¨Ö»Äܱ»ÓÃÓÚ¿ª·¢²¢Ðлò·Ö²¼Ê½ÏµÍ³¡££©
D:Used whenever a large number of change requests are anticipated. £¨±»ÓÃÓÚ¿ª·¢¿ÉÄܲúÉú´óÁ¿ÐèÇó±ä¶¯µÄÏîÄ¿¡££©
10. In the Unified Process model requirements are determined iteratively and may span more than one phase of the process.£¨ÔÚͳһ¹ý³ÌÄ£ÐÍÖУ¬ÐèÇóÔÚµü´úÖб»È·¶¨²¢ÇÒ¿ÉÄÜ¿çÔ½²»Ö¹Ò»¸ö¹ý³Ì½×¶Î¡££© A:
True£¨Õ棩
B:False£¨¼Ù£©
11. The component-based development model is£¨»ùÓÚ×é¼þµÄ¿ª·¢Ä£ÐÍ£© A:
Only appropriate for computer hardware design.£¨Ö»ÊÊÓÃÓÚ¼ÆËã»úÓ²¼þÉè¼Æ£© B:Not able to support the development of reusable components. £¨ÎÞ·¨Ö§³Ö¿É¸´ÓÃ×é¼þµÄ¿ª·¢£©
C:Works best when object technologies are available for support. £¨ÓÐÃæÏò¶ÔÏó¼¼ÊõÖ§³ÖʱЧ¹û×îºÃ£©
D:Not cost effective by known quantifiable software metrics.£¨²»·ûºÏÒÑÖªµÄ¿ÉÁ¿»¯µÄÈí¼þ¶ÈÁ¿µÄ³É±¾Ð§Ò棩
1. Explain why a software system used in a real-world environment must change or become progressive less useful?
2. Provide examples of software projects that would be amenable to the waterfall, prototyping, incremental models.
3. Describe the 5 levels of CMM.
4. Describe the advantages and disadvantages of waterfall model.
5. What are the differences between the 3 incremental models mentioned in this chapter?
Èý¡¢µÚ3ÕÂÈí¼þÐèÇó·ÖÎö
1. Use-case actors are always people, never system devices.£¨ÓÃÀýͼÖеIJÎÓëÕß±ØÐëÊÇÈË£¬¶ø²»ÄÜÊÇÆäËûµÄϵͳÉ豸¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
2. Which of following is not a UML diagram used creating a system analysis model?£¨ÒÔϵÄUMLͼÖУ¬ÄÇÒ»Ïî²»Äܱ»ÓÃÀ´´´½¨ÏµÍ³µÄ·ÖÎöÄ£ÐÍ£¿£© A:activity diagram£¨»î¶¯Í¼£© B:class diagram£¨Ààͼ£©
C:dataflow diagram£¨Êý¾ÝÁ÷ͼ£© D:state diagram £¨×´Ì¬Í¼£©
3. In win-win negotiation, the customer\\'s needs are met even though the developer\\'s need may not be.£¨ÔÚÒ»¸ö˫ӮµÄ̸ÅÐÖУ¬¼´Ê¹¿ª·¢ÕßµÄÐèÇó²»±»Âú×㣬¿Í»§µÄÐèÇóÈÔÓ¦µ±±»Âú×ã¡££©
A:True£¨Õ棩 B:False £¨¼Ù£©
4. The nature of collaboration is such that all system requirements are defined by consensus of a committee of customers and developers.£¨ºÏ×÷µÄ±¾ÖʾÍÔÚÓÚ¿Í»§ºÍ¿ª·¢Õß×é³ÉÒ»¸öÌÖÂÛ×飬´Ó¶ø¶¨Òå³öÒ»ÖµÄϵͳÐèÇó£© A:True£¨Õ棩 B:False £¨¼Ù£©
5. Analysis patterns facilitate the transformation of the analysis model into a design model by suggesting reliable solutions to common problems.£¨·ÖÎöģʽͨ¹ýÌá³öÕë¶ÔÒ»°ãÐÔÎÊÌâµÄ¿É¿¿½â¾ö·½°¸£¬ÓÐÖúÓÚ½«·ÖÎöÄ£ÐÍת»»ÎªÉè¼ÆÄ£ÐÍ¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
6. It is relatively common for different customers to propose conflicting requirements, each arguing that his or her version is the right one.£¨²»Í¬µÄÓû§¿ÉÄÜÌá³öÓгåÍ»µÄÐèÇó£¬Ã¿¸öÈ˶¼ÈÏΪËûÃÇ×Ô¼ºµÄ°æ±¾ÊÇ×îÕýÈ·µÄ£¬ÕâÊÇÒ»¸ö½ÏΪÕý³£µÄÏÖÏó¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
7. In collaborative requirements gathering, the facilitator£¨ÔÚÐ×÷ÐèÇóÊÕ¼¯µÄ¹ý³ÌÖУ¬Ðµ÷Õߣ© A:cannot be a member of the software team£¨²»ÄÜÊÇÈí¼þС×éµÄ³ÉÔ±£© B:cannot be a customer£¨²»ÄÜÊǿͻ§£©
C:controls and facilitates the process£¨¿ØÖƲ¢Ðµ÷¹ý³Ì½ø¶È£© D:must be an outsider £¨±ØÐëÊÇÒ»¸öÍⲿÈËÔ±£©
8. Which of the following is not one of the context-free questions that would be used during project inception?£¨ÏÂÃæÄÄÒ»¸öÑ¡Ïî²»ÊÇÉÏÏÂÎÄÎ޹ء¢¿É±»ÓÃÓÚÏîÄ¿³õʼ½×¶ÎµÄÎÊÌ⣿£© A:What will be the economic benefit from a good solution?£¨ºÃµÄ½â¾ö·½°¸»á´øÀ´Ê²Ã´¾¼ÃÀûÒæ£¿£©
B:Who is against this project?£¨Ë»á·´¶ÔÕâ¸öÏîÄ¿£¿£©
C:Who will pay for the work?£¨Ë½«ÎªÕâЩ¹¤×÷Ö§¸¶³êÀÍ£¿£© D:Who will use the solution?£¨Ë½«Ê¹ÓÃÕâ¸ö½â¾ö·½°¸£¿£©
9. A stakeholder is anyone who will purchase the completed software system under development.£¨ÀûÒæÏà¹ØÕß½«¹ºÂò¿ª·¢Íê³ÉºóµÄÍêÕûÈí¼þϵͳ¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
10. The best way to conduct a requirements validation review is to£¨½øÐÐÐèÇóÑéÖ¤¼ì²éµÄ×îºÃ·½Ê½ÊÇ£©
A:examine the system model for errors£¨¼ì²éϵͳģÐÍÖеĴíÎó£© B:have the customer look over the requirements£¨¿Í»§¼ì²éÐèÇó˵Ã÷£©
C:send them to the design team and see if they have any concerns£¨Èÿͻ§È¥Éè¼ÆÐ¡×éÈ·ÈÏÊÇ·ñÓëËûÃǵÄÉèÏëÓгöÈ룩
D:use a checklist of questions to examine each requirement £¨ÓÃÒ»¸ö¼ì²éÇåµ¥ÁбíÈ¥¼ìÑéÿÏîÐèÇó£©
11. Requirements engineering is a generic process that does not vary from one software project to another.£¨ÐèÇ󹤳ÌÊÇÒ»¸öÒ»°ãÐԵĹý³Ì£¬²»»áÒòÏîÄ¿µÄ±ä»¯¶ø±ä»¯¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
12. The result of the requirements engineering elaboration task is an analysis model that defines which of the following problem domain(s)?£¨ÐèÇ󹤳ÌÖÐϸ»¯ÈÎÎñµÄ½á¹ûÊÇÒ»¸ö¶¨ÒåÁËÒÔÏÂÄÄÏîÓòµÄ·ÖÎöÄ£ÐÍ£¿£© A:information£¨ÐÅÏ¢£© B:functional£¨¹¦ÄÜ£© C:behavioral£¨ÐÐΪ£©
D:all of the above £¨ÒÔÉÏËùÓУ©
13. The work products produced during requirement elicitation will vary depending on the£¨ÐèÇóµ¼³ö²úÉúµÄ²úÆ·½«ÒÀÀµÓÚ£©
A:size of the budget£¨Ô¤Ëã¹æÄ££©
B:size of the product being built£¨²úÆ·µÄ¹æÄ££©
C:software process being used£¨Èí¼þµÄ¿ª·¢¹ý³ÌÄ£ÐÍ£© D:stakeholders needs £¨ÀûÒæÏà¹ØÕßµÄÐèÇó£©
14. In requirements validation the requirements model is reviewed to ensure its technical feasibility.£¨ÔÚÐèÇóÑéÖ¤ÖУ¬ÐèÇóÄ£Ðͽ«±»¼ì²éÒÔÈ·±£¼¼Êõ¿ÉÐÐÐÔ¡££© A:True£¨Õ棩 B:False£¨¼Ù£©
15. The use of traceability tables helps to£¨¿É×·ËÝÐÔ±íµÄ×÷ÓÃÊÇ£©
A:debug programs following the detection of run-time errors£¨ÔÚ±àÒë³ÌÐòºó·¢ÏÖÔËÐÐʱ´íÎó£©
B:determine the performance of algorithm implementations£¨Åж¨Ë㷨ʵÏÖµÄÐÔÄÜ£© C:identify, control, and track requirements changes£¨Ê¶±ð£¬¿ØÖƺÍ×·×ÙÐèÇó±ä»¯£© D:none of the above £¨ÒÔÉ϶¼²»ÊÇ£©
16. Which of the following is not one of the requirement classifications used in Quality Function Deployment (QFD)?£¨ÒÔÏÂÄÄÒ»Ïî²»ÊÇÖÊÁ¿¹¦ÄÜÕ¹¿ªÖеÄÐèÇó·ÖÀࣿ£© A:exciting£¨ÐË·ÜÐèÇó£© B:expected£¨ÆÚÍûÐèÇó£© C:mandatory£¨Ç¿ÖÆÐèÇó£© D:normal £¨³£¹æÐèÇó£©
17. Developers and customers create use-cases to help the software team understand how different classes of end-users will use functions.£¨¿ª·¢ÈËÔ±ºÍ¿Í»§²ÉÓô´½¨ÓÃÀýͼµÄ·½Ê½£¬°ïÖúÈí¼þС×éÀí½â²»Í¬ÀàÐ͵Ä×îÖÕÓû§½«ÈçºÎʹÓÃϵͳ¹¦ÄÜ¡££© A:True£¨Õ棩
B:False £¨¼Ù£©
18. The job of the requirements engineer is to categorize all stakeholder information in a way that allows decision makers to choose an internally consistent set of requirements.£¨ÐèÇ󹤳ÌʦµÄ¹¤×÷ÊÇ»®·ÖÀûÒæ¹ØÏµÕßµÄÒªÇó£¬Ê¹µÃ¾ö²ßÕß¿ÉÒÔÑ¡Ôñ³öÒ»ÖÂÈϿɵÄÐèÇó¡££© A:True£¨Õ棩 B:False £¨¼Ù£©
19. The system specification describes the£¨ÏµÍ³¹æ¸ñ˵Ã÷ÊéÃèÊöÁË£©
A:Function, performance and constraints of a computer-based system£¨ÏµÍ³µÄ¹¦ÄÜ£¬ÐÔÄÜÒÔ¼°Ô¼ÊøÌõ¼þ£©
B:implementation of each allocated system£¨Ã¿¸ö·ÖÅäϵͳµÄʵÏÖ£© C:element software architecture£¨Èí¼þÔªËØµÄ¼Ü¹¹£©
D:time required for system simulation £¨ÏµÍ³Ä£ÄâµÄʱ¼äÒªÇó£©
1. Describe the weaknesses of use-cases as part of the requirements engineering process.
2. What are the major steps for requirements engineering?
3. Give some examples of functional and non-functional requirements.
4. What are the differences between product and process Requirements?
5. Please list some main requirements sources.
ËÄ¡¢µÚ4ÕÂÈí¼þÉè¼Æ¹¤³Ì
1. When using structured design methodologies the process of stepwise refinement is unnecessary. (µ±Ê¹Óýṹ»¯Éè¼Æ·½·¨Ê±£¬Öð²½¾«Á¶µÄ¹ý³ÌÔòÏÔµÃÎ޹ؽôÒª¡£) A:True£¨Õ棩 B:False £¨¼Ù£©
2. Software design is an iterative generic process that may be applied without modification to any software project.£¨Èí¼þÉè¼ÆÊÇÒ»°ãÐԵĵü´ú¹ý³Ì£¬²¢¿ÉÒÔ²»×öÐ޸ĵØÓ¦Óõ½ÈκÎÈí¼þÏîÄ¿£©
A:True£¨Õ棩 B:False £¨¼Ù£©
3. Design patterns are not applicable to the design of object-oriented software?£¨Éè¼ÆÄ£Ê½²»ÊÊÓÃÓÚÃæÏò¶ÔÏóµÄÈí¼þ¡££© A:True£¨Õ棩 B:False£¨¼Ù£©
4. Software designs are refactored to allow the creation of software that is easier to integrate, easier to test, and easier to maintain.£¨(ÖØ¹¹Èí¼þÉè¼Æ£¬Ê¹µÃÈí¼þ±äµÃ¸ü¼ÓÈÝÒ×ÕûºÏ¡¢²âÊÔºÍά»¤¡£)£©
A:True£¨Õ棩 B:False £¨¼Ù£©
5. Which design model is analogous to the detailed drawings of the access points and external utilities for a house?£¨ÏÂÃæÄĸöÉè¼ÆÄ£ÐÍ¿ÉÒÔÀà±È³É·¿×ÓÍⲿºÍÈë¿ÚµÄϸ½ÚÉè¼Æ£¿£© A:Architectural design(¼Ü¹¹Éè¼Æ)
B:Component-level design£¨×é¼þ¼¶Éè¼Æ£©