Term
| How does software differ from the artifacts produced by other engineering disciplines? |
|
Definition
| Software is both a product and a vehicle for delivering a product. |
|
|
Term
| How do software characteristics differ from hardware characteristics? |
|
Definition
| Software is developed, not manufactured. Software does not wear out, but it can deteriorate when changes occur. |
|
|
Term
| What do software engineering tools provide for process and methods. |
|
Definition
| automated or semi-automated support |
|
|
Term
| How are tasks, actions, and activities related to software process models? |
|
Definition
| A software process is made up of activities. Each activity is defined by a set of engineering actions. Each activity is defined by a task set that identifies the work items to be completed. |
|
|
Term
| How can process patterns assist a development team build software products efficiently? |
|
Definition
| Process patterns describe process-related problems that during software engineering, identify the environment in which the problems occurred, and suggest solutions. Process patterns provide you with a template. |
|
|
Term
| Why has the Personal Software Process not been widely adopted by industry? |
|
Definition
| It is intellectually challenging and demands a level of commitment and measurement that some software practitioners may not be able to obtain. |
|
|
Term
| Why are evolutionary models considered by many to be the best approach to software development in a modern context? |
|
Definition
| Because timelines for the development of modern software are becoming shorter, customers are becoming more diverse, and changes to requirements are becoming more common, we need a way to provide incremental or evolutionary delivery. The evolutionary process accommodates uncertainty, allows the delivery of partial solutions in an orderly manner, and reflects what really happens when you build complex systems. |
|
|
Term
| The “Manifesto for Agile Software Development” proposes the valuing of individuals and interactions over what? |
|
Definition
|
|
Term
| Describe the role of customers and end-users on an agile process team? |
|
Definition
| They participate as full collaborators. They provide information for creating use cases, information on the value business value of proposed software feature and functionality, and feedback on operational prototypes |
|
|
Term
| List the 5 key attributes of an effective software teams. |
|
Definition
| Sense of purpose, sense of involvement, sense of trust, sense of improvement, diversity of team member skill set |
|
|
Term
| What are the five values held by XP teams? |
|
Definition
| Communication, simplicity, feedback, courage, respect |
|
|
Term
|
Definition
| close informal verbal communication among team members and stakeholders establishing meaning for metaphors as part of continuous feedback |
|
|
Term
|
Definition
| design for immediate needs rather than future needs |
|
|
Term
|
Definition
| derives from the implemented software, the customer, and other team members |
|
|
Term
|
Definition
| The discipline to resist pressure to design for unspecified future requirements |
|
|
Term
|
Definition
| Courtesy among team members and stakeholders |
|
|
Term
| What are the tasks or activities for requirements engineering? |
|
Definition
| Inception, elicitation, elaboration, negotiation, |
|
|
Term
| What are the benefits of using analysis patterns during the analysis modeling process? |
|
Definition
| they speed up the the development of abstract analysis models that capture the main requirements of the concrete problem by providing reusable analysis models and facilitate the transformation of the analysis model into a design model by suggesting design patterns and reliable solutions for common problems. |
|
|
Term
| What work products result from elicitation? |
|
Definition
| a statement of need and feasibility, a bounded statement of scope for the system or product, a list of customers, users, and other stakeholders who participated in requirements elicitation, a description of the systems technical environment, a list of requirements and the domain constraints that apply to each, a set of usage scenarios that provide insight into the use of the system or product under different operating conditions, any prototype developed to better define requirements |
|
|
Term
| What questions should be asked to help refine a preliminary use case? |
|
Definition
Can an actor take some other action at this point?
Is it possible that the actor will encounter some error condition at this point?
Is it possible the actor will encounter some other behavior at this point? |
|
|
Term
| In collaborative requirements gathering, what is the role of the facilitator? |
|
Definition
| The role of the facilitator is to control the process. |
|
|
Term
| What are the primary advantages of the component-based process model for software engineering? |
|
Definition
| Component-based process models promote software reuse and re-usability and can result in a reduction in development cycle times, a reduction in project costs, and an increase in productivity. |
|
|
Term
| What does software do as a vehicle for delivering a product? |
|
Definition
| serves as a basis for computer control, communication, and creation of other programs. |
|
|
Term
| As a product, software is what? |
|
Definition
| An information transformer |
|
|
Term
| Describe the relationships among software engineering process and methods |
|
Definition
| Software process defines the framework that must be established for effective delivery of software engineering technology, by providing a context by which the software engineering methods are applied. |
|
|
Term
| The “Manifesto for Agile Software Development” proposes working software over what? |
|
Definition
| comprehensive documentation |
|
|
Term
| The “Manifesto for Agile Software Development” proposes valuing what over contract negotiation? |
|
Definition
|
|
Term
| The “Manifesto for Agile Software Development” proposes valuing what over following a plan? |
|
Definition
|
|
Term
| A frenzied work atmosphere in which team members do what can be considered toxic to a software team? |
|
Definition
| waste energy and lose focus on the objectives |
|
|
Term
| High frustration resulting in friction among team members caused by what kind of factors can be considered toxic to a team? |
|
Definition
| personal, business, or technological |
|
|
Term
| What type of procedures can be considered toxic to a team? |
|
Definition
| Fragmented or poorly coordinated |
|
|
Term
| What type of process model can become a roadblock to accomplishment, thus becoming toxic to a team? |
|
Definition
| poorly defined or improperly chosen |
|
|
Term
| Unclear definition of roles is considered toxic to a team because it can result in what? |
|
Definition
| finger-pointing and lack of accountability |
|
|
Term
| Continuous exposure to failure is considered toxic to a team because it can result in what? |
|
Definition
| loss of confidence and lowering of morale |
|
|
Term
| What is separation of concerns? |
|
Definition
| a design principle for separating a computer program into distinct sections, such that each section addresses a separate concern. |
|
|
