| Analysis phase | involves end users and IT specialists working together to gather, understand, and document the business requirements for the proposed system.
|
 |
|
|
| Business requirement | a detailed knowledge worker request that the system must meet in order to be successful.
|
|
|
|
| Critical success factor (CSF) | a factor simply critical to your organization's success.
|
|
|
|
| Design phase | the stage of system planning where the planner builds a technical blueprint of how the proposed system will work.
|
|
|
|
| Development phase | takes all of your detailed design documents from the design phase and transforms them into an actual system.
|
|
|
|
| Feature creep | occurs when developers add extra features that were not part of the initial requirements.
|
|
|
|
| Graphical user interface (GUI) | the interface to an information system.
|
|
|
|
| GUI screen design | the ability to model the information system screens for an entire system.
|
|
|
|
| Help desk | responds to knowledge workers' questions.
|
|
|
|
| Implementation phase | distributes the system to all of the knowledge workers and they begin using the system to perform their everyday jobs.
|
|
|
|
| Insourcing | means that IT specialists within your organization will develop the system.
|
|
|
|
| Joint application development (JAD) | occurs when knowledge workers and IT specialists meet, sometimes for several days, to define or review the business requirements for the system.
|
|
|
|
| Maintenance phase | monitors and supports the new system to ensure it continues to meet the business goals.
|
|
|
|
| Modeling | the activity of drawing a graphical representation of a design.
|
|
|
|
| Online training | runs over the Internet or off a CD-ROM.
|
|
|
|
| Outsourcing | the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service.
|
|
|
|
| Planning phase | involves determining a solid plan for developing your information system.
|
|
|
|
| Project manager | an individual who is an expert in project planning and management, defines and develops the project plan and tracks the plan to ensure all key project milestones are completed on time.
|
|
|
|
| Project milestone | represents a key date for which you need a certain group of activities performed.
|
|
|
|
| Project plan | defines the what, when, and who questions of system development including all activities to be performed, the individuals, or resources, who will perform the activities, and the time required to complete each activity.
|
|
|
|
| Project scope | clearly defines the high-level system requirements.
|
|
|
|
| Project scope document | a written definition of the project scope and is usually no longer than a paragraph.
|
|
|
|
| Proof-of-concept prototype | a prototype you use to prove the technical feasibility of a proposed system.
|
|
|
|
| Prototype | a model of a proposed product, service, or system.
|
|
|
|
| Prototyping | the process of building a model that demonstrates the features of a proposed product, service, or system.
|
|
|
|
| Request for proposal (RFP) | a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations (which we'll refer to as "vendors") to submit bids for its development.
|
|
|
|
| Requirement definition document | defines all of the business requirements and prioritizes them in order of business importance and places them in a formal comprehensive document.
|
|
|
|
| Scope creep | occurs when the scope of the project increases.
|
|
|
|
| Selfsourcing (also called knowledge worker development or end-user development) | the development and support of IT systems by knowledge workers with little or no help from IT specialists.
|
|
|
|
| Selling prototype | a prototype you use to convince people of the worth of a proposed system.
|
|
|
|
| Sign-off | the knowledge workers' actual signatures indicating they approve all of the business requirements.
|
|
|
|
| System development life cycle (SDLC) | a structured step-by-step approach for developing information systems.
|
|
|
|
| Technical architecture | defines the hardware, software, and telecommunications equipment required to run the system.
|
|
|
|
| Test condition | a detailed step the system must perform along with the expected result of the step.
|
|
|
|
| Testing phase | verifies that the system works and meets all of the business requirements defined in the analysis phase.
|
|
|
|
| User acceptance testing (UAT) | determines if the system satisfies the business requirements and enables the knowledge workers to perform their jobs correctly.
|
|
|
|
| User documentation | highlights how to use the system.
|
|
|
|
| Workshop training | held in a classroom environment and led by an instructor.
|