​IT professionals recognize that successful systems must be user-oriented, and users need to be involved, formally or informally, at every stage of system development.

​A single site visit usually gives true pictures, so it is unnecessary to visit more than one installation.

​Personal observation allows a systems analyst to verify statements made in interviews and determine whether procedures really operate as they are described.

​System requirements serve as benchmarks to measure the overall acceptability of a finished system.

Network administration includes hardware and software maintenance, support, and security.​

​Compared with traditional methods, the entire rapid application development (RAD) process is expanded and, as a result, the new system is built, delivered, and placed in operation much later.

System developers can initiate a formal project as early as the preliminary investigation stage, or later on, as analysis, design, and implementation activities occur.

When assessing schedule feasibility, a systems analyst must consider the interaction between time and costs.​

​The prior experience method to make time and cost estimates works best for large projects.

​System documentation always is up-to-date.