Accounting
Anthropology
Archaeology
Art History
Banking
Biology & Life Science
Business
Business Communication
Business Development
Business Ethics
Business Law
Chemistry
Communication
Computer Science
Counseling
Criminal Law
Curriculum & Instruction
Design
Earth Science
Economic
Education
Engineering
Finance
History & Theory
Humanities
Human Resource
International Business
Investments & Securities
Journalism
Law
Management
Marketing
Medicine
Medicine & Health Science
Nursing
Philosophy
Physic
Psychology
Real Estate
Science
Social Science
Sociology
Special Education
Speech
Visual Arts
Question
Traditional methods of collecting systems requirements include:A) interviews.
B) agile methodologies.
C) joint application design.
D) rapid application development.
E) prototyping.
Answer
This answer is hidden. It contains 1 characters.
Related questions
Q:
All of the following are types of user documentation EXCEPT:
A) release description.
B) reference guide.
C) acceptance sign-off.
D) entity-relationship diagrams.
E) user's guide.
Q:
Changing over from the old information system to a new one by turning off the old system as the new one is turned on best describes:
A) phased installation.
B) single location installation.
C) parallel installation.
D) direct installation.
E) rotation installation.
Q:
The organizational process of changing over from the current information system to a new one best defines:
A) reorganization.
B) physical design.
C) installation.
D) replacement.
E) system alteration.
Q:
User testing of a completed information system using real data in the real user environment refers to:
A) acceptance testing.
B) alpha testing.
C) beta testing.
D) system testing.
E) live testing.
Q:
The process of bringing together all of the modules that comprise a program for testing purposes is referred to as:
A) unity testing.
B) integration testing.
C) system testing.
D) implementation.
E) stub testing.
Q:
Testing each module alone in an attempt to discover any errors that may exist in the module's code is referred to as:
A) unit testing.
B) system testing.
C) stub testing.
D) singular testing.
E) a walkthrough.
Q:
A primary objective of using automated tools for systems development and maintenance is to change radically how code and documentation are modified and updated.
Q:
Build routines are software modules that have been tested, documented, and approved to be included in the most recently created version of a system.
Q:
The number of customers for a given system influences most of the costs associated with maintaining a system.
Q:
Today's environment makes it possible to maintain and update external documentation as long as desired.
Q:
A risk associated with the direct installation approach is that not all aspects of the new system can be compared to the old system.
Q:
During alpha testing, users test a completed information system using simulated data.
Q:
System testing is the process of bringing together all of the modules that a program comprises for testing purposes.
Q:
Walkthroughs are a very effective method for identifying errors in code.
Q:
Testing specialists are responsible for developing test plans, establishing testing standards, integrating testing and development activities in the life cycle, and ensuring that test plans are completed.
Q:
Which is the primary key(s) in the following STUDENT_GRADE(StudentID, CourseID, Grade)?
A) STUDENT_GRADE
B) StudentID
C) CourseID
D) StudentID, CourseID
E) Grade
Q:
If OrderNumber serves as the primary key in the ORDER relation and also appears as a nonkey attribute in the INVOICE relation, then OrderNumber is said to be a:
A) foreign key.
B) candidate key.
C) pointer.
D) relationship key.
E) marker.
Q:
The primary deliverable from logical database design is:
A) normalized relations.
B) design specifications.
C) an updated Baseline Project Plan.
D) a list of alternatives design strategies.
E) a production system.
Q:
Key physical database design decisions typically do not include:
A) choosing the storage format for each attribute from the logical database model.
B) grouping attributes from the logical database model into physical records.
C) arranging related records in secondary memory so that individual and groups of records can be stored, retrieved, and updated rapidly.
D) selecting media and structures for storing data to make access more efficient.
E) conducting requirements structuring.
Q:
Which of the following is NOT a key step in logical database design?
A) Combine normalized data requirements from all user interfaces into one consolidated logical database model.
B) Compare the consolidated logical database design with the translated E-R model and produce, through view integration, one final logical database design for the application.
C) Model how data flow through an information system, the relationships among the data flows, and how data come to be stored at specific locations.
D) Translate the conceptual E-R data model for the application into normalized data requirements.
E) Using normalization principles, develop a logical data model for each known user view for the application.
Q:
Designing the database for an Internet-based electronic commerce application differs significantly from the process followed when designing the database for other types of applications.
Q:
Multiple key retrieval is possible with sequential file organization.
Q:
Indexes should be used generously for databases intended primarily to support data retrievals.
Q:
Sequential files are practical for random row retrievals.
Q:
View integration is the last step of logical database design.
Q:
A recursive foreign key is a foreign key in a relation that references the primary key value of the same relation.
Q:
For a binary one-to-one relationship between two entities, A and B, the primary key of A becomes a foreign key in B and the primary key in B becomes a foreign key in A.
Q:
Each entity type in an ER Diagram becomes an attribute.
Q:
The creation of a separate relation is sometimes required to represent a relationship.
Q:
A relation is said to be in second normal form if the primary key consists of only one attribute.