Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
121 Cards in this Set
- Front
- Back
Overview of Project Management |
Step 1: create a work breakdown structure Step 2: analyze task patterns Step 3: calculate the critical path |
|
According to the Standish group only 1/3 of all software projects were |
According to the Standish group only 1/3 of all software projects were successful - met budget, schedue, and quality targets. |
|
project coordinator def |
A project coordinator handles administrative responsibilities for the team and negotiates with users who might have conflicting requirements or want changes that would require additional time or expense. |
|
project manager def |
Project managers typically performed for activities, or functions such as: planning, scheduling, monitoring, and reporting. |
|
project planning def
project scheduling def |
Project planning identifies all project tasks and estimates the completion time and cost of each.
Project scheduling involves the creation of a specific timetable, usually in the form of charts that show task, task dependencies, and critical task that might delay the project. |
|
Project monitoring def
Project reporting def |
Project monitoring requires guiding, supervising, and the coordinating of the project teams' workload.
Project reporting includes regular progress reports to management, users, and the project team itself. |
|
WBS abbr PERT abbr CPM abbr |
WBS Work breakdown structure PERT Program evaluation and review technique CPM critical path method |
|
person day |
person represents the work that one person cna complete in one day. |
|
SaaS |
Software as a Service is a model software deployment run application that is hsoted as a service provided to customers over the Internet Reduces cost |
|
Main patterns of development |
in-house purchase as a software package use outside consultant |
|
ASP |
Application service provider a firmt that delives a software application or access to an application by charging a usage or subscription fee |
|
Horizontal application
Vertical application |
Horizontal application is a software package that can be used in many different types of organizations
Vertical application is a software package designed to handlin information requirments for a specific type of business |
|
Tools used to evaluated development strategies' cost |
payback analysis return of investment net present value |
|
payback analysis |
payback analysus determins how long it takes an information system to pay gor itself throgut rediced cons and increased benefits |
|
ROI |
return of investment is a percentage rate that compares the total net benefits received from a project to the total cost |
|
Net present valie |
Net present valie of a project is the total value of the benefits minus the total valie of the cost with both cost and benefits adjusted to reflect the point in time at which they occur |
|
RFP RFQ |
RFP - request for proposal RFQ - request for quotation |
|
quality assurance |
The main objective of quality assurance is to avoid problems or to identify them as soon as possible. Poor quality can result from inaccurate requirements, design problems, coding errors, faulty documentation, and ineffective testing. |
|
Software engineering def |
Software engineering is a software development process that stresses solid design, accurate documentation, and careful testing. |
|
CMM |
CMM - Capability Maturity Model SEI designed a set of software development standards called CMM |
|
CMMI |
CMMI - Capability Maturity Model Integration a more recent version of CMM that integrates software and system development into a much larger framework called process improvement
CMMI• includes five maturity levels, from level I, which is referred to as unpredictable. poorly controlled, and reactive, to Level 5. in which the optimal result is process improvement. |
|
ISO 9000-3:2004 |
In 2004, ISO updated a set of guidelines called ISO 9000-3:2004, which provided a quality assurance framework for developing and maintaining software. According to ISO, a revision of this standard will be released in 2013. |
|
Application development def |
Application development is the process of constructing the programs and code modules that serve as the building blocks of the information system. |
|
module in application development |
module consists of related program code organized into small units that are easy to understand and maintain. |
|
Simplified model of an Extreme Programming (XP) project. Note the emphasis on iteration and testing. |
|
|
flowchart |
flowchart represents logical rules and interaction graphically, using a series of symbols connected by arrows. Using flowcharts, programmers can break large systems into subsystems and modules that are easier to understand and code. |
|
Pseudocode |
Pseudocode is a technique for representing program logic. Pseudocode is similar to structured English |
|
top-down approach in structured application development |
proceeds from a general design to a detailed structure |
|
Structure Charts in structured application development |
Structure charts show the program modules and the relationships among them. A structure chart consists of rectangles that represent the program modules, with a rrows and other symbols that provide additional in formation. Typically, a higher-level module, called a control module, directs lower-level modules, called subordinate modules. In a structure chart, symbols represent va rious actions or conditions. Structure chart symbols represent modules, data couples, control couples, conditions, and loops |
|
MODULE in Structure Charts |
A rectangle represents a module Vertical lines at the edges of a rectangle indicate that module 1.3 is a library module. A library module is reusable code and can be invoked from more than one point in the chart |
|
DATA COUPLE In Structure Charts |
An arrow with an empty ci rcle represents a data couple. A data couple shows data that one module passes to another. |
|
CONTROL COUPLE In Structure Charts |
An arrow with a filled circle represents a control couple. A control couple shows a message, also called a status flag, which one module sends to another. |
|
CONDITION in Structure Charts |
A line with a diamond on one end represents a condition. A condition line indicates that a control module determines which subordinate modules will be invoked, depending on a specific condition.
|
|
LOOP in Structure Charts |
curved arrow represents a loop. A loop indicates that one or more modules are repeated |
|
Condition in Structure Charts graph |
|
|
CONTROL COUPLE In Structure Charts |
|
|
MODULE in Structure Charts |
|
|
DATA COUPLE In Structure Charts |
|
|
Cohesion def |
Cohesion measures a module's scope and processing characteristics. A module that performs a single function or task has a high degree of cohesion, which is desirable. Because it focuses on a single task, a cohesive module is much easier to code and reuse. |
|
LOOP in Structure Charts |
|
|
Coupling def |
Coupling describes the degree of interdependence among modules. Modules that are independent are loosely coupled, which is desirable |
|
Phases of Drawing a Structure Chart |
STEP I: REVIEW THE DFDS STEP 2: IDENTIFY MODULES AND RELATIONSHIPS STEP 3: ADD COUPLES, LOOPS, AND CONDITIONS STEP 4: ANALYZE THE STRUCTURE CHART AND THE DATA DICTIONARY |
|
release plan from XP (extreme programming) |
release plan, which specifies when user stories will be implemented and the timing of the releases. Releases are relatively frequent, and each system release is like a prototype that can be tested and modified as needed. |
|
iteration cycle from XP (extreme programming) |
User stories are implemented in a series of iteration cycles. An iteration cycle includes planning, designing, coding, and testing of one or more features based on user stories. At the beginning of each iteration cycle, which is often two weeks long, the team holds an iteration planning meeting to break down the user stories into specific tasks that are assigned to team members. As new user stories or features are added, the team reviews and modifies the release plan. |
|
parallel programming from XP (extreme programming) |
parallel programming, two programmers work on the same task on the same computer; one drives (programs) while the other navigates (watches). |
|
test-driven design from XP (extreme programming) |
test-driven design focuses on end results from the beginning and prevents programmers from straying from their goals. Because of the magnitude and intensity of the multicycle process, agile testing relies heavily on automated testing methods and software. |
|
Desk checking |
Desk checking is the process of reviewing the program code to spot logic errors, which produce incorrect results. This process can be performed by the person who wrote the program or by other programmers. Many organizations require a more formal type of desk checking called a structured walkthrough, or code review. |
|
design walkthrough |
In addition to analyzing logic and program code, the project team usually holds a session with users called a design walkthrough, to review the interface with a crosssection of people who will work with the new system and ensure that all necessary features have been included |
|
unit testing def |
The testing of an individual program or module is called unit testing. The objective is to identify and eliminate execution errors that could cause the program to terminate abnormally, and logic errors that could have been missed during desk checking. |
|
stub testing def |
stub testing, the programmer simulates each program outcome or result and displays a message to indicate whether or not the program executed successfully. Each stub represents an entry or exit point that will be linked later to another program or data file. |
|
integration testing, or link testing. |
Testing two or more programs that depend on each other is called integration testing, or link testing |
|
system testing |
After completing integration testing, you must perform system testing, which involves the entire information system |
|
acceptance tests |
Successful completion of system testing is the key to user and management approval, which is why system tests sometimes are called acceptance tests. |
|
System documentation def |
System documentation describes the system's functions and how they are implemented. System documentation includes data dictionary entries, data flow diagrams, object models, screen layouts, source documents, and the systems request that initiated the project. System documentation is necessary reference material for the programmers and analysts who must support and maintain the system. |
|
Operations documentation def |
Operations documentation contains all the information needed for processing and distributing online and printed output. |
|
User documentation def |
User documentation consists of instructions and information to users who will interact with the system and includes user manuals, Help screens, and tutorials. |
|
System changeover def |
System changeover is the process of putting the new information system online and retiring the old system |
|
direct cutover approach |
direct cutover approach causes the changeover from the old system to the new system to occur immediately when the new system becomes operational. Direct cutover usually is the least expensive changeover method because the IT group has to operate and maintain only one system at a time. |
|
Analysts sometimes confuse phased and pilot operation methods. What is the difference |
Both methods combine direct cutover and parallel operation to reduce risks and costs. With phased operation, however, you give a part of the system to all users, while pilot operation provides the entire system, but to only some users. |
|
systems implementation phase consists of |
application development, testing, installation, and evaluation of the new system. |
|
Four changeover methods exist: |
direct cutover, parallel operation, pilot operation, and phased operation |
|
RAD |
Rapid Application Development (RAD) is a development lifecycle designed to give much faster development and higher-quality results than those achieved with the traditional lifecycle. It is designed to take the maximum advantage of powerful development software that has evolved recently |
|
CASE RIPP |
Computer-Assisted Software Engineering (CASE_ Rapid Iterative Production Prototyping (RIPP) - a precursor to RAD |
|
Rapid Application Development has four essential aspects |
Rapid Application Development has four essential aspects: methodology, people, management, and tools. |
|
RAD Stage |
Requirements Planning
User Design
Construction
Implementation |
|
query by example (QBE) |
language, the user provides an example of the data requested. |
|
Three data flow and process combinations that you must avoid |
Spontaneous generation - produces output but has input
Black hole - has input but no output
Gray hole - one input and one output, but the input obviously is insufficient to generate the output |
|
The symbol for a process |
rectangle with rounded corners and the name of the process appears inside |
|
logical model def |
logical model shows what the system must do, regardless of how it will be implemented physically |
|
physical model def |
a physical model that describes how the system will be constructed |
|
Data and process modeling involves three main tools |
data flow diagrams data dictionary process description |
|
systematic sample def |
for example select every tenth customer for review |
|
stratified sample def |
select representatives from each subset |
|
Hawthorne Effect |
the name comes from a well-known study performed in the Hawthorne plant of the Western Electric Company in the 20s
The purpose of the study was to determine how various changes in the work environment would affect employee productivity.
Result - productivity improved during observation whether the conditions were made better or worse |
|
REJ |
Rapid Economic Justification
MS has developed a method for measuring total costs and benefits called REJ |
|
TCO |
Total Cost of Ownership |
|
scalability def |
refers to a systems ability to handle increased business volume and transactions in the future |
|
decision tree |
decision tree is a graphical representation of the conditions, actions, and rules found in a decision table. Decisions trees show the logic structure in a horizontal form that resembles a tree with the roots at the left and the branches to the right. |
|
decision tree (scr) |
|
|
modular design |
modular design is based on combinations of three logical structures, sometimes called control structure, which server as building blocks for the process. Each logical structure must have a single entry and exit point. The three structure are called sequence, selection and iteration. Rectangle represent a step or process, a diamond represents a condition or decision, and the logic follow the lines in the direction indicated by the arrow. |
|
sequence in modular design |
the completion of steps in sequential order, one after another. One or more of the steps might represent a subprocess that contains additional logical structures.
|
|
selection in modular design |
The completion of one of two or more process steps based on the results of a test or condition |
|
iteration in modular design |
the completion of a process step that is repeated until a specific condition change.
|
|
context diagram def |
context diagram is a top-level view of an information system that show the system's boundaries and scope |
|
Leveling in process drawing |
Leveling is the process of drawing a series of increasingly detailed diagrams, until all functional primitives are identified
aka exploding, partitioning, or decomposing |
|
Balancing in process drawing |
Balancing maintains consistency among a set of DFDsby ensuring that input and output data flows align properly. |
|
Configuration management (CM) |
aka change control Is a process for controlling changes in system requirements during software development. CM also is an important tool for managing system changes and costs after a system becomes operational. |
|
Risk avoidance |
eliminates the risk by adding protective safeguards like installing a firewall to prevent unauthorized access |
|
Risk mitigation |
Mitigation reduces the impact of a risk by careful planning and preparation |
|
Risk transference |
this shifts the risk to another asset or party, such as an insurance compant |
|
Risk Acceptance |
Means that nothing is done. Companies usually accept a risk only when the protection clearly is not worth the expense. |
|
Capacity planning |
Capacity planning is a process that monitors current activity and performance levels, anticipates future activity, and forecasts the resources needed to provide desired levels of service |
|
What-if analysis |
This allows you to vary one or more elements in a model in order to measure the effect on other elements. |
|
Baseline def |
Baseline is a formal reference point that measures system characteristics at a specific time. System analysts use baselines as yardsticks to document features and performance during the system development process |
|
Software reengincering def |
Software reengincering uses analytical techniques to identify potential quality and performance improvements in an information system. In that sense, software reengincering is similar to business process reengineering, which seeks to simplify operations, reduce costs, and improve quality |
|
baseline |
A baseline is a formal reference point that measures system characteristics at a specific time. Systems analysts use baselines as yardsticks to document features and per-formance during the systems development process. |
|
The three types of baselines |
are functional, allocated, and product. The functional baseline is the configuration of the system documented at the beginning of the project. It consists of all the necessary system requirements and design constraints. The allocated baseline documents the system at the end of the design phase and identifies any changes since the functional baseline. The allocated baseline includes testing and verification of all system requirements and features. The product baseline describes the system at the beginning of system operation. The product baseline incorporates any changes made since the allocated baseline and includes the results of performance and acceptance tests for the operational system. |
|
operational costs |
include items such as supplies, equipment rental and software leases. |
|
Maintenance expenses |
vary significantly during the system's operational life and include spending ti support maintenance activities |
|
Maintenance activities |
include changing programs, procedure, or documentation to ensure correct system performance, adapting the system to changing requirements, and making the system operate more efficiently |
|
Corrective maintenance |
Corrective maintenance is performed to fix errors
|
|
adaptive maintenance |
adaptive maintenance adds mew capability and enhancements |
|
preventive maintenance |
improves efficiently |
|
preventive maintenance |
reduces the possibility of future system failure |
|
corrective maintenance |
corrective maintenance diagnoses and corrects errors in an operational system. |
|
types of coupling
|
describes the degree of interdependence among modules.
Loosely coupled - modules that are independent tightly coupled - one module is linked to the logic contained in another module |
|
Cohesion and coupling |
Cohesion and coupling are important tools for evaluating the overall design. It is desirable to have modules that are highly cohesive and looselycoupled |
|
Cohesion between modules |
cohesion measures a module's scope and processing characteristics. Module that performs as single function or task has a high degree of cohesion, which is desirable |
|
Capability Maturity Model (CMM) |
set of software development standards One of the development standards is CMM The purpose of the model was to improve software quality, reduce development time, and cut cost. |
|
CMMI |
Capability Maturity Model Integration (CMMI) is a newer model It integrates software and system development into a much larger framework called process improvement |
|
Payback analysis |
determines how long it takes an information system to pay for itself through reduced costs and increased benefits |
|
ROI |
return of investment (ROI) is a percentage rate that compares the total net benefits (the return) received from a project to the total costs (the investment) of the project |
|
Net present value (NPV) |
NPV of a project is the total value of the benefits minus the total value of the costs, with both costs and benefits adjusted to reflect the point in time at which they occur. |
|
object-oriented analysis |
describes an information system by identifying things called objects objects represents a real person, place, event, etc |
|
Payback analysis |
determines how long it tales an information system to pay for itself through reduced costs and increased benefits |
|
ROI |
ROI = return of investment is a percentage rate that compares the total net benefits received from a project to the total cost of the project |
|
NPV |
NPV = net present value Of a project is the total value of the benefits minus the total value of the costs, with both costs and benefits adjusted to reflect the point in time at which they occur |
|
data dictionary (data repository) |
is a central storehouse of information about the system's data. An analyst uses the data dictionary to collect, document, and organize specific facts about the system, including the contents of data flows, data stores, entries, and processes. A data dictionary also defines and describes all data elements and meaningful combinations of data elements. |
|
data element (def) |
called data item or field The smallest piece of data that has meaning within an information system |
|
data structures |
data elements are combined into records, also called data structures.
A record is a meaningful combination of related data elements that is included in a data flow or retained in a data store. |
|
process description |
documents the details of a functional primitive, and represents a specific set of processing steps and business logic |