Lifecycle Management and Development Concepts
Focus of design, build, and disposal procedures of software systems.
Focus of design, build, and implementation standards of software systems.
Procedures affecting the design, build, and implementation of software systems.
Standards and procedures affecting the design, implementation and disposal of software systems.
Lifecycle methodologies.
Software quality assurance.
Software quality attributes.
Software quality verification and validation.
Usability.
Portability.
Reusability.
Interoperability.
Usability.
Portability.
Reusability.
Interoperability.
The coding phase is checked to see if what was specified during the design phase is accomplished.
The testing phase is exempt from quality assurance procedures.
The design phase is not involved in quality assurance.
Specifications are checked during the design phase.
Design.
Coding.
Testing.
Standards.
Analyze requirements, including constraints.
Use capable software processes.
Follow a disciplined process.
Explore alternative concepts.
Analyze requirements, including constraints.
Use capable software processes.
Follow a disciplined process.
Explore alternative concepts.
Software qualities.
Procedural modules.
Functions and procedures.
Software process improvements.
Level 1.
Level 2.
Level 3.
Level 4.
Level 1.
Level 2.
Level 3.
Level 4.
Software metrics.
Software acquisition.
Software quality assurance.
Configuration management.
Timely.
Unambiguously defined.
Drives appropriate action.
Data is economical to collect.
Timely.
Unambiguously defined.
Drives appropriate action.
Data is economical to collect.
How accurate is the navigation algorithm?
How much did the first modules cost?
How long did it take to fix the errors?
How good is this product?
Portability.
Reliability.
Verifiability.
Maintainability.
Portability.
Reliability.
Verifiability.
Maintainability.
Evaluate user requirements.
Document flow analysis.
Conduct feasibility studies.
Conduct system studies.
Where and how current system fails to meet the present objective.
The amount of time it takes to manually perform the process.
The amount of redundant processes that are performed.
The total amount of processes to perform.
Evaluating user requirements.
Graphical representation.
System studies.
Flow charts.
Before the document flow analysis.
After the document flow analysis.
After the feasibility studies.
After the system studies.
How independent each module is.
The interdependency of each requirement.
The length of time it will take to code the module.
How well each requirement interacts with each other.
Conduct system studies.
Document flow analysis.
System studies brief.
Feasibility studies.
Evaluating user requirements.
Document flow analysis.
System studies brief.
Feasibility studies.
System.
Segment.
Computer software component.
Computer software configuration item.
Computer software unit (CSU).
Hardware configuration item (HWCI).
Computer software component (CSC).
CSCI.
To identify the functional and physical characteristics of selected system components.
To record/report change processing and implementation status.
To solicit bids for contracts under configuration control.
To control changes to those characteristics.
Assist program managers in achieving the required system performance.
Document the alternative designs that meet operational requirements.
Control and account for the functional and physical characteristics.
Audit the established baselines.
Assist program managers in achieving the required system performance.
Document the alternative designs that meet operational requirements.
Control and account for the functional and physical characteristics.
Audit the established baselines.
Apply configuration management to the software life cycle.
Perform functional and physical configuration audits.
Maximize productivity by minimizing mistakes.
Avoid multiple copies.
Apply configuration management to the software life cycle.
Perform functional and physical configuration audits.
Maximize productivity by minimizing mistakes.
Avoid multiple copies.
Configuration status accounting.
Configuration identification.
Configuration control.
Configuration audits.
Configuration status accounting.
Configuration identification.
Configuration control.
Configuration audits.
Product.
Allocated.
Document.
Functional.
Designed to port to different memory configurations.
Easily changed to accommodate other hardware platforms.
Tied closely to the operating system to appear seamless to the user.
Transferable and not dependent on other hardware platforms or operating systems.
Engineering.
Open architecture.
Decrease flexibility.
Sacrifice a working system.
Must be controlled.
Includes provisions for change.
Must be maintained throughout the life cycle.
Must provide for enhancements at predetermined phases in the life cycle.
Plot out the different standards each service would adopt.
Critique the warfare and warfare support systems technical reference model.
Instruct the different services on the various open systems standards presently in place.
Adopt a paradigm for the development of all warfare and warfare support systems among the services.
No impact.
It will be easier, but more expensive.
It will be cheaper, as will hardware maintenance and support.
It will be cheaper, at the expense of hardware maintenance and support.
Reduce system costs.
Reduce acquisition times.
Improve information sharing.
Reduce the need for standards.
A baseline document that will not be updated to facilitate services reaching the standard.
An archived document that will be revived as needed.
A living document that will be periodically updated.
Being approved by each of the services in turn.
Portable Operating System Interface for Computer Environment (POSIX).
Government Open Systems Interconnect Profile (GOSIP).
Structured Query Language (SQL).
X-Windows.
Portable Operating System Interface for Computer Environment (POSIX).
Government Open Systems Interconnect Profile (GOSIP).
Structured Query Language (SQL).
X-Windows.
Commercial off the shelf.
Best commercial practice.
Commercial type.
Olive drab.
Develop requirements to ensure suppliers are informed on specific equipment of function required.
Conduct a general survey of market place to determine availability of potential sources.
Submit a request for proposal (RFP) to current suppliers requesting bids.
Collect information by contacting the market based on your specific needs.
After the preliminary design review (PDR) is completed.
After the Concept Exploration phase is completed.
During the PDR.
During the Concept Exploration phase.
User Interface.
Graphical User Interface.
Integrated Drive Electronics.
Integrated Development Environment.
User Interface.
Graphical User Interface.
Integrated Drive Electronics.
Integrated Development Environment.
Objects.
Projects.
Project window.
Properties window.
Forms.
Controls.
Properties.
Project Explorer.
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.