stud
bud
Sign up
Log in
Home
Library
Explore
SAT
More
Final Exam - Soft Eng 1 Flashcards | StudBud
Explore
/
Final Exam - Soft Eng 1
Final Exam - Soft Eng 1
50 terms
·
StudBud Administration
·
18 plays
Imported from external platform
Flashcards
50 cards
F
Practice quiz
P
Host live
L
Questions
50
Answers
1
Software components that implement a singlefunction, such as a mathematical function, or an object class may be reused.
Object and Function
Application Reuse
System Reuse
Component Reuse
2
Requirements are recorded on “story cards,” and the stories to be included in a release are determined by time available
Refactoring
Incremental Planning
On-site Customer
Pair Programming
3
The requirements are analyzed systematically by a team of reviewers who check for errors and inconsistencies.
Prototyping
Requirement Change
Requirements Review
Test Case Generation
4
____ is concerned with understanding how a software system
Design Pattern
Designing Stage
Architectural Design
Architectural
5
The cost implementing requirements changes is reduced.
Waterfall
Standard Process
Integration
Incremental
6
Tools that may be used include automated testing tools, to support configuration management, and system integration
Plan Driven
XP Release
Agile Development
Extreme Programming
7
Making the system architecture explicit at an early stage in the system development requires some analysis.
Stakeholder Communication
Large Scale Reuse
System Architecture
System Analysis
8
It depends on the type of system being developed, the background and experience of the system architect.
Design Pattern
Design Issue
Design Decision
Digital Design
9
____ is an everyday technique that we use to manage complexity.
Classes
Generalization
Hierarchy
Specialization
10
Reused by incorporating it without change into other systems or by configuring the application for different customers
System Reuse
Component Reuse
Application Reuse
Object and Function Reuse
11
Candidate components are evaluated to see if they meet the essential requirements and if they are suitable for use in
Waterfall
Evaluation
Incremental
Integration
12
Large amounts of overtime are not considered acceptable, as the net effect is often to reduce code quality productivity
Test first development
Small Release
Sustainable Pace
Simple Design
13
Early delivery and deployment of useful software to the customers is possible.
Integration
Waterfall
Standard Process
Incremental
14
This is the set of activities that assess the impact and cost of changes.
Traceability
Tool Support
A change management process
Requiement Identification
15
show the sequence of actions involved in processing input data and generating an associated output.
Agile Driven
Data Driven
Data Sequence
Data Access
16
Used when developing an oop system model to show the classes in a system and the associations between these classes.
Class Structure
Object Oriented Diagram
Class Modeling
Class Diagram
17
software display the organization of a system in terms of the components that make up that system and their relationship
Entity Model
Use Case Model
Structural Model
Class Model
18
These check that the requirements reflect the real needs of system users.
Validity
Completeness
Consistency
Realism
19
Is a highlevel presentation of the system that may be used as a focus for discussion by a range of different stakeholder
System Analysis
Stakeholder Communication
Large Scale Reuse
System Architecture
20
Web pages Classes are provided to help you define templates and to populate these dynamically with specific data
Design Pattern
Front End
Design Issue
Dynamic
21
Complete systems, which may be made up of a number of application programs, may be reused as part of a system of systems
Application Reuse
System Reuse
Object and Function Reuse
Component Reuse
22
Do not have to be elaborated in detail but includes brief descriptions of essential requirements and desirable features.
Waterfall
Integration
Incremental
Specification
23
Developers work in pairs, checking each other's work and providing the support to always do a good job.
Pair Programming
Simple Design
Small Release
Refactoring
24
Requirements management involves the processing of large amounts of information about the requirements.
A change management process
Requiement Identification
Tool Support
Traceability
25
If an application system that meets the requirements, it may then be configured for use to create the new system
Configuration
Integration
Waterfall
Incremental
26
The system customer works closely with the development team and discusses these scenarios with other team members.
Task Cards
Test Cards
Test Case
User Story
27
The software to meet the specifications must be produced.
Software Evolution
Software Validation
Software Development
Software Development
28
Collection of abstract and concrete classes are adapted and extened to create application systems
Architectural Patterns
Application Framework
Design Patterns
ERP Systems
29
Each requirement must be uniquely identified so that it can be cross-referenced with other requirements
Requirements Identification
Prototyping
Test Case Generation
Requirements Review
30
Two or more application systems are integrated to provide extended functionality
App. Patterns
App. Framework
Architectural Pattern
App. Sys. Integration
31
___ is a software engineering strategy wherethe development process is geared to use existing software.
Reuse-based
Developer-based
Server-based
Client-based
32
WAFs may include classes to help implement user authentication(login) and access control
Security
Dynamic
Database Integration
Session Management
33
Policies define the relationships between each req. and between the req. and the system design should be recorded.
Tool Support
Traceability
Requiement Identification
A change management process
34
As soon as the work on a task is complete, it is integrated into the whole system.
Pair Programming
Refactoring
On-Site Customer
Continuous Integration
35
As the requirements change problems are discovered, the system design or implementation has to be reworked and retested
XP Release
Plan Driven
Plan Driven
Extreme Programming
36
are models of the dynamic behavior of a system as it is executing.
System Modeling
Class Model
Behavioral Model
Structural Model
37
This takes the fundamental process activities of specification, development, validation, and evolution.
Standard Process
Integration and Configuration
Waterfall
Incremental Development
38
the architecture should be designed to localize critical operations within a small number of components
Availability
Security
Performance
Safety
39
Involves developing an executable model of a system and using this with end-users and customers meets their needs.
Prototyping
Test Case Generation
Requirements Review
Requirements Change
40
__ an application, ranging in size from subsystems to single objects, may be reused.
System Reuse
Component Reuse
Application Reuse
Object and Function Reuse
41
All developers are expected to refactor the code continuously as soon as potential code improvements are found.
Small Release
Sustainable Pace
Simple Design
Refactoring
42
To reduce the potential for dispute between customer and contractor, system requirements should always be written as ___
Consistency
Realism
Verifiability
Completeness
43
To handle these changes, agile methods do not have a separate requirements engineering activity.
Test Case
Story Card
Task Cards
User Stories
44
Software design involves identifying and describing the fundamental software system abstractions and their relationships
Waterfall
Incremental
Integration
Standard Process
45
The system’s services, constraints, and goals are established by consultation with system users.
Standrad Process
Waterfall
Integration
Incremental
46
With incremental development, there is no system specification that can be used by an external testing team
Testing Development
Task Cards
Test first Development
Test Case
47
The functionality of the software and constraints on its operation must be defined.
Software Specification
Software Validation
Software Evolution
Software Development
48
Requirements in the document should not conflict. should not be contradictory constraints or different descriptions.
Consistency
Validity
Realism
Completeness
49
Requirements document should include requirements that define all functions and the constraints intended by the user.
Validity
Completeness
Realism
Consistency
50
The __ movement has meant that there is a huge code base thatcan be reused. This may be in form of libraries.
Component
Open-source
System Reuse
Application Reuse